Software framework method for realizing industrial manufacturing execution complex system partition

Abstract

The invention discloses a software framework method for realizing industrial manufacturing execution complex system partitions. The method relates to electric digital processing, and comprises the following steps: inserting an event notification carrying parameters in a universal area of a business layer, creating an extension code warehouse capable of being packaged into a maven project, defining an extension class and method with a specific annotation in the extension project, and then packaging the extension project and uploading the extension project to the maven warehouse; the extension package is introduced into a general area project, permission mapping of a user and the extension package is configured, a control layer can load related configuration during system operation, and when the user triggers an event, the system can call extension codes and general codes to cooperatively execute services, so that the expandability of a software framework is improved, and the system performance is improved. The problem that in the prior art, a software framework achieved through industrial manufacturing execution complex system partition is low in expandability is solved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of digital processing, and in particular to a software framework method for implementing partition of an industrial manufacturing execution complex system. BACKGROUND

[0002] In the field of industrial manufacturing, the execution system usually needs to cope with the challenges brought by different sub-industry or enterprise individualized needs, such as differences in the same production process, different internal logic of the same function, and different structures of the same business object. However, neither the traditional monolithic software architecture nor the modern micro-service architecture can effectively solve the problem of the mutual independence of standard content and industry characteristic content or enterprise individualized content in the design state and the mutual isolation of the two in the running state in the industrial manufacturing system. The existing system often meets different needs through hard-coded logic or customized development, resulting in high system maintenance cost, poor scalability, complex version management, and difficulty in flexible adaptation to diversified business scenarios while ensuring universality. Therefore, a new software framework architecture is urgently needed, which can realize independent development and management of general logic and extension logic in the design state, and seamless integration and on-demand loading of the two through a dynamic configuration and scheduling mechanism in the running state, so as to balance the standardization and individualization needs of the system and improve the maintainability, scalability and adaptability of the system.

[0003] For example, the Chinese invention patent with the publication number CN102945179B discloses a software upgrade method and device based on MTD partition, which includes: adding pre-upgrade MTD partition description information and upgrade data to a software upgrade file; reading the software upgrade file during the upgrade process to parse out the pre-upgrade MTD partition description information and upgrade data; writing the pre-upgrade MTD partition description information and upgrade data to the corresponding storage location according to the MTD partition correspondence relationship in the original MTD partition description information and the pre-upgrade MTD partition description information; starting the system uboot, reading the pre-upgrade MTD partition description information stored in the storage, assembling the MTD partition description information write-in parameters, and writing them into the system kernel.

[0004] For example, the Chinese invention patent with the publication number CN109840136B discloses an electromechanical system software architecture based on a partition operating system, which includes: a comprehensive task management partition and a ground maintenance and IBIT partition, and the application layer software configures the time scheduling table of the core operating system to determine the execution order and execution time of each partition; when the comprehensive task management partition judges that the aircraft state is in the air, the core operating system is configured to prohibit the ground maintenance and IBIT partition from being scheduled by configuring the core operating system time scheduling table; when the comprehensive task management partition judges that the aircraft state is on the ground, the core operating system is configured to start the ground maintenance and IBIT partition scheduling by configuring the core operating system time scheduling table.

[0005] But in the process of implementing the technical scheme of the embodiments of the present application, the applicant finds that the above-mentioned technology at least has the following technical problems:

[0006] Due to the individualized needs of different sub-industries or enterprises, the same production process, function logic and business object structure have significant differences, and both the traditional software architecture and the micro-service architecture are difficult to effectively support the flexible expansion and customization of industry or enterprise characteristic content while ensuring the generality of the system. In the design state, the general logic and the expansion logic are often mixed in the same code library, resulting in high code coupling degree, difficult maintenance, complex version management, and inability to support independent evolution of multiple expansion logics. In the running state, the system lacks flexible scheduling mechanism and dynamic configuration capability, and is difficult to dynamically load different expansion logics according to user identity or business scenario, and cannot realize the isolated execution and on-demand fusion of general logic and expansion logic.

[0007] In addition, the existing system often uses hard-coded calls or tight coupling methods for communication mechanisms between general logic and expansion logic, lacks decoupled event-driven mechanisms, resulting in complex access and high maintenance cost of expansion logic, and difficulty in ensuring the integrity and consistency of transactions. Therefore, there is an urgent need for a new software framework architecture that can realize the complete isolation and independent management of general logic and expansion logic in the design state, and realize the flexible scheduling and seamless fusion of the two through dynamic configuration and event-driven mechanisms in the running state. The software framework for partition implementation of industrial manufacturing execution complex system has low expandability. SUMMARY

[0008] The embodiments of the present application provide a software framework method for partition implementation of an industrial manufacturing execution complex system, which solves the problem of low expandability of the software framework for partition implementation of an industrial manufacturing execution complex system in the prior art, and improves the expandability of the software framework.

