Enterprise process system full life cycle data architecture establishment method and device, medium and equipment

Abstract

The invention discloses an enterprise process system full life cycle data architecture establishment method and device, a medium and equipment, and relates to the technical field of information. Through modeling design from a top layer to a bottom layer, the process system of an enterprise is managed in a digital form from demand to optimization and improvement of the full life cycle; element and digitization of the whole life cycle of the process system are realized, a whole life cycle data architecture of the enterprise process system is established, one-part definition and multiple-part reference of the element data of the process system can be realized, and complete information data management of the whole life cycle process of the complex enterprise process system is supported. Enterprise process system elements such as external files, compliance management, business rules, business processes, IT development and the like of enterprises are subjected to full-life-cycle management and operation in a digital form, and re-management of the enterprises based on model management is achieved.

Description

Technical Field

[0001] This application relates to the field of information technology, specifically to a method, apparatus, medium, and equipment for establishing a full lifecycle data architecture for an enterprise process system. Background Art

[0002] A process is a set of business execution standards that a company follows in its daily operations and management, aiming to ensure the stability and continuity of the company's business activities. The process management lifecycle covers process requirements, construction, execution, monitoring, and optimization. Traditional document-based processes cannot achieve full lifecycle digital closed-loop management of processes from requirements to operation. Summary of the Invention

[0003] The main purpose of this application is to provide a method, apparatus, medium and equipment for establishing a full lifecycle data architecture for enterprise process systems, aiming to build a comprehensive data system (hereinafter referred to as management BOM) covering all stages of the entire process lifecycle, including requirements, construction, execution, monitoring and optimization, to solve the problem that it is difficult to achieve digital management of full lifecycle data of enterprise process systems in the existing technology.

[0004] To achieve the above objectives, the technical solutions adopted in the embodiments of this application are as follows: In the first aspect, embodiments of this application provide a method for establishing a full lifecycle data architecture for an enterprise process system, which constructs a process system requirement dataset and forms an element BOM based on the internal and external requirements of enterprise management; Based on the actual business classification and processes of the enterprise, a process tree is constructed, and the process nodes are modeled to build the underlying data to form the process BOM; Based on the underlying model of the process nodes in the process BOM, IT development and operation data collection are carried out to form a dataset of business process node operation instances, i.e., the running BOM. Based on the running data of BOM process instances, process usage information is extracted, process performance information is calculated, process anomaly or deviation information and process change information are recorded to form a diagnostic BOM, thereby completing the establishment of the enterprise process system's full lifecycle data architecture.

[0005] In one possible implementation of the first aspect, after constructing a process system requirements dataset and forming an element BOM based on the internal and external requirements of enterprise management, the method also includes: The document structure is broken down according to external requirements to form clause element nodes; The clause elements are organized and merged to form compliance element nodes.

[0006] In one possible implementation of the first aspect, the attributes of the clause element node include: document number, document name, business category, responsible department, and document clause; the attributes of the compliance element node include: element number, element content, business category, responsible department, related external document clauses, and recipient.

[0007] In one possible implementation of the first aspect, after organizing and merging the clause nodes to form compliance element nodes, the method also includes: Based on the attributes of the objects to which compliance element nodes are received, connect compliance element nodes with business rule element nodes or process element nodes.

[0008] In one possible implementation of the first aspect, the attributes of the business rule element node include: business rule document number, document name, business category, responsible department, and business rule document clauses.

[0009] In one possible implementation of the first aspect, after constructing a process tree based on the enterprise's actual business classification and processes, and modeling the process nodes to build the underlying data to form the process BOM, the method also includes: Connect business rule element nodes and process element nodes based on the receiving object attribute of the business rule element node.

[0010] In one possible implementation of the first aspect, the dataset of process element nodes includes: process level, process number, process name, parent process, front-end process, back-end process, process owner, responsible department for the process, process performance indicators, process risks, associated compliance element nodes, and associated business rule element nodes.

