Systems and methods for modeling and monitoring processes in an organization using digital twins

Abstract

A system and method for modeling and monitoring processes in an organization using digital twins is disclosed. The system has a model builder that creates a model, communicates with a first user device and creates an integrated model of the process called a digital twin definition. The digital twin includes a server component for executing the digital twin definition and the server component also communicates with a plurality of transaction systems and ancillary systems. The digital twin has a client module that enables output on a second user device and deploys the digital twin to monitor the process. A method for creating a dynamic model and monitoring the model using a digital twin is disclosed. A method for creating the presentation is also disclosed.

Description

TECHNICAL FIELD

[0001] The present invention relates to modeling business processes, deploying these models to run as digital twins of the processes and using these digital twins to monitor business processes, and more particularly, to a plurality of such digital twins of a part of an organization or the entire organization.

[0002] DEFINITIONS

[0003] As used in the present invention, the following terms are generally intended to have the meanings described below, unless the context of their use indicates otherwise.

[0004] The expression "organization" used in the context of the present invention refers to, but is not limited to, a business organization or a government or an institution or any organized group pursuing a specific purpose. Specifically in the context of the present invention, the expression "organization" refers to, but is not limited to, the parent set of all systems, including IT and non-IT systems, the people operating and supervising these systems to achieve specific actions and activities related to different processes and different "entities" participating in these processes.

[0005] The expression "process domain" used in the context of the present invention refers to, but is not limited to, a collection of similar processes and transactions belonging to the enterprise common area. (Examples can include sales, marketing, human resources, accounting, finance, legal, etc.)

[0006] The expression "system" used in the context of the present invention refers to a physical or virtual platform or platform component on which actions or transactions are performed. (Examples can include: software systems, such as ERP, e-mail software; or platforms, such as Oracle databases, storage systems; or hardware servers, even manufacturing machines and workstations).

[0007] The expression "entity" used in the context of the present invention refers to a system-level object or a transaction-level object with specific characteristics, an identifiable life cycle and is considered to have a significant impact or play an important role in the overall operation of the process domain.

[0008] The term "twin" in the industry relates to the combination of one or more entity models running independently of the actual entity.

[0009] The term "digital twin" is a digital representation of a real-world entity or system. The implementation of a digital twin is an encapsulated software object or model that reflects a unique physical object and or software design pattern, organization, people or other abstraction.

[0010] The term "harmonium" refers to something that can exist independently and / or as part of something. Harmonium exists simultaneously as a self-sufficient whole in relation to its subordinate parts, and as a dependent part when considered from the opposite perspective.

[0011] The term "harmonizing entity" refers to an object or abstraction of the aforementioned entity that has an independent existence and can be considered as a harmonization as defined above. In the context of this invention, an entity or business object may be referred to as a harmonizing entity if it can exist or continue to perform its role without its harmonizing parent entity or container entity, and in the same manner as when a harmonizing parent entity exists.

[0012] In the context of this invention, the term "operational model" refers to a digital model or representation of the aforementioned copula entity, wherein the lifecycle of the entity is represented as a finite state machine, the activities performed during the lifecycle are represented as steps, and the operational aspects of the entity's lifecycle are captured by necessary logic.

[0013] In the context of this invention, the term "play" refers to, but is not limited to, a complete representation of an entity and its contribution to a process domain or enterprise. A "play" is a digital twin of a hoax entity. A "play" includes at least one operational model and may include combinations of other operational or analytical models.

[0014] In the context of this invention, the term "marker" refers to a "reference" included in a model or presentation that points to a specific attribute of a system or process that is considered important in the process model. Of a large number of features or attributes, only a few are considered important to the presentation, and these attributes are considered "marked".

[0015] These definitions supplement the definitions expressed in this field. Background Technology

[0016] Information technology (IT) applications in many organizations worldwide have reached a high level of sophistication in capturing and storing all critical business transactions across various process domains such as finance, sales, marketing, manufacturing, project and product management, and supply chain management. Numerous integrated or standalone IT systems provide the functionality to meet these needs. Some examples include ERP systems, customer relationship management (CRM) systems, supply chain management (SCM) systems, manufacturing information systems, and various financial accounting software. In the prior art, such systems are collectively referred to as "record systems" or transaction processing systems.

[0017] Over the past two decades, the field of Business Process Management (BPM) has received considerable attention. BPM focuses on "processes" rather than transactions, aiming to capture, analyze, optimize, and automate them. Several BPM suites exist that provide the features of managing and executing business processes. Existing BPM solutions typically include workflow and modeling services. Such BPM solutions also execute basic process steps or transactions. Most BPM suites use BPMN notation from the prior art for modeling. Existing suites known in the art are either human-centric (workflow), integration-centric (service bus), document-centric (case tools), or a combination of these.

[0018] Digital transformation driven by technologies such as artificial intelligence and automation has gained attention as a lever for improving business performance. In the case of automation, many new RPA (Robotic Process Automation) tools have been invented in this field, in addition to earlier approaches. Artificial intelligence tools and algorithms have been successfully applied to several specific problem statements. The widespread adoption of these tools across all business processes is still in its maturation stage.

[0019] Digital twins, as a phenomenon and as a technological implementation, have existed for quite some time. With the advent of computing technologies and their increasing accessibility and affordability, complex digital twins have become feasible for a wide range of applications. A digital twin is defined as a digital representation of a real-world entity or system. A digital twin is implemented as an encapsulated software object or model that reflects a unique physical object, process, organization, person, or other abstraction. Therefore, a twin can be viewed as a collection of one or more models of an entity, operating independently of the original system but situated within a shared context.

[0020] Several existing applications of digital twins have been disclosed in the prior art. Each application of a digital twin is characterized by its application or purpose and the combination of models used in the digital twin. These two aspects are distinct yet closely related. For example, several existing implementations of twins model manufacturing plants, machines, or workstations. Some of these twins are used for process simulation or scenario analysis, while others are used for production area design purposes. Some implementations have digital twins of aircraft used for simulation and personnel training. The models used in these twins are suitable for this purpose.

[0021] US Patent Application No. 20190138970A1 cites the use of digital twins based on "physics-based models," which are used in the context of operational technologies such as control systems, data recorders, and alarm systems. Furthermore, this patent proposes combining operational technologies and IT into a twin. This patent application suggests storing captured information about "entities" as "background" and acting with reference to this "background." It is noteworthy that this patent application discloses terms such as "twin builder," "twin runtime," "graph database," "Kafka pipeline," and "knowledge ingestion." US Patent Application '970 primarily focuses on digital twins of physical systems and lacks attention to developing digital twins for enterprise processes. The patent disclosure aims to display processed data and recommended actions on a user interface, although it does not detail any mechanisms for intervening in the real-time operation of physical entities. US Patent Application US20190138970A1 mentions the possibility of entity aggregation but does not disclose methods for aggregation at the enterprise level.