[0009] The embodiment of the application provides a software framework for implementing a partition of an industrial manufacturing execution complex system, comprising a business layer, a control layer and a configuration layer; the business layer comprises a general area and an extension area; wherein the general area is used for implementing standard logic of industrial manufacturing, and only one set of unified standard logic exists to cover basic processes and functions commonly used in the industry, and the standard logic covers basic processes and functions commonly used in the industry; the extension area is used for executing industry or enterprise characteristic logic, each characteristic logic exists in the form of an independent module, comprises exclusive data processing rules, business trigger conditions and output format definitions, and modules are interconnected through standardized adaptive interfaces and the general area and other extension modules to realize data intercommunication, when new characteristic demands are added, the extension can be completed by adding an independent module, and existing logic does not need to be modified; the control layer is below the business layer, and is used for scheduling standard contents of the general area and characteristic contents of the extension area, and is internally provided with a scheduling engine and a priority determination module; the scheduling engine identifies the standard contents and the characteristic contents to be executed by analyzing a business trigger signal; the priority determination module determines the execution order of the standard contents and the characteristic contents according to preset rules, and when there are multiple extension area characteristic contents, the extension area characteristic contents are called in turn according to a module registration order; the configuration layer is at the bottom, and is used for realizing mapping of users and extension contents, and can complete associated configuration of users and different business extension areas; the configuration layer comprises a user identity recognition interface, an extension content index library and a mapping relationship storage unit; when the extension content is not mapped with the user, the mapping relationship storage unit feeds back a null value, and the control layer receives the null value signal and only calls a standard content execution link of the general area.

[0010] The embodiment of the application provides a software framework method for implementing a partition of an industrial manufacturing execution complex system, comprising the following steps: first, inserting an event notification at a target business node of a general area of a business layer, and realizing the insertion by calling a preset notification sending interface, and carrying context parameters of the business node at the same time; second, creating an industry or enterprise extension code warehouse, generating a packable maven project based on the warehouse, and generating a jar package after compiling the project, and introducing the general area project in a package dependent manner; third, defining an extension class and an extension method in the extension project, and adding a specific annotation in front of the extension method to specify an event subscribed by the method; fourth, executing an mvn clean deploy command to pack and upload the extension project to a public maven warehouse for reference of the general area project.

[0011] The embodiment of the application provides a software framework method for realizing partition of an industrial manufacturing execution complex system, and further comprises the following steps: fifthly, defining coordinate information of the extension package in a pom file of the general area project, and introducing the extension package into the general area project; sixthly, configuring permission mapping of the user and the extension package through a system management background, and specifying the user who can use the extension package; seventhly, after the system is run, the control layer loads the extension package configuration of all users to the cache, and when the user triggers an event in the general area, the control layer calls corresponding extension code according to the cached configuration information, and cooperates with the general code to complete business execution.

[0012] The one or more technical solutions provided in the embodiment of the application have at least the following technical effects or advantages:

[0013] 1. The business layer is divided into a general area and an extension area, and a code complete isolation design is adopted, so that the general logic and the industry and enterprise characteristic logic evolve in independent code repositories, and code pollution is avoided. The extension area supports linear extension of multiple characteristic logics, and can be connected to the general area through simple annotations, greatly reducing the extension development threshold. At the same time, the publish-subscribe mode realizes decoupling of the general area and the extension area, and the two do not affect each other when upgrading or modifying, so that the system can quickly respond to the individual needs of different subdivided industries and enterprises, and the extension capability and long-term maintenance efficiency in the complex industrial scene are significantly improved.

[0014] 2. The control layer coordinates the initiation, transmission and processing of event notification, ensures that the general code and the extension code are executed in the same transaction, effectively avoids data inconsistency, and guarantees the accuracy of industrial manufacturing business data. The configuration layer dynamically calls corresponding logic according to the user identity through the mapping relationship between the user and the extension area, without the need to develop the system separately for different users, reducing redundant development and resource consumption. In addition, the general area can send event notifications carrying rich information at any position, and the extension area can realize accurate processing based on this, improving the business collaboration efficiency.

[0015] 3. The framework supports three kinds of extension logics, namely enhancement, replacement and deletion, which can flexibly cope with various non-standard scenes in industrial manufacturing. For example, industry-specific rules are added in the standard process through enhancement logic, enterprise self-defined processes are used to replace the general logic through replacement logic, and unnecessary standard steps are removed through deletion logic. Combined with the user mapping mechanism of the configuration layer, customized logic can be accurately executed for different users, and standard logic is automatically executed when there is no extension mapping, which guarantees the universality of industry standards and meets the individual needs of enterprises, and improves the adaptation capability to complex and variable industrial manufacturing environments. BRIEF DESCRIPTION OF DRAWINGS

[0016] Figure 1 A software framework method for realizing partition of an industrial manufacturing execution complex system is provided in the embodiment of the application.

[0017] Figure 2 A development flowchart of a software framework method for partition implementation of an industrial manufacturing execution complex system is provided for the embodiments of the present application.

[0018] Figure 3 A runtime scheduling flowchart of the software framework method for partition implementation of the industrial manufacturing execution complex system is provided for the embodiments of the present application. DETAILED DESCRIPTION

