CN117764538B - Business process generation method, device and equipment - Google Patents
Business process generation method, device and equipment Download PDFInfo
- Publication number
- CN117764538B CN117764538B CN202410179831.3A CN202410179831A CN117764538B CN 117764538 B CN117764538 B CN 117764538B CN 202410179831 A CN202410179831 A CN 202410179831A CN 117764538 B CN117764538 B CN 117764538B
- Authority
- CN
- China
- Prior art keywords
- water
- attribute information
- water service
- service flow
- metadata
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 133
- 230000008569 process Effects 0.000 title claims abstract description 82
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 claims abstract description 172
- 238000007726 management method Methods 0.000 claims description 105
- 238000013461 design Methods 0.000 claims description 35
- 238000002955 isolation Methods 0.000 claims description 31
- 238000012544 monitoring process Methods 0.000 claims description 15
- 238000003860 storage Methods 0.000 claims description 12
- 238000004458 analytical method Methods 0.000 claims description 11
- 230000000007 visual effect Effects 0.000 claims description 10
- 230000006399 behavior Effects 0.000 claims description 9
- 238000013500 data storage Methods 0.000 claims description 8
- 238000012545 processing Methods 0.000 claims description 8
- 238000004140 cleaning Methods 0.000 claims description 5
- 238000007689 inspection Methods 0.000 claims description 5
- 238000004590 computer program Methods 0.000 claims description 3
- 230000008859 change Effects 0.000 abstract description 9
- 230000006978 adaptation Effects 0.000 abstract description 5
- 230000006870 function Effects 0.000 description 9
- 238000007405 data analysis Methods 0.000 description 8
- 238000012360 testing method Methods 0.000 description 7
- 238000013523 data management Methods 0.000 description 6
- 238000011161 development Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 6
- 230000007246 mechanism Effects 0.000 description 6
- 230000004048 modification Effects 0.000 description 6
- 238000012986 modification Methods 0.000 description 6
- 238000004891 communication Methods 0.000 description 4
- 238000004659 sterilization and disinfection Methods 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 230000010354 integration Effects 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- ZAMOUSCENKQFHK-UHFFFAOYSA-N Chlorine atom Chemical compound [Cl] ZAMOUSCENKQFHK-UHFFFAOYSA-N 0.000 description 2
- 229910052801 chlorine Inorganic materials 0.000 description 2
- 239000000460 chlorine Substances 0.000 description 2
- 238000000354 decomposition reaction Methods 0.000 description 2
- 238000005286 illumination Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 239000007788 liquid Substances 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 238000004806 packaging method and process Methods 0.000 description 2
- 230000006798 recombination Effects 0.000 description 2
- 238000005215 recombination Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 239000008186 active pharmaceutical agent Substances 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000013499 data model Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000001151 other effect Effects 0.000 description 1
- 238000013468 resource allocation Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
Classifications
-
- Y—GENERAL 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
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02A—TECHNOLOGIES FOR ADAPTATION TO CLIMATE CHANGE
- Y02A20/00—Water conservation; Efficient water supply; Efficient water use
- Y02A20/152—Water filtration
Landscapes
- Stored Programmes (AREA)
Abstract
The invention provides a method, a device and equipment for generating a business process. The method for generating the business process comprises the following steps: acquiring attribute information of a water management system in a metadata form; configuring component elements required by the water service flow according to the attribute information of the water service management system in the metadata form; invoking at least one component element through the microservice event; and performing at least one operation on the at least one component element in a template area of the water service flow to generate the water service flow. The scheme provided by the invention can realize the rapid adaptation and personalized operation of the flow change of the water management system.
Description
Technical Field
The present invention relates to the field of computer information processing technologies, and in particular, to a method, an apparatus, and a device for generating a business process.
Background
In the smart water service industry, the solution of the traditional water service management system often appears to be inflexible and poorly adapted in face of the highly customized demands of the plant management systems of different scales and demands. These systems tend to be hard-coded and difficult to quickly adapt to changes in business processes and emerging operational requirements.
Disclosure of Invention
The invention provides a method, a device and equipment for generating a business process, which solve the technical problem that the existing system cannot adaptively generate the water business process.
In order to solve the technical problems, the technical scheme of the invention is as follows:
a business process generation method comprises the following steps:
acquiring attribute information of a water management system in a metadata form;
Configuring component elements required by the water service flow according to the attribute information of the water service management system in the metadata form;
invoking at least one component element through the microservice event;
And performing at least one operation on the at least one component element in a template area of the water service flow to generate the water service flow.
Optionally, acquiring attribute information of the water management system in the form of metadata includes:
and acquiring attribute information of the water management system in the form of metadata from a preset data source.
Optionally, according to the attribute information of the water service management system in the metadata form, the configuration of the component elements required by the water service flow includes:
Analyzing the attribute information of the water management system in the metadata form to obtain configuration information;
And carrying out attribute configuration on the component elements required by the water service flow according to the configuration information.
Optionally, invoking at least one component element by a microservice event, comprising:
Obtaining logic relations among all nodes of the water service flow;
And calling at least one component element through a micro-service event according to each node of the water service flow and the logic relation among the nodes.
Optionally, according to each node of the water service flow and the logic relationship between each node, invoking at least one component element through a micro service event, including:
Calling micro-service events corresponding to all nodes according to all nodes of the water service flow;
And calling at least one component element through the micro-service event corresponding to each node according to the logic relation among the nodes, wherein one micro-service event corresponds to one component element.
Optionally, at least one operation is performed on the at least one component element in a template area of the water service flow, so as to generate the water service flow, including:
obtaining a template area of a water service flow;
Placing the at least one component element in the template region;
and performing at least one operation on the at least one component element to generate a water service flow.
Optionally, the method for generating the business process further includes:
And isolating and/or encrypting and storing the flow data of the water service flow belonging to different users.
The embodiment of the invention also provides a device for generating the business process, which comprises the following steps:
the acquisition module is used for acquiring attribute information of the water management system in the form of metadata;
the processing module is used for configuring the component elements required by the water service flow according to the attribute information of the water service management system in the metadata form; invoking at least one component element through the microservice event; and performing at least one operation on the at least one component element in a template area of the water service flow to generate the water service flow.
The present invention also provides a computing device comprising: a processor, a memory storing a computer program which, when executed by the processor, performs the method as described above.
The invention also provides a computer readable storage medium storing instructions that when executed on a computer cause the computer to perform a method as described above.
The scheme of the invention at least comprises the following beneficial effects:
According to the scheme, the attribute information of the water management system in the form of metadata is obtained; configuring component elements required by the water service flow according to the attribute information of the water service management system in the metadata form; invoking at least one component element through the microservice event; at least one operation is carried out on the at least one component element in the template area of the water service flow to generate the water service flow, and the generated service flow of the water service management system can be generated through self-adaptive operation, so that the efficiency of generating the service flow is improved, and the requirement of intelligent water service can be met.
Drawings
FIG. 1 is a flow diagram of a method for generating a business flow according to an embodiment of the present invention;
FIG. 2 is a schematic block diagram of a water management system for a business process according to an embodiment of the present invention;
FIG. 3 is a schematic block diagram of a micro-service and containerized service deployment of a business process according to an embodiment of the present invention;
FIG. 4 is a schematic block diagram of a business process according to an embodiment of the present invention;
FIG. 5 is a schematic architecture diagram of a multi-tenant data management isolation mechanism for a business process according to an embodiment of the invention;
fig. 6 is a block diagram of a business process generating apparatus according to an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present invention are shown in the drawings, it should be understood that the present invention may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.
As shown in fig. 1, an embodiment of the present invention proposes a method for generating a service flow, including:
step 11, acquiring attribute information of a water management system in a metadata form;
Step 12, configuring the component elements required by the water service flow according to the attribute information of the water service management system in the metadata form;
step 13, calling at least one component element through a micro-service event;
And 14, performing at least one operation on the at least one component element in a template area of the water service flow to generate the water service flow.
The embodiment of the invention obtains the attribute information of the water management system in the form of metadata; configuring component elements required by the water service flow according to the attribute information of the water service management system in the metadata form; invoking at least one component element through the microservice event; at least one operation is carried out on the at least one component element in a template area of the water service flow to generate the water service flow, and the service flow of the water service management system can be generated through self-adaptive operation, so that the efficiency of generating the service flow is improved, and the requirements of intelligent water service can be met.
As shown in fig. 2, a schematic block architecture of the water management system includes: the edge equipment access layer is positioned on the data acquisition layer at the upper layer of the edge equipment access layer, and after the data acquisition layer acquires data, the data are transmitted to the platform layer through the network layer to carry out related equipment management modules, data analysis modules and application management modules; the platform layer transmits the result of the related data processing to the application service layer for generating a corresponding water service flow, and the application service layer carries out metadata form of attribute information of the water service management system; configuring component elements required by the water service flow according to the attribute information of the water service management system in the metadata form; invoking at least one component element through the microservice event; at least one operation is carried out on the at least one component element in a template area of the water service flow, so that the water service flow is generated; and finally, displaying the water service flow on a display layer.
Specifically, in the application services layer, data-driven dynamic attribute management is supported: when the system is started, metadata is first loaded from a preset source (e.g., database, configuration file, environment variable, etc.). These metadata contain key information about the behavior and properties of the system;
parsing and application configuration: the system parses the metadata and configures itself according to the information. Including setting database connections, service ports, security policies, etc.
Dynamic attribute management, defining various attributes in the system, such as connection strings, service parameters, etc. These properties are not defined statically in the code, but rather are specified dynamically by metadata.
Attribute reading and application: the system reads these properties at run-time and adjusts its behavior based on the property values. For example, changing the database connection string may allow the system to connect to a different database.
Runtime configuration adjustment, dynamic modification support: the system design allows for dynamic modification of metadata at runtime, thereby changing system behavior. Such modifications may be made through various interfaces, such as web interfaces, API calls, and the like.
Real-time reaction: after modifying the metadata, the system may react to these changes in real-time or under predetermined conditions without requiring a reboot or reload.
In an alternative embodiment of the present invention, the step 11 includes:
and acquiring attribute information of the water management system in the form of metadata from a preset data source.
In the above embodiment, the metadata is data describing data and its environment, and includes attribute information about system behavior. The preset data sources comprise: databases, configuration files, environment variables, etc. The system attribute information includes a connection string, service parameters, and the like. Further, the system can dynamically acquire the system attribute information in the form of the metadata after being modified at runtime, so that the system attribute information is not statically defined in the data, but is dynamically specified by the metadata.
Further, corresponding component elements are configured for the business process according to the system attribute information in the form of metadata acquired from the preset data source; then invoking at least one component element forming the business process through a micro-service event; and finally, placing at least one invoked component element in the acquired template area and performing at least one operation to generate the business flow. The system solves the technical problems that the existing system is not flexible enough and has poor adaptability, and is difficult to adapt to business process change and personalized operation.
In an alternative embodiment of the present invention, the step 12 includes:
Step 121, analyzing the attribute information of the water management system in the metadata form to obtain configuration information;
And step 122, carrying out attribute configuration on the component elements required by the water service flow according to the configuration information.
In this embodiment, the configuration information includes database connection information, service port information, security policy information, and the like. The database connection information includes a host name, a user name, a password, etc., and the service port information may be a designated system communication port number, etc.
Specifically, in the water management system, the component elements may include: work order management, water service pump house management, water tank cleaning service, process monitoring, inspection service, document library, equipment management, operation analysis and the like. The components constituting the assembly element may include: presetting a built model and presetting a built scene. The preset built model comprises the following components: drainage pit valve, immersible pump, relief valve, flowmeter, manometer, pump, online residual chlorine appearance, online turbidity appearance, ultraviolet disinfection appearance, floater level switch, static pressure liquid level appearance, water tank inflow flow meter, total inflow flowmeter, valve, pipe network pressure gauge, axial fan, dehumidifier, ball machine, shot-light, waterproof fluorescent lamp, entrance guard, disinfection appearance switch board, blowdown control box, illumination block terminal, branch accuse cabinet, master control cabinet etc.. The preset built scene may include: a single unit pump room, a double unit pump room, a three unit pump room, a four unit pump room and the like.
The analysis of the system attribute information in the metadata form means that the structure, meaning and relationship of the system attribute information in the metadata form are analyzed and understood, and the component elements can know the meaning, the attribute, the relationship among the system attribute information and the like of the system attribute information by analyzing the system attribute information in the metadata form and configuring the attribute of the component elements by the configuration information obtained after the analysis.
Because the system attribute information in the metadata form can be dynamically modified, the system can acquire the modified system attribute information in the metadata form when in operation, analyze the system attribute information in the metadata form to obtain new configuration information, and then use the new configuration information to carry out attribute configuration on the component elements, thereby realizing the dynamic attribute management of the system and being completed without restarting or reloading the system. For example: changing the database connection string in the system attribute information may allow the component elements to connect to different databases.
And by using metadata to perform attribute configuration on the component elements in the water service flow, not only is higher flexibility provided, but also the service adaptation and innovation speed can be accelerated by customizing the data structure and the service flow logic through a simple interface.
In an alternative embodiment of the present invention, the step 13 may include:
Step 131, obtaining each node of the water service flow and the logic relationship between each node;
And step 132, calling at least one component element through a micro-service event according to each node of the water service flow and the logic relation among each node.
In an alternative embodiment of the present invention, the step 132 may include:
step 1321, calling micro service events corresponding to each node according to each node of the water service flow;
step 1322, according to the logical relationship between the nodes, invoking at least one component element through a micro-service event corresponding to each node, where one micro-service event corresponds to one component element.
In the above embodiment, according to the number of the nodes and the component elements corresponding to each node in the acquired water service flow, a corresponding number of micro service events are established for each node, so as to ensure that each micro service event corresponds to one component element. And calling a corresponding micro-service event according to the logic relation among the nodes. The micro-service events can all operate independently, so that a user can upgrade and maintain the component elements independently without affecting the normal operation of other component elements. Since the microservice events are invoked according to the logical relationships between the nodes, so that each microservice event corresponds to a specific function, responsibilities, interfaces, and interaction protocols need to be defined for each microservice event.
Through the micro-service event, each component element can be independently invoked, as if each component element (such as user authority management, work order management, process monitoring and the like) were independently placed in a different 'small box' to operate, and the components are not mutually interfered. Since each microservice event can be developed by an independent team, so that different technology stacks and databases may be used between microservice events, interfaces and contracts between microservice events need to be defined to ensure compatibility and interoperability between microservice events.
The node of the water service flow is equivalent to the container mirror image of one or more micro service events, and the node contains codes, a runtime library and setting information required for running the micro service events corresponding to the node. Container management tools are used to handle creation, deployment, extension, and termination of the nodes. Using automation tools (such as CI/CD pipeline), micro-service events are deployed into corresponding nodes, such as: test nodes, pre-production nodes, etc.
For the water service management system, different component elements can be respectively generated into independent micro services, and then deployed into corresponding nodes and operated. For example, one can deploy these component elements into one node to enable them to be monitored and analyzed independently, while one can deploy one component element, such as a data analysis component, into another node to enable them to perform data analysis and report generation independently.
The maintainability and the expandability of the system are improved by deploying the component elements into the corresponding nodes through the micro-service events, so that a user can independently upgrade and maintain one module without affecting the normal operation of other modules. Meanwhile, rapid deployment and expansion are realized through a Docker et al container technology, and the method is suitable for distributed and heterogeneous environments. Particularly in the water management system, the method can combine the characteristics of the water service stations, bring remarkable improvement to the reliability, maintainability and expandability of the water management system, and is particularly suitable for the decentralized water service infrastructure management.
In an example, the process of generating the graphical water service flow is as follows:
1. Initializing a user interface, and starting the interface: when a user activates a tool, an intuitive user interface is presented first, which typically includes a menu bar, a toolbar, a flow design area, and a property editing area. Loading a component library: the tool loads a library of components containing a plurality of components from which the user can select the desired component.
2. Creating a new water service flow: a new water business process is started, and a blank canvas or base template is provided for the user to edit.
Selection and placement component: the user selects a desired node from the component library and places it in the design area by a drag-and-drop operation.
3. Design and connection flow nodes: the user connects each node through the visualized connection line to form a complete graphical water service flow. These connection lines represent data streams or control streams.
Configuring node attributes: each node has its own attributes, and can click on the node and configure in the attribute editing area, such as setting parameters, defining behaviors, etc.
Further, the graphical water service flow chart may be created or modified using a graphical tool. The graphical tool displays the relevant parameters and the expected results in real time, helping the operator to make decisions.
The graphical water service flow design tool comprises two modules which are dragged by a user-defined mode. The first is directed to: the visual interface for displaying interface information of the functional modules such as pump house management, water tank cleaning service, process monitoring, inspection service, document library, equipment management and operation analysis can be freely dragged and dragged to define and generate a service flow. The second is to process monitoring module, which can perform graphic model process design, including 2D,3D and other effects. The installation field process equipment live view map is modeled into a corresponding planar or 3D perspective view display. The graphical water business process design tool can enable a user to connect all nodes through visual connecting lines to form a complete process flow. These connection lines represent data streams or control streams. And the tool displays relevant parameters and expected results in real time to help the user to operate. The tool simplifies the complex water business process design into visual graphical operation, and compared with the traditional mode of depending on coding or fixing a template, the method is easier to use, can respond to the requirement of actual operation change more quickly, and improves the autonomy and flexibility of operation.
As shown in fig. 3, the micro-services and containerized traffic deployment:
1. defining a micro-service architecture, and splitting services: the application is split into multiple small, independent services, each of which is responsible for a specific function of the application, such as user rights management, work order management, process monitoring, etc.
Service definition: for each microservice, its responsibilities, interfaces, and interaction protocols are defined.
2. Development of micro services: each microservice is developed independently, using a technology stack and a database, which may be different.
Interfaces and contracts for communication between services are defined, ensuring compatibility and interoperability between services.
3. Containerization service, build container mirror: a container image is built for each micro-service, containing the code, runtime, libraries, and settings needed to run the service.
And (3) container management: container management tools (e.g., docker, kubernetes) are used to handle the creation, deployment, extension, and termination of containers.
4. Deploying the micro-service, and automatically deploying: micro-services are deployed into predefined environments, such as testing, pre-production, etc., using automated tools (e.g., CI/CD pipeline).
Service discovery: the service discovery mechanism is configured so that micro services can be located and communicate with each other.
Highly custom front end UI component library:
1. demand analysis: a need analysis is first performed to determine which types of components (e.g., buttons, forms, input boxes, charts, etc.) are necessary.
Design principle: the principles and criteria of component design are determined, such as accessibility, responsive design, consistency, and extensibility.
2. Component development, prototype design: prototypes were designed for each component, and their basic structure and functionality were determined.
Coding realization: these components are encoded using front-end techniques (e.g., HTML, CSS, javaScript, act, vue. Js, etc.).
Style customization: the style customizing function of the assembly is realized, so that the appearance can be easily changed as required.
3. Component test, unit test: unit tests are written for each component to ensure the correctness and stability of the independent functions.
And (3) integration test: and (3) performing an integration test to ensure the compatibility and performance of different components when working together.
4. Packaging and publishing
Packaging component library: tools (e.g., webpack or Rollup) are used to package component libraries that are easy to introduce and use in different projects.
Multi-tenant data management and isolation mechanism
1. User identification and login, user login: the system user logs into the account.
User identification: each user is assigned a unique identifier for identifying and isolating its data in the system.
2. Data storage policy, physical isolation: a separate database instance or Schema (Schema) is created in the database for each tenant, thereby enabling physical data isolation.
Logic isolation: and marking attribution for each data through the tenant ID in the shared database, thereby realizing logic isolation.
3. Data access control, access control policy: role-based access control (RBAC) is implemented to ensure that tenants can only access their own data.
Context-aware query: all database queries are filtered through tenant context, so that data isolation is ensured.
4. Multi-tenant resource management, resource allocation: the system allocates necessary resources (e.g., memory space, computing power) for each user and dynamically adjusts according to the needs.
Performance isolation: ensuring that the load of one tenant does not affect the performance of other tenants.
5. Security and compliance, data encryption: and encrypting the stored data to enhance the data security.
Compliance: ensuring that the data processing complies with the relevant data protection and privacy regulations.
In an alternative embodiment of the present invention, the step 14 may include:
step 141, obtaining a template area of the business process;
Step 142, placing the at least one component element in the template area;
and step 143, performing at least one operation on the at least one component element to generate a business process.
In this embodiment, the template area is an area capable of generating the business process after the system is started, and the template area may be an intuitive user interface. Specifically, the template area may be a blank canvas or a basic panel for editing by a user, and the interface includes a menu bar, a toolbar, a flow design area and a property editing area. The method comprises the steps of obtaining a template area of a business process, loading nodes forming the business process, a component library which comprises a plurality of component elements and can be customized, a database and a technical stack corresponding to each component element and connecting lines among the component elements. The assembly elements and the connecting lines among the assembly elements are visualized, and the assembly elements can be placed in the template area in a dragging mode or the like.
And placing the at least one component element in the template area, and then connecting a plurality of component elements through visualized connecting lines according to actual requirements, so that at least one operation is performed on the at least one component element, and a business process is generated. In particular, the visualized connection lines represent data streams or control streams. Since the attributes of the component elements differ, the attributes of the component elements can be configured within the attribute editing area in the template area. For example: setting parameters, defining behaviors, etc. Meanwhile, the template area can display relevant parameters of the component elements and expected results of the business process in real time, so that the decision making function of an operator is helped.
By visualizing the component elements, the connecting lines and the business process nodes, the complex business process design is simplified into visual graphical operation, different business processes can be designed, and meanwhile, a friendly user interface is provided, so that a user can easily create, modify and optimize the business processes. The user can design the business flow meeting the own requirements in modes of dragging component elements, setting attributes and the like. Compared with the traditional mode of depending on coding or fixed template, the method can respond to the requirement of actual operation change more quickly, provides higher autonomy and flexibility for operators, improves the operability and usability of the system, and enables users to respond to service change more quickly.
The at least one operation on the at least one component element further includes setting a set of componentized, reusable and configurable components from the component library for the business process, as if "furniture" were purchased from "parts supermarket", which can greatly reduce costs of interface development and maintenance.
As shown in fig. 4: the following is a business process:
Step 1: and starting and initializing the system, and loading a dynamic attribute management system driven by metadata. This step is the "out of box" of the system. The system allows configuration during operation, and dynamic adjustment is performed according to special requirements of different stations. The design method reduces the modification of the code layer and improves the flexibility and maintainability of the system. Meanwhile, through dynamic attribute management driven by metadata, the system can better adapt to the continuously-changing service requirements.
For example, when the system is started, it will read configuration information from the metadata, such as database connections, service ports, security policies, etc. According to the configuration information, the system can flexibly adjust the self behavior so as to meet the requirements of different stations.
Step 2: the user carries out visual configuration through a graphical water service flow design tool to design different technological flows. The tool provides a friendly user interface that allows a user to easily create, modify, and optimize a process flow. The technological process meeting the requirements of the user can be designed by dragging process nodes, setting node attributes and the like. At the same time, the tool automatically generates monitoring points and control logic and updates the process flow database. The design method improves the operability and usability of the system, and enables users to respond to service changes more quickly.
This step provides the basis for subsequent flow execution and monitoring.
Step 3: each module operates independently as a micro-service using micro-service and containerized service deployment. For example, the system may operate different modules of user rights management, work order management, process monitoring, etc. as independent micro-services, respectively. This step is just like each module (e.g. user rights management, work order management, process monitoring, etc.) is run in a separate "small box" without interfering with each other. The design method improves maintainability and expandability of the system, so that a user can independently upgrade and maintain one module without affecting normal operation of other modules. Meanwhile, rapid deployment and expansion are realized through a Docker et al container technology, and the method is suitable for distributed and heterogeneous environments. The design method can reduce the deployment time and cost of the system and improve the flexibility and expandability of the system.
Step 4: the highly customized front end UI component library provides a set of componentized, highly multiplexed, and configurable UI components according to user requirements. For example, a user may select components in different UI component libraries, such as tables, forms, charts, etc., based on their own preferences and business needs. These components are highly reusable and configurable, like "furniture" is selected from "parts supermarket", which can greatly reduce the cost of interface development and maintenance.
Step 5: the multi-tenant data management and isolation mechanism ensures isolation and security of different plant data. The design method can improve the data security, the integrity and the maintainability of the system. For example, the system can isolate and manage data of different plant stations through a multi-tenant mode. The step is just like that an independent room is established for each station, and the data in each room can only be managed and used by the corresponding station, so that the safety and isolation of the data are ensured.
For water pump plants, the reusable and configurable components can be built by selecting appropriate component elements from a component library according to user requirements. The reusable and configurable components include forms, charts, and the like. Specifically, the user can select a map positioning component, a patrol track component, a file library component and the like, and meanwhile, the reusable and configurable component can also support functions of data analysis, report generation and the like of the cross-plant station so as to better meet the business requirements of the user.
By providing a set of customizable and reusable component libraries to support various user interface requirements, rapid development of the system and speed of responding to user feedback can be supported, and personalized use experience is provided for different user groups.
Specifically, in the water management system, the component elements may include: work order management, water service pump house management, water tank cleaning service, process monitoring, inspection service, document library, equipment management, operation analysis and the like. The components constituting the assembly element may include: presetting a built model and presetting a built scene. The preset built model comprises the following components: drainage pit valve, immersible pump, relief valve, flowmeter, manometer, pump, online residual chlorine appearance, online turbidity appearance, ultraviolet disinfection appearance, floater level switch, static pressure liquid level appearance, water tank inflow flow meter, total inflow flowmeter, valve, pipe network pressure gauge, axial fan, dehumidifier, ball machine, shot-light, waterproof fluorescent lamp, entrance guard, disinfection appearance switch board, blowdown control box, illumination block terminal, branch accuse cabinet, master control cabinet etc.. The preset built scene may include: a single unit pump room, a double unit pump room, a three unit pump room, a four unit pump room and the like.
By visualizing the component elements, the connecting lines and the business process nodes, the complex business process design is simplified into visual graphical operation, different business processes can be designed, and meanwhile, a friendly user interface is provided, so that a user can easily create, modify and optimize the business processes. Just like the high building blocks of the music, the user can design the business flow meeting the own requirements in modes of dragging component elements, setting attributes and the like. Compared with the traditional mode of depending on coding or fixed template, the method can respond to the requirement of actual operation change more quickly, provides higher autonomy and flexibility for operators, improves the operability and usability of the system, and enables users to respond to service change more quickly. Compared with the traditional mode of coding or fixing templates, the method is easier to use, can respond to the requirement of actual operation change more quickly, and provides unprecedented autonomy and flexibility for plant operators.
In an optional embodiment of the present invention, the method for generating a business process further includes: and isolating and/or encrypting and storing the flow data of the business flows belonging to different users.
In this embodiment, isolating flow data of the business flows belonging to different users includes user identification, data storage policy, data access control, and multi-tenant resource management.
Wherein the user identification assigns a unique identifier to each user, which serves to identify and isolate account data for each user in the system.
The data storage strategy comprises physical isolation and logical isolation. Wherein physical isolation is the creation of separate database instances or schemas in the database for each user. Logical quarantine is to tag each piece of data in the shared database with its own address.
The data access control is to implement role-based access control, so that users can only access own data, and the database inquiry needs to be filtered, so that data isolation is ensured.
The multi-user resource management includes allocating necessary resources (e.g., memory space, computing power) for each user, and dynamically adjusting according to the needs and ensuring that the load of one user does not affect the performance of the other user.
Encrypting the process data pertaining to the business processes for different users includes encrypting the user data, ensuring that the data processing complies with data protection and privacy regulations.
As shown in fig. 5, the data security, integrity and maintainability of the system can be improved by isolating and/or cryptographically storing the flow data of the business flows belonging to different users. For example, the system may isolate and manage data for different users. This step is just like an independent "room" is created for each user, and the data in each room can only be managed and used by the corresponding user, ensuring the security and isolation of the data. For example, in a water service management system, supporting data analysis and report generation across plant sites while maintaining data security and isolation is particularly important for large water service companies or government institutions to manage multiple water service facilities. Since data of different water pump stations may have isolation and security requirements, we perform isolation and/or encryption storage on flow data of the business flows belonging to different users to ensure that data of different water pump stations are isolated and managed. Each water pump station user has own data storage and management space, and can only access and manage own data but cannot access the data of other stations. Therefore, the privacy and the safety of the data can be effectively protected, and meanwhile, the data of different station users can be independently analyzed and managed, so that the service demands of the different station users can be better met.
As shown in fig. 6, an embodiment of the present invention further provides a device 60 for generating a service flow, including:
an acquisition module 61, configured to acquire attribute information of the water management system in a metadata form;
The processing module 62 is configured to configure component elements required by the water service flow according to the attribute information of the water service management system in the metadata form; invoking at least one component element through the microservice event; and performing at least one operation on the at least one component element in a template area of the water service flow to generate the water service flow.
Optionally, acquiring attribute information of the water management system in the form of metadata includes:
and acquiring attribute information of the water management system in the form of metadata from a preset data source.
Optionally, according to the attribute information of the water service management system in the metadata form, the configuration of the component elements required by the water service flow includes:
Analyzing the attribute information of the water management system in the metadata form to obtain configuration information;
And carrying out attribute configuration on the component elements required by the water service flow according to the configuration information.
Optionally, invoking at least one component element by a microservice event, comprising:
Obtaining logic relations among all nodes of the water service flow;
And calling at least one component element through a micro-service event according to each node of the water service flow and the logic relation among the nodes.
Optionally, according to each node of the water service flow and the logic relationship between each node, invoking at least one component element through a micro service event, including:
Calling micro-service events corresponding to all nodes according to all nodes of the water service flow;
And calling at least one component element through the micro-service event corresponding to each node according to the logic relation among the nodes, wherein one micro-service event corresponds to one component element.
Optionally, at least one operation is performed on the at least one component element in a template area of the water service flow, so as to generate the water service flow, including:
obtaining a template area of a water service flow;
Placing the at least one component element in the template region;
and performing at least one operation on the at least one component element to generate a water service flow.
Optionally, the processing module 62 is further configured to isolate and/or cryptographically store flow data of the business flow belonging to different users.
It should be noted that, the device is a device corresponding to the above method, and all implementation manners in the above method embodiments are applicable to the embodiment of the device, so that the same technical effects can be achieved.
When the device is realized, the comprehensive modularized system for intelligent water management is realized, and the dynamic attribute management system driven by metadata is as follows: and the configuration in the running process is allowed to adapt to the special requirements of different stations, so that the code level is not required to be changed. Graphical water business process design tool: visual configuration is provided, so that a user can design different process flows conveniently, and monitoring points and control logic are automatically generated.
Micro-services and containerized traffic deployment: each module independently operates as a micro-service, and rapid deployment and expansion are realized by utilizing a Docker et al container technology, so that the method is suitable for distributed and heterogeneous environments.
Highly custom front end UI component library: a set of componentized, highly multiplexed, and configurable UI component libraries is provided for quickly building interfaces that meet user needs.
Multi-tenant data management and isolation mechanism: the isolation and the safety of the data of different stations are ensured, and meanwhile, the data analysis and report generation of the cross-station are supported.
Standardization and reusability of core service modules: the core modules such as user authority management, work order management, process monitoring and the like are designed as standardized modules which can be multiplexed among different stations.
By using metadata definition and dynamic attribute management, the system can adapt to different service requirements and improve flexibility.
The graphical design tool converts the process flow design into intuitive graphical operations, and a user can design and adjust the process flow by dragging and dropping and configuring elements.
The plug-in design of the security system allows for the rapid integration or replacement of security modules according to specific security requirements, improving the adaptability and security of the system.
The micro-service architecture enables each functional module to be independently run and updated, while the containerization technique simplifies the deployment and expansion of the modules.
The rich elements in the UI component library support the user to quickly construct and modify the interface according to the personalized requirements.
The multi-tenant architecture allows complex data analysis and report generation while guaranteeing data security, and is suitable for managing a plurality of water facilities.
Metadata driven dynamic attribute management system: most existing water management systems are relatively fixed in terms of data models and are difficult to accommodate for rapidly changing business requirements. The metadata-driven dynamic attribute management system not only provides higher flexibility, but also allows custom data structures and business logic through a simple interface. The method is a breakthrough in water service industry management software, can obviously reduce the dependence on technical experts, and accelerates the service adaptation and innovation.
A graphical process flow design tool: the tool simplifies the complex process flow design into visual graphical operation, is easier to use in the water management system, can respond to the requirement of actual operation change more quickly, and provides better autonomy and flexibility for factory operators.
Micro-services and containerized traffic deployment: in the water management system, the reliability, maintainability and expandability of the system are obviously improved, and the system is particularly suitable for decentralized water infrastructure management.
Highly custom front end UI component library: a set of highly customized and reusable UI component libraries is provided to support various user interface requirements. It supports rapid development and response to user feedback, providing a personalized use experience for different user groups.
Multi-tenant data management and isolation mechanism: and data analysis and report generation of cross-plant stations are supported while data security and isolation are maintained.
Standardization and reusability of core service modules: the standardization and reusability of the modules such as user authority management, work order management, process monitoring and the like improves the universality and expansibility of the system, and reduces the cost of new function deployment and maintenance.
There is also provided, in an embodiment of the present invention, a computing device including: a processor, a memory storing a computer program which, when executed by the processor, performs the method as described in the above embodiments. All the implementation manners in the method embodiment are applicable to the embodiment, and the same technical effect can be achieved.
Embodiments of the present invention also provide a computer readable storage medium storing instructions that, when executed on a computer, cause the computer to perform a method as described in the above embodiments. All the implementation manners in the method embodiment are applicable to the embodiment, and the same technical effect can be achieved.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk, etc.
Furthermore, it should be noted that in the apparatus and method of the present invention, it is apparent that the components or steps may be disassembled and/or assembled. Such decomposition and/or recombination should be considered as equivalent aspects of the present invention. Also, the steps of performing the series of processes described above may naturally be performed in chronological order in the order of description, but are not necessarily performed in chronological order, and some steps may be performed in parallel or independently of each other. It will be appreciated by those of ordinary skill in the art that all or any of the steps or components of the methods and apparatus of the present invention may be implemented in hardware, firmware, software, or a combination thereof in any computing device (including processors, storage media, etc.) or network of computing devices, as would be apparent to one of ordinary skill in the art after reading this description of the invention.
The object of the invention can thus also be achieved by running a program or a set of programs on any computing device. The computing device may be a well-known general purpose device. The object of the invention can thus also be achieved by merely providing a program product containing program code for implementing said method or apparatus. That is, such a program product also constitutes the present invention, and a storage medium storing such a program product also constitutes the present invention. It is apparent that the storage medium may be any known storage medium or any storage medium developed in the future. It should also be noted that in the apparatus and method of the present invention, it is apparent that the components or steps may be disassembled and/or assembled. Such decomposition and/or recombination should be considered as equivalent aspects of the present invention. The steps of executing the series of processes may naturally be executed in chronological order in the order described, but are not necessarily executed in chronological order. Some steps may be performed in parallel or independently of each other.
While the foregoing is directed to the preferred embodiments of the present invention, it will be appreciated by those skilled in the art that various modifications and adaptations can be made without departing from the principles of the present invention, and such modifications and adaptations are intended to be comprehended within the scope of the present invention.
Claims (5)
1. A method for generating a business process, comprising:
acquiring attribute information of a water management system in a metadata form;
Configuring component elements required by the water service flow according to the attribute information of the water service management system in the metadata form;
invoking at least one component element through the microservice event;
at least one operation is carried out on the at least one component element in a template area of the water service flow, so that the water service flow is generated;
Wherein, according to the attribute information of the water management system in the metadata form, the component elements required by the water business process are configured, comprising:
Analyzing the attribute information of the water management system in the metadata form to obtain configuration information;
performing attribute configuration on the component elements required by the water service flow according to the configuration information;
wherein invoking at least one component element through a microservice event comprises:
obtaining the number of each node of the water service flow and the corresponding component elements of each node, and establishing a corresponding number of micro-service events for each node, wherein one micro-service event corresponds to one component element;
obtaining a logic relationship among nodes of the water service flow;
the component elements may include: user account management, work order management, water service pump room management, water tank cleaning service, process monitoring, inspection service, document library, equipment management and operation analysis; the components constituting the assembly element may include: presetting a built model and presetting a built scene;
using container management tools to handle creation, deployment, extension, and termination of the nodes; deploying the microservice events into respective nodes using an automation tool;
generating independent micro-services respectively by different component elements, and then deploying the independent micro-services into corresponding nodes and operating;
Invoking at least one component element through a micro-service event according to the logic relationship among the nodes of the water service flow; the node comprises codes, a runtime library and setting information which are required by running the micro service event corresponding to the node;
Wherein, at least one operation is performed on the at least one component element in a template area of the water service flow, and the generating of the water service flow includes:
Obtaining a template area of a water service flow; the template area is an intuitive user interface, wherein the user interface comprises a menu bar, a tool bar, a flow design area and a property editing area, and is used for loading nodes forming the business flow, a component library which comprises a plurality of component elements and can be customized, a database and a technical stack corresponding to each component element and connecting lines among the component elements; wherein the component elements and the connecting lines between the component elements are visualized; the visualized connection lines represent data streams or control streams;
Placing the at least one component element in the template region;
the at least one component element is connected through a visual connecting line to generate a water service flow;
Acquiring attribute information of a water management system in a metadata form from a preset data source;
the metadata is descriptive data and data of the environment, and contains attribute information about system behavior; the preset data sources comprise: a database, a configuration file, and an environment variable;
analyzing the system attribute information in the metadata form means analyzing and understanding the structure, meaning and relation of the system attribute information in the metadata form, and the component elements can know the meaning, attribute and relation among the system attribute information by analyzing the system attribute information in the metadata form and configuring the attribute of the component elements by the configuration information obtained after analysis;
The system obtains the system attribute information in the form of the modified metadata when running, analyzes the system attribute information in the form of the metadata to obtain new configuration information, and uses the new configuration information to perform attribute configuration on the component elements so as to realize dynamic attribute management of the system;
According to each node of the water service flow and the logic relation among each node, invoking at least one component element through a micro service event, wherein the invoking comprises the following steps:
Calling micro-service events corresponding to all nodes according to all nodes of the water service flow;
invoking at least one component element through a micro-service event corresponding to each node according to the logic relationship among the nodes;
the method for generating the business process further comprises the following steps:
isolating and/or encrypting and storing the flow data of the business flows belonging to different users;
Isolating process data of the business processes belonging to different users comprises user identification, data storage strategies, data access control and multi-tenant resource management; the user identification is used for assigning a unique identifier to each user and playing a role in identifying and isolating account data of each user in the system; the data storage strategy comprises physical isolation and logical isolation, wherein the physical isolation is to create independent database examples or modes in a database for each user, and the logical isolation is to mark attribution for each data in a shared database through a user address.
2. The method for generating a business process according to claim 1, wherein acquiring the water management system attribute information in the form of metadata comprises:
and acquiring attribute information of the water management system in the form of metadata from a preset data source.
3. A business process generation device, comprising:
the acquisition module is used for acquiring attribute information of the water management system in the form of metadata;
The processing module is used for configuring the component elements required by the water service flow according to the attribute information of the water service management system in the metadata form; invoking at least one component element through the microservice event; at least one operation is carried out on the at least one component element in a template area of the water service flow, so that the water service flow is generated;
Wherein, according to the attribute information of the water management system in the metadata form, the component elements required by the water business process are configured, comprising:
Analyzing the attribute information of the water management system in the metadata form to obtain configuration information;
performing attribute configuration on the component elements required by the water service flow according to the configuration information;
wherein invoking at least one component element through a microservice event comprises:
obtaining the number of each node of the water service flow and the corresponding component elements of each node, and establishing a corresponding number of micro-service events for each node, wherein one micro-service event corresponds to one component element;
obtaining a logic relationship among nodes of the water service flow;
the component elements may include: user account management, work order management, water service pump room management, water tank cleaning service, process monitoring, inspection service, document library, equipment management and operation analysis; the components constituting the assembly element may include: presetting a built model and presetting a built scene;
using container management tools to handle creation, deployment, extension, and termination of the nodes; deploying the microservice events into respective nodes using an automation tool;
generating independent micro-services respectively by different component elements, and then deploying the independent micro-services into corresponding nodes and operating;
Invoking at least one component element through a micro-service event according to the logic relationship among the nodes of the water service flow; the node comprises codes, a runtime library and setting information which are required by running the micro service event corresponding to the node;
Wherein, at least one operation is performed on the at least one component element in a template area of the water service flow, and the generating of the water service flow includes:
Obtaining a template area of a water service flow; the template area is an intuitive user interface, wherein the user interface comprises a menu bar, a tool bar, a flow design area and a property editing area, and is used for loading nodes forming the business flow, a component library which comprises a plurality of component elements and can be customized, a database and a technical stack corresponding to each component element and connecting lines among the component elements; wherein the component elements and the connecting lines between the component elements are visualized; the visualized connection lines represent data streams or control streams;
Placing the at least one component element in the template region;
the at least one component element is connected through a visual connecting line to generate a water service flow;
Acquiring attribute information of a water management system in a metadata form from a preset data source;
the metadata is descriptive data and data of the environment, and contains attribute information about system behavior; the preset data sources comprise: a database, a configuration file, and an environment variable;
analyzing the system attribute information in the metadata form means analyzing and understanding the structure, meaning and relation of the system attribute information in the metadata form, and the component elements can know the meaning, attribute and relation among the system attribute information by analyzing the system attribute information in the metadata form and configuring the attribute of the component elements by the configuration information obtained after analysis;
The system obtains the system attribute information in the form of the modified metadata when running, analyzes the system attribute information in the form of the metadata to obtain new configuration information, and uses the new configuration information to perform attribute configuration on the component elements so as to realize dynamic attribute management of the system;
According to each node of the water service flow and the logic relation among each node, invoking at least one component element through a micro service event, wherein the invoking comprises the following steps:
Calling micro-service events corresponding to all nodes according to all nodes of the water service flow;
invoking at least one component element through a micro-service event corresponding to each node according to the logic relationship among the nodes;
the method for generating the business process further comprises the following steps:
isolating and/or encrypting and storing the flow data of the business flows belonging to different users;
Isolating process data of the business processes belonging to different users comprises user identification, data storage strategies, data access control and multi-tenant resource management; the user identification is used for assigning a unique identifier to each user and playing a role in identifying and isolating account data of each user in the system; the data storage strategy comprises physical isolation and logical isolation, wherein the physical isolation is to create independent database examples or modes in a database for each user, and the logical isolation is to mark attribution for each data in a shared database through a user address.
4. A computing device, comprising: a processor, a memory storing a computer program which, when executed by the processor, performs the method of any one of claims 1 to 2.
5. A computer readable storage medium, characterized in that instructions are stored which, when run on a computer, cause the computer to perform the method of any of claims 1 to 2.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202410179831.3A CN117764538B (en) | 2024-02-18 | 2024-02-18 | Business process generation method, device and equipment |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202410179831.3A CN117764538B (en) | 2024-02-18 | 2024-02-18 | Business process generation method, device and equipment |
Publications (2)
Publication Number | Publication Date |
---|---|
CN117764538A CN117764538A (en) | 2024-03-26 |
CN117764538B true CN117764538B (en) | 2024-05-31 |
Family
ID=90322281
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202410179831.3A Active CN117764538B (en) | 2024-02-18 | 2024-02-18 | Business process generation method, device and equipment |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN117764538B (en) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN118014334B (en) * | 2024-04-08 | 2024-06-07 | 微神马科技(大连)有限公司 | Service recording method and system |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3033894B1 (en) * | 1998-10-09 | 2000-04-17 | 横河電機株式会社 | Water supply business system |
CN109189381A (en) * | 2018-10-18 | 2019-01-11 | 行吟信息科技(上海)有限公司 | A kind of creation method and device of Business Stream component |
CN110516897A (en) * | 2019-06-03 | 2019-11-29 | 武汉市自来水有限公司 | A kind of water utilities nested type micro services system |
CN111241067A (en) * | 2020-01-14 | 2020-06-05 | 智恒科技股份有限公司 | Water affair big data mining modeling management method, device, equipment and medium |
CN113962549A (en) * | 2021-10-21 | 2022-01-21 | 广东电网有限责任公司 | Business process arrangement method and system based on power grid operation knowledge |
CN115658041A (en) * | 2022-12-27 | 2023-01-31 | 南京国睿信维软件有限公司 | Low code enhancement service implementing method based on-line service flow arrangement |
CN116485279A (en) * | 2023-06-13 | 2023-07-25 | 埃睿迪信息技术(北京)有限公司 | Equipment information processing method and device based on water management platform |
-
2024
- 2024-02-18 CN CN202410179831.3A patent/CN117764538B/en active Active
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3033894B1 (en) * | 1998-10-09 | 2000-04-17 | 横河電機株式会社 | Water supply business system |
CN109189381A (en) * | 2018-10-18 | 2019-01-11 | 行吟信息科技(上海)有限公司 | A kind of creation method and device of Business Stream component |
CN110516897A (en) * | 2019-06-03 | 2019-11-29 | 武汉市自来水有限公司 | A kind of water utilities nested type micro services system |
CN111241067A (en) * | 2020-01-14 | 2020-06-05 | 智恒科技股份有限公司 | Water affair big data mining modeling management method, device, equipment and medium |
CN113962549A (en) * | 2021-10-21 | 2022-01-21 | 广东电网有限责任公司 | Business process arrangement method and system based on power grid operation knowledge |
CN115658041A (en) * | 2022-12-27 | 2023-01-31 | 南京国睿信维软件有限公司 | Low code enhancement service implementing method based on-line service flow arrangement |
CN116485279A (en) * | 2023-06-13 | 2023-07-25 | 埃睿迪信息技术(北京)有限公司 | Equipment information processing method and device based on water management platform |
Also Published As
Publication number | Publication date |
---|---|
CN117764538A (en) | 2024-03-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP7275224B2 (en) | System and method for configuration of process plant using I/O abstraction field device configuration | |
CN112631555B (en) | System and method for developing industrial applications | |
US6643555B1 (en) | Method and apparatus for generating an application for an automation control system | |
CN117764538B (en) | Business process generation method, device and equipment | |
CN112558929A (en) | Artificial intelligence design analysis and recommendation | |
CN112558928A (en) | Virtual design environment | |
CN101589357B (en) | Check condition system used for human-computer interface | |
CN104756023B (en) | System building assistance tool and system | |
CN101788791B (en) | Application builder for industrial automation | |
CN103064356A (en) | Multiple deployment of applications with multiple configuration in industrial automation environment | |
JP6751551B2 (en) | Methods and equipment for configuring process control systems based on the general-purpose process system library | |
US20080148231A1 (en) | Computer-implemented system for analysis, administration, control, management and monitoring of a complex hardware/software architecture | |
CN101872280A (en) | In Process Control System operator interface configurations shown animation and incident | |
EP2419824A2 (en) | Utilizing spreadsheet user interfaces with flowsheets of a cpi simulation system | |
US20170131691A1 (en) | Group control and management among electronic devices | |
CN101763043A (en) | Method and system for an automation collaborative framework | |
US20170289731A1 (en) | Mobile Database Access Application Development System and Method | |
CN109976803A (en) | A kind of generation method and device of file | |
CN103792857A (en) | Scalable automation system | |
Gray et al. | A standardised modular approach for site SCADA applications within a water utility | |
Padget et al. | Deontic Sensors. | |
JP2014035687A (en) | Engineering system and monitoring control method thereof | |
US11853727B2 (en) | Group control and management among electronic devices | |
CN103714035B (en) | Multilayer software bus structure for integrated environment | |
CN107392414B (en) | Product data integration arrangement method and cloud service device |
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 |