Design document generation device and design document generation method

Abstract

To provide a design data generation device and a design data generation method that can suppress occurrence of data inconsistency when generating a plurality of design data for designing a PLC system.SOLUTION: A design data generation device 40 comprises a storage device 64 and a CPU 61. The storage device 64 stores a common database (DB) 50 in which data for generating a plurality of design data 30 are registered. The CPU 61 executes a plurality of processes (processes for executing respective tools) corresponding respectively to the plurality of design data 30. The CPU 61 updates the DB 50 based on data input by a user in each of the plurality of processes. The CPU 61 generates the plurality of design data 30 based on data read from the DB 50.SELECTED DRAWING: Figure 4

Description

[Technical field]

[0001] The present disclosure relates to a design document generation device and a design document generation method. [Background technology]

[0002] When monitoring and controlling automatic control devices in factories and various equipment installed in buildings from a central monitoring device, a PLC (Programmable Logic Controller) is used to ensure high safety and stability.

[0003] PLC software uses ladder logic, which is a symbolic representation of a relay circuit. For example, Japanese Patent No. 6203321 (Patent Document 1) discloses a device for creating materials for designing a PLC system including PLC software implemented with such ladder logic.

[0004] The device shown in Patent Document 1 creates a management item table that lists each monitoring element and each control element as management items for equipment, etc., and a PLC input / output table relating each terminal of the PLC input / output device and an address in the CPU device, etc., as multiple materials for designing a PLC system that controls all of the multiple PLCs installed in a facility. In this device, multiple processes such as a process for creating the management item table and a process for creating the PLC input / output table are executed, and a common database used for the multiple processes is prepared. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Patent No. 6203321 Summary of the Invention [Problem to be solved by the invention]

[0006] When multiple processes are executed (multiple tools are started) corresponding to each of the multiple design document data in order to generate multiple design document data for designing a PLC system, there is a risk of inconsistency occurring between the data because the same data is managed in duplicate. For example, inconsistency may occur between the data managed by each of the multiple processes (multiple tools) and the data registered in a database that is shared by these processes, depending on the timing of updates to the database.

[0007] The present disclosure has been made to solve the above-mentioned problems, and its purpose is to provide a design document generation device and a design document generation method that can suppress the occurrence of data inconsistencies when generating multiple design document data for designing a PLC system. [Means for solving the problem]

[0008] A design document generation device according to the present disclosure generates multiple pieces of design document data for designing a PLC system that controls all of multiple PLCs installed in a facility. The design document generation device includes a storage unit and a control unit. The storage unit stores a common database in which data for generating the multiple pieces of design document data is registered. The control unit executes multiple processes corresponding to each of the multiple pieces of design document data. In each of the multiple processes, the control unit updates the database based on data input by a user. The control unit generates the multiple pieces of design document data based on data read from the database.

[0009] The design document generation method according to the present disclosure is a method for generating multiple design document data for designing a PLC system that controls all of multiple PLCs installed in a facility. The design document generation method includes a step of registering data for generating the multiple design document data in a common database, and a step of executing multiple processes corresponding to each of the multiple design document data. The step of executing the multiple processes includes a step of updating the database based on data input by a user in each of the multiple processes, and a step of generating the multiple design document data based on data read from the database. Effect of the Invention

[0010] According to the present disclosure, it is possible to prevent data inconsistencies from occurring when generating multiple design document data for designing a PLC system. [Brief description of the drawings]

[0011] [Figure 1] 1 is a diagram showing a configuration of a PLC system in which a design document generating device according to an embodiment of the present invention is used, and a relationship between the system and design documents; [Diagram 2] FIG. 1 is a diagram illustrating a configuration of a design document generating device. [Diagram 3] FIG. 10 is a diagram for explaining a process flow for generating design materials in a conventional example. [Figure 4] FIG. 2 is a diagram for explaining a process flow of generating design materials according to the present embodiment. [Diagram 5] FIG. 13 is a diagram for explaining a launcher screen. [Figure 6] FIG. 13 is a diagram for explaining a management item table screen. [Figure 7] FIG. 13 is a diagram for explaining an input / output table screen. [Figure 8] FIG. 13 is a diagram for explaining a data output menu screen. [Figure 9] 2 is a flowchart of a main process executed by a CPU. [Figure 10]2 is a flowchart of a main process executed by a CPU. [Figure 11] 2 is a flowchart of a main process executed by a CPU. [Figure 12] 2 is a flowchart of a main process executed by a CPU. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, an embodiment will be described with reference to the drawings. In the following description, the same components are denoted by the same reference numerals. Their names and functions are also the same. Therefore, detailed description thereof will not be repeated.

[0013] [PLC System 10] FIG. 1 is a diagram showing the configuration of a PLC system 10 in which a design material generating device 40 according to the present embodiment is used, and a diagram showing the relationship with design materials 30. As shown in FIG.

[0014] The PLC system 10 controls a plurality of PLCs (PLC00 to PLC05 described later) installed in a facility. A design document generating device 40 generates a plurality of design documents (also referred to as “design document data”) 30 for designing the PLC system 10.

[0015] The multiple design documents 30 include a management item table (also referred to as "management item table data") 131, an input / output table (also referred to as "input / output table data") 132, a SW specification (also referred to as "SW specification data") 133, an equipment personnel number table (also referred to as "equipment personnel number table data") 134, a basic SW (also referred to as "basic SW data") 135, and a relative table (also referred to as "relative table data") 136 (see FIG. 4). Each design document 30 will be described later.

[0016] PLC system 10 is a building management system that manages multiple pieces of equipment in building 8 with one master PLC and five PLCs for each floor. Building 8 is an office building with one basement floor and four floors above ground. Building 8 has equipment such as a switchboard and cooling tower on the first basement floor (also referred to as "BF"), office equipment on the first floor (1F) to third floor (3F), and an employee cafeteria with a kitchen on the fourth floor (4F).