[0019] The embodiments of the present application provide a software framework method for partition implementation of an industrial manufacturing execution complex system, and solve the problem of low software framework extensibility for partition implementation of the industrial manufacturing execution complex system in the prior art. The embodiments of the present application insert event notifications carrying parameters into a business layer general area, create an extension code repository that can be packaged as a maven project, define extension classes and methods with specific annotations in the extension project, then package and upload the extension project to the maven repository, introduce the extension package in the general area project, configure the permission mapping of users and the extension package, and the control layer loads the related configuration when the system runs. When the user triggers an event, the system calls the extension code to cooperatively execute the business with the general code, and the software framework extensibility is improved.

[0020] The technical solutions in the embodiments of the present application are used to solve the problem of low software framework extensibility for partition implementation of an industrial manufacturing execution complex system, and the general idea is as follows:

[0021] The embodiments of the present application insert event notifications carrying parameters into a business layer general area, create an extension code repository that can be packaged as a maven project, define extension classes and methods with specific annotations in the extension project, then package and upload the extension project to the maven repository, introduce the extension package in the general area project, configure the permission mapping of users and the extension package, and the control layer loads the related configuration when the system runs. When the user triggers an event, the system calls the extension code to cooperatively execute the business with the general code, and the software framework extensibility is improved.

[0022] In order to better understand the above technical solutions, the above technical solutions will be described in detail in combination with the description of the drawings and the specific embodiments.

[0023] As Figure 1As shown, a software framework method overall architecture diagram of an industrial manufacturing execution complex system partition implementation provided by an embodiment of the present application is provided, the method comprising: a business layer, a control layer and a configuration layer; the business layer comprising a general area and an extension area; wherein the general area is used to implement standard logic of industrial manufacturing, and only one set of unified standard logic exists to cover the basic processes and functions commonly applicable in the industry, the standard logic covering the basic processes and functions commonly applicable in the industry; the extension area is used to execute industry or enterprise characteristic logic, each characteristic logic existing in the form of an independent module, comprising exclusive data processing rules, business trigger conditions and output format definitions, the modules realizing data intercommunication through standardized adaptive interfaces with the general area and other extension modules, when a characteristic demand is newly added, the extension can be completed by newly adding an independent module without modifying the existing logic; the control layer is below the business layer, and is used to schedule the standard content of the general area and the characteristic content of the extension area, and is internally provided with a scheduling engine and a priority determination module, the scheduling engine identifying the standard content and the characteristic content to be executed by analyzing a business trigger signal, the priority determination module determining the execution order of the two according to a preset rule, when there are multiple extension area characteristic contents, the modules are called in turn according to the module registration order; the configuration layer is at the bottom, and is used to realize the mapping of users and extension contents, and can complete the associated configuration of users and different business extension areas, the configuration layer comprising a user identity recognition interface, an extension content index library and a mapping relationship storage unit; when the extension content is not mapped with the user, the mapping relationship storage unit feeds back a null value, and the control layer receives the null value signal and only calls the standard content execution link of the general area.

[0024] In the embodiment, the software framework includes a business layer, a control layer, and a configuration layer, which work together to achieve high efficiency and flexibility of the industrial manufacturing execution system. The business layer is composed of a general area and an extension area. The general area focuses on implementing standard logic of industrial manufacturing, and only one set of unified standard exists, covering the basic processes and functions commonly applicable in the industry. This design fundamentally solves the problems of production process differences, functional logic differences, and business object structure differences caused by different industry segments and enterprise characteristics, providing a stable foundation core for the system. The extension area is responsible for executing industry or enterprise characteristic logic, supports multiple characteristic logics coexisting and linear expansion, meets customized needs in different scenarios, and cooperates with the completely isolated code design (the general area and the extension area and each extension have independent code repositories) to ensure the independent evolution of the logic of each area and reduce the risk of code pollution, significantly improving the scalability and maintainability of the system. The control layer is below the business layer, and its core function is to accurately schedule the standard content of the general area and the characteristic content of the extension area to ensure their orderly cooperation during runtime. The initiation, transmission, and processing of its unified event notification can ensure that the general code and the extension code are executed in the same transaction, effectively avoiding data inconsistency and ensuring the consistency and efficiency of business processing. The configuration layer is at the bottom and is responsible for mapping user and extension content. By establishing the association configuration of user identity and extension area, the system can dynamically call the corresponding logic according to the user identity, and only execute the general logic when the mapping is not established. This mechanism ensures the stability of the standard logic and provides flexible expansion space for personalized needs. Combined with the supported extension logic such as enhancement, replacement, and deletion, the system's ability to adapt to non-standard needs is greatly enhanced, allowing the system to accurately meet the diverse needs of the industrial manufacturing industry.

