Ship control system information layer software design method based on process engine

Abstract

The invention discloses a process engine-based ship control system information layer software design method, which comprises the following steps of: 1) carrying out demand analysis, and determining a task process involved in a scene; 2) summarizing generality among task processes, and constructing a corresponding hierarchical model; and 3) flow node decomposition and combined construction: converting the abstract model into an executable flow. According to the method, control tasks, which need to be realized by ship control system information layer software, in different fields of the ship are described by adopting a universal task flow design language, so that control connection and linkage of the ship in different fields can be realized, and the communication cost of control linkage among different fields is reduced; and the development cost is also reduced by a graphical interface.

Description

TECHNICAL FIELD

[0001] The present application relates to software development technology, and in particular to a ship control system information layer software design method based on a process engine. BACKGROUND

[0002] At present, the ship control system can be divided into power, electric power, auxiliary machinery and other systems according to the system, and each system is divided into multiple levels. In the ship control system, an embedded controller (such as PLC) or an industrial computer with preliminary data processing capability and basic control capability is often used as the control flow end, and more control and human-computer interaction functions are realized through information layer software. The number of devices that need to be collected and controlled on the whole ship is large, and the control flow information flow is complex, which leads to various information layer software architectures, and there are barriers to interconnection and intercommunication between each software to realize comprehensive control.

[0003] At present, the information layer software of the ship control system mainly adopts three design methods.

[0004] (1) The first method is to use LabVIEW. LabVIEW uses G language for graphical programming and has powerful real-time data acquisition and analysis processing capability, and is mainly used for developing test and measurement systems. However, LabVIEW is not adapted to domestic operating systems. At the same time, as a product of the American NI company, the authorization fee is high.

[0005] (2) The second method is to use configuration software. Configuration software (such as InTouch, WinCC, etc.) has a graphical interface and provides a convenient and easy-to-use development environment for developers. The disadvantage of using this method to realize ship comprehensive control is that the configuration software ecology is relatively closed, and the compatibility of different systems, different configuration software, and different versions of the same software is poor, making it difficult to realize interconnection and intercommunication between systems.

[0006] (3) The third method is to use programming language for customized development by a software development team. The advantage of this method is that it has high customization degree, and the disadvantage of using this method to realize ship comprehensive control is that this development method often takes a long time to develop and needs a long time for performance verification.

[0007] The current mainstream ship control system design method has the disadvantages of poor compatibility and high development cost. With the increasing requirements of ship integration and intelligence, the ability of ship control system to realize cross-field comprehensive control is becoming higher and higher, and there is an urgent need to propose a new ship control system information layer software design method to realize comprehensive and collaborative control of different systems and different levels in the ship control system and improve the design level of the ship control system. SUMMARY

[0008] The technical problem solved by the present application is to provide a ship control system information layer software design method based on a process engine in view of the defects in the prior art.

[0009] The technical solution adopted by the present application to solve its technical problem is: a ship control system information layer software design method based on a process engine, comprising the following steps: 1) performing requirement analysis to clearly define the task processes involved in the scene; The task processes of the ship control system information layer software are hierarchically divided according to the following dimensions, including the equipment internal dimension, the equipment between dimension and the system between dimension; 2) inducing the commonality among the task processes to build a corresponding hierarchical model; including: 2.1) designing the equipment task process: corresponding to the internal control logic of the equipment, specifically as follows: 2.1.1) extracting the physical properties, executable instructions and state threshold information of the target equipment; 2.1.2) clearly defining that the equipment task process includes three types of elements: virtual properties, virtual events and virtual services; 2.1.3) integrating the physical properties, virtual properties, virtual events and virtual services of the equipment to form a standardized equipment task process model; 2.2) designing the collaborative task process based on the equipment task process: 2.3) designing the scene task process based on the collaborative task process: 3) flow node decomposition and combination construction to convert the abstract model into an executable process.

[0010] According to the above scheme, in the step 1), the equipment internal dimension, the equipment between dimension and the system between dimension are specifically as follows: Equipment internal dimension: focusing on the logical calculation, event triggering and service execution related processes of a single equipment; Equipment between dimension: focusing on the linkage and cooperation processes of multiple equipments in the same system; System between dimension: focusing on the scene linkage control processes across systems.

[0011] According to the above scheme, in the step 2.1.2), the three types of elements: virtual properties, virtual events and virtual services are specifically as follows: Virtual property: the name and identification of a special property generated by logical calculation of multiple equipment properties; Virtual event: the description of an event generated by one or more attribute values as preset conditions; Virtual service: triggering the platform to issue instructions to the equipment with the rule output result as the precondition.