[0017] In the PLC system 10, a central monitoring device 12 is placed on the first basement floor, and a master PLC 16 is placed on a master PLC board 14 placed on an intermediate floor of a building 8. The central monitoring device 12 and the master PLC are connected by network wiring. This is called the first system of backbone network 18.

[0018] Furthermore, each floor from the first basement floor to the fourth floor has a respective PLC board 20a-20e, and each floor PLC board 20a-20e houses a respective floor PLC 22a-22e. The master PLC 16 and each floor PLC 22a-22e are connected by a network wiring separate from the first system of backbone network 18. This is called a second system of backbone network 26. The second system of backbone network 26 is a communication network between the master PLC and a different PLC, and is therefore called a CCL.

[0019] The master PLC board 14 and the individual floor PLC boards 20a to 20e are all housings that house PLCs and are RS boards located in remote positions when viewed from the central monitoring device 12, so they are distinguished by the names RS-0 to RS-5. RS is an abbreviation for Remote Station.

[0020] RS-0 is the master PLC board 14, RS-1 is the floor PLC board 20a located on the BF, and RS-2 is the floor PLC board 20b located on the 1st floor. Similarly, RS-3 is the floor PLC board 20c located on the 2nd floor, RS-4 is the floor PLC board 20d located on the 3rd floor, and RS-5 is the floor PLC board 20e located on the 4th floor.

[0021] Although the master PLC 16 and each floor PLC 22a-22e are both PLCs, PLC station codes are used to distinguish between them. The PLC station code is 00 for the master PLC 16, and 01 to 05 are assigned to each floor PLC 22a-22e. PLC station code 01 is assigned to each floor PLC 22a located on BF, and PLC station code 02 is assigned to each floor PLC 22b located on 1F.

[0022] Similarly, PLC station number 03 is assigned to PLC 22c located on the 2nd floor, PLC station number 04 is assigned to PLC 22d located on the 3rd floor, and PLC station number 05 is assigned to PLC 22e located on the 4th floor. Hereinafter, the PLCs with PLC station numbers 01 to 05 will be referred to as PLC01 to PLC05, respectively.

[0023] On each floor, monitoring elements and control elements related to the building 8 are arranged, and in the example of the building 8, monitoring elements and control elements related to the facilities such as a switchboard and a cooling tower are arranged on the BF. Therefore, the monitoring elements and control elements on the BF are collectively referred to as the power and air conditioning panel 24a. The power and air conditioning panel 24a corresponds to a counterpart panel connected to the PLC01.

[0024] Since office equipment is located on the first floor of building 8, the monitoring elements and control elements related to the office equipment on the first floor are collectively referred to as office 1 board 24b. Office 1 board 24b corresponds to the counterpart board connected to PLC02. Similarly, office equipment is also located on the second and third floors of building 8, so the monitoring elements and control elements related to these office equipment are collectively referred to as office 2 board 24c and office 3 board 24d, respectively. Office 2 board 24c and office 3 board 24d correspond to the counterpart boards connected to PLC03 and PLC04, respectively.

[0025] Since a staff cafeteria equipped with a kitchen is provided on the 4th floor of building 8, the monitoring elements and control elements related to the cafeteria are collectively indicated as cafeteria board 24e. Cafeteria board 24e corresponds to a counterpart board connected to PLC05. PLC01 to PLC05 are connected to their respective counterpart boards by general signal lines 28 such as RS232.

[0026] The overall specifications of the PLC system 10 are defined by the specifications between the central monitoring device 12 and the PLC00, and the specifications between the PLC00 and the PLC01 to PLC05. Among these, the design document 30 defines the specifications between the PLC00 and the PLC01 to PLC05.

[0027] The design document 30 is created based on an agreement reached in a meeting with the client who is to order the management system for building 8. The created design document 30 includes a management item table 131, an input / output table 131 for each of PLC01 to PLC05, and a SW specification 133. Details of the design document 30 will be described with reference to FIG. 3 and subsequent figures.

[0028] [Design document generation device 40] 2 is a diagram showing the configuration of the design document generating device 40. The design document generating device 40 can be configured with a computer, and as the computer, a personal computer suitable for table creation and calculation processing is used.

[0029] The design document generating device 40 includes a CPU (Central Processing Unit) 61, a ROM (Read Only Memory) 62, a RAM (Random Access Memory) 63, and a storage device 64. These are connected to each other via a bus so as to be able to communicate with each other.

[0030] The CPU 61 loads a program stored in the ROM 62 into the RAM 63 and executes it to realize various functions of the design document generation device 40. The ROM 62 stores a program in which the processing procedures of the design document generation device 40 are written.

[0031] The RAM 63 serves as a working area when the CPU 61 executes a program, and temporarily stores the program, data required for executing the program, and the like.

[0032] The storage device 64 is a non-volatile storage device. The storage device 64 is, for example, a hard disk drive (HDD) or a solid state drive (SSD). The storage device 64 stores a database (hereinafter, abbreviated as "DB") 50. The DB 50 is a common database that registers data for generating a plurality of design document data 30. In addition to the DB 50, the storage device 64 stores a design document generation tool 100, which will be described later.

[0033] An input device 44 such as a keyboard and a display device 46 such as a display are connected to the design document generating device 40.

[0034] [Design document generation process flow] In this embodiment, a design document generation tool 100 (see FIG. 4 described later) is used to generate multiple design documents 30 (control item table 131, input / output table 132, SW specification 133, equipment number table 134, basic SW 135, and correlation table 136). The design document generation tool 100 is a single piece of software that operates independently.

[0035] In contrast to this, as a conventional example, for example, a design document generation tool group 101 is configured as equivalent to the design document generation tool 100. Fig. 3 is a diagram for explaining the flow of a process for generating design documents in the conventional example. The design document generation tool group 101 includes a DB 50, a management item table creation tool 121, an input / output table creation tool 122, a SW specification creation tool 123, an equipment number table creation tool 124, a SW production support tool 125, and a correlation table creation tool 126.