[0025] Further, the general area and the extension area of the business layer adopt a completely isolated code design pattern. The general area and the extension area are managed and maintained by independent code repositories. For the extension area, if there are multiple different extension contents, including characteristic logic of different industries or individualized logic of different enterprises in the same industry, each extension content is configured with an independent code repository, and the extension contents are code-isolated. The general area, the extension area, and each extension content achieve code isolation through their independent code repositories to support the independent evolution of the business logic of the general area and the extension area. The general area iterates the industry standard, and the extension area updates according to specific needs.

[0026] In the embodiment, the general area and the extension area of the business layer adopt a code completely isolated design mode, and the two are managed and maintained by independent code repositories, and the physical isolation cuts off the code interference between the general logic and the characteristic logic from the root. For the extension area, as long as there are multiple different extension contents, each extension content is equipped with an independent code repository, and the extensions are also strictly code isolated. This design brings significant technical effects: on the one hand, it ensures that the business logic of the general area and the extension area can evolve independently, the general area can focus on the iterative optimization of industry standards, and constantly improve the basic processes and functions to adapt to the development of the industry, while the extension area can quickly update the characteristic logic according to the needs of specific industries or enterprises, and the two do not interfere with each other in the iteration process; on the other hand, it effectively controls the code complexity of each area, avoids the mutual penetration and pollution between the general code and the extension code and different extension codes, reduces the difficulty of code maintenance, improves the stability and scalability of the system, and provides a solid code management foundation for the long-term application of the framework in complex industrial scenarios.

[0027] Further, the association configuration of the user and the different business extension area is specifically that: a mapping relationship between the user identity and the corresponding extension area is established in the system; the control layer identifies the identity information of the current user in real time, and automatically calls the characteristic logic of the extension area associated with the user according to the mapping relationship between the user identity and the extension area in the configuration layer, and simultaneously calls the standard logic of the general area to jointly complete the business processing; for the user not associated with any extension area, the control layer only calls and executes the standard logic of the general area.

[0028] In the embodiment, by establishing the mapping relationship between the user identity and the corresponding extension area, the precise association configuration of the user and the different business extension areas is realized. During the system operation, the control layer captures the identity information of the current user in real time, and then automatically calls the characteristic logic of the extension area associated with the user according to the mapping relationship stored in the configuration layer, while seamlessly integrating the standard logic of the general area to complete the business processing loop together. For the user not associated with any extension area, the system only executes the standard logic of the general area. This mechanism brings significant technical effects: on the one hand, it can accurately meet the large number of non-standard system needs in the industrial manufacturing industry. Since there are differences in business rules of different sub-industries and different enterprises, through the dynamic binding of the user and the extension area, the same system can present personalized functions meeting different user needs, without the need to develop a system for each user, greatly reducing the development and maintenance cost; on the other hand, this dynamic calling mode based on identity not only guarantees the universality and stability of the general standard logic, but also meets the personalized needs through the flexible adaptation of the extension area, so that the system has high flexibility while maintaining uniformity, improving the adaptability of the system to complex industrial scenes. In addition, the real-time identification of the user identity by the control layer and the logic calling ensure the efficiency and accuracy of the business processing, avoid errors caused by manual intervention, and further enhance the reliability of the system.

[0029] Further, the information interaction between the general area and the extension area is realized by using a publish / subscribe mode; during the execution of the general area, when a specific business node is reached, the corresponding event notification is actively sent out, and the event notification contains the related information of the specific business node; the extension area pre-subscribes the required event notification, and when the corresponding event notification sent out by the general area is received, the extension logic is executed according to the notification content; the general area sends out the event notification according to the standard process, and the extension area only processes according to the subscribed event notification content.

[0030] In the embodiment, the information interaction between the general area and the extended area is implemented in a publish-subscribe mode, and the specific process is as follows: during the execution of the general area, when a specific business node is reached (such as completing a certain standard operation, triggering a key event, etc.), an event notification containing the relevant information of the business node is actively sent out; the extended area pre-subscribes the event notification required by itself, and after receiving the corresponding notification sent out by the general area, the extended area executes the corresponding extended logic according to the notification content. This mode realizes the complete decoupling of the general area and the extended area: the general area does not need to know the existence of the extended area and its internal logic, and only needs to send out event notifications according to the standard process; the extended area also does not need to understand the specific implementation details of the general area, and only needs to process according to the subscribed notification content. As a result, the following significant technical effects are brought about: when the general area is upgraded or the extended area is added or modified, the adjustment of one side will not affect the other side, effectively avoiding the chain reaction that one side changes and the other side needs to be modified synchronously, greatly reducing the complexity of system iteration. At the same time, this decoupling design enables the general area to focus on the optimization of industry standard logic, and the extended area can flexibly respond to changes in individualized demand, significantly improving the flexibility and adaptability of the system to different industrial scenarios, and providing strong support for the long-term stable evolution of the system.

[0031] Further, the initiation, transmission and processing of the event notification are all implemented by the control layer; the general area of the business layer triggers the event notification according to the preset interface specification, and the extended area receives the notification and executes the extended logic; the routing, distribution and execution timing control of the notification are all completed by the control layer; the standard code of the general area and the characteristic code of the extended area are executed in the same transaction, and when the general logic and the extended logic involve data operations, both of them are successfully executed and then submitted, or all of them are rolled back in case of an exception.