[0022] Another patent application, WO2018140395A1, discloses a method for creating digital twins for entire industrial facilities. This disclosure proposes creating digital twins for individual "assets" such as machines and workstations, and developing digital twins based on operational technology models. The focus of this disclosure is primarily on physical objects, mostly industrial objects. This disclosure does not attempt to model "processes" as the basic unit for digital twins. This patent application discusses the use of different operational models and the combination of these different models to form a digital twin. However, it should be noted that patent application WO2018140395A1 only discloses the formation of digital twins for physical systems and does not disclose digital twins related to software systems.

[0023] Another US patent application, US10431005B2, discloses the use of digital twins in the field of augmented reality for real-time image generation. The digital twin proposed in this patent application uses a model to create a visual simulation of the behavior of a physical system. However, this patent application does not disclose the use of the digital twin model for monitoring and performance improvement of objects or systems. This patent application does not propose creating digital twins for processes.

[0024] Another US patent application, US20170286572A1, proposes a category for creating digital twins of specific types of physical devices such as compressors, turbines, and other such high-energy assets. It proposes digital twins based on either a physics-based model or an operational technology-based model. It should be noted that this disclosure does not include digital twins of the creation process. Furthermore, this disclosure does not propose any interventions or actuations performed by the digital twin.

[0025] The field of this invention, namely business process modeling and the creation of digital twins of processes, presents some unique challenges.

[0026] Some processes within an organization extend beyond a single recording system. This means that some transactions within this process might be processed in one system, while others might be processed and stored in another. In most cases, transaction data flows seamlessly between applications. Therefore, application integration exists. However, in most cases, end-to-end process monitoring is impossible. Consequently, despite application integration, many of these processes develop into technology silos.

[0027] As can be seen, in many cases, individual applications have their own master data, which may not always be synchronized. Different reports / dashboards may provide mismatched views.

[0028] Every enterprise is unique in many ways. Even different parts of the same enterprise differ in many ways. Processes have nuances specific to the business, product, or location. Sometimes, these nuances can provide significant advantages. Record-keeping systems in this field focus on the standardization of transaction execution. Therefore, these important customizations are prohibited or excluded from the scope of transaction systems. These are then managed on some unintegrated platform.

[0029] Processes encompass both transactional and non-transactional activities. Typically, recording systems only capture transactional activities. Many important non-transactional aspects, such as budgets, forecasts, and targets, are often managed on supporting platforms like spreadsheets. These unrelated process actions and / or unrelated execution artifacts are typical examples of technology or organizational silos.

[0030] The aforementioned technology silos or organizational silos pose challenges to the ability to obtain an integrated end-to-end process view and monitor process effectiveness.

[0031] The inherent complexities of transactions and the storage of transaction data, coupled with the exclusion of numerous processes from the system, tend to entangle the process view and obscure data visibility. This also poses significant challenges to the implementation of automation and AI technologies, as considerable effort is spent on collecting, validating, and regulating data due to these exclusions. Integrating decisions generated by digital technologies and AI into existing process flows often requires significant effort or customization of the transaction system implementation. Numerous failures have been reported in implementing technologies such as AI and MI due to the challenges of integrating with the existing system landscape. All of these challenges stem from a lack of "fusion" within the application landscape and process domain.

[0032] There is a need for systems and methods to create dynamic models of processes that transcend organizational or technological silos, capturing both transactional and non-transactional aspects of a process. These models can be easily incorporated into all process customizations without disrupting transactions and eliminate transactional complexities that are independent of the process's perspective. There is also a need for systems and methods to create real-time digital twins that provide an end-to-end view of the process, helping to clarify process flows and democratize the visibility of process execution information. Furthermore, there is a need for a standalone platform that can operate collaboratively with all transactional systems, facilitating the easy integration of new non-transactional technologies into the current operational landscape. Finally, there is a need for systems and methods that can create, deploy, and run models and monitor processes in real time. Summary of the Invention

[0033] A system for modeling processes within an organization, deploying such models as digital twins, and using these digital twins to monitor processes has a first user device configured to receive data from a user. The system has a model builder for creating a model that communicates with and is based on input received from the first user device. An integrated model of the process, referred to as a digital twin definition, is created and stored in a memory unit.

[0034] A digital twin runs a model defined in the digital twin definition. It has a server component that executes the digital twin definition. The server component communicates with multiple transaction and auxiliary systems. The server component also interprets the model and executes the presentation. The digital twin has a client module capable of outputting to a second user device. The digital twin definition includes organizational information related to masters, IT and non-IT systems, organizational structure, roles and responsibilities, and employee information, which provides the execution context for all models within the digital twin.

[0035] A digital twin is defined as having at least one operational model and several other models representing the transactional and non-transactional aspects of a process. The operational model includes constraints on the entity's lifecycle, process performance parameters, visibility requirements, and actuation requirements. Digital twins communicate bidirectionally with multiple transactional and auxiliary systems; data exchange includes reading data related to transactional and organizational information and writing data through system mechanisms to initiate or actuate specific predetermined interventions.

[0036] The model builder includes a model creator configured to allow users to: define a finite state machine for an entity's lifecycle; define the steps within each state of the state machine; associate the system with the steps; and define the transition conditions between states. The model builder also includes a logic builder configured to allow users to create executable logic that executes on the system's server components, interpreting the state and dynamics of the flow based on input data received from the transaction system. The logic builder, based on input to the model creator, formally defines the requirements for the model logic. The model builder includes a data acquisition configuration module configured to prompt the user for comprehensive data requirements based on the lifecycle model and a list of tags, and to allow users to configure separate data exchange with different systems. The data acquisition configuration module, based on input to the model creator, formally generates interface requirements. Finally, the model builder includes a result configuration module configured to enable the user to configure at least one widget for displaying client-side visualizations.

[0037] The organization definition module enables users to capture basic information about the organization and its process domains. The model builder has a model manager that is configured to allow users to add additional models to the presentation and configure those models to work with the basic operational model.

[0038] The compiler and output formatter are configured to validate user input received from the model creator, logic builder, data acquisition configuration module, result configuration module, and model manager. The output compiler is also configured to interpret the input, validate the correctness of such input in relation to organizational information, and create digital twin definitions and store the digital twin definitions on a first data storage.

[0039] The digital twin includes a server component with a model interpretation module configured to: read transaction data and other relevant data from a transaction buffer, which is acquired by a data configuration module according to the configuration specified in the digital twin definition and stored in the transaction data buffer; evaluate the model based on the received data; and send the evaluation results to a memory in a client processor module. The server component also includes two independent scheduling modules to specify several schedules for the frequency of data acquisition and model evaluation.

[0040] The digital twin has a client processor configured to process the data from the second data storage to generate a response output upon receiving a request from a request controller, and is also configured to interface with the result generator to format and transmit the results.

[0041] The analysis module is configured to analyze the analysis model in the presentation.