[0036] The design document generation tool group 101 is composed of an application program using, for example, Excel (product name) by Microsoft Corporation. However, it is not limited to this, and any table creation program that can handle character strings and use multiple worksheets in one file, in which the row and column of a cell or a character string can be specified as a search key in one worksheet and the searched content can be copied and pasted into another worksheet, will do.

[0037] The following describes the procedure and process flow for creating the design document 30 in the conventional example. First, the designer starts the data reading support tool 111 and reads the pre-order management item table 110. The pre-order management item table 110 is design data that serves as a rough draft for creating the design document 30.

[0038] The data reading support tool 111 is a tool that converts data so that the contents of the pre-order management item table 110 can be read into the design document generation tool group 101 (or the design document generation tool 100). The data reading support tool 111 reads the pre-order management item table 110 and generates a pre-order I / F file 112.

[0039] Next, the control item table creation tool 121 is started and the pre-order I / F file 112 is read. Then, the necessary items are entered on the screen of the control item table creation tool 121 (entering into Excel cells on a screen like that of FIG. 6, which will be described later). Through these operations, the control item table 131 is created by the control item table creation tool 121.

[0040] Furthermore, an operation for registering data in the DB 50 is performed on the management item table creation tool 121. This allows the data on the management item table creation tool 121 to be reflected in the DB 50.

[0041] Next, equipment number table creation tool 124 is launched, and an operation to read data from DB 50 is performed, so that the data read from DB 50 is reflected in equipment number table creation tool 124. Then, the necessary items are entered on the screen of equipment number table creation tool 124. Through these operations, equipment number table creation tool 124 creates equipment number table 134. Furthermore, the data on equipment number table creation tool 124 is registered in DB 50.

[0042] Next, when the input / output table creation tool 122 is started and an operation is performed to read data from DB50, the data read from DB50 is reflected in the input / output table creation tool 122. Then, the required items are entered on the screen of the input / output table creation tool 122 (a screen like that of FIG. 7 described below). Through these operations, the input / output table 132 is created by the input / output table creation tool 122. Furthermore, the data on the input / output table creation tool 122 is registered in DB50.

[0043] Similarly, the SW specification creation tool 123 creates the SW specification 133. The SW production support tool 125 creates the basic SW 135. The relational table creation tool 126 creates the relational table 136. These tools also read data from the DB 50 and register data from each tool in the DB 50.

[0044] Furthermore, the management item table creation tool 121 outputs building management system data 141. The building management system data 141 is data to be used in a building management system that manages the entire building facilities including the PLC system 10. The designer starts up the building management system tool 142 and causes it to read the building management system data 141. The data reading support tool 111 generates data to be read into the building management system based on the building management system data 141.

[0045] As described above, each tool in the group of design material generating tools 101 can be started independently. Each tool exchanges data with the DB 50, and outputs the design material 30 corresponding to each tool.

[0046] The problem here is that although each tool uses the common DB50, each tool itself also stores data in Excel. In other words, the same data is stored in DB50 and each tool. This causes problems such as data inconsistency (disappointment) where data is updated in Excel on a tool but not reflected in DB50. For example, if data on Excel is updated in one tool without being reflected in DB50, and data is read from DB50 in another tool, data consistency between the tools will be lost.

[0047] In contrast to this, the present embodiment has a configuration as shown in Fig. 4. Fig. 4 is a diagram for explaining the flow of design material generation processing according to the present embodiment.

[0048] In this embodiment, a design document generation tool 100 is used instead of the design document generation tool group 101. The design document generation tool group 101 is composed of a plurality of tools that can be started independently. On the other hand, the design document generation tool 100 according to this embodiment starts as a single piece of software.

[0049] The basic operation is the same except that the group of planning document generation tools 101 is replaced with the design document generation tool 100. As in the example of Fig. 3, the design document generation tool 100 is started and the pre-order I / F file 112 created by the data reading support tool 111 is read.

[0050] After the designer has input data, etc., the design document generation tool 100 generates various design documents 30, including a management item table 131, an input / output table 132, a SW specification 133, an equipment number table 134, a basic SW 135, and a correlation table 136, all at once, and also generates data 141 for the building management system.

[0051] Here, the design document generation tool 100 runs as a single piece of software, but like the conventional example, it comprises a DB 50, a management item table creation tool, an input / output table creation tool, a SW specification creation tool, an equipment number table creation tool, a SW production support tool, and a correlation table creation tool.

[0052] The functions of these tools are equivalent to those of the design document generation tool group 101, but these are not application programs using Excel. When the design document generation tool 100 is started, first, a launcher tool (hereinafter also referred to as "launcher") is started.

[0053] Each tool can be launched from the launcher. Each tool reads data from DB50 and writes data to DB50 to generate design documents corresponding to each tool. However, the data used by each tool is managed only by DB50, and each tool itself does not hold the data.

[0054] When each tool is closed, the data held by the tool is always reflected in the DB 50, and when the tool is closed, the tool screen is cleared and the held data is discarded. Also, each tool is configured to be able to be selectively launched one by one from the launcher, and after data input and other operations are completed, the design documents 30 are output all at once.

[0055] For example, if the management item table creation tool is started from the launcher, the management item table creation tool reads the data from DB 50. After inputting data into the management item table creation tool is completed, DB 50 is updated and the management item table creation tool is terminated. In this case, the management item table creation tool itself does not hold the data.

[0056] After the management item table creation tool is finished, another tool can be launched. For example, if the equipment personnel table creation tool is launched from the launcher, the equipment personnel table creation reads data from DB50. After the input work in the equipment personnel table creation is finished, DB50 is updated and the equipment personnel table creation tool is terminated. In this case, the equipment personnel table creation tool itself does not hold the data.

[0057] After all the work is completed, the data output screen is started. On the data output screen, data is read from DB 50, and design documents 30 (control item table 131, input / output table 132, SW specification 133, equipment number table 134, basic SW 135, and correlation table 136) are output all at once. In this way, each data for outputting design documents 30 is managed centrally in DB 50.