[0011] In one possible implementation of the first aspect, the attribute data of the process element nodes includes: process definition, process purpose, process start condition, process input, step number, step name, step content, execution role, process output, and process end condition.

[0012] In one possible implementation of the first aspect, the attribute data of the process performance indicator includes: indicator number, indicator name, indicator definition, indicator purpose, calculation formula, unit, indicator dimension, and monitoring frequency.

[0013] In one possible implementation of the first aspect, the attribute data of process risk includes: risk number, risk event, risk category, risk occurrence frequency, risk impact degree, risk management strategy, control objective, and control measures.

[0014] In one possible implementation of the first aspect, the business process node running instance dataset, i.e., the running BOM, includes: business process number, business process name, this process instance number, front-end process instance number, process initiation time, initiator, initiator's department, process step number, step executor, execution start time, execution end time, execution result, and the IT system of the running instance.

[0015] In one possible implementation of the first aspect, the attribute data of the IT system of the process execution instance includes: IT system number, system name, system module, sub-module, and menu.

[0016] In one possible implementation of the first aspect, the diagnostic BOM dataset includes: business process number, business process name, process usage frequency, process performance indicators, and process change records.

[0017] In one possible implementation of the first aspect, the attribute data of the process performance indicator includes: indicator number, indicator name, indicator target value, indicator actual value, and indicator result collection date.

[0018] In one possible implementation of the first aspect, the attribute data of the process change record includes: reason for change, content of change, person who performs the change, person who approves the change, process version, release time, and effective time.

[0019] Secondly, embodiments of this application provide an apparatus for establishing a full lifecycle data architecture for an enterprise process system, comprising: The requirements layer construction module is used to record internal and external document information, split document clauses, and assign clause-receiving departments according to the internal and external requirements of enterprise management. The compliance element layer construction module is used to organize and merge the assigned internal and external document clause nodes to form compliance element nodes, and establish the association between compliance elements and business rule document clause nodes or process element nodes according to the objects to which compliance elements are undertaken. The process element layer construction module is used to build a process tree based on the actual business classification and process of the enterprise, and to model the process nodes to build the underlying data to form the process BOM. It also associates the compliance element nodes and business rule clause nodes with specific process steps / activities or forms and rules. The process execution instance layer construction module is used to perform IT development and operation data collection based on the underlying model of each process element node, and record the business process node execution instance data to form the execution BOM. The process diagnostic layer construction module is used to extract process usage information, calculate process performance information, record process anomaly or deviation information and process change information, and form a diagnostic BOM to complete the establishment of the enterprise process system's full lifecycle data architecture.

[0020] Thirdly, embodiments of this application provide a computer-readable storage medium storing a computer program, which, when loaded and executed by a processor, implements the method for establishing a full lifecycle data architecture for an enterprise process system as provided in any of the first aspects above.

[0021] Fourthly, embodiments of this application provide an electronic device, including a processor and a memory, wherein, Memory is used to store computer programs; The processor is used to load and execute computer programs to enable electronic devices to perform the enterprise process system full lifecycle data architecture establishment method provided in any of the first aspects above.

[0022] Compared with the prior art, the beneficial effects of this application are: This application proposes a method, apparatus, medium, and equipment for establishing a full lifecycle data architecture (management BOM) for an enterprise process system. The method includes: constructing a process system requirement dataset and forming an element BOM based on the internal and external requirements of enterprise management; constructing a process tree based on the actual business classification and processes of the enterprise, and modeling the process nodes to construct the underlying data to form a process BOM, where the element BOM provides requirement inputs for the process BOM, and the process BOM consumes the management requirements in the element BOM; collecting IT development and operation data based on the underlying model of the process nodes in the process BOM to form a business process node operation instance dataset, i.e., an operation BOM; and extracting process usage information, calculating process performance information, and recording process anomaly or deviation information, process change information, etc., based on the operation data of the process instances in the operation BOM to form a diagnostic BOM, thereby completing the establishment of a full lifecycle data architecture for the enterprise process system. This application, through top-down and bottom-up modeling design, manages the entire lifecycle of an enterprise's process system in digital form, from requirements to optimization and improvement. It realizes the element-based and digital transformation of the entire lifecycle of the process system, establishes a data architecture for the entire lifecycle of the enterprise's process system, and enables the definition of process system element data in one place and its reference in multiple places. It supports the full information data management of complex enterprise process system lifecycle processes, and manages and operates enterprise process system elements such as external documents, compliance management, business rules, business processes, and IT development in digital form throughout their entire lifecycle, realizing the enterprise's model-based re-management. Attached Figure Description