[0032] In the embodiment, the control layer is responsible for the whole process of the initiation, delivery and processing of the event notification, which makes the general area and the extended area of the business layer not need to pay attention to the complex control logic and can focus on the implementation of the core business logic. Specifically, the general area only needs to trigger the event notification according to the preset interface specification and does not need to consider how the notification is delivered and where it is delivered. The extended area only needs to focus on receiving the notification and executing the corresponding extended logic and does not need to care about the source and scheduling details of the notification. The remaining tedious control work such as the routing selection, accurate distribution and execution timing control of the notification is completed by the control layer. More importantly, the control layer can ensure that the standard code of the general area and the characteristic code of the extended area are executed in the same transaction: when the general logic and the extended logic involve data operations, both of them are executed successfully and submitted, or they are all rolled back in the presence of any exception. This mechanism fundamentally ensures the transaction integrity of the business processing, effectively avoids the data inconsistency problem caused by the asynchronous execution of the general logic and the extended logic, greatly guarantees the accuracy and reliability of the business data, and enables the system to maintain the consistency and stability of the data when processing complex industrial manufacturing business, even if it involves multi-area logic coordination, which provides a solid data foundation for subsequent data analysis and decision support.

[0033] Further, any business location of the general area of the business layer can insert and send the event notification, which is not limited by the specific function module or code structure. The event notification point can be set at the starting stage, the intermediate link and the end node of the standard flow according to the business demand. The event notification can carry any number and type of objects or variables, which include business data, context information and other contents related to the business node.

[0034] In the embodiment, the framework supports inserting and sending event notifications at any business location in the general area of the business layer, without being restricted by specific functional modules or code structures. Whether it is the starting stage, intermediate key link or end node of the standard process, the event notification point can be flexibly set according to actual business needs. This high degree of flexibility enables the general area to trigger interaction at the most critical and most needed expansion intervention node, breaking the restrictions of fixed notification positions on business collaboration. At the same time, the event notification can carry any number and type of objects or variables. These information can be core business data such as production parameters and order data, context information such as user identity and operation time, and other types of content related to the business node. With this feature, the general area can pass rich and accurate information to the expansion area according to the actual business scenario, and the expansion area can design and execute characteristic logic based on these information, greatly enhancing the depth and breadth of their collaborative work. The technical effect of this mechanism is very significant: it makes the function of the expansion area more targeted and practical, avoids the generalization or deviation of the expansion logic due to insufficient information, and enables the expansion area to accurately adapt to the individual needs of different business scenarios, further improving the system's ability to adapt to complex industrial manufacturing businesses and processing accuracy.

[0035] Further, the framework supports three types of expansion logic: enhancement, replacement and deletion. The enhancement logic is to add additional characteristic processing steps based on the execution of the general area standard logic, including adding industry-specific optimization rules after the standard production plan is generated. The replacement logic is to completely replace part of the standard logic of the general area with the characteristic logic of the expansion area, which is used for business links with unique processing methods, including replacing the general quality inspection logic with the enterprise's self-defined quality inspection process. The deletion logic is to cancel part of the standard logic in the general area that is not applicable to specific users, including removing some unnecessary report generation steps for the user.

[0036] In this embodiment, the framework supports three types of extended logic: enhancement, replacement, and deletion, which can comprehensively cover the individual needs of different industrial scenarios and provide flexible operation means for system adaptation to diversified businesses. Among them, the enhanced logic is to add additional special processing steps based on the execution of the standard logic in the general area, for example, after the standard production plan is generated, specific optimization rules are added according to the industry characteristics to make the plan more in line with the actual production rules of the industry. The replacement logic is to completely replace some standard logic in the general area with the special logic in the extended area, which is suitable for business links with unique processing methods, such as replacing the general quality inspection logic with the enterprise's self-defined quality inspection process to ensure that the processing method of the key link is highly matched with the actual operation of the enterprise. The deletion logic refers to canceling some standard logic in the general area that is not suitable for specific users, such as removing some unnecessary report generation steps for the user to simplify the operation process. The technical effects of these three types of extended logic are significant: they collectively build a multi-level customization system, which not only retains the basic support of the general standard, but also meets the differentiated needs through targeted adjustments, avoiding the problems of functional redundancy or insufficient adaptation caused by the "one-size-fits-all" of the general logic. This makes the system accurately respond to the business characteristics of different industries and different enterprises, greatly improving the practicality and adaptation accuracy of the system in complex industrial environments, while reducing the cost of secondary development by enterprises due to the inadaptability of the system.

[0037] Further, when the extension area accesses the general area, the developer adds a specific format of annotation in front of the self-defined extension code, which includes an extension class or an extension method, to complete the association docking of the extension content and the general area. The annotation contains key information for identifying the associated event notification, enabling the control layer to identify the correspondence between the extension code and the general area event.

