JP6216076B2 - System and method for identifying information relevant to a company - Google Patents

Description

  The present disclosure relates to enterprise software, and in particular to software that assists in finding information related to problems, opportunities, and / or unexpected or interesting events that affect processes performed by the enterprise.

  An enterprise (which may be any organization that performs activities for a purpose) generally has goals and processes designed to achieve those 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 (enterprise system users) need to be warned of issues that could pose a risk to the processes for which they are responsible. A user who needs to solve a problem will be free to use information related to the problem, particularly information about co-occurrence and past experience in the company related to the problem. The user may also want to cooperate with other users in problem solving.

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

  In accordance with the present disclosure, systems and methods are provided for discovering and retrieving information within an enterprise relating to enterprise issues, enterprise opportunities, and unexpected or interesting events. When the system retrieves company information, current items (eg, e-mails being routed) and past items (stored notes) to enrich the system's knowledge related to problems, opportunities, or events. ).

  According to a first aspect of the present disclosure, a process performed by an enterprise, or a process of discovering information related to an enterprise importance of the process, scans content related to the process performed by the enterprise. Comprising a configured computing device, the process comprising one or more process steps, wherein the computing device is a problem, opportunity (opportunity) or event (company) associated with the process step Identifying the key points); indexing the scanned content for the company key points; determining whether the scanned content is information related to a problem, opportunity or event; , Provide relevant information. The relevant information includes a description or review of the company's (or related company's) past experience with respect to the problem, 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. Company critical points are problems, opportunities or unexpected or interesting events and relate to other important points that further describe the cause, consequence, improvement (rescue).

  Determining whether the information is related to a problem, opportunity or event includes determining the impact of completion of the process step in achieving a goal associated with the process including the process step. This is referred to as the goal proximity of the process step. Also, the goal proximity of the process step may be used to determine a risk that is an important relevance criterion.

  Also, goal proximity determination may be used to find similar processes that are considered similar due to similarity in a comprehensive view of the process and similarity of proximity to the goal. Experience related to those similar processes is responded from the system to draw the user's attention.

  Relevance determination is facilitated by identifying processes characterized by generic process components in the system so that inferences of similarities or relationships between processes are drawn from their comprehensive perspective. May be. In addition, endemic problems or opportunities embedded in the process establish further similarities and relationships between the processes.

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

  In addition, the system may further include a user interface that utilizes the importance index to achieve the following: alert the user of problems associated with the set of processes involved; collaborative users (stakeholders) It is likely that the information given to the process will be limited to past contemporaneous information about the process and that the information about the underlying process will pose a risk for the cooperating group (stakeholders) For example, by providing users with information about the underlying process, it enables collaboration between users to deal with problems or opportunities associated with the process; description or review of past experience related to problems associated with the process Search for information containing. In an embodiment, the index engine is a middleware service.

  According to other aspects of the present disclosure, a user may manipulate (navigate) a recognition structure that retrieves past and present experiences used for various uses described herein.

  In addition, according to the present disclosure, when solving a company problem, using a company opportunity, explaining an object of interest or an unexpected event that occurs in a company activity, the following decision may be made. Good; By associating the content or data with the relevant enterprise key points (process nodes) or elements of the cognitive structure that are most closely related to these process nodes, the relevance of the content or data item to the enterprise is completely Determined; refer to process identifications and their comprehensive process components, the goal proximity of the process in which each process depends, the specific issues, opportunities and events associated with the process Makes it possible to completely determine the similarity between processes; the processes involved in one step When it is determined that a node presents a risk, (i) the goal proximity of the step to the direct goal of the step, (ii) the goal proximity of the step and the effect of the step on further dependent goals , (Iii) the estimated cost of the failed goal and the action to improve it, and (iv) the likelihood of failure by the node, the risk severity (importance) is fully determined Is done.

  The foregoing has outlined, rather broadly, preferred features of the present disclosure so that those skilled in the art may better understand the detailed description of the following disclosure. Additional features of the disclosure will be described in forming the subject matter of the claims of the disclosure. Those skilled in the art should recognize that they can readily use the disclosed concepts and clearly illustrated forms as a basis for designing and modifying other structures that perform the same purposes as the present disclosure. It should be appreciated that such other constructions do not depart from the spirit and scope of the present disclosure in its broadest form.

FIG. 1 systematically illustrates an enterprise having goals and processes using software that discovers relevant information linked to the enterprise, in accordance with aspects of the present disclosure.

FIG. 2 systematically shows one view of process nodes for enterprise processes.

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

FIG. 4 illustrates a process associated with a company goal.

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 the interaction between actors in a company and certain process steps.

FIG. 7A systematically illustrates a generic process and a more specific process.

FIG. 7B systematically illustrates a process that includes process nodes or enterprise critical points.

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

FIG. 9 is a flowchart illustrating the process of assigning node attributes by an expert user at a level specific to the various contexts of abstraction.

FIG. 10 is a flowchart illustrating steps in accordance with aspects of the present disclosure that identify generic processes and processes that are similar to a given original process.

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

FIG. 12 is a flowchart illustrating a method according to an aspect of the present disclosure, in which software builds and integrates enterprise key points.

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

FIG. 14 systematically illustrates a system according to an aspect of the present disclosure that collects information and indexes the information for the company critical points.

FIG. 15 systematically illustrates goal convergence according to aspects of the present disclosure.

FIG. 16 systematically illustrates a system used by multiple users, including users with limited viewing rights.

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

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

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

  Software embodying the present disclosure is referred to as “overlay” in this disclosure. Overlays help you discover information within your company. This source is typically an 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 enterprise that the enterprise wishes to access on a regular basis. According to one aspect of the overlay, the overlay functions as a relevance engine as opposed to a search engine. Overlays search only for information that may be relevant to company issues, company opportunities, and unexpected or interesting events.

  Overlay software is used for business processes such as the relationships between enterprise processes and the key points of such processes (ie, hazards, anticipated failures, conflicts, risks, common causes, areas related to attention and knowledge). Use the relationship between the focus points). The overlay software provides the user with only appropriate returns (search results) from potential data and content so that the following can be achieved: Use sex.

  The overlay provides the overlay user with an overview of the changes underlying any enterprise software / e-mail that may constitute the enterprise point for which the user is responsible. In large organizations, it is not possible for senior staff to manually navigate and monitor all applications. Also, it is impossible for the senior staff to handle hard wired workflows that are potentially events that can constitute a problem, and that are difficult to change for all possible events. Since enterprise important points often arise from the combination of multiple events, overlays help identify those corporate important points. The overlay also refrains from such notifications if frequent notifications are not desired.

  Overlays allow overlay users to access corporate content and / or data systems (including e-mail systems) from a remote location using a mobile device. Furthermore, the overlay enables drawing in which events affecting the important points of the company are selected (filtered).

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

  Overlays allow overlay users to manage unwanted events supported by relevant legacy content.

  Glossary

  Cause: An occurrence or potential event that will cause an outcome.

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

  Impact: An event or potential event that will affect a 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: To find the cause of a problem and to explain the cause of the event or opportunity of interest.

  Organize: abstraction, generalization, grouping.

  Goal proximity / proximity: The ratio of the influence of a process step to the goal of the process to which the step belongs.

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

  Recognition structure: A structure in which information is indexed in a manner that conforms to known recognition principles.

  The main way to better understand a problem or opportunity: how to determine the most relevant relevance for the problem or opportunity.

  Events / Study / Description / Experience: These are experience events that can describe all or part of a cause, outcome, risk, improvement. These may include generalized descriptions and generalized models to describe how things work 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 property of an entity described in this disclosure. Node attributes are used to determine node similarity. In other words, it is a characteristic of a node that determines similarity. Node attributes are represented in the state model. That is, the node characteristics are represented in the state model.

  Take responsibility: A situation where the attributes of an actor have a great influence on the output of a process or process step.

  Problem / Failure: For purposes of this disclosure, problems and failures are problems reasonably expected by experienced practitioners and / or nodes considered within the process of failure, or phenomena that are not explained, or This is an unexplained cause and effect phenomenon.

  Opportunity / Success: In the present disclosure, opportunity and success are nodes that are considered in the process of problems and / or failures reasonably anticipated by experienced practitioners.

  Event / Unexpected Event / Interested Event: For the purposes of this disclosure, an event is an occurrence that an experienced practitioner considers important to the company and their goals.

  Process node: A part of a process where experienced practitioners anticipate problems and opportunities.

  Experienced practitioners: those who have been responsible for, and have been responsible for, the majority of their work experience in processes that are determined to be experienced. Those who are conscious of special characteristics and who recognize processes subordinate to processes that are considered to have abundant experience and subordinate processes.

  Company: Any organization, or collection of organizations, that operates for one or more known purposes. Predictability of goals at one time, predictability of plans and processes to achieve those goals, and values, skills, information, endurance, emotions that are substantially known in relation to the goals Are generally characterized by actors having

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

  Corporate activities: Activities recognized by practitioners in each field or one or more fields.

  External process: An external process that occurs outside the enterprise, on which several enterprise processes depend, for example, design, construction, education, and preparatory activities that can be part of any process step. A process that is not designed to serve a known goal, but is found to occur in an environment that affects corporate processes and goals (eg, human activity at discretion). Or a process that is not directly related to human activity, such as an environmental phenomenon.

  Practitioners: People with average experience in the company.

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

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

  Object: An object in some area of the process.

  Context: The environment within the field where the process takes place.

  Abstracted object: An object that may be abstracted and as a result may be applied to more than one field.

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

  Domain: Industry, company department, or any corporate structure. Here, the corporate structure is such that process steps and technologies are specified, and a practitioner can understand the process steps and the technologies.

  Immobilization: A characteristic of an entity within a business activity model. The practitioner expects the characteristic to be sufficiently constant and predictable, so it is considered constant although it changes.

  Relevance criteria: Any entity that helps build a business activity model or business activity structure.

  Environment: Context, runtime, or similar.

  Process: A series of actions that are useful for combining goals and conditional goals. Processes range from fixed processes to established processes, newly established processes, and the range of processes to be executed.

  Script: A process that is consciously and potentially executed by being fixed.

  Plan: A plan is a less well-defined process where the steps in the process are ordered in a way that fits the current environment. The hierarchy of plan goals is often different from the underlying process associated with the plan.

  Inanimate process: A process that does not involve human intervention (for example, a chemical process) and has no goals other than the process goals that are artificially set as part of the process It is good. For example, corrosion is a viable process that is predictable and well known, but 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 prefering 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 corporate fields generally have the following attributes with respect to goals: value set, skill set, knowledge set, information set, endurance set, emotion set. One or more companies may belong to a sector, defined as an industry, company department, or any company structure. Here, the corporate structure refers to a structure in which process steps and technologies are specified, and a practitioner can understand the process steps and the technologies. Thus, practitioners in a given field may be said to share specific knowledge.

  Goal 11 directly affects a corporate goal (which is often expressed at a high level, so a company-specific process is not associated with that corporate goal), the main goal (one or more corporate goals) Achievements) and conditional goals (i.e. goals that are not the top-priority reasons for designing the process and may otherwise prevent the main goal from being achieved, or the main goal) Processes may be based on goals (generally performed by corporate actors who act to achieve goals) that can achieve goals but achieve something they do not want. Alternatively, the process is not based on goals, but can often be artificially defined and designed. Alternatively, the process is not based on goals 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 sought by a person but is not necessarily artificially defined. There are risks and problems and opportunities arise when performing various processes within an enterprise. These issues have causes, consequences, risks, potential impacts and improvements.

  The part 13 of the process in which risks, problems, opportunities are shown as experiences that can present them, or accounted as experiences that can cause unexpected or interesting events, This is called a “process node”. Process nodes are often identified by actors 15 who have experience in the enterprise. The overlay software 16 according to the form accessed as a service on the Web 100 by the company searches the company internal content and data 14, and sometimes the 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. The overlay searches the natural language search based on the process nodes in the enterprise and the word expressions used to describe the natural language. The overlay also retrieves structured data that is known to be associated with 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 can be part of design, construction, or education, and optional process steps. It is. The process is not designed to serve a known goal, but may be a process that is discovered to occur within an environment that affects the enterprise process and goal (eg, any human activity) . Alternatively, the process may be a process that is not directly related to human activity, such as an environmentally dependent phenomenon.

  Process node

  As systematically shown in FIG. 2, the process node 21 is characterized by one or more problems, opportunities, and / or unexpected / interesting events within the process or within the process steps of the process. It is done. In a natural language search 23 of company data and internal content (and other information sources) 24, a word representation 22 describing a process node is used.

  Enterprise process nodes represent the components of the recognition structure (detailed below). Process nodes as components of the perception structure are the problems and / or opportunities for practitioners to discover relevance to goals and / or processes within the enterprise, and sometimes outside of the enterprise's direct scope of activity. And / or a review or description of the event. Such activities outside the company's direct scope of activity include other companies, the business community, the political environment, the social environment, the physical environment, the biological environment, or any environment that significantly affects the corporate process. However, it is not limited to these.

