Management system and management method

The database management system addresses the inefficiencies in modular construction by centralizing database management, enhancing commissioning efficiency and reducing manual errors through a virtual network connection.

JP7794146B2Active Publication Date: 2026-01-06YOKOGAWA ELECTRIC CORP
View PDF 8 Cites 0 Cited by

Patent Information

Application Number
JP2023027661
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2023-02-24
Publication Date
2026-01-06
Estimated Expiration
2043-02-24

AI Technical Summary

Technical Problem

The modular construction method faces challenges in efficiently performing commissioning work in the module yard due to the need for splitting and merging of the master database during commissioning, which is labor-intensive and prone to errors.

Method used

A database management system that includes a database device, control device, and management device, allowing for centralized data management and eliminating the need for manual splitting and merging of databases by connecting devices in a virtual environment via a wide area network.

Benefits of technology

This system enables efficient and error-free commissioning operations by centrally managing the master database, reducing the burden on workers and minimizing manual errors.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007794146000001
    Figure 0007794146000001
  • Figure 0007794146000002
    Figure 0007794146000002
  • Figure 0007794146000003
    Figure 0007794146000003
Patent Text Reader

Abstract

To more efficiently execute trial operation work to centrally manage a master database.SOLUTION: A management system includes a database device, a controller, and a management device. The database device stores data related to the setting of devices included in a plant. The controller is used for controlling trial operation of a plant module as at least part of the plant and is arranged in a module yard where the trial operation is performed. The management device performs system construction and maintenance management of the plant module. The management device stores data changed by the trial operation into the database device. The management device downloads the data used for the trial operation from the database device to the controller via a wide area network.SELECTED DRAWING: Figure 2
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The present invention relates to a management system and a management method. [Background technology]

[0002] In recent years, the modular construction method (hereinafter also referred to as the module construction method) has become mainstream in the construction of process plants. Here, the modular construction method is a construction method in which, in order to minimize work at the plant construction site (hereinafter also referred to as the site), a set of components (hereinafter also referred to as the module) is constructed with steel frames, piping, equipment, etc. arranged in a yard (hereinafter also referred to as the module yard) separate from the site, and the plant is completed by transporting the modules to the site and joining them together. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2022-155175 Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the above-mentioned modular construction method, it is difficult to efficiently perform commissioning work (hereinafter also referred to as trial operation) in the module yard. This is because the above-mentioned technology requires splitting the master database during commissioning work in the module yard. Also, when the commissioning work is completed, the split databases must be merged into one master database.

[0005] One aspect is to perform commissioning operations more efficiently and to centralize the master database. [Means for solving the problem]

[0006] A management system according to one aspect includes a database device, a control device, and a management device. The database device stores data related to the settings of each device included in a plant. The control device is used to control a trial run of a plant module that is at least a part of the plant, and is located in a module yard where the trial run is performed. The management device performs system construction and maintenance management of the plant module. The management device stores data changed by the trial run in the database device. The management device downloads the data used for the trial run from the database device to the control device via a wide area network. [Effects of the Invention]

[0007] According to one embodiment, it is an object to perform commissioning operations more efficiently and to centrally manage the master database. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram for explaining an overview of a database management process according to an embodiment. [Figure 2] FIG. 1 is a diagram for explaining an overview of a database management process according to an embodiment. [Figure 3] 1 is a diagram illustrating an example of the overall configuration of a database management system according to an embodiment. [Figure 4] FIG. 1 is a block diagram illustrating an example of the configuration of a database device according to an embodiment. [Figure 5] FIG. 2 is a block diagram showing an example of the configuration of a management device (ENG) according to the embodiment. [Figure 6] 1 is a block diagram illustrating an example of the configuration of an information processing device according to an embodiment. [Figure 7] FIG. 10 is a sequence diagram showing an example of the flow of a database management process according to the embodiment. [Figure 8] FIG. 2 is a diagram illustrating an example of a hardware configuration of a database device. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, embodiments of the management system and management method disclosed in the present application will be described in detail with reference to the accompanying drawings. Note that the invention of the present application is not limited to the embodiments described here. Furthermore, identical elements are given the same reference numerals, and redundant explanations will be omitted as appropriate. Furthermore, each embodiment can be combined as appropriate within a range that does not cause inconsistencies.

[0010] [1. Introduction] In the database management system 1 (an example of a management system) according to this embodiment, commissioning work is carried out in a commissioning office, multiple module yards, and sites (plant construction sites) in preparation for the construction of a plant using a modular construction method and the operation of the plant.

[0011] The commissioning work is managed by a commissioning office, which may be, for example, but is not limited to, an operator's management center in a module yard or an operator's management center in a plant.

[0012] The commissioning office uses a database that has passed inspection by FAT (Factory Acceptance Test). Here, FAT is an in-house inspection process that covers the inspection process from basic design to the final inspection stage of the plant, including functional inspection before commissioning work and factory shipping inspection. Once the FAT inspection is completed, an inspected DB (Data Base) is created.

[0013] This FAT verified DB is set as the management DB (master database) of the development system. For example, the management DB is created by manually copying the verified DB. Here, the development system is a system that manages the databases provided to the site system.