[0023] Figure 1 This is a schematic diagram of the electronic device structure of the hardware operating environment involved in the embodiments of this application; Figure 2 A flowchart illustrating the method for establishing a full lifecycle data architecture for an enterprise process system provided in this application embodiment; Figure 3This is a schematic diagram illustrating the modeling of process element nodes in the method for establishing a full lifecycle data architecture for an enterprise process system provided in this application embodiment; Figure 4 This is a schematic diagram of an operational example of the method for establishing a full lifecycle data architecture for an enterprise process system provided in this application embodiment; Figure 5 A schematic diagram of process execution instance data established using the method provided in the embodiments of this application; Figure 6 This application provides a schematic diagram illustrating a method for managing data associations between different BOMs within a BOM; Figure 7 A schematic diagram of the module for establishing a full lifecycle data architecture for enterprise process systems provided in this application embodiment; The diagram is labeled as follows: 101-Processor, 102-Communication bus, 103-Network interface, 104-User interface, 105-Memory. Detailed Implementation

[0024] It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit this application.

[0025] See attached document Figure 1 , attached Figure 1 This is a schematic diagram of the electronic device structure of the hardware operating environment involved in the embodiments of this application. The electronic device may include: a processor 101, such as a central processing unit (CPU), a communication bus 102, a user interface 104, a network interface 103, and a memory 105. The communication bus 102 is used to realize the connection and communication between these components. The user interface 104 may include a display screen and an input unit such as a keyboard. Optionally, the user interface 104 may also include a standard wired interface and a wireless interface. The network interface 103 may optionally include a standard wired interface and a wireless interface (such as a Wi-Fi interface). The memory 105 may be a storage device independent of the aforementioned processor 101. The memory 105 may be a high-speed random access memory (RAM) or a stable non-volatile memory (NVM), such as at least one disk storage device. The processor 101 may be a general-purpose processor, including a central processing unit, a network processor, etc., or it may be a digital signal processor, an application-specific integrated circuit, a field-programmable gate array or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component.

[0026] Those skilled in the art will understand that the appendix Figure 1 The structure shown does not constitute a limitation on the electronic device and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0027] As attached Figure 1 As shown, the memory 105, which serves as a storage medium, may include an operating system, a network communication module, a user interface module, and a device for establishing a full lifecycle data architecture for enterprise process systems.

[0028] In the appendix Figure 1 In the electronic device shown, the network interface 103 is mainly used for data communication with the network server; the user interface 104 is mainly used for data interaction with the user; the processor 101 and the memory 105 in this application can be set in the electronic device. The electronic device calls the enterprise process system full life cycle data architecture establishment device stored in the memory 105 through the processor 101 and executes the enterprise process system full life cycle data architecture establishment method provided in the embodiment of this application.

[0029] See attached document Figure 2 Based on the hardware device described in the foregoing embodiments, embodiments of this application provide a method for establishing a full lifecycle data architecture for an enterprise process system, including the following steps: S10: Based on the internal and external requirements of enterprise management, construct a process system requirement dataset and form an element BOM.

[0030] In the specific implementation process, based on the organization's administrative region, industry, and affiliation, documents that the enterprise must comply with and include in the implementation are identified from aspects such as laws and regulations, provincial and ministerial requirements, national standards, industry standards, and requirements of superior units, thus constructing a process system requirement dataset. Each external document forms a top-level node, and the attributes of this type of node mainly include the external document name, document security level, issuing agency, document type, business category, and whether it is accepted. For example, the "Data Security Management Measures in XX Field" has a security level of public, is issued by the XX department, is a law and regulation, belongs to the management process and information technology category, and the company must accept it.