[0042] A method for modeling processes within an organization, deploying these models as digital twins, and using systems to monitor these digital twins includes the following steps: selecting process domains for model creation; identifying and listing objects and entities participating in the process domain; identifying harmonizing entities from the list and merging all non-harmonizing entities by characteristics into one or more harmonizing entities; qualifying harmonizing entities based on their attributes; merging unqualified entities from one or more qualified harmonizing entities by characteristics, the above process steps allowing users to flexibly define demonstrator boundaries and associate them with harmonizing relationships; prioritizing and sorting qualified entities to actually create demonstrators; creating demonstrators that facilitate at least one model builder for each qualified harmonizing entity; establishing data interfaces with transaction data acquisition modules and existing transaction systems; executing the digital twin definition on a server in supervised mode, parallel to the actual transactions as digital twins, where the twin acts as an observer, evaluating the model based on real-time input, actuating actions on the transaction system, and monitoring business processes using predetermined performance metrics and alert conditions.

[0043] The method for creating a demo entity includes the following steps: identifying the lifecycle states of the entity; a model creator creates a finite state machine for the entity; identifying the transitions for each state and identifying the conditions that enable the transitions; identifying the process steps involved in each state, and the actions associated with those process steps, which allow mapping the business view of the process to the technologies and systems in the entity's lifecycle; identifying and marking the boundaries to be included in the model from the transaction system; using a logic builder to constrain and program different model conditions for transitions, step completions, and other conditions, so that the model logic is not transactionally complex; the model creator records parameters such as performance parameters and invention parameters; a data acquisition configuration module defines the data interface with the transaction system, the interface requirements being generated based on system-defined specifications; a result configuration module programs the result visualization; an organization module configures master files, roles, systems, organizational structure, employee information, and employee roles; a model manager creates and integrates the model for collaborative operation with the basic operational model; and an output compiler compiles, tests, and deploys the demo entity components on the appropriate server components. Attached Figure Description

[0044] The objects and advantages of the present invention will become apparent from the following description, which is read with reference to the accompanying drawings, wherein:

[0045] Figure 1 A system is shown that uses digital twins that communicate with other systems in the system environment to model and monitor processes within an organization;

[0046] Figure 2 The present invention is shown Figure 1The system includes multiple modules according to the present invention;

[0047] Figure 3 The logical representation of an organization modeled according to the present invention is shown;

[0048] Figure 4 It was shown as Figure 3 A logical component of a process domain that is part of an organization;

[0049] Figure 5 It shows that it was deployed in Figure 1 Different components of the demo on the digital twin;

[0050] Figure 6 It shows Figure 2 The model builder is shown, illustrating its different components;

[0051] Figure 7 It shows Figure 2 The digital twin module;

[0052] Figure 8 The steps involved in the method of the present invention are shown, the method using Figure 2 The system creates a dynamic model of the process and uses its digital twin to monitor the process; and

[0053] Figure 9 It shows Figure 8 The detailed steps for the "Create Presentation" step in the method steps.

[0054] According to the present invention, it is Figure 8 It continues and details the main steps of "creating a presentation".

[0055] Figure Labels

[0056] 100 - Systems and methods for modeling processes within an organization and monitoring processes using digital twins.

[0057] 104-Transaction System

[0058] 108-Auxiliary System

[0059] 112-Model Builder

[0060] 114-Digital Twin

[0061] 120-Client

[0062] 124-Processor

[0063] 126-Memory Chip

[0064] 202 - Integrated Process Model (Output of Model Builder), Definition of Digital Twin

[0065] 204-Memory

[0066] 206-User Equipment 1

[0067] 208-User Equipment 2

[0068] 210-Server Components

[0069] 212-Client Module

[0070] 300-organization

[0071] 302 - Process Area

[0072] 304 System

[0073] 306-Main File

[0074] 308 - Organizational Structure

[0075] 310 - Master Roles

[0076] 312 - Organize Employees

[0077] 314-Process Area

[0078] 402a-Harmonious Entity 1

[0079] 404a-Demonstration Entity 1

[0080] 402b-Honorable Entity 2

[0081] 404b-Demo 2

[0082] 402n-Harmonious Entity N

[0083] 404n-Demonstration Body N

[0084] 502 - Demonstration Body

[0085] 504 - Basic Operating Model

[0086] 506 - Entity Lifecycle

[0087] 508 - Performance

[0088] 510-Visibility

[0089] 512-Intervention and Actuation

[0090] 514 - Status

[0091] 516 - Steps

[0092] 518-Transaction

[0093] 520-Action

[0094] 522-KPI

[0095] 524 - Alert

[0096] 526-Character

[0097] 528-View

[0098] 530-individual

[0099] 532-Dashboard

[0100] 534-Automation

[0101] 536-Action Invocation

[0102] 538 - Tag List

[0103] 540 - Other Models

[0104] 542 - Basic Statistical Model

[0105] 544-Decision System Model

[0106] 546-AI and Machine Learning Models

[0107] 548-Life Cycle Model

[0108] 550 - Budget, Planning, Forecast

[0109] 552-Gamification Model

[0110] 554 - Or-based model

[0111] 556-Mathematical Model

[0112] 602 - Model Creator

[0113] 604 - Logic Builder

[0114] 606 - Transaction Data Acquisition Configuration Module

[0115] 608 - Result Configuration Module

[0116] 610 - Organizational Background

[0117] 612-Model Manager

[0118] 614 - Compilers and Output Formatters

[0119] 700-Model and Transaction Data Interpretation Module

[0120] 702 - Transaction Data Acquisition Scheduler

[0121] 704 - Transaction Data Acquisition Module

[0122] 706 - Transaction Data Buffer

[0123] 708 - Model Evaluation Scheduler

[0124] 710 - Transaction Data Processing Module

[0125] 712-Actuation Module

[0126] 714 - Client Processor

[0127] 716-Data Memory

[0128] 718 - Request Controller

[0129] 720 - Result Generator

[0130] 722-Analysis Module

[0131] 724-Statistics Engine

[0132] 726-Learning Engine

[0133] 728-Collaboration Server Module

[0134] 730 - Workflow Viewer

[0135] 732 - Result Formatter

[0136] 734 - Client-side Analysis

[0137] 740-Collaboration Client Detailed Implementation

[0138] For better understanding, specific exemplary details are used to explain the invention described herein. However, those skilled in the art can practice the disclosed invention without using these specific details.

[0139] The phrase "one embodiment" or "an embodiment" as used in the specification means that a specific feature, structure, characteristic, or function described in connection with that embodiment is included in at least one embodiment of the invention. The phrase "in one embodiment" appearing throughout the specification does not necessarily refer to the same embodiment.

[0140] The "preferred embodiments" mentioned in the specification refer to specific features, structures, characteristics, or functions described in detail, thereby omitting known constructions and functions in order to clearly describe the present invention.

[0141] The foregoing description of specific embodiments of the invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed, and it will be apparent that many modifications and variations are possible in accordance with the foregoing teachings.

