JP6820956B2 - Systems and methods for identifying information relevant to a company - Google Patents

Description

This disclosure relates to enterprise software, in particular to software that assists in discovering information related to problems, opportunities, and / or events of interest that are unexpected or of interest, affecting the processes performed by the enterprise.

A company (which may be any organization that carries out activities for a purpose) generally has goals and processes designed to achieve these goals. In general, problems within an enterprise will affect the success of one or more processes. These issues must be focused and identified in an efficient manner. People in the enterprise (users of the enterprise system) need to be warned of problems that can pose risks to the processes they are responsible for. Users who need to resolve a problem will want to be free to use information related to the problem, especially information about concurrency and past experience within the company related to the problem. The user may also want to work with other users in solving problems.

Therefore, it is desirable to implement a system that identifies and retrieves information related to the problem associated with the process and guides the information to the user who is most interested in the problem.

The disclosure provides systems and methods for discovering and retrieving information within a company related to company problems, company opportunities, and events of interest or unexpected interest. When the system searches for company information, current items (eg, e-mail being circulated) and past items (stored notes) are used to increase knowledge of the system related to problems, opportunities, or events. ) Is indexed.

According to the first aspect of the present disclosure, a process performed by a company, or a process of discovering information related to a company's importance of said process, is such that it scans content related to the process performed by the company. Containing a configured computing device, the process comprises one or more process steps, the computing device being a problem or opportunity or event (enterprise) associated with the process step. Identify (important points); index the scanned content for the corporate important point; determine if the scanned content is information related to a problem, opportunity or event; to the user. , Provide relevant information. The relevant information includes statements or reviews of the company's (or related companies') past experience with respect to an issue, opportunity or event. The scanned content may include e-mail communications to or from the company; documents generated by the company; and / or web content accessible to the company. Corporate importance is an event of problem, opportunity or unexpected or interest, with respect to other important points further describing the cause, effect, improvement (relief).

Determining whether information is relevant to a problem, opportunity, or event involves determining the impact of completing a process step on achieving goals related to the process, including the process step. This is called the goal proximity of the process step. The process step goal proximity may also be used to determine risk, which is an important relevance criterion.

Also, the determination of goal proximity may be used to find similar processes that are considered similar due to their similarity in a comprehensive view of the process and their proximity to goals. Experiences related to those similar processes are responsive from the system to get the user's attention.

Relevance decisions are facilitated by identifying processes characterized by comprehensive process components within the system so that inferences of similarities or relationships between processes are drawn from their comprehensive perspective. You may. In addition, endemic problems or opportunities embedded in the process establish further similarities and relevance between the processes.

The system comprises a scanner for scanning content related to a process executed by the enterprise; a language parser that identifies concepts within the scanned content; and a process node (process node). Indexes the scanned content related to the problem, opportunity or event) and determines whether the scanned content is related to the problem, opportunity or event. Including. The language parser and index engine assign a stress point relevance to the concepts in the scanned content, thereby generating an important point index for the item in the scanned content. To do.

In addition, the system may further include a user interface that utilizes the key point index to achieve the following; warn the user of problems associated with a set of related processes; collaborative users (stakeholders). Limiting the information given to the process to past concurrency information about the process, and the information about the subordinate process is likely to pose a risk (process risk) to the collaborating group (stakeholders). For example, by providing the user with information about the subordinate process, the cooperation between the users to deal with the problem or opportunity associated with the process is realized; the description or examination of the past experience related to the problem associated with the process. Search for information that includes. In the embodiment, the index engine is a middleware service.

According to another aspect of the disclosure, the user may manipulate (navigate) a cognitive structure that retrieves past and present experience used for the various uses described herein.

According to this disclosure, even if the following decisions are made when solving a company's problem, taking advantage of a company's opportunity, or explaining an interest or unexpected event that occurs in a company's activities: Good; by associating the content or data with the relevant corporate key points (process nodes) or the elements of the cognitive structure that are most closely related to these process nodes, the relevance of the content or data item to the company is complete. Determined; seeing process identification and their comprehensive process components, the goal proximity of the process to which the process is subordinate in each process, unique issues, and opportunities and events associated with the process. Completely determines the similarity between processes; when a process node contained in one step is determined to be risky, (i) the step relative to the direct goal of the step. Goal Proximity, (iii) Goal Proximity of the Step and its Impact on Further Dependent Goals of the Step, (iii) Estimated Cost of Failed Goals and Actions to Improve It, (iv) The Node By referring to the possibility of failure due to, the severity (importance) of the risk is completely determined.

Those skilled in the art may better understand the detailed description of the disclosure below, as the aforementioned matters have outlined the preferred features of the present disclosure fairly broadly. By forming the claims of the present disclosure, additional features of the present disclosure are described. Those skilled in the art should recognize that they can readily use the disclosed concepts and well-defined forms as the basis for designing and modifying other structures that perform the same purposes as the present disclosure. It should be recognized that such other structures do not deviate from the spirit and scope of the present disclosure in the broadest form of the present disclosure.

FIG. 1 systematically illustrates a company with goals and processes using software that discovers relevant information linked to the company in the form of the present disclosure.

FIG. 2 systematically shows one perspective of process nodes for corporate processes.

FIG. 3 systematically illustrates the abstracted activities that form the basis of the definition of process nodes.

FIG. 4 illustrates the processes associated with a company's goals.

FIG. 5 illustrates some details of the two processes and the problems associated with these processes.

FIG. 6A illustrates goal proximity for various process steps.

FIG. 6B illustrates interactions between actors within an enterprise and predetermined process steps.

FIG. 7A systematically illustrates a comprehensive process as well as a more specific process.

FIG. 7B systematically illustrates a process including a process node or a corporate key point.

FIG. 8 systematically illustrates process nodes showing risks, causes, consequences, and improvements associated with multiple processes.

FIG. 9 is a flow chart illustrating the process by which an expert user assigns node attributes at a level specific to the various contexts of the abstraction.

FIG. 10 is a flow chart illustrating a process according to the embodiment of the present disclosure, which identifies a comprehensive process and a process similar to a predetermined original process.

FIG. 11 is a flowchart illustrating a process according to the embodiment of the present disclosure in which an expert user establishes a system of events or reappearance stories.

FIG. 12 is a flow chart illustrating a method according to the embodiment of the present disclosure in which software builds and integrates corporate key points.

FIG. 13A is a series of flowcharts illustrating steps performed by a user of a system of the present disclosure form in order to solve a problem or take advantage of an opportunity. Reference numeral 13B is a series of flowcharts illustrating steps performed by the user of the system of the present disclosure form in order to solve a problem or take advantage of an opportunity.

FIG. 14 systematically illustrates a system according to the embodiment of the present disclosure that collects information and indexes information on important points of the enterprise.

FIG. 15 systematically illustrates the convergence of goals according to the embodiment of the present disclosure.

FIG. 16 systematically illustrates a system used by a plurality of users, including users with restricted viewing privileges.

FIG. 17 systematically illustrates an emergency management system known in the prior art.

FIG. 18 systematically illustrates the emergency management system according to the embodiment of the present disclosure.

FIG. 19 is a diagram showing more elements in the emergency management system of FIG. 18, which illustrates the display of selected nodes.

The software that embodies this disclosure is referred to herein as an "overlay." Overlays help you discover information within your enterprise. This source is typically enterprise internal context and enterprise data, including communications within the enterprise and communications between the enterprise and external organizations. Other sources of information are external information related to the company that the company wants to access on a regular basis. From one perspective of overlays, overlays act as a relevance engine, as opposed to a search engine. Overlays search only for information that may be relevant to a company's problems, company's opportunities, and unexpected or interesting events.

Overlay software is a business of relevance between corporate processes and of corporate importance within such processes (ie, dangers, expected failures, conflicts, risks, common causes, areas related to attention and knowledge). Use the relationships between the focus points). Overlay software provides users with only the appropriate returns (search results) from potential data and content so that the following can be achieved: Relationships between the above corporate processes, relationships between corporate important points Use sex.

Overlays provide overlay users with an overview of the changes underlying any enterprise software / e-mail that may constitute the enterprise importance for which they are responsible. In large organizations, it is not possible for senior staff to manually navigate and monitor all applications. In addition, it is not possible for the senior staff member to perform hard wired workflows for all possible events that could potentially constitute a problem. Since corporate importance is often caused by the combination of multiple events, overlays help identify those corporate importance. Overlays also withhold frequent notifications if they are not desired.

Overlays allow users of overlays to access corporate content and / or data systems (including e-mail systems) from remote locations using mobile devices. In addition, overlays allow for filtered drawing of events that affect corporate importance.

Overlays allow overlay users to handle events and equivalent alerts, as well as enriched content for which the user has knowledge related to metadata.

Overlays allow users of overlays to manage unwanted events that are supported by the relevant legacy content.

Glossary

Cause: An event that occurs or is a potential event that will cause the result.

Source: An event that occurs or is a potential event that may be the reason for the cause.

Impact: An event that occurs or is a potential event that will affect the process, plan goal, or conditional goal.

Risk: Potential impact. This has a positive meaning when dealing with opportunities and a negative meaning when dealing with problems.

Diagnosis: Finding the cause of a problem and explaining the cause of an event or opportunity of interest.

Organize: Abstraction, generalization, grouping.

Goal Proximity / Proximity: The ratio of the effect of a process step on the goal of the process to which the step belongs.

Goal, or Conditional Goal: A goal, or conditional goal, designed in a corporate process.

Cognitive structure: A structure that indexes information in a way that conforms to known recognition principles.

The main means of gaining a deeper understanding of a problem or opportunity: A method of determining the most appropriate relevance of a problem or opportunity.

Event / Review / Description / Experience: These are empirical events that can describe all or part of the cause, effect, risk, or improvement. These may include a generalized description, a generalized model for describing how things behave within the process to which they are assigned.

Model: A generalized event that explains the cause and effect.

Description: A description of the problem, opportunity, or unexpected event.

Attribute: A characteristic of the entity described in this disclosure. Node attributes are used to determine node similarity. That is, it is a characteristic of the node that determines the similarity. Node attributes are represented in the state model. That is, the characteristics of the node are represented in the state model.

Responsible: A situation in which the attributes of an actor have a significant impact on the output of a process or process step.

Problems / Failures: In this disclosure, problems and failures are problems reasonably expected by experienced practitioners and / or nodes considered within the process of failure, or unexplained phenomena, or It is a phenomenon of cause and effect that is not explained.

Opportunity / Success: In this disclosure, opportunity and success are the nodes considered in the process of problems and / or failures reasonably expected by an experienced practitioner.

Events / Unexpected Events / Events of Interest: In this disclosure, an event is an event that occurs, which an experienced practitioner considers important to the company and its goals.

Process node: A well-experienced practitioner is part of the process of anticipating problems and opportunities.

Experienced Practitioners: Those who have been responsible for the processes that are determined to be experienced in most of their work experience, the specific process, and its master. Those who are aware of these characteristics, who are aware of processes that are subordinate to and subordinate to processes that are considered to have a wealth of experience.

Enterprise: Any organization, or collection of organizations, that operates for one or more known purposes. The predictability of goals in one go, the predictability of plans and processes to achieve those goals, and the values, skills, information, endurance, and emotions that are virtually known in relation to the goals. It is generally characterized by an actor having.

Corporate activity structure; a framework related to the standards of relevance recognized by practitioners in many areas.

Corporate activity: An activity recognized by practitioners in each field or one or more fields.

External Processes: External processes that occur outside the enterprise to which some enterprise processes are subordinate, such as design, construction, education, and preparatory activities that can be part of any process step. A process that is not designed to serve known goals, but is found to occur in environments that affect corporate processes and goals (eg, human activity at discretion). Or it is a process that is not directly related to human activity, such as an environmental phenomenon.

Practitioners: Business people with average experience.

Overlay: The system and / or method according to the present disclosure.

Unique Problems / Opportunities / Nodes: Problems, opportunities, or unexpected / potential / occasional occurrences at different levels of abstraction considered by experienced practitioners that iterate through various related processes. It is an event to be done. Problems and opportunities cannot be defined without defining the first goal. Therefore, unique problems / opportunities are associated with goals.

Object: An object in some area of the process.

Context: The environment within the field in which the process occurs.

Abstracted Object: An object that may be abstracted and, as a result, an object that may be applied in more than one area.

Abstracted Context: A context that may be abstracted and, as a result, a context that may be applied to more than one area.

Area: Industry, company sector, or any corporate structure. Here, the corporate structure means that a process step and a technology are specified, and a practitioner can understand the process step and the technology.

Immobilization: A characteristic of an entity in a corporate activity model. Practitioners expect the property to be sufficiently constant and predictable, so the property is considered to be variable but constant.

Relevance Criteria: Any entity that helps build a corporate activity model or corporate activity structure.

Environment: Context, runtime, or something similar.

Process: A set of actions that helps combine goals and conditional goals. Processes range from fixed processes to established processes, newly established processes, and planning of processes to be performed.

Script: A fixed, conscious and potentially executed process.

Planning: Planning is a less-defined process in which steps within a process are ordered in a way that suits the current environment. The hierarchy of planning goals is often different from the underlying process associated with the plan.

Inanimate process: A process that does not involve human intervention (eg, a chemical process) and has no goals other than the goals of a process artificially set as part of the process. It may be good. Corrosion, for example, is a non-living process that is predictable and well known, but is not considered as a process-based goal.

Animate processes that are not based on goals: Processes that people experience but are not based on clear goals, such as valuing a particular type of music or preferring a particular color. .. The common term for this is arbitrary.

Conditions: As defined in English and AI (artificial Intelligence).

Corporate goals and processes

