JP2000250920A - Shared information reference device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To refer to the unified names of control objects which differ at every plant and also to easily refer to the name of the control object of a higher rank such as the name of a plant belonging to a relevant control object when the states of plural control objects are compared with each other. SOLUTION: When the control data designated by an access data designation part 151 are shown at a data display part 153, an identification information selection part 152 selects the identifier of a relevant control object and also a proper identifier among those of higher rank control objects to which the said relevant control object belongs on the basis of the identification system that is designated by an identification system designation part 141. Then the acquired identifier is sent to a unifying word conversion part 103 to obtain a unified identifier.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for controlling data managed in an information control system of a plant such as a chemical plant or a power plant by a person other than an operator of the plant, for example, an operator of another plant, a staff of a head office, or a researcher The present invention relates to a shared information reference device used when referring to. Such a device can be widely applied particularly when referring to control data of a plant via an intranet, the Internet, or the like.

[0002]

2. Description of the Related Art In an information control system for controlling a chemical plant or the like, status data from a sensor installed at a site and setting data to a controller are accessed in units called tags. In this tag, values such as a current value, an upper limit value, a lower limit value, and a set value are stored. Tags are assigned unique alphanumeric characters within the plant called tag codes (such as “PV1001”), and can be identified thereby. Tags are grouped in units of devices to which the sensors are attached, and devices are grouped in units of equipment constituted by the devices. In this way, all data in the plant is managed in a hierarchical structure such as equipment-equipment-tag. This hierarchy is defined for each plant according to the structure of the plant.

Conventionally, this control information has been referred to by a control terminal installed in a plant operation room. This device includes:
A screen showing the name of the equipment, the name of the device or the tag code and its control status is displayed, through which the operator performs plant monitoring control.

[0004] In recent years, there has been an increasing need to refer to control information of a plant not only inside the plant but also from a head office or a research laboratory due to the spread of Internet technology or the like. If the head office can refer to the control information of each plant, it is possible to intensively grasp the operation status of each plant and issue an appropriate operation instruction to each plant. In addition, if the control information of each plant can be referred to at the research laboratory, it is possible to analyze the relationship between the control states of the plants that manufacture the same product and the yield of the product and issue a more efficient control instruction.

However, when a person who is not familiar with the plant-specific structure, such as a head office staff member or a researcher at a research laboratory, refers to control information using a screen created for each plant, each data is attached to any equipment. There is a problem that it is difficult to know which sensor value indicates. First, a tag code is like a consistent number given to control data handled in a plant, and it is difficult for an operator of the plant to determine which equipment and which sensor value it represents. Second, even if the tag code and the equipment to which the tag belongs or the type of sensor represented by the tag are displayed, these names are hard to understand because they are independent definitions for each plant. For example, to express the same temperature, “temperature”, “ond”,
There are cases where different names such as “T” are given, and it is difficult to determine that all of them represent the same temperature. Third, when comparing the state of equipment of multiple plants on the screen created for use in that plant,
Each screen does not show which plant the data belongs to, so it is hard to understand.

[0006]

As described above, when a person other than a plant-specific operator, such as a staff at a head office or a researcher at a research laboratory, refers to control information of a plant, there are the following problems.

[0007] 1) or is difficult to understand what the control object in the tag code representing which sensors which part of any equipment to be expressed.

2) The names are different for each plant, even though they actually represent the same device or the same state.
In addition, similar names are given even though they represent different devices or different states.

3) Even when comparing control data of the same equipment in different plants, since the identifier for discriminating the control data does not clearly indicate which plant, the data that corresponds to which plant is different. It is hard to understand.

An object of the present invention is to provide a user-friendly information reference device.

[0011]

Means for Solving the Problems One of the following is used as means for solving any of 1) to 3) described in the problem. As a first embodiment, the present apparatus includes a display processing unit that displays a control target and identification information for identifying the control target, an identifier of the control target and an identifier of a higher control target to which the control target belongs. It comprises a display terminal having an identifier selection unit for selecting an identifier to be specified from among them, and a shared information server that manages the control target of the plant in a hierarchical manner and periodically reflects the state of the control target.