The process node may include differences to the review and / or description of potential issues, opportunities, events as follows.
(A) Consideration and / or description or data regarding problems or opportunities or unexpected events in executing one or more goals or conditional goals within the following processes.
(1) A process that is considered to be affected at the time it is considered or described or at a later time.
(2) A process that becomes a component of a process 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 problems or opportunities and / or potential problems or opportunities within the processes below the affected process.
(B) Investigation and / or description or data regarding:
(1) Review and / or description or data regarding the explanation of problems, opportunities or unexpected events.
(2) Review and / or description or data regarding the analysis of the cause of a problem, opportunity, or unexpected event.
(3) Review and / or description or data regarding the cause of the problem, opportunity, or unexpected event (cause of the cause).
(4) Review and / or description or data on plans that can be considered as actions to improve problems or take advantage of opportunities.
(5) Review and / or description or data on procedures that describe how to avoid problems or how to draw opportunities.

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

  The recognition structure considered in this disclosure is a structure having information indexed using a method that conforms to a known recognition principle, which allows the relevance of information to be determined. And are configured to be related to each other.

  As systematically shown in FIG. 3, the recognition structure 33 is an abstract representation of daily activities and objects related to them. These are activities and objects that are familiar to the average practitioner outside the subject area of the company. This is because they are used in business activities in many fields every day. Such business activities and objects 32 are generalized to users, user roles, tasks, contexts in which tasks and processes occur, corporate objects, processes, goals, skills, values, actors in the process, 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 recognition structure may be abstracted and / or other abstracted entities.

Therefore, the recognition structure 33 may include the following.
goal;
Goals and associated processes, and associated unique nodes (detailed below);
Company, company department, associated roles, actors, and attributes (eg, skills, values, etc.);
Generalized process node;
Specific process nodes;
Low-level goals and associated process steps;
The task and the actor or role that defines the task;
The context and the associated process or task that the context affects;
The object and the associated process or task that the object affects;
Workflow;
User

  The overlay software also discovers information related to any process or process node or any element of the recognition structure. The information retrieval method used by the overlay software is applied to this related information. Moreover, these search methods are applied to many elements of the recognition structure.

  The word “relevant” is related to the process at risk, as an additional process at risk, the cause process, the abstract cause process, the additional cause process, Process of action for improvement, related as a process similar to any other process, associated by a common context or object or abstraction thereof, associated by a common node or abstraction, common This includes, but is not limited to, a goal or a conditional goal, or association by a combination thereof.

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

  As described in detail below, the relevance between a company and a content item or data may be completely determined by the company importance (process node).

  Process analysis; process similarity

  FIG. 4 is a systematic diagram showing some goals and some processes for a company. This figure shows that 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 company shown in the figure is a company that carries goods transportation, particularly transportation including sea transportation. Therefore, there are other goal sets 44 in the field of companies dealing with “Navigation”. In this example, the process 45 for navigating from one point to another has the following steps 46. The multiple steps are viewing (eg, finding a navigation goal), moving (eg, operating an engine), and setting the course at the requested position. In FIG. 5, as shown in more detail, the “seeing” process step has the need for glasses. Therefore, the loss of glasses becomes a problem component 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. Also good. The group of goals 47 includes a main goal ("fire gun", "hit target"), and conditional goals ("avoid other objects", "avoid explosions"). The conditional goal “Avoid Explosion” needs to be met so that the goal “fire gun” is achieved in the desired manner. The process 48 for achieving the goal “fire gun” includes a “view subject” step 49. The activity “watching” may be determined as a comprehensive activity associated with both processes. Further, the process 48 includes a step 50 for “tuning the gun”. The process step for “tuning the gun” has the need for a wrench, and losing the wrench becomes a problem component of the process step. Losing spectacles and losing a wrench may be determined as a global problem (i.e. a global node), i.e. "losing tools".

  In FIG. 5, some nodes and some processes are context specific and are labeled as generic in the context. It can be seen that even processes in different fields are related to generic processes and generic nodes. More generally, once context-specific nodes are identified, those nodes that are context-specific define more generic nodes. These more generic nodes then define generic components in a context / domain specific process in a given domain. These generic process components, and their generic nodes, will be in other disciplines at some level of inclusiveness, and as a result will represent nodes that are specific to this different context / field right.

  Process nodes may be similar to other process nodes. This is determined by the similarity of the processes or process steps that are described in detail below. As shown in FIG. 5, process steps of different processes often have commonality. When a process step is common to two processes, the two processes are considered similar if they can similarly affect the goal of the main process to which the process step belongs. The influence of the process step on the goal to which the process step belongs is referred to as “goal proximity” of the process step.

  Overlay software discovers events that are similar to a problem and / or opportunity of a given process node by finding similar processes and showing similar events with similar process and process nodes and goal proximity. In this regard, it should be noted that the overlay does not depend on a vast combination of process conditions for event similarity. Overlay evaluates process similarity from goal proximity, node similarity, and abstract or unique node (an abstract node or unique node defines an abstract process) Provides an alternative way to do this, because at the most abstract level the process has been devised to handle highly abstract unique nodes). In a given process, process conditions are included in the process. Thus, the discovery of similar processes will define conditions that are comparable. This is because, in practice, prominent conditions are introduced into the process nodes (process problems and opportunities). Thus, if a process node has defined process criteria, that process node is also sufficient to define conditions within the process.

  It should be noted that the overlay searches for similarities that are included in both processes and nodes. In general, processes are developed such that problem nodes are avoided and opportunity nodes are drawn. A given process may have one or more nodes. As a result, node similarity is included in process similarity.

  Furthermore, the hierarchy of goals within the process affects the similarity determination. 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 the characteristics of process similarity. Processes with similar goal hierarchies will be similar. Thus, process similarity does not depend solely on a common process or a common generalization for those process steps.

  Goal proximity; chance of success

  In general, not all process steps are equally essential in achieving successful process goals. As described above, the word “goal proximity” means the influence of the process step on the goal to which the process step belongs. Process step goal proximity may be quantified by how close the process step is to achieving success or failure with respect to one or more process goals or conditional goals. 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 subject” is determined to be 70%, depending on the completion of the process step “seeing the subject”. These relationships are systematically indicated by arrows 61 and 62 in FIG. 6A. As a result, problems within a high goal proximity process step will have a greater impact on the success of the process. Goal proximity provides an additional measure of process similarity. Processes that have a similar impact on the goals of the subordinate processes and processes that also have a common generic or specific characteristic (eg, common nodes) are considered to be similar, even if they occur in different areas .

  Rich resources (or lack of resources) are considered attributes of process steps within the process. Therefore, the resource redundancy affects the goal proximity of the process. Further, depending on process abundance or process redundancy, problems or opportunities within the process affect the proximity of the process steps to the goal.

  Also, actors (people who perform processes or who do not execute processes but are involved in processes) affect the success of the process. As shown systematically in FIG. 6B, actors primarily affect the process steps for which they are responsible. In general, an actor has the following attributes: value, skill, expertise, information, durability, and emotion. Depending on the process step, other actor attributes may be considered relevant. Attributes then affect the likelihood of an anticipated problem or opportunity related to the process step, and consequently the process goal. As illustrated in FIG. 6B, an actor 63 responsible for the step “view subject” has skills that affect one or more objects 65 associated with the process step and the context 66 in which the step is performed. , Value, knowledge 64. If the object used in the “view target” step is a scope to see and the context is fog, the skill of the actor using that scope to see the target in the fog is Significantly affects success. From this example, it can be seen that the process step itself also has a goal (“find objects using a scope”), and that the attributes of the actor affect the goal. In general, the process steps that an actor performs or influences have a goal and a conditional goal. And it is those steps that the actor's attributes affect, or the goals of these components, or conditional goals.

  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 a comprehensive process of “traveling by controlling a car or ship”. And it has comprehensive components such as viewing, steering, planning and so on. A comprehensive process is a process that is not domain specific and is recognized by practitioners with average expertise in other fields. In general, a process has a generic component or belongs to a more generic process.

  A comprehensive process is a process that is less specific to a context in a given area. As the process reaches a higher level of abstraction, it will be less specific and include more generalized nodes. Processes that are least specific to the context can become very general so that they do not have unique steps, and as a result, are identified from other than the unique nodes (detailed below) It may be difficult.

  The generic process may be expressed as schematically illustrated in FIG. 7A. The high level goal set 71 has a child goal set 72, which in turn has child goal sets 73, 74. Processes 75 and 76 are designed to achieve goals 73 and 74, respectively. The solid boundaries of the processes 75, 76 in the figure indicate that these processes are field specific processes. The dotted line represents a generic process 77 or a generic process sub-step 78.

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

  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, result, or improvement related to a problem / opportunity / event that occurs in connection with the process or other processes.

  In process 700 shown in FIG. 7B, each of process steps 711-733 has a goal proximity with respect to goal G1. Otherwise, if the node represents a risk, each of process steps 711-733 has the potential for process failure. These concepts are used to analyze the risks associated with the process. Unlike other risk analysis methods, in overlay software, risk is specified by goal proximity or otherwise by evaluating likelihood. As described above, goal proximity is a percentage specified for the degree to which a goal in a process or a conditional goal is affected by the success or failure of a subordinate process. The goal proximity of processes with the same level of subordinate or subordinate degree is added to 1 or 100% overall. Each subordinate process relies on an equally low level process at a subordinate degree. For example, in the process of navigating, determining the ship's direction depends on propulsion and 100% steering. The propulsive force and steering being 100 depends on the electric power. In the process of determining the direction of the ship, there are equally subordinate process steps, such as continuing to watch, planning the navigation, and managing the crew.

  Risk is assessed in terms of goal proximity. When a process within a step is determined to have a risk, the severity of that risk is the step's goal proximity with respect to the immediate goal for the process, the step's goal proximity with respect to the dependent goal, goal failure May be fully determined by referring to the accumulated cost for and the accumulated cost for actions to improve against goal failure.

  The goal proximity helps to assess the cost of the process and the software to manage the process. Add 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, and benefit from the success of the affected processes The connected goal proximity of the cause and 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 selling overlay software that manages information related to risk mitigation or use of opportunities is worthwhile. Overlay assesses the value of processes or their nodes, and builds the right indicators for assessing the value of software that helps manage the process by mitigating risks and managing opportunities.

  The risk or potential opportunity is presumed to be more qualitatively determined by the availability of relevant experience in the process that will be affected by the problem, as determined by the goal proximity of the dependent processes May be. Furthermore, by integrating the goal proximity and the probability of failure and opportunity within the underlying processes, impacts, risks and opportunities can be assessed quantitatively.

  Connected process

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

  As described in some content or represented by some data pattern, an opportunity or unexpected event 80 has associated risks, causes, consequences, improvements (rescue). In general, all risks, causes, consequences and improvements will not be found in a single 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 subordinate goal sets 811, 812. These processes all have nodes associated with problems / opportunities / events 80. In the example shown, node 85 indicates a process step within process 81 that is at risk. Step node 86 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 other steps of process 801 represents an improvement.

  Specific problems and impacts

  As described 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 higher levels of abstraction are reached.

  A comprehensive process can be abstracted into multiple types. Of the comprehensive processes, one type may be associated with a domain-level process and will be recognized by practitioners with experience in similar fields. For example, traveling far away with a vehicle is a kind of comprehensive process that is different from HR management. At various levels of abstraction, experienced practitioners consider certain problems or opportunities to be repeated in various related processes. Such a problem / opportunity is referred to as unique. Since problems and opportunities cannot be defined without setting an initial goal, unique problems / opportunities are associated with the goal.

  A comprehensive process type is defined by a unique problem / opportunity combination. For example, in the field of human resource management, there are many unique problems and opportunities related to human resources going back in the past. And the entire process field has grown to address those issues and opportunities. Furthermore, high level of comprehensiveness processes are defined by their unique nodes. Also, in overlays, generic processes, including generalized nodes and / or further generalizations, are grouped with unique problems or opportunities. This is done when the process becomes very common, so these process steps become common, and the entire process is defined without reference to specific problems or opportunities (often referred to as themes) Because it becomes difficult. In an overlay, the generic process is defined by a combination of abstract unique problems or opportunities associated with the generic process.

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

  A high level of unique problems or opportunities (themes) are highly domain specific and help to organize low level unique problems, followed by unlimited number of unique problems in an unlimited number of fields. Useful for organizing multiple levels. In addition, unique problems or opportunities (themes) help organize a high level generalized process, followed by a number of comprehensive processes that are highly domain specific and unlimited at a low level. Useful for organizing.

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

  Objects and contexts

  With reference to FIG. 6B, as described above, objects and contexts change the influence of nodes on process completion and goal achievement. Nodes may affect more or less the process and the goals of the process as a result of different contexts or objects. In some cases, process nodes are different when the process is very specific to the field and has a very specific context and specific objects. Subsequently, contexts and objects are affected by actors and attributes of the actors (or companies or departments and attributes of companies). Thus, in general, different actors or contexts will have different actors having different effects on the same process. The context or object itself may provide more or less the possibility of affecting one or more process goals or one or more subordinate process goals.

  Object and context changes affect both process and goal proximity. The goal proximity varies depending on the process. However, if the processes are very similar, they have objects and contexts that can be different in different fields. Thus, in order to facilitate the adoption of overlays across disciplines, overlays incorporate relationships between object contexts and their processes, depending on the discipline. So in new areas, the system highlights different objects and contexts, especially when each process step is affected by differences in objects or contexts, and re-evaluates the goal proximity for each process step. You may request that. Also, to facilitate adoption across disciplines or businesses, overlays may include contexts and relationships with objects and actors, users, and other elements of the recognition structure.

  Objects and contexts can be generalized or subdivided into components and can have relationships between them. Objects and contexts associated with a company, along with their relationships, have generalized representations and components that vary depending on the goals that the objects and contexts fulfill and the associated processes or plans.

  The degree to which the system requires all or some attributes to be dynamically related to each other is based on the experience and requirements of each field and the client application of the system. If all attributes are not dynamically active, the dynamic interrelationship of the attributes with the entity that they would normally affect remains constant in the default state. For example, when an actor's attributes are considered average for convenience, the impact of actor attributes on the likelihood of problems and opportunities occurring within the process step is unbiased. In another example, if the redundancy of resources used in a process step is average, the proximity of the process step that affects the goal is average. When an expert in a process considers the process average in the field, the effect of the attributes is average.

  Along with time specifications for concurrent events, objects and / or contexts help determine whether two events of similar events are actually the same event. This is important when the search goal for relevant information is to find content and data that coincide with the event.

  Goal hierarchy and goal competition

  To determine which sub-process steps are more important in any environment, it is required to examine the goal hierarchy and goal conflicts between goals in the process. The more the process is applied, the more consistent the goal hierarchy and the more attention is paid to the process design to avoid problems due to goal conflicts. If the process changes and becomes like an action plan with a new process process step and a new goal structure, the goal hierarchy and goal conflict need to be re-established. In addition, new process steps need to be applied to mitigate the bad effects of inadequate results and the bad effects of goal competition as a result of a poorly maintained goal hierarchy.

  Overlay relevance model: goals, processes, nodes

  While it is beneficial to have a consistent relationship between goals, processes, and nodes (consistent relationship), it is not essential (hereinafter referred to as relevance convention). For overlay users, if the relationship between goals, processes, and nodes appears consistent but does not follow convention, the result of the relevance (ie, the experience event output by the relevance engine) May remain sufficiently satisfactory. This is because, in general, current conventions do not group goals, processes, and nodes according to any consistent convention. The relevance conventions used, according to aspects of the present disclosure, are detailed below.

  Node attribute

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

  (1) Goals and actors: Goal conflicts exist between processes designed to overcome goal conflicts and between actors behind the process. For example: Legal contracts are designed as a process to let people agree how conflicts are avoided or arbitrated. Mechanical design is a process that overcomes the competition between the benefits and costs of mechanical 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 goals of different actors and / or between the main goal and the conditional goal. While the assets available in the environment are helping to achieve the goal, there may be additional types of goal competition between the goal and the obstacles in the environment. 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 goods. Each product has specific assets and obstacles that are affected by this goal competition. The customary goal competition between quality and cost in the manufacturing process and the production of mechanical mechanisms, determined by the product, has an associated node. The node most closely associated with this goal conflict is the cause node of any product failure. Goal contention is therefore closely related to the nodes in the causal process.

  (2) Assets and failures: Assets and failures are elements specific to the context and process most associated with each node. They are elements in the process that change according to the context and are generalized to more comprehensive assets and obstacles when grouped by generalizing the relevant contexts. Again, referring to the example of manufactured goods and the example of intrinsic goal competition between quality and cost, in the same context (eg, control oil pumps), a group of similar products with common designs. Will have similar problems characterized by the assets and obstacles affected. In addition, due to design diversity among products within the same context group, there may also be assets and obstacles associated with problem nodes that differ between the products. In this case, the context structure needs to divide the product into individual specific issues and further individual products with associated assets and obstacles. This means that nodes grouped in this very specific context are not generalized between different contexts. However, all nodes will be grouped under a goal conflict between quality and cost. As such, a group of contexts manage assets and faults that are active at an active problem or opportunity node. Some contexts involve more generic nodes and generalize more easily. Some contexts remain specialized in very specific contexts.

  The relationship between assets and failures for nodes is managed by the context structure. Nodes specify assets that face obstacles that can create problems and opportunities within the process. If the problem and opportunity are active when the node is not the result of a goal conflict between actors instead of the goal of the process and the context asset and fault where the process occurs, the associated asset and fault are Active.

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

  (4) Relationship between goal conflict and cause node: The affected node attributes are similar in a state that may change more and less easily into a group without knowledge of the identified field. Goal conflicts that belong to the same abstracted group are generated by nodes having the abstracted attributes. The relationship between cause and effect between the cause node and the affected node helps to associate the node from one context-specific field to the other.

  Expert user process

  As the overlay expert user gets used to the system's recognition structure, the overlay expert user assigns node attributes at various levels specific to the abstraction context. The overlay expert user then assigns node attributes to a higher level of abstraction. Also, computerized methods for model node attributes may be used to assist expert users.

  Node identification