As systematically shown in FIG. 1, a company 1 generally has a goal 11 and a process 12 designed to achieve the goal. Companies, and their fields, generally have the following attributes with respect to goals: a set of values, a set of skills, a set of knowledge, a set of information, a set of endurance, a set of emotions. One or more companies may belong to one sector, defined as an industry, a division of a company, or any corporate structure. Here, the corporate structure refers to a structure in which a process step and a technology are specified and a practitioner can understand the process step and the technology. Therefore, it may be said that practitioners in a given field share unique knowledge.

Goal 11 directly affects the corporate goal (often expressed at a high level, so company-specific processes are not associated with the corporate goal), the main goal (one or more corporate goals). Achievements), and conditional goals (ie, goals that are not the top priority for designing a process and, when not achieved, may prevent the achievement of the main goal, or the main goal. The process may be based on goals (generally performed by corporate actors who act to achieve the goals), which can achieve the goals but achieve what they do not want. Alternatively, the process may not be goal-based, but may usually be artificially defined and designed. Alternatively, the process may not be goal-based and may not be artificially defined or artificially designed. The process may include mechanical functions. Alternatively, the process may include any process that is artificially designed for the goal one seeks, but is not necessarily artificially defined. There are risks, problems and opportunities when performing various processes within a company. These problems have causes, consequences, risks, potential impacts, and improvements.

Part 13 of the process in which a risk, problem, or opportunity is shown to be an experience that can present them, or is occupied as an experience in which an unexpected event or an event of interest can occur, is referred to as "corporate importance" or. Called a "process node". Process nodes are often identified by actors 15 who have experience within the enterprise. The overlay software 16 according to the form accessed as a service on the Web 100 by a company searches the company's internal contents and data 14, and sometimes external data, and generates information in which the identified important points are indexed. To do. The indexed information then has an important point relevance assigned to it. Overlays search natural language searches based on process nodes within the enterprise and word expressions used to describe natural language. The overlay also searches for structured data that is known to be relevant to each process node.

More generally, the process may be either an internal process or an external process, or a combination of the two. Internal processes are defined within the enterprise, and external processes are those that occur outside the enterprise and are preparatory activities that can be part of design, construction, or education, and any process steps. Is. A process is not designed to serve a known goal, but may be a process that is discovered to occur within a corporate process and an environment that affects the goal (eg, the activity of any person). .. Alternatively, the process may be a process that is not directly related to human activity, such as an environment-dependent phenomenon.

Process node

As systematically shown in FIG. 2, process nodes 21 are characterized by one or more problems, opportunities, and / or unexpected / interesting events within a process or process step of a process. Be done. In the natural language search 23 of the corporate data and internal content (and other sources of information) 24, the word expression 22 that describes the process node is used.

A company's process nodes represent components of the cognitive structure (detailed below). Process nodes as a component of a cognitive structure are problems and / or opportunities for practitioners to discover goals and / or process relevance within a company, or sometimes outside the company's direct scope of activity. And / or includes review or description of the event. Activities outside the direct scope of such a company may include other companies, the business world, the political environment, the social environment, the physics environment, the biological environment, or any environment that significantly affects the corporate process. It may be, but it is not limited to these.

The process node may include differences in the review and / or description of potential issues, opportunities, events, as follows:
(A) Review and / or description or data regarding a problem or opportunity or unexpected event in performing one or more goals, or conditional goals, within the process below.
(1) Processes that are considered to be affected at the time of consideration, description, or subsequent time.
(2) A process that becomes a component of a process that is subordinate to the affected process.
(3) A process that includes a problem or opportunity that can become active if a subordinate process fails.
(4) A process that includes a problem or opportunity and / or a potential problem or opportunity within a subordinate process to the affected process.
(B) Examination and / or description or data regarding the following.
(1) Review and / or description or data regarding the description of a problem, opportunity or unexpected event.
(2) Examination and / or description or data regarding the analysis of the cause of a problem, opportunity, or unexpected event.
(3) Examination and / or description or data regarding the cause (cause of the cause) of a problem, opportunity, or unexpected event.
(4) Review and / or description or data on plans that may be considered as actions to improve the problem or take advantage of the opportunity.
(5) Review and / or description or data on procedures that describe how to avoid problems or seize opportunities.

Examinations or descriptions relating to process nodes can be expressed in text or drawings, or in any combination that constitutes the customary expression used in corporate software or content. This may include, but is not limited to, spreadsheets, e-mails, documents, metadata, data in databases, electronic messages, voice communications and the like.

The recognition structure considered in the present disclosure is a structure having information indexed by a method conforming to a known recognition principle, and the recognition principle allows the determination of the relevance of the information. It is configured to be related to each other.

As systematically shown in FIG. 3, the recognition structure 33 is an abstract expression of daily activities and objects related thereto. These are activities and objects that are familiar to the average practitioner outside the scope of the enterprise. Because they are used daily in business activities in many areas. Such corporate activities and objects 32 generalize users, user roles, tasks, contexts in which tasks and processes occur, corporate objects, processes, goals, skills, values, actors within processes, any of these. Including, but not limited to. A given process node represents a component of the recognition structure. All nodes and entities in the cognitive structure may be abstracted and / or other abstracted entities.

Therefore, the recognition structure 33 may include the following.
goal;
Goals and related processes, and associated unique nodes (detailed below);
Companies, corporate departments, associated roles, actors, and attributes (eg skills, values, etc.);
Generalized process node;
Unique process node;
Low-level goals and associated process steps;
Tasks and actors or roles that define the tasks;
The context, and the associated process or task that the context affects;
Objects and associated processes or tasks that they affect;
Workflow;
User

Overlay software also discovers information related to any process or process node, or any element of the cognitive structure. The information retrieval method used by the overlay software applies to this relevant information. Also, these search methods apply to many elements of the recognition structure.

The word "relevant" is related as a process at risk, as an additional process at risk, a causal process, an abstracted causal process, an additional causal process, Processes of action for improvement, being involved as processes similar to any other process, being associated by a common context or object or their abstractions, being associated by a common node or abstraction, common It includes, but is not limited to, goals or conditional goals, or being associated by a combination thereof.

If the information is not the primary means of gaining a deeper understanding of the problem, opportunity, or event of interest / interest, the information is irrelevant to the purpose of the overlay.

As described in detail below, the relevance of a company to an item or data of content may be entirely determined by the company's key points (process nodes).

Process analysis; process similarity

FIG. 4 is a systematic diagram showing some goals and some processes for one company. In this figure, the set of goals 41 for the entire enterprise has a number of processes designed to achieve these goals. One process 42 has a plurality of steps 43. The companies illustrated are companies that carry out goods transportation, especially transportation including sea transportation. Therefore, in the field of companies dealing with "Navigation", there is another set of goals 44. In this example, the process 45 for navigating from one point to another has a plurality of steps 46: The plurality of steps are to see (for example, to find a navigation goal), to move (for example, to operate an engine), and to set a course at a requested position. As shown in more detail in FIG. 5, the process step of "seeing" has the need for eyeglasses. Therefore, the loss of eyeglasses is a component of the problem of the process step.

Even companies in different disciplines (eg military training) with different goals 47 (eg firing guns on the ground) have several process steps similar to the navigation process 45. Is also good. The group of goals 47 includes a main goal (“fire a gun”, “hit a target”) and a conditional goal (“avoid other objects”, “avoid explosion”). The conditional goal "Avoid explosion" needs to be met so that the goal "Fire a gun" is achieved in the desired way. The process 48 for achieving the goal "fire a gun" includes a "see target" step 49. The activity "seeing" may be determined as a comprehensive activity related to both processes. In addition, process 48 includes step 50 for "adjusting the gun." The process step for "adjusting the gun" has the need for a wrench, and losing the wrench is a component of the problem in that process step. Losing eyeglasses and losing a wrench may be determined as a comprehensive problem (ie, a comprehensive node), ie, "lost tools".

In FIG. 5, some nodes, and some processes, are labeled as context-specific and comprehensive in the context. It can be seen that even processes in different fields relate to comprehensive processes and comprehensive nodes. More generally, once context-specific nodes have been identified, those context-specific nodes define a more comprehensive node. These more comprehensive nodes then define comprehensive components in context / field-specific processes in a given field. These inclusive process components, and their inclusive nodes, will be in other areas at some level of inclusiveness and, as a result, show nodes that are specific to this different context / area. right.

A process node may resemble other process nodes. This is determined by the process similarity, or process step similarity, described in detail below. As shown in FIG. 5, the process steps of different processes often have something in common. When one process step is common to two processes, the two processes are considered similar if the process step can influence the goals of the main process to which the process step belongs in the same way. The effect of a process step on the goal to which the process step belongs is referred to as the "goal proximity" of the process step.

Overlay software discovers similar processes and discovers similar events to problems and / or opportunities for a given process node by showing similar events with similar processes and process nodes and goal proximity. In this regard, it should be noted that overlays do not rely on a vast combination of process conditions for event similarity. Overlay evaluates process similarity from goal proximity, node similarity, and abstracted or unique nodes (abstracted or unique nodes define an abstracted process). It provides an alternative way to do this, because at the most abstract level, the process is devised to handle highly abstracted and unique nodes). In a given process, process conditions are included within the process. Therefore, the discovery of similar processes will define conditions that are comparable. This is because, in reality, prominent conditions are carried into process nodes (process problems and opportunities). Therefore, if the process node defines the criteria for the process, the process node is also sufficient to define the conditions within the process.

It should be noted that overlays search for similarities contained in both processes and nodes. In general, a process is developed so that problem nodes are avoided and opportunity nodes are pulled out. A given process may have one or more nodes. As a result, node similarity will be included in process similarity.

In addition, the hierarchy of goals within the process influences the determination of similarity. The hierarchy of goals in the process and the hierarchy of conditional goals determine the profile of the goals in the process. This is thought to be an additional determination of process similarity characteristics. Processes with a hierarchy of similar goals will be similar. Therefore, process similarity does not depend solely on common processes, or common generalizations for those process steps.

Goal proximity; chance of success

In general, not all process steps are equally essential to achieving the success of a process goal. As mentioned above, the word "goal proximity" means the effect of a process step on the goal to which the process step belongs. The goal proximity of a process step may be quantified by how close the process step is to achieving success or failure with respect to the goals or conditional goals of one or more processes. For example, as shown in FIG. 6A, the achievement of the goal "fire gun" is determined to be 50% depending on the completion of the process step "adjust gun". Achieving the goal "hit the target" is determined to be 70% depending on the completion of the process step "seeing the target". These relationships are systematically shown by arrows 61 and 62 in FIG. 6A. As a result, problems within a process step with high goal proximity will have a greater impact on the success of the process. Goal proximity provides an additional measure of process similarity. Processes that have similar influences to the goals of subordinate processes, and processes that also have common inclusive or specific characteristics (eg, common nodes), are considered similar, even if they occur in different disciplines. ..

Abundance of resources (or lack of resources) is considered to be an attribute of process steps within the process. Therefore, resource redundancy affects process goal proximity. Moreover, depending on the abundance of the process, or the redundancy of the process, problems or opportunities within the process affect the proximity of the process step to the goal.

Also, the actor (the person who runs the process, or the person who does not run the process but is involved in the process) influences the success of the process. As systematically shown in Figure 6B, actors primarily influence the process steps for which they are responsible. In general, actors have the following attributes: values, skills, expertise, information, endurance, and emotions. Other actor attributes may be considered relevant, depending on the process step. The attributes then affect the likelihood of an expected problem or opportunity related to the process step and, as a result, the goal of the process. As illustrated in FIG. 6B, the actor 63 responsible for "seeing an object" is a skill that affects one or more objects 65 associated with a process step and the context 66 in which the step is performed. , Value, knowledge 64. If the object used in the "see target" step is a scope for viewing and the context is fog, the skill of the actor who uses the scope to see the target in the fog is Greatly influences success. From this example, it can be seen that the process step itself also has a goal (“finding an object using a scope”), and that the actor's attributes affect that goal. In general, a process step that an actor executes or influences has a goal and a conditional goal. And it is the goal of these steps, or the components of these, or the conditional goal that the attributes of the actor influence.

Comprehensive processes and nodes

Processes can be abstracted into comprehensive process groups. The process may belong to a comprehensive group or may have a comprehensive process step. For example, navigating a ship may belong to the comprehensive process of "traveling in control of a car or ship." And it has comprehensive components such as seeing, steering, planning, etc. A comprehensive process is one that is not discipline-specific and is recognized by practitioners with average expertise in other disciplines. In general, a process has a comprehensive component or belongs to a more comprehensive process.

A comprehensive process is one that is less specific to the context in a given area. As the process reaches a higher level of abstraction, it becomes less specific and contains more generalized nodes. Processes with the least specificity to the context may be very general so that they do not have specific steps, and as a result, identify from other than the unique node (detailed below). May be difficult.

The inclusive process may be represented as systematically illustrated in FIG. 7A. The high level goal group 71 has a child goal group 72, followed by the child goal group 72 having child goal groups 73, 74. Processes 75 and 76 are designed to achieve goals 73 and 74, respectively. The solid boundaries of processes 75 and 76 in the figure indicate that these processes are field-specific. The dotted line represents the inclusive process 77 or the inclusive process substep 78.

A comprehensive process has nodes, contexts, and objects generalized from many disciplines of processes that have been discovered by practitioners and the general public to be part of many disciplines of processes. The comprehensive process may be biased towards one or more specific areas with few attributes when all areas are considered. This applies to contexts, objects, generalized nodes, etc. (but not limited to these).

Process nodes may be systematically represented as illustrated in FIG. 7B. Nodes are found in each of the three process steps in process 700 and in each of the two process steps in process 710. Each of Nodes 701-705 may be a risk, cause, effect, or improvement related to a problem / opportunity / event that occurs in connection with that process, or a plurality of other processes.