[0014] Next, commissioning work is carried out in the module yard. Here, the module yard is a place where the trial operation of equipment to be used in the site system is carried out for each piece of equipment that shares common processes and operations within the plant. The module yard is a place where the trial operation of process equipment is carried out, but is not limited to this.

[0015] [1.1. Challenges] In conventional commissioning work, a test run DB is generated for each commissioning system in multiple module yards from an inspected DB by FAT or a management DB (master database) of the development system. Here, the commissioning system is the system that executes the commissioning work.

[0016] The commissioning database is created by retaining the data necessary for commissioning work at the module yard from the management database and deleting the data necessary for commissioning work at other module yards.

[0017] The data required for the commissioning work in the module yard is data on the control devices and safety control devices that are the targets of the commissioning work, and on the necessary components, such as the relevant FCS (Field Control Station).

[0018] A commissioning DB is created for each module yard. The created commissioning DB is sent to the module yard, where a commissioning system including the commissioning DB is constructed.

[0019] Next, in the module yard, commissioning work is carried out for each commissioning system. This work optimizes the DB for trial operation in the module yard. Then, based on the optimized DB for trial operation, the management DB for the development system is equalized.

[0020] For example, when the commissioning work changes the test run DB of the module yard, the management DB of the development system is equalized based on this test run DB. Also, when the management DB is changed, the test run DB of the module yard is equalized based on the management DB. The management DB can be changed, for example, by equalizing it with the test run DB of another module yard. Equalization is performed manually, for example, using a tool.

[0021] Next, at the site, a site DB required for starting up the site system is set up based on the management DB of the development system. Here, the site system is a system that executes processing and management within the actual plant, such as a system that performs SAT (Site Acceptance Test).

[0022] For example, when commissioning work is completed at one of multiple module yards, the management database of the development system is manually copied to the site database.

[0023] From then on, each time commissioning work is completed in the module yard, the trial operation DB is merged into the management DB of the development system. After merging, the management DB is verified. If the verification is successful, the management DB is merged into the site DB.

[0024] Commissioning work is also performed on site using the site DB. Commissioning work on site and commissioning work in the module yard are performed simultaneously (in parallel) for a certain period of time. During this time, equalization processing of the trial operation DB and management DB, verification processing of the management DB, and merging processing of the management DB and site DB are repeatedly performed.

[0025] In this way, a commissioning system is constructed for each module yard, so in conventional systems, the trial operation database is created manually, i.e., the management database is divided.

[0026] Furthermore, in conventional systems, the trial operation DB that has been changed in the module yard must be merged manually (or using a tool) into the management DB.

[0027] As described above, conventional systems require splitting and merging of the management DB (master database). Therefore, it is desirable to be able to perform commissioning work more efficiently.

[0028] Furthermore, this splitting and merging work is performed manually by a person in charge. Therefore, it is necessary to clearly define the detailed work procedures for the splitting and merging work. It is also necessary to clearly determine the person in charge of the work. If the commissioning work is carried out over a long period of time (for example, years), the person in charge of the work will also be assigned for a long period of time, which could increase the burden on the person in charge.

[0029] Furthermore, since this dividing and merging work is performed manually, there is a risk of operational errors occurring.

[0030] [1.2. Overview of proposed technology] Therefore, the database management system according to this embodiment connects a database device constructed in a virtual environment to a commissioning system and executes database management processing. This allows commissioning work to be performed in the database management system without dividing the management DB. The database device has a management DB that stores data used in the commissioning work.

[0031] 1 and 2 are diagrams for explaining an outline of a database management process according to an embodiment. The database management process shown in FIGS.

[0032] First, a schematic configuration of a database management system 1 will be described with reference to Fig. 1. As shown in Fig. 1, the database management system 1 includes a database device 10, control devices 20A and 20B, safety control devices 30A and 30B, management devices 40A and 40B, operation devices 50A and 50B, and information processing devices 104A, 104B, 105A, and 105B.

[0033] Here, a commissioning work is performed for each module yard in the database management system 1. In the commissioning work performed for each module yard, the control device 20, the safety control device 30, the management device 40, the operation device 50, etc. are used.

[0034] Hereinafter, these devices and commissioning work will be distinguished by module yard by adding an alphabetical letter after the reference numeral. Also, when it is not necessary to distinguish by module yard, the alphabetical letter will be omitted.

[0035] (Database device 10) The database device 10 stores data used for commissioning work (trial operation work) of a plant. For example, the database device 10 saves data used for commissioning work in a project (PJT) DB 121, which is a management DB (master database).

[0036] (Control device 20) The control device 20 is a controller that controls the plant. Here, the control device 20 controls the test operation of the module. Hereinafter, the control device 20 is also referred to as an FCS (Field Control Station) 20.

[0037] The control device 20 performs a trial run operation using the data stored in the database device 10. The control device 20 downloads the data stored in the database device 10 to the FCS_DB 221 and performs a trial run operation.

[0038] (Safety control device 30) The safety control device 30 is a controller (control device) that detects abnormalities during plant operation. Hereinafter, the safety control device 30 performs abnormality detection during test operation of a module. Hereinafter, the safety control device 30 will also be referred to as an SCS (Safety Control Station) 30.