[0142] Throughout the description, all the different environments in this embodiment that are part of "systems and methods for modeling and monitoring processes in an organization using digital twins" are referred to below as the "systems" or "systems and methods" of the present invention.

[0143] Figure 1 The system 100 of the present invention and the environment in which it interacts are illustrated. According to the present invention, system 100 includes a model builder 112, a digital twin 114, and a terminal client module 212. The model builder 112 is hosted on a desktop or in a virtual environment. The digital twin 114 includes multiple server environments typically hosted in the cloud or on a client device. According to the present invention, the terminal client views output or monitors processes through a digital twin from an end-user device such as a laptop, desktop computer, smartphone, iPad, or tablet computer.

[0144] According to the present invention, a digital twin 114, as part of system 100, communicates with multiple transaction systems 104 and auxiliary systems 108. Transaction systems 104 typically include systems such as human resources systems, supply chain management systems, enterprise resource planning systems, or other record-keeping systems. Auxiliary systems 108 typically include different platforms, such as artificial intelligence platforms, analytics platforms, IoT platforms, and common operating tools such as spreadsheets.

[0145] Understandably, the process includes multiple basic transactions as well as non-transactional activities. A transactional system 104, also known as a "recording system," captures transaction details. The process also includes important non-transactional activities such as analysis, forecasting, predictive insights, budgeting, etc. According to the present invention, multiple systems that enable these activities and are not recording systems, such as spreadsheets, AI systems, RPA tools, etc., are referred to as auxiliary systems 108.

[0146] The digital twin 114 operates on a processor 124 and a memory chip 126, which are configured to receive and execute functions according to the invention. In this embodiment, the processor 124 is selected from the group consisting of application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), advanced RISC machine (ARM) processors, microprocessors or controllers, and any combination thereof.

[0147] System 100, particularly digital twin 114, interacts bidirectionally with transaction system 104 and auxiliary system 108. According to the invention, digital twin 114 reads specific entity attributes and organizational attributes such as master data and employee data from transaction system 104. Digital twin 114 reads auxiliary parameters such as objectives, budgets, forecasts, and analysis results from auxiliary system 108. Digital twin 114 is configured to send predetermined actuation commands to transaction system 104 and auxiliary system 108. These actuation commands invoke, for example, services, execute commands, or activate robot programs. The actuation commands are invoked along with the necessary data or parameters required for the service or robot program.

[0148] Figure 2 A system 100 according to the present invention is described. System 100 includes a model builder 112, a digital twin 114, at least one first user device 206, and at least one second user device 208. The first user device 206 is configured to receive user input. In this embodiment, the model builder 112 receives input required to create a demo entity 502. This input includes entity lifecycle 506 definitions, performance specifications 508, visibility requirements 510, and intervention requirements 512. The model builder 112 also receives organizational configurations and specifications for other models. In this embodiment, the first user device 206 is selected from, but not limited to, the group consisting of laptops, desktops, smartphones, iPads, and tablets.

[0149] Model builder 112 is configured to communicate with first user device 206 to receive inputs required for various models in the creation process, and is also configured to compile and format all such inputs into a complete definition of demo body 202, hereinafter referred to as the "digital twin definition" stored on first data storage 204. Digital twin definition 202 is deployed on server 210 of system 100, with a real-time interface set up along with the necessary transaction system 104, and the output of this real-time interface is to be viewed on second user device 208. Digital twin 114 includes server component 210 and client module 212.

[0150] Figure 3The logical components of the organization 300 proposed in this invention are illustrated. Organization 300 provides a context in which various IT or non-IT systems operate. Multiple operations or transactions enable the implementation of various processes. Organization 300 is considered to include all process domains 302 and all IT and non-IT systems 304. According to the invention, organization 300 also provides a context for all entities to operate. This context includes, but is not limited to, master data 306, definitions of roles and responsibilities 310, information related to organizational structure 308, and employee data 312. In this invention, master data 306 also includes relational information, which can be of one of the following types: hierarchical structure, heterogeneous structure, or harmonious structure. According to the invention, organization 300 includes at least one process domain 302 and at least one system 304.

[0151] Figure 4 It shows Figure 3 The logical components of a single process domain 314 within an organization are described below. In this embodiment, each process domain 314 includes at least one harmonizing entity 402a, which is already eligible to be modeled as the primary entity of a presentation body 502. The presentation body 502 created with entity 402a as the primary entity is 404a. In this embodiment, the model of a process domain 314 is a combination of all presentation bodies corresponding to eligible harmonizing entities such as 402a, 402b, etc.

[0152] According to the present invention, entities within an organization include business entities and system entities. Business entities are business objects or transaction artifacts created in any process. System entities are configuration items, such as IT systems or physical systems.

[0153] When twin 114 is executed in system 100 of the present invention, multiple instances of the business entity exist at any given time, each instance following its independent lifecycle. In the case of system entities, only one instance of each system entity exists at a time.

[0154] According to the present invention, a harbinger entity is defined as an entity that exists or continues to perform its role even in the absence of its harbinger parent entity or container entity, and in the same manner as when a harbinger parent entity exists. For example, in the absence of a computer as a harbinger parent entity (hard drive), the hard drive will not perform its role. Therefore, the hard drive cannot be a harbinger entity; however, it is a component of another entity. On the other hand, a cloud storage unit can be modeled as a harbinger entity because the cloud storage continues to perform the role assigned to it, even without a harbinger parent entity for the cloud storage: the storage cluster. In another example, a line item in an order is not or may not be a harbinger entity; however, a delivery note or invoice based on that line item is modeled as a harbinger entity.

[0155] Figure 5The components of the demonstrator 502 are shown, including, for example... Figure 1 The digital twin 114 shown. Demonstration body 502 includes a basic operating model 504 (hereinafter referred to as the "basic model"), an optional set of other models 540 configured to work in conjunction with the basic model 504, and a shared tag list 538.

[0156] The basic operational model 504 is the central component of the digital twin 114 of the process modeled according to the present invention. The basic operational model 504 captures lifecycle and associated operational parameters, such as those captured in the many underlying transactions constituting the process. This definition of the basic operational model 504 ensures that the digital twin reflects the behavior of the actual process. The basic operational model 504 includes an entity lifecycle model 506, process performance parameters 508, process visibility requirements 510, and intervention and actuation definitions 512.

[0157] Entity lifecycle model 506 includes the definition of state 514, the definition of steps or activities performed in each step 516, the necessary logical conditions representing transition conditions 518, and manual or automatic actions as part of step 516. This aspect of twin 114 ensures business-oriented interpretation of the underlying transactions. In this embodiment, entity lifecycle model 506 is implemented through a unique combination that includes creating a finite state machine for the process and identifying the activities performed within each state of the finite state machine. This combination uniquely captures both the composition and dynamics of the process.

[0158] Performance parameter 508 includes two important aspects. The first aspect is the definition of the key performance indicators (hereinafter referred to as KPIs) 522 from the perspective of business results, and the second aspect is the definition of abnormal conditions or alarm conditions 524. This explicit and deeply rooted capture of performance parameters enables the twin in this invention to effectively monitor process performance.