The operator specifies the identification method of the tag data to be accessed using the menu displayed by the identifier selection unit of the display terminal. For example, a designation is made to display the device name to which the tag belongs together with the tag code. When the operator refers to the control data "PV0001", the device name ("boiler"), series name ("series 1"), and plant name ("plant 1") to which the tag belongs are sent from the shared information server to the display terminal. Is sent. The identifier selection unit of the display terminal selects a device name, which is the identification method specified by the operator, from the received higher-level control target names, and passes it to the display processing unit. The display processing unit displays the received name “boiler / PV0001”. As a result, the name of the device or the name of the plant indicated by the tag data can be confirmed.

[0013] More preferably, the identifier selection unit acquires a higher-order control object to which all tag data displayed on the display terminal belong, and from the acquired control objects, names of the control objects in each layer along the hierarchy. It is a means of selection.

[0014] When the operator sets the temperature of the series 1 boiler "PV00
To compare “01” with the temperature “PV1001” of the boiler of series 2, the equipment name (“boiler”), series name (“series 1”), and plant name (“plant 1”) are sent to PV0001. The device name (“boiler”), the system name (“system 2”), and the plant name (“plant 1”) are sent to the PV 1001. The identifier selection unit is sent. The control target names are compared in order from the highest order, and it is determined that the control target common to both is a plant identified by “plant 1”. The equipment name and tag code are displayed, that is, “Series 1 / Boiler / PV0001”, “Series 2 / Boiler /
PV1001 ”is displayed. When comparing the status of the same equipment among a plurality of systems or plants, it is possible to surely grasp which system or plant each equipment belongs to.

As a second embodiment, the present apparatus comprises a display processing unit for displaying a control target and identification information for identifying the control target, an identifier of the control target and a higher control target to which the control target belongs. A display terminal having an identifier selecting unit for selecting an identifier to be specified from the identifiers; a shared information server that hierarchically manages the control target of the plant and periodically reflects the state of the control target; And a dictionary server that manages the first name for identifying the second name in association with the second name.

The operator specifies the identification method of the tag data to be accessed using the menu displayed by the identifier selection unit of the display terminal. For example, a designation is made to display the device name to which the tag belongs. Also, instead of displaying the tag code, the sensor value name (indicating what sensor value the tag represents)
To be displayed. The operator sets the control data “PV
When referring to “0001”, the shared information server sends the tag code “PV00” together with the higher-level control target name such as the device name (“boiler”) and the plant name (“plant 1”) to which the tag belongs.
"01" to the dictionary server, which returns the "boiler" registered in association with "boiler" and the "temperature" registered in association with "PV0001" to the shared information server. Next, the shared information server transmits the control target name returned from the dictionary server to the display terminal, and the identifier selection unit of the display terminal uses an identification method instructed by the operator based on the transmitted control target name. Name,
Select the sensor name and pass it to the display processing unit. The display processing unit displays the received name “boiler / temperature”. Thereby, even if the name of the control target is different for each shared information server, it can be standardized. Further, it is possible to know what sensor the tag code represents.

According to the first embodiment, not the tag code but the name of the control target indicated by the tag is displayed.
It is possible to reliably grasp what equipment the displayed sensor data represents. Also, when comparing control data of the same equipment in different plants, the identifier for identifying each control data clearly indicates which plant belongs, so that it is easy to identify which data belongs to which plant. Can be determined.

According to the second embodiment, even if the name indicating the control target is different for each shared information server,
These names can be standardized and displayed. Since the names of the same equipment are displayed the same and the names of different equipment are displayed differently, those equipments can be identified with certainty.

[0019]

BRIEF DESCRIPTION OF THE DRAWINGS FIG.

FIG. 1 is a block diagram of the present invention.

The operator terminal 120 is connected to the plant database servers 100 and 110 using the network 20 such as the Internet. Hereinafter, the plant database server 100 is referred to as a site 1 server, and the plant database server 110 is referred to as a site 2 server.

The site 1 server 100 includes a plant data management unit 101, a data access module management unit 102,
And a unified term conversion unit 103. Site 2 server 11
0 has the same configuration, and the plant data management unit 111,
It comprises a data access module management unit 112 and a unified term conversion unit 113.

The plant data management unit 101 collects and holds sensor data from the sensor 130 installed at the site via the control network 190. Also operator terminal
In response to the data access request from 120, the requested data is transmitted to the operator terminal.

Data access module management unit 102
Is implemented in a WWW (World Wide Web) server, and can download the data access processing module 150 in response to a download request from the operator terminal 120.

The operator terminal 120 is the site 1 server 1
When the data in the plant data management unit 101 of the site 1 is accessed, the data access processing module 150 is downloaded from the data access module management unit 102 of the site 1 server, and the data in the plant data management unit 111 of the site 2 server 110 is accessed. To do so, the data access processing module 150 is downloaded from the data access module management unit 112 of the site 2 server.

The data access processing module 150 is Ja
It is implemented by va and executed by the module execution unit 160 such as a WWW browser after being downloaded.
The data access processing module 150 includes an access data designation unit 151, an identification information selection unit 152, and a data display unit 1.
53. Mouse 1 of operator terminal 120
The input by 70 via the module implementation unit 160
The screen drawing command input to the access data specifying unit 151 and executed by the data display unit 153 is displayed on the CRT 180 via the module execution unit 160.

The operator terminal 120 has an identification method designation module 140. Identification method designation module 1
40 has an identification method designation unit 141. Identification method specification section
141 issues an instruction command of the identification method to the identification information selection unit 152 in the data access processing module 150 via the module execution unit 160.

FIG. 2 shows plant data managed by the plant data management unit 101.

As shown in FIG. 2A, plant data is managed in a hierarchical structure such as plant-sequence-equipment-tag. Each node is assigned an ID 201 that uniquely identifies the node, and a name 202 assigned to the node. For example, a node 200 indicating a tag of PV0001
0001 contains “PV0001” as the name 202. When accessing data managed by the plant data management unit 101, the ID 201 of the data is specified.
The sensor values collected via the control network 190 are managed as tags in the configuration shown in FIG. Each tag has a configuration as shown in FIG.

When referring to data as shown in FIG. 2 at the operator terminal 120, the present invention has the following functions.

1) Specifying a higher-level control target: A higher-level control target to which a control target to be referenced belongs can be specified.
For example, when referring to tag data, it is possible to specify which plant, affiliate, or facility the tag belongs to.

2) Name conversion: The tag code is converted into a sensor name represented by the tag. When referring to data of a plurality of sites, even if the names of the control targets are different for each site, they are converted and displayed to a unified name. This makes it easy to understand which sensor value of which facility the tag represents.

First, a description will be given of 1) clarification of a high-order control object.

As shown in FIG. 3A, “PV0001” representing the boiler temperature at site 1 and “PV10” representing the boiler temperature at site 2
When "01" is displayed, it is possible to instruct the specification of the name of a higher control object to which the tag belongs in a dialog 1600 displayed by the identification method specifying unit 141. For example, in FIG. When designated by 350, each of the meters 1201 and 1202 has "Site 1"
/ PV0001 "and" site 2 / PV0001 "are displayed. Furthermore, as shown in FIG. 3B, when" sequence "and" equipment "are additionally specified in the dialog 1600 displayed by the identification method specifying unit 141," site 1 "is displayed. / Series 1 / Boiler / PV0001 "
It is displayed as “Site 2 / Series 1 / Boiler / PV0001”. This makes it clear which site each data belongs to, so that when comparing data from a plurality of sites, it is possible to confirm which data belongs to which site without mistake.

The method for realizing this is as follows.

First, in order to refer to the data in the site 1 server 100 and the data in the site 2 server 110, the data access module management unit 10 of each server is referred to.
2, 112, the data access processing module 150 is downloaded. The data access processing module 150 downloaded from the data access module management unit 102 displays the meter 1201, and the data access processing module 150 downloaded from the data access module management unit 112 displays the meter 1202.

When the operator designates an identification method using the dialog 1600 displayed by the identification method designation section 141, the identification information selection in the two data access processing modules 150 to which the identification method designation information 400 as shown in FIG. Registered in the unit 152. Here, 401
Is the machine ID of the operator terminal 120, and 402 is the specified identification method.

The processing described hereinafter is performed on the site 1 server 100
Since the same applies to the data access processing module downloaded from the site 1 server and the data access processing module downloaded from the site 2 server 110, the data access processing module downloaded from the site 1 server will be described.

The access data specifying unit 151 determines that the site 1
The server 100 requests data to be accessed. For example, when it is desired to acquire the name of the tag data indicated by the ID PV0001, the data shown in FIG. Here, 501 is the machine ID of the operator terminal 120, 502 is the machine ID of the server 100, 504 is the request type (in this case, an ID meaning the acquisition of the name of the tag data is entered), and 505 is the ID of the target tag. is there. This data is processed by the plant data management unit 101 in the site 1 server 100. As a result, FIG.
The data shown in (b) is generated. Here, 511 is the machine ID of the operator terminal 120 and 512 is the server 100
514 is the number of acquired data, 515
1 to 5154 are acquired data. This data is obtained as follows.

When the data PV0001 is designated by the target data ID 505 in the request data of FIG. 5A, the plant data management unit 101 searches for the data of ID PV0001 in FIG. When the name “PV0001” with the ID PV0001 is obtained,
Acquire the parent node of the node and obtain the facility name "Boiler"
To get. Further, a series name “series 1” which is a parent of the node is acquired. Similarly, the plant name “site 1” is acquired. The obtained data is referred to as data 5 in FIG.
Set 151 to 5154. Here, 4 is set to the total number of data 514 in order to transmit data of four layers.

In order to associate FIG. 5 (a) with FIG. 5 (b), corresponding requests and responses have the same numbers in 503 and 513 (this number is incremented each time a request is issued). ). This data is passed to the identification information selection unit 152 in the data access processing module 150.

The identification information selecting section 152 receiving this data
Determines which of the four names set in 5151 to 5154 in FIG. 5B is to be displayed. That is, with reference to the identification method designation information 400 shown in FIG.
151 is valid. ii) If a series is registered in the name type 402, 515
2 is valid.

Iii) If equipment is registered in the name type 402, 5153 is made valid.

Iv) If TAG is registered in the name type 402, 5154 is made valid.

The name to be displayed is set to the identification name 703 of the meter component having the structure shown in FIG. That is, with reference to the identification method designation information 400 shown in FIG.
In the case of FIG. 3A, 5151 and 5154 are valid, and “Site 1” and “PV0001” are attribute 70 of the meter component.
Set to 3. In the case of FIG.
2,5153,5154 are valid, and “Site 1”, “Series 1”, “Boiler” and “PV0001” are attribute 7 of the meter part.
Set to 03.

When displaying the current value of the tag,
The access data specifying unit 151 transmits the data shown in FIG. 5C to the plant data management unit 101, and acquires the data shown in FIG. The current value data 515 thus obtained is set in the attribute 704.

As shown in FIG. 6B, the identification name set in the attribute 703 of the meter component is displayed on the identification name display section 710 of the meter component 1201, and the current value of the sensor set in the attribute 704 is the sensor value. It is displayed on the value display section 711.

Thus, the display is performed as shown in FIGS. 3 (a) and 3 (b).

According to the present invention, not only the operator can explicitly specify which hierarchy name is to be displayed, but also the hierarchy to be automatically displayed can be set according to the data to be accessed. If the data displayed on the screen has the same parent, the layers below the parent are displayed as names.
That is, as shown in FIG. 7A, when data belonging to the same facility in the site 1 is displayed, its name is displayed as “PV0001” or “PV0002”. On the other hand, FIG.
As shown in (b), if the data displayed by the meter 1202 is changed to that of the site 2 in the dialog 1610 displayed by the access data specifying unit 151, the names of all layers are displayed in order from the plant name. Thereby, an appropriate data name can be displayed according to the data that the operator wants to refer to at the same time. The method for realizing this is as follows.

The identification information selecting section 152 obtains the information shown in FIG.
The data of (b) is passed to the identification method designation module 140. The identification method designation module 140 holds the data of FIG. 5B received from each data access processing module 150, and performs the following operations as shown in FIG.
152, 5153, or 5154 is determined.

(Step 1) Identification method designation module 1
If the site name 5151 is the same in all data held by 40, go to step 2; otherwise, 5151, 515
2, 5153, 5154, the identification method designation information 400 of the data access processing module 150.
Set to. That is, “plant + system + equipment + TAG” is set in the name type 402. Go to step 5.

(Step 2) Identification method designation module 1
If the series name 5152 is the same in all the data held by 40, go to step 3; otherwise, 5152, 515
3, 5154 is set in the identification method designation information 400 of the data access processing module 150.
That is, “series + facility + TAG” is set in the name type 402. Go to step 5.

(Step 3) Identification method designation module 1
If the equipment name 5153 is the same in all data held by 40, go to step 4; otherwise, 5153, 5154
To display the data access processing module 150
Is set in the identification method designation information 400 of the user. That is, “equipment + TAG” is set in the name type 402.
Go to step 5.

(Step 4) Identification method designation module 1
The identification method designation information 400 of the data access processing module 150 is displayed so as to display 5154 held by the
Set to. That is, "TAG" is added to the name type 402.
Is set. Go to step 5. (Step 5) End.

Next, the identification method designation information 400 set.
, The identification information selection unit 152 of each data access processing module 150 has 5151, 5152, 515
At 3,5154, a valid one is set in the attribute 703 of the meter part.

In the case of FIG. 7A, the processing is performed up to step 4, and as a result, only the tag name is displayed.

In the case of FIG. 7B, all the names are set in the attribute 703 in step 1, and as a result, the display is made from the site name.

Next, 2) name conversion will be described.

The plant data management units 101 and 111 of the servers 100 and 110 have the configuration shown in FIGS.
It is assumed that the control target is managed in a hierarchy as shown in (b).

As shown in FIG. 9A, when "equipment" and "TAG" are specified as identification types in a dialog 1602 displayed by the identification method specifying unit 141, "BOILER /" is used as an identifier for identifying control data. PV0001 ”,“ Boiler / PV
0001 "is displayed. In this way, even if the boiler is expressed in the same way, if there is a discrepancy in the equipment name managed between the two sites, this is reflected in the display. It is difficult to understand that they represent the same equipment.Although the boiler has various sensor information, it is difficult to know which sensor value is displayed by the meter. Dialog 1 like
When the “name conversion” toggle button is checked in addition to “equipment” and “TAG” in 602, both identifiers are unified to “boiler / temperature”. Thereby, the meters 1201, 1
It is easy to see that the value displayed at 202 indicates the temperature of the boiler.

The method for realizing this is as follows.

First, when an identification method and name conversion are instructed by a dialog 1602 issued by the identification information selection unit 152, the identification method designation information 1000 as shown in FIG.
Registered in 2. Here, 401 is the operator terminal 12
0, machine ID 402, designated identification method, 100
1 is a flag indicating the presence or absence of a name conversion instruction.

Next, access data specifying section 151 requests site 1 server 100 for the data to be accessed. For example, when it is desired to acquire the name of the tag data indicated by the ID PV0001, the data shown in FIG. 5A is transmitted to the plant database server 100. This data is processed by the plant data management unit 101 in the plant database server 100, and as a result, data shown in FIG. This data is passed to the identification information selection unit 152 in the data access processing module 150.

The identification information selecting section 152 refers to the name type 402 and the name conversion instruction 1001 of the identification method designation information 1000 with the name conversion instruction, and receives 5151, 5152, 5153, and 5153 in FIG. Among the 5154s, those that require name conversion are determined. That is, i) If “plant” is registered in the name type 402 and “present” is registered in the name conversion instruction 1001, 5151 is set as a name conversion target.

Ii) If “series” is registered in the name type 402 and “present” is registered in the name conversion instruction 1001, 5152 is to be subjected to name conversion.

Iii) If “equipment” is registered in the name type 402 and “present” is registered in the name conversion instruction 1001, 5153 is set as a name conversion target.

Iv) If “TAG” is registered in the name type 402 and “Yes” is registered in the name conversion instruction 1001, 5154 is set as a name conversion target.

The identification information selecting section 152 transmits data requesting name conversion to the site 1 server. This data is shown in FIG. Here, 501 is the operator terminal 1
20 is a machine ID, and 502 is a machine I of the server 100.
D, 1104 is a request type (containing the ID of the name to be converted), and 1105 is a name to be converted. For example, when converting the equipment name “BOILER”, “equipment conversion” is entered in 1104 and “BOILER” is entered in 1105. Also,
When converting the tag code “PV0001”, “TAG conversion” is entered in 1104 and “PV0001” is entered in 1105.

Site 1 that received the data of FIG.
The server 100 passes it to the unified term conversion unit 103.

The unified term conversion unit 103 acquires the corresponding standard term by referring to the table 900 (FIG. 12) contained therein. That is, the item having the type specified by the request type 1104 and the item specified by the conversion
1, 902 to retrieve a standard term 903 associated therewith. For example, when "equipment conversion" is specified in 1104 and "BOILER" is specified in 1105, it is checked whether or not both are registered by referring to 901 and 902, and the registered "boiler" is acquired in association therewith. I do. Next, the acquired standard term “boiler” is changed to standard term 11
The response data shown in FIG. 11B is transmitted to the data access processing module 150 again.

In the same manner, the identification information selecting unit 152 assigns all the names extracted as name conversion targets to the site 1 server 1
A request for conversion is sent to the unified term conversion unit 103 in 00. After converting all the names extracted as name conversion targets,
The name designated as the name type 402 of the identification method designation information of 0 is set in the identification name 703 of the meter component. 9A and 9B based on the information thus set.
The display is performed as shown in (b).