[0039] The safety controller 30 performs a trial run operation using the data stored in the database device 10. The safety controller 30 downloads the data stored in the database device 10 to the SCS_DB 321 and performs a trial run operation.

[0040] (Management device 40) The management device 40 performs system construction and maintenance management of the plant system. Here, the management device 40 performs system construction of the module during test operation of the module. Hereinafter, the management device 40 is also referred to as an ENG (engineering system, or engineering terminal) 30.

[0041] The management device 40 stores the data changed by the commissioning work in the database device 10. In addition, the management device 40 downloads the data acquired from the database device 10 to the control device 20 and the safety control device 30.

[0042] (Operating device 50) The operation device 50 operates and monitors the plant. Hereinafter, the operation device 50 will also be referred to as an HIS (Human Interface Station) 50.

[0043] In the database management system 1 according to this embodiment, some devices are constructed in a virtual environment. For example, in the example of Fig. 1, the database device 10, ENG 40, and HIS 50 are constructed in the virtual environment. On the other hand, the FCS 20 and SCS 30 are placed in the commissioning office.

[0044] The commissioning office and the virtual environment are connected via a wide area network. That is, the FCS 20 and the SCS 30 are connected to the database device 10, the ENG 40, and the HIS 50, respectively, via the wide area network. The wide area network may be, for example, the Internet.

[0045] (Information processing devices 104, 105) The ENG 40 and the HIS 50 receive instructions from the user via information processing devices 104 and 105 located in the commissioning office. That is, the ENG 40 and the HIS 50 receive remote access from the commissioning office.

[0046] For example, the ENG 40 and the HIS 50 function as thin client-compatible server devices. The information processing devices 104 and 105 function as thin client terminals. Hereinafter, the information processing devices 104 and 105 are also referred to as PCs (Personal Computers) 104 and 105.

[0047] The database device 10, the ENG 40, the HIS 50, and the PCs 104 and 105 may be connected to one another via a general-purpose network (e.g., a public network). These devices may be connected using common communication standards such as Ethernet (registered trademark) and Wi-Fi (registered trademark). Such a public network may also be referred to as a PCN.

[0048] Meanwhile, the FCS20, SCS30, ENG40, and HIS50 can be connected to one another via a dedicated network (control bus). This dedicated network is an Ethernet-based real-time plant network for process automation. Hereinafter, this dedicated network will also be referred to as Vnet / IP.

[0049] The FCS 20, SCS 30, ENG 40, and HIS 50 are connected to a private network and a wide area network via a WAC route, which will be described later.

[0050] The system that performs the commissioning work is also referred to as the commissioning system (CS). Commissioning systems (CS) include the FCS20, SCS30, ENG40, HIS50, and PC104 and 105.

[0051] Next, we will explain the outline of the database management process executed by this database management system 1. Note that, although we will explain the outline of the database management process executed in the commissioning work C_A performed in the module yard M_A, the database management process is also executed in the commissioning work C_B performed in the module yard M_B in a similar manner.

[0052] 1, the FCS 20A and the SCS 30A download data to be used in the commissioning work C_A (step S1). The download is performed, for example, by an operator performing the commissioning work issuing an instruction to the database device 10 using a management device.

[0053] The database device 10 transmits data used in the commissioning work C_A to at least one of the FCS 20A and the SCS 30A in accordance with instructions from the worker. The worker, for example, accesses the ENG 40 from the PC 104 and instructs the database device 10 via the ENG 40 to transmit data.

[0054] The download is performed via the ENG 40 A. The downloaded data is stored in at least one of the FCS_DB 221 and the SCS_DB 321.

[0055] 2, when data is updated in the commissioning work C_A, the ENG 40A updates the data stored in the database device 10 (step S2). The update is performed, for example, by the worker performing the commissioning work issuing an instruction to the database device 10 using a management device.

[0056] The database device 10 updates the PJT_DB 121 using the data updated in the commissioning work C_A in accordance with instructions from the worker.

[0057] After updating the data, the database device 10 transmits the updated data to at least one of the FCS 20 and the SCS 30. When the data is updated in this manner, the FCS 20 and the SCS 30 download the updated data (step S3). The downloaded data is stored in at least one of the FCS_DB 221 and the SCS_DB 321.

[0058] As described above, data is updated and downloaded in the same manner for the commissioning work C_B. In this manner, in this embodiment, the database device 10 is constructed in a virtual environment and stores data used for the commissioning work C.

[0059] This allows the database device 10 to centrally manage data (master database) used for multiple commissioning works C. Therefore, the database management system 1 according to this embodiment does not need to divide and integrate data, and can execute the commissioning works C more efficiently.

[0060] This also eliminates the need to manually split and integrate the management DB (master database), and eliminates the need to assign a worker to perform the split and integration tasks, reducing the burden on the worker and reducing manual errors.

[0061] [2. System configuration example] [2.1. Example of overall system configuration] Fig. 3 is a diagram showing an example of the overall configuration of a database management system 1 according to an embodiment. Note that Fig. 3 appropriately illustrates components necessary for explaining this embodiment, and some components not necessary for the explanation may be omitted.

