Method for dynamic assembly of business process based on disassembly and assembly of detachable components

Abstract

The application discloses a kind of based on disassembling component decomposition and combination service process dynamic assembly method, according to each maintenance service demand, the method for dynamically generating this maintenance service process.Its operation includes service model dynamic creation, process dynamic assembly.It specifically includes node object initialization step;Register object service fragment step;Initialization service boundary step;Explicitly listen to the rule of each object step;Explicit dynamic process arrangement rule step;Process output step;And configuration form data step.The application provides a kind of service process dynamic assembly method, to reduce the dependence on artificial when product maintenance service, to reduce cost, reduce complexity, improve efficiency.

Description

Technical Field

[0001] This invention relates to a method for dynamically assembling business processes based on the decomposition and reassembly of detachable components using a computer, belonging to the field of computer communication technology. Background Technology

[0002] With the development of computer and communication technologies, various industries generally need digital transformation. In the business operations of each industry, the dynamic assembly of business processes is involved. From a technical implementation perspective, most existing technologies still rely on manual construction and maintenance. However, due to the increasing complexity of business processes, dynamic assembly of business processes typically requires significant human resources. For the repair of complex products with numerous parts, the dynamic assembly of business processes is also cumbersome, time-consuming, and requires substantial manpower.

[0003] Taking a subway company as an example, its maintenance of auxiliary inverter box components is relatively complex, involving multiple parts and generally having a relatively fixed product structure, raw material list, and component matching relationships. The maintenance process of auxiliary inverter box components is a complex business process composed of sub-processes of different components, either in parallel or in series, containing more variations and uncertainties. How to construct and maintain the maintenance business of auxiliary inverter box components has become an important issue for subway companies. Component maintenance in the maintenance of auxiliary inverter box components is a key link, involving uncertainties in component maintenance models and maintenance processes, making it a key issue in information technology. Summary of the Invention

[0004] Objective of the Invention: Addressing the problems and shortcomings of existing technologies, this invention first provides a dynamic assembly method for business processes based on the decomposition and reassembly of detachable components, solving the time-consuming and labor-intensive dynamic assembly process for the maintenance of complex products. Furthermore, taking an auxiliary inverter box as an example, this invention provides a dynamic assembly method for business processes.

[0005] Specifically, the maintenance process for different auxiliary reverse gearbox components depends not only on the component's structure (e.g., which sub-components it contains, and which sub-sub-components it contains) but also on maintenance requirements (e.g., to what extent or at what level the maintenance needs to be performed). Fixed processes and fixed maintenance models are insufficient to meet complex and ever-changing business needs. For auxiliary reverse gearbox maintenance scenarios with numerous business elements, complex relationships, and cumbersome business logic, as described above, a dynamic assembly method for the business process based on the decomposition and recombination of detachable components is designed. This allows the maintenance model to be dynamically created based on process data, providing process-oriented guidance to frontline personnel to handle complex maintenance processes. This reduces the complexity and cost of the subway company's auxiliary reverse gearbox maintenance process, improves efficiency, and facilitates the routine operation and maintenance of components with similar structures.

[0006] Technical solution: A dynamic assembly method for business processes based on the decomposition and reassembly of detachable components, mainly including dynamic creation of business models and dynamic assembly of business processes;

[0007] The dynamic creation process of the business model includes the following steps:

[0008] (11) Initialize node objects. Based on the current business requirements, abstract all product components into node objects, and organize the node objects into a multi-branch tree structure according to the hierarchical relationship between node objects.

[0009] (12) Register the business behavior of the registered object. For each node object, register the business segments involved in the corresponding component, that is, all operations that the component can perform, such as maintenance, disassembly, etc., as the business behavior of the node object.

[0010] The dynamic assembly process of the business process mainly includes the following steps:

[0011] (21) Initialize the business boundary. Based on the current business requirements, identify which node objects are the end objects in the multi-branch tree structure, and establish a processing stack to store node objects and a task queue to store task objects.

[0012] (22) Clearly define the listening rules for each node object, that is, declare the behavior rules for the object when the node object enters the processing stack and exits the processing stack;

