CN112799651A - Event-driven electronic batch recording system - Google Patents

Event-driven electronic batch recording system Download PDF

Info

Publication number
CN112799651A
CN112799651A CN202110151416.3A CN202110151416A CN112799651A CN 112799651 A CN112799651 A CN 112799651A CN 202110151416 A CN202110151416 A CN 202110151416A CN 112799651 A CN112799651 A CN 112799651A
Authority
CN
China
Prior art keywords
design
flow
event
service
name
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202110151416.3A
Other languages
Chinese (zh)
Other versions
CN112799651B (en
Inventor
岳磊
牛鹏飞
闫晓风
王钧
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Instrumentation Technology And Economy Institute P R China
Original Assignee
Instrumentation Technology And Economy Institute P R China
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Instrumentation Technology And Economy Institute P R China filed Critical Instrumentation Technology And Economy Institute P R China
Priority to CN202110151416.3A priority Critical patent/CN112799651B/en
Publication of CN112799651A publication Critical patent/CN112799651A/en
Application granted granted Critical
Publication of CN112799651B publication Critical patent/CN112799651B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/30Creation or generation of source code
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/21Design, administration or maintenance of databases
    • G06F16/211Schema design and management
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02PCLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/30Computing systems specially adapted for manufacturing

Abstract

The invention discloses an event-driven electronic batch recording system. In the invention, the MES product functions designed by applicability and expandability have expandability, can be continuously expanded along with the gradual improvement of application and the gradual increase of users (including member units and the public), and the whole system can be smoothly transited to a new system after being upgraded. Meanwhile, in the development of a software system, the reusability of each functional module is considered, so that the complexity of system expansion is reduced; the MES product design adopts a componentized design concept, the whole system adopts a componentized service design, and by adopting a unified standard interface specification, the expansion of a software system and the addition of other subsystems in future are facilitated, and the maintainability and the expansibility of the product are improved; the design scheme is based on an advanced technology, and adopts an advanced field design concept, an SOA technical route and a technical system architecture, so that the project has a leading domestic position.

Description

Event-driven electronic batch recording system
Technical Field
The invention belongs to the technical field of event processing, and particularly relates to an event-driven electronic batch recording system.
Background
MES is composed of MES Framework and MES Components, wherein MES Framework is a platform modeling center and MES Components is an industry library suite center. MES is a whole set of industrial basic management platform developed specially for production execution in the intelligent manufacturing industry; the MES Framework modeling center is an industrial product knowledge base constructed based on ISA-95 committee specification standards; MES Components are production management suites that we custom-make for each domain of the MES industry.
However, when a common system is used, the security is generally not high, and a uniform standard interface specification is not adopted, so that the software system is inconvenient to expand and add other subsystems.
Disclosure of Invention
The invention aims to: to solve the above-mentioned proposed problems, an event-driven electronic batch recording system is provided.
The technical scheme adopted by the invention is as follows: an event-driven electronic batch recording system, comprising the steps of:
s1, firstly, designing an architecture: design the external entities (other systems, devices and people) and the nature of the interaction with the target system, and the environment in which the target system operates. The manner in which software interacts with external entities is typically modeled with an architectural environment diagram. The system that interacts with the target system can be represented as: a superior system, an inferior system, a peer system, and a participant;
s2, the designer divides the module according to the service requirement contained in the component, forms the module list and confirms the corresponding relation between the module and the requirement;
s3, designing module, defining main function of module; the logic flow of the module is represented by an Excel chart (such as a flow chart and the like) with necessary description, and the flow chart is described; the characteristics of each input parameter are given, including name, identification, type and format of data, valid range of data value, and input mode. Giving out the characteristics of each output parameter, including name, identification, data type and format, effective range of data value, output form, output medium, and description of output graph and symbol; including the calculation of formulas and descriptions, certain set or necessary logical relationships. For functions, the emphasis is put on; establishing a data table structure, indexes and the like according to the data design specification, and carrying out optimization design to form a database design specification;
s4, after defining the design rule of the database, constructing a CMES platform; the service construction of the platform framework comprises the construction of an abstract model under the condition that no specific service is contained, the constructed design idea does not contain specific service components, the specific implementation requirement is that the atomic service center establishes a domain concept model, the message driving center instantiates the model concept, namely when the atomic service center construction is designed, the message driving center runs, the messages in running are divided into different types of messages to be issued to the outside, and subscribers can selectively select response events;
s5, creating a new flow example; service scene: a flow creation person logs in a workflow design tool; clicking a new button, inputting a key value of the flow in a popped new window, wherein the key value needs to ensure uniqueness; the system checks whether the key value is unique, and if the key value is unique, the system prompts the success of new establishment;
s6, defining the flow activity starting point, the flow node and the flow ending node, and opening the existing flow
Describing relevant elements of the current process, including a process key, an application name, a module name, a process name, creation time and modification time; storing the flow; clicking a storage button to make data persistence on the current edited flow in an XML format;
s7, the current node needs to communicate with the links and tells the resource address or URL; i.e., communicate with those forms, including link key, name, availability, description, category, OpUrl; displaying the linked list statistics at the same time; dispatch notifier pages; the organization structure chart completes the configuration of the organization structure of the personnel by using the organization tree of the personnel in the unified authority; the resource selection is mainly the selection of organization structure personnel;
s8, a variable editing page; namely, self-defining of variables, defining a self-defining data column required by the current flow; such as forms, URLs, jump pages, related resource information relating to the current activity;
s9, each activity node has an activity node entry point and an output point after being defined, the action page setting for linking the exit of the current node and the entrance of the next node, namely completing the adding rule, is the setting of the expression, and the format must be the Boolean value format;
s10, clicking the pop-up menu of the active icon by right click to click the newly-built sub-process editor, inputting process information, and selecting the blocking type and whether the current process is serial or parallel;
and S11, dynamically loading the events to be executed by using a reflection-type System.
In a preferred embodiment, in the step S1, the content in the structural model inside the design target system is refined into components; the components are divided into service components and infrastructure components, the service components come from the service field, and the infrastructure components have no service connection with the service field and provide operation support for the service components; the designer should follow the following principles when dividing the component: the function is relatively independent; low coupling, high cohesion principle; independent delivery principles are possible; seamless assembly and reuse principles among components; the main output of the architecture design is a software architecture diagram, which comprises a data architecture and a program structure; a designer gives a detailed description of each part in the software architecture diagram; since the system is based on the FKS platform architecture system, all the factors are completely considered according to the stage of design work, and the design is not needed again.
In a preferred embodiment, in step S2, the module should be split according to the following basic principle: the module is proper in size when being cut and has a clear module structure; generally, the functions of the split modules are required to be relatively independent and complete; defining reasonable dependency relationship among modules; the reasonable module dependence relationship is determined in the design stage, so that more reasonable arrangement of project plans is facilitated; duplicate work is eliminated as much as possible and common modules are built to reduce redundancy.
In a preferred embodiment, in step S4, the process center is also a building of an abstract model, the building design concept is not dependent on any service, and is also a building of an abstract model, the process center is designed with two major elements, one major element is a process design work, and the other major element is a process operation work; when the process design is carried out, namely the process design, the function definition during the design comprises the definition of the elements of the process definition, the process description, the attribute definition, the resource definition, the variable management and the activity definition in the process design, so that the description during the design is realized; and similarly, flow operation and flow operation, wherein the flow operation comprises flow starting, task pending and BPM flow list to realize the management of the working state of the flow in operation.
In a preferred embodiment, the step S8 includes a variable key, a variable name, a value object, a description, and a variable type; and displaying the variable list after saving.
In a preferred embodiment, in step S8, process information is set, and the process editing page includes a process key, a name, a description, whether to use, an application name (approval), a process type (approval process), a form address, and an automatically generated activity dispatcher (True/False).
In a preferred embodiment, in step S9, the user logs in to the workflow design tool, enters a process editing page, and the user clicks an activity in the process editing area, and the system displays the V attribute of the current connection line in the attribute editing area; editing the attribute of the connecting line by a user, and finishing the unified saving of the process through the saving function of the process editing; setting conditions: the system is used for clicking a certain connecting line in the process editing area and popping up an active condition setting page by a floating menu clicking system; the page elements include: and storing the key, the name, the value, the condition description and the numerical value type into a database after the key, the name, the value, the condition description and the numerical value type are stored.
In a preferred embodiment, in step S10, the specific list information includes: flow key, sub-flow name, blocking type: waiting for all branch flows to complete 2: any branching flow does not wait for 3: wait for any branch flow to complete 4: wait for certain branch flows to complete), serial/parallel; and clicking to save the database.
In a preferred embodiment, in step S11, the developer only needs to find the corresponding command according to the scenario GUID selected and set by the user.
In a preferred embodiment, in step S11, if it is an event, the user selects that event and publishes that event, the event is published in the message queue, and the developer only needs to subscribe to the corresponding event according to the event ID set by the user.
In summary, due to the adoption of the technical scheme, the invention has the beneficial effects that:
1. in the invention, the MES product functions designed by applicability and expandability have expandability, can be continuously expanded along with the gradual improvement of application and the gradual increase of users (including member units and the public), and the whole system can be smoothly transited to a new system after being upgraded. Meanwhile, in the development of a software system, the reusability of each functional module is considered, so that the complexity of system expansion is reduced; the MES product design adopts a componentized design concept, the whole system adopts a componentized service design, and by adopting a unified standard interface specification, the expansion of a software system and the addition of other subsystems in future are facilitated, and the maintainability and the expansibility of the product are improved; the design scheme is based on an advanced technology, and adopts advanced field design concepts, SOA technical routes and technical system architectures, so that the project has a leading status in China, and the characteristics of long service cycle and high performance index of the built system are ensured; the area sharing exchange platform has great stability and reliability, and with the increase of information exchange and sharing requirements of the industry library, it is very important to adopt a development technology and a design scheme which are mature in technology, highly reliable, safe and stable, and the MES can ensure the normal operation of the whole system and can cope with the expected abnormal conditions.
2. In the invention, the security of the MES is a highlight of the product, when the product is designed, various security technical means such as message data packet encryption, issued service header encryption, data key encryption, single sign-on authentication, domain server authentication and event issuing subscription monitoring are adopted in the aspect of software design, and a firewall at a hardware server end is provided with an IPS intrusion prevention system, flow control, VPN, audit alarm and the like to ensure tight protection of a related application database; the platform uses the message driving architecture to ensure that the system has good platform portability and can stably and reliably run on various platforms. The service can be reissued to run normally on the premise that the corresponding platform is not modified basically; the MES design fully considers the principle of 'standard and open', adopts the design concept of message service drive, and uses the message flow as the content message packet to support various corresponding software and hardware interfaces, so that the MES has high flexibility and high extensibility, has the characteristic of interconnection and intercommunication with various systems, realizes real open in structure, is convenient for interconnection and expansion with other systems, is easy to realize migration to the advanced technology in the future, fully protects the existing systems of users, and comprehensively reflects the portability, interoperability, system independence and integration.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the embodiments of the present invention, and it is obvious that the described embodiments are some embodiments of the present invention, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
An event-driven electronic batch recording system, comprising the steps of:
s1, firstly, designing an architecture: design the external entities (other systems, devices and people) and the nature of the interaction with the target system, and the environment in which the target system operates. The manner in which software interacts with external entities is typically modeled with an architectural environment diagram. The system that interacts with the target system can be represented as: a superior system, an inferior system, a peer system, and a participant; in step S1, refining the content in the structural model inside the design target system into a component; the components are divided into service components and infrastructure components, the service components come from the service field, and the infrastructure components have no service connection with the service field and provide operation support for the service components; the designer should follow the following principles when dividing the component: the function is relatively independent; low coupling, high cohesion principle; independent delivery principles are possible; seamless assembly and reuse principles among components; the main output of the architecture design is a software architecture diagram, which comprises a data architecture and a program structure; a designer gives a detailed description of each part in the software architecture diagram; because the system is based on an FKS platform architecture system, all the factors are completely considered according to the stage of design work, and the design is not needed again;
s2, the designer divides the module according to the service requirement contained in the component, forms the module list and confirms the corresponding relation between the module and the requirement; in step S2, the module segmentation should consider the following basic principles: the module is proper in size when being cut and has a clear module structure; generally, the functions of the split modules are required to be relatively independent and complete; defining reasonable dependency relationship among modules; the reasonable module dependence relationship is determined in the design stage, so that more reasonable arrangement of project plans is facilitated; duplicate work is eliminated as much as possible, and a common module is established to reduce redundancy;
s3, designing module, defining main function of module; the logic flow of the module is represented by an Excel chart (such as a flow chart and the like) with necessary description, and the flow chart is described; the characteristics of each input parameter are given, including name, identification, type and format of data, valid range of data value, and input mode. Giving out the characteristics of each output parameter, including name, identification, data type and format, effective range of data value, output form, output medium, and description of output graph and symbol; including the calculation of formulas and descriptions, certain set or necessary logical relationships. For functions, the emphasis is put on; establishing a data table structure, indexes and the like according to the data design specification, and carrying out optimization design to form a database design specification;
s4, after defining the design rule of the database, constructing a CMES platform; the service construction of the platform framework comprises the construction of an abstract model under the condition that no specific service is contained, the constructed design idea does not contain specific service components, the specific implementation requirement is that the atomic service center establishes a domain concept model, the message driving center instantiates the model concept, namely when the atomic service center construction is designed, the message driving center runs, the messages in running are divided into different types of messages to be issued to the outside, and subscribers can selectively select response events; in the step S4, the process center is also a building of an abstract model, the building design concept is not dependent on any service, and is also a building of an abstract model, the process center is designed with two major elements, one major element is process design work, and the other major element is process operation work; when the process design is carried out, namely the process design, the function definition during the design comprises the definition of the elements of the process definition, the process description, the attribute definition, the resource definition, the variable management and the activity definition in the process design, so that the description during the design is realized; similarly, the process operation and the process operation are carried out, wherein the process operation comprises process starting, task waiting and BPM process list to realize the management of the working state of the process in the operation process;
s5, creating a new flow example; service scene: a flow creation person logs in a workflow design tool; clicking a new button, inputting a key value of the flow in a popped new window, wherein the key value needs to ensure uniqueness; the system checks whether the key value is unique, and if the key value is unique, the system prompts the success of new establishment; in step S8, the variable key, the variable name, the value object, the description, and the variable type are included; displaying the variable list after storage;
s6, defining the flow activity starting point, the flow node and the flow ending node, and opening the existing flow
Describing relevant elements of the current process, including a process key, an application name, a module name, a process name, creation time and modification time; storing the flow; clicking a storage button to make data persistence on the current edited flow in an XML format;
s7, the current node needs to communicate with the links and tells the resource address or URL; i.e., communicate with those forms, including link key, name, availability, description, category, OpUrl; displaying the linked list statistics at the same time; dispatch notifier pages; the organization structure chart completes the configuration of the organization structure of the personnel by using the organization tree of the personnel in the unified authority; the resource selection is mainly the selection of organization structure personnel;
s8, a variable editing page; namely, self-defining of variables, defining a self-defining data column required by the current flow; such as forms, URLs, jump pages, related resource information relating to the current activity; in step S8, process information is set, and a process editing page includes a process key, a name, a description, whether to use, an application name (approval), a process type (approval process), a form address, and an automatically generated activity dispatcher (True/False);
s9, each activity node has an activity node entry point and an output point after being defined, the action page setting for linking the exit of the current node and the entrance of the next node, namely completing the adding rule, is the setting of the expression, and the format must be the Boolean value format; in step S9, the user logs in to the workflow design tool, enters a process editing page, and the user clicks a certain activity in the process editing area, and the system displays the V attribute of the current connection line in the attribute editing area; editing the attribute of the connecting line by a user, and finishing the unified saving of the process through the saving function of the process editing; setting conditions: the system is used for clicking a certain connecting line in the process editing area and popping up an active condition setting page by a floating menu clicking system; the page elements include: storing the key, the name, the value, the condition description and the numerical value type into a database after the key, the name, the value, the condition description and the numerical value type are stored;
s10, clicking the pop-up menu of the active icon by right click to click the newly-built sub-process editor, inputting process information, and selecting the blocking type and whether the current process is serial or parallel; in step S10, the specific list information includes: flow key, sub-flow name, blocking type: waiting for all branch flows to complete 2: any branching flow does not wait for 3: wait for any branch flow to complete 4: wait for certain branch flows to complete), serial/parallel; clicking a storage database; MES product functions designed according to applicability and expandability have expandability, and can be continuously expanded along with gradual improvement of applications and gradual increase of users (including member units and the public), and the whole system can be smoothly transited to an upgraded new system. Meanwhile, in the development of a software system, the reusability of each functional module is considered, so that the complexity of system expansion is reduced; the MES product design adopts a componentized design concept, the whole system adopts a componentized service design, and by adopting a unified standard interface specification, the expansion of a software system and the addition of other subsystems in future are facilitated, and the maintainability and the expansibility of the product are improved; the design scheme is based on an advanced technology, and adopts advanced field design concepts, SOA technical routes and technical system architectures, so that the project has a leading status in China, and the characteristics of long service cycle and high performance index of the built system are ensured; the area sharing exchange platform has important stable and reliable relation, and with the increase of information exchange and sharing requirements of an industry library, it is very important to adopt a development technology and a design scheme which are mature in technology, highly reliable, safe and stable, and an MES can guarantee the normal operation of the whole system and can cope with the expected abnormal condition;
s11, dynamically loading the event to be executed by using a reflection system reflection dynamic method; in step S11, the developer only needs to find the corresponding command according to the scene GUID selected and set by the user to execute the command; in step S11, if it is an event, when the user is in a custom design, the platform already selects the event according to the user behavior, and issues the event, the event in the message queue is issued, and the developer waits for subscription all the time, and only needs to subscribe to the corresponding event according to the event ID set by the user; the MES security is a bright spot of the product, when the product is designed, various security technical means such as message data packet encryption, issued service header encryption, data key encryption, single sign-on authentication, domain server authentication and event issuing subscription monitoring are adopted in the aspect of software design, an IPS intrusion prevention system, flow control, VPN, audit alarm and the like are arranged on a firewall at a hardware server end to ensure, and the related application database is strictly protected; the platform uses the message driving architecture to ensure that the system has good platform portability and can stably and reliably run on various platforms. The service can be reissued to run normally on the premise that the corresponding platform is not modified basically; the MES design fully considers the principle of 'standard and open', adopts the design concept of message service drive, and uses the message flow as the content message packet to support various corresponding software and hardware interfaces, so that the MES has high flexibility and high extensibility, has the characteristic of interconnection and intercommunication with various systems, realizes real open in structure, is convenient for interconnection and expansion with other systems, is easy to realize migration to the advanced technology in the future, fully protects the existing systems of users, and comprehensively reflects the portability, interoperability, system independence and integration.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.