[0062] The database management system 1 includes a yard commissioning system YCS_1A constructed in a module yard M_A and a virtual commissioning system VCS_1A constructed in a virtual environment VM. The yard commissioning system YCS_1A and the virtual commissioning system VCS_1A function as one commissioning system CS_1A.

[0063] In addition to the yard commissioning system YCS_1A, multiple yard commissioning systems YCS_2A to YCS_4A are constructed in the module yard M_A. Also, virtual commissioning systems VCS_2A to VCS_4A corresponding to the multiple yard commissioning systems YCS_2A to YCS_4A, respectively, are constructed in the virtual environment VM.

[0064] In this way, a plurality of commissioning systems CS_1A to CS_4A corresponding to the module yard M_A are constructed.

[0065] (Virtual Commissioning System VCS_1A) The virtual commissioning system VCS_1A has a DCS_ENG40_1A, an ESD_SENG40_2A, an FGS_SENG40_3A, and an HIS50A.

[0066] DCS_ENG40_1A is an engineering terminal for the Distributed Control System. ESD_SENG40_2A is an engineering terminal for the emergency shutdown device. FGS_SENG40_3A is an engineering terminal for the fire protection and extinguishing equipment.

[0067] DCS_ENG40_1A, ESD_SENG40_2A, and FGS_SENG40_3A correspond to the above-mentioned ENG40A. The above-mentioned ENG40A may have all the functions of DCS_ENG40_1A, ESD_SENG40_2A, and FGS_SENG40_3A. Alternatively, the ENG40A may have at least one function of DCS_ENG40_1A, ESD_SENG40_2A, and FGS_SENG40_3A.

[0068] (Yard Commissioning System YCS_1A) The yard commissioning system YCS_1A includes a DCS_FCS20A, an ESD_SCS30_1A, an FGS_SCS30_2A, a DCS_PC104_1A, an ESD_PC104_2A, an FGS_PC104_3A, an HIS_PC105A, and a PRM60A.

[0069] The DCS_FCS20A is a controller that controls the distributed control system of the module. The DCS_FCS20A corresponds to the FCS20A described above. This DCS_FCS20A is the target of commissioning work by the commissioning system CS_1A. Hereinafter, the DCS_FCS20A that is the target of commissioning work will also be referred to as the target DCS_FCS20A.

[0070] The ESD_SCS30_1A is a controller that controls the emergency shutdown device. The ESD_SCS30_1A corresponds to the above-mentioned SCS30A. This ESD_SCS30_1A is the target of commissioning work by the commissioning system CS_1A. Hereinafter, the ESD_SCS30_1A that is the target of the commissioning work will also be referred to as the target ESD_SCS30_1A.

[0071] The FGS_SCS30_2A is a controller that controls the emergency shutdown device. The FGS_SCS30_2A corresponds to the above-mentioned SCS30A. This FGS_SCS30_2A is the target of commissioning work by the commissioning system CS_1A. Hereinafter, the FGS_SCS30_2A that is the target of the commissioning work will also be referred to as the target FGS_SCS30_2A.

[0072] DCS_PC104_1A is an information processing device used to remotely access DCS_ENG40_1 A. DCS_PC104_1A corresponds to the above-mentioned PC104A.

[0073] The ESD_PC 104_2A is an information processing device used to remotely access the ESD_SENG 40_2A, and corresponds to the PC 104A described above.

[0074] The FGS_PC 104_3A is an information processing device used to remotely access the FGS_SENG 40_3A. The FGS_PC 104_3A corresponds to the above-mentioned PC 104A.

[0075] The HIS_PC 105A is an information processing device used to remotely access the HIS 50A, and corresponds to the PC 105A described above.

[0076] The PRM 60A is a device for checking the connections of the field devices included in the module, and includes a database (not shown) for storing device information.

[0077] The device information held in this database is imported into the site system via plug-and-play. The master PRM_DB 70, described below, is primarily used to manage shared data. The data stored in the master PRM_DB 70 is manually equalized to the PRM 60A database as needed.

[0078] The DCS_ENG40_1A, ESD_SENG40_2A, FGS_SENG40_3A, and HIS50A of the virtual commissioning system VCS_1A and the DCS_FCS20A, ESD_SCS30_1A, FGS_SCS30_2A, and PRM60A of the yard commissioning system YCS_1A are connected using a dedicated network (control bus).

[0079] These devices are connected via network devices such as a gateway (not shown), a firewall (not shown), a switching hub (not shown), a router, etc. Here, a WAC (Wide Area Communication) router 81 and a WAC engineering terminal (not shown) manufactured by Yokogawa may be used as the router.

[0080] The WAC router 81 connects to dedicated networks and wide area networks, and prioritizes data according to the type of communication data and the device with which it communicates. This allows the WAC router 81 to optimize the amount of communication data. In addition to redundant communication modules, the WAC router 81 also doubles communication lines to ensure system reliability.

[0081] In this way, by using the WAC router 81 that allows highly reliable and secure communication, a more reliable and secure dedicated network (control bus) can be constructed.