[0058] [Design Document Generation Tool 100] The operation of the design material generation tool 100 will be specifically described below with reference to Figures 5 to 8. Figure 5 is a diagram for explaining a launcher screen 70.

[0059] 5(a), when the design document generation tool 100 is started, a launcher screen 70 is displayed. The launcher screen 70 is provided with a "Project Information" button, a pull-down menu, an "Open" button, a "Data Output" button, and an "Exit" button.

[0060] Clicking the "Project Information" button displays a "Project Information Screen" (not shown) for inputting project information. Project information includes, for example, the project name, building number, order number, and building specifications. The designer inputs this information. Also, some of the information can be read from the pre-order I / F file 112. After inputting this information, the DB 50 is updated, the project information screen is closed, and the user returns to the launcher screen 70.

[0061] When the pull-down menu on the launcher screen 70 is pressed, a list of each tool is displayed, as shown in Fig. 5(b). For example, when "Management Item Table" is selected and the "Open" button is clicked, the management item table creation tool is launched.

[0062] The correspondence between the selection items in the pull-down menu and the tools and output data is as shown in Fig. 5(c). The selection items include a management item table (ID:1), an input / output table (ID:2), SW specifications (ID:3), an equipment number table (ID:4), a basic SW (ID:5), and a relative table 136 (ID:6).

[0063] When a selection item is selected and the "Open" button is clicked, the tool with the ID number corresponding to the selected selection item is started. The tool corresponding to the management item table (ID: 1) is the management item table creation tool, which creates the management item table 131.

[0064] (ID:2) Corresponding to the input / output table is an input / output table creation tool, which generates an input / output table 132. (ID:3) Corresponding to the SW specification is an SW specification creation tool, which generates an SW specification 133. (ID:4) Corresponding to the equipment personnel number table is an equipment personnel number table creation tool, which generates an equipment personnel number table 134.

[0065] Corresponding to the basic SW (ID: 5) is a basic SW creation tool, which generates the basic SW 135. Corresponding to the relative table (ID: 6) is a relative table creation tool, which generates the relative table 136.

[0066] When each tool is started, the DB is read and some or all of the output data corresponding to the started tool is automatically generated and displayed on the screen. The designer adds or changes data on the screen as necessary and updates the DB.

[0067] When the work in each tool is completed, the user returns to the launcher screen 70. When the "Data Output" button is clicked, a data output menu screen 73 is displayed. On the data output menu screen 73, the design documents 30 can be generated all at once.

[0068] The generated design materials 30 (design material data 30) is, for example, a data file in a format readable by software for viewing materials, a data file in a format readable by dedicated software for designing software, or a data file in a format readable by some kind of dedicated software.

[0069] When the data output menu screen 73 is closed, the screen returns to the launcher screen 70. When the "Exit" button is clicked, the display of the launcher screen 70 is terminated and the design material generation tool 100 is terminated.

[0070] Fig. 6 is a diagram for explaining the control item table screen As shown in Fig. 6, when the control item table creation tool is started, a control item table screen 72 is displayed.

[0071] "Case name" is the name of PLC system 10. In the example of Fig. 1, the name of building 8, etc. is taken as the "case name." "Backbone" is the system name of backbone network 26 between PLC00 and PLC01-PLC05 in PLC system 10; in the case of Fig. 1, the second system of backbone network 26 is defined as CCL, so "CCL" is entered in advance. "Case name" and "Backbone" can be read from DB 50 and displayed.

[0072] Following the "Management item name," "PLC station number," and "RS panel name" are six I / O signal types. The six I / O signal types are two related to control, "BO: Individual start / stop" and "AO: Analog output," and four related to monitoring, "BI: Status," "BI: Measurement," "AI: Current / voltage," and "AI-R: Resistance."

[0073] "Management item name" is the name of the management item, i.e., the name of the management item, where the control elements and monitoring elements located in building 8 in PLC system 10 are considered to be "management items." "PLC station number" is the station number of the PLC that handles that "management item," so "00" is entered for PLC00. "RS panel name" is the name of the RS panel that houses that PLC, so "RS-1" is entered for RS-1. At least one PLC is housed in an RS panel.

[0074] The six I / O signal type columns indicate the signal type when the "control item" is handled by the PLC. One signal type is defined for one "control item."

[0075] The two "control" related signals, "BO: Individual On / Off" and "AO: Analog Output", are signals output from a PLC to a control element when the management item relates to a control element. When the signal is a binary digital signal, it is "BO: Individual On / Off". BO=1 is a signal that activates the operation of the target control element, and BO=0 is a signal that stops the operation of the target control element. Examples of "BO" signals include turning the heater on and off, lighting on and off, air conditioning on and off, and power on and off. When the signal output to a control element is an analog signal, it is "AO: Analog Signal". Examples of "AO" signals include continuously variable opening and closing signals for valves, lighting dimming signals, and air conditioning temperature command signals.

[0076] "BI" and "AI" related to "monitoring" are signals input from a monitoring element to a PLC when a management item is related to the monitoring element. When the signal is a binary digital signal, it is "BI", and when it is an analog signal, it is "AI".

[0077] "BI" indicates the state of the monitored element, with BI=1 indicating that the monitored element is in operation and BI=0 indicating that the monitoring element is stopped. "BI" is a pulse signal, and there are monitored elements that "meter" by counting this pulse signal. Examples include electricity meters, water meters, and gas meters. These measure amounts by rotating a disk or ring. By outputting one pulse per rotation and counting the number of pulses, the consumption of these can be "metered."

[0078] In other words, power meters, water meters, gas meters, etc. are not monitored by analog signals, but rather by the number of pulses in the binary "BI." The "Status" and "Measurement" columns of the "BI" are the same binary signal inputs, but are used to distinguish whether or not the number of pulses needs to be counted in the PLC.

[0079] In other words, if the monitored element is a "meter", a circle mark is entered in the "measurement" column, and if it is not a "meter", a circle mark is entered in the "status" column. The circle mark may be entered by clicking on the corresponding area, or a check box may be checked instead of the circle mark.