Claims (10)

1. An event-driven electronic batch recording system, characterized by: the event-driven electronic batch recording system comprises the following steps:
s1, firstly, designing an architecture: designing external entities (other systems, devices and people) interacting with the target system and characteristics of interaction, and an environment in which the target system operates, modeling a way in which software interacts with the external entities by using an architecture environment diagram generally, and a system interacting with the target system can be represented as follows: a superior system, an inferior system, a peer system, and a participant;
s2, the designer divides the module according to the service requirement contained in the component, forms the module list and confirms the corresponding relation between the module and the requirement;
s3, designing module, defining main function of module; the logic flow of the module is represented by an Excel chart (such as a flow chart and the like) with necessary description, and the flow chart is described; giving out the characteristics of each input parameter, including name, identification, data type and format, effective range of data value and input mode, giving out the characteristics of each output parameter, including name, identification, data type and format, effective range of data value, output form, output medium and description of output graph and symbol; the method comprises the steps of calculating formulas and descriptions, and certain set or necessary logical relations, wherein for functions, emphasis is placed; establishing a data table structure, indexes and the like according to the data design specification, and carrying out optimization design to form a database design specification;
s4, after defining the design rule of the database, constructing a CMES platform; the service construction of the platform framework comprises the construction of an abstract model under the condition that no specific service is contained, the constructed design idea does not contain specific service components, the specific implementation requirement is that the atomic service center establishes a domain concept model, the message driving center instantiates the model concept, namely when the atomic service center construction is designed, the message driving center runs, the messages in running are divided into different types of messages to be issued to the outside, and subscribers can selectively select response events;
s5, creating a new flow example; service scene: a flow creation person logs in a workflow design tool; clicking a new button, inputting a key value of the flow in a popped new window, wherein the key value needs to ensure uniqueness; the system checks whether the key value is unique, and if the key value is unique, the system prompts the success of new establishment;
s6, defining the flow activity starting point, the flow node and the flow ending node, and opening the existing flow
Describing relevant elements of the current process, including a process key, an application name, a module name, a process name, creation time and modification time; storing the flow; clicking a storage button to make data persistence on the current edited flow in an XML format;
s7, the current node needs to communicate with the links and tells the resource address or URL; i.e., communicate with those forms, including link key, name, availability, description, category, OpUrl; displaying the linked list statistics at the same time; dispatch notifier pages; the organization structure chart completes the configuration of the organization structure of the personnel by using the organization tree of the personnel in the unified authority; the resource selection is mainly the selection of organization structure personnel;
s8, a variable editing page; namely, self-defining of variables, defining a self-defining data column required by the current flow; such as forms, URLs, jump pages, related resource information relating to the current activity;
s9, each activity node has an activity node entry point and an output point after being defined, the action page setting for linking the exit of the current node and the entrance of the next node, namely completing the adding rule, is the setting of the expression, and the format must be the Boolean value format;
s10, clicking the pop-up menu of the active icon by right click to click the newly-built sub-process editor, inputting process information, and selecting the blocking type and whether the current process is serial or parallel;
and S11, dynamically loading the events to be executed by using a reflection-type System.
2. An event-driven electronic batch recording system as claimed in claim 1, wherein: in step S1, refining the content in the structural model inside the design target system into components; the components are divided into service components and infrastructure components, the service components come from the service field, and the infrastructure components have no service connection with the service field and provide operation support for the service components; the designer should follow the following principles when dividing the component: the function is relatively independent; low coupling, high cohesion principle; independent delivery principles are possible; seamless assembly and reuse principles among components; the main output of the architecture design is a software architecture diagram, which comprises a data architecture and a program structure; a designer gives a detailed description of each part in the software architecture diagram; since the system is based on the FKS platform architecture system, all the factors are completely considered according to the stage of design work, and the design is not needed again.
3. An event-driven electronic batch recording system as claimed in claim 1, wherein: in step S2, the module segmentation should consider the following basic principles: the module is proper in size when being cut and has a clear module structure; generally, the functions of the split modules are required to be relatively independent and complete; defining reasonable dependency relationship among modules; the reasonable module dependence relationship is determined in the design stage, so that more reasonable arrangement of project plans is facilitated; duplicate work is eliminated as much as possible and common modules are built to reduce redundancy.
4. An event-driven electronic batch recording system as claimed in claim 1, wherein: in the step S4, the process center is also a building of an abstract model, the building design concept is not dependent on any service, and is also a building of an abstract model, the process center is designed with two major elements, one major element is process design work, and the other major element is process operation work; when the process design is carried out, namely the process design, the function definition during the design comprises the definition of the elements of the process definition, the process description, the attribute definition, the resource definition, the variable management and the activity definition in the process design, so that the description during the design is realized; and similarly, flow operation and flow operation, wherein the flow operation comprises flow starting, task pending and BPM flow list to realize the management of the working state of the flow in operation.
5. An event-driven electronic batch recording system as claimed in claim 1, wherein: in step S8, the variable key, the variable name, the value object, the description, and the variable type are included; and displaying the variable list after saving.
6. An event-driven electronic batch recording system as claimed in claim 1, wherein: in step S8, process information is set, and the process editing page includes a process key, a name, a description, whether to use, an application name (approval), a process type (approval process), a form address, and an automatically generated activity dispatcher (True/False).
7. An event-driven electronic batch recording system as claimed in claim 1, wherein: in step S9, the user logs in to the workflow design tool, enters a process editing page, and the user clicks a certain activity in the process editing area, and the system displays the V attribute of the current connection line in the attribute editing area; editing the attribute of the connecting line by a user, and finishing the unified saving of the process through the saving function of the process editing; setting conditions: the system is used for clicking a certain connecting line in the process editing area and popping up an active condition setting page by a floating menu clicking system; the page elements include: and storing the key, the name, the value, the condition description and the numerical value type into a database after the key, the name, the value, the condition description and the numerical value type are stored.
8. An event-driven electronic batch recording system as claimed in claim 1, wherein: in step S10, the specific list information includes: flow key, sub-flow name, blocking type: waiting for all branch flows to complete 2: any branching flow does not wait for 3: wait for any branch flow to complete 4: wait for certain branch flows to complete), serial/parallel; and clicking to save the database.
9. An event-driven electronic batch recording system as claimed in claim 1, wherein: in step S11, the developer only needs to find the corresponding command according to the scene GUID selected and set by the user to execute the command.
10. An event-driven electronic batch recording system as claimed in claim 1, wherein: in step S11, if the event is an event, when the user is in a custom design, the platform already selects the event according to the user behavior, and issues the event, the event in the message queue is issued, and the user waits for a subscription, and the developer only needs to subscribe to the corresponding event according to the event ID set by the user.
CN202110151416.3A 2021-02-03 2021-02-03 Event-driven electronic batch recording system Active CN112799651B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110151416.3A CN112799651B (en) 2021-02-03 2021-02-03 Event-driven electronic batch recording system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110151416.3A CN112799651B (en) 2021-02-03 2021-02-03 Event-driven electronic batch recording system