In process 700 shown in FIG. 7B, each of process steps 711-733 has a goal proximity with respect to goal G1. Elsewhere, each of process steps 711-733 has the potential for process failure if the node represents risk. These concepts are used to analyze the risks associated with the process. In overlay software, unlike other risk analysis methods, risk is specified by goal proximity or otherwise by assessing likelihood. As mentioned above, goal proximity is a specified percentage of the extent to which a goal or conditional goal within a process is affected by the success or failure of a subordinate process. The goal proximity of processes with the same level of subordinate or subordination is added to the overall 1 or 100%. Each dependent process depends on a process of equally low level of subordinate. For example, in the process of navigating, determining the direction of a ship depends on propulsion and 100% steering. The propulsion and steering of 100 depends on the power. The process at the level of determining the direction of a ship has equally subordinate process steps, such as keeping an eye on it, planning navigation, and managing seafarers.

Risk is assessed in terms of goal proximity. When a process within a step is determined to be at risk, the severity of the risk is the goal proximity of the step with respect to the direct goal to the process, the goal proximity of the step with respect to the dependent goal, and the goal failure. It may be determined entirely by reference to the accumulated costs for and the accumulated costs for actions to improve against goal failure.

Goal proximity helps to assess the cost of a process and the cost of software to manage the process. In addition to the goal proximity of the cause and effect links linked to the likelihood of failure and the cost of failure, or the cost of the process of action for improvement, to the benefits of succeeding the influencing process. The goal proximity of the linked cause-effect link is a quantitative indicator of risk or opportunity. And this means that processes designed to manage risk or take advantage of opportunities have costs to the company. This also means that it is worthwhile to sell overlay software that manages information related to risk mitigation or the use of opportunities. Overlays assess the value of processes or their nodes and build the right indicators for assessing the value of software that assists in managing processes by mitigating risks and managing opportunities.

The risk or potential opportunity is presumed to be more qualitatively determined by the availability of relevant experience within the process that will be affected by the problem, as determined by the goal proximity of the dependent process. May be done. In addition, impacts, risks, and opportunities can be quantitatively assessed by integrating goal proximity with the percentage of failures and opportunities in subordinate processes.

Connected process

It should be noted that nodes that represent risks, causes, effects, and improvements help connect processes. A simple example of this is shown in FIG.

Opportunity or unexpected event 80 has associated risks, causes, consequences, and improvements (reliefs), as described in some content or represented by some data patterns. In general, no risk, cause, effect or improvement will be found in one process. The process 81 associated with the goal set 82 is different from the processes 801, 802 associated with the goal set 83 and the lower goal sets 811, 812. All of these processes have nodes associated with the problem / opportunity / event 80. In the example shown, node 85 represents a process step within process 81 at risk. Node 86 of the step in process 801 indicates the cause of the problem / opportunity / event. However, node 87 shows the node result of the step in process 802. Node 88 in the other steps of process 801 represents an improvement.

Unique issues and implications

As mentioned above, a comprehensive process is a process in a field that is less specific to the context. Comprehensive processes include less specific and more generalized nodes as they reach higher levels of abstraction.

Comprehensive processes can be abstracted into multiple types. One type of comprehensive process may be associated with a field-level process and will be recognized by experienced practitioners in similar fields. For example, traveling far by vehicle is a different kind of comprehensive process than personnel management. At various levels of abstraction, experienced practitioners consider that a particular problem or opportunity is repeated in a variety of related processes. Such problems / opportunities are referred to as unique. Unique problems / opportunities are associated with goals, because problems and opportunities cannot be defined without setting the first goal.

Comprehensive process types are defined by unique problem / opportunity combinations. For example, in the field of human resources management, going back in time, there are many unique issues and opportunities related to human resources. And the entire field of process has grown to address those issues and opportunities. In addition, high levels of inclusiveness processes are defined by their unique nodes. Also, in overlays, generalized nodes and / or comprehensive processes, including further generalizations, are grouped by unique problems or opportunities. This is done when processes become very common, these process steps also become common, and the whole process is defined without reference to specific problems or opportunities (often referred to as themes). Because it becomes difficult. Overlays define a comprehensive process by a combination of abstracted and unique problems or opportunities associated with the comprehensive process.

In assessing process similarity, additional similarity criteria are one or more unique problems found in a comprehensive process or comprehensive process step. If two clearly different process steps with very high similarity are adversely affected by an expected problem or opportunity of the same abstracted nature, then the two clearly different process steps are It turns out that it should be similar.

A high level of unique problem or opportunity (theme) is highly specific to the field and helps to organize a low level of unique problem, followed by an unlimited number of fields and an unlimited number of unique problems. Useful for organizing multiple levels. Also, a unique problem or opportunity (theme) helps to organize a high level of generalized process, followed by a large number of comprehensive processes that are highly disciplined and low level unlimited. Useful for organizing.

The words used to describe a comprehensive process are often simplified for a set of goals and are often associated with unique problems that are too long to be expressed in natural language. Thus, at various levels of abstraction, a group of unique problems can have names associated with a comprehensive process at various levels of abstraction.

Objects and context

With reference to FIG. 6B, as described above, objects and contexts change the effect of nodes on process completion and goal achievement. Nodes may have more or less influence on a process and the goals of that process as a result of differences in context or objects. In some cases, a process node is different when the process is very discipline-specific and has very specific contexts and unique objects. The context and objects are subsequently influenced by the actor and the attributes of that actor (or the company, or the department and attributes of the company). So, in general, different objects or contexts will cause different actors to have different effects on the same process. The context or object itself may provide more or less potential to influence one or more process goals, or one or more dependent process goals.

Changes in objects and contexts affect both process and goal proximity. Goal proximity varies with the process. However, if the processes are very similar, they will have objects and contexts that may differ in different disciplines. Therefore, to facilitate the adoption of overlays across disciplines, overlays incorporate the relationship between the object context and its process, depending on the discipline. Therefore, in new areas, the system highlights different objects and contexts, and re-evaluates the goal proximity to each process step, especially when each process step is affected by the differences in the objects or contexts. You may request that. Overlays may also include contexts and relationships with objects and actors, users, and other elements of the cognitive structure to facilitate cross-disciplinary adoption.

Objects and contexts can be generalized or subdivided into components and can have relationships between them. Objects and contexts associated with an enterprise have generalized representations and components, along with their relationships, which vary depending on the goals achieved by the objects and contexts and the associated processes or plans.

The extent to which a system requires all or part of its attributes to be dynamically related to each other depends on the experience and requirements of each discipline and the client application of the system. If all attributes are not dynamically active, the dynamic interrelationships of the attributes with entities that would normally affect them are kept constant in the default state. For example, when actor attributes are considered average for convenience, the effect of actor attributes on the likelihood of problems and opportunities occurring within a process step is unbiased. In another example, if the redundancy of the resources used in a process step is average, then the proximity of the process step that affects the goal is average. When a process expert considers a process to be average in the field, the effect of the attributes is average.

Objects and / or contexts, along with time specifications for concurrency events, help determine if two events of a similar event are actually the same event. This is important when the goal of searching for relevant information is to discover content and data that coincides with the event.

Goal hierarchy and goal competition

In any environment, it is required to investigate the hierarchy of goals and the competition for goals among the goals in the process in order to determine which subprocess steps are more important. The more consistently the process is applied, the more consistent the hierarchy of goals is, and more attention is paid to the design of the process to avoid problems due to goal conflicts. Goal hierarchies and goal conflicts need to be reestablished as the process changes and becomes like the process steps of a new process and the planning of actions with a new goal structure. In addition, new process steps need to be applied to mitigate the negative impact of poor results and the negative impact of goal competition as a result of poorly maintained goal hierarchies.

Overlay relevance model: goals, processes, nodes

It is beneficial, but not essential, to have a consistent relationship between goals, processes, and nodes (hereinafter referred to as the relevance convention). To the user of the overlay, if the relationships between goals, processes, and nodes appear to be consistent, but do not follow convention, the consequences of the relevance (that is, the empirical events that the relevance engine outputs). May remain fully satisfactory. This is because, in general, current conventions do not group goals, processes, or nodes by any consistent convention. The relevance practices used with respect to the embodiments of the present disclosure are detailed below.

Node attributes

Nodes may be used to draw similarities between processes and between events of experience, as node attributes help define nodes. Usually this is only done by an expert user of the system. Node attributes may be grouped as follows.

(1) Goals and Actors: There are goal conflicts between processes designed to overcome goal conflicts and between actors behind the processes. For example: Legal contracts are designed as a process for consensus on how conflicts are avoided or arbitrated. Machine design is the process of overcoming the competition between the benefits and costs of machine products. Taximeters automate the process of overcoming competition between the taxi service industry and customers in terms of price.

There is a goal conflict between the goals of different actors and / or between the main goal and the conditional goal. There may be additional types of goal competition between goals and obstacles in the environment, while the assets available in the environment help achieve the goals. Assets and obstacles are context-specific and are influenced by specific goal competition. For example, competition between quality and cost affects the quality and efficiency of manufactured products. Each product has certain assets and obstacles that are affected by this goal competition. The customary goal competition between quality and cost in the manufacture of manufacturing processes and mechanical mechanisms, as determined by the product, has associated nodes. The node most closely associated with this goal conflict is the node responsible for any product failure. Therefore, goal contention is closely related to the nodes in the causative process.

(2) Assets and failures: Assets and failures are elements that are most specific to the context and process associated with each node. They are elements within the process that change according to the context, and when grouped by generalizing the relevant context, they are generalized to more comprehensive assets and obstacles. Again, referring to the example of manufactured products and the example of the essential goal competition between quality and cost, in the same context (eg, controlled oil pumps), into a group of similar products with common design. Will have similar problems characterized by the assets and obstacles affected. In addition, there will be assets and obstacles associated with different problem nodes between products due to design diversity across products within the same context group. In this case, the structure of the context needs to separate the product into individual specific problems and additional individual products with associated assets and disabilities. This means that nodes grouped in this very specific context will not be generalized between different contexts. However, all nodes will be grouped under a goal competition between quality and cost. Therefore, a group of contexts manages assets and failures that are active at the node of active problem or opportunity. Some contexts are more easily generalized with more comprehensive nodes. Some contexts remain specialized in very specific contexts.

The association between assets and failures for a node is managed by a context structure. Nodes identify assets that face obstacles that can cause problems and opportunities within the process. If the problem and opportunity are active when the node replaces the goal of the process with the asset and failure of the context in which the process occurs and is not the result of a goal conflict between actors, the relevant asset and failure Active.

(3) Cause node and affected node: The cause node has a node that is affected, and describes why a predetermined node is active as a problem, opportunity, or event. Nodes that can be active in the causative process, as well as nodes that can be active in the affected process, are used to identify node attributes.

(4) Relationship between goal conflict and causative node: Affected node attributes are similar to groups without knowledge of the specified field, in a state where they may change more and may not be so easy. Nodes with the abstracted attributes of will cause goal contention that belongs to the same abstracted group. The cause-effect relationship between the causative node and the affected node helps to associate the node from one context-specific area to the other.

Expert user process

When an overlay expert user becomes accustomed to the cognitive structure of the system, the overlay expert user assigns node attributes at various levels specific to the context of the abstraction. The overlay expert user then assigns node attributes to a higher level of abstraction. Computerized methods may also be used for model node attributes to assist expert users.

Node identification

In the following procedure (shown in FIG. 9), expert user 920 may proceed to the next step in accordance with the present disclosure to identify nodes at various levels of abstraction.
(1) Identifying a node: An overlay expert user identifies a node found in a context-specific process for which similarity to other processes is sought (step 921). ;
(2) Identify the context associated with each node at various levels of abstraction (step 922). This is achieved through a field (context-specific) process model that specializes in the enterprise in which the process in question and the processes that depend on it are analyzed for context specificity.
(3) Identify node attributes with a lower context level (step 923). : Overlay expert users identify node attributes as node attributes 930, as described above: attribute 931 is context-specific process goals and conditional goals; goal conflicts; context-specific assets and obstacles; Includes context-specific causes and effects of nodes in a process (where similarities are sought between the process and other processes).
(4) Select from a set of abstracted, lower context level node attributes (step 924). That is, at the stage of context abstraction in steps 1 to 3 above, a selection is made from a set of node attributes that have been established in advance. The overlay system 940 presents the user with a higher level of selection of node attributes. The expert user selects a higher level attribute to match the attributes of the lower level node identified in step 3.
(5) Select a set of node attributes with a higher or highest level of context (step 925). : Overlay displays a selection of higher or highest context level enterprise node attributes. The expert user selects the highest level of attributes that match the attributes identified in step 3.

The above sequence of steps can be applied to the selection of nodes so that process similarities can be identified. Alternatively, the series of steps described above can be applied to a node so that node similarity can be identified.

Process and node relationships

Process similarity is identified by comparing the higher level of abstraction node attributes with the context-specific process node attributes. For example, in military training exercises, context-specific processes, such as seeing an object, cannot be seen due to a node (eg, a physical obstacle, poor lighting environment, etc.). It cannot be seen because the scope is dysfunctional, etc.). Subsequently, these are due to higher level of abstraction nodes (eg, not visible due to obstacles, invisible due to the environment, no device to improve vision) by overlay expert users. In addition, it is abstracted into something that cannot be seen. The newly abstracted cluster of nodes spawns a higher level of inclusive process, which is a unique process abstraction when looking at the object.

However, in order to match a higher level of inclusive process to a lower level of context-specific process through node attributes, the opposite of the abstraction may be done, which is more inclusive. Nodes and their attributes may be selected, and processing may be performed in the reverse order by collating them with context-specific nodes in other fields. In this way, two processes in different or similar fields, albeit in different contexts, can be collated against similarity. This similarity, in turn, provides the ability to use experience in context-specific areas to anticipate problems and opportunities in other context-specific areas.