[0013] (23) Define the dynamic process arrangement rules and dynamically process the node objects in the processing stack to generate task objects and store them in the task queue.

[0014] (24) Process output: Archive and organize the task objects in the task queue and output them as business processes for use by front-line business personnel.

[0015] (25) Configure form data. Each step of the business process output by the workflow is called a workflow node. Different workflow nodes can be configured to be associated with forms, so that front-line business personnel can match the corresponding workflow based on the current component to be processed, and then query the corresponding operation content based on the corresponding form. The form is a form about construction standards and operation methods. After the workflow is dynamically generated, the form and workflow are bound together. The workflow is used to guide what to do, and the form is used to specify how to do it. Each form has its own ID, which is marked on the corresponding workflow step, and this is called association. Alternatively, you can manually indicate how to do it, which is called configuration.

[0016] The product is an auxiliary inverter box. During node object initialization, all auxiliary inverter box components are abstracted into node objects. During business boundary initialization, based on the current business requirements, i.e., the level of components to which the auxiliary inverter box needs to be disassembled for this inspection, it is determined which node objects are the end objects on the multi-branch tree structure for the business requirements.

[0017] The hierarchical relationship between node objects in the dynamic creation of the business model refers to the topological dependency between parent and child objects. In other words, in business requirements, operations on child objects depend on prior business behaviors of the parent objects.

[0018] In the aforementioned business behavior of the registered object, the business segment refers to: for the leaf node object in the node object, its business behavior mainly involves business behavior for itself; for other objects in the node object, it mainly involves business behavior for itself and some business behavior for its child objects.

[0019] A node object refers to an object that is abstracted from specific product components and organized as a type of multi-branch tree node;

[0020] Leaf node objects refer to node objects that have no child objects, i.e., node objects abstracted from components that cannot be further disassembled in actual maintenance.

[0021] The term "terminated object" refers to an object that is no longer decomposed further in a particular maintenance task, based on the clearly defined business boundary of that task. In other words, it is the deepest-level component disassembled in this maintenance task, and its determination is independent of the node object.

[0022] Task objects refer to the business behaviors of node objects output after being processed by the processing stack. In the specific context of this auxiliary inverter box maintenance business, they are business operations targeting specific components, such as disassembling the auxiliary inverter box, and are stored in the task queue.

[0023] The rules for entering and exiting the processing stack are as follows: newly added node objects are added to the top of the processing stack, and newly popped objects are the most recently added node objects; the rules for entering and exiting the task queue are as follows: newly added task objects are located at the end of the task queue, and newly popped task objects are the first objects added.

[0024] In the dynamic assembly method of the business process, the listening rules for each object, that is, the behavior rules for objects when they enter or leave the processing stack, include:

[0025] For terminated objects: when an object is pushed onto the processing stack, its own business behavior is added to the task queue; when an object is removed from the processing stack, the processing stack remains unchanged.

[0026] For non-terminal objects:

[0027] First, for leaf node objects:

[0028] When an object is pushed onto the processing stack, it is considered that the object processing has ended; when an object is popped off the processing stack, it is considered that the object processing has ended.

[0029] Second, for other objects:

[0030] When an object is pushed onto the processing stack, its child objects are added to the processing stack, and the decomposition behavior of the current object is added to the task queue; when an object is popped off the processing stack, the assembly behavior of the current object's child objects and its own business behavior are added to the task queue.

[0031] The dynamic process orchestration rules include initializing the processing stack and processing the processing stack.

[0032] The dynamic process orchestration rules, specifically the initialization of the processing stack, involve adding all objects that do not depend on other objects in the current business behavior proposed by the upstream business to the processing stack and triggering their corresponding listening rules. If this results in more node objects being added to the processing stack, this behavior continues until the processing stack remains unchanged.

[0033] The aforementioned dynamic process orchestration rules, specifically the processing stack behavior, refer to:

[0034] Operation 1: Remove the first object from the processing stack and trigger its listening rule. If this brings more node objects to the processing stack, continue triggering their listening rules until the processing stack remains unchanged. At this point, both the task queue and the processing stack are modified.

[0035] Operation 2: Repeat Operation 1 until the processing stack is empty.

[0036] The form data refers to all business actions for the current component, such as repair, maintenance, and for some components, disassembly and assembly of sub-components. When using the business, the corresponding business action is matched according to the type of component being repaired.

[0037] Beneficial Effects: For the business of disassembled components in discrete manufacturing, most existing technologies rely on manual construction and maintenance of business processes. However, due to the increasing complexity of these processes, existing technologies typically require significant manpower. For the repair of complex products with numerous parts, the dynamic assembly of business processes is also cumbersome, time-consuming, and requires substantial manpower. Using a computer-based method for the dynamic assembly of business processes for the disassembly and reassembly of disassembled components, as described in this invention, can save manpower, improve efficiency, reduce errors, and further promote the informatization process of traditional discrete manufacturing. Each generated process is retained for reuse, review, and maintenance. Simultaneously, the processes generated by this method can standardize the operations of frontline staff and provide technical guidance. Attached Figure Description

[0038] Figure 1 This is a flowchart of a method according to an embodiment of the present invention;

[0039] Figure 2 This is a flowchart of a fine-grained scan of representative objects and their hierarchical relationships in the auxiliary gearbox maintenance business scenario, as described in this embodiment of the invention.

[0040] Figure 3 This is a schematic diagram of a multi-branch tree composed of objects in the auxiliary inverse box part of an embodiment of the present invention;

[0041] Figure 4 This is a schematic diagram of a multi-branch tree class that clearly defines business boundaries in an embodiment of the present invention. Detailed Implementation

[0042] The present invention will be further illustrated below with reference to specific embodiments. It should be understood that these embodiments are for illustrative purposes only and are not intended to limit the scope of the invention. After reading the present invention, any modifications of the present invention in various equivalent forms by those skilled in the art will fall within the scope defined by the appended claims.

[0043] A dynamic assembly method for business processes based on the decomposition and recombination of detachable components is disclosed. For ease of understanding and explanation, this method primarily uses the maintenance of auxiliary and reverse gearboxes in a subway company, a discrete manufacturing enterprise, as an example, but this is not limiting. The technology disclosed herein can be applied to any suitable scenario in various other industries.

[0044] The following describes the overall process of the dynamic assembly method for business processes based on the disassembly and reassembly of detachable components according to embodiments of the present disclosure. Figure 1An exemplary flowchart of a dynamic assembly method for business processes based on the decomposition and assembly of disassembled components according to an embodiment of the present disclosure is shown. Preferably, the dynamic assembly method 100 for business processes based on the decomposition and assembly of disassembled components according to an embodiment of the present disclosure is divided into a dynamic model creation step S100A and a dynamic process assembly step S100B, wherein the dynamic model creation step S100A may include the following steps S110 to S120, and the dynamic process arrangement step S100B may include the following steps S130 to S170. Details of each step S110 to S170 are as follows:

[0045] Node object initialization S110: For each detachable component that may be involved in the process to be orchestrated, it is abstracted into a node object, and according to its hierarchical relationship (child objects are decomposed from parent objects), the node objects are organized into a multi-branch tree structure.

[0046] Register object business behavior S120: For each node object, register the business segments involved in its original components as node object business behaviors.

[0047] Initialize the business boundary S130. Based on the current business requirements, i.e., the level of components to which the auxiliary reverse box needs to be disassembled in this maintenance operation, determine which node objects are the end objects in the multi-branch tree structure, and establish a processing stack to store node objects and a task queue to store task objects.

[0048] Define the listening rules S140 for each object, that is, define the behavior rules for each node object when the node object enters and exits the processing stack;

[0049] Define the dynamic process orchestration rules S150, and dynamically process the node objects in the processing stack to generate task objects and store them in the task queue.

[0050] The process output S160 archives and organizes the task objects in the task queue and outputs them as a business process for front-line business personnel, namely the operators who specifically carry out the maintenance and repair of product components.

[0051] Configure form data S170. Different process nodes can be associated with forms through configuration, so that front-line business personnel can match the corresponding process according to the current pending components, and then query the corresponding operation content according to each step in the process.

[0052] Next, to make this disclosure easier to understand, we will take the maintenance of auxiliary inverter boxes, a specific example encountered in discrete manufacturing, as an example. Figure 2As shown, the auxiliary inverter box is a detachable component. Based on the dynamic assembly method of the business process in this embodiment, a dynamic assembly method for the maintenance business process is given, which specifically includes the following steps:

[0053] In step S110, taking the auxiliary reverse gear box as an example of a detachable component, it is first abstracted as a node object. Since processing (maintaining) the auxiliary reverse gear box does not depend on any prior business behavior of any object, it is the parent object. Furthermore, because the business behavior (maintenance) of the box body depends on the business behavior of disassembling the auxiliary reverse gear box downwards, the components to be disassembled downwards are child objects of the auxiliary reverse gear box object. This downward disassembly behavior is repeated until all detachable components are abstracted as node objects. After this step is completed, the following can be obtained: Figure 3 The auxiliary inverse box multi-way tree object model shown has some simplified elements.

[0054] In step S120, in the actual business of a discrete manufacturing subway company, different detachable components have specific behaviors, such as maintenance, replacement, disassembly, and assembly of sub-objects. In this step, specific business segments of the detachable components need to be injected into the multi-branch tree object model generated in step S110. It is important to note that objects at the leaf nodes of the multi-branch tree, such as boxes, do not have the business behavior of disassembly.

[0055] In implementation step S130, frontline business personnel, based on business needs, clarify the level to be decomposed, i.e., the business boundary, specifically identifying which objects are the final objects. We take the business boundary as a box, optical fiber, capacitors C1-C6, and diodes as an example. Based on business needs, frontline business personnel mark some objects in the auxiliary inverse box multi-branch tree model as final objects. Simultaneously, a processing stack and a task queue are established. The processing stack is a last-in-first-out restricted linear list, and the task queue is a first-in-first-out restricted linear list. The processing stack stores node objects to be processed, and the task queue stores specific business behaviors for a particular object, i.e., task objects. The task queue as a whole can be considered an incomplete process.

[0056] Note: In the previous steps, objects were categorized into different levels and further divided into terminated objects and non-terminated objects. These two categories are not necessarily related. The former is determined by the dependencies between objects, while the latter is determined by frontline business personnel during the specific business process.

[0057] Implement step S140 to define the listening rules for each object. Because the entire process is dynamically assembled, the processing of each object is reactive.

[0058] For all terminated objects, in this embodiment, these are the enclosure, optical fiber, capacitors C1-C6, and diode. When an object enters the processing stack, its own business behavior is added to the end of the process processing queue. When an object exits the processing stack, an identity transformation is performed on the process processing stack, i.e., it remains unchanged.

[0059] Leaf node objects in non-terminal objects are not included in this embodiment, and their behavior in and out of the processing stack is defined the same as that of terminal objects.

[0060] For other objects, namely the secondary inverse box (module A11), when an object is pushed onto the processing stack, its child objects are also added to the processing stack. Furthermore, based on the downward decomposition behavior of the current object, it is added to the task queue.

[0061] In step S150, the specific behavior of initializing the processing stack is as follows: All objects in the current business action proposed by the upstream business that do not depend on other objects (i.e., all objects that are not sub-objects of any object; in this case, the auxiliary inverse box) are added to the processing stack. Adding the auxiliary inverse box object to the processing stack triggers the monitoring rules for the auxiliary inverse box object, adding the disassembly behavior of the auxiliary inverse box to the task queue, and simultaneously adding its sub-objects, the box body, the fiber optic cable, and the A11 module to the processing stack. Because the A11 module is another object, adding it to the processing stack triggers the monitoring rules for it, adding its sub-objects, capacitors C1-C6 and diodes, to the processing stack, and simultaneously adding the disassembly behavior of its A11 module to the task queue.

[0062] After the processing stack is initialized, processing begins. At this point, the processing stack contains diodes, capacitors C1-C6, the enclosure, the optical fiber, module A11, and the auxiliary inverter box. The task queue contains the disassembly actions for the auxiliary inverter box and the disassembly actions for module A11. When the processing stack is not empty, processing continues on the first element in the processing stack.