[0159] The definition of process visibility 510 includes specific requirements related to: the various roles 526 that operate within the process, the view of the process 528, the individuals associated with the process 530, and the various dashboards 532 required for effective visualization of the process status. This definition of process visibility democratizes the availability of information across silos.

[0160] Tag list 538 is a comprehensive list of all tags confined within the presentation body, spanning all models. This concept of a shared tag list 538 across different models within the presentation body enables smooth integration between different models, including operational models, analytical models, etc. Other models 540 are additional models that typically represent non-transactional aspects of processes. Coherently integrating these aspects into the presentation body achieves true integration. In this invention, such models may include, but are not limited to, statistical models 542, decision system models 544, AI and ML models 546, lifecycle models 548, etc. This practice of integrating multiple interrelated models into a single presentation body provides significant advantages to system 100.

[0161] Now refer to Figure 6 The model builder 112 includes a model creator 602, a logic builder module 604, a data acquisition configuration module 606, a result configuration module 608, an organization definition module 610, a model manager 612, and a compiler and output formatter 614. The first user device 206 enables the user to input all the features of the process and organization required to create the presentation into the model builder 112.

[0162] The output of model builder 112 is a digital twin definition 202. In this implementation, it is in the form of a file. Model builder 112 compiles and validates various inputs, creates the digital twin definition 202, and stores it in memory 204. The digital twin definition 202 must include all configurations of the presentation body 502 and background information on the aforementioned organization 300 and process domain 314. Model builder 112 includes specific functionalities to achieve this goal.

[0163] Model Creator 602 allows the user to configure entity lifecycles 506, states, steps, and transition conditions. It defines the configurations related to process performance 508 and actuation 512. In this embodiment, this module creates a Markov state machine for the underlying process by capturing state and transition information. In another embodiment, standard Business Process Modeling Notation (BPMN) is used to capture steps.

[0164] The logic builder module 604 allows users to specify the logic to be executed in order to interpret the state of the process based on transaction data received from the transaction system. In one implementation, the logic builder module 604 is capable of “code-free” graphical programming using various standards specified by IEC 1131 and IEC 1499. In yet another implementation, the logic builder 604 is capable of generating script interfaces and code using various parameters such as tags.

[0165] The data acquisition configuration module 606 captures comprehensive data exchange requirements from various systems participating in the demo 502. These include, but are not limited to, the underlying transaction system 104. In an implementation, this module is implemented as queues and topics configured in a platform such as Kafka. The result configuration module 608 assists the user in configuring client-side visualization for the demo 502 as required by the visibility requirement 510 of the demo 502 by defining at least one widget.

[0166] The organization definition module 610 allows users to capture the necessary information related to organization 300 and process domain 314. This information provides context for the execution of the digital twin 114. The model manager 612 allows users to add all other models to the presentation and configure these models to work with the basic operational model specified by the model creator 602 via the result configuration module 608.

[0167] The compiler and output formatter 614 are configured to validate received user input and input obtained from: model creator 602, logic builder 604, transaction data acquisition configuration module 606, and result configuration module 608. It is also configured to validate the configuration of other models specified by model manager 612. Furthermore, it is configured to interpret input, compile input, and create output as integrated process model 202. This integrated process model 202 is stored on first data memory 204.

[0168] Figure 7 The digital twin 114 components of system 100 are described. According to the present invention, a demonstrator or a group of models deployed and executed in parallel with a transaction system is defined as a digital twin. The digital twin includes a server component 210 and a client component 212. Server component 210 includes a model interpretation module 700, an analysis module 722, a client processor module 714, and a collaboration server 728. Server 210 receives a digital twin definition 202 and deploys and executes this digital twin definition 202.

[0169] According to the present invention, the server performs at least four operations. First, the server 210 continuously interfaces with the transaction system 104 or the auxiliary system 108 and obtains data from the transaction system or the auxiliary system. Second, the server 210 interprets the data according to a defined model and updates and manages the status. Third, the server 210 receives and fulfills requests from different client sides. Finally, the server 210 also manages collaboration between different users and user groups.

[0170] The model interpretation module 700 is configured to manage two sets of schedules. The data acquisition scheduler 702 manages communication with the transaction system, while the model evaluation scheduler 708 is set up based on the timescale criticality considerations of the digital twin model and operations. The transaction data buffer 706 holds transaction and master data received from the transaction system, as well as actuation data to be sent to various systems. In this invention, these buffers are implemented via a messaging platform such as Kafka. The transaction data processing module 710 reads data from the buffer 706, evaluates the model, and sends the evaluation results to the client processor module 714. The analysis model configured within the demonstrator is evaluated by the analysis module 722 based on signals from the scheduler 708.

[0171] The client processor module 714 includes: a data storage 716; a request controller 718; and a result generator 720. In one embodiment, the data storage 716 includes a graph database integrated with a distributed data storage system for processing structured and unstructured data.

[0172] The collaboration server module 728 enables different users of system 100 to collaborate and communicate with the help of collaboration client 740. System 100 provides unique and advantageous features in which users collaborate and communicate on specific topics in the model, such as business entities, system entities, alarms, actions, KPIs, etc.

[0173] Client module 212 includes a process viewer 730, a result formatter 732, a client-side analysis module 734, and a collaboration client 740. The client module runs on the second user equipment 208 and fulfills the key monitoring requirements of view 528, dashboard 532, and alarm 524. According to the invention, the second user equipment 208 is selected from, but not limited to, the group consisting of laptops, desktop computers, smartphones, iPads, and tablet computers.

[0174] Digital twin 114 continuously reads data from transaction system 104. It interprets this data independently based on its defined model, unrelated to the transaction system. Therefore, according to the invention, digital twin 114 acts as an observer. Furthermore, digital twin 114 does not participate in the processing of transactions governed by transaction system 104, but is capable of making predetermined interventions. This "supervisory mode" configuration enables the digital twin to monitor processes and achieve fusion without interrupting ongoing operations and transaction processing. This aspect gives the invention a significant advantage over the prior art.

[0175] Furthermore, the digital twin 114 only reads selected or "tagged" attributes of the underlying transaction and has its own independent logic for "interpreting" these tag values. This aspect of having synchronous, real-time data and independent interpretation frees the model from unnecessary transactional complexity. The independent configuration of the logic builder allows twins to be created at any level of complexity, regardless of the underlying system or transactions.

[0176] Figure 8 and Figure 9 The steps involved in creating dynamic models and monitoring processes using the system 100 of the present invention are described. Method 800 includes steps involving: identifying and qualifying candidate entities, creating various models for the entities as demonstrators, deploying and running these demonstrators as digital twins of the processes, and using these twins to monitor the processes. This method is preferably performed on the system 100 of the present invention.

[0177] In the first step 802, for the organization, various process domains are identified and specific process domains are prioritized for creating digital twins.