Identification of similar processes

In the following procedure (shown in FIG. 10), an expert user may proceed to the next step to identify a process in another field that is similar to the original process 1070 and is context specific.

(1) According to this procedure, the comprehensive process is first identified as follows: : A context-specific process within an enterprise has that context structure. Context structures are identified and collated against new areas of the process being compared (step 1071). This means that the abstract representation of the selected context will be collated between as many disciplines as the estimated number that should work in the overlay system. The context-specific nodes are then identified at the level most specific to the context (step 1072). These context-specific nodes have been assigned node attribute 1082 by overlay expert users using the specific methods shown above. The node and the node attributes are abstracted to a higher context level by the overlay expert user (step 1073) to obtain a new abstracted node cluster (step 1074). The new node cluster spawns a higher comprehensive process, which is an abstraction of the original context-specific process (step 1075).

The process with the most original nodes abstracted into a higher context is the highest level of comprehensive process associated with the original process. Comprehensive processes are iteratively identified (steps 1076, 1075). A) The identification process is performed by an expert user naming the process and assigning the process to a comprehensive set of processes. B) Also, to ensure that the process is unique, and to ensure that the process is not in a comprehensive set of processes in advance by having the same node and the same node attributes, an expert. The identification process is performed by the user collating the node and the node attribute by the above method. C) The expert user subdivides the expected comprehensive process into comprehensive process steps, applies the above process for matching node attributes in these smaller component steps, and from that component step. , The above identification process may be performed by summarizing into a larger and more comprehensive process. However, grouping from small component steps into a large, comprehensive process limits the level of generality of the process, as it would require the same component steps. If the steps cannot be easily changed in mechanical function and in other more fixed processes, a method of assessing the generality of the steps of smaller components is more preferred. For planning where the process steps have not yet been defined, it is more preferable to start with a more complex process with many component nodes.

That is, the level of process subdivision (where the above method of abstracting node attributes to higher process levels applies) depends on what the expert user chooses or what is of interest. May change. If the method is applied to lower level process steps (subdivided process steps) within a larger process, by collating the goal proximity with the number of lower processes. Process similarity is directed towards higher levels of process. If the applied method is applied to a higher level process (coarse process), the process similarity is expressed at a higher level without emphasizing the similarity of the lower steps. Each method has different advantages. The coarser method is different, but in comparing processes with similar goals, so that the method of subdivision is a better way to compare processes with similar steps and goals. It would be the best way.

(2) Discover similar processes in many different areas that are unique to the context. : After identifying the highest level of comprehensive process (step 1077), the expert user proceeds to discover more context-specific processes that are abstractions. In general, high-level processes will be inclusive for context-specific processes within different disciplines 1081.

To test which context-specific process fits best, discover which context-specific process contains the most nodes with a set of node attributes that are closest to the comprehensive process node's attributes ( Step 1078). This is achieved by starting at the highest level and comparing node attributes at various levels of abstraction.

(3) Goal proximity is applied to compare the importance of common processes within each field (step 1079). This step is more important than subsequent steps in cases where the impact of the process on the goals for which it is useful reveals more importance or similarity criteria. If the original process is run in a different context, this similarity tests whether the new context-specific process has similar goal proximity to the main and conditional goals. This includes dependent processes that are potentially affected by nodes that share a common abstraction between the context-specific processes being compared. If the importance of the processes needs to be similar between the processes being compared, this is done before assessing the context similarity.

(4) A node attribute test (step 1080) is applied to discover the context / object cluster that is most susceptible to the selected node. This step requires knowledge of the capabilities of such contexts and objects related to multiple disciplines (usually very similar disciplines) in order to determine their susceptibility to selected nodes. .. If context-specific obstacles and assets are more important as relevant focus, and if the context-related similarities of multiple nodes in a particular case are more important than process similarities. This step is more important than the preceding step. That is, node selection is a narrow selection that does not completely fill a wide range of process nodes, but is a grouping of more processes and contexts that have nodes of common interest. Is also good. For example, many machine failures have case nodes that apply to a particular machine, with design, manufacturing, and operational standards that are susceptible to the same failure. In order to discover these other machines, it is necessary that few nodes are selected within the comprehensive process selected, and expert users are aware of the other machines and are influenced by them. Node attributes must be matched based on ease.

In practice, it should be noted that discovering a similar single node related to multiple contexts / multiple disciplines is just as important as discovering a cluster of similar nodes. In one form, this issue may be addressed by identifying a first context and a second context for the node. The node is specific to the first context. Therefore, the node is characterized as a first context-specific node. The second context is a higher level of abstraction than the first context. Therefore, the node is not specific to the second context. Then there will be two sets of node attributes associated with the node according to the first context and the second context respectively. Then, at least one comprehensive node may be identified in a situation where the comprehensive node has attributes according to the high context level corporate node attributes.

Establishing the system in multiple events