In the following procedure (shown in FIG. 9), the expert user 920 may proceed to the next procedure in accordance with the present disclosure to identify nodes at various levels of abstraction.
(1) Identify nodes: The expert user of the overlay identifies the nodes found in the context specific process that are searched for similarities with other processes (step 921). ;
(2) Identify the context associated with each node at various levels of abstraction (step 922). This is achieved through a domain (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 the specificity of the context.
(3) Identify lower context level node attributes (step 923). The overlay expert user identifies the node attribute as a node attribute 930, as described above: attribute 931 is a context-specific process goal and conditional goal; goal conflict; context-specific assets and obstacles; Context-specific causes and consequences of the node of the process (similarity between the process and other processes).
(4) Select from a set of abstracted lower context level node attributes (step 924). That is, in the context abstraction stage in the above steps 1 to 3, a selection is made from a set of node attributes fixed in advance. Overlay system 940 presents the user with a selection of higher level node attributes. The expert user selects a higher level attribute to match the attribute of the lower level node identified in step 3;
(5) Select a set of node attributes of higher or highest level context (step 925). The overlay displays a selection of higher or highest context level enterprise node attributes. The expert user selects the highest level attribute that matches the attribute identified in step 3.

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

  Process and node relationships

  Process similarity is identified by comparing higher level abstraction node attributes to context specific process node attributes. For example, in military training exercises, context-specific processes, such as looking at an object, can not be seen because of a node (e.g. Because the scope is dysfunctional and cannot be seen). Subsequently, these can be achieved by expert users of overlays because of the higher level of abstraction (eg, inability to see due to obstacles, inability to see for the environment, and lack of visual enhancement devices). Is not abstractable). The newly abstracted cluster of nodes generates a higher level comprehensive process that is a unique process abstraction when looking at an object.

  However, to match a higher level inclusive process to a lower level context specific process via node attributes, the reverse of abstraction may be performed, which is more inclusive. The process may be performed in the reverse order by selecting specific nodes and their attributes and collating them with context specific nodes in other fields. In this way, two processes in different or similar fields, although in different contexts, can be matched against similarity. This similarity then provides the ability to use experience in the context specific area to predict problems and opportunities in other areas specific to the context.

  Identify similar processes

  In the following procedure (shown in FIG. 10), an expert user may proceed to the next procedure to identify processes in other areas similar to the original process 1070 that are specific to the context.

  (1) According to this procedure, a comprehensive process is first identified as follows: : The context-specific process within an enterprise has its context structure. The context structure is identified and matched against a new area of the process being compared (step 1071). This means that the abstract representation of the selected context is matched across many disciplines, equivalent to the number estimated to work in the overlay system. The context specific node is then identified at the level most specific to the context (step 1072). These context-specific nodes were assigned node attributes 1082 by an overlay expert user using the specific method 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 generates a higher comprehensive process that is an abstraction of the original context specific process (step 1075).

  The process that has the most original nodes abstracted into a higher context is the highest level comprehensive process that is associated with the original process. The generic process is identified iteratively (steps 1076, 1075). A) An expert user gives a name to the process and assigns the process to a comprehensive set of processes, whereby the identification process is performed. B) also an expert to verify 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 attribute. 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 generic process into generic process steps and applies the above process for matching node attributes in these smaller component steps, from that component step The above identification process may be performed by putting it into a larger comprehensive process. However, bringing together a small component step into a large generic process limits the level of generality of the process since the same component step would be required. A method that evaluates the generality of the steps of smaller components is more preferred if the steps cannot be easily changed in mechanical function and in other more fixed processes. For plans where the process steps are not yet defined, a method starting from a more complex process with many component nodes is preferred.

  That is, depending on what the expert user chooses or focuses on, the level of process subdivision (to which the above methods for node attributes and abstraction of node attributes to higher process levels apply) is May change. If the method is applied to a lower level process step (subdivided process step) within a larger process, the goal proximity and the matching of the number of lower processes, Process similarity is directed to a higher level 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 a different method, but the more subdivided method is a better way to compare processes with similar steps and similar goals. It will be the best method.

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

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

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

  (4) Apply a node attribute test (step 1080) to find the context / object cluster that is most sensitive to the selected node. This step requires knowledge of the function of such contexts and objects related to multiple disciplines (usually very similar disciplines) to ascertain their susceptibility to the selected node. . If context-specific obstacles and assets are more important as relevant focus targets, and if the similarity related to the context of multiple nodes in a particular case is more important than process similarity, This step is more important than the previous step. In other words, node selection is a narrow range selection, not a full range of process nodes, but a grouping of a larger number of processes and contexts that have a common node of interest. Also good. For example, many machine faults have case nodes that apply to a particular machine with design, manufacturing, and operational criteria that are susceptible to the same fault. In order to discover these other machines, it is necessary that fewer nodes are selected within the selected comprehensive process, and the expert user has knowledge of the other machines and their influence. Node attributes must be matched based on ease.

  It should be noted that in practice finding similar single nodes related to multiple contexts / multiple domains is just as important as finding clusters of similar nodes. In one form, this problem 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 abstracted at a higher level than the first context. Therefore, the node is not specific to the second context. There will then be two sets of node attributes associated with the node according to the first and second contexts, respectively. Then, in a situation where the generic node has an attribute according to a high context level enterprise node attribute, at least one generic node may be identified.

  Establishing the system in multiple events

  FIG. 11 illustrates a procedure 1180 for anchoring multiple events in the system (results that make it easier to solve a problem by allowing company experience to be collected, or opportunities using overlays Is the result of using The user establishes the system by entering the process, node, goal, and goal proximity (step 1181). These may be entered using the experience of industrial practitioners. Events 1186 are entered into an index story 1185, detailed by an expert and / or recorded by a company, with the help of the index engine 1187. Nodes are problems and opportunities that have been revealed in consideration of causes, results, improvements, and explanations found in events (detailed stories). In this case, it is assumed that the context specific process, context, goal, cause, result, and goal proximity are established.

  Process abstraction: Similarity between contexts

  In the second phase of establishing the system, the overlay expert user will be able to generalize the process and node to allow non-expert users to discover similar processes involving multiple disciplines and multiple contexts. Generalization is applied (step 1182). An expert using indexing assistance from the overlay may match nodes via node attributes to infer process generality and process similarity (step 1183).

  Overlay method steps

  FIG. 12 provides a way for the overlay system to discover problems within the enterprise and past experience associated with the user, i.e. lessons learned from past risks, causes, consequences and improvements (also called stories). 3 is a flowchart illustrating a method.

  The method performed by the overlay is related to building a framework of enterprise importance. Corporate goals (as described above, corporate goals and main goals) are established in step 901. Various processes designed to achieve these goals are established at step 902. Process impact (goal proximity) is established in step 903. In step 904, problems, opportunities, and events related to the process are identified. In step 905, a framework of enterprise importance is built according to the description of the process; problems; opportunities; events affecting the process; causes, consequences, risks, and improvements; and how the processes affect each other.

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

  The process is analyzed to identify process generalization and, as a result, to identify a generic process (step 906). In step 907, generic nodes and unique themes are identified from the process. Corporate internal content and corporate data are scanned, and the scanned content is indexed to corporate criticality using an index engine (step 908). In a predetermined process, the system determines the impact of the predetermined problem and sends a description of the problem to the user most interested in the problem (steps 909-910). The system focuses on user cooperation on issues, the causes of the issues, and important matters that are affected by the improvement of the issues, and proceeds to coordinate the structure according to the framework of points of importance (step 911). The system retrieves related past experiences from the indexed information and outputs the relevant stories of them (problem, cause of problem, improvement of problem) to the user (step 912).

  Solving problems using overlays

  A method for solving problems from the user's perspective using overlay (or taking advantage of, determining, answering questions) is illustrated in the connected flow charts shown in FIGS. 13A and 13B.

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

  A user handling a problem (opportunity, decision, or question) 1001 first creates an outline of a temporary plan in the user's own mind regarding the problem to be solved (step 1010). The provisional plan is devised outside the system. In the corresponding system action (step 1020), the user is allowed to select several generic processes that the plan organizes. By including a combination of minor word searches retrieved with a pre-set search in a generic process or goal, these processes are output in various ways. That is, to provide a search for the basic concept of the recognition structure. In general, the selection of processes within a narrow range is more specific to the process than the selection of processes that are the goal search results, and is narrower than the selection of processes that are the search results of the comprehensive process. There is a wide range compared to process selection, which is a search result of a specific process.

  In step 1011, the user selects a narrow range of process combinations to select a goal corresponding to the process output by the system, and the system generates an initial hierarchy of goals (step 1021). The goal hierarchy is modified to take into account how actors 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 problems and opportunities are known, how well established, how well the process of action for improvement is well known and how well established) Within the selected process, the goal conflict and hierarchy will be the same.

  In step 1013, the user retrieves a unique node from the selected process (ie, the selected process within the outlined plan). The corresponding system action (step 1023) is to search for a unique process for the set of processes. The user uses the unique process to highlight the relevant 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 finding groups associated with the process, depending on the commonality of the nodes and the goal proximity related to the process (steps 1015-1025).

  If the user collects past experiences and recalls the user's own experience through stories (problems, opportunities, and interests / content related to unexpected events), the system will result Help the user readjust the goal and goal hierarchy and highlight the goal conflict (steps 1016, 1026) so that the process can best find the goal hierarchy and the goal conflict.

  Using the output story, the user creates and tests a temporary solution (step 1017). The user then selects additional processes, modifies the outlined plan, and tests the revised plan (steps 1018, 1019). In a common review document managed by overlay, the plan does not need to be maintained in the system other than those described in a review with colleagues. If there is an advantage in retaining the plan, the plan may be retained. For example, if the experience is thought to be useful for future reference, the plan has a better hierarchy of goals compared to the standard process to be replaced in some circumstances In some cases, the plan may be retained. The searched stories help the user gather practical experience and come up with the most feasible plan. Overlay assists in searching past experiences through stories and helps the right stakeholders work together when considering.

  Overlay system

  The system that performs the overlay includes an index structure (or index engine) that defines how to achieve relationships between nodes or enterprise critical points. The index structure includes word patterns and data patterns that include business objects associated with nodes or company critical points. The system also includes a language parser and scanner that is used to scan existing or new content and to assign the content to process nodes. Overlay index structures help users find information related to company critical points more effectively than using conventional search engines.

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

  The overlay implementation according to this embodiment is shown systematically in FIG. The overlay includes a content scanner 1101 for scanning external relation data including corporate content, corporate data, and business objects, a language parsing device 1120, and an index engine 1150. The scanner obtains content from various sources, for example, e-mail 1102, document 1103, application data including business objects 1104, and web content 1105. The language parser 1120 works with the index engine 1150 to identify concepts in 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 that the overlay searches for specific data at a specific location within the application. The output importance index 1160 supports the range of the user interface 1170. The user interface uses the importance index to alert users to problems, allows users to collaborate, and restricts the information passed to the process for interested users (if Whereas, even if the information is only directly related to the underlying processes for users who are not interested parties, the relevant past experience is retrieved. In the form shown, the user interface includes a web-based search interface 1171, a web-based collaboration tool 1172, a portal-based interface 1173 for application integration, mobile alerts for problem-related alerts, collaboration, and search. An interface 1174 and an interface 1175 for integrating the importance index into one or more desired office applications.

  The index engine uses the index model 1130 to index information on important points of the company. The index model is constructed using a history of events (story of how a company has handled important points in the past) 1106 and current problem solving events 1107 within the company. Thus, both current and past events are used to establish the system. By analyzing the current events, the events for the recognition structure are indexed. If the separated process is not directly part of the solution to the company problem, past events are entered as experience.

  Furthermore, when the system is established, the index engine refers to the contexts mutually. It uses a comprehensive view of processes from previously established disciplines, and inclusive nodes, allowing the system to settle in new disciplines, with word concepts related to experience and content. You can do that. A context specific node defines a more comprehensive node. These more generic nodes then define generic process components that are specific to the content / field. These generic process components, and their generic nodes, will exist at several levels of generality in the new domain, and as a result, nodes specific to this different context / domain. Will show.

  Index to other software products, including third-party products such as content management systems, search solution products, ERP (Enterprise Resource Planning) systems, or other systems that may benefit from the addition of criticality 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 the content associated with the node;
Understand the enterprise by associating nodes with each other in the cognitive structure;
Solve problems in the enterprise;
Discover information that protrudes within the company.

Some advantages of using an overlay system are as follows.
Assess the process similarity between the two processes being compared;
Describe the processes and plans associated with the enterprise;
Discover relevant information about problems and opportunities;
Find outflowing 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 to improve on problems and opportunities;
Make strategic plans for problems and opportunities;
Give users insight into the causes and consequences in the industry;
Allow users to be creative in dealing with problems and opportunities;
Help users in explaining complex phenomena related to the company's business or in an environment where the company is active and has a huge impact on the company;
Helping experts to help the company in solving problems or taking advantage of opportunities for the company;
Discover relationships between cognitive structure elements based on business activity.

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

  Referring to FIG. 16, system 1200 includes a function 1202 that adjusts a plurality of user interfaces 1204a-1204e to reflect each user's associated current state of a live event. This means that only the part of the set of mutually associated nodes 1206 among the nodes selected by the context that associates the user with the current state of the user is presented to each user. Each user interface 1204a-1204e has a display 1208a-1208e having a limited display area. If all the nodes 1206 are displayed in the restricted display areas 1208a-1208e, the displayed nodes will be too small for display or interaction by the user. In addition, 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 a display space for information related to the current latest state becomes large. . However, since all nodes 1206 are related by cause, effect, and similarity, the user can reverse the above if required to display any node assigned to the stakeholder. You may process a procedure.

  The function (facility) 1202 adjusts the user interface to be focused on the node most relevant to the user / stakeholder, and the user / stakeholder according to the progress of the situation related to the user / stakeholder. You may change the combination of the nodes most relevant to the parties concerned. The system may change the display of the user interfaces 1024a-1024e so that the display space for information related to the latest state associated with the user / stakeholder is increased. However, regardless of the current focus content shown on the screen, all nodes associated with the user are accessible at the discretion of the user.

  Function 1202 is accessible through the node 1206 and is used to confirm that the information held therein is current, and to confirm that the status of each user 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 a light detector, for recognizing a fire detector or moisture detector to recognize pipe leaks or pipe ruptures. 1212 may be sufficient. Further, the function 1202 may remain connected to the remote site 1214 via the Internet 1216. Such remote sites can include other departments of the enterprise, external databases (eg, administrative sites for building plans or access to wiring diagrams), public databases (eg, search engines), and private It may include, but is not limited to, a database (eg, connection diagrams for equipment parts available from the builder or manufacturer, or for ships).

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

  The 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 interfaces 1204a to 1204e. Any communication format may be used, such as a cellular network 1222, a wireless local network, or the Internet 1216. It is beneficial to instantiate node 1206 not only from changes in the information underlying the database, but also through direct user input to user interfaces 1204a-1204e controlled by the overlay. This is treated as information in a database or other computerized function to be processed by a scanner, etc., but the information will be entered via a user interface controlled by the overlay. . This information may be a simple selection of the node 1206 formed by the user interface or a user instantiation action option related to the content entered by the node 1206 and / or the user. Information such as images and video is made available via functions 1202 displayed on the mobile device displays 1208a-1208e or via 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 interrelation node 1206, and the data in the database 1224 exist as middleware services. This middleware service allows logic / code modifications and database 1224 modifications and node 1206 modifications without requiring any programmatic changes to the user interface 1204.

  Overlays involve a combination of interrelated nodes that are connected by cause, effect, and similarity. Also, the cause and result can be determined by a formula and by the relationship between characteristics related to the node. In conventional programming, changes are made to relationships and changes to data representing problems and opportunities. After these changes are made, a new user interface needs to be designed to present these new relationships to the user. This embodiment avoids performing the second programming.

  The encoded relationship 1226 between nodes 1206 can be clarified. And if you draw the cause and the result, and draw the influence and the cause, then program the code / logic that changes in the node and in the formula to which they connect, all the nodes When connected to other nodes, the code / logic is programmed without changing the relationship of information provided in the user interface in another example. System 1200 builds database 1224. In the database 1224, each increment of data relates to at least a node 1206, and the relationship from one node 1206 to another node 1206 ′ is described by code / logic related from one node to another node. Is done. The nodes are related to each other by the code / logic of the application that draws the cause and result and draws the cause and result. On the user interface 1204 of the restricted display area display 1208, data from the database 1224 associated with each node 1206, 1206 'is displayed, organized in correspondence with nodes directly linked to each other. These nodes are related to each other by cause and effect and by what is derived from the cause and effect.

  The user interface is a series that is not designed as a program for an ongoing use case. Prior art user interfaces are designed to fit a fixed predetermined use case. For example, there may be a user interface that determines the route to an exit within a fired building by providing a default selection of navigation options. Different user interfaces may be needed for escape from the building and emergency situations such as broken legs inherent in the escape. Different user interfaces will be needed for coordinators who oversee the position status of evacuees. The overlay user interface fits all use cases, including unexpected use cases in the future. This is because the overlay user interface is derived from a continuous node structure that contains the logic of the system and contains future logic. In addition, the logic of the system and the state of each attribute of the system are drawn by cause and effect links between the node and each node of the node, so there are two variables to describe. It is a link between a node and another node. This can be drawn graphically in a topographical map similar to a vector map. However, just having two variables, a node with links to other nodes and the ability to expand or collapse child nodes from the parent node, allows this topographic drawing and increases or decreases the number of nodes. That is displayed on the user interface to which the user is associated with zoom out to understand the situation and zoom in to focus on specific nodes and related information. Currently, a group of processes regardless of whether the processes are sequential and whether they are related to each other and how many processes are being drawn. There is currently no user interface for drawing. That is, you can navigate from one of thousands of node choices to focus on one of the lowest lowest nodes, and choose any of the nodes between these external ones There is currently no graphical user interface that can be navigated from and so on with continuous drawing.

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

  This is in contrast to prior art enterprise process drawing user interface software, which requires each user interface to be detailed or predetermined 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 enlarged or reduced by zooming in and out. However, this method does not have the ability to present a process. This is because display in an electronic map is not used to draw processes and relationships between processes, but is used to draw positions and distances in two dimensions. . On the other hand, in the overlay, the empty space is used to draw the cause and effect links and processes. That is, nodes draw problems and opportunities, links draw causes and results of linking nodes, and empty parts are used to indicate subordinates or subordinates. The salient feature to achieve this is that the process and representative nodes converge. That is, the child nodes are folded into the parent node, so that the child nodes fit each other when zoomed out. Flowcharts and similar process block diagrams are used to draw processes from small to large enterprise systems. However, the flowchart draws sequential processes and branches that do not fit each other so that they can zoom 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 failures affect company reputation? And in that case, is the sequence important, or is the cause and effect important? How does misalignment of ball bearings affect the structural integrity of the machine? How can a sequential step flow chart help to draw this? A link between two unlinked processes in the sequence can be connected on 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 include an obvious cause and effect relationship between nodes that are also computer readable and process nodes that also converge. They also fit together to allow zoom out in graphical drawing. Also, when they are required by the scope of the drawing system for which they are designed, they fully depict the relationship between process problems or opportunities and other process problems or opportunities.

  In other words, the prior art composite flowchart is not a mere process flow, but attempts to draw process relationships, but cannot provide convergent nodes. As such, the detailed process converges to a clear parent process and can be converged to a complete cause and effect relationship between nodes that are computer readable and processable by the computer. Thus, when drawing interrelated enterprise processes in the user interface, these prior art composite flowcharts show the process but not the degree of association 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 is statistically defined by the community to which the user belongs. On the other hand, as described in this disclosure, in an overlay, the relationship between cause and effect is empirically drawn, either by goal proximity or an algorithm, if there is a clear quantitative relationship. The Both goal proximity and relevance algorithms that draw causes and results are computer readable and can draw the importance of relationships. Statistically, drawn relationships are computer readable. However, if the result is a result of aggregation that is not completely independent and the dependency of the result, the statistical sample is a result of aggregation having a completely different cause. So, if the cause and effect are ambiguous, or if the statistical sample is insufficient for the statistically derived significant relevance, then the drawn relevance is Inevitably not accurate.

  For example, a ship collision that has been statistically analyzed and assigned to an artificial factor such as a human error is not meaningful enough. Because all technical aspects of marine transportation that could cause collisions, such as steering mechanism failures, are also man-made factors such as machine design, manufacturing, maintenance, operational complexity, etc. It is because it accompanies. For undefined relationships or statistically related nodes as shown in the prior art, the user interface will be cumbersome with relationships between undefined or statistically derived nodes. For example, in an emergency situation, the relationship is disruptive and the purpose of the application, which is entirely computerized, is to respond to the emergency situation that should provide information related to minimal damage. Would be practically useless.

  In another method of the prior art, which is a graphical two-dimensional drawing used for formal risk assessment, commonly referred to as a “bow tie” block diagram, the relationship between “failure mode or danger” and the process is the node It is drawn by connecting the statistical possibilities between and "severity". However, since there are “failure mode or danger” and “process”, “goal”, and their links, and there are many “conditions” and other variables, the elements do not converge. In the overlay, “risk”, “danger”, “failure”, and “result” do not converge so that process nodes converge. For example, in an emergency situation, such a conventional “bowtie” drawing will not show the entire situation. Although it will represent failure nodes and dangers, the user may contribute to other processes that are affected by the dangers drawn in the bowtie block diagram, or the results shown in the bowtie block diagram. Or what if you want to focus on other processes? How are they connected? The bow tie block diagram shows what is logically derived in relation to the combination of the affected process and the risk of the cause and the focused process or risk only in the best state. There is no idea to show how all the processes in the enterprise are connected. Therefore, in an emergency situation, if the user needs to view other processes that correspond to the stakeholder, or if the system helps focus on the latest event, it will be discontinuous. You have to do another graphical drawing that is different from the previous graphical drawing. Thus, the graphical drawing is discontinuous and cannot be used for zooming in and out (requiring continuity). Subsequently, this means that not pre-designing the user interface for each process, or use case, or user / system interaction point, any process in the system, and any future This leads to the inability to draw the process.

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

  In part, the above serves to explain:

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

  As a source of information to manage event triggers with respect to problems and opportunities and interests or unexpected events, or important monitoring elements lost and relevant information that improves user decisions, One way to enhance business understanding is to reduce the time to strengthen the underlying enterprise system and sometimes replace it.

  The reason for strengthening or replacing these underlying enterprise applications is that these systems are old and past, so they are ergonomically designed and thus make it efficient to function overlays. The reason is that it is rarely updated with the times to provide correct triggers and related information.

  Replace these enterprise applications for overlay without much effort in building applications, such as understanding past code, maintaining past code, or improving past code To do so, it is necessary to utilize the core innovation part of the overlay to enhance or replace past systems. That is, this is to facilitate the creation of a supplemental corporate information system when required.

  An important objective is not to rely on traditional software development methods, and as a result, business experts, so-called stakeholder and experts, do not require much traditional application building methods. It is possible to build and to supplement or create these systems. This increases the likelihood that the resulting system will be beneficial, and increases the likelihood that the system will be built and speeded up to accommodate new and urgent demands.

  System-based overlay operations are partly driven by the node structure and partly by traditional data structures in the underlying enterprise application. Those aspects of the system that operate with the node structure generally involved in the navigation of the system and the relationship between nodes, i.e. the discovery of relevance information for users within the enterprise, are very flexible. Those aspects of the system that require the creation and interaction of business objects, generally operating on traditional code in the underlying application, change the evaluation of the business model as defined by domain 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 of purpose and suitability of the underlying past application.

  The following section discloses a form of overlay concept that understands all the operations of the system operated by the newly extended node structure by removing the need for traditional code. Thus, conceptually speaking, the business model becomes the code of the application. This makes it possible to achieve the above general purpose in the overlay system.

  In prior art and past systems, the business model may be made to operate according to the business model, i.e. it may be moved between transaction tasks, may be accessed via a navigation filter, etc. As a function. In general, these business models represent a set of related attributes that model simple data packages, ie, real-world objects and concepts, such as people or documents. It corresponds to these business models currently implemented using traditional code. These business models include attributes and relationships with other objects drawn from many use cases. It seems to be a home repair tool with accessories to suit a number of home repairs. However, the relationship is more ordered than home repair tools. And, for the diversity of users of the business model, which is almost equivalent to the diversity of using modern smartphones and modern computers, attributes and relationships to other business objects It is cumbersome and difficult for the designer to understand and manage.

  For example, packaging attributes into business objects is the fact that these attributes and their values tend to be determined by a complex underlying process, and software engineers are commonly used during system development. Is subject to rules and restrictions that are not noticed and that span companies (and indeed within other companies).

  For example, in a spare purchase order, a single item is selected.

  Part number: The method by which the part is described is probably due to a complex process of going back to the original manufacturing process.

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

  Required by date: This also relates to resource availability, device accessibility, and how and when the device is used.

  Scheduled delivery date: This relates to the availability of the supply personnel, which relates to the personal and professional requirements of the subject personnel to prepare the order for delivery.

  In short, a simple business object for an item in a purchase order would traditionally obtain only a portion of the above. However, mapping the above items to the complicated cause and effect node structure is essential for realizing an effective business process support system. This can be easily extended by supporting useful decisions and extending the node structure.

  It is especially important to be a challenge when the “ideal” business process is not followed, that is, how exceptions are handled. For example, if a part is not delivered on time, the next action to be taken is the risk assessment and the expected reliability of the equipment, allowing reduction of the selected action 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 requirements of different companies. Here, the different companies inherently tend to have different interpretations and usage patterns with respect to the business objects. In practice, the business object implementation encapsulates the business logic, which should be in the model, not in the code. And in that the business model can control how the business object behaves, the business logic is hardly developed in a way that is visible to the business model.

  Therefore, the standard idea is to remove the idea of business objects as a fixed concept, not to adopt attributes as very small primitive concepts. In effect, this replaces the concept of business objects based on the node structure of nodes that are interrelated by clearly described computer-readable causes and consequences, or by derivation or transformation from causes and consequences. New and very dynamic types of data display can be revealed in computer readable logic, in different transformation logic, and in other user interface logic that is guaranteed by known prior art systems Would be.

  As is evident by the interrelated node structure, this improved idea of overlay / TA system is a clear combination of process models with data models defined as attributes. This of data with interrelated nodes connected by cause and effect, i.e. data with 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 critical transformation logic that can be read by the host computer and for critical user interface attributes without special programming skills. This is in contrast to traditional data structures such as a relational database. Here, the traditional data structure is what the data is for (i.e., the goals it supports) are not explicitly expressed and in order to derive a preferred user interface Points that have not been determined to be required. Traditionally, it is information that is hidden and fixed as a result of being embedded in the code. In addition, it enables experts in real-world processes and computerized transaction processes to understand all computerized processes in enterprise applications and extend them 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 overlay is that all transformation logic is in the cause-result link between nodes. It is. And the unique concept of the overlay does not require any other logic to affect either application conversion or user interface attributes. There may be logic external to the node structure that is required for supplementary services, but no business logic of the enterprise or attribute display of the user interface is required at all outside the node structure.

  In general, modern information systems are understood as multiple layers, each layer performing a specific type of function and serving 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 that is presented to the user of the system, and the entire layer is derived from the business model.

  Business logic layer or “intermediate” layer. This layer defines a representation of how the user and the organization should be supported within the scope required by the user and the organization to meet the user and organization goals. It consists of a business model that operates in an implementation framework that is an overlay.

Data management layer; this layer facilitates the storage of state information, again the whole layer is derived from the business model.
Business logic layer

  As described above, this layer is composed of two basic elements that are a business model and an implementation framework on which the business model is executed. Business models are created and managed by non-software engineers, and traditional programming languages and database knowledge will not be required. Thus, the business model will define everything that is required to derive important information systems, ie those that support the organization in meeting its objectives. Thus, the important part of the difficulty remains too vague to handle the underlying implementation framework and too vague to provide a predictable, useful and usable final result. To support the definition of models that are easily understandable for non-technical people.

At the heart of the overlay business model is the node. It is an important point for businesses where operators, sensors or other system agents need to determine and provide input, i.e. state changes. Or it is an important point for the enterprise when the user needs to be aware of something by the system. At a high level, the collection of these nodes defines the organization's process model, and when the organization's process model is combined with the underlying state model, the users required to support each enterprise critical point. Sufficient information should be provided to derive the interface. Elements of the process model can be mapped to a higher comprehensive process abstraction within the parent process model (master process model). The applicant will now describe 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. There are other types of relationships, as outlined below, but basically a node is related to other nodes as a cause and a result.

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

  A node relates to a set of attributes linked to the node in the “node cluster” of the node. A node cluster is a collection of related nodes that are typically related to processes and other reasons. The node cluster is clearly defined by an expert in the field of creating a model. Each node is designated as either input (read-only) or output (read-write). A set of attributes for a node is referred to as a “description pattern” for that node.

  Basically, a node is stateless in that it consumes or generates a class of attributes. In other words, there is no concept of node instantiation. Instead, the node becomes interested as a result of the state of the 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 to be executed. Typically, this state change is the result of a request from an action associated with the cause node.

In addition, a node is related to another node as belonging to the same related area, that is, as a task in an organized task grouping. The organizational relationship does not necessarily imply that it is a member of the same node cluster due to direct causes and consequences. 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 does not have cause and effect links to the process that the node organizes or to other processes. This is how such an organizational node is affected by the nodes that the organizational node organizes, or how the organizational node affects other nodes. This is because it is unclear. That is, if a person asks how to "acquire" fails, and when at risk, when to "acquire", the answer is unclear. Similarly, if a person asks 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 impact that onboard repairs can be performed. So nodes organized by those nodes have normal cause and effect links to other nodes, while organizational nodes like "acquire" are for navigation purposes. Is.
Business logic layer: State model

  This is where data is stored to allow users to share information and to allow the system to “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 value for that attribute.

  The attribute value of the state model may include a link to a further attribute value in the model via a node in order to show the relationship. For example, age and name attributes may be linked to employee ID attributes to collectively represent employees. And this may be represented in a node cluster. At the class level, the types of relationships that exist are typically drawn from the process model (node cluster) as a result of an attribute that is part of the same cluster serving a larger emulated process or parent node. .

  Here, an important mechanism is the context component of the overlay interface. The attributes used for context filtering, i.e. navigation of the system using key identifiers, become "key" attributes. Key attributes are the primary navigation method when many similar processes are distinguished by their cause and effect by a key identifier, and many related but different process steps use the same key identification. Form. For example, if an employee's name is defined as a key attribute, and each of the employee's age attributes forms two nodes in a large cluster that identifies an employee, the system Names and employee age attributes can be linked. If you have more than one employee and the process steps are the same for all employees, and you want to handle key details and system navigation when handling details about the employee The use of key attributes helps to clarify the focus on the right employee.

This method of state management represents a major branch point from conventional systems. Here, an idiomatic system is one that is necessary to complete the current process from the data model by removing all domain-specific knowledge and having that knowledge drawn from the process model. In a new design that affects the system's ability to accurately present the system, we will help avoid potential transformations that would prevail in information systems design assumptions. is there.
Business logic layer: Master process model

  An executable node instantiates a node class (abstracted node cluster that renders an abstracted process) defined by the parent process model, and the node class (abstracted process) Related to the abstract node cluster). As an abstract version of a domain-specific node, the node class obtains the common elements in the domain-specific node. For example, a node class may cover concepts such as planning, checking, agreeing, warnings, etc. An abstracted node class represents a concept that can also be understood by a “cave man” in the first abstraction we can understand as humans.