[0038] In this embodiment, the implementation of the extension area accessing the general area is extremely simple. The developer only needs to add a specific format of annotation in front of the self-defined extension code, which includes an extension class or an extension method, to complete the association docking of the extension content and the general area. The annotation contains key information for identifying the associated event notification, which enables the control layer to accurately identify the correspondence between the extension code and the general area event, ensuring that the extended logic can be triggered at the correct business node. This access method has significant technical effects: without the need for developers to write complex interface adaptation code or perform tedious configuration operations, it greatly reduces the technical threshold and workload of extension development. Even developers who are not familiar with the internal mechanisms of the framework can quickly complete the development and access of the extended logic. At the same time, this simple association method reduces the errors that may occur during the extension access process, improves development efficiency, and enables the system to respond more quickly to the individual needs of industries or enterprises, further enhancing the flexibility and practicality of the framework.

[0039] AsFigure 2 As shown in the figure, a development flowchart of a software framework method for partition implementation of an industrial manufacturing execution complex system is provided in the embodiment, the software framework method for partition implementation of an industrial manufacturing execution complex system comprises: first, inserting an event notification at a target business node in a general area of a business layer, and achieving by calling a preset notification sending interface, while carrying context parameters of the business node; second, creating an industry or enterprise extension code repository, and generating a packable maven project based on the repository, and generating a jar package after compiling the project, and introducing the general area project in a package dependent manner; third, defining an extension class and an extension method in the extension project, and adding a specific annotation before the extension method to specify an event subscribed by the method; fourth, executing an mvn clean deploy command to pack and upload the extension project to a public maven repository for reference by the general area project.

[0040] As shown in the figure, a development flowchart of a software framework method for partition implementation of an industrial manufacturing execution complex system is provided in the embodiment, the software framework method for partition implementation of an industrial manufacturing execution complex system comprises: first, inserting an event notification at a target business node in a general area of a business layer, and achieving by calling a preset notification sending interface, while carrying context parameters of the business node; second, creating an industry or enterprise extension code repository, and generating a packable maven project based on the repository, and generating a jar package after compiling the project, and introducing the general area project in a package dependent manner; third, defining an extension class and an extension method in the extension project, and adding a specific annotation before the extension method to specify an event subscribed by the method; fourth, executing an mvn clean deploy command to pack and upload the extension project to a public maven repository for reference by the general area project. Figure 3 As shown in the figure, a development flowchart of a software framework method for partition implementation of an industrial manufacturing execution complex system is provided in the embodiment, the software framework method for partition implementation of an industrial manufacturing execution complex system comprises: first, inserting an event notification at a target business node in a general area of a business layer, and achieving by calling a preset notification sending interface, while carrying context parameters of the business node; second, creating an industry or enterprise extension code repository, and generating a packable maven project based on the repository, and generating a jar package after compiling the project, and introducing the general area project in a package dependent manner; third, defining an extension class and an extension method in the extension project, and adding a specific annotation before the extension method to specify an event subscribed by the method; fourth, executing an mvn clean deploy command to pack and upload the extension project to a public maven repository for reference by the general area project.

[0041] In the embodiment, there are seven consecutive steps, and the cooperation of each step ensures efficient access and running of the extension logic. First, an event notification is inserted at a target business node in a general area of a business layer, which can be achieved by calling a preset notification sending interface, while carrying context parameters of the business node, which provides a precise trigger point and information basis for the interaction between the general area and the extension area; second, an industry or enterprise extension code repository is created, and a packable maven project is generated to ensure that a jar package is generated after compiling so as to be introduced into the general area in a package dependent manner at runtime, and this standardized project management manner facilitates the maintenance and reuse of extension content; third, an extension class and an extension method are defined in the extension project, and a specific annotation must be added before the extension method to specify the subscribed event, which, in combination with the simple annotation access design, greatly reduces the technical threshold of extension development, enabling developers to quickly complete the associated configuration; fourth, the extension project is packed and uploaded to a public maven repository by an mvn clean deploy command, providing a convenient channel for reference by the general area project, and ensuring the standardized distribution of the extension content.

[0042] In the subsequent steps, the fifth step defines the extension package coordinates in the general area project pom file to introduce the extension package, realizing the seamless integration of the extension content and the general area; the sixth step configures the permission mapping of the user and the extension package through the system management background, so that the system can accurately control the use permission of the extension function of different users and adapt to the personalized needs; after the seventh step of running the system, the control layer loads the user extension package configuration to the cache, and when the user triggers the event, the corresponding extension code is called to cooperate with the general code to complete the business closed loop, ensuring the efficiency and continuity of business processing. The technical effects of these steps are remarkable: the whole process adopts a standardized and lightweight operation mode, reducing complex configuration and adaptation work, improving the efficiency of extension development and integration, and at the same time, through the permission mapping and cooperative execution mechanism, the system can not only uniformly support general needs, but also flexibly respond to personalized needs, enhancing the practicality and adaptability of the framework in the industrial manufacturing scene.