FIG. 11 illustrates a procedure 1180 for establishing multiple events in a system (results that facilitate problem solving by allowing the collection of corporate experience, or opportunities with overlays. Is the result of using. The user establishes the system by inputting processes, nodes, goals, and goal proximity (step 1181). These may be entered using the experience of an industrial practitioner. Event 1186 is entered into Index Story 1185, detailed by experts and / or recorded by the company, with the help of Index Engine 1187. Nodes are the problems and opportunities identified in the discussion of causes, consequences, improvements, and explanations found in an event (a detailed story). In this case, it is assumed that the context-specific process, context, goal, cause, effect, and goal proximity are established.

Process abstraction: Similarities between contexts

In the second stage of establishing the system, overlay expert users can generalize the process and node to allow non-expert users to discover similar processes related to multiple disciplines and multiple contexts. Apply the generalization (step 1182). Experts who use indexing assistance from overlays may match nodes via node attributes to infer process generality and process similarity (step 1183).

Overlay method steps

FIG. 12 provides how the overlay system discovers problems within the enterprise and provides user-related past experience, that is, lessons learned (also called stories) from past risks, causes, consequences, and improvements. It is a flowchart which illustrates the method.

The method performed by overlays is related to building a framework of corporate importance. Corporate goals (as mentioned above, corporate goals and main goals) are established in step 901. Various processes designed to achieve these goals are established in step 902. The process impact (goal proximity) is established in step 903. In step 904, process-related problems, opportunities, and events are identified. In process 905, a framework of corporate key points is constructed according to the process description; problems; opportunities; events affecting the process; causes, effects, risks, and improvements; the way the processes influence each other.

It should be noted that building a framework involves identifying similar processes. As mentioned above, this involves identifying common process steps and / or applying other criteria to various processes.

Processes are analyzed to identify process generalizations and, as a result, comprehensive processes (step 906). In step 907, the inclusive node and the unique theme are identified from the process. Company internal content and company data are scanned, and the scanned content is indexed for company importance using an index engine (step 908). The system determines the impact of a given problem in a given process and sends a description of the problem to the user who is most interested in the problem (steps 909-910). The system focuses on the user's cooperation in the problem, the cause of the problem, and the important matters affected by the improvement of the problem, and proceeds to coordinate the structure according to the framework of the important point (step 911). The system searches the indexed information for related past experiences and outputs to the user the relevant stories of them (problems, problem causes, problem improvements) (step 912).

Solving problems with overlays

A method of solving a problem (or taking an opportunity, making a decision, answering a question) from the user's point of view using an overlay is illustrated in the connected flowcharts shown in FIGS. 13A and 13B.

It should be noted that the methods described in this disclosure are repetitive, and the order of the steps depends on how similar the problem or opportunity of interest is to past problems or opportunities. It should be noted that the order of the steps depends on how well the problem and opportunity of interest are managed in a known process. If the process or opportunity is not well known and a process that can be improved is not sufficiently established, the order of steps and emphasis will differ from that described in this disclosure.

A user dealing with a problem (opportunity, decision, or question) 1001 first outlines a tentative plan in his or her own mind regarding the problem to be solved (step 1010). The tentative plan is devised outside the system. In the corresponding system action (step 1020), the user is allowed to select several comprehensive processes organized by the plan. These processes are output in a variety of ways by including a combination of search for minor words searched by a preset search in a comprehensive process or goal. That is, this is to provide a search for the basic concepts of cognitive structures. In most cases, process selection within a narrow range is more process-specific than process selection, which is the search result for goals, and narrower than process selection, which is the search result for comprehensive processes. Yes, it is a search result of a unique process, which is a wide range compared to the process selection.

In step 1011 the user selects a narrow range of process combinations, selects goals corresponding to the processes output by the system, and the system generates a hierarchy of initial states of goals (step 1021). The goal hierarchy is modified to take into account how the actor performing the process and the goals of the process affect the hierarchy, and how the selected goals compete with each other (step 1012). System action in step 1022). The fewer processes selected (and how well known the problems and opportunities are, how well established they are, how well known the process of action for improvement is, and how well established they are. Within the selected process (depending on), the goal contention and hierarchy will be the same.

In step 1013, the user searches for a unique node from the selected process (ie, within the outlined plan, the selected process). The corresponding system action (step 1023) is to search for a process that is unique to a set of processes. The user highlights the relevant processes using the unique process. The system selects more processes that are known to be associated with the identified unique node (steps 1014-1024). The user then selects selected stories and opportunities organized by process issues / opportunities and unique issues / opportunities. Stories are searched by discovering process-related groups according to node commonality and process-related goal proximity (steps 1015-1025).

The system results when the user collects past experience and recalls the user's own experience through stories (content and data related to problems, opportunities, and interests / unexpected events). Helps the user readjust the goal and goal hierarchy and highlight the goal conflict so that the goal hierarchy and the process that best fits the goal conflict can be found (steps 1016, 1026).

Using the output story, the user creates and tests a tentative solution (step 1017). The user then selects a further process, modifies the outlined plan, and tests the modified plan (steps 1018, 1019). In common review documents managed by overlays, the plan does not need to be retained in the system except as described in the review with colleagues. If it is advantageous to retain the plan, the plan may be retained. For example, if the experience is considered to be useful for reference in the future, especially if the plan has a better hierarchy of goals than the standard process being replaced in an environment. In some cases, the plan may be retained. The searched stories help users gather the experience of practitioners to come up with the most feasible plans. Overlays help you find past experiences through stories and help the right stakeholders work together when considering them.

Overlay system

The system that performs the overlay includes an index structure (or index engine) that defines how to achieve relationships between nodes or between corporate critical points. The index structure includes word patterns and data patterns, including business objects related to nodes or corporate importance. The system also includes a linguistic parser and scanner used to scan existing or new content and to assign that content to process nodes. Overlay indexing helps users discover information related to corporate importance more effectively than using conventional search engines.

It should be noted that the relevance of content within an enterprise is determined exclusively by addressing process nodes. The user defines a recognition structure to perform indexing. Essential criteria for relevance are defined within the recognition index structure.

The implementation of overlays according to this embodiment is systematically shown in FIG. The overlay includes a content scanner 1101 for scanning external relations data including corporate content, corporate data, and business objects, a language parser 1120, and an index engine 1150. The scanner acquires content from various sources, such as application data including e-mail 1102, document 1103, business object 1104, and web content 1105. The language parser 1120 works with the index engine 1150 to identify concepts within the scanned content 1110 and assign important points associated with those concepts. In the case of application data, the relevance of important points is preset, so the overlay searches for specific data at a specific location within the application. The important point index 1160 output supports the range of user interface 1170. The user interface utilizes a key point index to alert users to problems, allows users to collaborate with each other, and limits the information passed to the process for interested users (if now). By the way, it searches for relevant past experiences (even if the information is only directly related to a subordinate process for non-stakeholder users). In the embodiments shown, the user interface is a web-based search interface 1171, a web-based collaboration tool 1172, a portal-based interface 1173 for application integration, and a portable device for warnings, cooperation, and searches related to problems. Interface 1174, and interface 1175 for integrating the key point index into one or more desirable office applications.

The index engine uses index model 1130 to index information about corporate importance. The index model is constructed using a history of events (a story of how a company has dealt with important points in the past) 1106 and current problem-solving events 1107 within a company. Therefore, both current and past events are used to establish the system. By analyzing the current events, the events for the cognitive structure are indexed. If the isolated process is not directly part of the solution to the company's problem, past events are entered as experience.

Moreover, when establishing the system, the index engine references the context to each other. This is because by using a comprehensive view of the process from a previously established field, and a comprehensive node, the system is settled in a new field, with experience and content-related word concepts. Can be done. Context-specific nodes define more comprehensive nodes. These more comprehensive nodes then define a comprehensive process component specific to the content / field. These inclusive process components, and their inclusive nodes, will exist at several levels of generality in the new field, and as a result, nodes that are specific to this different context / field. Will show.

Index to other software products, including content management systems, search solution products, third-party products such as enterprise resource planning (ERP) systems, or to other systems that may benefit from the addition of critical point-related software. The index engine may provide the service to be granted.

In one form, the index engine 1150 is a middleware service provided via a web service.

The system according to the present disclosure may be used for the following.
Identify content related to a node;
Understand the enterprise by associating nodes with each other in the cognitive structure;
Solving problems within the enterprise;
Discover information that goes beyond your company.

Some of the advantages of using an overlay system are:
Evaluate the process similarity between the two processes being compared;
Explain processes and plans related to the enterprise;
Discover relevant information about problems and opportunities;
Find out-of-the-box information (unresolved notifications) about problems and opportunities;
Assess the risks and consequences of problems and opportunities;
Anticipate problems and opportunities;
Diagnose problems and opportunities;
Apply action plans for improvement on problems and opportunities;
Make strategic plans for problems and opportunities;
Give users insight into causes and consequences in the industry;
Allow users to be creative in dealing with problems and opportunities;
Helping users in explaining complex phenomena related to a company's business, or in explaining the environment in which a company operates and has a significant impact on the company;
Helping experts to help the company in solving problems or taking advantage of opportunities for the company;
Discover the relationships between the elements of the cognitive structure based on corporate activity.

For example, on one floor of a factory, the users of the system typically have defined functions, and individual and comprehensive goals for delivering products to customers, managers, sellers, assistant management ,. Engineers and maintenance personnel will be included. Many of these users access the corporate model through mobile devices such as mobile phones, tablets, or other personal electric devices (PEDs). Often, these mobile devices have a user interface (display screen, including a touch screen) with a limited area. Assuming that the complete node structure of the enterprise is displayed on the display screen, the nodes may be too small for the user to see or access by touching the node of interest to the user. .. Therefore, the system is designed to illustrate only the nodes of interest to individual users, and optionally some additional nodes on one side of the nodes of interest. As the goals of a particular user change, so does the node of interest illustrated on the user's display screen.

With reference to FIG. 16, system 1200 includes a function 1202 that coordinates a plurality of user interfaces 1204a-1204e to reflect the associated current state of each user in a live event. This means that among the nodes screened by the context that associates the user with the user's current state, only the portion of the pair of nodes 1206 associated with each other is presented to each user. Each user interface 1204a-1204e has a display 1208a-1208e with a limited display area. If all nodes 1206 were displayed in the restricted display area 1208a-1208e, the displayed nodes would be too small to be displayed or interacted with by the user. Also, the current state of the user may change, and the system 1200 may be required to change the display of the user interface 1204 so that the display space for information related to the current latest state is large. .. However, all nodes 1206 are related by cause, effect, and similarity, so if a user is required to view any node assigned to a stakeholder, the user reverses the above. You may process the procedure.

Facility 1202 adjusts the user interface to be focused on the nodes that are most relevant to the user / stakeholder, and the user / stakeholder depends on the progress of the situation related to the user / stakeholder. You may change the combination of nodes that are most relevant to the stakeholders. The system may modify the display of user interfaces 1024a-1024e so that the display space for up-to-date information related to the user / stakeholder is increased. However, at the user's discretion, all nodes associated with the user are accessible, regardless of the current focus content shown on the screen.

Function 1202 is accessible through node 1206 to ensure that the information held internally is current, and to ensure that each user's situation is current. Communicate with many external devices. The first external device may be a keyboard 1210. The second external device is a remote sensor, such as a temperature detector or photodetector, to recognize a fire detector, or a humidity detector, to recognize a pipe leak or pipe rupture. It may be 1212. Further, the function 1202 may remain connected to the remote site 1214 via the Internet 1216. Such remote sites include other departments of the enterprise, external databases (eg, administrative sites for building plans or accessing routing diagrams), public databases (eg, search engines), and private. It may include, but is not limited to, a database (eg, a wiring diagram for a component of the device available to the builder or manufacturer, or for a ship).

Function 1202 is a non-transient digital storage medium and a computer-readable medium capable of executing instructions encoded in a digital storage medium that stores corporate models, corporate content, and corporate data. Includes computing device 1218 with. Here, the process associated with the model includes a computer-readable description of the nodes, the relationships between the nodes, and the computer-readable description of the content and data and the relationships between the different nodes.

Function 1202 can communicate with each user via the transmission device 1220. The transmission device transmits information to each user and receives information from the user through the user interface 1204a-1204e. Any communication format, such as mobile phone network 1222, wireless local network, or Internet 1216 may be used. It is useful to instantiate node 1206 not only from changes in the information underlying the database, but also through the user's direct input to user interfaces 1204a-1204e controlled by overlays. This is treated as information in the database or in other computerized functions that should be processed by scanners etc., but that information will be entered via a user interface controlled by overlays. .. This information may be a simple selection of node 1206 formed by the user interface, or a choice of user instantiation actions related to node 1206 and / or content entered by the user. Information such as images and videos becomes available by or through function 1202 displayed on the display 1208a-1208e of the mobile device. User instantiation actions are input to function 1202 by the user via transmission functions 1220, 1216, and computing device 2018.

The user interface 1204, the structure of the interrelationship nodes 1206, and the data in the database 1224 exist as middleware services. This middleware service allows logic / code modifications, database 1224 modifications, and node 1206 modifications without requiring any programmatic changes to user interface 1204.

Overlays incorporate a combination of interrelated nodes that are connected by cause, effect, and similarity. In addition, the cause and effect can be determined by a formula and by the relationship between the characteristics related to the node. In idiomatic programming, changes are made to relationships and to data that represent problems and opportunities. After these changes have been made, new user interfaces will need to be designed to present these new relationships to the user. This embodiment avoids performing the second programming.

A coded relationship 1226 between nodes 1206 can be clarified. Then, if you draw the cause and effect, and the effect and what is derived from the cause, by programming the code / logic that changes within the node and within the formulas to which they connect, all nodes When connected to another node, the code / logic is programmed without changing the relationships of the information given in the user interface in another example. The system 1200 builds the database 1224. In the database 1224, each increment of data relates to at least node 1206, and the relationship from one node 1206 to another node 1206'is described by code / logic relating from one node to another. Will be done. The nodes are related to each other by the code / logic of the application, which draws the cause and effect, and what is derived from the cause and effect. On the user interface 1204 of display 1208 in a limited display area, data from database 1224 associated with each node 1206, 1206', organized for nodes directly linked to each other, is displayed. These nodes relate to each other by cause and effect, and by what derives from cause and effect.

The user interface is a set that is not designed as a program for the current use case. The prior art user interface is designed to fit a fixed given use case. For example, there may be a user interface that determines the route to an exit within a building where a fire broke out, by providing a default choice of navigation options. Different user interfaces will be needed for escape from the building and for emergencies such as broken legs that are inherent in the escape. A different user interface will be needed for the coordinator who oversees the evacuees' position status. The overlay user interface fits all use cases, including unexpected future use cases. This is because the overlay user interface contains system logic and is derived from a continuous node structure that contains future logic. In addition, there are two variables to describe because the logic of the system and the state of each attribute of the system is drawn by the cause-effect link between the node and each node of the node. It is a link between a node and another node. It can be drawn graphically within a topographic map similar to a vector map. However, having only two variables, a node with links to other nodes and the ability to expand or collapse child nodes from the parent node, allows for this topographical drawing and increases or decreases the number of nodes. That is, zooming out to understand the situation and zooming in to focus on a particular node and related information are displayed on the user interface to which the user is associated. Currently, a group of processes, whether or not the processes are sequential, and how much they relate to each other, and how many processes are drawn. There is no user interface to draw at this time. That is, you can navigate from a choice of thousands of nodes to focus on one of the lowest lower nodes, and make any choice between these external nodes. There is currently no graphical user interface that can be navigated from and so with continuous drawing.

The display that the user wants to see in zoom-in mode may be the display of the attributes of the node and the link (view) rather than the node and the link between the nodes, but these attributes are the node in focus. And by links, it is on the basis of being dynamically generated. Programmatically, the displayed attributes are not generated. Node attributes are dynamically generated in the detailed interface.

This is in contrast to prior art enterprise process rendering user interface software, which requires each user interface to be refined or pre-determined and programmatically generated. One example of an existing continuous drawing software system that does not draw an enterprise process is an electronic map. The electronic map can be expanded or contracted by zooming in and out. However, this method does not have the ability to present the process. This is because in electronic maps, display is not used to depict processes and relationships between processes, but is used to depict positions and distances in two dimensions. .. On the other hand, in overlays, the empty space is used to draw the cause-effect link and process. That is, nodes draw problems and opportunities, links draw the causes and consequences of linking nodes, and vacant parts are used to indicate subordination or subordination. A striking feature that achieves this is that processes and typical nodes converge. That is, the child nodes are collapsed to the parent node, so that when zoomed out, the child nodes fit together. Flowcharts and similar process block diagrams are used to depict processes from small to large enterprise systems. However, the flow charts depict sequential processes and branches that do not fit together so that they can be zoomed out.

Process sequences are often too small to define all process relationships in a practical way. For example, in a sequential step, how can we define how audit failure affects a company's reputation? And at that time, is the sequence important, or is the cause and effect important? How does the misalignment of ball bearings affect the integrity of the machine's structure? How would a flow chart of sequential steps help draw this? A link between two processes that are not linked in the sequence can be connected in the flowchart, but the link no longer draws the process flow and cannot be drawn as a component of the flowchart.

Other complex process drawings may be created in a two-dimensional UI format. However, they involve a clear cause-effect relationship between nodes that are also computer readable and process nodes that also converge. Also, in graphical drawing, they fit together to allow zooming out. Also, when they are required by the scope of the drawing system in which they are designed, they fully depict the relationship between a process problem or opportunity and another process problem or opportunity.

In other words, the complex flowchart of the prior art is not just a process flow, but tries to draw a process relationship, but cannot provide a node that converges. As such, the detailed process can converge to an obvious parent process as well as a computer-readable and, as a result, a complete cause-effect association between the nodes that the computer can handle. Thus, in the user interface, when drawing interrelated enterprise processes, these prior art composite flowcharts show the processes, but not the degree of relevance between the processes that is sufficient to converge. This is because the nodes do not converge and the relevance is often undefined, or in some cases statistically defined by the community to which the user belongs. On the other hand, as described in the present disclosure, in overlays, the causal-effect association is empirically depicted by either the goal proximity or the algorithm if there is a quantitatively obvious association. To. Both the goal proximity and the relevance algorithm that draws the cause and effect are computer readable and can depict the importance of the relationship. Statistically, the rendered relevance is computer readable. However, if the result is an aggregated result of cause and effect dependencies that are not completely independent, the statistical sample will be an aggregated result of results with completely different causes. Therefore, if the cause and effect are ambiguous, or if the statistical sample is inadequate for the important statistically elicited association, the rendered association is , Inevitably not accurate.

For example, a ship collision that has been statistically analyzed and assigned to an artificial factor such as human error is not sufficiently meaningful. Because all the technical perspectives of marine transportation that will cause collisions, such as steering failure, also include anthropogenic factors such as machine design, manufacturing, maintenance and operational complexity. Because it is accompanied. For undefined relationships, or statistically related nodes as shown in the prior art, the user interface will be complicated by the relationships between undefined or statistically derived nodes. For example, in an emergency, the relationship may be confusing and the purpose of the application, which is entirely computerized, for the response in an emergency to provide information related to minimal damage. Would virtually ruin it.

In other prior art methods, commonly referred to as "bowtie" block diagrams, which are graphical two-dimensional drawings used for formal risk assessment, the association between "failure mode or danger" and a process is a node. Draw by connecting the statistical possibilities between and the "severity". However, the elements do not converge because there are "failure mode or danger", and "process", "goal", and their links, as well as "conditions" and many other variables. In overlays, "risk", "danger", "failure", and "result" do not converge, just as process nodes converge. For example, in an emergency, such idiomatic "bowtie" drawing would not show the whole situation. It will represent failed nodes and dangers, but other processes that the user is affected by the dangers drawn on the bowtie block diagram, or other that contributes to the results shown on the bowtie block diagram. What if you wanted to focus on that, or other processes? How are they connected? The bowtie block diagram shows the risk combinations of affected processes and causes and the processes of focus, or those that are logically derived in relation to the risks, only in the best possible conditions. There is no idea of showing how all the processes in a company are connected. Therefore, in an emergency, it is discontinuous if the user needs to view other processes that correspond to stakeholders, or if it helps the system focus on the latest events. You have to do other graphical drawing that is different from the graphical drawing of the past. Therefore, the graphical drawing is discontinuous and cannot be used for zooming in and out (which requires continuity). Subsequently, this means that without pre-designing the user interface for each process, or use case, or user / system interaction point, any process within the system, and any future. It leads to not being able to draw the process of.

Therefore, the prior art system produces a user interface drawing for any process, a group of processes emulated in the system, and any of the current process, group, future process or group.

In part, the above will help explain the following:

Use the key points of overlays to enhance or replace the underlying enterprise application. :

In its role as a source of information for managing event triggers with respect to issues and opportunities and interests or unexpected events, or important monitoring factors lost, and relevant information that enhances user decisions. One way to enhance business understanding is to reduce the time it takes to strengthen the underlying corporate system and sometimes replace it.

The reason for enhancing or replacing these underlying enterprise applications is that these systems are ergonomically immature because they are old and old, so that overlays work efficiently. The reason is that it is rarely updated in time to provide the correct triggers, and relevant information.

Replace these enterprise applications for overlays without much effort in building the application, such as understanding past code, maintaining past code, or improving past code In order to do so, it is necessary to utilize the core innovations of overlays to enhance or replace past systems. That is, this is to facilitate the creation of supplementary enterprise information systems when requested.

The important purpose is not to rely on traditional software development methods, and as a result, business experts, so-called stakeholders and experts in the field, do not demand much traditional application building methods. To be able to build and to be able to add or create supplements to these systems. This increases the likelihood that the resulting system will be beneficial, as well as the speed at which the system will be built to adapt to new and urgent needs.

The system-based overlay behavior is partly driven by node structures and partly by traditional data structures within the underlying enterprise application. Those aspects of the system, operated by the node structure generally involved in the navigation of the system and the relationships between nodes, i.e., the discovery of information of relevance to users within the enterprise, are very flexible. In general, those aspects of the system, which require the creation and interaction of business objects, behaved by traditional code within the underlying application, change the evaluation of the business model, defined by field experts. It remains difficult and expensive to do and cannot be easily expanded. This latter situation means that the overlay system remains immature with respect to the quality and suitability of the underlying past application objectives.

The following sections disclose a form of overlay concept that, by removing the need for traditional code, understands all the behavior of the system, driven by the newly extended node structure. So, conceptually, the business model is the code of the application. This makes it possible to achieve the above-mentioned general purpose in the overlay system.

In the prior art and past systems, the business model may be made to operate by the business model, that is, it may be moved between transaction tasks, it may be accessed through a navigation filter, etc. Works as. In general, these business models represent a package of simple data, i.e., a set of related attributes that model real-world objects or concepts, such as people or documents. It corresponds to these business models currently implemented using traditional code. These business models include attributes as well as relationships with other objects derived from many use cases. It seems to be a home repair tool with accessories to fit many home repair tasks. However, the relationship is on the order of greater order than home repair tools. Then, targeting the diversity of users in the business model, which is almost the same as the diversity when using modern smartphones and modern computers, attributes and relationships with other business objects are described. It is cumbersome and difficult to describe and manage by the designer.

For example, packaging attributes into business objects is a fact that these attributes and their values tend to be determined by the underlying processes, and are commonly used by software engineers during system development. It is subject to rules and restrictions that are unnoticed, spanning (and, in fact, within other companies) between companies.

For example, in a spare purchase order, select a single item.

Part Number: The method by which the part is described is probably determined by the complex process of following the path back to the original manufacturing process.

Required quantity: This can be determined by a complex combination of conditions, including the mechanical condition for the order, upcoming maintenance, time, labor, money and availability of other resources. ..

Date-based requirements: This also relates to resource availability, equipment accessibility, and equipment usage and timing.

Planned Delivery Date: This relates to the availability of the supplier staff, which is related to the personal and professional requirements of the subject staff to prepare the order for delivery.

In short, a simple business object of an item in a purchase order will traditionally get only some of the above. However, mapping the above items to a node structure of complex cause and effect is indispensable for realizing an effective business process support system. This can be easily extended by supporting informative decisions and by extending the node structure.

It is especially important that the issue is when the "ideal" business process does not continue, that is, how exceptions are handled. For example, if the parts are not delivered on time, the next action to be taken is such as the expected reliability of the device, which allows for risk assessment and reduction of selected actions. , You may rely on very complex information.

In addition to this, there are very common scenarios in the implementation of business objects that do not easily meet the demands of different companies. Here, the different companies tend to, in essence, have different interpretations and usage patterns with respect to the business object. In practice, the implementation of a business object encapsulates the business logic, which should be in the model, not in the code. Moreover, in that the business model can control how the business object behaves, the business logic is hardly developed in a manner that can be seen from the business model.

Therefore, the standard idea is to remove the idea of business objects as a fixed concept, not to adopt attributes as a very small primitive concept. In effect, this replaces the notion of a business object based on the node structure of a node, which is interrelated by a clearly described computer-readable cause and effect, or by a derivative or variant of the cause and effect. It is possible to reveal new and highly dynamic types of data display within computer-readable logic, within another transformation logic, and within another user interface logic guaranteed by known prior art systems. Will do.

The idea of this improvement of the further overlay / TA system is a clear combination of process models with data models defined as attributes, as evidenced by the interrelated node structure. This data that has nodes that are connected by cause and effect, that is, data that have nodes that clearly indicate what the data is for and how the data is transformed. Coupling is central to the functionality of the system for important conversion logic that can be read by the host computer, and for important user interface attributes without special programming skills. This is in contrast to traditional data structures such as relational databases. Here, the traditional data structure is one in which the purpose of the data (ie, the goals it supports) is not clearly expressed and in order to elicit a favorable user interface. Refers to those that have not been determined to be required. Traditionally, it is hidden and fixed information as a result of being embedded in the code. In addition, it extends them to enable experts in real-world processes, and computerized transactional processes, to understand all computerized processes within a company's application, and when needed. Information that needs to be revealed in the model to be able to do it.

Unlike other databases, such as structures without SQL nodes, in building or extending enterprise applications, the unique concept of overlays is that all transformation logic is within the cause and effect links between the nodes. Is. And the overlay-specific concept does not require any other logic to influence either application transformations or user interface attributes. There may be logic outside the node structure required for auxiliary services, but outside the node structure, there is no need for corporate business logic or user interface attribute display.

Modern information systems are generally understood as multiple layers, each layer performing a particular type of function and servicing adjacent layers. And the overlay / TA concept is no exception. The next generation overlay / TA concept has three layers, outlined below.

User interface layer. This layer forms the interface presented to the users of the system, and the entire layer is derived from the business model.

Business logic layer, or "middle" layer. This layer defines the representation of how the user and the organization should be supported to the extent required by the user and the organization in order to meet the goals of the user and the organization. It consists of a business model that works in an implementation framework that is an overlay.

Data management layer; This layer facilitates the storage of state information, and this layer is also a layer derived from the business model.
Business logic layer

As mentioned above, this layer consists of two basic elements: the business model and the implementation framework in which the business model is executed. Business models will be created and managed by non-software engineers and will not require knowledge of traditional programming languages and databases. Therefore, the business model will define an important information system, that is, everything that is required to elicit what supports the organization in meeting its objectives. So the important of the difficulties remains too ambiguous to handle with the underlying implementation framework, and too ambiguous to provide predictable, informative and available end results. To support the definition of a model that is easily understandable to non-engineers when it remains.

At the heart of Overlay's business model are nodes. It is a corporate importance when the operator, or sensor or other system agent, needs to determine and provide an input, ie, a change of state. Or, it's a corporate importance when the user needs to be aware of something by the system. At a high level, a collection of these nodes defines an organization's process model, and when the organization's process model is combined with the underlying state model, the users required to support each company's key points. Sufficient information should be provided to elicit the interface. The elements of the process model can be mapped to a higher comprehensive process abstraction within the parent process model (master process model). Now, the applicant describes each component in more detail.
Business logic layer: process model

A process model is defined as a set of interconnected nodes. Each node has a set of attributes that are input to or output from the node. Other types of relationships also exist and are outlined below, but basically nodes relate to other nodes as a cause and effect.

The cause-effect relationship between nodes implies that an action can occur explicitly or implicitly by a user or other agent as part of the cause node as a result of data entry or existence. To do. Here, the causative node is a trigger for a state change and presents the affected node as an "of interest". Therefore, the "code" of the system that is linked to the action and linked to the cause and effect nodes can focus on influencing the state change as a result of calling the action.

A node relates to a set of attributes linked to a node within the node's "node cluster". A node cluster is typically a collection of related nodes that are related to a process and other reasons. Moreover, the node cluster is clearly defined by an expert in the field of creating a model. In each node, it is designated as either an input (read-only) or an output (read-write). A set of attributes for a node is referred to as a "descriptive pattern" for that node.

Basically, a node is stateless in that it consumes or creates a class of attributes. In other words, there is no idea of node instantiation. Instead, the node is of interest as a result of the state of attribute input for that node. For example, the "evaluate parts procurement and transportation options" node is of interest when there is a significant demand from the vessel being executed. This state change is typically the result of a request from the action associated with the causative node.

Nodes also relate to other nodes as belonging to the same area of interest, that is, as a task in organizational task grouping. The organizational relationship does not necessarily imply that it is a member of the same node cluster by direct cause and effect. Rather, the organizational relationships are used to help the user when navigating what can be a complex node structure. For example, an "acquisition" node that organizes many "acquisition" processes has no cause-effect link to the process that the node organizes, or to other processes. This is how such an organizational node is affected by the node that the organizational node organizes, or how the organizational node affects other nodes. Is unclear. So if one asks how "acquisition" fails and when at risk, when to "acquire", the answer is unclear. Similarly, if one asks the question of which process fails when "acquisition" fails, the answer is unclear. However, small nodes in the grouping, such as "ship inventory status" for spare parts, have a very clear effect on being able to perform onboard repairs. So while the nodes organized by those nodes have the usual cause-effect links to other nodes, organized nodes like "acquisition" are for navigation purposes. It is a thing.
Business logic layer: state model

This is where data is stored so that users can share information and that the system can "remember" things between user sessions.

When an attribute is identified as part of the process model, the state model is automatically expanded to easily store the values for that attribute.

The attribute values of the state model may include links to further attribute values within the model via nodes to indicate the relationship. For example, the age and name attributes may be linked to the employee ID attributes to collectively represent the employee. And this may be represented within the node cluster. At the class level, the types of relationships that exist are typically derived from the process model (node cluster) as a result of attributes that are part of the same cluster that serves larger emulated processes or parent nodes. ..

Here, the important mechanism is the context component of the overlay interface. The attribute used for context filtering, that is, system navigation using key identifiers, becomes the "key" attribute. Key attributes are the primary navigation method when many similar processes are distinguished by their cause and effect by key identifier, and when many related but different process steps use the same key identification. To form. For example, if an employee's name is defined as a key attribute, and in a large cluster that identifies one employee, each of the employee's age attributes forms two nodes, then the system is concerned. You will be able to link the name and the age attribute of the employee. To assist with key attributes and system navigation when dealing with details about an employee, with two or more employees and the process steps being the same for all employees. The use of key attributes helps clarify that the focus is on the right employee.

This method of state management represents a major turning point from conventional systems. Here, the idiomatic system is what is necessary to complete the process currently occurring from the data model by removing all the knowledge specific to the field and having the knowledge derived from the process model. In a system that helps us avoid potential transformations, where the assumptions made in the information system design dominate in new designs that affect the capabilities of the system in accurately presenting. is there.
Business logic layer: master process model

A viable node is assumed to instantiate a node class (an abstracted node cluster that draws an abstracted process) defined by the parent process model, and is the node class (abstracted process). Is related to the abstracted node cluster) that draws. As an abstract version of a field-specific node, the node class gets common elements in the field-specific nodes. For example, the node class may cover concepts such as planning, checking, agreeing, warning, and so on. The abstracted node class represents the concept that can be understood by the "cave man" in the first abstraction that we can understand as human beings.