[0063] The diode object, being both the underlying and final object, is added to the task queue along with its business logic. The diode object is then popped from the processing stack.

[0064] When processing capacitors C1-C6, since they are low-level and end objects, their business logic is added to the task queue. The capacitors C1-C6 objects are then popped from the processing stack.

[0065] When processing module A11, since it is a different object, its behavior of assembling sub-objects and its own business behavior are added to the task queue, and module A11 is popped from the processing stack.

[0066] When processing fiber optics, since they are end objects, their business behavior is added to the task queue, and the fiber optic object is popped from the processing stack.

[0067] The processing container, being both the underlying and final object, has its business logic added to the task queue. The container object is then popped from the processing stack.

[0068] When processing the secondary inverse box, since it is another object, its assembly of sub-objects and its own business behavior are added to the task queue, and the secondary inverse box module is popped from the processing stack.

[0069] At this time, the processing stack is empty, and the task queue is disassembling the auxiliary inverter box, disassembling the A11 module, maintaining the diode, maintaining capacitors C1-C6, assembling the A11 module, maintaining the A11 module, maintaining the optical fiber, maintaining the enclosure, assembling the auxiliary inverter box, and maintaining the auxiliary inverter box. This is exactly the process required by front-line business personnel.

[0070] For ease of understanding, the changes in the processing stack and task queue for each step in S150 are presented in tabular form. It's important to note that, for clarity, the triggering of the listening rule and the entry of the node object into the processing stack are separated into two steps; however, the triggering of the listening rule and the popping of the node object from the stack due to processing the node object are combined into one step. In actual operation, it should be reactive, so they are all implemented as one step. Furthermore, each decomposable business behavior is represented here by maintenance. The specific process of step S150 is shown in Table 1 below.

[0071] Table 1

[0072]

[0073]

[0074] Implement step S160 to output the tasks in the task queue.

[0075] In step S170, configure the form data. Different process nodes can be associated with form IDs through configuration. When using the system, users match the corresponding maintenance process based on the type of component being inspected, and then query the corresponding maintenance form content based on each step in the process. For example, the specific maintenance steps for the auxiliary reverse gearbox module are shown in Table 2. At this point, the process is relatively complete. Frontline staff match the corresponding process based on the current business object, and then query the corresponding operation content based on each step in the process. Table 2 shows a simplified version of the form matched for the specific maintenance of the auxiliary reverse gearbox module.

[0076] Table 2

[0077]

[0078]

Claims

1. A dynamic assembly method for business processes based on the decomposition and reassembly of detachable components, characterized in that, This includes dynamic creation of business models and dynamic assembly of business processes; The dynamic creation process of the business model includes the following steps: (11) Initialize node objects. Based on the current business requirements, abstract all product components into node objects, and organize the node objects into a multi-branch tree structure according to the hierarchical relationship between node objects. (12) Register the business behavior of the registered object. For each node object, register the business segments involved in its corresponding component, that is, all operations that the component can perform, as the business behavior of the node object. The dynamic assembly process of the business process includes the following steps: (21) Initialize the business boundary. Based on the current business requirements, determine which node objects are the end objects in the multi-branch tree structure for the business requirements, and establish a processing stack to store node objects and a task queue to store task objects. (22) Clearly define the listening rules for each node object, that is, declare the behavior rules for the object when the node object enters the processing stack and exits the processing stack; (23) Clarify the dynamic process arrangement rules, and dynamically process the node objects in the processing stack to generate task objects and store them in the task queue; (24) Process output: Archive and organize the task objects in the task queue and output them as business processes for use by front-line business personnel. (25) Configure form data. Different process nodes can be associated with forms so that front-line business personnel can match the corresponding process according to the current components to be processed, and then query the corresponding operation content according to the corresponding form.