[0043] It should be noted that the structure of the software framework is divided into a business layer, a control layer and a configuration layer from top to bottom: the business layer contains a general area and an extension area; the control layer schedules the general and extension content below the business layer; the configuration layer at the bottom completes the mapping of users and extension content, and only executes the general logic when there is no mapping. The integration of the general and extension models is completed by the extension area as needed, realizing the independent development of the design state general and extension content in separate warehouses, and the same code supporting general and personalized needs in the running state. First, the business content is divided into a general area and an extension area, the code is completely isolated and managed in separate warehouses, and multiple extensions are also isolated, ensuring that the logic of each area evolves independently, controls complexity, and avoids code pollution; second, the user is associated with the business extension area through configuration, and different code logic is executed according to the user identity at runtime to meet a large number of non-standard needs; third, the general area and the extension area use a publish / subscribe mode of communication, the general area sends event notifications, and the extension area subscribes to implement extension logic, both sides are decoupled, and maintenance of the extension is facilitated; fourth, the control layer ensures that the general and extension codes are in the same transaction, ensuring transaction integrity; fifth, the framework supports sending event notifications carrying any number and type of objects or variables at any position in the general area; sixth, the framework supports enhancing, replacing and deleting extension logic; seventh, the extension implementation is simple, and a custom code can be connected to the general area by adding an annotation in front of it. The implementation steps are clear: first, insert event notifications into the general area of the business layer and carry context parameters; second, create an industry extension code warehouse and a packageable maven project, define extension classes and methods with specific annotations; third, package the extension project and upload it to the public maven warehouse, and import the extension package in the pom file of the general area project; fourth, configure the user and the extension package permission mapping through the management background; and fifth, run the system, the control layer loads the user extension package configuration into the cache, and the extension code is called to complete the business closed loop when the user triggers the event. The stability and universality of the standard logic are ensured, the personalized needs are met through flexible extension mechanism and precise user mapping, the system maintainability and scalability are improved through decoupled design, the data consistency is guaranteed by unified transaction, the development threshold is reduced by simple extension method, and the adaptability and practicality of the system in complex industrial environments are greatly enhanced.

[0044] Those skilled in the art will appreciate that embodiments of the application can be provided as methods, systems, or computer program products. Accordingly, the application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the application can take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROMs, optical storage media, etc.) having computer-usable program code embodied in the medium.

[0045] The present application is described in reference to the flowchart illustrations and / or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart illustrations and / or block diagrams. Figure 1 one or more functions specified in the flowchart illustrations and / or block diagrams. Figure 1 one or more functions specified in the flowchart illustrations and / or block diagrams.

[0046] These computer program instructions can also be stored in a computer- readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instructions which implement the functions specified in the flowchart illustrations and / or block diagrams. Figure 1 one or more functions specified in the flowchart illustrations and / or block diagrams. Figure 1 one or more functions specified in the flowchart illustrations and / or block diagrams.

[0047] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart illustrations and / or block diagrams. Figure 1 one or more functions specified in the flowchart illustrations and / or block diagrams. Figure 1 one or more functions specified in the flowchart illustrations and / or block diagrams.

[0048] While the preferred embodiments of the application have been described, additional variations and modifications can be made to the embodiments by those of skill in the art once they have the benefit of the present disclosure without departing from the spirit and scope of the application. Accordingly, the attached claims are intended to embrace all such variations and modifications as fall within the scope of the present application.

[0049] Obviously, numerous modifications and variations of the present application are possible in light of the above teachings. It is therefore to be understood that within the scope of the appended claims and their equivalents, the application can be practiced otherwise than as specifically described.

Claims

1. A software framework for industrial manufacturing execution complex system partition implementation, characterized in that, The application relates to a three-layer system for realizing industrial manufacturing, which comprises a business layer, a control layer and a configuration layer. The business layer comprises a general area and an extension area. The general area is used for realizing standard logic of industrial manufacturing, and only one set of unified standard logic exists to cover basic processes and functions commonly used in the industry. The extension area is used for executing industry or enterprise characteristic logic, each characteristic logic exists in the form of an independent module, contains exclusive data processing rules, business trigger conditions and output format definitions, and realizes data intercommunication with the general area and other extension modules through standardized adaptive interfaces, when new characteristic demands are added, the extension can be completed by adding an independent module without modifying existing logic. The control layer is below the business layer and is used for scheduling standard contents of the general area and characteristic contents of the extension area, and is internally provided with a scheduling engine and a priority judgment module. The scheduling engine identifies standard contents and characteristic contents to be executed by analyzing business trigger signals, and the priority judgment module determines the execution sequence of the two according to preset rules. When there are multiple extension area characteristic contents, the modules are called in sequence according to the registration sequence.

2. The software framework for partitioning implementation of an industrial manufacturing execution complex system of claim 1, wherein, The configuration layer is at the bottom and is used for realizing mapping of users and extension contents, can complete associated configuration of users and different business extension areas, and comprises a user identity recognition interface, an extension content index library and a mapping relationship storage unit. When extension contents are not mapped with users, the mapping relationship storage unit feeds back a null value, and the control layer only calls the standard content execution link of the general area after receiving the null value signal. The general area and the extension area of the business layer adopt a code completely isolated design mode, and the general area and the extension area are respectively managed and maintained by independent code repositories.