The abstracted node class serves two main purposes. First, when thinking about how to model field-specific events, for example, by reminding business experts what events need to be considered, or by field experts. By helping to understand the work individually, the abstracted node class serves as guidance for experts in the business area. Second, the abstracted node class accelerates the modeling process by facilitating reuse and by allowing similar processes related to models in multiple disciplines to be quickly identified. .. However, reuse does not have to be copy-and-paste of components of comprehensive code, but rather may apply to node classes (abstracted clusters) for all instances / use cases. .. This is because it is not easy in any case to describe an abstraction or class level cluster using a suitable coding language that can be transformed without adopting a field / use case level. However, linking field clusters to node classes (abstracted clusters) is very obvious, and as a result, improving the logic to the field / use case level relative to the cascade class level. To be very clear.
User interface layer

The user interface layer combines the information contained in the business model with the encoded basics of the most practical user interface design in order to present the user with a graphical user interface.

Existing prior art uses business objects as one of the basic concepts with UI. That is, the user creates a business object and outputs the display of the business object in order to display the content and change the content when necessary. In the methods of the present disclosure, overlays understand the fundamental changes in the way the basic interaction UI concept becomes the node itself. The user deploys the node UI to display the requested information in order to execute the process and obtain the information for updating the state model.

Basically, the node UI presents the input and output attributes of the target node and surrounding nodes, that is, the node cluster. The output attribute is read / write (read / write), but the attribute identified as input is read only (read only). Attribute values are grouped where needed and are defined by the process model as described above.

The number of attribute values present defines the format of the display and the availability of supported navigation tools (sort, filter, search). If there is a lot of data, as a result, the UI will be dynamically and properly adopted. The attribute may be highlighted as a key attribute for the node, and the node may influence the way the attribute is presented on the node's display screen.

For nodes with a large number of output attributes, based on the initial key attribute list and attribute set editor, the system may rely on a two-step UI model, but in both cases the UI works. Must be generated. An example of this would be a purchase order. For purchase orders, the first step provides a summary of the relevant key attributes (date, supplier name, order identification, recipient), and the second step is the complete purchase order header, and It will be a more complex UI that procures all items.

Just as determining which attributes are related, the cause-effect relevance between nodes also affects how those attributes are presented. For example, it may be visually emphasized depending on the attributes affected by the association between cause and effect. The relevance is directly related to the node in question, or directly related to the display of the node cluster, which provides a single UI to capture the relevance of multiple causes and effects. is there. The platform builds a UI approach suitable for decisions or decisions or transactions to be made.

Also, if a plurality of attributes are deemed necessary to pass a context to other attributes that are considered to be related by the node structure, the plurality of attributes are determined to be related. For example, if the name of a component of a machine is identified as an input attribute, the system may also be considered to be the name of the relevant ship. These key attributes are used to define the display range within a data structure that is preferred for grid display. In this example, within the process named "data population master setup", the node named after the ship will be followed by a component of the machine as a sister node to the identifying node.
Data management layer

The data management layer is the layer that transforms the state model into the implementation framework provided by the existing database management system within the business model. If necessary, the need for scalability, and the formal correlated database structure, since the underlying scheme will be a metamodel to support the on-the-fly extensibility that is occurring today. The lack of need for data means that the data is likely to survive as a key value pair. This, in turn, naturally leads to the use of NoSQL database systems such as CASSANDRA (The Apache Software Foundation, Los Angeles, CA). This method reduces the possibility that the underlying data management scheme will interfere with system performance.

There are many other types of computational logic that go into information systems beyond simply presenting data and taking input. In the following, we briefly consider how some further calculations are covered.
Create and delete attributes

As mentioned in the description of the state model, the action that leads to the creation of a new attribute will trigger the execution of a constructor function that creates and anchors that attribute and other related attributes. Attribute deletion must be supported as a parameter by a special hard-coded action type that retrieves the attribute from the node UI. You should also be able to define a destructor function that contains logic to check the validity of the deletion.
Event handling