Abstracted node classes serve two main purposes. First, when thinking about how to model a domain-specific event, for example, by reminding a business domain expert what events need to be considered, or By helping the work to understand the work individually, the abstracted node classes serve as guidance for the business domain expert. Second, abstracted node classes accelerate the modeling process by facilitating reuse and by allowing rapid identification of similar processes related to multidisciplinary models. . However, reuse may not be a copy-and-paste of generic code components, 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 abstraction or class level clusters using a suitable coding language that can be transformed without adopting a domain / use case level. However, linking a domain cluster to a node class (abstracted cluster) is very obvious and as a result, improving the logic to the domain / use case level relative to the cascade class level Is very clear.
User interface layer

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

  Existing prior art uses a business object as one of the basic concepts among the concepts involving UI. That is, the user creates a business object and outputs a display of the business object in order to display the content and change the content when necessary. In the method of the present disclosure, the overlay understands the fundamental change in the way that the basic interaction UI concept becomes the node itself. The user expands the node UI to display the required information for executing the process and obtaining information for state model updates.

  Basically, the node UI presents input attributes and output attributes of a target node and peripheral nodes, that is, a 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 necessary and are defined by the process model as described above.

  The number of attribute values present defines the display format 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 adopted appropriately. The attribute may be highlighted as a key attribute for the node, and the node may also affect how the attribute is presented on the node display screen.

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

  Similar to determining which attributes are relevant, the relationship between causes and effects between nodes also affects how those attributes are presented. For example, it may be visually emphasized according to the attribute that is influenced by the relationship between the cause and the result. The relevance is directly related to the node in question, or directly related to the display of the node cluster, providing a single UI for obtaining relevance between multiple causes and consequences. is there. The platform builds a UI approach that is suitable for decisions or decisions or transactions to be made.