[0080] "AI" is a voltage signal or a current signal, but temperature is measured by measuring resistance. "AI" is converted from an analog signal to a digital signal in the PLC and transmitted to PLC00, but the circuits used to convert "current / voltage" analog signals and "resistance" analog signals to digital signals are different. Therefore, to distinguish between the types of input / output devices related to "AI", input / output devices related to "current / voltage" are indicated as "AI" and input / output devices related to "resistance" are indicated as "AI-R".

[0081] Enter the name of the monitored element in "Management Item Name," enter the station number of the PLC that handles that monitored element in "PLC Station Number," and enter the name of the RS panel that houses that PLC in "RS Panel Name." Then determine whether the type of signal input from the monitored element to the PLC is a binary digital signal or an analog signal. If it is a digital signal, determine whether it is the "BI" "Status" or the meter system "Measurement," and enter a circle in either field. If it is an analog signal, determine whether it is the "Current / Voltage" or the temperature detection "Resistance," and enter a circle in either field.

[0082] The number of RS panels and the number of PLCs are set by the designer based on the total number of "management items" and their layout in Building 8. As an example, in the case of Figure 1, the total number of "management items" is 350. In the case of an eight-slot PLC, if one slot is reserved for communications and one spare slot, six slots can be allocated for I / O devices. If standard I / O devices with 16 channels are used, one PLC can handle approximately 100 "management items." If the total number of "management items" is 350, four PLCs will be required.

[0083] In the PLC system 10 of FIG. 1, an RS board is placed on each floor, and each RS board is configured to house one PLC.

[0084] The designer completes inputting information about all "control items." The total number of "control items" is 350, but Fig. 6 shows only a portion of them. A scroll bar is displayed on the right side of the control item table screen 72. By operating this scroll bar, all control items can be displayed.

[0085] When all items are entered and the "Register" button is clicked, the DB 50 is updated. When the "Close" button is clicked, the management item table creation tool is terminated and the screen returns to the launcher screen 70. If the DB 50 has not been updated when the "Close" button is clicked, the DB 50 is updated and the management item table creation tool is terminated.

[0086] The control item table data 131 output by the control item table creation tool is data including a plurality of control items (control item names) for the entire PLC system 10. Each of the plurality of control items is associated with a PLC number (PLC station number: 00-05) that identifies each of the plurality of PLCs (PLC00-05) and a type of input / output signal input to and output from the plurality of PLCs (BO: individual on / off, "AO: analog output", "BI: status", "BI: measurement", "AI: current / voltage", "AI-R: resistance").

[0087] Fig. 7 is a diagram for explaining the input / output table screen. As shown in Fig. 6, when the input / output table creation tool is started, an input / output table screen 71 is displayed.

[0088] In this embodiment, although illustration is omitted, it is assumed that the configuration shown in the lower part of the figure has been set by the equipment number table tool. Here, in PLC01, the model name "QCCL" is placed in slot=0 as a "communication" device. In this example, the "points" are set to "32", and the "start address" for "QCCL" is set to "03E0". Also, in PLC01, "BI64" is assigned to slot=01 to slot=03 as an input device.

[0089] The leading XY address of the BI device is "X100", and the leading XY address of "X100" is assigned to "BI64" in slot 01. "BI64" in slot 02 is assigned "X140", shifted by "20" in 16-bit notation corresponding to 64 channels, and "BI64" in slot 03 is assigned "X180", shifted by a further "20" for 64 channels. Equipment personnel count data 135 output by the equipment personnel count tool is data indicating such equipment configuration.

[0090] In the I / O table screen 71, data is read from DB50, and the case name, subsystem, system, station number, and board name are displayed. "Model name," "Slot No.", and "Start XY" are basic information related to the I / O device "BI64." When an I / O device is selected, the information corresponding to that I / O device is displayed as is. In this example, the "Model name" is "BI64," the "Slot No." is "1," and the "Start XY" is "0100."

[0091] The "Pin number" in the I / O information column is the terminal number of the relevant I / O device. "CH" is the channel number of the relevant I / O device, "BI64." "Address" is the address of the CPU in the relevant PLC. "Name" is the "Management item name" in the management item table. Since "BI64" has 64 channels, "CH" displays channels "1" to "64," and "Pin number" displays the terminal numbers from "1" to "80." Also, reflecting that "Start XY" is "0100," "Address" displays "X100" to "X13F."

[0092] Designers can use the vacant "pin numbers" from "1B04" to "1B01" to assign a common terminal for the power supply. For example, the common terminal for the power supply of PCL01 can be set to COM1, and COM1 can be set to the vacant pin number.

[0093] Then, the control item table is read from DB50. Then, the PLC station number = 01 is used as the first search key, and "BI", which is the type of I / O signal corresponding to "BI64", which is the model name of the selected I / O device, is used as the second search key to extract the "control item name" sequentially from the smallest row number.

[0094] Next, for the multiple "control item names" that were extracted, the "control item name" with the smallest row number is obtained and entered into the "Name" of "CH"=1 in the PLC I / O table blank 35. In the control item table of Figure 6, the first control item name among the control item names that correspond to "BI" for PLC station number=01 is "Low temperature PACACP status." This is entered into the "Name" of "CH"=1 in the I / O table.

[0095] Thereafter, the names of the control items are entered in order in the "Name" column. Also, "Measuring" is entered in the "Signal Type" column in Fig. 7, corresponding to the circle mark for "Measuring" in "BI" in Fig. 6. As in Fig. 6, a scroll bar is displayed on the right side of the input / output table screen 71. All items can be displayed by operating this scroll bar.

[0096] When editing of the I / O table for "BI64" placed in slot=1 of PLC01 is finished, the designer clicks the "Next" button. This displays the I / O table for "BI64" placed in slot=2 of PLC01. Each time the "Next" button is clicked, the I / O table for the next slot is displayed.