Action code should be able to be defined for system and custom events as well as constructor and destructor events. For example, when the node display screen is opened and displayed, edited, or the like. When a state change occurs, a custom event related to the action code starts. This looks the same as a database trigger, but is represented by a node structure as a reusable abstract process, even at a very detailed level associated with a transaction type process.
Access control and security

In essence, access control is provided as part of the role-node-user-context structure. An additional access control layer should not need to include this structure.
Computer-readable, calculated attributes of cause and effect

This is a core concept that provides users with computational support. The fields to be calculated are defined as the product of a script, which includes, but is not limited to, program structures such as mathematical operators, logical operators, condition / selection loops, and the like. Typically, the calculated fields are updated as a result of the action of transitioning from the causative node to the affected node.
System integration

The node structure concept that is at the heart of the overlay model stems from both the standpoint of integrating different types of information systems (in terms of integrating processes (or users), and in terms of simpler data integration. It is to provide a useful framework for the event of integration). In the following description, we will focus on each of these.

Process integration is understood as the transition of information between processes. The process is not emulated by the same system, but it is desirable that the process should be integrated in order for the process to run efficiently. When both systems to be integrated represent conflicts in the representation of the same underlying entity, that is, both systems do not provide the same business object implementation, and neither system has the attributes of the business object. The problems associated with this type of integration are the most difficult when it is not the preferred representation of all scenarios related to. Attribute matching is possible by subdividing business objects into their underlying attributes, assigning nodes to them, and applying logic to the relationships between the nodes. This is because the attribute is assigned to the nodes that draw the same business logic in both systems, which is appropriate for integration.

The process integration methodology may look similar to the following method, in which idiomatic code that uses business model objects is transformed into code hosted in an overlay node model structure. :
Map the state model to the state model of the two systems to be integrated.
Abstract the problems and solutions provided by each application to be integrated.
Create a cluster of abstracted nodes that contains the processes to be integrated.
In each application that should be integrated, connect the abstracted nodes to the attributes.
If done correctly, the two sets of attributes (ie, the abstracted set and the set from the application) will be the same. That is, for each node in each field, a prediction pattern is created, data is placed in the above table, and the node is connected to the abstracted node.
Ultimately, the data in the expected pattern will be equivalent, although the table relationships and groupings will be different for each of the two applications to be integrated. Therefore, any relationship-based goal implemented by the application is replaced by the node structure.
The prediction pattern accurately extracts collation data from each database. This is because the nodes describe exactly the same data, and each database provides different relationships.

As an actor who "executes" a node for the simpler tasks of data integration, the applicant looks to an external system. As a result, as part of the node structure, we define the data transformations required to pass the data out and to accept (and process) the data. That is, you can see an external data system that wants data in a certain (specific) way, exactly as people do. Of course, the durability of a system tends to be low when it comes to accepting inputs that do not follow the exact rules for the capabilities of the system (there is no reason why it cannot be entered). However, it will be required to build some platform elements to support different service types, platforms, etc. becoming security-aware, which is done completely comprehensively. ..

With reference to FIG. 15, the above contents may be illustrated. In emergencies requiring evacuation and school blockades at schools, the common goal of 1500 is for 100% of students to evacuate and 100% of the doors to be closed. As such, the two processes to be integrated are the condition of the doors and the number of students in the school. The two state models to be mapped are the "door state" (open or closed) and the "current number of students" (add 1 if entering (+1), 1 if exiting). Draw (-1) to count the students passing through the door). The problem and solution are then abstracted to monitor the condition of the door and to count how many students pass when the door is open.

Then, node A1502, node B1504, node C1506, and node D1508 represent a cluster of nodes including processes to be integrated. The abstracted nodes 1502-1508 then connect to the door state attributes and the student attributes. Each node has a cause-effect relationship associated with an intermediate goal. For example, the intermediate goal E1510 is the number of closed doors counted, and the intermediate goal F1512 is the number of students at the evacuation meeting place. These goals then converge to a common goal that determines the proportion of people (students) at the evacuation meeting point and the proportion of closed doors. When both are 100%, the common goal 1500 is achieved.

When an attribute is identified as part of the process model, the state model is automatically extended to facilitate the storage of values for that attribute. That is, when an attribute is newly defined as part of the process model represented by the node's expected pattern, the state model programmatically stores the value for that attribute without extending the state support model. Expanded for ease. In the example of FIG. 15, the other attribute may be to turn off the light, and the state model may be extended to include the light state (on, off).

Resource allocation and scheduling. These are two examples of common programmatic difficulties that you may face when trying to build a system on a platform. A set of services can be built to provide computational support based on the best established practices. That is, the platform can provide a comprehensive resource allocation and scheduling engine that can be used in a variety of situations.

Advanced data visualization. The platform provides a set of services that display data by retrieving the data and making tables, graphs, and other visualizations. The output of the data and the associated display leads to the output of the node. The above-mentioned advanced data display, that is, the data input inserted in this top-level interaction of visualization, is achieved again based on the full display on the interrelated node structure. The node structure is considered to require user interaction (interaction). Therefore, any display clearly indicates either the conventional output display, which is the result of the information processing of the system, or the input dialog for incorporating the user's reaction into the output of the display.

Emergency response. Occasionally there will be sudden changes in the stakeholder goal priorities and, as a result, the connections between the nodes of the input and output relevance. For example, if an emergency (eg, a fire destroys a factory floor) occurs, the goal hierarchy changes and a new emergency overlay node network applies. Emphasize normal corporate goals The highest level of goals are implemented to minimize damage and allow personnel to evacuate safely compared to pre-emergency situations. And all the relationships between the processes that should follow, and the stakeholders change. As a first example, the role of assistant management may change from entering data to storing the data contained in the company's database. As a second example, the role of the maintenance worker may change from maintaining the device under good operating conditions to removing power from the device. As a third example, the seller's role may change from contacting potential customers over the phone to notifying crisis managers and managing the safe evacuation of equipment.

It is also recognized that physical objects and environments may be transformed while the emergency is in progress. For example, evacuation routes may be blocked and alternative routes may be determined. Alternatively, if the first identified responder is busy with another call, an alternate team must be identified and contacted.

The emergency response requires a person who is not the first user, a corporate participant, to enter information about the progress of the emergency from the perspective of the parties. The emergency response also requires a temporary user who will act (function) as a corporate employee in response to the emergency.

Emergency situations require coordination management. With reference to FIG. 17, in the prior art of emergency management linked in the core part, the information of a person who is not a corporate participant was used, but the information was handled through the person who receives the incoming call. Members of the organization 1230 (preferably those who are safety experts, but may not be such, depending on the scope and timing of emergencies) are Fire Department 1232, Police Station 1234, Health Worker 1236, Environmental Protection Agency. Stay in touch with one or more non-corporate participants, such as 1238. The member 1230 is then responsible for delivering this information to other members 1240a-1240e of the organization.

Prior art models have many shortcomings. In emergencies, many companies cannot afford to have a waiting call center to accept calls and experienced users. Here, the experienced level people are those who can interpret the information and can distribute the information to users in the enterprise who use the information to act and make decisions. Member 1230 receives information from multiple non-corporate participants 1232, 1234, 1236, 1238, who may not contact each other and give contradictory advice. People who may be. The member is responsible for disseminating appropriate information to multiple members of the company 1240a-1240e, and each member of the members may be interested in different things during an emergency and over time. It may change within the environment. In addition, members of companies 1240d, 1240e may contact each other 1242, and as a result, may neglect to pay attention to orders from member 1230. Member 1230 may need to terminate communication due to an emergency or due to a lack of cell phone battery. It is clear that prior art systems are not suitable for serious emergencies in large enterprises. Furthermore, it is clear that a system is needed to obtain the information, to interpret the information, and to redistribute the information to the decision makers and participants who need it.

With reference to FIG. 18, corporate respondents 1204a, 1204b, 1204c, 1204d, 1204e, as well as persons 1232, 1234, 1236, 1238 who are not bystanders or corporate employees, via the local telephone network, the local wireless communication network. With the addition of mobile phones, which can use mobile devices to access the Internet, first or temporary users will be able to participate in emergency response. They can enter information from a set of unexpected choices. The computer processor can then determine how to automatically deliver the information to the interested group. Emergency situations often require a combination of actions for a small number of improvements, so a combination of many choices at once is not necessary.

In an emergency, each corporate participant, or non-corporate participant, has a small combination of activity and experience that requires communication with others. Therefore, the novice user can easily select the action of the system because there are several choices through the system. If a mobile device that works with an inexperienced user provides many choices to the user with respect to information or response, the mobile device is not useful. The system needs to be aware of the situation in order to provide a combination of a small number of options.

In order to design a system of limited choices, it is necessary to accurately emulate the current situation. For example, in various dangers related to things like fires, storms, intruders, and different types of physical environments, a common emergency action is evacuation. For all enterprises, one or more of these are covered in many emergency response plans.

The following features are required to build emergency response applications for mobile devices:
A central application for controlling functionality.
In the central control process, the type of emergency must be specified.
Users in the enterprise must be given the appropriate interface to the current emergency. Users in the enterprise perform different activities in any emergency, so they must have access to different combinations of application interfaces for each special thing in each emergency. If an emergency expands, branches, or changes in stages, users within the enterprise must be given a less different but focused application interface. When users in an enterprise change due to absence, loss of function, or changing circumstances, users in other enterprises must take over their tasks and the appropriate user interface.
Non-users in the enterprise must be given the appropriate user interface, depending on their circumstances and often their whereabouts.
When users within the enterprise or non-users within the enterprise have to rely on responding with text messages, they are parsed at the core of the system to the right stakeholders for decisions or activities. Must be delivered. The system will need to assign SMS (Short Message Service) messages to corporate importance.

To achieve the above, the application will need to anticipate all activities and decisions of participants in emergency scenarios, their combination, and their transformations. A system suitable for responding to an emergency is preferably configured appropriately, regardless of the type or nature of the emergency, the type of information, or the type of decision made from the information.

The user interface requires user profiling, so each user obtains the appropriate user interface throughout the emergency.

Changing the User Interface Changes in the situation must change the user interface during an emergency, as soon as the situation branches, or as soon as the user changes. Depending on the designated user, changes in the situation may be automated or triggered.

A portion of function 1202 is illustrated with reference to FIG. Node 1206 is an important point for emergencies and is linked to nodes that identify different types of emergencies such as fire 1252, flood 1254, and intruder 1256. These different types of emergencies include the site of the problem 1258, the number of people arriving at a safe place 1260, the number of uncounted people 1262, the on-site emergency device 1264, the exit location 1266. Have a common node. Some nodes may have subnodes, for example, the number of people arriving at a safe location corresponds to each person's medical condition subnode, node 1268, and each person's medical condition. May have the corresponding sub-attributes in the state model.

The display screen 1208 of a person who is not a corporate employee, such as fire department 1232 or medical institution 1236, displays different information to the employee. For example, the fire department displays attributes such as the type of emergency (fire 1252) and location 1258 and the number of uncounted people 1262. No other information is displayed so that the information related to the fire department can be large enough for a useful display on a small screen. The display may be scrolled so that other information, such as location or exit 1266, is centered on display 1208. Also, a limited number of user input nodes 1270 are displayed, such as "Are specialized devices required?" With reference to FIGS. 18 and 19, if the answer to the user's input query is "yes", then the idea that the fire is essentially chemical is sent to the system. Will be done. The system may then access an in-house database for determining what chemicals are burning and a remote database 1214 for instructions on how to extinguish the fire, and immediately. You may return to the fire department staff 1232 and relay the information immediately.

Healthcare workers 1236 also understand that the emergency is fire 1252, but location 1258 may be less relevant than the number of people in safe locations 1260 and their medical status 1268. You may. Healthcare professionals may also scroll to other nodes and attributes, for example knowing the number of uncounted people 1262 is a query as to whether additional medical equipment may be needed locally. It may help you answer 1270'.

Emergency situations bring a strong interest to the user, and perhaps agility within a limited range.

The size of the screen is very small, alphanumeric characters, and the touch screen keyboard is physically very small.

In an emergency, it is necessary for the system to communicate with the user, and for the user, in order to send and receive information, to achieve the situation-specific needs. , Systems, and communication with each other's users is necessary. The information to be received or transmitted is context-specific and / or user-specific as perceived as necessary.

Situation-specific nodes relate to users whose need is recognized in an emergency. The relationship is through cause and effect and is a sequential process. Causes and effects are concentrated on the associated node. Instantiating situations with other stakeholders, or sensors, allows you to direct new alerts in situations where the user's attention is in progress. Sequential nodes allow transactions (ie, user input) to follow the sequence when needed. It may also be necessary to report a non-transactional sequence, indicating a sequential state. For example, counting the number of students, another example is an administrator who follows a sequence that approves the publication of a gradual expansion or gradual reduction situation.

Therefore, the system has A) a new situation to instantiate nodes related to the user through cause and effect, B) recent users who have selected the node, and sequential nodes related to those nodes, cause and so on. The results must indicate those associated nodes, C) the nodes that delineate the greatest risk and severity to the stakeholders.

Within a restricted display screen, with each role associated with quite a few nodes. You may not be able to see all the nodes on the screen unless you show them so small that they are not clearly visible and that you cannot navigate, especially in an emergency. Therefore, the three options to focus on are A) recent conditions related to the current node, B) nodes in which the user is currently playing a role or may want the user to output, and C) stakeholders. It is a node that draws the maximum risk and severity for.

A user can navigate other distant nodes according to another user who is deemed necessary.

To synchronize the control panel of an aircraft, the control panel is associated with all the latest potential emergency risks to roles / users, causes and consequences for the latest potential emergency risk nodes, and consequences. It will display the node, the last node of attention to the user / role, and the node with the highest risk and severity for stakeholders.