[0031] Each requirement node in the top-level tree structure of the aforementioned requirement dataset is organized and merged to form compliance element nodes. External document clauses that the enterprise must comply with are analyzed and summarized. Clauses with similar content from different documents are consolidated and converted into internal compliance management requirements. Based on the enterprise's internal business management classification, a structured dataset of compliance elements that the enterprise must follow is constructed. The attributes of compliance element nodes mainly include element number, element content, business category, responsible department, associated external document clauses, and receiving object (such as a business rule element category or a process category). Furthermore, based on the distribution route of the receiving object and business category attribute of the compliance element node, specific business rule elements or processes, as corresponding receiving objects, create their own relationships with the compliance elements to receive the corresponding requirements of the compliance elements.

[0032] In one embodiment, after constructing a management system requirements dataset and forming a top-level tree structure based on external requirements of enterprise management, the method further includes: The top-level tree structure is broken down into clause nodes based on externally required documents; Each requirement node in the top-level tree structure is organized and merged to form compliance element nodes, including: Each requirement node and its clause node in the top-level tree structure are organized and merged to form a compliance element node. Based on the attributes of the objects to which the compliance element node is received, the compliance element node is connected to the business rule element node or process element node.

[0033] In the specific implementation process, external documents can be broken down into several clauses based on the granularity of their content, forming clause nodes. The attributes of a clause node mainly include: clause number, clause content, whether it applies to this enterprise, the receiving party (such as a certain compliance element), and the responsible department. Clauses are numbered, and the content and the determination of whether they apply to this enterprise are recorded. For each clause, a division of responsibilities is assigned. For example, a department creates a compliance element "Data Classification and Grading Management in the Industrial and Information Technology Field," defines the content of this element, and uses it to receive the requirements of Clauses X and XX of the "Data Security Management Measures for XX Field," etc., and implements the content of this element into the "Manage Data Assets" process for execution and solidification.

[0034] S20: Based on the actual business classification and processes of the enterprise, construct a process tree, and model the process nodes to build the underlying data to form the process BOM. The element BOM provides the requirement input for the process BOM, and the process BOM consumes the management requirements in the element BOM.

[0035] In the specific implementation process, based on the actual business classification and processes of the enterprise, a process tree is constructed to form enterprise process element nodes, and the processes are modeled to form the underlying data of the process nodes. The model data for process nodes mainly includes process hierarchy, process number, process name, parent process, front-end process, back-end process, process owner, responsible department, process performance indicators, process risks, related compliance element nodes, and related business rule element nodes. Furthermore, the content attribute data in the business process nodes includes process start conditions, process inputs, step numbers, step names, step content, execution roles, process outputs, and process end conditions. Furthermore, the attribute data for process performance indicators includes: indicator number, indicator name, indicator definition, indicator purpose, calculation formula, unit, indicator dimension, and monitoring frequency. Furthermore, the attribute data for process risks includes: risk number, risk event, risk category, risk occurrence frequency, risk impact degree, risk management strategy, control objective, and control measures.

[0036] In the process modeling process described above, compliance element nodes and business rule clause nodes are associated with specific process steps / activities or forms and rules.

[0037] In practical implementation, for example, a company constructs an enterprise business process architecture based on its internal business management logic. The structure of the process architecture is divided into four layers, including business domain, process group, process, and sub-process, as shown in the appendix. Figure 3 As shown, enterprises can construct or modify process models for "managing data assets" to meet the compliance requirements of "data classification and grading management in the industrial and information technology sector".

[0038] S30: Based on the underlying model of the process BOM process nodes, IT development and operation data collection are performed to form a business process node operation instance dataset, i.e., the operation BOM.