[0097] When input has been completed for all slots of PLC01, the I / O display for PLC02 will be displayed. In this way, you can enter and edit the I / O tables for PLC01 to 05. You can also display the previous I / O table by clicking the "Previous" button.

[0098] When all items are entered and the "Register" button is clicked, the DB 50 is updated. When the "Close" button is clicked, the input / output table creation tool is terminated and the screen returns to the launcher screen 70. If the DB 50 has not been updated when the "Close" button is clicked, the DB 50 is updated and the input / output table creation tool is terminated.

[0099] The input / output table data 132 output by the input / output table creation tool is data including a plurality of addresses (such as "X100") to which input / output signals are assigned. Each of the plurality of addresses is associated with one of a plurality of management items (such as "low temperature PAC, APC status"). The input / output table makes it possible to specify which signal is input to and output from which terminal (which address) of which device.

[0100] Moreover, the multiple design document data 30 include SW specification data 133 and basic SW data 135 as software data. The software data is data for creating a ladder program that operates the PLC system 10. The SW specification data 133 is specification data illustrating the control flow of input and output signals. The ladder program is created by referring to this specification. The basic SW data 135 is software data to be read into dedicated software that generates the ladder program. The relative table data 136 is drawing data for displaying a wiring diagram showing the connection relationships of the PLC system 10.

[0101] 8 is a diagram for explaining the data output menu screen. When the "Data Output" button is clicked on the launcher screen 70, a data output menu screen 73 is displayed as shown in FIG.

[0102] On the screen, check boxes are displayed corresponding to each item in the Input / Output Table, SW Specifications, Equipment Quantity Table, Basic SW, Relative Table, and Management Item Table. All of these check boxes are displayed as checked. Clicking the "Output" button will generate design documents corresponding to the items whose check boxes are checked.

[0103] When the "Output" button is clicked with all items checked as shown in FIG. 8, the design documents 30, including the control item table 131, input / output table 132, SW specification 133, equipment number table 134, basic SW 135, and correlation table 136, are output.

[0104] In this embodiment, each tool, such as a management item table creation tool, reads data from the DB 50 for each design document 30, and outputs design documents 30 such as the management item table 131 corresponding to each tool. However, this is not limited to the above, and the design document generation tool 100 itself may read data from the DB 50 and output each design document 30. When the "Close" button is clicked, the data output menu screen 73 closes and the screen returns to the launcher screen 70.

[0105] [Main processing flowchart] The CPU 61 executes a design document generation process. The main process is a process executed by the CPU 61 when the design document generation tool 100 is started, and corresponds to Fig. 5 to Fig. 8. Fig. 9 to Fig. 12 are flowcharts of the design document generation process executed by the CPU 61. Hereinafter, "step" may be simply referred to as "S".

[0106] 9, when the execution of the design material generation process starts, the CPU 61 starts up a launcher (launcher tool) in S11 and advances the process to S12. As a result, a launcher screen 70 (see FIG. 5(a)) is displayed on the display device 46.

[0107] In S12, the CPU 61 determines whether or not the "Case Information" button has been clicked. If the CPU 61 determines in S12 that the "Case Information" button has been clicked (YES in S12), the process proceeds to S13. On the other hand, if the CPU 61 does not determine in S12 that the "Case Information" button has been clicked (NO in S12), the CPU 61 executes S12 again.

[0108] In S13, the CPU 61 reads data from the pre-order I / F file as pre-order data, and proceeds to S14. In S14, the CPU 61 acquires input information for the project data entered by the designer, and proceeds to S15. For example, input information such as the project name and building number as shown in FIG. 5(a) is acquired.

[0109] In S15, the CPU 61 determines whether or not the "Register" button has been clicked. If the CPU 61 determines in S15 that the "Register" button has been clicked (YES in S15), the process proceeds to S16. On the other hand, if the CPU 61 does not determine in S15 that the "Register" button has been clicked (NO in S15), the process returns to S14. In S16, the CPU 61 updates the DB 50 based on the input information of the case data, and proceeds to "A" (S21 in FIG. 10).

[0110] As shown in Fig. 10, the CPU 61 determines in S21 whether or not a button has been operated on the screen shown in Fig. 5(a) and (b). If the CPU 61 determines in S21 that a button has been operated (YES in S21), the process proceeds to S22. On the other hand, if the CPU 61 does not determine in S21 that a button has been operated (NO in S21), the CPU 61 executes S21 again.

[0111] In S22, the CPU 61 determines whether or not a menu has been selected and the "Open" button has been clicked. If the CPU 61 determines in S22 that a menu has been selected and the "Open" button has been clicked (YES in S22), the process proceeds to "B" (S31 in FIG. 11). On the other hand, if the CPU 61 does not determine in S22 that a menu has been selected and the "Open" button has been clicked (NO in S22), the process proceeds to S23.

[0112] In S23, the CPU 61 determines whether or not the "Data Output" button has been clicked. If the CPU 61 determines in S23 that the "Data Output" button has been clicked (YES in S23), the process proceeds to "C" (S41 in FIG. 12). When the "Data Output" button is clicked, the data output menu screen 73 (see FIG. 8) is displayed. On the other hand, if the CPU 61 does not determine in S23 that the "Data Output" button has been clicked (NO in S23), the process proceeds to S24.

[0113] In S24, the CPU 61 determines whether or not the "End" button has been clicked. If the CPU 61 determines in S24 that the "End" button has been clicked (YES in S24), the design document generation process ends. When the design document generation process ends, the design document generation tool 100 ends. On the other hand, if the CPU 61 does not determine in S24 that the "End" button has been clicked (NO in S24), the process returns to S21.

[0114] 11, in S31, the CPU 61 starts a tool having an ID corresponding to the selection item shown in Fig. 5(c) and proceeds to S32. That is, one of the tools, the management item table creation tool, the input / output table creation tool, the SW specification creation tool, the equipment number table creation tool, the basic SW creation tool, and the correlation table creation tool, is started.