In addition, when a plurality of attributes seem to be necessary for passing 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 machine component is identified as an input attribute, the system may also be considered the name of the associated ship. These key attributes are used to define the display range in the preferred data structure for grid display. In this example, within the process named “data population master setup”, the ship's name node would be followed by a machine component as a sister node to the identification node.
Data management layer

  The data management layer is a layer in the business model that converts the state model into an implementation framework provided by an existing database management system. If necessary, the underlying scheme will become a metamodel to support on-the-fly extensibility, so there is a need for scalability and a formal correlative database structure. The lack of need means that the data is likely to persist as key value pairs. Subsequently, this naturally leads to the use of a NoSQL database system 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 an information system beyond simply presenting data and obtaining input. In the following, a brief discussion will be given of how some further calculations are covered.
Create and delete attributes

As mentioned in the description of the state model, actions that lead 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 needs to be supported by a special hard-coded action type that gets the attribute from the node UI as a parameter. It should also be possible to define destructor functions that contain logic to check the validity of the deletion.
Event handling

It should be possible to define action codes for system and custom events, as well as constructor and destructor events. For example, when a node display screen is opened and displayed, edited, or the like. When a state change occurs, a custom event related to the action code is started. This looks the same as a database trigger, but is expressed in a node structure as a reusable abstract process, even at the 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. It should not be necessary to include this structure with an additional access control layer.
Calculated attributes that are computer readable for cause and effect

This is a core concept that provides computational support to the user. The calculated field is 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 computed field is updated as a result of the action of transitioning from the cause node to the affected node.
System integration

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

  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 to perform the process efficiently. When both systems to be integrated represent a conflict in the representation of the same underlying entity, that is, both systems do not provide the same business object implementation, and neither system is a business object attribute The problem associated with this kind of integration becomes the most difficult when it is not a preferred representation of the entire scenario related to. By subdividing business objects into their underlying attributes, assigning nodes to them, and applying logic to the relationships between nodes, attributes can be matched. This is because the attribute is assigned to the node that renders the same business logic in both systems that is appropriate for integration.

The process integration methodology may look similar to the following method, where conventional code that uses business model objects is transformed into code hosted in the 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 contain the processes to be integrated.
In each application to be integrated, connect an abstracted node to an attribute.
If done correctly, the two sets of attributes (ie, the abstracted set and the set from the application) will be identical. That is, an expected pattern is created for each node in each field, data is placed in the above-described table, and connected to the abstracted node.
Finally, in each of the two applications to be integrated, the data in the expected pattern will be equivalent, although the table relationships and groupings are different. Thus, any goal based on relationships implemented by the application is replaced by the node structure.
As for the expected pattern, collation data is accurately extracted from each database. This is because nodes describe exactly the same data and each database provides a different relationship.

  For simpler tasks of data integration, Applicants look at external systems as actors that “execute” nodes. As a result, as part of the node structure, it defines the data transformations required to pass data to the outside and to accept data (and process the data). In other words, you can look at the external data system that wants the data in a certain (specific) way, exactly as people do. Of course, if the system's capabilities are to accept inputs that do not follow the exact rules (which is why there is no reason why they cannot be entered), then the system's durability tends to be low. However, it will be required to build several platform elements to support different service types, platforms, etc. being able to consider security, but this will be done completely comprehensively .

  Referring to FIG. 15, the above contents may be illustrated. In an emergency situation requiring school evacuation and school blockade, a common goal 1500 is that 100% of students are evacuated and the door is 100% closed. As such, the two processes to be integrated are the door status and the number of students in the school. The two state models to be mapped are “door state” (open or closed) and “number of students currently in” (add 1 when entering (+1), 1 when leaving) (-1) and count students passing through the door). And problems and solutions are abstracted to monitor the status of the door and to count how many students pass when the door is open.

  Node A 1502, node B 1504, node C 1506, and node D 1508 represent a cluster of nodes that include processes to be integrated. The abstracted nodes 1502-1508 are connected to the door state attribute and the student attribute. Each node has a cause-effect relationship associated with the 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 percentage of people (students) at the evacuation meeting place and the percentage of closed doors. The common goal 1500 is achieved when both are 100%.

  When an attribute is identified as part of the process model, the state model is automatically expanded to facilitate storage of values for the attribute. That is, when an attribute is newly defined as part of the process model represented by the expected pattern of the node, the state model stores the value for that attribute programmatically without extending the state support model. Extended to make it easier. In the example of FIG. 15, another 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 program difficulties that can be encountered when trying to build a system on a platform. A set of services can be built to provide computational support based on the best practices established. 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 acquiring data and visualizing tables, graphs, and others. The output of data and the associated display leads to the output of the node. The above advanced data display, ie the data input inserted in this visualization top level interaction, is again achieved based on the full display on the interrelated node structure. The node structure is considered to require user interaction. Therefore, an arbitrary display clearly indicates either a conventional output display resulting from the information processing of the system, or an input dialog for bringing a user's reaction into the output of the display.

  Emergency response. Occasionally situations arise where the priority of the stakeholder goal and, as a result, the connection between the input and output relevance nodes changes suddenly. For example, if an emergency occurs (eg, a factory floor is destroyed by a fire), the goal hierarchy changes and a new emergency overlay node network applies. Highest level goals are implemented that minimize damage and allow personnel to evacuate safely compared to pre-emergency situations that emphasize normal corporate goals And the relevance between processes to follow and all of the stakeholders change. As a first example, the role of the administrative assistant may change from inputting data to storing data contained in a company database. As a second example, the role of the maintenance worker may change from removing power from the device to maintaining the device under good operating conditions. As a third example, the role of the merchant may change from contacting the potential customer over the phone to notifying the crisis manager and managing the safe evacuation of the equipment.

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

  The emergency response requires the first user, who is not the business participant, to enter information regarding the progress of the emergency as seen by the parties. The emergency response also requires a temporary user who will work (function) as a corporate employee in response to the emergency.

  Emergency situations require coordinated management. Referring to FIG. 17, in the prior art of emergency management linked in the core part, information of a person who is not a company participant was used, but the information was handled via a person who received a telephone call. Members of the organization 1230 (preferably those who are safety experts, but may not be such depending on the scope and timing of the emergency) include fire station 1232, police station 1234, medical personnel 1236, environmental protection agency Keep in touch with someone who is not one or more company participants, such as 1238. The member 1230 is then responsible for distributing this information to the other members 1240a-1240e of the organization.

  Prior art models have many shortcomings. In an emergency situation, many companies cannot afford to have a call center waiting to receive calls and an experienced level of users. Here, an experienced level of people refers to those who can interpret the information and distribute the information to users in the enterprise that use the information to act and make decisions. Member 1230 has received information from non-company participants 1232, 1234, 1236, 1238, who may not contact each other and give conflicting advice It may be people. The member is responsible for disseminating appropriate information to multiple members of the companies 1240a-1240e, and each of the members may be interested in different during an emergency and May change in the environment. Further, members of companies 1240d, 1240e may contact each other 1242, and as a result, it may be neglected to pay attention to orders from member 1230. Member 1230 may need to terminate communication due to an emergency or because of a battery shortage on the mobile phone. Clearly, prior art systems are not suitable for serious emergencies in large companies. Furthermore, it is clear that a system is needed to obtain information, to interpret the information, and to redistribute the information to the decision makers and participants who need the information.

  Referring to FIG. 18, corporate responders 1204a, 1204b, 1204c, 1204d, and 1204e, as well as persons 1232, 1234, 1236, and 1238, who are not bystanders or corporate staff, pass through the local telephone network and the local wireless network With the addition of a mobile phone that can use a mobile device to access the Internet, the first user or a temporary user can participate in an emergency response. They can enter information from an unexpected set of choices. The computer processor can then decide how to automatically distribute information to interested groups. An emergency is usually a situation that requires a combination of actions for a small number of improvements, so a combination of many choices at a time is not necessary.

  In an emergency situation, each business participant or a person who is not each business participant has a small combination of activities and experience that require communication with others. Thus, the novice user has several options through the system, so the novice user can easily select the system action. If a mobile device that works with an inexperienced user provides the user with many choices regarding information or responses, the mobile device is not useful. In order to provide a small number of alternative combinations, the system needs to be aware of the situation.

  In order to design a limited choice system, it is necessary to accurately emulate the current situation. For example, in a variety of hazards related to things like fire, storms, intruders, and various types of physical environments, a common emergency action is evacuation. Many emergency response plans cover one or more of these for all businesses.