3. The software framework for partitioning implementation of an industrial manufacturing execution complex system of claim 1, wherein, For the extension area, if there are multiple different extension contents, including characteristic logic of different industries or individualized logic of different enterprises in the same industry, each extension content is configured with an independent code repository, and code isolation is maintained between the extension contents. The general area, the extension area and the extension contents realize code isolation through independent code repositories, so that the business logic of the general area and the extension area can independently evolve, the general area iterates industry standards, and the extension area is updated according to specific demands. The configuration layer realizes associated configuration of users and different business extension areas, specifically by establishing mapping relationship between user identity and corresponding extension area in the system.

4. The software framework for partitioning implementation of an industrial manufacturing execution complex system of claim 1, wherein, The control layer identifies the identity information of the current user in real time, and automatically calls the characteristic logic of the extension area associated with the user according to the mapping relationship between user identity and extension area in the configuration layer, and simultaneously calls the standard logic of the general area to jointly complete business processing. For users not associated with any extension area, the control layer only calls and executes the standard logic of the general area. Information interaction between the general area and the extension area is realized by adopting a publish-subscribe mode. The general area actively sends corresponding event notifications when a specific business node is reached during execution, and the event notifications contain related information of the specific business node. The extension area pre-subscribes required event notifications, and executes corresponding extension logic according to the notification content after receiving the corresponding event notification sent by the general area. The general area sends event notification according to standard flow, and the extension area only processes the content of the subscribed event notification.

5. The software framework for partition implementation of an industrial manufacturing execution complex system of claim 4, wherein, The initiation, delivery and processing of the event notification are all implemented by the control layer; The general area of the business layer triggers event notification according to preset interface specification, and the extension area receives the notification and executes the extension logic; the routing, distribution and execution timing control of the notification are completed by the control layer; The standard code of the general area and the characteristic code of the extension area are executed in the same transaction, and when the general logic and the extension logic involve data operation, both of them are successfully executed and committed, or all are rolled back in case of exception.

6. The software framework for partition implementation of an industrial manufacturing execution complex system of claim 4, wherein, Any business location of the general area of the business layer can insert and send event notification, which is not limited by specific function modules or code structure, and event notification points can be set at the starting stage, intermediate link and end node of the standard flow according to business needs; The event notification can carry any number and type of objects or variables, including business data, context information and other related content.

7. The software framework for partition implementation of an industrial manufacturing execution complex system of claim 1, wherein, The extension logic supported by the framework includes enhancement, replacement and deletion; The enhancement logic is to add additional characteristic processing steps based on the execution of the standard logic of the general area, including adding industry-specific optimization rules after the standard production plan is generated; The replacement logic is to completely replace a part of the standard logic of the general area with the characteristic logic of the extension area, which is used for business links with unique processing methods, including replacing the general quality inspection logic with the enterprise's self-defined quality inspection process; The deletion logic is to cancel a part of the standard logic in the general area that is not applicable to a specific user, including removing some unnecessary report generation steps for the user.

8. The software framework for partition implementation of an industrial manufacturing execution complex system of claim 1, wherein, When the extension area accesses the general area, the developer adds a line of specific format annotation before the custom extension code, which can complete the association and docking of the extension content and the general area. The extension code includes extension classes or extension methods. The annotation contains key information for identifying the associated event notification, which enables the control layer to identify the correspondence between the extension code and the general area event.

9. A software framework method for partitioning implementation of an industrial manufacturing execution complex system, said software framework method for partitioning implementation of an industrial manufacturing execution complex system applying the software framework for partitioning implementation of an industrial manufacturing execution complex system according to any one of claims 1 to 8, characterized in that, It includes: First, insert event notification at the target business node of the general area of the business layer, and achieve it by calling the preset notification sending interface, while carrying the context parameters of the business node; Second, create an industry or enterprise extension code repository, and generate a packable maven project based on the repository. The project generates a jar package after compilation, which is introduced into the general area project in a package-dependent manner; Third, define extension classes and extension methods in the extension project, and add specific annotations before the extension methods to specify the events subscribed by the methods; Fourth, execute the mvn clean deploy command to package and upload the extension project to the public maven repository for the general area project to reference.

10. A software framework method for partitioning implementation of an industrial manufacturing execution complex system, said software framework method for partitioning implementation of an industrial manufacturing execution complex system applying the software framework for partitioning implementation of an industrial manufacturing execution complex system according to any one of claims 1 to 8, characterized in that, It also includes: Fifth, define the coordinate information of the extension package in the pom file of the general area project, and introduce the extension package into the general area project; Sixth, configure the permission mapping of users and extension packages through the system management background, and specify the users who can use the extension package. Step 7, after running the system, the control layer loads all the user's extension package configurations to the cache, and when the user triggers an event in the general area, the control layer calls the corresponding extension code according to the cached configuration information, and cooperates with the general code to complete the business execution.

Images