Publications (2)

Publication Number Publication Date
CN112799651A true CN112799651A (en) 2021-05-14
CN112799651B CN112799651B (en) 2023-08-04

Family

ID=75814095

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110151416.3A Active CN112799651B (en) 2021-02-03 2021-02-03 Event-driven electronic batch recording system

Country Status (1)

Country Link
CN (1) CN112799651B (en)

Citations (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1994018620A1 (en) * 1993-02-08 1994-08-18 Action Technologies, Inc. Method and apparatus for managing business processes
CN101794226A (en) * 2010-03-08 2010-08-04 山东大学 Service software construction method and system adapting to multiple business abstraction levels
CN103679329A (en) * 2012-09-06 2014-03-26 西门子公司 Method and system for handling batch production within ANSI/ISA/95 production scheduling extended with batch production parameter historian
CN103761082A (en) * 2013-12-31 2014-04-30 湖南大唐先一科技有限公司 Componential research and development mode and domain driving model combined application development system and platform
WO2014135095A1 (en) * 2013-03-06 2014-09-12 Syngenta Participations Ag Dihydrobenzofuran derivatives as insecticidal compounds
CN105630472A (en) * 2014-11-03 2016-06-01 中国科学院沈阳自动化研究所 Quick client development frame for manufacturing execution system and software development method for frame
US20170108852A1 (en) * 2015-10-16 2017-04-20 Juan Tirado Middleware architecture for validating and controlling manufacturing processes
CN109726900A (en) * 2018-12-14 2019-05-07 广东工业大学 A kind of the manufacture execution Workflow system and implementation method of message-driven
RU2704873C1 (en) * 2018-12-27 2019-10-31 Общество с ограниченной ответственностью "ПЛЮСКОМ" System and method of managing databases (dbms)
CN110428112A (en) * 2019-08-09 2019-11-08 烟台东方纵横科技股份有限公司 A kind of dual prevention mechanism management system of enterprise based under internet+mode
CN110597950A (en) * 2019-08-08 2019-12-20 浙江中控技术股份有限公司 Batch record auditing process control method and device based on deviation management
CN111461517A (en) * 2020-03-27 2020-07-28 机械工业仪器仪表综合技术经济研究所 Intelligent information system for planning laboratory workflow
CN112101701A (en) * 2020-07-28 2020-12-18 重庆华森制药股份有限公司 Intelligent manufacturing system and manufacturing method for producing polyethylene glycol electrolyte powder
CN112101771A (en) * 2020-09-10 2020-12-18 重庆华森制药股份有限公司 Automatic production control system and production method for Danshu soft capsules
CN112199515A (en) * 2020-11-17 2021-01-08 西安交通大学 Polymorphic knowledge map driven knowledge service innovation method

Patent Citations (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1994018620A1 (en) * 1993-02-08 1994-08-18 Action Technologies, Inc. Method and apparatus for managing business processes
CN101794226A (en) * 2010-03-08 2010-08-04 山东大学 Service software construction method and system adapting to multiple business abstraction levels
CN103679329A (en) * 2012-09-06 2014-03-26 西门子公司 Method and system for handling batch production within ANSI/ISA/95 production scheduling extended with batch production parameter historian
WO2014135095A1 (en) * 2013-03-06 2014-09-12 Syngenta Participations Ag Dihydrobenzofuran derivatives as insecticidal compounds
CN103761082A (en) * 2013-12-31 2014-04-30 湖南大唐先一科技有限公司 Componential research and development mode and domain driving model combined application development system and platform
CN105630472A (en) * 2014-11-03 2016-06-01 中国科学院沈阳自动化研究所 Quick client development frame for manufacturing execution system and software development method for frame
US20170108852A1 (en) * 2015-10-16 2017-04-20 Juan Tirado Middleware architecture for validating and controlling manufacturing processes
CN109726900A (en) * 2018-12-14 2019-05-07 广东工业大学 A kind of the manufacture execution Workflow system and implementation method of message-driven
RU2704873C1 (en) * 2018-12-27 2019-10-31 Общество с ограниченной ответственностью "ПЛЮСКОМ" System and method of managing databases (dbms)
CN110597950A (en) * 2019-08-08 2019-12-20 浙江中控技术股份有限公司 Batch record auditing process control method and device based on deviation management
CN110428112A (en) * 2019-08-09 2019-11-08 烟台东方纵横科技股份有限公司 A kind of dual prevention mechanism management system of enterprise based under internet+mode
CN111461517A (en) * 2020-03-27 2020-07-28 机械工业仪器仪表综合技术经济研究所 Intelligent information system for planning laboratory workflow
CN112101701A (en) * 2020-07-28 2020-12-18 重庆华森制药股份有限公司 Intelligent manufacturing system and manufacturing method for producing polyethylene glycol electrolyte powder
CN112101771A (en) * 2020-09-10 2020-12-18 重庆华森制药股份有限公司 Automatic production control system and production method for Danshu soft capsules
CN112199515A (en) * 2020-11-17 2021-01-08 西安交通大学 Polymorphic knowledge map driven knowledge service innovation method

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
陈从旺等: "制造执行系统在制药行业的应用", vol. 28, no. 9, pages 180 - 183 *

Also Published As

Publication number Publication date
CN112799651B (en) 2023-08-04

Similar Documents

Publication Publication Date Title
US8195436B2 (en) Multi-infrastructure modeling system
Martínez et al. A big data-centric architecture metamodel for Industry 4.0
US8473263B2 (en) Multi-infrastructure modeling and simulation system
US20040039468A1 (en) Method, system and apparatus for an industrial framework based on integrated applications via adapters
US8478850B2 (en) Platform component architecture (PCA)-based system, method and application designer
CN111913734A (en) On-line development platform based on micro-service technology system
CN101201599A (en) Hmi views of modules for industrial control systems
CN109684057A (en) Task processing method, device and storage medium
JP2005521111A (en) Business process policy object
CN109032590B (en) Configuration method, device, terminal and storage medium of visual development environment
CN110825457A (en) Method and device for processing business in business engine, storage medium and electronic equipment
CN116382643A (en) Running system based on low-code platform
Yuan et al. Collaborative construction industry integrated management service system framework based on big data
CN112799651A (en) Event-driven electronic batch recording system
Li et al. The design and research of front-end framework for microservice environment
Lin et al. A flexible graphical user interface for performance modeling
CN114610309A (en) Object configuration method, device, equipment and storage medium
Xie et al. Lightweight business process modelling
CN113919796A (en) Smart community heterogeneous system integration method
CN111145004B (en) Intelligent financial auditing platform based on editable workflow
Demchak et al. The treasure map for Rich Services
CN113886061A (en) Industry thing networking operation and maintenance platform
US11972257B2 (en) Industrial automation system topology with point to point business rule integration
US20240020117A1 (en) Industrial automation system topology with point to point business rule integration
EP4307104A1 (en) Extensible profiles for industrial controller devices

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant