Tool for configuring and managing a process control network including the use of spatial information
24 claims: 16 independent, 8 dependent
- 1プロセッサ及びメモリを有するコンピュータを備えたプロセス制御ネットワークを設定及び管理する方法において、 前記コンピュータが 、 プロセス制御ネットワーク に関連した情報 を含む施設の空間レイアウトに関する情報を受信するステップと、 前記コンピュータが、前記プロセス制御ネットワーク内の複数のデバイスの設定に関する情報を受信するステップと、 前記コンピュータが、前記複数のデバイスを制御する ための 複数の機能ブロックを生成して作動させるステップと、 前記コンピュータが、選択された標準プロトコルの要求への適合のために前記プロセス制御ネットワークの前記設定をチェックするステップと、 前記コンピュータが、前記複数のデバイスの状態を得るステップと、 前記コンピュータが、前記施設の空間レイアウトに関して前記複数のデバイスの状態を提示するステップと、 を有 し、 前記プロセス制御ネットワークのレイアウトは前記コンピュータにより自動的に生成され ることを特徴とするプロセス制御ネットワークを設定及び管理する方法。
- 2前記設定をチェックするステップは、前記コンピュータが、前記プロセス制御ネットワークのレイアウトが前記選択された標準プロトコルの判定基準に従うことを確認すべく、前記施設の物理的なレイアウトに関して前記プロセス制御ネットワークのレイアウトを解析することを含むことを特徴とする請求項1記載のプロセス制御ネットワークを設定及び管理する方法。
- 3前記コンピュータがランタイム環境において前記プロセス制御ネットワークを管理するステップを更に有することを特徴とする請求項1記載のプロセス制御ネットワークを設定及び管理する方法。
- 4前記プロセス制御ネットワークを管理するステップは、作動警報を示すために、前記プロセス制御ネットワークの空間表示における点滅デバイス表現を提供することを含むことを特徴とする請求項3記載のプロセス制御ネットワークを設定及び管理する方法。
- 5前記プロセス制御ネットワークを管理するステップは、前記複数のデバイスのマスター・リセット又は自己テストを開始することを含むことを特徴とする請求項3記載のプロセス制御ネットワークを設定及び管理する方法。
- 6前記プロセス制御ネットワークを管理するステップは、前記プロセス制御ネットワークのポート及び通信の統計を得ることを含むことを特徴とする請求項3記載のプロセス制御ネットワークを設定及び管理する方法。
- 7前記施設の空間レイアウトは三次元のレイアウトであることを特徴とする請求項3記載のプロセス制御ネットワークを設定及び管理する方法。
- 8前記標準プロコトルはフィールドバス・プロコトルであることを特徴とする請求項2記載のプロセス制御ネットワークを設定及び管理する方法。
- 9前記プロセス制御ネットワークのレイアウトを解析するステップは、前記プロセス制御ネットワークのセグメントの支線の長さをチェックすることを含むことを特徴とする請求項2記載のプロセス制御ネットワークを設定及び管理する方法。
- 10プロセス制御ネットワークを設定及び管理する装置において、 プロセッサ及びメモリを有するコンピュータと、 前記コンピュータに、施設の空間レイアウトに関する情報を提供する手段と、 前記コンピュータに、前記プロセス制御ネットワーク内で使用される複数のデバイスの設定に関する情報を提供する手段と、 前記複数のデバイスを制御する複数の機能ブロックを生成して作動させる手段と、 選択された標準プロトコルの要求への適合のために前記プロセス制御ネットワークの前記設定をチェックする手段と、 前記複数のデバイスの状態を得る手段と、 前記施設の空間レイアウトに関して前記複数のデバイスの状態を提示する手段と、 前記施設の空間レイアウトに適用される前記プロセス制御ネットワークのレイアウトを提供するために使用されるツールと、 を備え 、 前記プロセス制御ネットワークのレイアウトを提供するために使用される前記ツールは前記プロセス制御ネットワークレイアウトを自動的に生成するツールを更に含む ことを特徴とするプロセス制御ネットワークを設定及び管理する装置。
- 11前記プロセス制御ネットワークで使用される物品に関する情報を前記コンピュータに提供する手段を更に備えることを特徴とする請求項 10 記載のプロセス制御ネットワークを設定及び管理する装置。
- 12前記設定をチェックすることは、前記ツールを、前記プロセス制御ネットワークのレイアウトが前記選択された標準プロコトルの判定基準に従うことを確認すべく、前記施設の空間レイアウトに適用される前記プロセス制御ネットワークのレイアウトを解析するために使用することを特徴とする請求項 10 記載のプロセス制御ネットワークを設定及び管理する装置。
- 13前記ツールは、ランタイム環境において前記プロセス制御ネットワークを管理するために使用されることを特徴とする請求項 10 記載のプロセス制御ネットワークを設定及び管理する装置。
- 14前記プロセス制御ネットワークを管理するために使用される前記ツールは、作動警報を示すために、前記プロセス制御ネットワークの空間表示における点滅デバイス表現を提供することを含むことを特徴とする請求項 10 記載のプロセス制御ネットワークを設定及び管理する装置。
- 15前記プロセス制御ネットワークを管理することは、前記プロセス制御ネットワークのポート及び通信の統計を得ることを含むことを特徴とする請求項 10 記載のプロセス制御ネットワークを設定及び管理する装置。
- 16前記施設の空間レイアウトは3次元のレイアウトであることを特徴とする請求項 10 記載のプロセス制御ネットワークを設定及び管理する装置。
- 17前記標準プロコトルはフィールドバス・プロコトルであることを特徴とする請求項 12 記載のプロセス制御ネットワークを設定及び管理する装置。
- 18プロセッサ、ディスプレイ及びメモリを有するコンピュータを含むプロセス制御ネットワークと、複数の設備とを備えるプロセスプラントを管理する方法において、 前記コンピュータが、前記メモリに、前記複数の設備の空間レイアウトに関する情報を格納するステップと、 前記コンピュータが、前記メモリに、前記プロセス制御ネットワークに関連する複数のデバイスの設定に関する情報を格納するステップと、 前記コンピュータが、前記メモリに、前記複数のデバイスを制御するよう構成された複数の機能ブロックを格納するステップと、 前記コンピュータが、選択された標準プロトコルの要求への適合のために前記プロセス制御ネットワークの前記設定をチェックするステップと、 前記コンピュータが、前記ディスプレイ上に前記複数の設備の空間レイアウトを提示するステップと、 前記コンピュータが、前記ディスプレイ上に前記複数の設備の空間レイアウトに関する前記複数の機能ブロックを提示するステップと、 前記コンピュータが、前記プロセス制御ネットワークに関連する前記複数のデバイスからプロセス情報を得るステップと、 前記コンピュータが、前記ディスプレイ上に前記複数の機能ブロックに関する前記プロセス情報を提示するステップと、 を有 し、 前記複数のデバイスからプロセス情報を得るステップは、前記複数のデバイスに関連するプロセスシミュレーション情報を得ることを更に有 することを特徴とするプロセスプラントを管理する方法。
- 19前記複数の設備の空間レイアウトを提示するステップは、3次元グラフィックスにおいて前記複数の設備の空間レイアウトを提示することを更に有することを特徴とする請求項 18 記載のプロセスプラントを管理する方法。
- 20更に、前記コンピュータが、前記複数の機能ブロックの少なくとも一つに関連するパラメータの値を変更することをユーザに許容するステップと、 前記コンピュータが、前記変更されたパラメータの値に関してプロセスシミュレーション情報を生成するステップと、 前記コンピュータが、前記複数の設備の空間レイアウトに関して前記プロセスシミュレーション情報を提示するステップと、 を有することを特徴とする請求項 18 記載のプロセスプラントを管理する方法。
- 21更に、前記コンピュータが、前記複数のデバイスのパフォーマンスを監視するステップと、 前記コンピュータが、前記複数のデバイスのパフォーマンスに関連してパフォーマンスの統計を生成するステップと、 前記コンピュータが、前記複数の設備の空間レイアウトに関して前記パフォーマンスの統計を提示するステップと、 を有することを特徴とする請求項 18 記載のプロセスプラントを管理する方法。
- 22更に、前記複数の設備の空間レイアウトに関し、前記コンピュータが、複数のプロセスブロックを含むプロセスシミュレーションを提供するステップと、 前記コンピュータが、前記複数のプロセスブロックの各々を複数のプロセスグラフィックエレメントの少なくとも一つに関連付けるステップと、 を有することを特徴とする請求項 18 記載のプロセスプラントを管理する方法。
- 23プロセス制御ネットワーク及び複数の設備を備えるプロセスプラントを管理するシステムであって、 複数のプロセス制御デバイスと、前記複数のプロセス制御デバイスに通信可能に接続されたコンピュータとを有し、 該コンピュータが、プロセッサと、ディスプレイと、メモリとを備え、該メモリには、 前記複数の設備の空間レイアウトに関する情報と、 前記プロセス制御ネットワークに関連する前記複数のプロセス制御デバイスの設定に関する情報と、 前記複数のプロセス制御デバイスを制御するよう構成された複数の機能ブロックと、 前記プロセッサ上で動作されるよう構成されたコンピュータプログラムコードと、が格納されるようになっており、 該コンピュータプログラムコードは、選択された標準プロトコルの要求への適合のために前記プロセス制御ネットワークの前記設定をチェックし、前記ディスプレイ上で前記複数の設備の空間レイアウトを提示し、前記複数の設備の空間レイアウトに関して前記複数の機能ブロックを提示 し、前記複数のプロセス制御デバイスに関するプロセスシミュレーション情報を提供 するよう構成されていることを特徴とするプロセスプラントを管理するシステム。
- 24前記コンピュータプログラムコードは、更に、前記複数のデバイスからプロセス情報を得るよう構成され、かつ、前記複数の機能ブロックに関して前記プロセス情報を提示するよう構成されていることを特徴とする請求項 23 記載のプロセスプラントを管理するシステム。
Independent claims24
50 paragraphs, as filed
The present invention generally relates to process control networks, and in particular to methods and devices for setting up and managing process control networks.
Large processes such as chemical, petroleum, and other manufacturing and refining processes have a large number of locations located within the facility to measure and control process parameters and thereby affect process control. Has a field device. These devices are, for example, sensors such as temperature, pressure, and flow rate sensors, as well as control elements such as valves and switches. Historically, the process control industry has used manual operations such as manually reading level and pressure gauges, turning valves, wheels, etc. to operate measurement and control field devices within the process. It was.
Nowadays, process control, as a whole, is a microprocessor that monitors a process by sending and receiving instructions and data between hardware devices to control either a specific process or the entire process. Often implemented using a base controller, computer, or workstation. Certain process control functions performed by software programs on these microprocessors, computers, or workstations are individually designed, modified, or modified through programming without the need for hardware modifications. For example, the engineer reads the fluid level from the level sensor in the tank, compares the tank level to the desired predetermined level, and the read level is the required predetermined level in the program to be written. Have the controller open and close the supply valve based on whether it is lower or higher. The parameters are easily changed by displaying the selected screen of the process and by modifying the program using the selected screen. The engineer mainly changes the parameters by displaying and modifying the process engineer's screen.
A controller, computer, or workstation stores and executes centralized, often complex control methods to affect the measurement and control of process parameters with respect to the overall control method. However, the control methods that are usually performed are proprietary to the manufacturer of the field device, thus making the extension, upgrade, reprogramming, and / or service of the process control system difficult and expensive. This is because the provider of the field device must be involved in the essential methods for performing any of these actions. In addition, equipment that can be used or interconnected is in a situation where the provider does not support the functionality of some devices or devices manufactured by other manufacturers due to the uniquely developed nature of the field devices. Can also be limited by.
To overcome some of the problems inherent in the use of proprietary field devices, the process control industry has, for example, HART®, DE, PROFIBUS®, WORLD FIP®, He has developed a number of standard open communication protocols, including LONWORKS®, Device-Net, and CAN protocols. These standard protocols enable field devices manufactured by different manufacturers that should be used together within the same process control environment. In theory, any field device that follows one of these protocols could be with a process control system or other controller that supports the protocol, even if the field device is manufactured by a different manufacturer. It can communicate and be used within a process to be controlled by the process control system or other controller.
To perform control functions, each process control device had the ability to perform one or more basic control functions, as well as the ability to communicate with other process control devices that use standard open protocols. It has a microprocessor. In this way, field devices manufactured by different manufacturers can be interconnected within a process control loop to communicate with each other and perform one or more process control functions or control loops. Another example of an open communication protocol that allows devices manufactured by different manufacturers to interact and communicate with each other via a standard bus that acts on distributed control within a process is the FOUNDATION Fieldbus Protocol by FOUNDATION Fieldbus (Fieldbus Protocol. "). The Fieldbus protocol is an all-digital, two-wire loop protocol.
<p> When using these protocols, the issues associated with designing process control systems or networks relate to the actual physical layout and interconnection of various process control devices. In particular, each of these protocols describes value constraints due to the physical characteristics that the process control system must operate in order to comply with the standards. These constraints include voltage drop across the communication section, branch line length, overall cable length, overall current draw, and total number of process control devices for a particular hub. As with controllers and operator stations, the physical locations of vessels, pipes, pumps, motors, and valves describe constraints that must be taken into account when configuring process control systems or networks. The interrelationship of these constraints is important and valuable, depending on the value of the constraint. Managing the system can be cumbersome due to the complexity of most purification and manufacturing facilities.</p><p> In addition to executing the control process, the software program also monitors and displays the display of the process and provides feedback in the form of an operator display or a display relating to the state of a particular process. Also, when a problem occurs, the monitoring software program issues an alarm. When a problem occurs, some programs display instructions or suggestions to the operator. The operator responsible for the control process needs to look at the process from his point of view and quickly correct the problem. The display or console is between a controller or computer-based microprocessor that performs process control functions and an operator, and between a programmer or engineer and a controller or computer-based microprocessor that performs process control functions. Mainly provided as an interface.</p><p> Systems that perform, monitor, control, and feed back functions in a process control environment are primarily implemented by software written in a high-level computer programming language such as Basic, Fortran, or C, on a computer or controller. Will be executed. Although these high-level languages are effective for process control programming, they are usually not used or understood by process engineers, maintenance engineers, control engineers, operators, and supervisors. Higher level graphical display languages such as continuous function blocks and ladder logic have been developed for such workers. Thus, engineers, maintenance workers, operators, lab workers, etc. each need a graphical representation of the elements of the process control system that allow them to see the system associated with their responsibilities. ..</p><p> A graphical representation of the elements of the process control system is provided without interrelationship to the spatial layout of the facility and only shows the logical connection of devices and functions. For example, a process control program, written in Fortran, may request two inputs, calculate the average of those inputs, and produce an output value equal to the average of the two inputs. This program may be referred to as the "average" function and may be called and referenced through a graphical display for the control engineer. A typical graphical display can consist of two inputs, one output, and a rectangular block with a label indicating "average". Different programs can be used to generate a graphical representation of this same function for the operator to display the mean. Before the system is delivered to the customer, these software programs are placed in a library of predefined user-selectable features. The program is identified by a functional block. The user then calls a function, for example, one of several functional blocks from a library used to logically define a process control solution rather than having to develop an entirely new program in Fortran. By selecting one, it is possible to select a predefined graphical representation represented by a rectangular box to generate different displays for operators, engineers, etc.</p><p> A standardized set of functions, each of which is represented by a related function block, can be stored in the control library. Designers with such libraries choose process control solutions by logically interconnecting on the display screen of a computer, a variety of functional blocks represented by rectangular boxes to perform a particular task. Functions or elements can be designed. The microprocessor or computer associates each of the functions or elements defined by the functional blocks with a predefined template stored in the library, and each of the program functions or elements is associated with each other according to the interconnection desired by the designer. To relate to. The designer designs the entire process control program using a logical representation of the predefined functions, without even correlating the design to the dimensions of the space of the refinery or manufacturing facility.</p><p> One problem with the graphical display provided is that only logical connections are shown. Currently, the physical layout of the facility does not correlate with the settings of the process control system and cannot be referenced while managing the system. When setting up a process control system, spatial information must be measured and entered manually. When managing a process control system, the physical location of the devices and controllers must be determined manually, often increasing the time required to correct problems and manage the process control system.</p><p> What is needed is a method of setting up a process control system that takes into account the physical layout of the facility and allows the system operator to quickly access the spatial locations of the process control devices and controllers.</p>
<p> The present invention relates to the use of facility spatial information for setting up and managing process control systems contained within a facility. The process control system may follow standard protocols. Such a system favors the efficient design and use of process control systems and ensures that the physical characteristics of the system follow standards. In addition, such systems also advantageously provide more efficient diagnostics, online debugging, alarm management, and device maintenance. The tool may optionally provide automatic generation of the layout of the process control network applied to the spatial layout of the facility.</p><p> In another embodiment, the tool is used to analyze the layout of a process control network applied to the physical layout of a facility to ensure that the layout of the network follows the criteria of a standard protocol such as the Fieldbus protocol. Used for.</p><p> The tool can optionally provide a blinking device representation to indicate an activation alarm in the network.</p><p> In another embodiment, the process control network is first set up using a logical connection, and then the settings are applied to the spatial layout of the facility and the spatial information applied to the layout of the network. Used to manage process control networks.</p>
The invention of the present application can be better understood by reference to the accompanying drawings for its many purposes, features, and advantages identified by those skilled in the art.
(Embodiment 1) The process control environment 100 is shown in FIG. 1 and shows a control environment for implementing a digital control system, a process controller, and the like. The process control environment 100 includes an operator workstation 102, a lab workstation 104, and an engineering workstation 106 electrically interconnected by a local area network (LAN) 108, or various workstations and multiple workstations. It has other known communication connections that transmit and receive data in the controller / multiplexer 110 and control signals. Workstations 102, 104, and 106 are, for example, computers that follow an IBM compatible architecture. Workstations 102, 104, and 106 are shown to be connected by LAN 108 to a plurality of controllers / multiplexers 110 that are electrically connected between the workstation and the plurality of processes 112. LAN in a number of different embodiments The 108 has a single workstation directly connected to the controller / multiplexer 110, or instead has multiple workstations (eg, three workstations 102,104,106), and the purpose of the process control environment 100. And have many controllers / multiplexers 110 based on requirements. In certain embodiments, the single process controller / multiplexer 110 controls several different processes 112, or instead controls part of a single process.
In process control environment 100, the process control method is by generating a software controlled solution for engineering workstation 106 and, for example, via LAN 108 to perform the solution, operator workstation 102, lab. Developed by transmitting to workstation 104 and controller / multiplexer 110. The operator workstation 102 provides an interface display for the control / monitoring method performed by the controller / multiplexer 110, and also displays the process 112 to change the control attribute values as required by the designed solution. To communicate with one or more of the controller / multiplexer 110. Process 112 consists of one or more field devices, which can be high performance field devices or conventional (non-high performance) field devices.
In addition, the operator workstation 102 transmits visual and audio feedback to the operator with respect to the state and conditions of the controlled process 112. The engineering workstation 106 has a processor 116, a display 115, and one or more input / output (I / O) devices or user interface devices 118 (eg, keyboard, light pen, etc.). The workstation 106 also has a memory 117 that includes volatile and non-volatile memory. The memory 117 includes a control program executed on the processor 116 that realizes the control operations and functions of the process control environment 100. Memory 117 is also a configuration and management tool 120 (Control). It also has Studio tools). The operator workstation 102 and other workstations (not shown) in the process control environment 100 have a display (not shown) and a user interface device (not shown) to allow interaction between the user and the processor. It has at least one central processor (not shown) electrically connected to (not shown).
The tool 120 is used for the configuration of the process control network (100) and to ensure that the process control network (100) corresponds to the desired standard protocol (eg, Fieldbus protocol). .. The tool 120 may also be used to provide more efficient troubleshooting and maintenance during the management of the process control network (100). The tool 120, preferably software stored in memory 117, may be included on a computer-readable recording medium and is executed by processor 116 of engineering workstation 106. The computer-readable recording medium can be a flexible disk (floppy (registered trademark) disk), a CD-ROM, or any other type of recording medium on which software can be stored. The tool 120 may include only the logical connections of process 112 or physical connections that incorporate the spatial features of the refinery or manufacturing facility layout on the display 115 of the engineering workstation 106. Allows the screen display to be presented.
While the tools of the present invention are described in detail together with a process control system using a Fieldbus device (synonymous with a process control network in the present specification), the tools of the present invention are protocols that depend on other than the 2-wire bus, and It should be noted that it can be used in process control systems with other types of field devices and communication protocols, including protocols that support analog only or both analog and digital communications. Thus, for example, the tools of the present invention are used in any process control system that communicates using communication protocols such as HART, PROFIBUS, or any other communication protocol that exists or may be developed in the future. be able to.
A general description of the Fieldbus protocol, field devices configured according to this protocol, how communication occurs in process control environment 100 running the Fieldbus protocol, and examples of restrictions on the values required under the Fieldbus protocol are provided. .. However, it should be understood that the Fieldbus protocol is known to those of skill in the art, and numerous articles, pamphlets, and specifications available, distributed, and available from the Fieldbus Foundation, a non-profit organization located in Austin, Texas. It is described in detail in the book. In particular, the Fieldbus protocol, which includes the value constraints required under the Fieldbus protocol, is described in detail in the Foundation Fieldbus (1996), Wiring and Installation 31.25 Kbits / sec Voltage Mode Wiring Media Application Guide.
Typically, the Fieldbus protocol provides a standardized physical interface in a two-wire loop to a bus that interconnects process control equipment such as sensors, actuators, controllers, valves, etc. contained within the measurement or process control environment 100. Provided are digital, serial, and bidirectional communication protocols. The Fieldbus protocol effectively provides a local area network for field equipment (field devices) within the process. The Fieldbus protocol enables these devices to perform control functions in distributed locations throughout the process and to communicate with each other before and after the execution of these control functions to perform the overall control method. To do. The Fieldbus protocol enables control functions that should be distributed across the process control network (100), which reduces the complexity of the central process controller or eliminates the need altogether. However, the distributed nature of the system adds complexity when managing the system and determining the physical location of the device in question, when troubleshooting and managing the system.
The Fieldbus protocol allows control of field devices and overall process control systems by providing communication through device descriptions and functional blocks. A field device is a field device such as a transmitter and a valve with a processor that monitors the performance and status of the device. The device description is similar to the driver for the device. For field devices, the device description has calibration procedures, parameter procedures, and other information required by the control system to communicate with the field device. The field device is capable of notifying the control system of standard operating parameters, self-diagnosing problems such as uncalibrated equipment, and notifying the control system. Each field device has a unique physical device tag and a corresponding network address.
Many types of communications are available to manage field devices, obtain port and communication statistics, obtain field device status, view and change resource settings and parameters, and field devices. It includes initiating a master reset or self-test of the device, displaying the state of the sensor, raising and lowering the sensor and making changes to zero. Managing the characteristics of a process control system by providing spatial information as well as managing the communications listed above is more efficient and easier to use.
With reference to FIG. 2, the controller / multiplexer and process portion of the process control network (process control environment) 100 of FIG. 1 according to the Fieldbus protocol is shown. The network 100 has a controller / multiplexer 110 coupled via a bus 142 to one or more processes 112 consisting of a plurality of field devices. Bus 142, like any other feature, has multiple sections or segments with corresponding lengths. Bus 142 may also have one or more junction boxes 144 (JB1, JB2, JB3) often referred to as "bricks". Each junction box 144 may be coupled to one or more fieldbus devices 146 via bus 142. Also, the controller / multiplexer 110 is coupled to at least one power source (PS) 148. The network shown in FIG. 2 is an example only, and there are many other ways in which the process control network 100 can be configured using the Fieldbus protocol.
The process control network 100 includes the length of branch lines of a specific communication section, the length of the entire bus, the total number of process control devices coupled to a specific junction box, and the controller and the controller and the layout of the manufacturing facility. It has a number of spatial features such as the physical location of the device. These spatial features can be automatically measured and calculated during system setup using spatial information about the physical layout of the facility. The process control network 100 also has a number of non-spatial features such as voltage drop across the communication section, current draw across segments, and device types in the system. These non-spatial features are provided by the user when configuring the system. The tool 120 analyzes these features to determine if the process control network 100 corresponds to the desired standard protocol.
Once the process control system setup is complete, the tool 120, which includes the spatial layout of the system in the facility, is used to manage the process control system using any workstation 102, 104, or 106. Can be done. Functions for managing process control systems include functions such as diagnostics, online debugging, alarm monitoring, and device maintenance. When a valve or other device fails during diagnostic and alarm monitoring, the device representation on the display device screen can be flashed on the spatial display of the facility and is easily found. The device tag name, as well as the spatial location of the device, can be used to identify the valve or other device. During online debugging, the values of connectors and attributes in the functional block can be shown in the spatial representation of the facility to make it easier for the user to see the current conditions of the system. By selecting a device in the spatial display during device maintenance, it is possible to obtain the current status and information about the device, such as the current flow rate or the latest maintenance record.
The process control environment (process control network) 100 exists in the configuration model or configuration implementation 210 and the management or runtime model or implementation 220 shown in FIG. Configuration implementation 210, component devices, objects, interconnects and interrelationships within the process control environment 100 are defined and associated with spatial information regarding the physical layout of the facility. At runtime execution 220, various component device, object, interconnect, and interrelationship operations are performed. Configuration Implementation 210 and Runtime Implementation 220 are interconnected through an ASCII-based download language. The download language creates system objects according to user-supplied definitions and generates examples from the supplied definitions. Also, in addition to downloading definitions, the download language uploads examples and example values. Configuration Enforcement 210 is activated to run at Runtime Enforcement 220 using the installation procedure.
The process control environment 100 has a plurality of subsystems with some of the subsystems having both configuration and runtime execution. For example, the process graphics subsystem 230 provides a user-defined display and operator interface for the architecture of the process control environment 100. The process graphics subsystem 230 has a process graphics editor 232, a portion of the configuration implementation 210, a process graphics viewer 234, and a portion of the runtime implementation 220. The process graphics editor 232 is connected to the process graphics viewer 234 by the intersubsystem interface 236 in the download language. The process control environment 100 also has a control subsystem 240 that configures and installs the control modules and equipment modules in the definition and module editor 242 and executes the control modules and equipment modules in the runtime controller 244. The definition and module editor 242 operates within the configuration implementation 210 and the runtime controller 244 operates within the runtime implementation 220 to provide continuous and ordered control functions. The definition and module editor 242 is connected to the runtime controller 244 by the intersubsystem interface 246 in the download language. The plurality of subsystems are interconnected by subsystem interface 250.
Configuration Implementation 210 and Runtime Execution 220 connect to the master database 260 to support access to common data structures. Transfer configuration data from master database 260 to local Connect to master database 260, for example to local database 262 as directed by the user, to various local (non-master) databases 262. Part of the master database 260 is the immutable database 270. The immutable database 270 transcends time so that the database continues to exist even after the builder of the database no longer exists, and the database is located in an address space different from the address space in which the database was constructed. An object that transcends space so that it can move. All setting implementations 210 are stored in the immutable database 270.
Runtime Execution 220 connects to immutable database 270 and local database 262 to access the data structures generated by Configuration Execution 210. In particular, runtime execution 220 acquires selected equipment modules, displays, etc. from the local database 262 and the immutable database 270. Runtime Execution 220 connects to other subsystems to install the definition and therefore installs the object used to generate the example and exemplifies the runtime example when the definition does not yet exist. And transmit information from various sources to the destination object.
A flow diagram showing the operation of the tool 120 is shown with reference to FIG. As present in various programs running under the Windows® operating system, the different steps of Tool 120 work according to the "wizard" function. After each step is completed, the user moves to the next step by operating the "NEXT" button or the like. If the user does not want to proceed, the user can exit the tool 120 by activating the "EXIT" button or the like.
At step 310, the user provides the tool 120 with information about the non-spatial features of the process control network 100. This information includes information about customers, devices used, calibration data, tag names, cable types, power supply characteristics, and cards, segments, as well as junction configuration information. Customer information can include the name of the customer, the name of the company, the location of the facility where the network is located, the name of the representative providing the tool, and the name of the contact person to that representative. The card configuration information can provide the user with information about the type of card used and the operation used to analyze the process control network 100. Segment configuration information can include power supply voltage, cable type (including information about the gauge of the wiring used within the cable, as well as other characteristics of the cable). The junction configuration information includes information about the device to be coupled to the junction and how the junction is configured, including the type of branch cable and the type of tool to couple to the junction box. .. In a preferred embodiment, the device is a device that follows the Fieldbus protocol. The user can optionally assign the tag identification to the device.
To configure the card, the user selects a controller card from the list of available controller cards. After the card is selected, the appropriate information for the selected controller card may be provided to the tool 120. In essence, by choosing a controller card, the user sets the segment of the network. In a preferred embodiment, each controller card is capable of controlling two segments. However, depending on the controller card, the segment can be more or less controlled by the controller card. While the segment is set, the user can access the summary of the information provided to the tool 120.
In step 320, the user provides the tool 120 with spatial information about the facility. In particular, the physical layout of the facility, including sketch size, equipment type, size, and location, and frame representation is provided. This information can be provided to Tool 120 by the user or imported from another tool such as the 3D Toolkit (eg, the published inventor from TGS).
At step 330, the functional block is generated and activated. In the Fieldbus protocol, functional blocks provide control of system behavior and can include features such as calibration procedures, parameter procedures, and communication procedures. Each Fieldbus device can have several functional blocks. The placement and interconnection of blocks defines the functionality of the Fieldbus device.
In step 340, the physical layout of the process control system is applied to the spatial information about the layout of the facility. Functional blocks and devices are connected and generally connected to the wiring of wire frames and other devices in the facility. The layout can be done manually by the user, or the tool 120 can automatically generate the physical layout of the process control system. Information such as the length from the controller to the junction or from one junction to another, and the length of the branch line can be automatically generated and calculated from the spatial layout of the refinery or manufacturing facility. In another embodiment, the functional block and device connections are first logically connected and later applied to spatial information about the facility.
At step 350, the process control system settings are checked for compliance with the requirements of the selected protocol. All of the branch line lengths of the segment are checked to ensure that the branch line length does not exceed a given branch line length as defined by standard protocols. The length of the branch line is limited by the number of devices in the segment (per segment). For example, the smaller the number of devices, the longer the branch line length for each segment. The number of devices per segment is also checked to ensure that the number of devices does not exceed the number of predetermined devices. The number of devices allowed can vary based on the controller used by the process control network 100. In a preferred embodiment, the controller allows 16 devices to be coupled to the bus on a segment-by-segment basis. However, current Fieldbus standards allow up to 32 devices to be coupled to the bus on a segment-by-segment basis. The overall current draw for each segment is checked to ensure that the current draw does not exceed the maximum current draw allowed by standard protocols.
In a preferred embodiment, the maximum current draw allowed is 375mA per segment. Cable lengths for all segments (including branch line lengths) are checked to ensure that the lengths do not exceed the maximum segment lengths allowed by standard protocols. In a preferred embodiment, the maximum allowable segment length is 6232 feet or 1900 meters. The minimum voltage per segment is checked to ensure that the voltage at any device coupled to the process control network 100 exceeds or is equal to the voltage described by the standard protocol. In a preferred embodiment, this voltage is 12.5 volts. If one or more values are not within the range defined by the protocol, the user can return to step 340 to modify the settings of process control network 100.
Once the process control network 100 is set up, the user can take advantage of the non-spatial and spatial information provided to begin managing the process control system (step 360). Many types of communications are available to manage field devices, obtain port and communication statistics, obtain field device status, view and change resource settings and parameters, and field devices. It includes initiating a master reset or self-test of the device, displaying the state of the sensor, raising and lowering the sensor and making changes to zero. Managing the characteristics of a process control system by providing spatial information as well as managing the communications listed above is more efficient and easier to use.
Spatial information about the facility can be entirely 3D with 3D walls, devices, workstations, etc. Spatial information about the facility can also be a 2D blueprint of the facility with the process control system settings mapped onto it, or any combination of 2D and 3D suitable for the user application.
In another embodiment, the tool 120 can provide the user with a way to obtain a bill of materials for the design of the process control network 100. The tool 120 can also automatically provide the layout of the process control system within the physical layout of the facility, making it possible to ensure that the protocol requirements are met.
In another embodiment, the user can configure the system without providing the spatial information of the facility and later add the spatial information used in the management of the process control system.
It is understood that the function is described to have an event with a certain regularity, but any other regularity for which the information is provided or the step is completed is included in the present invention. Will be done.
With reference to FIG. 5, the screen display of the setting part of the tool 120 that uses the logical connection of the process control system is shown in the main control window of the tool 120. The screen representation of the tool 120 includes a text-based pull-down menu 402, a pictogram menu 404, a stencil portion representation 406, and a diagram portion screen display 408. The stencil item 420 is displayed within the representation 406 of the stencil portion. The user's diagram of the design of the process control environment 100 is presented in the screen display of the diagram portion. This diagram of the process control design environment is referred to as the representation of the process control environment 100. Each of the representations in the main window can be resized and repositioned by the user according to known Windows® techniques. The tool 120 tracks the position and size of the frame of the main window by retaining immutable object data, including coordinates in a two-dimensional display, as well as styles and other information.
When designing the process control environment 100 using logical connections, the user simply activates the stencil item from the representation 408 of the stencil part and wants the activated stencil item in the screen display 408 of the diagram part. Drag it to the desired position and drop the activated stencil item to the desired position. The Control Studio object system 130 then generates a diagram item to cause the diagram to generate an object with all the information needed to set up the process control environment 100. Since the stencil item is an object that has all the information required for the diagram to set the process control environment 100, when the design of the process control environment 100 is completed, this design is suitable for the process control environment 100. It is possible to download directly to various parts.
With reference to FIGS. 5 and 6-8, the screen display of the spatial layout portion of the tool 120 that uses the spatial information of the facility in the layout of the process control system is shown. The tool 120 provides different angles and magnified views of the spatial layout of the process control system. This expression can be grayscale or color. The screen display can be included in the window of the tool 120, which is similar to the screen display window 408 of the diagram portion. Other methods of presenting spatial information fall within the scope of the present invention.
When designing the process control environment 100 using the spatial information of the facility, the user either imports the physical layout of the facility or generates the layout in the diagram portion of the main control window of tool 120. Start with. To add a field device or function, the user simply activates the stencil item from the representation 408 of the stencil portion and places the activated stencil item in the desired position in the spatial representation of the facility within the screen display 408 of the diagram portion. Drag to and drop the activated stencil item to the desired location. Similar to the rectangular representation of function, stencil items include a three-dimensional representation of the item found in refining or manufacturing facilities (eg, valves, pumps, tanks, pipes, etc.). Control The spatial portion of Studio Object System 130 then generates a diagram item with the information needed to set up the process control environment 100 within the spatial layout of the facility. When the process control environment 100 is completed within the diagram part, this design is because the stencil item is an object that has all the information needed for the diagram to set the process control environment 100 within the spatial layout of the facility. It can be downloaded directly to any part of the process control environment 100, including the spatial part of the Control Studio object system.
With reference to FIGS. 6 to 8 again, an example of the screen display 500 of the space is shown including an example of the physical layout of the facility in the space display. In particular, FIG. 6 shows a representation of the physical layout of the facility over the schematic representation of the facility. Spatial representations further include physical and logical representations of the various components of the process control environment 100. Therefore, the user can advantageously see the physical positions of the various components of the process control environment 100 superimposed on the schematic representation of the facility. 7 and 8 show an enlarged and rotated display of the portion of the diagram representation of FIG. Thus, FIGS. 7 and 8 show how the user can access parts of the diagram representation as shown in FIG. 6 to get a better view of a particular part of the process control environment 100. Shows an example of. It is understood that the spatial representation does not need to be superimposed on the schematic representation.
(Embodiment 2) Other embodiments are within the scope of the following claims.
For example, it is understood that while the protocol in which the preferred embodiments are described analyzes the process control network 100 for the Fieldbus protocol, any protocol can be analyzed by appropriately adjusting the constraints.
Also, for example, while preferred embodiments run under the Windows® operating system and use wizard-type representations, it is understood that these details are not limiting to the overall concept of the present invention. Will be done.
Also, although certain embodiments of the present invention have been illustrated and described, it will be apparent to those skilled in the art that modifications and modifications can be made in a broader sense without departing from the present invention. Accordingly, the appended claims include purposes such as all modifications and modifications contained in the original intent and purpose of the invention, including implementation in other programming languages. It is not limited. Further, although preferred embodiments are disclosed to be implemented in software, implementation in hardware, such as in application-specific integrated circuits, is also understood to be within the following claims.
<figref num="1">FIG. 6 is a schematic block diagram of a process control system showing a workstation including tools according to a generalized embodiment of the present invention that provides spatial setup and management capabilities.</figref><figref num="2">It is a block diagram of the controller / multiplexer and the process part of the process control system shown in FIG.</figref><figref num="3">It is a schematic block diagram which shows the process control environment in setting execution and management or runtime execution.</figref><figref num="4">It is a flowchart which shows the operation of the tool according to this invention.</figref><figref num="5">It is a screen display of the setting part of the tool showing the function of the process control system and the logical connection between the devices.</figref><figref num="6">FIG. 5 is a screen representation of a spatial portion showing the functions of a process control system and the physical connections between devices and their relative positions in the spatial layout of the facility.</figref><figref num="7">FIG. 5 is a screen representation of a spatial portion showing the functions of a process control system and the physical connections between devices and their relative positions in the spatial layout of the facility.</figref><figref num="8">FIG. 5 is a screen representation of a spatial portion showing the functions of a process control system and the physical connections between devices and their relative positions in the spatial layout of the facility.</figref>
Code description
100 Process control environment (process control network) 102 Operator workstation 104 Lab Workstation 106 Engineering Workstation 108 Local Area Network (LAN) 110 Process Controller / Multiplexer 112 process 115 display 116 processor 117 memory 118 User Interface Device 120 Configuration and management tools 130 Control Studio Object System 146 Fieldbus device 210 Setting implementation (setting model) 220 Runtime Implementation (Management or Runtime Model) 240 control subsystem 242 Definition and Module Editor 244 Runtime controller 260 master database 262 local database 270 immutable database 500 screen display
8 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8
Every citation, both ways
| Document | Relation | Office |
|---|---|---|
| JP08006884A | Cites | Japan |
| JP04225472A | Cites | Japan |
27 members in 6 offices
Priority claims5
| Document | Office | Kind | Date |
|---|---|---|---|
| 09488335 | United States of America | – | |
| 48833500 | United States of America | A | |
| 48833500 | United States of America | A | |
| 2000488335 | – | – | – |
| US20000488335 | – | – | – |
Members27
| Document | Office | Kind | |
|---|---|---|---|
| GB0101255D0 | United Kingdom | D0 | |
| GB2358487A | United Kingdom | A | |
| DE10102205A1 | Germany | A1 | |
| JP2001273345A | Japan | A | |
| GB2358487B | United Kingdom | B | |
| US6772017B1 | United States of America | B1 | |
| US2005010307A1 | United States of America | A1 | |
| US7010362B2 | United States of America | B2 | |
| GB0701784D0 | United Kingdom | D0 | |
| DE10102205B4 | Germany | B4 | |
| US2007179645A1 | United States of America | A1 | |
| CN101013318A | China | A | |
| JP2007242000A | Japan | A | |
| GB2437757A | United Kingdom | A | |
| GB2437757A8 | United Kingdom | A8 | |
| DE102007004341A1 | Germany | A1 | |
| HK1115204A | Hong Kong, China | A | |
| US2008312757A9 | United States of America | A9 | |
| US7474929B2 | United States of America | B2 | |
| JP2009048650A | Japan | A | |
| GB2437757B | United Kingdom | B | |
| JP4860044B2 | Japan | B2 | |
| JP2012074083A | Japan | A | |
| JP4989604B2This record | Japan | B2 | |
| CN101013318B | China | B | |
| JP5201843B2 | Japan | B2 | |
| JP5308508B2 | Japan | B2 |
15 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Cancellation because of no payment of annual feesLAPS | LAPS | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| First payment of annual fees (during grant procedure)JAPANESE INTERMEDIATE CODE: A61A61 | A61 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Decision of grant or rejection writtenTRDD | TRDD | |
| Transfer to examiner for re-examination before appeal (zenchi)AppealJAPANESE INTERMEDIATE CODE: A911A911 | A911 | |
| Written amendmentJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Decision of refusalJAPANESE INTERMEDIATE CODE: A02A02 | A02 | |
| Written amendmentJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Written permission of extension of timeJAPANESE INTERMEDIATE CODE: A602A602 | A602 | |
| Written request for extension of timeJAPANESE INTERMEDIATE CODE: A601A601 | A601 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 |
Numbers
- Publication
- 4989604
- Publication, DOCDB
- 4989604
- Publication, EPODOC
- JP4989604B
- Application
- 257113
- Application, DOCDB
- 2008257113
- Application, EPODOC
- JP20080257113
Titles2
- Japanese
- プロセス制御ネットワークを設定及び管理する方法並びに装置
- English
- How and equipment to set up and manage process control networks
Classification
- CPC, 8
- G05B19/41885
- G05B2219/32085
- G05B2219/32356
- G05B2219/32365
- G05B2219/23182
- Y02P90/02
- Y10S715/967
- Y10S715/965
- IPC, 2
- G06F17 50
- G05B19 418