According to the present invention, 1) not only the tag code but also the name of the control target indicated by the tag is displayed, so that the displayed sensor data can be used to ascertain which equipment is represented. can do.

2) Even if the name indicating the control target is different for each shared information server, these names can be standardized and displayed. Since the names of the same equipment are displayed the same and the names of different equipment are displayed differently, those equipments can be identified with certainty.

3) By displaying the sensor data name instead of the tag code notation, it is easy to grasp from which sensor of the equipment the tag expresses data.

4) When comparing control data of the same equipment in different plants, since an identifier for discriminating each control data clearly indicates which plant belongs to which plant, which data belongs to which plant Can be easily determined.

[0076]

According to the above configuration of the present invention, a user-friendly information reference device can be provided.

[Brief description of the drawings]

FIG. 1 is a system configuration diagram.

FIG. 2 shows data managed by a plant data management unit.

FIG. 3 shows a display example of data identification information.

FIG. 4 shows identification method designation information possessed by an identification information selection unit 152.

FIG. 5 shows communication data between a shared server and an operator terminal.

FIG. 6 shows the relationship between the attribute of a meter component and its display.

FIG. 7 shows an example of a relationship between an instruction of access data and a name display.

FIG. 8 is a diagram showing a difference between facility names managed at site 1 and site 2.

FIG. 9 shows an example of data access involving name conversion.

FIG. 10 shows identification method designation information with a name conversion instruction.

FIG. 11 shows a name conversion request and its response data.

FIG. 12 shows a name conversion table included in the unified term conversion unit 103.

[Explanation of symbols]

Reference numeral 20: network, 100: site 1 server that publishes plant data of site 1, 101, 111: plant data management unit, 102, 112: data access module management unit, 103, 113: unified term conversion unit, 11
0: Site 2 server for publishing plant data of site 2, 120: operator terminal for accessing data of each site, 130: sensor, 140: identification method designation module, 141: identification method designation unit, 150: data access processing module , 151... Access data designating section, 1
52: identification information selection unit, 153: data display unit, 160
... Module execution unit, 190 ... Control network, 40
0, 1000: identification method designation information of the identification information selection unit 152; 900: name conversion table of the unified term conversion unit 103; 1600, 1602: identification method designation unit 1
Dialog displayed by 41.

 ──────────────────────────────────────────────────続 き Continuing on the front page (72) Inventor Masayuki Tani 7-1-1, Omikacho, Hitachi City, Ibaraki Prefecture Within Hitachi Research Laboratory, Hitachi, Ltd. (72) Inventor Hiroshi Kobayashi 5-chome, Omikamachi, Hitachi City, Ibaraki Prefecture No. 1 F term in the Hitachi, Ltd. Omika factory (reference) 5B075 KK03 ND03 ND35 NK02 PP03 PP13 PP22 PQ02 PQ20 5H215 AA01 BB12 CC07 CX08 GG03 GG05 JJ14

Claims (5)

[Claims] 1. A shared information reference device for referencing a control object managed hierarchically, means for designating a control object to be referred to, an identifier of the designated control object and a higher-level control object to which the control object belongs. A shared information reference device, comprising: an identifier selecting unit that selects an identifier to be specified from the identifier; and a unit that specifies the identifier selected by the identifier selecting unit. 2. The shared information reference device according to claim 1, wherein, for each identifier selected by the identifier selecting means, an identifier standardizing means for acquiring a second identifier registered in association with the identifier; Means for specifying the second identifier acquired by the identifier standardizing means. 3. The shared information reference device according to claim 1, wherein said identifier selecting means selects a second control target from a higher control target to which the specified control target belongs; A shared information reference device for acquiring an identifier of each control target according to a hierarchical structure from the second control target to the first control target. 4. The shared information reference apparatus according to claim 3, wherein said higher-level control target specifying means is means for acquiring a common control target to which all the control targets to be referred belong. apparatus. 5. A shared information referencing device according to claim 1, wherein: means for designating a screen to refer to the control object; and a common control object to acquire a common control object to which all the control objects to be referenced on the designated screen belong. A shared information reference device comprising: an acquiring unit; and a unit that specifies an identifier of each control target according to a hierarchical structure from the control target acquired by the common control target acquisition unit to each control target.