In order to build an emergency response application for mobile devices, the following features are required:
Central application for function control.
In the central control process, the type of emergency must be specified.
Users in the enterprise must be provided with an appropriate interface for the current emergency situation. Because users in the enterprise perform different activities in any emergency, they must be able to access different combinations of application interfaces for each special thing in each emergency. If an emergency grows in steps or branches, or otherwise changes, users within the enterprise must be given a focused but different 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.
Those who are not users in the enterprise must be given an appropriate user interface, depending on their situation and usually their whereabouts.
When users in the enterprise or those who are not enterprise users have to rely on responding with text messages, they are parsed at the core of the system and are the right stakeholder for decisions or activities. Must be delivered. The system will need to assign SMS (Short Message Service) messages to enterprise critical points.

  In order to achieve the above, the application will need to anticipate all the activities and decisions of the participants in the emergency scenario, their combination, and their variations. A system suitable for emergency response 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 gets an appropriate user interface through an emergency situation.

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

  Referring to FIG. 19, a portion of function 1202 is illustrated. Node 1206 is important 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 problem site 1258, number of people arriving at safe locations 1260, number of uncounted people 1262, local emergency device 1264, exit location 1266, etc. Have a common node. Some nodes may have sub-nodes, for example, the number of people arriving at a secure location corresponds to each person's medical status sub-node, node 1268, and each person's medical status May have corresponding sub-attributes in the state model.

  A display screen 1208 of a person who is not a company employee such as the fire department 1232 or the medical institution 1236 displays different information to be used for the employee. For example, the fire department displays attributes such as the type of emergency (fire 1252), location 1258, and number 1262 of uncounted people. No other information is displayed so that the information related to the fire department can be made large enough to display beneficially on a small screen. The display may be scrolled so that other information, such as location or exit 1266, is centered on the display 1208. Also, a limited number of user input nodes 1270 are displayed, such as “Are specialized devices required?”. Referring to FIGS. 18 and 19, if the answer to the user's input query is “yes”, an idea that the fire is essentially chemical is sent to the system. Is done. The system may then access a corporate database to determine 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 professional 1236 also understands that the emergency is fire 1252, but location 1258 may be less relevant than the number 1260 of people in a safe location and their health status 1268. You may do it. The health care worker may also scroll to other nodes and attributes, for example knowing the number 1262 of uncounted people is a query whether additional medical equipment may be needed locally. It may help answer 1270 '.

  An emergency situation results in a strong user interest and possibly agility within a limited range.

  The screen size is very small and alphanumeric and touch screen keyboards are physically very small.

  In an emergency situation, it is necessary for the system to communicate with the user, and for the user to accomplish the situation specific needs to send and receive information. It is necessary to communicate with the system and each other's users. The information to be received or transmitted is specific to the situation and / or specific to the recognized user.

  Situation-specific nodes relate to users who are recognized in need in an emergency situation. The relationship is via cause and effect and is a sequential process. Causes and consequences concentrate on the associated nodes. Instantiating a situation with another stakeholder or sensor allows it to be directed to a new alert in a situation where the user's attention is ongoing. When necessary, sequential nodes allow transactions (ie user input) to follow the sequence. It may also be necessary to report that the sequence is not a transaction and indicates a sequential state. For example, counting the number of students, another example is an administrator following a sequence that authorizes the publication of a situation that expands or contracts in stages.

  Therefore, the system will: A) a new situation that instantiates the nodes associated with the user via causes and consequences, B) the recent users who selected the nodes, and the sequential nodes, causes and The results must show those related nodes, C) nodes that depict the maximum risk and severity for the stakeholder.

  In a restricted display screen with each role associated with a significant number of nodes. It may be impossible to display all the nodes on the screen without displaying small nodes so that they are not clearly visible and cannot be navigated, especially in emergency situations. Thus, the three options to focus on are: A) recent situation related to the current node, B) the node that the user is currently playing or that the user may want to output, and C) the stakeholder. A node that draws the maximum risk and severity for.

  The user can navigate to other remote nodes according to another user whose need is recognized.

  In order to synchronize the aircraft control panel, the control panel must be responsible for all the risks related to the latest potential emergency for the role / user, the causes and consequences for the latest potential emergency risk node. It will display the node, the last node of attention to the user / role, the highest risk and severity node for the stakeholder.

  A similar example for a portable device is a conversation during an emergency situation where it is difficult to convey sound. If the conversation is not related to an emergency that is currently occurring, or not related to a new conversation about the emergency or the most important thing about the emergency and a particular participant The person who listens to the conversation will not join the conversation while panicked by an emergency.