[0082] This control bus is a dedicated network for connecting devices included in the commissioning system CS_1A and is different from general networks. For example, signals (Vnet / IP communication packets) in a format specific to the commissioning system CS_1A are sent and received on the control bus.

[0083] The commissioning systems CS_2A to CS_4A have the same configuration as the commissioning system CS_1A, and therefore the description thereof will be omitted here.

[0084] In addition, although it has been described here that four commissioning systems CS_A corresponding to the module yard M_A are constructed, the number of commissioning systems CS_A to be constructed is not limited to four. The number of commissioning systems CS_A to be constructed may be three or less, or five or more.

[0085] There may also be multiple module yards M where modules are constructed. In the example of FIG. 3, module construction and commissioning work are carried out in three module yards M_A to M_C. As with module yard M_A, one or more commissioning systems CS_B and CS_C are constructed in module yards M_B and M_C. The number of module yards M is not limited to three, and may be two or less, or four or more.

[0086] (Commissioning system CS_S to be constructed at site S) Also, at the site S where the plant will finally be constructed, commissioning work is carried out on the modules transferred from the module yard M. The commissioning system CS_S constructed at the site S includes a virtual commissioning system VCS_S and a site commissioning system SC_S.

[0087] The virtual commissioning system VCS_S includes a DCS_ENG40_1S, an ESD_SENG40_2S, an FGS_SENG40_3S, and an HIS50S. The site commissioning system SC_S includes a DCS_FCS20S, an ESD_SCS30_1S, an FGS_SCS30_2S, a DCS_PC104_1S, an ESD_PC104_2S, an FGS_PC104_3S, an HIS_PC105S, and a PRM60S.

[0088] The configuration of the commissioning system CS_S constructed at the site S is the same as that of the commissioning system CS_1A constructed at the module yard M_A, and therefore a description thereof will be omitted.

[0089] (Database device 10) The database device 10 is arranged in a virtual environment. The database device 10 may be a database server arranged in a cloud. As described above, the database device 10 stores data used in the commissioning work.

[0090] (Master PRM_DB70) The master PRM_DB 70 is a database device that stores data used by the PRM 60. As described above, the master PRM_DB 70 mainly stores shared data for the PRM 60. The data stored in the master PRM_DB 70 is manually equalized to the database of the PRM 60A as necessary.

[0091] The database device 10, master PRM_DB70, DCS_ENG40_1A, 40_1S, ESD_SENG40_2A, 40_2S, FGS_SENG40_3A, 40_3S, and HIS50A, 50S located in the virtual environment and DCS_PC104_1A, 104_1S, ESD_PC104_2A, 104_2S, FGS_PC104_3A, 104_3S, HIS50A, 50S, and PRM60A, 60S located in the module yard M_A and site S are connected via a general-purpose network.

[0092] These devices are connected via network devices such as a gateway (not shown), a firewall (not shown), a switching hub (not shown), and a router (not shown). General-purpose networks are networks used for general communications, such as the Internet, a LAN (Local Area Network), and a WAN (Wide Area Network). For example, in general-purpose networks, communications are performed based on standards such as Ethernet.

[0093] The database device 10, the master PRM DB 70, the DCS ENGs 40_1A and 40_1S, the ESD ENGs 40_2A and 40_2S, the FGS ENGs 40_3A and 40_3S, and the HISs 50A and 50S may be physically located in the same place (a remote office). Alternatively, these devices may be physically distributed. This remote office may be, for example, a location different from the module yard M or the site S.

[0094] The devices located in the remote offices and the devices located in the module yard M and site S are connected via a wide area network.

[0095] The database management system 1 may include devices other than those described above. For example, the database management system 1 may include a backup database device or the like.

[0096] [2.2. Database device configuration example] 4 is a block diagram showing an example of the configuration of the database device 10 according to the embodiment. The database device 10 includes a communication unit 11, a storage unit 12, and a control unit 13.

[0097] (Communications Department 11) The communication unit 11 is a processing unit that communicates with other devices, and is realized by, for example, a communication interface, etc. For example, the communication unit 11 communicates with the ENG 40.

[0098] (Storage unit 12) The storage unit 12 is a processing unit that stores various data and various programs executed by the control unit 13. The storage unit 12 is realized by, for example, a memory, a hard disk, etc. The storage unit 12 has a PJT_DB 121. The PJT_DB 121 is a database that stores data used in commissioning work.

[0099] (Control unit 13) The control unit 13 controls the entire database device 10. The control unit 13 has a data transmission unit 131 and a data update unit 132. Here, the control unit 13 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).

[0100] (Data transmission unit 131) The data transmission unit 131 transmits the data stored in the PJT_DB 121 to at least one of the FCS 20 and the SCS 30 via the ENG 40 .

[0101] The range of data that the ENG 40 can access is determined for each module yard M (or each commissioning system CS). That is, access restrictions to the PJT_DB 121 are set for each commissioning system CS.

[0102] Therefore, the data transmission unit 131 transmits data within a range corresponding to the commissioning system CS to at least one of the FCS20 and the SCS30.