[0012] According to the above scheme, the step 2.2) is specifically as follows: 2.2.1) Define the target of the cooperative scenario, screen the list of devices participating in the linkage, and call the device task flow model corresponding to each device; 2.2.2) Linkage rule definition; Determine the input and output attributes, and determine the interaction parameters between the device models and the execution sequence of the device operation; 2.2.3) Connect / parallel the multiple device task flow models according to the linkage rule, add the task flow name, associated device list, input and output attributes, scene label, and form the cooperative task flow model.

[0013] According to the above scheme, the step 2.3) is specifically as follows: 2.3.1) Obtain the target of the cross-system scenario, disassemble the list of systems involved in the scenario, and sort out the triggering conditions of the scenario; 2.3.2) Call the cooperative task flow model and the device task flow model in the related system, and determine the triggering relationship between the systems; 2.3.3) Integrate the cross-system cooperative task flow model and the device task flow model according to the scene logic, add the scene name, associated system list, triggering condition, and exception handling rule, and form the scene task flow model.

[0014] According to the above scheme, the step 3) is specifically as follows: 3.1) Disassemble all task flows into four types of standard nodes: user nodes, event nodes, control nodes, and judgment nodes. The four types of standard nodes correspond to the core functions of input and output, event listening, interface operation, and logical judgment, respectively, to realize the standardization of flow description; 3.2) Use the flow engine for graphical flow design. Different types of nodes are pre-made in the flow node library, and the flow can be constructed by dragging from the flow node library; According to the above scheme, in the step 3.2), the graphical flow design is performed using the flow engine, which is specifically as follows: Through graphical dragging, the order of the device task flow, the cooperative task flow, and the scene task flow is used to associate various nodes to complete flow construction.

[0015] According to the above scheme, in the step 3.2), the flow construction is completed according to the node type to perform corresponding operations, and the specific operations are as follows: User node execution operation: wait for user confirmation operation to complete the business action of the node; Event node execution operation: wait for device event reporting to complete the business action of the node; The control node performs an operation: the control node configures a device of the node to issue a control instruction, and the flow engine accesses a control instruction interface of the device, and when called, performs device control according to a preset logic; The judgment node performs an operation: the judgment logic written in the node is executed to determine the branch of the execution flow; According to the next node indicated by the node, the operation corresponding to the node is executed in a loop until the entire flow is executed.

[0016] The beneficial effects of the present application are: 1、 The present application describes a common task flow design language for different field control tasks of a ship that need to be realized by a ship control system information layer software, simplifies the complex task flow into four types of nodes, and compared with a traditional ship control system information layer software design method, can realize the control of different fields of the ship, reduces the communication cost of control linkage between different fields, and the graphical interface also reduces the development cost. BRIEF DESCRIPTION OF DRAWINGS

[0017] The present application will be further described below in combination with the drawings and embodiments, and the drawings are as follows: Figure 1 is a method flowchart of an embodiment of the present application; Figure 2 is a flow engine working principle diagram of an embodiment of the present application. DETAILED DESCRIPTION

[0018] In order to make the purpose, technical scheme and advantages of the present application more clear, the present application will be further described in combination with embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application, and are not used to limit the present application.

[0019] As shown in Figure 1 , a ship control system information layer software design method based on a flow engine includes the following steps: 1) Perform requirement analysis to clearly define the task flow involved in the scene; The task flow of the ship control system information layer software is hierarchically divided according to the following dimensions, including the device internal dimension, the device between dimension and the system between dimension; Device internal dimension: focusing on the logical calculation, event triggering, service execution related flow of a single device; Device between dimension: focusing on the linkage and cooperation flow of multiple devices in the same system; System between dimension: focusing on the scene linkage control flow across systems; 2) Induce the commonality between the task flows to build a corresponding hierarchical model; including: 2.1) Design device task flow: corresponding to the internal control logic of the device, as follows: 2.1.1) Extract the basic information of the target device, such as physical properties (such as voltage, current, temperature), executable instructions (such as opening and closing valves, starting and stopping units), state threshold values (such as high temperature alarm threshold), etc. 2.1.2) Clearly, the device task flow contains three types of elements: virtual properties, virtual events, and virtual services. Virtual properties: the name and identification of special properties generated by logical calculation of multiple device properties. For example: when the power cannot be directly measured, the power P is calculated by voltage U╳current I.