To be flexible, such a system requires the use of the following elements: :
Important points of the company;
Relationships between important corporate points;
Stakeholders in the company important points;
Input from the user;
Scanning enterprise systems to discover information related to nodes;
Performing language parsing of enterprise systems to discover information related to nodes;
A context that allows users to select options for contexts that are difficult to select in an emergency.

  Without taking into account the relationships between enterprise critical points, the system would need to maintain pre-specified role task relationships and pre-specified task trees. To change to a branch of the current scenario, the central control process would be to provide a modified task tree for each profiled user.

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

  In the absence of a relationship between tasks, there will be multiple 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 key points, the number of user interfaces will be reduced to one large connected user interface that can focus on any instantiated key point. As a result, the user will see the nodes around the important points that have been instantiated and selected by the context applied to them. That is, the system reduces each user's (existence) exposure at the interface, depending on the state and context, and the stakeholder's stakeholder. State instantiation is selected by the designated user or automatically by the system.

  In order to retrieve information for the field and deliver it to the correct user for activity and decision purposes, the system must expect that information and pre-plan it to present it to the user. It is necessary to have an improved method. This is possible using prior art software and hardware applications.

  A hindrance in design is getting the right user interface for each user and environment. The following paragraphs describe some alternatives in the prior art.

  Determines the direction of physical objects relative to input items. For example, determining the orientation of a physical object is navigating the system by first selecting from a physical location choice or a choice of people in need of evacuation. If there are only a few physical object options, and the physical object is important to show relevant information, the direction of the physical object in the navigation user interface Can be determined. However, if there are many objects to choose from by each user, it may be further required to have complex navigation. For example, suppose that there are five buildings and various places in the building for evacuation at school. Evacuation is a place (thing related) and, as a result, objects are involved, so there can be evacuation information based on buildings as determining the direction of an object. There are also other objects related to emergencies, such as school students. However, depending on the time of day, there are many different students for each class. Discover information based on students or buildings, as many types of information are not easily related to these two physical objects, such as information on the type of injury and information related to situations such as weather or breathing problems It will be difficult to navigate the system to do so.

  Determine the direction of business objects to display related objects. Determining the direction of navigation of a business object may be, for example, via a safety instruction document. Because there are too many process steps in many processes, there will be too many choices per user, so displaying a drawing of a business object such as an associated instruction document to the user is a problem. Since there is information such as instructions in the case of panic, instructions in the case of injury, medical records of personnel, alternative exit routes based on location, it is difficult to determine the direction of the business object. In order to present the correct object to the user's attention, instantiation of the current process and selection of several objects are required. This requires a process related to the object. Doing this without a model is very inconsistent and difficult in software development and maintenance. Each object must have code written for it to be output to the correct 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 complicated to navigate the system. will do.

  Representing a user assigned to a node and context pair. It is likely that the personnel available in an emergency situation may not be users who respond to the system's default expectations, as is the case with normal corporate software system users. Thus, changes to the user's access may be required at the start and when an emergency is occurring. This can be done on the fly as the situation progresses, only with the overlay model of the present disclosure or with a number of programmatically pre-designed interfaces. Since there will be a lot with expansion, a number of programmatically predefined interfaces must be assigned for correct use and for the current ongoing situation. This is a huge task in the design and implementation phase of a determined model task for an emergency response application, and is a fairly difficult task during an emergency. there will be. And without the multiple interfaces programmatically pre-designed for the current situation and instantiation for development in an emergency situation, navigation to the correct object is very difficult on mobile devices. It would have a low affinity.

  SMS message used to coordinate emergency situations. If SMS messages are sent from the field, they will need to be interpreted and a central system for assigning words to nodes will be required. Interpreting the SMS message will require assigning a linguistically appropriate expected pattern to the node. An alternative is to have a team of people that adjust the SMS message channel from the source to where it needs to be determined.

  Accordingly, it is desirable for emergency response applications to utilize an overlay continuous user interface. The user interface can be realized by a corporate model that is revealed by connected nodes by cause and effect. Furthermore, the user interface can be realized by being able to instantiate a part of the user interface for a new warning. In addition, the user interface can be output by allowing the user to output a past node to be focused or by allowing the user to output a new area to be focused related to the user / stakeholder. Can be realized.

  Although the present disclosure has been described in terms of specific forms, it is apparent in view of the above description that numerous alternatives, numerous modifications, and numerous variations will be apparent to those skilled in the art. Accordingly, this disclosure is intended to embrace all such alternatives, all modifications and all variations that do not depart from the scope and spirit of this 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 Process node consideration 21 Process node; Process node and related examination 22 Word expression; Word expression describing process node 23 Natural language search; Overlay natural language search 24 Corporate data and internal content; Corporate data / Content 32 Business Activity and Object 33 Recognition Structure 41, 44, 82, 83 Goal Set 43, 43-1, 43-2, 43-3, 46, 49, 50 Step 45 Process; Navigation Process 47 Goal 61, 62 Arrow 6 4 Skill, Value, Knowledge 65 Object 66 Context 71 High-level goal set 72, 73, 74 Child goal set 77 Comprehensive process 78 Comprehensive process sub-step 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 Sub goal sets 901-912, 921-925, 1071-1080, 1181-1183, 1010-1026 Step 920 Expert user 930 Node attribute; Attribute 931 Attribute 932 High level attribute; Attribute 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 Attributes 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 enterprise; Problem solving in the enterprise 1110 Scanned content 1120 Language parser 1130 Index model 1150 Index engine 1160 Important point index 1171 Web-based search interface; Web-based search 1172 Web-based collaboration tool; Web-based collaboration 1173 Portal-based interface for application integration; Application integration 1174 Mobile device interface; Mobile device 1175 interface; Office / e-mail Application 1180 To fix multiple events in the system 1185 Index story; Story 1186 Event 1187 Index engine; Index 1200 System 1202 Function 1208 Display of limited area; 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 Encoded Relationship 1230 Member 1232 Fire Department Staff; Non-Company Participant 1234 Police station; non-business participant 1236療従 parties; 1238 Environmental Protection Agency who is not a corporate participants; a person who is not a corporate participant 1240a-1240e companies of member 1242 Contact 1252 node (fire)
1254 nodes (flood)
1256 nodes (intruders)
1258 node (site of problem)
1260 nodes (number of people arriving at a safe place)
1262 nodes (number of people not counted)
1264 nodes (on-site emergency equipment)
1266 node (exit location)
1268 nodes (medical situation of people in a safe place)
1270 user input node; query 1500 common goal 1502 node A; abstract node 1504 node B; abstract node 1506 node C; abstract node 1508 node D; abstract node 1510 intermediate goal E
1512 Intermediate Goal F

Claims (35)

A system including a plurality of mobile terminals and the central application control function, the portable terminal includes a communication link, e Bei display and power supply,
The plurality of mobile terminals communicate with the central application control function, the central application control function comprising a computer-readable medium having executable instructions encoded on a non-transitory digital storage medium; Non-transitory digital storage media includes computing devices that also store corporate models, corporate content and corporate data ;
The process associated with the model includes a plurality of nodes, a computer readable description of relationships between different nodes, and a computer readable description of content, data and relationships between different nodes; Including
The display is
A limited area in which fewer than all nodes are visible at the first predetermined moment and the interrelationships that communicate with the computing device and are displayed at the first predetermined moment And a function for identifying a node to be
The computing device communicates with the plurality of mobile terminals,
The computing device transmits different information packets to each mobile terminal and receives different information packets from each mobile terminal, each of the information packets depending on the node assigned to each user. ,
Each transmitted package is an arbitrary response of the system detected by the computing device that changes the state of the node assigned to the user from the designed response to the interaction caused by the user and the cause and effect. A system characterized by depending on changes in the state of a node. The system of claim 1, wherein the state of the interrelated nodes is determined by computer code encoded on the non-transitory digital storage medium, and the relationship between the interrelated nodes is dynamic. The system of claim 2, wherein the state of the interrelated nodes changes based on communication between the computing device and the plurality of mobile terminals. 3. The system of claim 2, wherein a new emergency overlay node network is applied that changes the relevance between subsequent processes in response to changes in the stakeholder goal hierarchy . Each of the mobile terminals
The system of claim 1, comprising a display that is integral with the portable terminal and that communicates with the portable terminal. 6. The system of claim 5, wherein the nodes visible at the first predetermined moment are interrelated nodes that allow access to information about the user. The system of claim 6, wherein the computing device communicates with the mobile terminal to identify the interrelated nodes that are displayed at the first predetermined moment. The system of claim 7, wherein the computing device accesses a status state of an ongoing event and changes the interrelated node combination as a function of time and status state. The system according to claim 7, wherein each of the mobile terminals can display a node that is consecutive in a preceding stage and / or a succeeding stage of the interrelated nodes specified by the function. At any one or more predetermined moments of (i) folding a child node to a parent node, (ii) expanding a child node below the parent node, or (iii) expanding or contracting The system of claim 9, wherein the user can change the number of interrelated nodes visible on the display. 11. The system of claim 10, wherein the user interface allows a user to increase the number of interrelated nodes visible on the display at any predetermined moment. The system of claim 10, wherein the user interface allows a user to reduce the number of interrelated nodes visible on the display at any predetermined moment. 11. The system of claim 10, wherein all nodes can be visible on the display at any predetermined moment. A system for discovering and converting information related to processes related to a company,
The system
A computer-readable medium having executable instructions encoded on a non-transitory digital storage medium, the non-transitory digital storage medium also storing corporate models, corporate content, and corporate data Equipped with a computing device,
The process associated with the model includes a plurality of nodes and computer-readable associations that describe the associations between different nodes expressed as computer-readable causes and consequences. A readable description of content, data and associations between different nodes;
A conversion value is assigned to one or more adjacent nodes by a software code, and the software code defines a cause and a result that can be read by a computer when connecting the node and the adjacent node.
The system
A device that communicates with the computing device and is capable of inputting and outputting data relating to enterprise critical points;
An interface associated with the mobile device that provides the user with content and data that can assist the user in solving problems, taking advantage of opportunities, and understanding events, and the node is first A user interface with a display visible at a given moment of time;
Including the system.   15. The display has a limited area that is integrated with a mobile terminal and communicates with the mobile terminal so that fewer nodes than all the nodes are visible at the first predetermined moment. System.   The system of claim 15, wherein the nodes visible at the first predetermined moment are interrelated nodes that allow access to information about the user.   The system of claim 16, wherein the computing device communicates with the mobile terminal to identify the interrelated nodes that are displayed at the first predetermined moment.   18. The system of claim 17, wherein the computing device accesses a status state of an ongoing event and changes the interrelated node combination as a function of time and status state.   The system according to claim 17, wherein the mobile terminal also displays a node that is consecutive in a preceding stage and / or a succeeding stage of the interrelated nodes specified by the function.   The user interface includes one or more predetermined arbitrary moments of (i) folding a child node into a parent node, (ii) expanding a child node under the parent node, and (iii) expanding or contracting. 19. The system of claim 18, wherein the system allows a user to change the number of interrelated nodes visible on the display.   21. The system of claim 20, wherein the user interface allows a user to increase the number of interrelated nodes visible on the display at any predetermined moment.   19. The system of claim 18, wherein the mobile terminal displays a node that indicates the greatest risk for the enterprise.   21. The system of claim 20, wherein all nodes can be visible at any predetermined moment. The system of claim 14 , wherein the association between adjacent nodes is derived from computer readable causes and consequences. 15. The system of claim 14 , wherein the change in value in the state model associated with the node is computer readable and does not require a change in content and data relevance descriptions between the node and adjacent nodes. A method of emulating real-world processes in an overlay system,
The method
Identify multiple system process steps and assign attributes that are the state attributes of processes that are the basis of the real world,
Associate attributes related to the node with the node,
Building the system process steps into multiple clusters of nodes;
Establish the causes and consequences of the relationship between the nodes that the computer can read,
Use transactional process nodes to identify the underlying state values of real-world processes and their unique locations in the state model,
The attributes related to each node is set to the state model,
Use computer readable cause and effect links between nodes to determine the relationship between the state elements of the processes underlying the real world,
Includes steps. 27. The method of claim 26 , wherein each process node is characterized by a state model attribute. 28. The method of claim 27 , wherein when a new node or new attribute is identified, the state model is automatically extended to allow storage of values for the node or attribute. When a new node or new attribute is identified, the node or attribute is added to a node cluster, and the user interface is automatically expanded to accommodate the new node and its attributes. 27 methods. When the existing nodes or an existing attribute is inactive, the node or attribute is removed from the node cluster, the user interface is automatically being narrowed to delete the attribute with the node, it claims 27 the method of. A method of integrating at least two processes in two different systems or processes that are not necessarily designed to work together to achieve a common goal comprising:
The method
Comprises identifying one of the node cluster from the plurality of cluster nodes by a is sufficiently abstract and effective node in both the first process and the second process,
Each node in the node cluster describes an enterprise critical point having one or more intermediate goals, and each node includes data and / or content associated with the corporate critical point,
Each node in the node cluster has a cause and effect relationship with other nodes in the node cluster, and the cause and effect relationship can be expressed by a computer-readable mathematical algorithm. ,
The intermediate goal converges to the common goal. 32. The method of claim 31 , wherein each process node is characterized by a state model attribute. 35. The method of claim 32 , wherein when a new node or new attribute is identified, the state model is automatically extended to allow storage of values for the node or attribute. When a new node or new attribute is identified, the node or attribute is added to a node cluster, and the user interface is automatically expanded to accommodate the new node and its attributes. 32 methods. When the existing nodes or an existing attribute is inactive, the node or attribute is removed from the node cluster, the user interface is automatically being narrowed to delete the attribute with the node, claim 32 the method of.

Images