[0103] The data transmission unit 131 may transmit all of the data within the range corresponding to the commissioning system CS in one batch to at least one of the FCS 20 and the SCS 30. Alternatively, the data transmission unit 131 may transmit differential data resulting from data updates to at least one of the FCS 20 and the SCS 30. By having the data transmission unit 131 transmit the differential data, the time required for downloading can be shortened.

[0104] (Data update unit 132) The data update unit 132 updates the data stored in the PJT_DB 121 in response to a request from the ENG 40. The data update unit 132 updates the data in the PJT_DB 121 by adding new data and changing data already stored therein.

[0105] [2.3. Example of management device configuration] 5 is a block diagram showing an example of the configuration of a management device (ENG 40) according to the embodiment. The ENG 40 includes a communication unit 41, a storage unit 42, and a control unit 43.

[0106] (Communications Department 41) The communication unit 41 is a processing unit that communicates with other devices, and is realized by, for example, a communication interface, etc. For example, the communication unit 41 communicates with the database device 10, the PC 104, the FCS 20, and the SCS 30.

[0107] Here, the communication unit 41 may include a first communication unit for connecting to a general-purpose network and a second communication unit for connecting to a dedicated network. In this way, the ENG 40 may include communication units according to the network to be connected.

[0108] (Storage unit 42) The storage unit 42 is a processing unit that stores various data and various programs executed by the control unit 43. The storage unit 42 is realized by, for example, a memory, a hard disk, and the like.

[0109] (Control unit 43) The control unit 43 controls the entire ENG 40. The control unit 43 has an acquisition request unit 431 and an update request unit 432. Here, the control unit 43 can be realized by, for example, an electronic circuit such as a CPU or an MPU, or an integrated circuit such as an ASIC or an FPGA.

[0110] (Acquisition request unit 431) The acquisition request unit 431 requests the database device 10 to acquire data to be used for the commissioning work. The acquisition request unit 431 requests the database device 10 to transmit the data to at least one of the FCS 20 and the SCS 30.

[0111] (Update request section 432) The update request unit 432 requests the database device 10 to update the PJT_DB 121 in accordance with changes that have occurred in the commissioning work. For example, the update request unit 432 directly reflects the changes that have occurred in the commissioning work (for example, the range and sequence operation of the equipment) in the PJT_DB 121.

[0112] If data is automatically downloaded when the PJT_DB121 is updated, the data acquisition request by the acquisition request unit 431 may be omitted. In this case, when a data update request is made by the update request unit 432, the database device 10 updates the PJT_DB121 and transmits the updated data to at least one of the FCS20 and the SCS30.

[0113] [2.4. Example of configuration of information processing device] 6 is a block diagram showing an example of the configuration of an information processing device 100 according to an embodiment. The information processing device 100 functions as PCs 104 and 105. The information processing device 100 includes a communication unit 110, a storage unit 120, a control unit 130, and an input / output unit 140.

[0114] (Communication unit 110) The communication unit 110 is a processing unit that communicates with other devices, and is realized by, for example, a communication interface, etc. For example, the communication unit 110 communicates with the ENG 40 or the HIS 50.

[0115] (Storage unit 120) The storage unit 120 is a processing unit that stores various data and various programs executed by the control unit 130. The storage unit 120 is realized by, for example, a memory, a hard disk, and the like.

[0116] (control unit 130) The control unit 130 controls the entire information processing device 100. The control unit 130 can be realized by, for example, an electronic circuit such as a CPU or an MPU, or an integrated circuit such as an ASIC or an FPGA.

[0117] (I / O section 140) The input / output unit 140 accepts input of various information to the information processing device 100. The input / output unit 140 is, for example, a mouse and a keyboard. The input / output unit 140 outputs various information. The input / output unit 140 is, for example, a display and a speaker, and outputs abnormal values ​​in the plant, system errors, etc.

[0118] The information processing device 100 transmits input received from the worker via the input / output unit 140 to the ENG 40 or the HIS 50 constructed in the virtual environment. This allows the worker to operate the ENG 40 or the HIS 50 via the information processing device 100.

[0119] [3. Database management processing] FIG. 7 is a sequence diagram showing an example of the flow of a database management process according to the embodiment.

[0120] First, before the commissioning work is performed, the ENG 40 transmits a data acquisition request to the database device 10 (step S101). For example, the ENG 40 transmits the data acquisition request by receiving an instruction from a worker via the PC 104.

[0121] The database device 10 that has received the data acquisition request transmits the data to the ENG 40 (step S102). The database device 10 transmits to the ENG 40 the data that the commissioning system CS to which the ENG 40 belongs has access authority.

[0122] Upon receiving the data, the ENG 40 downloads the received data to the FCS 20 (step S103). The ENG 40 can download the received data to the FCS 20 by repeatedly transmitting short packets. Alternatively, the ENG 40 may transmit the received data in a batch. By transmitting the data in a batch, the download time can be shortened. The FCS 20 stores the received data in the FCS_DB 221.

[0123] Next, the ENG 40 and the FCS 20 perform the commissioning work (step S104).

[0124] The ENG 40 transmits a data update request to the database device 10 (step S105). The ENG 40 notifies the database device 10 to update the PJT_DB 121 based on the changes that have occurred as a result of this commissioning work.

[0125] Upon receiving the update request, the database device 10 updates the PJT_DB 121 in accordance with the notification from the ENG 40 (step S106).

[0126] This allows the ENG 40 to directly reflect changes (such as device ranges and sequence operations) that occur during commissioning work in the PJT_DB 121.

[0127] A worker performing commissioning work in the module yard M remotely accesses the ENG 40 via the PC 104. In response to this, the ENG 40 transmits an update request to the database device 10 in accordance with instructions from the worker.

[0128] After updating the data, the database device 10 transmits the updated data to the ENG 40 (step S107). Upon receiving the updated data, the ENG 40 transfers the updated data to the FCS 20 (step S108).

[0129] Although the case where the FCS_DB 221 of the FCS 20 is created and updated has been described here, the SCS_DB 321 of the SCS 30 is created and updated in the same manner.

[0130] Furthermore, updates to the PJT_DB 121 and the FCS_DB 221 can be performed each time during the commissioning process.

[0131] Furthermore, when the shared data held by the PJT_DB121, i.e., the data common to multiple module yards M and sites S, is updated, the database device 10 may transmit the updated shared data to the ENG40 of each module yard M and site S. In this case, the ENG40 transfers the updated shared data to the FCS_DB221 and updates the FCS_DB221.

[0132] Alternatively, the database device 10 may notify the ENG 40 of each module yard M and site S that the shared data in the PJT_DB 121 has been updated. Upon receiving the notification, the ENG 40 determines whether or not to download the updated shared data, and downloads the updated shared data to the FCS_DB 221 according to the determination result. For example, the ENG 40 determines whether or not to download the updated shared data in accordance with an instruction from a worker.

[0133] As described above, the database management system 1 according to this embodiment allows a plurality of commissioning systems CS and sites S to share the PJT_DB121, thereby enabling centralized management of the PJT_DB121.

[0134] Furthermore, the database management system 1 according to this embodiment updates the PJT_DB 121 using the ENG 40. After the PJT_DB 121 is updated, the updated data is downloaded.

[0135] In the database management system 1 according to this embodiment, the database device 10 and the ENG 40 are connected to the FCS 20 and the SCS 30 via a wide area network.

[0136] As a result, the database management system 1 according to this embodiment can build a system that utilizes a wide area network and can follow modular construction methods for plant construction while reducing manual work errors by workers.

[0137] Furthermore, the ENG 40 is connected to the FCS 20 and SCS 30 via a WAC router 81. This allows for highly reliable and secure communications to be achieved between the ENG 40 and the FCS 20 and SCS 30, even though the wide area network is used.

[0138] Furthermore, in the database management system 1 according to this embodiment, the commissioning work at the site S is carried out in parallel with the commissioning work at the module yard M.

[0139] Furthermore, the ENG 40 is connected to the FCS 20 and SCS 30 via a dedicated control bus, which allows the FCS 20 and SCS 30 to download programs generated by the ENG 40 more reliably and at higher speeds.

[0140] As described above, in this embodiment, the ENG40 placed in the virtual environment VM generates a program to operate at least one of the FCS20 and SCS30 deployed on the module yard M located in distant locations, such as multiple countries.

[0141] The ENG40 downloads the program generated in this virtual environment VM to the FCS20 or SCS30 via a dedicated control bus using the WAC router 81. This allows the database management system 1 to reflect the program in the FCS20 or SCS30 more reliably and more quickly.

[0142] This allows the database management system 1 to reduce the impact that the commissioning work at the module yard M has on the schedule for the commissioning work at the site S.