[0039] In the specific implementation process, IT development and operational data collection are carried out based on the underlying model of each process node to form a business process node operation instance dataset, as shown in the appendix. Figure 5 The diagram illustrates a module within an information system built by an enterprise for executing and recording the results of a process. After execution, it generates instance data of the process flow and its results. Electronic workflows or information systems developed based on business process nodes and their underlying model data ensure consistency between the process model and IT functions.

[0040] The business process execution instance data mainly includes the business process number, business process name, this process instance number, front-end process instance number, process initiation time, initiator, initiator's department, process step number, step executor, execution start time, execution end time, execution result, and the IT system running the instance. Furthermore, based on the IT system attributes of the execution instance in the business process node, the specific IT system serves as the corresponding process execution IT tool. Each IT system menu creates its own relationship with the business process to fulfill the execution specifications and requirements stipulated by the business process.

[0041] S40: Based on the running data of the BOM process instance, extract process usage information, calculate process performance information, record process anomaly or deviation information and process change information, and form a diagnostic BOM to complete the establishment of the enterprise process system's full lifecycle data architecture.

[0042] In the specific implementation process, process usage information is extracted from the running BOM data, process performance information is calculated, and process abnormality or deviation information and process change information are recorded to achieve diagnosis and improvement of process operation.

[0043] The modeling and design are completed from top to bottom, with each node being an object model, as shown in the attached figure. Figure 4 The enterprise process system full lifecycle data architecture shown includes, from top to bottom, the requirement layer, compliance element layer, business rule element layer, process element layer, process operation instance layer, and process diagnosis layer. The clauses on which the establishment of compliance element nodes is based can be obtained from the business management system under this business management system, or from the business management system under different business categories.

[0044] In this embodiment, through top-down modeling design, the entire lifecycle of the enterprise's process system, from requirements to optimization and improvement, is managed digitally. This achieves the element-based and digital transformation of the entire lifecycle of the process system, establishing a data architecture for the entire lifecycle of the enterprise's process system. This enables the definition of process system element data in one place and its reference in multiple places, supporting the full information data management of the complex enterprise process system's entire lifecycle. It also enables the digital management and operation of enterprise process system elements such as external documents, compliance management, business rules, business processes, and IT development throughout their entire lifecycle, achieving model-based re-management of the enterprise.

[0045] The Bill of Materials (BOM) is primarily used to describe the elements that make up a process system and the relationships between them. The data runs through the end-to-end lifecycle of process requirements, process construction, process execution, and process operation. This data structure is not limited to text descriptions but is also a computer-readable data file. The digitization of the process system will make automated processing and intelligent analysis of processes possible, thereby greatly improving the efficiency and accuracy of process governance. It is the core data for company management.

[0046] As an innovative data organization and management approach, the core of a Management Bill of Materials (BOM) revolves around structured process elements. It organically integrates and manages multiple dimensions of elements, including external requirements, internal management documents, business process design and construction, and the IT systems that support the process execution. Through this integration, the Management BOM enables precise implementation of business needs and compliance requirements within the process system, forming a closed-loop control mechanism that ensures business processes remain consistent with internal and external regulations (documentary compliance) and with the actual execution of the process within the IT system (documentary compliance).

[0047] The management BOM, in the order of its construction, mainly includes element BOM, process BOM, instance BOM, and diagnostic BOM.

[0048] The element BOM is used to represent the internal and external documents and clauses that the process must comply with from the perspective of process requirements. After sorting and analyzing, they are transformed into a list of management requirements in the form of elements and clauses.

[0049] A process BOM is used to represent a list of elements that constitute a process from the perspective of process construction, including the process architecture (L1-L4) and the final-level process model (L5 / L6).

[0050] An instance BOM is used to represent a list of elements that constitute the process and results of a process instance from the perspective of process operation.

[0051] A diagnostic BOM is a list of elements used to characterize the diagnostic results and improvement processes generated by analyzing process instances from a process operation perspective.

[0052] To achieve a single data source, data relationships between different BOMs in the management BOM are established through extraction, inheritance, and other methods to avoid duplicate definitions and ensure data consistency, as shown in the attached figure. Figure 6 The specific relationships are explained below: a) Element BOM and Process BOM: The Element BOM provides the requirement input for the Process BOM. The Process BOM should consume the management requirements in the Element BOM to ensure that the company's management requirements can be accurately integrated into the business process and are consistent in word and deed.

[0053] b) Process BOM and Instance BOM: The process BOM provides the execution requirements input for the instance BOM. The instance BOM should inherit the model of the process BOM and develop electronic flow or information systems with the process model as the data source. On this basis, the running process and result information are added, and the process and IT are integrated, and the document and reality are consistent.

[0054] c) Process BOM and Diagnostic BOM: The process BOM provides improvement target inputs for the diagnostic BOM. The diagnostic BOM should extract performance indicators such as processing time, error rate, and customer satisfaction from the process BOM as the basis for monitoring and diagnosis, and add the result information of the performance indicators within a certain time range.

[0055] d) Instance BOM and Diagnostic BOM: The instance BOM provides data input for the diagnostic BOM. The diagnostic BOM extracts the running time, frequency, and single-node throughput of the process from the instance BOM, and dynamically maintains the diagnostic result information based on this and the diagnostic model.

[0056] By filtering, merging, and reorganizing the data related to each BOM in the management BOM, views tailored to different usage needs can be automatically generated, such as various system views generated based on element BOMs, end-to-end process design views at different levels and from different perspectives generated based on process BOMs, end-to-end process operation views generated based on instance BOMs, and problem views generated based on diagnostic BOMs.

[0057] See attached document Figure 7 Based on the same inventive concept as in the foregoing embodiments, this application also provides an apparatus for establishing a full lifecycle data architecture for an enterprise process system, comprising: The requirements layer construction module is used to record internal and external document information, split document clauses, and assign clause-receiving departments according to the internal and external requirements of enterprise management. The compliance element layer construction module is used to organize and merge the assigned internal and external document clause nodes to form compliance element nodes, and establish the association between compliance elements and business rule document clause nodes or process element nodes according to the objects to which compliance elements are undertaken. The process element layer construction module is used to build a process tree based on the actual business classification and process of the enterprise, and to model the process nodes to build the underlying data to form the process BOM. It also associates the compliance element nodes and business rule clause nodes with specific process steps / activities or forms and rules. The process execution instance layer construction module is used to perform IT development and operation data collection based on the underlying model of each process element node, and record the business process node execution instance data to form the execution BOM. The process diagnostic layer module is used to extract process usage information, calculate process performance information, record process anomaly or deviation information, process change information, etc., and form a diagnostic BOM to complete the establishment of the enterprise process system's full lifecycle data architecture.

[0058] Those skilled in the art should understand that the division of the various modules in the embodiments is merely a logical functional division. In actual applications, they can be fully or partially integrated into one or more actual carriers. These modules can be implemented entirely in software through processing unit calls, entirely in hardware, or a combination of software and hardware. It should be noted that each module in the enterprise process system full lifecycle data architecture establishment device in this embodiment corresponds one-to-one with each step in the enterprise process system full lifecycle data architecture establishment method in the aforementioned embodiments. Therefore, the specific implementation of this embodiment can refer to the implementation of the aforementioned enterprise process system full lifecycle data architecture establishment method, which will not be repeated here.

[0059] Based on the same inventive concept as in the foregoing embodiments, embodiments of this application also provide a computer-readable storage medium storing a computer program. When the computer program is loaded and executed by a processor, it implements the method for establishing a full lifecycle data architecture for an enterprise process system as provided in the embodiments of this application.

[0060] Based on the same inventive concept as in the foregoing embodiments, embodiments of this application also provide an electronic device, including a processor and a memory, wherein, Memory is used to store computer programs; The processor is used to load and execute computer programs to enable electronic devices to perform the enterprise process system full lifecycle data architecture establishment method provided in the embodiments of this application.

[0061] In some embodiments, the computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; or it may be a device including one or any combination of the above-mentioned memories. The computer may be a variety of computing devices, including smart terminals and servers.

[0062] In some embodiments, executable instructions may take the form of a program, software, software module, script, or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.

[0063] As an example, executable instructions may, but do not necessarily, correspond to files in the file system. They may be stored as part of a file that holds other programs or data, for example, in one or more scripts in a Hyper Text Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple collaborative files (e.g., a file that stores one or more modules, subroutines, or code sections).

[0064] As an example, executable instructions can be deployed to execute on a single computing device, or on multiple computing devices located in one location, or on multiple computing devices distributed across multiple locations and interconnected via a communication network.

[0065] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.

[0066] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0067] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as read-only memory / random access memory, magnetic disk, optical disk) and includes several instructions to cause a multimedia terminal device (which may be a mobile phone, computer, television receiver, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0068] In summary, the embodiments of this application provide a method, apparatus, medium, and equipment for establishing a full lifecycle data architecture for an enterprise process system. The method includes: constructing a process system requirement dataset and forming an element BOM based on the internal and external requirements of enterprise management; constructing a process tree based on the actual business classification and processes of the enterprise, and modeling the process nodes to construct the underlying data to form a process BOM, where the element BOM provides requirement inputs for the process BOM, and the process BOM consumes the management requirements in the element BOM; collecting IT development and operation data based on the underlying model of the process nodes in the process BOM to form a business process node operation instance dataset, i.e., an operation BOM; and extracting process usage information, calculating process performance information, and recording process anomaly or deviation information, process change information, etc., based on the operation data of the process instances in the operation BOM to form a diagnostic BOM, thereby completing the establishment of a full lifecycle data architecture for the enterprise process system. This application, through top-down and bottom-up modeling design, manages the entire lifecycle of an enterprise's process system in digital form, from requirements to optimization and improvement. It realizes the element-based and digital transformation of the entire lifecycle of the process system, establishes a data architecture for the entire lifecycle of the enterprise's process system, and enables the definition of process system element data in one place and its reference in multiple places. It supports the full information data management of complex enterprise process system lifecycle processes, and manages and operates enterprise process system elements such as external documents, compliance management, business rules, business processes, and IT development in digital form throughout their entire lifecycle, realizing the enterprise's model-based re-management.

[0069] The above description is only a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A method for establishing a full lifecycle data architecture for an enterprise process system, characterized in that, The following steps are involved: Based on the internal and external requirements of enterprise management, construct a process system requirement dataset and form an element BOM; Based on the actual business classification and processes of the enterprise, a process tree is constructed, and the process nodes are modeled to build the underlying data to form the process BOM; Based on the underlying model of the process nodes in the process BOM, IT development and operation data collection are carried out to form a dataset of business process node operation instances, i.e., the running BOM. Based on the running data of BOM process instances, process usage information is extracted, process performance information is calculated, process anomaly or deviation information and process change information are recorded to form a diagnostic BOM, thereby completing the establishment of the enterprise process system's full lifecycle data architecture.

2. The method for establishing a full lifecycle data architecture for enterprise process systems according to claim 1, characterized in that, After constructing a process system requirements dataset and forming an element BOM based on the internal and external requirements of enterprise management, the method further includes: The document structure is split according to the external requirements to form clause element nodes; The elements of the aforementioned clauses are organized and merged to form compliance element nodes.

3. The method for establishing a full lifecycle data architecture for enterprise process systems according to claim 2, characterized in that, The attributes of the clause element nodes include: document number, document name, business category, responsible department, and document clause. The attributes of the compliance element nodes include: element number, element content, the business category, responsible department, related external document clauses, and recipient.

4. The method for establishing a full lifecycle data architecture for enterprise process systems according to claim 2, characterized in that, After organizing and merging the clause nodes to form compliance element nodes, the method further includes: Based on the receiving object attribute of the compliance element node, connect the compliance element node with the business rule element node or the process element node.

5. The method for establishing a full lifecycle data architecture for enterprise process systems according to claim 4, characterized in that, The attributes of the business rule element nodes include: business rule document number, document name, business category, responsible department, and business rule document clauses.