[0020] Virtual events: the description (name and identification) of events generated by one or more attribute values as preset conditions. For example: when the cabin temperature reaches the threshold, a high temperature event is generated. Virtual services: the output results as preconditions to trigger platform-issued device instructions. For example: first issue instruction one, and then issue instruction two after receiving the response message. 2.1.3) Integrate the physical properties, virtual properties, virtual events, and virtual services of the device to form a standardized device task flow model. 2.2) Design collaborative task flow based on device task flow: collaborative task flow corresponds to multi-device linkage in the same system; the collaborative task flow model associates the attributes, services, and events of multiple devices, and the collaborative task flow includes task flow name, associated devices, input and output attributes, and realizes the orderly cooperation between devices. 2.2.1) Clearly define the target of the collaborative scenario (such as working condition switching), filter the list of participating devices, and call the corresponding device task flow model of each device. 2.2.2) Linkage rule definition. Determine input and output attributes: clearly define the interaction parameters between device models and the execution order of device operations. 2.2.3) Connect multiple device task flow models in series / parallel according to the linkage rules, add task flow name, associated device list, input and output attributes, scene tag, and form a collaborative task flow model. 2.3) Design scene task flow based on collaborative task flow: scene task flow corresponds to cross-system linkage; scene task flow contains multiple device models, collaborative task flow, and scene linkage, and the core is to integrate device task flow, collaborative task flow, and multi-system resources to respond to complex scene requirements (such as cross-system emergency disposal in the case of fire in the power station cabin).

[0021] 2.3.1) Obtain the core goal of the cross-system scenario (such as emergency disposal of power plant cabin fire), disassemble the system list involved in the scenario (such as power system, fire fighting system, pipeline system), and sort out the trigger condition of the scenario (such as temperature too high + fire sensor alarm); 2.3.2) Call the cooperative task process model in the related system (such as generator set load transfer cooperation model) and equipment task process model, and clarify the trigger relationship between systems; 2.3.3) Integrate the cross-system cooperative task process model and equipment task process model according to the scene logic, add scene name, related system list, trigger condition, and abnormal handling rule, and form a scene task process model; 3) Process node decomposition and combination construction, convert abstract model to executable process; 3.1) All task processes are disassembled into four types of standard nodes: user node, event node, control node, and judgment node. The four types of standard nodes correspond to the core functions of input and output, event listening, interface operation, and logic judgment, realizing the standardization of process description; 3.2) As Figure 2 , use the process engine for graphical process design. Different types of nodes are pre-made in the process node library, which can be dragged out from the process node library to build the process; Through graphical dragging, the order of equipment task process, cooperative task process, and scene task process is used to associate various nodes to complete process construction; Among them, the completion of process construction is according to the type of node to perform corresponding operation, the specific operation is as follows: User node execution operation: wait for user confirmation operation to complete node business action; Event node execution operation: wait for device to report event to complete node business action; Control node execution operation: give the device configured by the node to issue control instruction, the process engine will access the control instruction interface of the device, and when called, it will control the device according to the preset logic; Judgment node execution operation: execute the judgment logic written in the node to determine the branch of the execution process; According to the next node pointed by the node, the operation corresponding to the node is executed in a loop until the entire process is executed.

[0022] An application example: Using a hierarchical ship control system design method based on process engine, the linkage control of ship fire fighting system and mechanical and electrical system is completed.

[0023] Step one: carry out requirement analysis, and make clear the task flow involved in the scene, the task flow existing in the device, the task flow between devices, and the task flow between systems. In this example, the task flow existing in the device includes checking water pressure before spraying, etc. The task flow between devices includes water pressure control between the fire pump and the fire spraying device. The task flow between systems includes the associated control of the fire spraying and the power-off of the cabin area.

[0024] Step two: summarize the commonality between the task flows, and form the task flow model. The modeling process of the task flow model in different levels is as follows: The task flow existing in the device and the device task flow, for example, set the checking flow before spraying in the fire spraying device. If the water pressure is insufficient, prompt the spraying failure and alarm.

[0025] The task flow between devices, i.e. the collaborative task flow, for example, when the water pressure of the fire spraying is insufficient, increase the running power of the fire pump.

[0026] The task flow between systems, i.e. the scene task flow, for example, before the fire pump starts to spray, the mechanical and electrical system should cut off all power equipment in the target cabin through the distribution board to avoid secondary disasters.

[0027] Step three. Decompose and connect each task according to the four types of nodes (user node, event node, control node, and judgment node), for example, the user's order to extinguish the fire is the user node, the alarm of the fire alarm is the event node, the start of the fire spraying device is the control node, and whether the cabin sealing extinguishing condition is met is the judgment node. According to the order of the device task flow, the collaborative task flow, and the scene task flow, the flow is constructed in the flow engine. The former task flow should be used as the basis for the design of the latter task flow. For example, when constructing the control flow of "increasing the pressure of the water supply pump due to insufficient fire water pressure", the "checking the fire water pressure of the fire spraying device" can be called as a node.

[0028] It should be understood that those skilled in the art can make improvements or changes according to the above description, and all these improvements and changes should belong to the protection scope of the appended claims of the present application.

Claims