[0115] In S32, the CPU 61 reads the DB 50 and proceeds to S33. The information read from the DB 50 is displayed on the screen of each tool. In S33, the CPU 61 obtains data input information input by the user and proceeds to S34. For example, data input information on a management item table screen 72 as shown in FIG. 6 or data input information on an input / output table screen 71 as shown in FIG. 7 is obtained.

[0116] In S34, the CPU 61 determines whether or not the "Register" button has been clicked. If the CPU 61 determines in S34 that the "Register" button has been clicked (YES in S34), the process proceeds to S35. On the other hand, if the CPU 61 does not determine in S34 that the "Register" button has been clicked (NO in S34), the process returns to S33.

[0117] In S35, the CPU 61 updates the information DB based on the data input information entered on the screen of each tool, and proceeds to S36. In S36, the CPU 61 ends the currently active tool when the "Close" button is clicked, and proceeds to "A" (S21 in FIG. 10).

[0118] In this manner, the CPU 61 executes a plurality of processes (processes for executing each tool such as the management item table creation tool in S31 to S36) corresponding to each of the plurality of design document data 30 (such as the management item table data 131). In each of the plurality of processes, the CPU 61 updates the DB 50 based on data input by the user. The CPU 61 also executes a process for executing a launcher tool as a main process. In the process for executing the launcher tool, the CPU 61 selects one of the plurality of processes and starts it (S31). In each of the plurality of processes, the display device 46 also performs display based on data input by the user and data read from the DB 50.

[0119] 12, the CPU 61 determines in S41 whether or not the "output" button has been clicked. If the CPU 61 determines in S41 that the "output" button has been clicked (YES in S41), the process proceeds to S42. On the other hand, if the CPU 61 does not determine in S41 that the "output" button has been clicked (NO in S41), the CPU 61 executes S41 again.

[0120] In S42, the CPU 61 sets i=1, and proceeds to S43. In S43, the CPU 61 determines whether or not an output file (output data) corresponding to ID=i has been selected. That is, in FIG. 8, the CPU 61 determines whether or not a check box has been checked.

[0121] The relationship between the selection items, tools, and output files corresponding to the IDs is as shown in Figure 5(c). For example, the selection item corresponding to ID=1 is "Management Item Table", the tool corresponding to ID=1 is "Management Item Table Creation Tool", and the output file corresponding to ID=1 is "Management Item Table 131".

[0122] If the CPU 61 determines in S43 that an output file corresponding to ID=i has been selected (YES in S43), the process proceeds to S44. On the other hand, if the CPU 61 does not determine in S43 that an output file corresponding to ID=i has been selected (NO in S43), the process proceeds to S47.

[0123] In S44, the CPU 61 starts the tool with ID=i, and the process proceeds to S45. In S45, the CPU 61 reads the DB 50, and the process proceeds to S46. In S46, the CPU 61 outputs output data, and the process proceeds to S47. For example, if the check box for "input / output table" (ID=1) is checked, the control item table creation tool is started, and the control item table data 131 is output based on the read DB 50.

[0124] In S47, the CPU 61 determines whether or not i<6. If the CPU 61 determines in S47 that i<6 (YES in S47), the process proceeds to S48. On the other hand, if the CPU 61 does not determine in S47 that i<6, that is, if the process for all IDs (1 to 6) has been completed (NO in S47), the process proceeds to S49.

[0125] In S48, the CPU 61 sets i=i+1, and returns the process to S43. If the "Close" button is clicked in S49, the CPU 61 ends the data output menu screen 73 (FIG. 8) and returns the process to "A" (S21 in FIG. 10). In this way, the CPU 61 generates multiple pieces of design document data 30, such as the management item table data 131, based on the data read from the DB 50.

[0126] As described above, the design document generating device 40 in this embodiment generates a plurality of design document data 30 for designing the PLC system 10 that controls the entirety of a plurality of PLCs (PLC00 to PLC05) installed in a facility. The design document generating device 40 includes a storage device 64 and a CPU 61. The storage device 64 stores a common database (DB) 50 that registers data for generating a plurality of design document data 30. The CPU 61 executes a plurality of processes (processes for executing each tool) corresponding to each of the plurality of design document data 30. In each of the plurality of processes, the CPU 61 updates the DB 50 based on data input by a user. The CPU 61 generates a plurality of design document data 30 based on data read from the DB 50. In this way, each tool does not hold data itself, and data is managed only by the common DB 50, so that it is possible to suppress the occurrence of data inconsistency when generating a plurality of design document data 30 for designing the PLC system 10.

[0127] In this embodiment, a building management system in which a plurality of pieces of equipment in a building with one basement floor and four aboveground floors are managed by one master PLC and five individual floor PLCs has been described as an example of a PLC system. However, the present invention is not limited to this, and the number of individual floor PLCs may be other than the above, and the building may have other numbers of floors. Furthermore, the present invention may be a management system for machinery and equipment other than a building management system.

[0128] [Main components and effects] The main configurations and effects of the above-described embodiment will be described below.

[0129] (1) The design document generating device 40 generates a plurality of design document data 30 for designing a PLC system 10 that controls a plurality of PLCs (PLC00 to PLC05) installed in a facility. The design document generating device 40 includes a storage device 64 and a CPU 61. The storage device 64 stores a common database (DB) 50 that registers data for generating a plurality of design document data 30. The CPU 61 executes a plurality of processes (processes for executing each tool) corresponding to each of the plurality of design document data 30. In each of the plurality of processes, the CPU 61 updates the DB 50 based on data input by a user. The CPU 61 generates a plurality of design document data 30 based on data read from the DB 50. In this way, each tool does not hold data itself, and data is managed only by the common DB 50, so that it is possible to suppress the occurrence of data inconsistency when generating a plurality of design document data 30 for designing the PLC system 10.

[0130] (2) The CPU 61 further executes a main process (a process for executing a launcher). The main process is a process for selecting and starting one of a plurality of processes. In this way, the tools are started one by one to update the DB 50, so that the occurrence of data inconsistency can be suppressed.