6. The method for establishing a full lifecycle data architecture for an enterprise process system according to claim 1, characterized in that, Based on the actual business classification and processes of the enterprise, a process tree is constructed, and after modeling the process nodes and building the underlying data to form the process BOM, the method further includes: Connect business rule element nodes and process element nodes based on the receiving object attribute of the business rule element node.

7. The method for establishing a full lifecycle data architecture for enterprise process systems according to claim 4, characterized in that, The dataset of process element nodes includes: process level, process number, process name, parent process, front-end process, back-end process, process owner, responsible department for the process, process performance indicators, process risks, associated compliance element nodes, and associated business rule element nodes.

8. The method for establishing a full lifecycle data architecture for enterprise process systems according to claim 4, characterized in that, The attribute data of the process element nodes include: process definition, process purpose, process start condition, process input, step number, step name, step content, execution role, process output, and process end condition.

9. The method for establishing a full lifecycle data architecture for an enterprise process system according to claim 7, characterized in that, The attribute data of the process performance indicators include: indicator number, indicator name, indicator definition, indicator purpose, calculation formula, unit, indicator dimension, and monitoring frequency.

10. The method for establishing a full lifecycle data architecture for an enterprise process system according to claim 7, characterized in that, The attribute data of the process risk includes: risk number, risk event, risk category, risk occurrence frequency, risk impact degree, risk management strategy, control objective, and control measures.

11. The method for establishing a full lifecycle data architecture for enterprise process systems according to claim 1, characterized in that, The business process node running instance dataset, i.e., the running BOM, includes: business process number, business process name, this process instance number, front-end process instance number, process initiation time, initiator, initiator's department, process step number, step executor, execution start time, execution end time, execution result, and the IT system of the running instance.

12. The method for establishing a full lifecycle data architecture for an enterprise process system according to claim 11, characterized in that, The attribute data of the IT system of the process execution instance includes: IT system number, system name, system module, sub-module, and menu.

13. The method for establishing a full lifecycle data architecture for an enterprise process system according to claim 1, characterized in that, The diagnostic BOM dataset includes: business process number, business process name, process usage frequency, process performance indicators, and process change records.

14. The method for establishing a full lifecycle data architecture for an enterprise process system according to claim 13, characterized in that, The attribute data of the process performance indicators include: indicator number, indicator name, indicator target value, indicator actual value, and indicator result collection date.

15. The method for establishing a full lifecycle data architecture for an enterprise process system according to claim 13, characterized in that, The attribute data of the process change record includes: reason for change, content of change, person who performs the change, person who approves the change, process version, release time, and effective time.

16. A device for establishing a full lifecycle data architecture for an enterprise process system, characterized in that, include: The requirements layer construction module is used to record internal and external document information, split document clauses, and assign clause-receiving departments according to the internal and external requirements of enterprise management. The compliance element layer construction module is used to organize and merge the assigned internal and external document clause nodes to form compliance element nodes, and establish the association between compliance elements and business rule document clause nodes or process element nodes according to the objects to which compliance elements are undertaken. The process element layer construction module is used to build a process tree based on the actual business classification and process of the enterprise, and to model the process nodes to build the underlying data to form the process BOM. It also associates the compliance element nodes and business rule clause nodes with specific process steps / activities or forms and rules. The process execution instance layer construction module is used to perform IT development and operation data collection based on the underlying model of each process element node, and record the business process node execution instance data to form the execution BOM. The process diagnostic layer construction module is used to extract process usage information, calculate process performance information, record process anomaly or deviation information and process change information, and form a diagnostic BOM to complete the establishment of the enterprise process system's full lifecycle data architecture.

17. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is loaded and executed by the processor, it implements the method for establishing a full lifecycle data architecture for an enterprise process system as described in any one of claims 1-15.

18. An electronic device, characterized in that, Including processor and memory, among which, The memory is used to store computer programs; The processor is used to load and execute the computer program so that the electronic device performs the method for establishing a full lifecycle data architecture for an enterprise process system as described in any one of claims 1-15.

Images