[0178] In step 804, all objects or entities participating in the selected process domain of 802 are identified and listed. In step 806, harmonizing entities from the list are identified and all non-harmonizing entities are merged into harmonizing entities by attribute or characteristic. In step 808, the identified harmonizing entities are "qualified" to create a presentation body. Entities that are not qualified in this step, i.e., entities for which no presentation body will be created, are merged into the appropriate qualified entities by characteristic.

[0179] In steps 806 and 808, this method manages the relationships between demonstrators as holacracy. The step of merging non-holacracy entities and holacracy entities that do not qualify as demonstrators into selected entities ensures the comprehensiveness of the operational model. The holacracy structure provides complete flexibility and control over the complexities of digital twins.

[0180] In step 810, the creation of the demo entities is prioritized and sorted. In this step, the demo entity builder 112 records the results of all previous method steps. In step 812, a demo entity 502 is created for each eligible entity. Step 812 is executed on the model builder 112 of system 100. The output of this step 812 is the digital twin definition 202.

[0181] In step 814, the interface with the transaction system is set and configured based on the definitions of these interfaces created in step 812, in the system and tags. These interfaces with the transaction system are set in the data acquisition module 704.

[0182] In step 816, digital twin definition 202 is executed as digital twin 114 in supervised mode. This model is deployed on server 210 as digital twin 114 in supervised mode. In step 818, business processes are monitored using the digital twin. In this step, client module 212 is used to continuously monitor performance metrics, status, and abnormal conditions to improve performance parameters, including strategic, tactical, or operational KPIs.

[0183] Figure 9 Described Figure 8 The steps involved in step 812 are included in the process of creating each demo entity 502. In step 902, the lifecycle states of the entity are identified. In step 904, a finite state machine is created for the entity using model creator 602. In step 906, the permissible transitions and enabling conditions for each transition are identified and recorded. In step 908, the activities performed in each state and the associated manual or automatic actions are identified. In this step, they are recorded as “Steps” in model creator 602. In step 910, attributes from transaction system 104 are identified and tagged. In this step, a tag list 538 is recorded in model creator 602. Steps 902 through 906 record structural, compositional, and lifecycle information about the entity.

[0184] In step 912, the interpretation logic required for the operation of the digital twin is programmed using logic builder 604. This step dynamically incorporates the process into the model. In this implementation, this step uses standards based on IEC 61131 and IEC 61499. A unique feature of this method is that the logic requirements are specified in a standardized manner by module builder 112 based on the structural and lifecycle information captured using model creator 602 in step 910. This feature greatly simplifies model creation.

[0185] In step 914, the performance parameters and interventions are programmed using model creator 602. In step 916, the data acquisition module 606 is configured based on the tag list and other data requirements. In step 918, the visualization of presentation 502 is created and configured using results configurator 608.

[0186] In step 920, the organization module 610 is used to configure the organizational background, including master files, relationships, master roles, etc.

[0187] In step 922, the model manager 612 is used to create other models and integrate them into the presentation.

[0188] In step 924, a compiler and output formatter are used to compile and test the demo 502 or the digital twin definition 202. The system deploys the various components to the data acquisition module 704, the model interpretation module 700, and the analysis module 722.

[0189] Now referring to the operation Figures 1 to 9 In organizations utilizing the systems and methods of this invention, multiple stakeholders participate in the creation and use of the proposed digital twin 114. Process owners are the owners of the process definitions for a specific group of processes. Typically, they are also the owners of some business functions belonging to that specific domain and are considered experts in that particular process. The system manager is responsible for deploying, monitoring, and maintaining the digital twin 114 and its various interfaces with other IT systems. Business users are the end users of the systems of this invention.

[0190] After selecting process domain 314 for creating the digital twin 114, the process owner of process domain 302, together with other stakeholders, selects and qualifies candidate entities for creating the demo entity 502 according to steps 806, 808, and 810. First, all objects and entities participating in the operation of process domain 302 are identified. They are categorized into holacracy entities or non-holacracy entities based on criteria. Holacracy entities 404n are also qualified based on the business requirements for creating the demo entity 502. It is ensured that identified non-holacracy entities and holacracy entities 404n that do not qualify for demo entity creation are merged into qualified entities by attribute.

[0191] However, it should be understood that these steps ensure that the model of process domain 302 as a group of demonstrators is a collective exhaustive representation of the process. This also ensures that each demonstrator 502 is self-contained and independent, while maintaining close synergy with other demonstrators, thereby ensuring the consistency and scalability of the entire model. In the system 100 of the present invention, the above decisions are recorded. This step begins with all process owners collaboratively configuring the organization 300, process domain 302, and defining the demonstrators 502. Using at least one first user device 206 and organization definition module 300, the process owners maintain all relevant background information defined in the organization 300. According to the present invention, demonstrators 502 include at least one operational model 504 and may include combinations of other operational models 540 or analytical models. Using at least one user device 206 and model builder 112 of the proposed system, the process owners first create a basic operational model 504 for the entity. This includes defining the entity's lifecycle, states and steps, performance parameters; and participating in the system for identifying steps and performance parameters. Based on this, operational model tags are created in tag list 538. The process owner then incorporates the non-transactional parts of the process into the presentation body definition by configuring other analysis models or operational models as other models 540. In defining these, model creator 602, logic creator 604, and transaction data acquisition configuration module 606 are used.

[0192] The process owner and business users configure client-side visualization for presentation 502 collaboratively by defining at least one widget using the result configuration module 608, as required by the visibility requirement 510 of presentation 502. After defining all components of presentation 502, the process owner integrates other models with presentation 502 using model manager 612. The process owner compiles the presentation using compiler and output formatter module 614. The output of a successful compilation is a digital twin definition 202. This artifact is stored in memory 204. In one implementation, the model builder 112 component can be hosted on user device 206 as a desktop or mobile application. In other implementations, the model builder 112 component can be hosted in the cloud and accessed from a first user device 206.

[0193] The server-side environment setup includes separate servers for the model and data interpretation module 700, client processor 714, and analysis module 722. In embodiments, these servers may be hosted in the cloud or a dedicated data center. The setup also includes a server data acquisition module 704 and an actuation module 712. In embodiments, these include messaging and streaming media platforms such as Apache Kafka. The server-side environment also includes data storage for model data and model definitions. In embodiments, these include at least one graph database and a database that supports SQL or non-SQL data.

[0194] The system administrator deploys the demo 502 or digital twin definition 202 on server 210. The proposed system 100 has the capability to deploy different components on the corresponding server environment. The system administrator uses a specific scheduler to configure the scheduler for individual model evaluations and system-wide data acquisition. Finally, the digital twin 114 is placed into "run" mode, where it begins to operate under supervision along with the transaction system 104 and auxiliary system 108, and begins evaluating the model and interpreting the data.