[0131] (3) The design document generating device 40 further includes a display device 46. The display device 46 displays, in each of the multiple processes, data input by the user and data read from the DB 50. This allows the data generated in the multiple design document data 30 to be confirmed on the display device 46.

[0132] (4) The plurality of design document data 30 includes control item table data 131. The control item table data 131 includes a plurality of control items for the entire PLC system 10. Each of the plurality of control items is associated with a PLC number that identifies each of the plurality of PLCs and a type of input / output signal that is input to and output from the plurality of PLCs. This makes it possible to prevent data inconsistencies from occurring in the PLC system 10 generated including the control item table data 131.

[0133] (5) The plurality of design document data 30 includes input / output table data 132. The input / output table data 132 includes a plurality of addresses to which input / output signals are assigned. Each of the plurality of addresses is associated with one of a plurality of management items. This makes it possible to prevent data inconsistencies from occurring in the PLC system 10 generated using the input / output table data 132.

[0134] (6) The multiple design document data 30 include software data (SW specification data 133, basic SW data 135). The software data is data for creating a program that operates the PLC system 10. This makes it possible to prevent data inconsistencies from occurring in the PLC system 10 generated using the SW specification data 133 and basic SW data 135.

[0135] (7) The design document generation method is a method for generating a plurality of design document data 30 for designing a PLC system 10 that controls a plurality of PLCs (PLC00 to PLC05) installed in a facility. The design document generation method includes a step of registering data for generating the plurality of design document data 30 in a common database (DB) 50, and a step of executing a plurality of processes (processes for executing each tool) corresponding to each of the plurality of design document data 30. The step of executing the plurality of processes includes a step of updating the DB 50 based on data input by a user in each of the plurality of processes, and a step of generating the plurality of design document data 30 based on data read from the DB 50. In this way, each tool does not hold data itself, and data is managed only by the common DB 50, so that it is possible to suppress the occurrence of data inconsistency when generating the plurality of design document data 30 for designing the PLC system 10.

[0136] The embodiments disclosed herein are merely examples and are not limited to the above. The scope of the present invention is defined by the claims, and it is intended to include all modifications within the scope and meaning equivalent to the claims. [Explanation of symbols]

[0137] 8 building, 10 PLC system, 12 central monitoring device, 14 master PLC panel (RS-0), 16 master PLC (PLC00), 18 first system backbone network, 20a, 20b, 20c, 20d, 20e PLC panel for each floor (RS-1 to RS-5), 22a, 22b, 22c, 22d, 22e PLC panel for each floor (PLC00 to PLC05), 24a power and air conditioning panel, 24b office 1 panel, 24c office 2 panel, 24d office 3 panel, 24e cafeteria panel, 26 second system backbone network (CCL), 28 signal line, 30 design documents, 40 design document generation device, 44 input device, 46 display device, 50 DB, 61 CPU, 62 ROM, 63 RAM, 64 storage device, 70 launcher screen, 71 input / output table screen, 72 management item table screen, 73 Data output menu screen, 100 design document generation tool, 101 design document generation tool group, 110 pre-order control item table, 111 data reading support tool, 112 pre-order I / F file, 121 control item table creation tool, 122 input / output table creation tool, 123 SW specification creation tool, 124 equipment number table creation tool, 125 SW production support tool, 126 relative table creation tool, 131 control item table, 132 input / output table, 133 SW specification, 134 equipment number table, 135 basic SW, 136 relative table, 141 building management system data, 142 building management system tool.

Claims

1. A design document generation device that generates a plurality of design document data for designing a PLC system that controls a plurality of PLCs installed in a facility, A storage unit that stores one database in which common data for generating the plurality of pieces of design document data is registered; a control unit that executes a plurality of processes corresponding to each of the plurality of design document data, The control unit is When a predetermined process among the plurality of processes is instructed by a user, the predetermined process is started, while control is performed so that processes other than the predetermined process among the plurality of processes are not started; When an instruction to register the specified data is given after the user inputs the specified data in the specified process, the specified data is discarded and the specified data is registered in the database; the predetermined data is data used for predetermined design document data corresponding to the predetermined processing, and includes common data used for design document data different from the predetermined design document data, The control unit generates the plurality of design document data collectively using data read from the database when an output instruction is given by the user.

2. 2. The design document generating device according to claim 1, further comprising a display unit that performs display based on the data input by the user and the data read from the database in each of the plurality of processes.

3. the plurality of design document data includes management item table data including a plurality of management items for the entire PLC system, 3. The design document generating device according to claim 1, wherein each of the plurality of management items is associated with a PLC number that identifies each of the plurality of PLCs and a type of an input / output signal that is input to or output from the plurality of PLCs.

4. the plurality of design document data includes input / output table data including a plurality of addresses to which the input / output signals are assigned; 4. The design document generating device according to claim 3, wherein each of the plurality of addresses is associated with one of the plurality of management items.

5. 5. The design material generating device according to claim 4, wherein the plurality of design material data includes software data for creating a program for operating the PLC system.

6. 1. A design document generation method for generating a plurality of design document data for designing a PLC system for controlling a plurality of PLCs installed in a facility, comprising: A step of registering common data for generating the plurality of design document data in one database; executing a plurality of processes corresponding to each of the plurality of design document data; The step of executing the plurality of processes includes: a step of controlling, when a predetermined process among the plurality of processes is instructed by a user, to start the predetermined process while not starting any process other than the predetermined process among the plurality of processes; a step of discarding the predetermined data and registering the predetermined data in the database when an instruction to register the predetermined data is given after the user inputs the predetermined data in the predetermined process; the predetermined data is data used for predetermined design document data corresponding to the predetermined processing, and includes common data used for design document data different from the predetermined design document data, The design material generating method, wherein the step of executing the plurality of processes further includes a step of generating the plurality of design material data collectively using data read from the database when an output instruction is given by the user.

Images