2. The dynamic assembly method for business processes based on the decomposition and reassembly of detachable components as described in claim 1, characterized in that, The product is an auxiliary inverter box. During node object initialization, all auxiliary inverter box components are abstracted into node objects. During business boundary initialization, based on the current business requirements, i.e., the level of components to which the auxiliary inverter box needs to be disassembled for this inspection, it is determined which node objects are the end objects on the multi-branch tree structure for the business requirements.

3. The dynamic assembly method for business processes based on the decomposition and reassembly of detachable components according to claim 1, characterized in that, The hierarchical relationship between node objects in the dynamic creation of the business model refers to the topological dependency between parent and child objects. In other words, in business requirements, operations on child objects depend on prior business behaviors of the parent objects.

4. The dynamic assembly method for business processes based on the decomposition and reassembly of detachable components as described in claim 1, characterized in that, In the aforementioned business behavior of the registered object, the business segment refers to: for the leaf node object in the node object, its business behavior mainly involves business behavior for itself; for other objects in the node object, it involves business behavior for itself and some business behavior for its child objects.

5. The dynamic assembly method for business processes based on the decomposition and reassembly of detachable components according to claim 1, characterized in that, A node object refers to an object that is abstracted from specific product components and organized as a type of multi-branch tree node; Leaf node objects refer to node objects that have no child objects, i.e., node objects abstracted from components that cannot be further disassembled in actual maintenance. The term "terminated object" refers to an object that is no longer decomposed further in a particular maintenance task, based on the clearly defined business boundary of that task. In other words, it is the deepest-level component disassembled in this maintenance task, and its determination is independent of the node object. Task objects refer to the business behaviors of node objects output after being processed by the processing stack. In the specific context of this auxiliary inverter box maintenance business, they are business operations targeting specific components and stored in the task queue.

6. The dynamic assembly method for business processes based on the decomposition and reassembly of detachable components according to claim 1, characterized in that, The rules for entering and exiting the processing stack are as follows: newly added node objects are added to the top of the processing stack, and newly popped objects are the most recently added node objects; the rules for entering and exiting the task queue are as follows: newly added task objects are located at the end of the task queue, and newly popped task objects are the first objects added.

7. The dynamic assembly method for business processes based on the decomposition and reassembly of detachable components according to claim 1, characterized in that, In the dynamic assembly method of the business process, the listening rules for each object, that is, the behavior rules for objects when they enter or leave the processing stack, include: For terminated objects: when an object is pushed onto the processing stack, its own business behavior is added to the task queue; when an object is removed from the processing stack, the processing stack remains unchanged. For non-terminal objects: First, for leaf node objects: When an object is pushed onto the processing stack, it is considered as if the object processing has ended; when an object is popped off the processing stack, it is considered as if the object processing has ended. Second, for other objects: When an object is pushed onto the processing stack, its child objects are added to the processing stack, and the decomposition behavior of the current object is added to the task queue; when an object is popped off the processing stack, the assembly behavior of the current object's child objects and its own business behavior are added to the task queue.

8. The dynamic assembly method for business processes based on the decomposition and reassembly of detachable components according to claim 1, characterized in that, The dynamic process orchestration rules include initializing the processing stack and processing the processing stack. The specific behavior of initializing the processing stack is as follows: all objects that do not depend on other objects in the current business behavior proposed by the upstream business are added to the processing stack, and their corresponding listening rules are triggered. If more node objects are added to the processing stack, this behavior continues until the processing stack remains unchanged.

9. The dynamic assembly method for business processes based on the decomposition and reassembly of detachable components according to claim 8, characterized in that, The dynamic process orchestration rules, specifically the processing stack behavior, refer to: Operation 1: Remove the first object from the processing stack and trigger its listening rule. If this brings more node objects to the processing stack, continue triggering their listening rules until the processing stack remains unchanged. At this point, both the task queue and the processing stack are modified. Operation 2: Repeat Operation 1 until the processing stack is empty.

10. The dynamic assembly method for business processes based on the decomposition and reassembly of detachable components according to claim 1, characterized in that, The form data refers to all business activities for the current component, including repair, maintenance, and for some components, disassembly and assembly of sub-components. When using the business, the corresponding business activity is matched according to the type of component being repaired.

Images