[0195] After being placed in "Run", server component 210 begins to execute its actions. Transaction data acquisition configuration module twin 606 triggers communication with transaction system 104 to read data according to a predetermined schedule. The received data is stored in transaction data buffer 706. Transaction data processing module 710 reads data from buffer 706, evaluates the model, and stores the evaluation results in the database. The analysis model configured within demo unit 502 is evaluated by analysis module 722 based on the data in the database, according to model evaluation schedule 708.

[0196] The client processor module 714 processes requests from multiple second user devices 208. Requests generated using the second client devices 208 are processed by the request controller 718, and responses to these requests are sent via a result generator 720, which is displayed on the user devices 208 by a process viewer 730 and a result formatter 732.

[0197] After the demo 502 is deployed and the digital twin 114 is operational, business users and process owners can begin monitoring business processes using client module 120 installed on at least one second client device 208. Using the results from client module 120, business users and process owners can monitor processes using features such as: process view, lifecycle view, process health, system health, actions generated for specific entities for each user, alerts generated based on process performance requirements, timelines for each entity, various dashboards, and outputs from other models integrated into demo 502. These views are presented by results configuration module 608. Users can communicate and collaborate with other users using collaboration client 740. Chats can be general chat or topic-specific chats for any entity / action / alert.

[0198] The systems and methods of the present invention advantageously create dynamic models of processes within an organization. Furthermore, the systems and methods monitor said processes by deploying the models as digital twins of the actual processes.

[0199] This invention provides a comprehensive, end-to-end, and flexible solution for monitoring processes within an organization. The solution can model the entire organization or be applied to a single entity. The boundaries and scope of the entity can be selected between any two states. Therefore, entity boundaries can be split or combined. Entities can be implemented individually and linked via harmonization, or they can be merged into a single entity. The system and method allow for the inclusion of auxiliary non-transactional activities. They can also be incorporated into interdependent systems. Thus, the method and system advantageously provide a comprehensive and flexible solution.

[0200] This invention, through a "real-time digital twin" monitoring process, provides a state view by evaluating model parameters based on real-time data. This eliminates the inherent complexities associated with transactions, flexibly allowing implementers to choose the level of complexity of the digital twin and simplifying implementation and operation. Furthermore, when the digital twin is running in production, it does not interfere with any transactional systems.

[0201] In this invention, the digital twin is configured in a supervised mode, acting as a real-time observer that independently evaluates its model and provides system mechanisms to initiate or actuate specific predetermined interventions. This configuration offers several advantages. Implementing the digital twin does not cause any disruption to operations.

[0202] This invention, in which the organization is configured to provide context to all presentations, advantageously eliminates the challenge of inconsistent master files or mismatched records, thereby overcoming technology silos. Furthermore, due to the shared context across all presentations, most organizational complexities are advantageously clarified.

[0203] This invention advantageously creates a view of a “process,” rather than a simple ordered set of activities. A finite state machine provides a “business view,” while steps provide a view of activities closely linked to the system. Therefore, any merged non-transactional process step or any new technology can be inserted into the model at the appropriate step or action level or in the process state. Thus, this invention creates an advantageous way to achieve seamless integration of new technologies with ongoing operations with less effort and without disrupting business operations. Furthermore, this allows the definition of performance metrics to be consistent with this business view at the strategic, tactical, and operational levels, and allows for proactive capture or handling of alerts, which facilitates aligning digital twins with the organization's business objectives.

[0204] The method of this invention includes defining a demonstrator body as a combination of lifecycle models of harmonic entities. This is significantly different from previous approaches that model processes as ordered sets of activities. This methodological approach differs considerably from the modeling domain of business processes. By defining and configuring demonstrator bodies in this way, this method advantageously allows for the division of process domains into mutually exclusive and collectively exhaustive entity lifecycles, referred to herein as "demonstrator bodies".

[0205] The method of the present invention further defines the following steps: achieving optimal granularity of the presentation entity definition by fusing non-harmonizing entities or harmonizing entities not selected for the presentation entity into at least one of the selected entities according to entity attributes. This ensures that the entire entity attribute space of the process domain is covered by its digital twin. This comprehensive coverage provides a significant advantage to the digital twin created by the present invention.

[0206] The method of this invention allows multiple entities within the same process domain to share holacracy relationships. Because users can select the appropriate granularity of entities to create, this approach of modeling process domains as holacracy entities provides significant flexibility and scalability to the enterprise model. Furthermore, it offers the flexibility to develop some holacracy attributes into entities at later stages without disrupting existing entities.

[0207] The method of this invention utilizes a finite state machine of entity lifecycles as a medium for capturing "processes," and subsequently links these states to activities and the system. This method offers significant advantages over existing technologies because it enables the system of this invention to be a comprehensive process model.

[0208] The system of this invention provides a single end-to-end platform for modeling and monitoring processes. System 100 performs model creation, model validation, model deployment including interface settings, model execution as a digital twin, and process monitoring.

[0209] The system of this invention allows multiple auxiliary models to be integrated into a single presentation body, enabling the non-transactional parts of a process to be easily incorporated into a single model. This provides significant advantages.

[0210] The system of the present invention, wherein a single lifecycle model spans many systems and extends beyond multiple transactions, advantageously provides a unified, end-to-end model, easily offering an end-to-end view of the process. Furthermore, since this end-to-end view is available throughout the entire process and for all entities, this system advantageously popularizes process visibility.

[0211] The system of this invention allows for "no-code," graphical programming, enabling business users to create / maintain process logic for their own twins. Therefore, the system and the twin can advantageously access and respond to evolving business needs. Furthermore, the system specifies the requirements for the logic in a standardized manner. This makes the complete implementation very easy and robust. Moreover, because this logic is independent of transaction logic, unaffected by transaction-related complexities, and created by business users, it can be easily incorporated into process nuances and customizations. Therefore, this system effectively breaks down organizational barriers.

[0212] The system of this invention allows each activity or step to be mapped to a state on one side and to a system on the other, advantageously providing a combined process-system health view that offers insights into the real-time health of all systems and their impact on the overall process status. This is highly useful for reducing the effort and cost of IT application management.

[0213] The system of this invention enables real-time collaboration through secure messaging built within the system. Specifically, using the system's topic-based chat function, users can collaborate and communicate on business-related topics such as specific entities, alert conditions, or specific KPI trends, utilizing rich background information and effective features.

[0214] The system and methodology have the advantage of enabling the configuration, deployment, and operation of digital twins of business processes in a short time with minimal effort.

[0215] The above description of the embodiments is provided for illustrative purposes and is not intended to limit the scope of the invention. The various components of a particular embodiment are generally not limited to that particular embodiment but are interchangeable. Such variations should not be considered as departing from the invention, and all such modifications should be considered within the scope of the invention.

[0216] The embodiments were chosen and described in order to best explain the principles of the invention and its practical application, thereby enabling others skilled in the art to best utilize the invention and its different embodiments, and to make various modifications to suit the intended particular use.

[0217] It should be understood that various omissions and substitutions of equivalents may be suggested or made advantageous as circumstances may be, but these are intended to cover the application or implementation without departing from the scope of the invention.