A similar example for mobile devices is conversations during emergencies in situations where it is difficult to convey sound. If the conversation is not related to the current emergency, or to the new risks associated with the emergency, or to the new conversation about the emergency and the most important things about a particular participant. In the meantime, the listener of the conversation will not participate in the conversation while panicked by an emergency.

To be flexible, such systems require the use of the following elements: :
Corporate importance;
Relationships between corporate important points;
Stakeholders of corporate importance;
Input from the user;
Scanning a corporate system to discover information related to a node;
Performing linguistic parsing of a corporate system to discover information related to a node;
A context that allows the user to select choices for contexts that are difficult to select in an emergency.

The system will need to maintain a pre-specified role-task relationship and a pre-specified task tree, without considering the relationships between corporate importance. As a central control process, it would be necessary to provide a modified task tree for each profiled user in order to turn it into a branch of the current scenario.

Alternatively, determining the orientation of an object is an associated, difficult to navigate, remaining option.

In the absence of relationships between tasks, there will be a number of task trees / user interfaces profiled for the user. Adding and reducing tasks may be the only way to reduce them. However, if there is no relationship between them, it will be difficult for the task to be selected and applied to the user interface during an emergency.

In the overlay relationship between process critical points, the number of user interfaces will be reduced to one large, concatenated user interface that can focus on any instantiated critical points. As a result, the user sees the nodes around the important points that are instantiated and selected by the context that applies to them. That is, the system reduces the exposure of each user (existence) at the interface, depending on the state and context, and the stakeholders of the profiling user. The instantiation of the state is selected by the specified user or automatically by the system.

In order to retrieve information for the field and to deliver it to the right users for the purpose of activities and decisions, the system must anticipate that information and plan ahead to present it to users. Must have the method. This is possible using prior art software and hardware applications.

The obstacle in design is to acquire the correct user interface for each user and environment. The following paragraphs describe some alternatives in the prior art.

Determines the direction of the physical object with respect to the input. For example, determining the orientation of a physical object is to guide (navigate) the system by first choosing from a choice of physical location or choice of people in need of evacuation. If there are only a few physical object choices, and the physical object is important to indicate relevant information, then the orientation of the physical object in the navigation user interface. It is possible to determine. However, if there are many objects to choose from for each user, more complex navigation will be required. For example, suppose there are five buildings and various places in the building for evacuation at school. Since evacuation is a place (related) and, as a result, the object is involved, there can be building-based evacuation information as determining the direction of the object. There are also other objects related to emergencies, such as students in the school. However, there are many different students in each class, depending on the time of day. Discover information based on students or buildings, as much information, such as information on the type of injury and information related to situations such as weather or breathing problems, is not easily related to these two physical objects. Navigating the system to do so would be difficult.

Determine the direction of business objects to display related objects. Determining the direction of navigation for a business object may be, for example, through a safety instruction document. Displaying a drawing of a business object, such as a related instruction document, to the user is a problem, as there will be too many choices per user due to the many process stages of many processes. It is difficult to determine the direction of a business object because of the existence of information such as instructions in the case of panic, instructions in the case of injury, medical records of personnel, and alternative exit routes based on location. Instantiation of the current process and selection of some objects are required to present the correct object to the user's attention. This requires processes related to the object. Doing this without a model is very inconsistent and difficult in software development and maintenance. Each object must have the code written for it so that it is output to the right user at the right time. In addition, regular upgrades of emergency response applications require new software releases, and such upgrades make the system more complex and more complex to navigate the system. will do.

Representing a user assigned to a node and context pair. The personnel available in an emergency may not have to be users who meet the system's default expectations, as in the case of normal enterprise software system users. Therefore, changes to user access may be required at the start and at the time of an emergency. When the situation is in progress, it is possible to do this on the fly only with the overlay model of the present disclosure or with a large number of programmatically pre-designed interfaces. Programmatically predefined interfaces must be assigned for proper use and for the current situation, as there will be many things with extensions. This is a fairly difficult task during an emergency, as it requires enormous resources during the design and implementation phase of a well-directed model task for an emergency response application. there will be. And without multiple interfaces programmatically pre-designed for the current situation and instantiation for development in emergencies, navigating to the correct object is very difficult on mobile devices. It will have a low affinity for.

SMS messages used to coordinate emergencies. If SMS messages are sent from the field, they will need to be interpreted and will require a central system for assigning words to nodes. Interpreting SMS messages will require assigning linguistically appropriate prediction patterns to the nodes. An alternative is to have a team of people who coordinate the communication path of SMS messages from the source to determine the need.

Therefore, it is desirable for emergency response applications to utilize the overlay's continuous user interface. The user interface can be realized by the model of the company revealed by the nodes connected by the cause and effect. Further, the user interface can be realized by being able to instantiate a part of the user interface for a new warning. In addition, by allowing the user to output past nodes of focus, or by allowing the user to output new areas of focus that are relevant to the user / stakeholder. Can be realized.

Although the present disclosure has been described from the standpoint of a unique form, it is clear to those skilled in the art that numerous alternatives, numerous modifications, and numerous modifications will be apparent to those skilled in the art. As such, the disclosure is intended to include all such alternatives, all modifications and all modifications that do not deviate from the scope and spirit of the disclosure and the scope and spirit of the claims.

1 Company 11 Company Goals 12, 42, 48, 75, 76, 81, 700, 710, 801, 802 Process 13 Part of Process; Process Node 14 Company Internal Content and Data; Internal / External Content Data 15, 63 Actors 16 Overlay software 17 Examination of process nodes 21 Process nodes; Process nodes and related examinations 22 Word expressions; Word expressions that describe process nodes 23 Natural language search; Overlay natural language search 24 Corporate data and internal content; Corporate data / Content 32 Corporate Activities and Objects 33 Recognition Structure 41, 44, 82, 83 Goal Pairs 43, 43-1, 43-2, 43-3, 46, 49, 50 Step 45 Process; Navigation Process 47 Goals 61, 62 Arrow 64 Skill, Value, Knowledge 65 Object 66 Context 71 High Level Goal Pair 72, 73, 74 Child Goal Pair 77 Comprehensive Process 78 Comprehensive Process Substep 80 Opportunity or Unexpected Event; Problem / Opportunity / Events; Problems, Opportunities or Unexpected Events 85-88, 701-705, 1206, 1206'Node 100 Web (Web)
711-733 Process Steps 811, 812 Lower Goal Pairs 901-912, 921-925, 1071-1080, 1181-1183, 1010-1026 Process 920 Expert User 930 Node Attributes; Attribute 931 Attributes 932 High Level Attributes; Attributes 940 Overlay System; System 1001 Problem, Opportunity, Decision, or Question 1024a-1024e, 1170, 1204, 1204a-1204e User Interface 1070 Context Specific Process; Original Process 1081 Field 1082 Node Attribute 1101 Content Scanner; Scanner 1102 e-mail
1103 Document 1104 Business object; Application data 1105 Web content 1106 Event history 1107 Problem-solving event in the company; Problem-solving in the company 1110 Scanned content 1120 Language syntax analyzer 1130 Index model 1150 Index engine 1160 Key point index 1171 Web-based search interface; Web-based search 1172 Web-based integration tools; Web-based integration 1173 Portal-based interface for application integration; Application integration 1174 Mobile device interface; Mobile device 1175 interface; Office / e-mail Application 1180 Procedure for fixing multiple events in the system; 1185 index story to be fixed in the system; Story 1186 Event 1187 Index engine; Index 1200 System 1202 Function 1208 Limited area display; Display screen 1208a-1208e Display area Display 1210 Keyboard 1212 Remote Sensor 1214 Remote Site; Remote Database 1216 Internet; Transmission Function 1216a Internet 1218 Computing Device 1220 Transmission Function; Transmission Equipment 1222 Mobile Phone Network; Local Wireless Network 1224 Database 1226 Coded Relationship 1230 Member 1232 Fire Department staff; Non-corporate participants 1234 Police Department; Non-corporate participants 1236 Medical workers; Non-corporate participants 1238 Environmental Protection Bureau; Non-corporate participants 1240a-1240e Corporate members 1242 Contact 1252 nodes (fire)
1254 node (flood)
1256 node (intruder)
1258 node (problem site)
1260 nodes (number of people arriving in a safe place)
1262 nodes (number of uncounted people)
1264 node (local emergency equipment)
1266 node (exit location)
1268 node (medical status of people in a safe place)
1270 User Input Nodes; Query 1500 Common Goal 1502 Node A; Abstraction Node 1504 Node B; Abstraction Node 1506 Node C; Abstraction Node 1508 Node D; Abstraction Node 1510 Intermediate Goal E
1512 Intermediate goal F

Claims (11)

A system that discovers and transforms information related to processes related to a company.
The system
It comprises a computer-readable medium with executable instructions encoded on a non-temporary digital storage medium, said non-temporary digital storage medium also storing company models, company content and company data. Equipped with a computing device
The business logic layer associated with the model is a description of the relationships between multiple nodes and the different nodes that are computer readable relationships that are expressed as computer readable causes and consequences. Includes computer-readable description of content, data and relationships between different nodes,
The software code defines the causes and effects that can be read by the computer when connecting the node to the adjacent node.
The system
A device that can communicate with the computing device and input / output data related to important corporate points.
A user interface and an interface associated with the device, comprising a display in which a plurality of nodes or nodes related to content and data are visible in a first predetermined moment.
Including the system. The business logic layer includes a master process model that facilitates the representation of node states, values and the abstraction or generalization of adjacency logic used in the enterprise, the master process model being node states, values and adjacencies. Including alternative representations of logic
The system of claim 1, wherein the abstraction represents an alternative but equivalent combination of node states, values and adjacent logic that occurs within different information structures within each state model. Similarities between two nodes appear in the state model and are calculated according to the contextual data that appears as the connection links and their abstractions in the master process model utilized by each of the two nodes. The system of claim 2. The model does not require further modification of the underlying structured storage mechanism or data model and can be dynamically modified while the event is in progress by adding or subtracting nodes. Item 1 system. The system of claim 4, wherein the model can be dynamically modified while the event is in progress, without any programmatic modification entered into the user interface. The computing device is replaced by a plurality of networked computing devices or cloud infrastructures, and the encoded executable instruction is the plurality of networked computing devices or the cloud. The system of claim 1, which is divided and executed between infrastructures. A system that emulates the underlying process in an overlay system
The system
A plurality of steps of the underlying process are identified, and each of the plurality of steps is assigned an attribute that is a state attribute of the underlying process.
The attributes associated with a node are associated with that node, and the state of each node is a single attribute within that node.
Build process steps into a cluster of multiple nodes
Establish a computer-readable cause-effect link between the nodes in the cluster,
Set the attributes for each node in each state model and
Computer-readable causes and consequences such that the single attribute is processed by adjacent links and propagated to the next linked node to determine the relationships between the state elements of the underlying process. Use the link,
A system that uses steps. The system of claim 7, wherein each node contains state information, wherein the state information includes context, which facilitates propagation to compatible nodes, particularly according to state parameters. Each node has multiple states, at least one state contains context
The system of claim 8, wherein the state value propagates to the compatible adjacent node by matching the compatible state including the context in the adjacent node having a plurality of states including the context. A middleware device intervening between a central device and one or more external devices, both the central device and the one or more external devices having executable instructions encoded on a non-temporary digital storage medium. Equipped with computer readable media
The middleware device is
a) A middleware service with a database and processor, the database storing a model of one or more companies, the model storing business processes, enterprise domain software logic, data and content used by the central device. Included and integrated, the model includes a process node of one or more enterprises and a link connecting the process nodes, each process node has an attribute value and a state, and the link is a computer of association between adjacent process nodes. Defines readable coded relationships with middleware services,
b) Store the model of one or more enterprises or a portion thereof, the model including and integrating business processes, enterprise domain software logic, data and content used by the external device, the model is 1 Including the process nodes of the above enterprises and the links connecting the process nodes, each process node has an attribute value and a state, and the link has a computer-readable coded relationship of relationships between adjacent process nodes. With one or more external devices as defined
c) Effective for monitoring execution by the one or more external devices, the middleware device is a packet of information between the central device and the one or more external devices using their corresponding models. When the middleware service detects a change in the expected functionality of one or more external devices through its corresponding model, the processor resets the attributes of the corresponding model of the central device. The middleware service that changes the state and value of the corresponding node in response to that change and propagates the value to the affected node in the processor model via the adjacent code / logic of the corresponding node. A middleware device equipped with. A middleware processor intervening between a central device and one or more external processors, both the middleware processor and the one or more external processors having executable instructions encoded on a non-temporary digital storage medium. Configured to access computer readable media,
The middleware processor is
a) A middleware service that includes a database and a middleware processor, the database storing a model of one or more enterprises, the model being accessed by the middleware processor, business processes, enterprise domain software logic, data and content. Includes and integrates, the model contains links connecting process nodes and process nodes of one or more enterprises, each process node has an attribute value and state, and the link is the association between adjacent process nodes. With middleware services that define computer-readable coded relationships,
b) The one or more external processors also access at least one or more enterprise models or parts thereof, which include business processes, enterprise domain software logic, data and content used by the external processors. Integrating, the model contains process nodes of one or more enterprises and links connecting process nodes, each process node has an attribute value and state, and the link is read by a computer of associations between adjacent process nodes. With one or more external processors that define possible coded relationships,
c) Effective for monitoring execution by the one or more external processors, the middleware service is a packet of information between the middleware processor and the one or more external processors using their corresponding models. When the middleware service detects a change in expected functionality of one or more external devices through its corresponding model, the middleware processor resets the attributes of the corresponding model of the central device. The middleware, which changes the state and value of the corresponding node in response to the change and propagates the value to the affected node in the model of the middleware processor through the adjacent code / logic of the corresponding node. A middleware processor with services.

Images