Creation support apparatus, creation support method, and creation support program
The creation support system automates the generation of specialized plant operation documents by associating templates with system components, reducing manual effort and ensuring consistency in SOPs and narratives.
Patent Information
- Application Number
- JP2023107117
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-06-29
- Publication Date
- 2025-01-17
- Estimated Expiration
- 2043-06-29
AI Technical Summary
Existing technologies face challenges in creating highly specialized documents such as SOPs and narratives for plant operations, requiring extensive manual effort and consistency checks across multiple documents.
A creation support system that utilizes templates for system components, allowing engineers to select modules in a configuration diagram, associate them with document templates, and automatically generate and update SOPs and narratives based on setting information.
Facilitates easy creation of highly specialized documents with reduced manual effort, ensures consistency, and reduces the risk of errors by automating the process of generating SOPs and narratives.
Smart Images

Figure 2025006368000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a creation support device, a creation support method, and a creation support program. [Background technology]
[0002] SOP (Standard Operating Procedure) is a standard operating procedure used in plant operations. Plant operators operate the plant using the SOP document as the master. SOP is created from a control specification called a narrative created by EPC (Engineering-Procurement-Construction) companies, etc. [Prior art documents] [Non-patent literature]
[0003] [Non-Patent Document 1] Yokogawa Electric Corporation, Yokogawa Solution Services Corporation: “CENTUM VP”, [online], [Retrieved May 25, 2023], Internet <https: / / www.yokogawa.co.jp / solutions / products-and-services / control / control-and-safety-system / distributed-control-systems-dcs / centum-vp / > Summary of the Invention [Problem to be solved by the invention]
[0004] However, with the above technology, it is difficult to create documents such as narratives and SOPs that require high levels of expertise and are used in plants. For example, in order to create an SOP, it is necessary to create a narrative as text data, and further refer to many documents such as ICSS (Integrated Control and Safety System) applications and tag lists, and check the consistency between the documents, which makes it very difficult to create.
[0005] The present invention has been made in view of the above, and has an object to easily create highly specialized documents. [Means for solving the problem]
[0006] The present invention provides a creation support device that includes a memory unit that stores templates of each module indicating functional units of system components and templates of documents that explain the functions of each module or define procedures for operational control of each module, in association with each other; a reception unit that accepts selection of a specific module included in a configuration diagram that indicates the configuration of the system; and an output unit that outputs a document of the selected specific module based on setting information set for the components included in the selected specific module and the document template associated with the template of the selected specific module.
[0007] The present invention also provides a creation support method in which a computer executes a process in which it retains templates of each module indicating functional units of the components of a system in association with document templates that explain the functions of each module or define procedures for operational control of each module, accepts selection of a specific module included in a configuration diagram showing the configuration of the system, and outputs a document of the selected specific module based on setting information set for the components included in the selected specific module and the document template associated with the template of the selected specific module.
[0008] The present invention also provides a creation support program that causes a computer to execute a process of storing templates of each module indicating functional units of the components of a system in association with document templates that explain the functions of each module or define procedures for operational control of each module, accepting selection of a specific module included in a configuration diagram that indicates the configuration of the system, and outputting a document of the selected specific module based on setting information set for the components included in the selected specific module and the document template associated with the template of the selected specific module. Effect of the Invention
[0009] According to the present invention, it is possible to easily create highly specialized documents. [Brief description of the drawings]
[0010] [Figure 1] 1 is a diagram illustrating a configuration example and a processing example of a creation support system according to an embodiment; [Diagram 2] 2 is a block diagram showing an example of the configuration of an engineer terminal of the creation support system according to the embodiment; FIG. [Diagram 3] FIG. 4 is a diagram illustrating an example of a library information storage unit of the engineer terminal according to the embodiment. [Figure 4] FIG. 13 is a diagram illustrating an example of an output result storage unit of the engineer terminal according to the embodiment. [Diagram 5] FIG. 2 is a diagram showing a specific example 1 of a process of the creation support system according to the embodiment. [Figure 6] FIG. 11 is a diagram showing a specific example 2 of the process of the creation support system according to the embodiment. [Figure 7] FIG. 11 is a diagram showing a specific example 3 of the process of the creation support system according to the embodiment. [Figure 8] FIG. 11 is a diagram showing a specific example 4 of the process of the creation support system according to the embodiment. [Figure 9] FIG. 5 is a diagram showing a specific example 5 of the process of the creation support system according to the embodiment. [Figure 10] FIG. 6 is a diagram showing a specific example 6 of the process of the creation support system according to the embodiment. [Figure 11] FIG. 7 is a diagram showing a specific example 7 of the process of the creation support system according to the embodiment. [Figure 12] FIG. 8 is a diagram showing a specific example 8 of the process of the creation support system according to the embodiment. [Figure 13] FIG. 9 is a diagram showing a specific example 9 of the process of the creation support system according to the embodiment. [Figure 14] FIG. 10 is a diagram showing a specific example 10 of the process of the creation support system according to the embodiment. [Figure 15] FIG. 11 is a diagram showing a specific example 11 of the process of the creation support system according to the embodiment. [Figure 16] FIG. 12 is a diagram showing a specific example 12 of the process of the creation support system according to the embodiment. [Figure 17] FIG. 13 is a diagram showing a specific example 13 of the process of the creation support system according to the embodiment. [Figure 18] 1 is a flowchart showing an example of a process flow of a creation support system according to an embodiment. [Figure 19] FIG. 2 is a diagram illustrating an example of a hardware configuration according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0011] Hereinafter, a creation support device, a creation support method, and a creation support program according to an embodiment of the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to the embodiment described below.
[0012] [Embodiment] The configuration and processing of the creation support system 100 according to the embodiment, the configuration and processing of the engineer terminal 10 of the creation support system 100, and the processing flow of the creation support system 100 will be described below in order, and finally the effects of the embodiment will be described.
[0013] 1. Configuration and processing of the creation support system 100 The configuration and processing of the creation support system 100 according to the embodiment will be described in detail with reference to Fig. 1. Fig. 1 is a diagram showing an example of the configuration and processing of the creation support system 100 according to the embodiment. Below, an example of the configuration of the entire creation support system 100, an example of the processing of the entire creation support system 100, and problems with the creation support system 100P according to the reference technology will be described in order, and finally, the effects of the creation support system 100 will be described. Note that in the embodiment, factory production remote monitoring using plant equipment, which is a device installed in a plant, will be described as an example, but the device and field of use are not limited, and the invention can also be applied to environmental measurement remote monitoring such as power monitors, wind power generation, water and sewage monitors, and river monitors.
[0014] (1-1. Example of the overall configuration of the creation support system 100) An example of the overall configuration of the creation support system 100 will be described with reference to Fig. 1. The creation support system 100 has an engineer terminal 10. The engineer terminal 10 is a creation support device used by an engineer E who manages a plant control system. Here, the engineer terminal 10 is connected to devices and databases (not shown) so as to be able to communicate with each other by wire or wirelessly via a predetermined communication network (not shown). Note that the predetermined communication network can be any of various communication networks such as the Internet or a dedicated line.
[0015] The engineer terminal 10 accepts operations by an engineer E. The engineer terminal 10 is realized, for example, by a desktop PC (Personal Computer), a notebook PC, a smartphone, a tablet terminal, a smart watch, a mobile phone, a PDA (Personal Digital Assistant), etc. The example of Fig. 1 shows a case where the engineer terminal 10 is realized by a desktop PC.
[0016] 1 may include a plurality of engineer terminals 10. The engineer terminal 10 may be realized by an on-premise system, a cloud system, or the like.
[0017] (1-2. Example of the overall processing of the creation support system 100) An example of the overall processing of the creation support system 100 will be described with reference to Fig. 1. The processing of steps S1 to S6 below may be executed in a different order. Also, some of the processing of steps S1 to S6 below may be omitted.
[0018] (1-2-1. Library information setting process) First, the engineer terminal 10 sets library information (step S1). For example, the engineer terminal 10 acquires and stores library information created by an engineer E from past operation data of the plant.
[0019] Here, library information refers to information about modules that indicate functional units of the components that make up a plant, and is information that associates, for example, control typicals, which are templates for control loops, narrative templates, which are control specifications ("narrative templates" as appropriate), SOP templates, which are standard operating procedures for the plant ("SOP templates" as appropriate), etc.
[0020] (1-2-2. Control typical designation processing) Secondly, engineer E specifies a control typical on a digital P&ID (Piping and Instrument Diagram) (step S2). Here, the digital P&ID is a configuration diagram showing the configuration of a plant, and is a diagram including setting information such as the names of plant equipment, which are components. For example, engineer E operates the engineer terminal 10 to specify a plant. The engineer terminal 10 displays the digital P&ID of the plant specified by engineer E on a monitor screen. Engineer E operates the engineer terminal 10 to specify a control loop on the digital P&ID. The engineer terminal 10 displays a list of control typicals applicable to the control loop specified by engineer E (suitably referred to as a "control typical list") on a monitor screen. Engineer E operates the engineer terminal 10 to specify a control typical on the control typical list. The engineer terminal 10 accepts the control typical specified by engineer E. At this time, the engineer terminal 10 acquires setting information of the control loop specified by engineer E on the digital P&ID.
[0021] (1-2-3. Narrative output processing) Third, the engineer terminal 10 outputs a narrative (step S3). For example, the engineer terminal 10 acquires a narrative template linked to a control typical designated by the engineer E, and replaces setting items such as an equipment name of the narrative template with setting information acquired from the digital P&ID to generate text data and image data of a narrative that describes the function of the control loop, and displays the generated data on a monitor screen.
[0022] (1-2-4. SOP output processing) Fourth, the engineer terminal 10 outputs the SOP (step S4). For example, the engineer terminal 10 acquires an SOP template linked to a control typical designated by the engineer E, and replaces setting items such as an equipment name of the SOP template with setting information acquired from the digital P&ID to generate text data of an SOP indicating a procedure for controlling the operation of a control loop, and displays the text data on a monitor screen.
[0023] (1-2-5. Output result correction process) Fifth, engineer E modifies the output result (step S5). For example, engineer E operates the engineer terminal 10 to add alarm information to the plant equipment included in the text data of the narrative displayed on the monitor screen. At this time, the engineer terminal 10 displays on the monitor screen the text data of the narrative modified by engineer E, and also displays on the monitor screen the text data of the SOP that reflects the modified content of the narrative.
[0024] (1-2-6. Processing to reflect corrections) Sixth, the engineer terminal 10 reflects the correction content in the library information (step S6). For example, when alarm information is added to a plant device included in a narrative, the engineer terminal 10 adds the alarm information to a narrative template corresponding to the corrected narrative in the library information, and also adds the alarm information to a control typical and an SOP template linked to the narrative template.
[0025] (1-2-7.Others) In the above processing of steps S3 and S4, the narrative and SOP are described as output results, but the engineer terminal 10 can also display on the monitor screen a drawing of a control typical specified by the engineer E. The engineer terminal 10 can also display on the monitor screen an instantiation list showing a list of plant equipment constituting a control loop specified by the engineer E.
[0026] In addition, in the above-mentioned processing of steps S5 and S6, the processing of correcting the narrative has been described, but the engineer E can also correct the image data showing the drawing of the control typical and the text data of the SOP displayed on the monitor screen. At this time, when the text data of the SOP is corrected, the engineer terminal 10 corrects the SOP template corresponding to the corrected SOP in the library information, and corrects the control typical and the narrative template linked to the SOP template. In addition, when the image data showing the drawing of the control typical is corrected, the engineer terminal 10 corrects the control typical corresponding to the corrected image data in the library information, and corrects the narrative template and the SOP template linked to the control typical.
[0027] (1-3. Effects of the Creation Support System 100) In the following, the background of the plant, the outline and problems of a creation support system 100P according to the reference technology will be described, and then the effects of the creation support system 100 will be described.
[0028] (1-3-1. Background of the plant) In plants, bulk engineering is commonly used for engineering DCS (Distributed Control System) to generate control loops in bulk using control typicals, which are templates for control loops, and tag lists. In addition to tag names, control typicals contain setting items such as range information, industrial unit information, and control direction, and bulk engineering is realized by mechanically substituting the corresponding setting information from the tag list into the control typical.
[0029] In addition, SOPs are created as documents to be used in operating the plant. SOPs must be created before the plant is commissioned.
[0030] (1-3-2. Overview of the Creation Support System 100P) In the Creation Support System 100P, bulk engineering is realized using control typicals as described above, while the narratives, which are control specifications, are simply created as text data by EPC contractors, etc. Also, in the Creation Support System 100P, the SOPs, which are standard operating procedures, are created by DCS system vendors, etc., by referring to many documents such as narratives, ICSS applications, tag lists, etc.
[0031] (1-3-3. Problems with the 100P Creation Support System) The creation support system 100P has the following problems. First, in the creation support system 100P, it is necessary to create a narrative for each control loop, so creating a narrative is time-consuming. Second, in the creation support system 100P, it is necessary to create an SOP by referring to many documents such as narratives, ICSS applications, and tag lists, so it is difficult to create an SOP. In particular, in the creation support system 100P, the consistency of information in each document is not guaranteed, so knowledgeable engineer E must create the documents while checking the consistency between them. Third, in the creation support system 100P, after creating a narrative or SOP, it is necessary to modify each document corresponding to the approved narrative or SOP, so the burden on engineer E is large.
[0032] (1-3-4. Overview of the Creation Support System 100) First, the engineer terminal 10 sets library information in which control typicals, narrative templates, and SOP templates created from past plant operation data are organized into libraries. Second, the engineer terminal 10 accepts designation of control loops and control typicals by engineer E via the digital P&ID of the plant, and acquires setting information for the control loops. Third, the engineer terminal 10 displays, as output results, drawings of the control typicals designated, instantiation lists, narratives, and SOPs on the monitor screen. Fourth, when any of the output results is changed, the engineer terminal 10 reflects the changes in the library information to be saved.
[0033] (1-3-5. Effects of the Creation Support System 100) The creation support system 100 has the following effects. The effects on the system vendor and the effects on the EPC contractor or plant manager will be described below.
[0034] (1-3-5-1. Effects on system vendors) First, the creation support system 100 allows the system vendor to easily create a narrative, thereby reducing the number of man-hours required by the system vendor. In other words, once the narrative is complete, the system vendor can semi-automatically create the DCS application and SOP, making it easy to create documents. Second, the creation support system 100 ensures that the narrative, DCS application, and SOP are completely consistent, thereby reducing rework due to misunderstandings in specifications. Third, the creation support system 100 allows the system vendor to reduce the number of required resources. In other words, the system vendor no longer needs to secure a lead-class engineer E who is required to check the consistency of the documents.
[0035] (1-3-5-2. Effects on EPC contractors or plant managers) First, the creation support system 100 can reduce the effort required for EPC contractors to create narratives. Second, the creation support system 100 can reduce document inconsistencies, thereby reducing the risk of accidents during trial operation due to missed checks at FAT (Factory Acceptance Test). Third, the creation support system 100 provides high-quality documents to plant managers, thereby reducing the time the plant managers spend checking consistency when making future modifications or expansions.
[0036] 2. Configuration and Processing of the Engineer Terminal 10 of the Creation Support System 100 The configuration and processing of the engineer terminal 10 included in the creation support system 100 shown in Fig. 1 will be described with reference to Fig. 2. Fig. 2 is a block diagram showing a configuration example of the engineer terminal 10 of the creation support system 100 according to the embodiment. Below, a detailed description will be given of a configuration example and processing example of the engineer terminal 10 according to the embodiment, and a specific example of processing of the creation support system 100.
[0037] (2-1. Configuration and Processing Examples of Engineer Terminal 10) An example of the configuration and processing of the engineer terminal 10 will be described with reference to Fig. 2. The engineer terminal 10 includes an input unit 11, a display unit 12, a communication unit 13, a storage unit 14, and a control unit 15.
[0038] (2-1-1. Input section 11) The input unit 11 controls input of various information to the engineer terminal 10. For example, the input unit 11 is realized by a mouse, a keyboard, etc., and accepts input of various information to the engineer terminal 10.
[0039] (2-1-2.Display section 12) The display unit 12 is responsible for displaying various types of information from the engineer terminal 10. For example, the display unit 12 is realized by a display or the like, and displays various types of information stored in the engineer terminal 10.
[0040] (2-1-3. Communications Department 13) The communication unit 13 manages data communication with other devices. For example, the communication unit 13 performs data communication with each communication device via a router, etc. The communication unit 13 can also perform data communication with an operator's terminal (not shown).
[0041] (2-1-4. Storage section 14) The storage unit 14 stores various information referenced when the control unit 15 operates and various information acquired when the control unit 15 operates. The storage unit 14 has a library information storage unit 14a and an output result storage unit 14b. Here, the storage unit 14 can be realized by, for example, a semiconductor memory element such as a random access memory (RAM) or a flash memory, or a storage device such as a hard disk or an optical disk. In the example of FIG. 2, the storage unit 14 is installed inside the engineer terminal 10, but it may be installed outside the engineer terminal 10, or multiple storage units may be installed.
[0042] The storage unit 14 stores a template of each module indicating a functional unit of the system components and a template of a document that defines a description of the function of each module or a procedure related to the operation control of each module in association with each other. For example, the storage unit 14 stores a template of each module and a template of a narrative that is a specification that defines a description of the function of each module in association with each other. The storage unit 14 also stores a template of each module and a template of an SOP that is a procedure that defines a procedure related to the operation control of each module in association with each other. Furthermore, the storage unit 14 stores a template of each module and a template of a narrative that is a specification that defines a description of the function of each module in association with each other.
[0043] (2-1-4-1. Library information storage unit 14a) The library information storage unit 14a stores library information. For example, the library information storage unit 14a stores library information acquired by an acquisition unit 15a of the control unit 15 described later. Here, an example of data stored in the library information storage unit 14a will be described with reference to FIG. 3. FIG. 3 is a diagram showing an example of the library information storage unit 14a of the engineer terminal 10 according to the embodiment. In the example of FIG. 3, the library information storage unit 14a has items such as "control system," "control typical," "narrative template," and "SOP template."
[0044] "Control system" refers to identification information for identifying a plant control system that controls a plant, such as an identification number or an identification symbol of the plant control system. "Control typical" refers to a template of a control loop that indicates the functional unit of a process device that is a component of a plant, such as a template of a control loop for proportional-integral-differential (PID) control, pump on-off control, etc. "Narrative template" refers to a template of a control specification that defines an explanation of the function of a control loop, such as a template of image data, text data, etc. that explains the function of a control loop for PID control, pump on-off control, etc. "SOP template" refers to a template of a standard operating procedure that defines the procedure for the operation control of a control loop, such as a template of image data, text data, etc. that shows the procedure for the operation control of a control loop for PID control, pump on-off control, etc.
[0045] That is, Figure 3 shows an example in which the following data is stored in the library information storage unit 14a for a plant control system identified by "Control System CS001", including {Control typical: "Typical001", Narrative template: "Narrative001", SOP template: "SOP001"}, {Control typical: "Typical002", Narrative template: "Narrative002", SOP template: "SOP002"}, {Control typical: "Typical003", Narrative template: "Narrative003", SOP template: "SOP003"}, etc.
[0046] (2-1-4-2. Output result storage unit 14b) The output result storage unit 14b stores the output result. For example, the output result storage unit 14b stores a control typical, a concretization list, a narrative, and an SOP, which are output results generated by the output unit 15c of the control unit 15 described later. Here, an example of data stored in the output result storage unit 14b will be described with reference to FIG. 4. FIG. 4 is a diagram showing an example of the output result storage unit 14b of the engineer terminal 10 according to the embodiment. In the example of FIG. 4, the output result storage unit 14b has items such as "output result", "control typical", "concretization list", "narrative", and "SOP".
[0047] The "output result" indicates identification information for identifying the output result, such as an identification number or an identification symbol of the output result. The "control typical" indicates output data of a template of a specified control loop, such as image data showing a drawing of a template of a control loop such as PID control, on-off control of a pump, etc. The "embodiment list" indicates output data regarding plant equipment included in a specified control loop, such as text data showing a list of the names of the plant equipment and identification information of the control typical. The "narrative" indicates output data of a control specification that defines a description of the function of a specified control loop, such as image data, text data, etc. explaining the function of a control loop such as PID control, on-off control of a pump, etc. The "SOP" indicates output data of a standard operating procedure that defines a procedure for the operation control of a control loop, such as image data, text data, an application, etc. showing a procedure for the operation control of a control loop such as PID control, on-off control of a pump, etc.
[0048] That is, in Figure 4, {Output result: "Output result #1", Control typical: "Typical001.modx", Instantiation list: "List001.xlsx", Narrative: "Narrative001.xml", SOP: "SOP001.xml"}, {Output result: "Output result #2", Control typical: "Typical002.modx", Instantiation list: "List002.xlsx", Narrative: "Narrative002.xml", SOP: "SOP001.xml"} 13 shows an example in which the following data is stored in the output result memory unit 14b: {Output result: "Output result #3", Control typical: "Typical003.modx", Instantiation list: "List003.xlsx", Narrative: "Narrative003.xml", SOP: "SOP003.xml"}, ...
[0049] (2-1-5. Control unit 15) The control unit 15 is responsible for controlling the entire engineer terminal 10. The control unit 15 has an acquisition unit 15a, a reception unit 15b, and an output unit 15c. Here, the control unit 15 can be realized by, for example, an electronic circuit such as a CPU (Central Processing Unit) or an MPU (Micro Processing Unit), or an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array).
[0050] (2-1-5-1. Acquisition part 15a) The acquiring unit 15a acquires various kinds of information. The acquiring unit 15a may store the acquired various kinds of information in the storage unit 14. For example, the acquiring unit 15a acquires library information input by an engineer E and stores it in the library information storage unit 14a. The acquiring unit 15a also acquires setting information set for components included in a selected predetermined module from a configuration diagram showing the system configuration.
[0051] To explain a specific example of library information, the acquisition unit 15a acquires library information created and input by engineer E from past plant operation data, such as {Plant control system: "Control system CS001", control typical: "Typical001", narrative template: "Narrative001", SOP template: "SOP001"}, {Plant control system: "Control system CS001", control typical: "Typical002", narrative template: "Narrative002", SOP template: "SOP002"}, {Plant control system: "Control system CS001", control typical: "Typical003", narrative template: "Narrative003", SOP template: "SOP003"}, and stores it in the library information storage unit 14a.
[0052] To explain a specific example of the setting information, for a control loop "control loop PL001" specified by engineer E on the digital P&ID, the acquisition unit 15a acquires tag information "Tag001" related to the plant equipment such as equipment name, equipment function, and alarm threshold value, unit information "Unit001" related to the connection relationship of the plant equipment included in the control loop, and P&ID information "P&ID001" related to the drawing of the specified control loop, and outputs them to the output unit 15c. At this time, the acquisition unit 15a may store the setting information acquired from the digital P&ID in the storage unit 14.
[0053] (2-1-5-2. Reception section 15b) The reception unit 15b receives various information. The reception unit 15b may store the received various information in the storage unit 14. For example, the reception unit 15b receives a selection of a predetermined module included in a configuration diagram showing the configuration of a system. At this time, the reception unit 15b receives a selection of a predetermined module specified by a user and a template applicable to the predetermined module in the configuration diagram displayed on a terminal used by the user.
[0054] That is, the reception unit 15b receives the selection of a control loop specified by engineer E on the digital P&ID displayed on the display unit 12 of the engineer terminal 10 used by engineer E, and also receives the selection of a control typical applicable to the control loop specified by engineer E on the control typical list, which is a list of control loop templates displayed on the display unit 12.
[0055] To explain a specific example, the reception unit 15b receives the selection of a control loop "Control Loop PL001" specified by engineer E on the digital P&ID, identifies the control function of "Control Loop PL001" as "Control System CS001", outputs a control typical list {Control Typical: "Typical001", Control Typical: "Typical002", Control Typical: "Typical003", ...} which is a list of control typicals applicable to "Control System CS001" to the display unit 12, and receives the selection of the control typical "Typical001" specified by engineer E on the control typical list.
[0056] (2-1-5-3. Output section 15c) The output unit 15c outputs various information. The output unit 15c acquires various information stored in the storage unit 14. The output unit 15c also acquires various information acquired by the acquisition unit 15a. The output unit 15c also acquires various information accepted by the acceptance unit 15b. The output result generation process and the output result reflection process will be described below.
[0057] (Output result generation process) The output unit 15c outputs the document of the selected predetermined module based on the setting information set for the components included in the selected predetermined module and the template of the document associated with the template of the selected predetermined module. For example, the output unit 15c outputs the specification of the selected predetermined module based on the setting information and the template of the specification stored in the storage unit 14. The output unit 15c also outputs the procedure manual of the selected predetermined module based on the setting information and the template of the procedure manual stored in the storage unit 14. At this time, the output unit 15c acquires the setting information set for each component included in the configuration diagram, and outputs the specification of the selected predetermined module by replacing the setting items of the template of the specification associated with the template applicable to the selected predetermined module using the acquired setting information, and outputs the procedure manual of the selected predetermined module by replacing the setting items of the template of the procedure manual associated with the template applicable to the selected predetermined module using the acquired setting information. The output unit 15c also outputs a drawing showing the selected predetermined module. Furthermore, the output unit 15c outputs a list of the components included in the selected predetermined module.
[0058] That is, the output unit 15c acquires the setting information of the plant equipment included in the control loop designated by the engineer E on the digital P&ID and selected by the reception unit 15b, and outputs the narrative and the SOP by replacing the setting items of the narrative template associated with the control typical selected by the reception unit 15b and the SOP template associated with the control typical with the setting information. At this time, the output unit 15c may output a drawing of the control typical, a concrete example list showing the relationship between the names of the plant equipment included in the control loop and the control typical, and the like.
[0059] To explain a specific example, the output unit 15c acquires the equipment name "FC7100" as the setting information of the plant equipment included in the control loop selected by the reception unit 15b, and replaces the generic name "xxx" of the narrative template associated with the control typical selected by the reception unit 15b and the generic name "xxx" of the SOP template associated with the control typical with the equipment name "FC7100", thereby generating a narrative "Narrative001.xml" and an SOP "SOP001.xml" as output results, and stores them in the output result storage unit 14b of the storage unit 14. The output unit 15c also causes the display unit 12 to display the drawing of the control typical, the instantiation list, the narrative, and the SOP as output results.
[0060] (Output result reflection process) When the output specification is changed, the output unit 15c reflects the change in the template of the specification stored in the storage unit 14, and also reflects the change in the template of each module and the template of the procedure manual. When the output procedure manual is changed, the output unit 15c reflects the change in the template of the procedure manual stored in the storage unit 14, and also reflects the change in the template of each module and the template of the specification. When the drawing showing the outputted specific module is changed, the output unit 15c reflects the change in the template of each module stored in the storage unit 14, and also reflects the change in the template of the specification and the template of the procedure manual.
[0061] That is, when any one of the drawings, narrative, and SOP of the outputted control typical is changed, the output unit 15c reflects the change contents in all of the control typical, narrative template, and SOP template, which are the library information stored in the library information storage unit 14a of the storage unit 14. At this time, when any one of the drawings, narrative, and SOP of the outputted control typical is changed, the output unit 15c may output the drawings, narrative, and SOP of the control typical again using the library information reflecting the change contents.
[0062] To explain a specific example, when alarm information is added by engineer E to the output narrative "Narrative.xml", the output unit 15c adds the alarm information to "Narrative001" to update the narrative template, adds the alarm information to "Typical001" to update the control typical, and adds the alarm information to "SOP001" to update the SOP template. At this time, the output unit 15c may update the drawing of the control typical "Typical001.modx", the narrative "Narrative001.xml", and the SOP "SOP001.xml" as the output result stored in the output result storage unit 14b of the storage unit 14 using the library information to which the alarm information has been added, and may also cause the drawing, narrative, and SOP of the control typical to which the alarm information has been added to be displayed on the display unit 12.
[0063] (2-2. Specific Example of Processing by Creation Support System 100) Specific examples of the processing of the creation support system 100 will be described with reference to Fig. 5 to Fig. 17. Fig. 5 to Fig. 17 are diagrams showing Specific Example 1 to Specific Example 13 of the processing of the creation support system 100 according to the embodiment.
[0064] (2-2-1. Specific Example 1) An example of library information related to PID control stored in the engineer terminal 10 will be described as a first specific example of the processing of the creation support system 100 with reference to FIG.
[0065] As shown in the example of Figure 5, the engineer terminal 10 stores, as library information regarding the control loop of PID control, image data of a drawing of a "Control Typical", which is a template for a control loop including a generic name "xxx" (see Figure 5(1)), image data and text data of a "Narrative Template", which is a template for a narrative including a generic name "xxx" (see Figure 5(2)), and text data of a "SOP Template", which is a template for an SOP including a generic name "xxx" (see Figure 5(3)), in association with each other.
[0066] (2-2-2. Specific Example 2) An example of library information related to on / off control of a pump stored in the engineer terminal 10 will be described as a second specific example of the processing of the creation support system 100 with reference to FIG.
[0067] As shown in the example of Figure 6, the engineer terminal 10 stores, as library information regarding a control loop for pump on / off control, image data of a drawing of a "Control Typical", which is a template for a control loop including a generic name "xxx" (see Figure 6(1)), image data and text data of a "Narrative Template", which is a template for a narrative including a generic name "xxx" (see Figure 6(2)), and text data of an "SOP Template", which is a template for an SOP including a generic name "xxx" (see Figure 6(3)), in association with each other.
[0068] (2-2-3. Specific Example 3) 7, an example of a display screen displayed by the engineer terminal 10 will be described as a third specific example of the process of the creation support system 100. In the following, an example of displaying a digital P&ID will be described as the display screen.
[0069] As shown in the example of Fig. 7, the engineer terminal 10 displays on the monitor screen a digital P&ID showing the configuration of the plant control system for a plant identified by "Plant PS001" using symbols showing the equipment functions of the plant equipment and lines showing the connection relationships of piping, etc. The digital P&ID is not only a visible drawing, but also includes setting information such as tag information.
[0070] (2-2-4. Specific Example 4) 8, an example of a display screen displayed by the engineer terminal 10 will be described as a fourth specific example of the process of the creation support system 100. In the following, an example of displaying a tag list on a digital P&ID will be described as the display screen.
[0071] As shown in the example of Fig. 8, the engineer terminal 10 can display setting information based on an operation on the monitor screen by engineer E. In the example of Fig. 8, when engineer E clicks on the symbol of the plant equipment "FC7100" on the monitor screen (see Fig. 8(1)), the engineer terminal 10 displays a tag list that is a list of tag information including the equipment name of the plant equipment "FC7100" and the like (see Fig. 8(2)).
[0072] (2-2-5. Specific Example 5) 9, an example of a display screen displayed by the engineer terminal 10 will be described as a specific example 5 of the process of the creation support system 100. In the following, an example of a display screen in which a control loop is specified on a digital P&ID will be described.
[0073] As shown in the example of Fig. 9, Engineer E can specify a control loop for which a narrative or SOP is to be created based on an operation on the monitor screen. In the example of Fig. 9, Engineer E performs a drag operation on the digital P&ID and specifies an arbitrary control loop by filling in a circular area (see the shaded area in Fig. 9). At this time, the engineer terminal 10 displays a colored control loop (see the thick line in Fig. 9) corresponding to a functional unit including the plant equipment "FC7100" and the like. The engineer terminal 10 also acquires setting information such as the equipment name "FC7100" of the plant equipment assigned to the digital P&ID.
[0074] (2-2-6. Specific Example 6) 10, an example of a display screen displayed by the engineer terminal 10 will be described as a specific example 6 of the process of the creation support system 100. In the following, an example of a "control typical setting screen" for specifying a control typical for a control loop will be described as the display screen.
[0075] As shown in the example of FIG. 10, Engineer E can specify a control typical for a control loop for which a narrative or SOP is to be created based on an operation on a monitor screen. In the example of FIG. 10, the engineer terminal 10 displays a control typical list (see FIG. 10(2)) showing a list of control typicals applicable to a control loop (see FIG. 10(1)) specified by Engineer E on a digital P&ID. Engineer E selects a control typical "Typical001" to be applied to the specified control loop from the control typical list. The engineer terminal 10 can also display a drawing of the control typical selected by Engineer E (see FIG. 10(3)). Then, Engineer E clicks the "OK" button (see FIG. 10(4)) to confirm the control typical selected from the control typical list, and clicks the "Cancel" button (see FIG. 10(5)) to select again.
[0076] (2-2-7. Specific Example 7) 11, an example of an output result generated by the engineer terminal 10 will be described as a specific example 7 of the process of the creation support system 100. In the following, an example of generating a narrative and an SOP as the output result will be described.
[0077] As shown in the example of Fig. 11, for a control loop (see Fig. 11(1)) including plant equipment "FC7100", the engineer terminal 10 generates a narrative (see Fig. 11(2)) in which the generic name "xxx" of the narrative template is replaced with the equipment name "FC7100", and generates an SOP (see Fig. 11(3)) in which the generic name "xxx" of the SOP template is replaced with the equipment name "FC7100". At this time, the engineer terminal 10 generates the narrative and SOP based on setting information including tag information, unit information, P&ID information, etc. acquired from the digital P&ID.
[0078] (2-2-8. Specific Example 8) 12, an example of a display screen displayed by the engineer terminal 10 will be described as a specific example 8 of the process of the creation support system 100. In the following, an example of a "narrative correction screen" for correcting a narrative will be described as the display screen.
[0079] As shown in the example of FIG. 12, the engineer E can modify the displayed narrative based on the operation on the monitor screen. In the example of FIG. 12, the engineer terminal 10 displays a narrative (see FIG. 12(1)) generated for a control loop specified by the engineer E, as well as a list (see FIG. 12(2)) showing a list of alarm logics that can be added to the narrative. The engineer E selects alarm information "Alarm" and "High" related to the upper threshold of the alarm to be added to the displayed narrative from the list. The engineer terminal 10 can also display a narrative template (see FIG. 12(3)) corresponding to the alarm information selected by the engineer E. Then, the engineer E checks the modified narrative (see FIG. 12(4)) that reflects the addition of the alarm information, and clicks the "Add" button (see FIG. 12(5)) if he / she wants to confirm the modification of the narrative, or clicks the "Cancel" button (see FIG. 12(6)) if he / she wants to modify it again.
[0080] (2-2-9. Specific Example 9) An example of library information in which the engineer terminal 10 reflects the correction contents will be described as a ninth specific example of the processing of the creation support system 100 with reference to FIG.
[0081] As shown in the example of FIG. 13, when a narrative is modified by an operation of an engineer E, the engineer terminal 10 can reflect the modification content in the stored library information based on the modified narrative reflecting the modification content. In the example of FIG. 13, the engineer terminal 10 adds alarm information to the stored library information based on the modified narrative reflecting the addition of alarm information (see FIG. 13(1)). At this time, the engineer terminal 10 adds alarm information related to the upper limit threshold to the control typical associated with the narrative template of the modified narrative (see FIG. 13(2)), and adds alarm information related to the upper limit threshold to the SOP template associated with the narrative template of the modified narrative (see FIG. 13(3)). In addition, the engineer terminal 10 adds alarm information related to the upper limit threshold to the narrative template of the modified narrative to ensure the consistency of the library information.
[0082] In the example of FIG. 13, the process of reflecting the modification content of the narrative has been described, but the engineer terminal 10 can also reflect the modification content of the drawing of the control typical and the SOP displayed on the monitor screen. At this time, when alarm information is added to the SOP, the engineer terminal 10 modifies the corresponding SOP template in the library information, and modifies the control typical and the narrative template linked to the SOP template. Also, when alarm information is added to the image data of the drawing of the control typical, the engineer terminal 10 modifies the corresponding control typical in the library information, and modifies the narrative template and the SOP template linked to the control typical. That is, in the creation support system 100, the control typical, the narrative template, and the SOP template are always synchronized, and when any one is changed, the other two are automatically updated.
[0083] (2-2-10. Specific Example 10) 14, an example of an output result generated by the engineer terminal 10 will be described as a specific example 10 of the process of the creation support system 100. In the following, an example of generating a modified control typical drawing as the output result will be described.
[0084] 14, the engineer terminal 10 generates image data "Typical001.modx" of a modified control typical drawing, which is a control loop template including the generic name "xxx" of the plant equipment and to which alarm information "High" related to the upper limit threshold has been added. The engineer terminal 10 may display the modified control typical drawing on a monitor screen, or may collectively generate control loops included in the plant using the image data of the modified control typical drawing.
[0085] (2-2-11. Specific Example 11) 15, an example of an output result generated by the engineer terminal 10 will be described as a specific example 11 of the process of the creation support system 100. In the following, an example of generating a concretization list as the output result will be described.
[0086] 15, the engineer terminal 10 generates text data "List001.xlsx" of an instantiation list related to the plant equipment included in the control loop. The engineer terminal 10 may also display the instantiation list on a monitor screen.
[0087] (2-2-12. Specific Example 12) 16, an example of an output result generated by the engineer terminal 10 will be described as a specific example 12 of the process of the creation support system 100. In the following, an example of generating a modified SOP as the output result will be described.
[0088] 16, the engineer terminal 10 generates text data "SOP001.xml" of the modified SOP in which the plant equipment name "FC7100" has been replaced and alarm information "3. Alarm Management" relating to the upper limit threshold has been added. Furthermore, the engineer terminal 10 may display the modified SOP on a monitor screen, or may output the modified SOP to an interface that assists in the creation of advanced SOPs.
[0089] (2-2-13. Example 13) 17, an example of an output result generated by the engineer terminal 10 will be described as a specific example 13 of the process of the creation support system 100. In the following, an example of generating a corrected narrative as the output result will be described.
[0090] 17, the engineer terminal 10 generates image data and text data "Narrative001.xml" of the corrected narrative in which the device name "FC7100" of the plant device has been replaced and alarm information related to the upper limit threshold has been added. The engineer terminal 10 may display the corrected narrative on a monitor screen, or may issue the corrected narrative as a completed document.
[0091] 3. Processing flow of the creation support system 100 A process flow of the creation support system 100 according to the embodiment will be described with reference to Fig. 18. Fig. 18 is a flowchart showing an example of a process flow of the creation support system 100 according to the embodiment. Note that the processes of steps S101 to S119 below may be executed in a different order. Also, some of the processes of steps S101 to S119 below may be omitted.
[0092] (3-1. Library information acquisition process) The engineer terminal 10 executes a library information acquisition process (step S101). For example, the engineer terminal 10 acquires and stores library information that associates control typicals, narrative templates, and SOP templates.
[0093] (3-2. P&ID Acquisition Processing) The engineer terminal 10 executes a P&ID acquisition process (step S102). For example, the engineer terminal 10 acquires a digital P&ID indicating the configuration of a plant designated by the engineer E, and displays it on a monitor screen.
[0094] (3-3. Setting information acquisition process) The engineer terminal 10 executes a setting information acquisition process (step S103). For example, the engineer terminal 10 acquires setting information including tag information, unit information, P&ID information, etc., assigned to the digital P&ID displayed on the monitor screen.
[0095] (3-4. Control Loop Reception Processing) The engineer terminal 10 executes a control loop reception process (step S104). For example, the engineer terminal 10 receives a control loop designated by the engineer E on the digital P&ID.
[0096] (3-5. Control typical reception process) The engineer terminal 10 executes a control typical receiving process (step S105). For example, the engineer terminal 10 receives the control typical selected by the engineer E from the control typical list.
[0097] (3-6. Narrative output processing) The engineer terminal 10 executes a narrative output process (step S106). For example, the engineer terminal 10 obtains a narrative template associated with the selected control typical, replaces setting items such as equipment names of the narrative template with setting information obtained from the digital P&ID, and generates a draft version of the narrative and displays it on the monitor screen.
[0098] (3-7. Narrative Modification Processing) Engineer E executes a narrative correction process (step S107). For example, Engineer E corrects the narrative by inputting missing information or data that needs to be adjusted in the narrative displayed on the monitor screen.
[0099] (3-8. Processing to reflect corrections) The engineer terminal 10 executes a process of reflecting the correction contents (step S108). For example, the engineer terminal 10 corrects the control typical, narrative template, and SOP template, which are library information, based on the difference between the narrative before and after the correction. After that, the engineer terminal 10 proceeds to the process of steps S109, S113, and S117.
[0100] (3-9. Control typical / embodiment list output processing) The engineer terminal 10 executes a control typical / concretization list output process (step S109). For example, the engineer terminal 10 displays on a monitor screen a concrete example list showing a list of plant equipment and the like included in the control loop together with a drawing of the control typical reflecting the contents of the narrative correction.
[0101] (3-10. Control loop generation process) The engineer terminal 10 executes a control loop generation process (step S110). For example, the engineer terminal 10 collectively generates control loops that configure a plant in an engineering environment using a plurality of control typicals and tag lists. If the engineer E modifies the control typical (step S111: Yes), the engineer terminal 10 proceeds to the process of step S112. On the other hand, if the engineer E does not modify the control typical (step S111: No), the engineer terminal 10 ends the process.
[0102] (3-11. Modified control typical output processing) The engineer terminal 10 executes the corrected control typical output process (step S112). For example, the engineer terminal 10 displays the corrected control typical drawing on the monitor screen, and proceeds to the process of step S108.
[0103] (3-12.SOP output processing) The engineer terminal 10 executes an SOP output process (step S113). For example, the engineer terminal 10 displays the SOP in which the correction content of the narrative is reflected on a monitor screen.
[0104] (3-13. Interface input processing) The engineer terminal 10 executes an interface input process (step S114). For example, the engineer terminal 10 inputs the SOP reflecting the narrative modification content to an interface that assists in creating an advanced SOP. If the engineer E modifies the SOP (step S115: Yes), the engineer terminal 10 proceeds to the process of step S116. On the other hand, if the engineer E does not modify the SOP (step S115: No), the engineer terminal 10 ends the process.
[0105] (3-14. Corrected SOP output processing) The engineer terminal 10 executes the modified SOP output process (step S116). For example, the engineer terminal 10 displays the modified SOP on the monitor screen using the above interface, and proceeds to the process of step S108.
[0106] (3-15. Corrected narrative output processing) The engineer terminal 10 executes a post-correction narrative output process (step S117). For example, the engineer terminal 10 displays the narrative reflecting the correction content on a monitor screen.
[0107] (3-16. Completed document issuance process) The engineer terminal 10 executes a completed document issuing process (step S118). For example, the engineer terminal 10 prints the narrative reflecting the correction content as a completed document. If the engineer E corrects the completed document (step S119: Yes), the engineer terminal 10 proceeds to the process of step S107. On the other hand, if the engineer E does not correct the completed document (step S119: No), the engineer terminal 10 ends the process.
[0108] 4. Effects of the embodiment Finally, effects of the embodiment will be described below: Effects 1 to 8 corresponding to the processing according to the embodiment will be described below.
[0109] (4-1. Effect 1) First, in the process according to the embodiment described above, the engineer terminal 10 stores a control typical, which is a template of a control loop showing the functional units of the components of the system, in association with a document template that describes the function of the control loop or defines a procedure for controlling the operation of the control loop, accepts the selection of a specific control loop included in a configuration diagram showing the configuration of the system, and outputs a document of the selected specific control loop based on the setting information set for the components included in the selected specific control loop and the document template associated with the control typical of the selected specific control loop. Therefore, in this process, highly specialized documents can be easily created.
[0110] (4-2. Effect 2) Secondly, in the process according to the embodiment described above, the engineer terminal 10 stores the control typical and a narrative template, which is a specification that defines the description of the function of the control loop, in association with each other, and outputs the narrative of a selected predetermined control loop based on the setting information and the stored narrative template. Therefore, in this process, the narrative can be easily created as a highly specialized document.
[0111] (4-3. Effect 3) Thirdly, in the process according to the embodiment described above, the engineer terminal 10 stores the control typical and the template of the SOP, which is a procedure manual that defines the procedure for the operation control of the control loop, in association with each other, and outputs the SOP of the selected predetermined control loop based on the setting information and the stored SOP template. Therefore, in this process, the SOP can be easily created as a highly specialized document.
[0112] (4-4. Effect 4) Fourthly, in the process according to the embodiment described above, the engineer terminal 10 stores the control typical, a narrative template which is a specification defining the description of the function of the control loop, and an SOP template which is a procedure defining the procedure for the operation control of the control loop in association with each other, and accepts the selection of a specific control loop designated by the engineer E and a control typical applicable to the specific control loop in the configuration diagram displayed by the engineer terminal 10 used by the engineer E, acquires setting information set for each component included in the configuration diagram, and outputs the narrative of the selected specific control loop by replacing the setting items of the narrative template associated with the control typical applicable to the selected specific control loop using the acquired setting information, and outputs the SOP of the selected specific control loop by replacing the setting items of the SOP template associated with the template applicable to the selected specific control loop using the acquired setting information. Therefore, in this process, the setting items of the document are automatically replaced, and the engineer E does not have to take the trouble of manually replacing the setting items, so that the narrative and SOP can be easily created as highly specialized documents.
[0113] (4-5. Effect 5) Fifth, in the process according to the embodiment described above, when the output narrative is changed, the engineer terminal 10 reflects the change in the narrative template stored therein, and also reflects the change in the control typical and SOP templates. Therefore, in this process, even if an addition or modification is made to the narrative, consistency is ensured, and the narrative and SOP can be easily created as highly specialized documents.
[0114] (4-6. Effect 6) Sixth, in the process according to the embodiment described above, when the output SOP is changed, the engineer terminal 10 reflects the change in the template of the SOP stored therein, and also reflects the change in the control typical and narrative templates. Therefore, in this process, even if the SOP is added or modified, consistency is ensured, and the narrative and SOP can be easily created as highly specialized documents.
[0115] (4-7. Effect 7) Seventh, in the process according to the embodiment described above, the engineer terminal 10 outputs a drawing showing a control typical of a selected predetermined control loop, and when the output drawing is changed, the change is reflected in the stored control typical, and the change is also reflected in the narrative template and the SOP template. Therefore, in this process, even if the control typical drawing is added or modified, consistency is ensured, and the narrative and SOP can be easily created as highly specialized documents.
[0116] (4-8. Effect 8) Eighth, in the process according to the embodiment described above, the engineer terminal 10 outputs a list of components included in the selected control loop. Therefore, in this process, a narrative and an SOP can be easily created as highly specialized documents, and the engineer E can refer to the list to check detailed information about the control loop, improving the convenience of the engineer E who creates the document.
[0117] 〔system〕 The information including the processing procedures, control procedures, specific names, various data and parameters shown in the above documents and drawings can be changed arbitrarily unless otherwise specified.
[0118] In addition, each component of each device shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure. In other words, the specific form of distribution and integration of each device is not limited to that shown in the figure. In other words, all or part of them can be functionally or physically distributed and integrated in any unit according to various loads, usage conditions, etc.
[0119] Furthermore, each processing function performed by each device may be realized, in whole or in part, by a CPU and a program analyzed and executed by the CPU, or may be realized as hardware using wired logic.
[0120] [Hardware] Next, a hardware configuration example of the engineer terminal 10, which is a creation support device, will be described. Note that other devices can also have a similar hardware configuration. FIG. 19 is a diagram showing a hardware configuration example according to an embodiment. As shown in FIG. 19, the engineer terminal 10 has a communication device 10a, a HDD (Hard Disk Drive) 10b, a memory 10c, and a processor 10d. In addition, each unit shown in FIG. 19 is connected to each other by a bus or the like.
[0121] The communication device 10a is a network interface card or the like, and communicates with other servers. The HDD 10b stores programs and databases that operate the functions shown in FIG.
[0122] The processor 10d reads out a program that executes the same processes as the respective processing units shown in FIG. 2 from the HDD 10b, etc., and loads it in the memory 10c, thereby operating a process that executes each function described in FIG. 2, etc. For example, this process executes a function similar to that of each processing unit possessed by the engineer terminal 10. Specifically, the processor 10d reads out a program having functions similar to those of the acquisition unit 15a, the reception unit 15b, the output unit 15c, etc., from the HDD 10b, etc. Then, the processor 10d executes a process that executes the same processes as those of the acquisition unit 15a, the reception unit 15b, the output unit 15c, etc.
[0123] In this way, the engineer terminal 10 operates as a device that executes various processing methods by reading and executing the programs. The engineer terminal 10 can also realize the same functions as the above-mentioned embodiment by reading the above-mentioned programs from a recording medium using a media reading device and executing the read-out programs. Note that the programs in these other embodiments are not limited to being executed by the engineer terminal 10. For example, the present invention can be similarly applied to cases where other computers or servers execute the programs, or where these execute the programs in cooperation with each other.
[0124] This program can be distributed via a network such as the Internet. This program can also be recorded on a computer-readable recording medium such as a hard disk, a flexible disk (FD), a CD-ROM, a magneto-optical disk (MO), or a digital versatile disk (DVD), and can be executed by being read out from the recording medium by a computer.
[0125] 〔others〕 Some examples of combinations of the disclosed technical features are set out below.
[0126] (1) A creation support device comprising: a memory unit that stores templates of each module indicating functional units of components of a system in association with a document template that describes the function of each module or defines procedures for operational control of each module; a reception unit that receives a selection of a specific module included in a configuration diagram showing the configuration of the system; and an output unit that outputs a document of the selected specific module based on setting information set for the components included in the selected specific module and the document template associated with the template of the selected specific module.
[0127] (2) The memory unit stores a template for each module in association with a specification template that defines a description of the function of each module, and the output unit outputs a specification for the selected specified module based on the setting information and the specification template stored in the memory unit.
[0128] (3) The memory unit stores a template for each of the modules in correspondence with a template of a procedure manual that defines procedures for operational control of each of the modules, and the output unit outputs a procedure manual for the selected specified module based on the setting information and the template of the procedure manual stored in the memory unit.
[0129] (4) The memory unit stores a template for each of the modules, a specification template that defines a description of the functions of each of the modules, and a procedure manual template that defines a procedure for operational control of each of the modules in association with each other, the reception unit receives a selection of the specific module specified by the user in the configuration diagram displayed on a terminal used by the user, and a template applicable to the specific module, the output unit obtains the setting information set for each of the components included in the configuration diagram, and uses the setting information to replace setting items in the specification template that corresponds to the template applicable to the selected specific module, thereby outputting the specification of the selected specific module, and uses the setting information to replace setting items in the procedure manual template that corresponds to the template applicable to the selected specific module, thereby outputting the procedure manual of the selected specific module.
[0130] (5) The creation support device described in (4), wherein when the output specification is changed, the output unit reflects the changes in the template of the specification stored in the memory unit, and also reflects the changes in the templates of each module and the template of the procedure manual.
[0131] (6) A creation support device as described in (4) or (5), wherein when the outputted procedure manual is changed, the output unit reflects the changes in the template of the procedure manual stored in the memory unit, and also reflects the changes in the templates of each module and the template of the specification manual.
[0132] (7) The creation support device described in any one of (4) to (6), wherein the output unit outputs a drawing showing a template of the selected specific module, and when the output drawing is changed, reflects the changes in the templates of the respective modules stored in the memory unit, and also reflects the changes in the template of the specification and the template of the procedure manual.
[0133] (8) The creation support device according to any one of (1) to (7), wherein the output unit outputs a list of the components included in the selected predetermined module.
[0134] (9) A creation support method in which a computer stores, in association with each other, a template of each module indicating a functional unit of a system's components and a document template that explains the function of each module or defines procedures for controlling the operation of each module, accepts selection of a specific module included in a configuration diagram showing the configuration of the system, and outputs a document of the selected specific module based on setting information set for the components included in the selected specific module and the document template associated with the template of the selected specific module.
[0135] (10) A creation support program that causes a computer to execute a process of storing templates of each module indicating functional units of the components of a system in association with document templates that explain the functions of each module or define procedures for controlling the operation of each module, accepting selection of a specific module included in a configuration diagram showing the configuration of the system, and outputting a document of the selected specific module based on setting information set for the components included in the selected specific module and the document template associated with the template of the selected specific module. [Explanation of symbols]
[0136] 10 Engineer Terminal 11 Input section 12 Display section 13. Communications Department 14 Storage section 14a Library information storage unit 14b Output result storage section 15 Control section 15a Acquisition part 15b Reception 15c Output section 100 Creation Support System
Claims
1. a storage unit that stores a template of each module indicating a functional unit of a component of the system and a template of a document that describes a function of each module or defines a procedure related to operation control of each module in association with each other; a reception unit that receives a selection of a predetermined module included in a configuration diagram showing a configuration of the system; an output unit that outputs a document of the selected predetermined module based on setting information set for the component included in the selected predetermined module and a template of the document associated with a template of the selected predetermined module; A creation support device comprising:
2. The storage unit is storing a template for each of the modules in association with a template for a specification defining a description of the function of each of the modules; The output unit is outputting a specification of the selected predetermined module based on the setting information and a template of the specification stored in the storage unit; The creation support device according to claim 1.
3. The storage unit is storing a template of each of the modules in association with a template of a procedure manual that defines a procedure for controlling the operation of each of the modules; The output unit is outputting a procedure manual for the selected predetermined module based on the setting information and the template of the procedure manual stored in the storage unit; The creation support device according to claim 1.
4. The storage unit is storing a template for each of the modules, a specification template defining a description of the functions of each of the modules, and a procedure template defining a procedure for controlling the operation of each of the modules in association with each other; The reception unit is receiving a selection of the predetermined module and a template applicable to the predetermined module designated by the user in the configuration diagram displayed on a terminal used by the user; The output unit is acquiring the setting information set for each of the components included in the configuration diagram; outputting a specification of the selected predetermined module by replacing a setting item of the template of the specification corresponding to a template applicable to the selected predetermined module using the setting information; outputting a procedure manual for the selected predetermined module by replacing a setting item of the template of the procedure manual associated with a template applicable to the selected predetermined module using the setting information; The creation support device according to claim 1.
5. The output unit is When the outputted specification is changed, the change is reflected in the template of the specification stored in the storage unit, and the change is also reflected in the templates of the modules and the template of the procedure manual. The creation support device according to claim 4.
6. The output unit is When the output procedure manual is changed, the change is reflected in the template of the procedure manual stored in the storage unit, and the change is also reflected in the templates of the modules and the template of the specification. The creation support device according to claim 4.
7. The output unit is outputting a drawing showing a template of the selected predetermined module, and when the output drawing is changed, reflecting the change in the template of each of the modules stored in the storage unit, and reflecting the change in the template of the specification and the template of the procedure manual; The creation support device according to claim 4.
8. The output unit is outputting a list of the components included in the selected predetermined module; The creation support device according to claim 4.
9. The computer retaining a template of each module indicating a functional unit of a component of the system and a template of a document defining a description of the function of each module or a procedure related to the operation control of each module in association with each other; Accepting a selection of a predetermined module included in a configuration diagram showing a configuration of the system; outputting a document of the selected predetermined module based on setting information set for the component included in the selected predetermined module and a template of the document associated with a template of the selected predetermined module; A creation aid that performs a process.
10. On the computer, retaining a template of each module indicating a functional unit of a component of the system and a template of a document defining a description of the function of each module or a procedure related to the operation control of each module in association with each other; Accepting a selection of a predetermined module included in a configuration diagram showing a configuration of the system; outputting a document of the selected predetermined module based on setting information set for the component included in the selected predetermined module and a template of the document associated with a template of the selected predetermined module; A creation support program that executes the process.
Citation Information
Patent Citations
Automatic programming device
JP1997091128A
Operation procedure manual preparation support system
JP2009181170A
Standard work manual generation device, standard work manual generation method, and computer program
JP2013097443A
Document generation device
JP2022057203A