Claims

1. A system (100) for modeling and monitoring processes in an organization using digital twins, comprising: A first user equipment (206) is configured to receive data from a user; A model builder (112) is used to create a model, which communicates with a first user device (206) and creates an integrated model of the process called a digital twin definition (202); A digital twin (114) that runs a model in a digital twin definition (202) has a server component (210) that executes the digital twin definition (202) and also communicates with multiple transaction systems (104) and auxiliary systems (108). The server component (210) interprets the model and executes a presentation (502). The digital twin (114) communicates with the multiple transaction systems (104) and the auxiliary systems (108) in a bidirectional manner. Data exchange includes reading data related to transaction information and organizational information and writing data through system mechanisms to initiate or actuate specific predetermined interventions. The digital twin (114) has a client module (212) that enables output on a second user equipment (208); as well as Deploy such digital twins and use them to monitor the processes.

2. The system (100) for modeling and monitoring processes in an organization using digital twins as described in claim 1, wherein, The model builder (112) processes user input to create, validate, and compile the digital twin definition (202) and stores the digital twin definition (202) in memory (204).

3. The system (100) for modeling and monitoring processes in an organization using digital twins as described in claim 1, wherein, The digital twin definition (202) includes at least one operational model (504) of the modeled entity and multiple other models (540) representing the transactional and non-transactional aspects of the process. The operational model (504) includes limitations on entity lifecycle (506), process performance parameters (508), visibility requirements (510), and intervention and actuation definitions (512).

4. The system (100) for modeling and monitoring processes in an organization using digital twins as described in claim 1, wherein, The digital twin definition (202) includes organizational information related to master files, IT and non-IT systems, organizational structure, roles and responsibilities, and employee information, which provides the execution context for all models in the digital twin (114).

5. The system (100) for modeling and monitoring processes in an organization using digital twins as described in claim 1, wherein, The model builder (112) includes: A model creator (602) is configured to allow a user to: define a finite state machine for an entity lifecycle (506); define the steps within each state of the state machine; associate the system with the steps; and define the transition conditions between states. A logic builder (604) is configured to allow a user to create executable logic that executes on a server component (210) of the system (100) and interprets the state and dynamics of the process based on input data received from the transaction system (104). The logic builder (604) normatively defines the requirements for the model logic based on the input to the model builder (602). A data acquisition configuration module (606) is configured to prompt the user for comprehensive data requirements based on a lifecycle model and a tag list (538) and allow the user to configure separate data exchange with different systems. The data acquisition configuration module (606) generates interface requirements in a standardized manner based on the input to the model creator (602). The result configuration module (608) is configured to enable the user to configure at least one widget for displaying client-side visualizations; Organization definition module (610) enables users to capture basic information about organizations and process domains; A model manager (612) configured to allow the user to add other models (540) and analysis models to the presentation body (502), and to configure all models to work with the basic operational model (504); and A compiler and output formatter (614) are configured to verify user input received from the model creator (602), the logic builder (604), the data acquisition configuration module (606), the result configuration module (608), and the model manager (612). The compiler and output formatter are also configured to interpret the input, verify the correctness of such input in relation to organizational information, and create the digital twin definition (202) and store the digital twin definition (202) on a first data memory.

6. The system (100) for modeling and monitoring processes in an organization using digital twins as described in claim 1, wherein, The digital twin (114) includes: A server component (210) has a model and transaction data interpretation module (700), which is configured to: read transaction data and other related data from a transaction buffer, which is acquired by a data acquisition configuration module (606) and stored in the transaction data buffer (706) according to the configuration specified in the digital twin definition (202); evaluate a model based on the received data; and send the evaluation result to a memory in a client processor module (714). The server component (210) also includes two separate scheduling modules to specify several schedules for data acquisition and model evaluation frequencies; The client processor module (714) is configured to process the data from the second user equipment (208) to generate a response output upon receiving a request from the request controller, and is also configured to interface with the result generator to format and transmit the result; Analysis module (722), configured to analyze the analysis model within the demonstration body (502); and The server component (210) is configured to receive and execute digital twin definitions (202); wherein one or more processors are used to implement the model and transaction data interpretation module (700), the client processor module (714), and the analysis module (722).

7. A method (800) for modeling and monitoring processes in an organization using digital twins, comprising the steps of creating dynamic models and monitoring business processes using digital twins: (I) Identify the process domains (302) in the enterprise and select the process domains (302) to create a model; (II) Identify and list the objects and entities participating in the process domain (302); (III) Identify harmonizing entities (402n) from the list and merge all non-harmonizing entities into one or more harmonizing entities (402n) based on their characteristics. (IV) Based on the attributes of the merging entity (402n), the eligibility of the merging entity (402n) is determined; (V) Merge unqualified entities from one or more qualified harmonizing entities (402n) by characteristics. The above process steps III, IV and the current step allow users to flexibly define the boundaries of the demonstrators and link them to harmonizing relationships. (VI) Prioritize and sort eligible entities for actual creation and deployment of demos; (VII) Create a demo body (502) to facilitate at least one first user device (206) and model builder (112) for each eligible harmonizing entity (402n). (VIII) Establish a data interface with the transaction data acquisition module (704) and the existing transaction system (104); (IX) The digital twin definition (202) is executed as a digital twin (114) on the server component (210) in supervised mode, in parallel with the actual transaction, wherein the digital twin (114) acts as an observer to evaluate the model based on real-time input and actuate actions on the transaction system (104); and (X) Use real-time digital twin (114) to monitor business processes, wherein the digital twin definition (202) has predetermined performance metrics and alarm conditions.

8. The method (800) for modeling and monitoring processes in an organization according to claim 7, wherein the method for creating a demo (502) comprises the following steps: (I) Identify the lifecycle states of the harmonizing entity (402n); (II) The model creator (602) creates a finite state machine for the entity; (III) Identify the transition for each state and enable the transition in each transition; (IV) Identify the process steps involved in each state, as well as the actions associated with said process steps, the aforementioned process steps II, III and the current process step allow the technology and system to map the business view of the process to the entity lifecycle (506); (V) Identify and mark the boundaries to be included in the model from the transaction system (104); (VI) Use the logic builder (604) to constrain and program different model conditions for transformation, step completion and other conditions so that the model logic does not have transaction complexity; (VII) The model creator (602) programs parameters such as performance parameters and invention parameters; (VIII) The data acquisition configuration module (606) is limited to the data interface with the transaction system (104), and the interface requirements are generated based on the system definition specifications; (IX) The results configuration module (608) programs the visualization of results; (X) Organization Definition Module (610) configures organizational background matters, roles, systems, organizational structure, employee information, and employee roles; (XI) The model manager (612) creates a model and integrates the model with the presentation body (502); and The (XII) compiler and output formatter (614) compile, test, and deploy the demo body (502) components on the model and transaction data interpretation module (700) and the analysis module (722).

Images