1. A process engine based software design method for information layer of a ship control system, characterized in that, Comprising the following steps: 1) Conduct a needs analysis to identify the task processes involved in the scenario; The task processes of the information layer software of the ship control system are hierarchically divided into the following dimensions, Including the internal dimension of the device, the dimension between devices, and the dimension between systems; 2) Induce the commonality between task processes and build corresponding hierarchical models, including: 2.1) Designing device task processes: corresponding to the internal control logic of the device, as follows: 2.1.1) Extracting the physical properties, executable instructions, and state threshold information of the target device; 2.1.2) Identifying that the device task process includes three types of elements: virtual properties, virtual events, and virtual services; 2.1.3) Integrating the physical properties, virtual properties, virtual events, and virtual services of the device to form a standardized device task process model; 2.2) Designing collaborative task processes based on device task processes: 2.3) Designing scenario task processes based on collaborative task processes: 3) Process node decomposition and combination construction to convert abstract models into executable processes.

2. The process engine based ship control system information layer software design method according to claim 1, characterized in that, In step 1), the internal dimension of the device, the dimension between devices, and the dimension between systems are as follows: Internal dimension of the device: focusing on the logical calculation, event triggering, and service execution related processes of a single device; Dimension between devices: focusing on the linkage and collaboration processes of multiple devices within the same system; Dimension between systems: focusing on the scenario-based linkage control processes across systems.

3. The process engine based ship control system information layer software design method according to claim 1, characterized in that, In step 2.1.2), the three types of elements: virtual properties, virtual events, and virtual services are as follows: Virtual properties: the name and identification of special properties generated by logical calculation of multiple device properties; Virtual events: the description of events generated by one or more attribute values as preset conditions; Virtual services: triggering platform-issued device instructions with rule-based output results as preconditions.

4. The process engine based ship control system information layer software design method according to claim 1, characterized in that, In step 2.2), the details are as follows: 2.2.1) Clearly define the target of the collaborative scenario, filter the list of devices involved in the linkage, and call the corresponding device task process model of each device; 2.2.2) Define linkage rules; Determine input and output properties, and clearly define the interaction parameters between device models and the execution order of device operations; 2.2.3) Connect / parallel multiple device task process models according to linkage rules, add task process names, associated device lists, input and output properties, and scenario tags to form collaborative task process models.

5. The process engine based ship control system information layer software design method according to claim 1, characterized in that, In step 2.3), the details are as follows: 2.3.1) Obtain the target of the cross-system scenario, decompose the list of systems involved in the scenario, and sort out the triggering conditions of the scenario; 2.3.2) Call the collaborative task process model and device task process model of the related system, and clearly define the triggering relationship between systems; 2.3.3) Integrate the collaborative task process model and device task process model across systems according to the scenario logic, add scenario names, associated system lists, triggering conditions, and exception handling rules to form a scenario task process model.

6. The process-engine-based ship control system information layer software design method according to claim 1, characterized in that, In step 3), the details are as follows: 3.1) all task processes are disassembled into four types of standard nodes, i.e. user nodes, event nodes, control nodes and judgment nodes, the four types of standard nodes correspond to the core functions of input and output, event listening, interface operation and logical judgment respectively, and the standardization of process description is realized; 3.2) graphical process design is performed using a process engine, different types of nodes are prefabricated in a process node library, and the process can be constructed by dragging from the process node library.

7. The process-engine based ship control system information layer software design method according to claim 6, characterized in that, In the step 3.2), graphical process design is performed using a process engine, and the specific process is as follows: In a graphical dragging manner, the process is constructed by associating various types of nodes in the order of device task process, collaborative task process and scenario task process through data flow.

8. The process-engine-based ship control system information layer software design method according to claim 7, characterized in that, In the step 3.2), the process construction is completed according to the operation of the corresponding node type, and the specific operation is as follows: The operation of the user node: after the user confirms the operation, the business action of the node is completed; The operation of the event node: after the device reports the event, the business action of the node is completed; The operation of the control node: the device configured for the node issues a control instruction, the control instruction interface of the device is connected in the process engine, and when called, the device is controlled according to the preset logic; The operation of the judgment node: the judgment logic written in the node is executed to determine the branch of the execution process; The operation corresponding to the node is executed according to the next node indicated by the node, and the whole process is executed until the whole process is executed. 9.A computer device, comprising a memory and a processor, wherein the memory stores a computer program, and the computer device is configured to perform the method according to any one of claims 1-8 when the computer program is executed by the processor. The processor executes the computer program to realize the steps of the method of any one of claims 1 to 8.

10. A computer-readable storage medium having stored thereon a computer program, characterized in that, The computer program is executed by the processor to realize the method of any one of claims 1 to 8.

Images