[0143] [4. 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.

[0144] Furthermore, the components of each device shown in the figure are functional concepts and do not necessarily have to be physically configured as shown. In other words, the specific form of distribution and integration of each device is not limited to that shown. In other words, all or part of them can be functionally or physically distributed and integrated in any unit depending on various loads, usage conditions, etc.

[0145] Furthermore, all or any part of the processing functions performed by each device may be realized by a CPU and a program analyzed and executed by the CPU, or may be realized as hardware using wired logic.

[0146] [5. Hardware] Next, an example of the hardware configuration of the database device 10 will be described. Fig. 8 is a diagram illustrating an example of the hardware configuration of the database device 10. As shown in Fig. 8, the database device 10 has a communication device 10a, an HDD (Hard Disk Drive) 10b, a memory 10c, and a processor 10d. The components shown in Fig. 8 are connected to each other via a bus or the like.

[0147] The communication device 10a is a network interface card or the like, and communicates with other servers. The HDD 10b stores programs and DBs that operate the functions shown in FIG.

[0148] The processor 10d reads out a program that executes the same processes as the respective processing units shown in Fig. 4 from the HDD 10b or the like and loads it into the memory 10c, thereby operating a process that executes the respective functions described in Fig. 4 or the like. For example, this process executes the same functions as the respective processing units of the database device 10. Specifically, the processor 10d reads out a program having the same functions as the data transmission unit 131, the data update unit 132, or the like from the HDD 10b or the like. Then, the processor 10d executes a process that executes the same processes as the data transmission unit 131, the data update unit 132, or the like.

[0149] In this way, the database device 10 operates as a device that executes various processing methods by reading and executing a program. The database device 10 can also realize functions similar to those of the above-described embodiment by reading the program from a recording medium using a media reader and executing the read program. Note that the program in these other embodiments is not limited to being executed by the database device 10. For example, the present invention can also be applied in the same way to cases where another computer or server executes the program, or where these execute the program in cooperation with each other.

[0150] This program can be distributed via a network such as the Internet. In addition, this program can 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 from the recording medium by a computer.

[0151] Although an example of the hardware configuration of the database device 10 has been described here, the ENG 40, the HIS 50, the information processing device 100, etc. can also be realized with a similar hardware configuration.

[0152] [6. Other] Some examples of combinations of the disclosed technical features are set out below. (1) a database device that stores data related to the settings of each device included in the plant; a control device used to control a test run of a plant module that is at least a part of the plant, and disposed in a module yard where the test run is performed; a management device that performs system construction and maintenance management of the plant module; Equipped with The management device storing the data changed by the test run in the database device; downloading the data to be used in the test run from the database device via a wide area network; Management system. (2) the control device and the management device are connected via the wide area network, The data is downloaded to the control device via the management device. (1) The management system described in (1). (3) the control device and the management device are connected via a dedicated network; the database device and the management device are connected via a general-purpose network; (2) The management system described in (2). (4) The control device is a device that performs plant control of the plant module, or a device that detects an abnormality when an abnormality occurs in the plant module, according to any one of (1) to (3). (5) a second control device used to control a second test run of a second plant module different from the plant module and disposed in a second module yard where the second test run is performed; a second management device that performs second system construction and second maintenance management of the second plant module; Furthermore, The second management device storing the data changed by the second test run in the database device; downloading the data to be used in the second test run from the database device via the wide area network; The management system according to any one of (1) to (4). (6) further comprising an operating device for operating and monitoring the plant module; The operation device is connected to the control device via the wide area network. The management system according to any one of (1) to (5). (7) the control device, the management device, and the operation device are connected via a dedicated network; the database device, the management device, the operation device, and the information processing device are connected via a general-purpose network; the information processing device accesses at least one of the management device and the operation device via the general-purpose network; (6) The management system described in (6). (8) a database device that stores data related to the settings of each device included in the plant; a control device used to control a test run of a plant module that is at least a part of the plant, and disposed in a module yard where the test run is performed; a management device that performs system construction and maintenance management of the plant module; A management method by a management system comprising: the management device stores the data changed by the test run in the database device; The management device downloads the data to be used for the test run from the database device via a wide area network; Management methods including. [Explanation of symbols]

[0153] 1 Database Management System 10 Database equipment 11,41,110 Communications Department 12,42,120 storage section 13,43,130 Control section 20 Control device 30 Safety control device 40 Management device 50 Operating device 131 Data transmission unit 132 Data Update Section 140 Input / output section 431 Acquisition request section 432 Update request section

Claims

1. a database device that stores data related to the settings of each device included in the plant; a control device used to control a test run of a plant module that is at least a part of the plant, and disposed in a module yard where the test run is performed; a management device that performs system construction and maintenance management of the plant module; Equipped with The management device storing the data changed by the test run in the database device; downloading the data to be used in the test run from the database device to the control device via a wide area network; the database device is connected to the wide area network via a router; Management system.

2. the control device and the management device are connected via the wide area network, The data is downloaded to the control device via the management device. The management system according to claim 1 .

3. the control device and the management device are connected via a dedicated network; the database device and the management device are connected via a general-purpose network; The management system according to claim 2 .

4. The management system according to claim 1 , wherein the control device is a device that performs plant control of the plant module, or a device that detects an abnormality when the abnormality occurs in the plant module.

5. a second control device used to control a second test run of a second plant module different from the plant module, and disposed in a second module yard where the second test run is performed; a second management device that performs second system construction and second maintenance management of the second plant module; Furthermore, the second management device stores the data changed by the second test run in the database device; The second management device downloads the data to be used for the second test run from the database device to the second control device via the wide area network. The management system according to claim 1 .

6. further comprising an operating device for operating and monitoring the plant module; The operation device is connected to the control device via the wide area network. The management system according to claim 1 .

7. the control device, the management device, and the operation device are connected via a dedicated network; the database device, the management device, the operation device, and the information processing device are connected via a general-purpose network; the information processing device accesses at least one of the management device and the operation device via the general-purpose network; The management system according to claim 6.

8. The management system described in claim 1, wherein the database device is placed in a virtual environment.

9. a database device that stores data related to the settings of each device included in the plant; a control device used to control a test run of a plant module that is at least a part of the plant, and disposed in a module yard where the test run is performed; a management device that performs system construction and maintenance management of the plant module; A management method by a management system comprising: the management device stores the data changed by the test run in the database device; The management device downloads the data to be used for the test run from the database device to the control device via a wide area network; said database device is connected to said wide area network via a router; Management methods including.

Citation Information

Patent Citations

  • Field bus system

    JP2005158026A

  • Management system

    JP2006059045A

  • Industrial apparatus control system

    JP2013105301A

  • Maintenance evaluation system

    JP2015203966A

  • Improved test manager for industrial automation control apparatus

    JP2018067282A