JPH07297878A - Distributed production equipment - Google Patents

Abstract

PURPOSE:To obtain a system environment independently of a specification specific to each device and each network by providing a virtual model to cover a difference from specifications between different kind of devices and a difference from specifications between network protocols to the device. CONSTITUTION:A device model 300a is a virtual model devised sufficiently to cover the difference from specifications of real devices 400 being objects of operation, and an application 100 accesses the device model 300a in place of the real devices 400. Furthermore, a network model 300b is a virtual model devised sufficiently to cover a difference from network protocols and the application 100 accesses the network model 300b in place of the real networks. Thus, the portability of the applications is secured to enhance the transplantation performance and the divertibility. Furthermore, the performance of inter- operation is secured in the system, and the excellent environment is obtained, in which technical problems relating to the connection and the operation of devices at system building-up are not conscious.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a distributed production apparatus in which a plurality of heterogeneous devices are distributed and arranged on various networks, and more particularly to the provision of a system environment that is not affected by the unique specifications of each device and each network.

[0002]

2. Description of the Related Art In a conventional FA (factory automation) total system, a network, a PLC (programmable logic controller), a workstation, etc. are being developed as individual items, but a unified system concept for the entire system was considered. It cannot be said that the development of a suitable device has been sufficiently studied.

As future problems in the FA total system environment, work stations, PLCs,
In a system environment in which various devices such as other devices exist, ensuring portability and interoperability of applications has become an important issue.

[0004]

By the way, in developing an application in this type of system, the following problems are encountered.

1) It is compelled to create a system swayed by API (application programming interface) specifications. That is, not only the specifications differ for each device, but for example, different networks have different language interfaces, and system design is becoming very complicated.

2) It is forced to create a system that is swayed by the specifications of the device to be accessed. That is, the physical mounting method, model, etc. of the access target device are different for each access target device, which also makes the system design very complicated.

3) The system is forced to be built around the specifications specific to the network. For example, it is natural that the control protocol is different for each network, and the system design is becoming very complicated in order to support the different control protocol for each network.

As described above, in the development of an application in this type of system, it is not enough to satisfy the user's request, and various techniques considering API specifications, access target device specifications, network-specific specifications, etc. Is required to overcome the social problems.

In addition, when the applications are viewed from the functional side, although they are almost the same, they must be individually designed, produced, and evaluated depending on the access target device, the network, and the like.

FIG. 11 summarizes the above problems as factors affecting application development. Here, the system shown in FIG. 11 can be considered as a configuration in which an application that is an operation source and an actual device that is an operation target are connected via a network that is a data exchange unit. , It can be defined as an entity that describes the control and management procedures for satisfying user requirements.

In FIG. 11, the application operating environment relating to the operation source is as follows: 1) interface specifications (calling method, function name, etc.) 2) description language 3) OS (operating system), process management, message communication, etc. 4) basic software Wear is considered.

The device access environment related to the operation target is as follows: 1) memory allocation and configuration (address, name, size, accessible unit) which are physical factors 2) functional characteristics (operation, mode) 3) functional control Means (setup, control procedure, preparation, etc.) are considered.

As a network access environment for the data exchange means, 1) means for file transfer, message service, etc. 2) function (capability) depending on the above means 3) control procedure can be considered.

Therefore, an object of the present invention is to provide a system environment that is not affected by the specific specifications of each device and each network.

Specifically, it is an object of the present invention to provide a distributed production apparatus that enables the following concept.

1) Ensure portability for applications. That is, the portability and diversion of the developed application are improved.

2) Ensure interoperability in the system. That is, at least the user and the SE (system engineer) provide an environment in which the system does not need to be aware of the technical problem regarding the connection and operation of each device when constructing the system.

3) Transition from access transparency to position transparency. That is, it is possible to access the resources without notifying the location information about the resources scattered on the network. Here, access transparency refers to a state in which a resource can be freely accessed if the location of the resource is known, and location transparency refers to a state in which the resource can be accessed freely if the name of the resource is known. .

4) Transition from real device access to common model access. With such a configuration, the same model can be accessed by understanding the common model.

[0020]

In order to achieve the above object, the present invention is a distributed production apparatus in which a plurality of heterogeneous devices are distributed and arranged on various networks, and a difference in specifications between the plurality of heterogeneous devices and the network. It is characterized by comprising a virtualization model for absorbing the difference in the protocol of 1. and an integrated interface means for supporting access to the virtualization model.

Further, the present invention is a distributed production apparatus in which a plurality of heterogeneous devices are distributed and arranged on various networks, and is provided with an application as an operation source and an actual device as an operation target, and the applications are integrated. Application programming interface,
A first common or limited model, a first distributed computing environment, connected to a network via a first network architecture, wherein the real device is a real device interface, a second common or limited model,
A second distributed computing environment, characterized by being connected to the network via a second network architecture.

Further, according to the present invention, a plurality of clients, which are terminals for each business, and a file / database server are connected to the first network, and a plurality of programmable logic controllers are connected to the second network.
In a distributed production apparatus in which the first network and the second network are connected via a production management data server, the client, the file database server, and the production management data server, respectively. A network operating system is installed, resources on both the file / database server and the production management data server are managed by a directory service, and a virtual programmable logic controller memory area is provided in the memory on the production management data server. It is characterized by securing and maintaining data synchronism by an event or data link function.

Further, according to the present invention, a plurality of clients, which are terminals for each business, and a file database server are connected to the first network, and a plurality of programmable logic controllers are connected to the second network.
In a distributed production apparatus in which the first network and the second network are connected via a production management data server, the client, the file database server, and the production management data server, respectively. An open software / distributed computing environment is implemented, resources on both the file / database server and the production control data server are managed by a directory service, and virtual programming is performed in the memory on the production control data server. It is characterized by securing a logic controller memory area and maintaining data synchronism by an event or data link function.

[0024]

According to the present invention, a virtualization model is provided for absorbing the differences in specifications between a plurality of different types of devices and the differences in network protocols, and the integrated interface means supports access to the virtualization model.

Here, the virtualization model includes a device model for absorbing a difference in specifications between the plurality of different types of devices and a network model for absorbing a difference in protocol of the network.

Further, the integrated interface means is
An access management unit that manages access to the virtualization model, a position management unit that manages the position of the device, and an interface control unit that controls an interface to the virtualization model are provided.

Further, in the present invention, the application that is the operation source is connected to the network through the integrated application programming interface, the first common or limited model, the first distributed computing environment, and the first network architecture, The real device to be operated is connected to the network via the real device interface, the second common or limited model, the second distributed computing environment, and the second network architecture.

Here, the integrated application programming interface includes processing request management means for managing processing requests from the application.

The first and second common or limited models each include an object entity and an object management means.

The first and second distributed computing environments provide an environment related to access to devices distributed and arranged on the network.

Further, the first and second network architectures perform communication management for providing various network protocol services to the first and second distributed computing environments.

The real device interface provides an interface for accessing the real device.

Further, in the present invention, a network operating system is mounted on each of the client, the file / database server, and the production management data server, and resources on both the file / database server and the production management data server are installed. Is managed by a directory service, a virtual programmable logic controller memory area is secured in the memory on the production management data server, and data synchronism is maintained by an event or data link function.

According to the present invention, the above client,
An open software foundation / distributed computing environment is mounted on each of the file / database server and the production control data server, and resources on both the file / database server and the production control data server are provided by a directory service. A virtual programmable logic controller memory area is secured in the memory on the production management data server, and data synchronism is maintained by an event or data link function.

[0035]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT An embodiment of a distributed production apparatus according to the present invention will be described below in detail with reference to the drawings.

First, the basic structure of the distributed production apparatus of the present invention will be described.

The distributed production apparatus of the present invention has the following configuration.

1) Virtualization of device access In order to absorb the differences in specifications of real devices that are the target of operation, a device model that is sufficiently virtualized is provided, and for this virtualized device model, Configure to access.

2) Virtualization of network access In order to absorb the difference in each network protocol, a sufficiently virtualized network model is provided, and the virtualized network model is accessed.

3) Virtualization viewed from application Supports access to a virtualized network model and device model, and is configured so that it is not necessary to be aware of the difference in location of each device and the difference in device. . Specifically, it provides access mechanisms for network and device models, device location management functions, and simple program interface specifications.

FIG. 1 shows a schematic system configuration of a distributed production apparatus according to the present invention based on the basic configuration of the present invention. In FIG. 1, this distributed production apparatus is
The operation source is an application (AP) 100, an integrated application programming interface (integrated API) 200, a virtualization model 300, and a real device 400 that is an operation target.

Here, the virtualization model 300 comprises a device model 300a and a network model 300b. The device model 300a enables virtualization of device access, and the network model 300b is network access. It enables the virtualization of.

That is, the device model 300a is sufficiently virtualized in order to absorb the difference in the specifications of the real device 400 to be operated, and the application 100 replaces this real device 400 with this device. Access the model 300a.

The network model 300b is sufficiently virtualized to absorb the difference in network protocol, and the application 100 is
This network model 30 instead of the real network
Access 0b.

The integrated application programming interface 200 enables virtualization as seen from the application.
00 supports access to the device model 300a and the network model 300b. With this support, from the application 100 side, the location of the real device 400 and the real device 40
Be able to operate without being aware of the 0 specification.

FIG. 2 shows an example of architecture for embodying the configuration shown in FIG.

The architecture shown in FIG. 2 is for exchanging data between the application 100 which is the operation source and the real device 400 which is the operation target via a network. The application 100 has an integrated application programming interface ( Integrated AP
I) 11, a common model or limited model 12, a distributed computing environment 13, and a network architecture 14 are provided. On the real device 400 side, a real device interface 21, a common model or limited model 2 is provided.
2. A distributed computing environment 23 and a network architecture 24 are provided.

This architecture exists to guarantee portability and interoperability and provide location transparency to the application 100 in an environment where various devices are scattered on the network.

The respective layers will be described below.

1) Integrated Application Programming Interface (Integrated API) The integrated application programming interface 11 is a layer for managing processing requests from the application 100 or the functional component 10, and executes the following functions. a) grammatical check on processing request (processing request from application 100 or functional component 10) b) existence check of destination included in processing request (processing request from application 100 or functional component 10) c) object management, library, etc. The response from is converted into a format understandable to the application 100 or the functional component 10. d) Execution of access to objects, etc.

2) Common or Limited Models The common or limited models 12 and 22 are layers for managing object entities and objects, and execute the following functions. a) Object model entity definition b) Model access management (integrated API 11, distributed computing environment 13, 23, access from actual device interface 21) c) Object model entity (data, etc.) synchronous management d) Model Perform conversion between

Here, a concrete example of the common or limited model is as shown in FIG. 3 or FIG.

The model shown in FIG. 3 shows an example of a virtual file model. The virtual file model 30 is a file database 41 of the real device 40 which is the operation target.
Has a virtual file database section 31 corresponding to, a virtual memory section 32 corresponding to a memory (such as a PLC memory) 42 of the real device 40, and a virtual / real device mapping section 33. Using this virtual file model 30,
By accessing the virtual file model 30, the application 100, which is the operation source, can substantially access the real device 40.

The model shown in FIG. 4 is a common model and CS.
It shows an example of a VMD model (virtual production model) in combination with a (companion standard) model. In this case, three programmable logic controllers PLC1 to PLC3, three communication devices RC1 to RC3, and three numerically controlled machine tools N are to be operated.
C1 to NC3 are assumed, and the programmable logic controller PLC, which constitutes a CS model / actual device mapping unit, in the CS model 30b, respectively.
1-PLC3 corresponding to the PLC-VMD unit 36-1, RC1-VMD corresponding to the communication device RC1-RC3 36-
2, NC-compatible with numerical control machine tools NC1 to NC3
The VMD unit 36-3 is provided, and the common model 30a is provided.
Includes a virtual PLC-VMD unit 34-1, RC-VMD corresponding to the PLC-VMD unit 36-1 of the CS model 30b.
Virtual RC-VMD section 34-2, N corresponding to section 36-2
Virtual NC-VMD unit 3 corresponding to C-VMD unit 36-3
4-3, a common model / CS model mapping unit 35 is provided.

When this VMD model is used, the application 100 which is the operation source accesses this VMD model, so that the actual devices PLC1 to PLC1 are substantially
It becomes possible to access C3, RC1 to RC3, NC1 to NC3.

3) Distributed Computing Environment The distributed computing environments 13 and 23 are layers that support the call function between the operation source and the real device by using the network architectures 14 and 24, and connect to devices scattered in the network. To provide an environment for access. As an example of this distributed computing environment,
There are the following: a) OSF / DCE (Open Software Foundation / Distributed Computing Environment) b) OSI (Open Systems Interconnection) 7 layers (MMS
(Production message service) + DS (directory service) + Service management / conversation management (message procedure management, resource information management)

4) Network Architecture The network architectures 14 and 24 are layers for performing communication management, and correspond to the network architecture portion from the first layer to the fifth layer of the OSI reference model. The network architectures 14 and 24 provide various protocol (transport layer, network layer, etc.) services to the distributed computing environments 13 and 23 through interfaces. Note that examples of this interface include a TDI and a NetBIOS interface.

5) Real Device Interface The real device interface 21 is the real device 400.
A layer that provides an interface for access to
It performs the following functions. a) Creation of message packet for real device access, disassembly b) Generation of object, access, etc.

6) Application The application 100 may be a tool software CIM construction tool in addition to the user application.

7) Real Device The real device 400 is a file database, PLC.
(Programmable logic controller) Main unit, NC
(Numerical control machine tool), RC (communication device), etc. are considered.

FIG. 5 shows an embodiment of the distributed production apparatus according to the present invention.

In FIG. 5, this embodiment is a second network in which a plurality of clients 501 to 503, which are terminals for each business, and a file / database server 504 are connected to a network 500 which is a first network. A plurality of programmable logic controllers (PLC) 511 to 513 are connected to the network 510, the network 500 and the network 510 are connected via a production management data server 520, and the file / database server 504 stores the data. Device 50
5 is connected.

Here, the network 510 is a factory interface network service (FI).
NS), C-mode link (SLK, trade name of OMRON Corporation), etc. that handles C mode commands and the like can be used.

In the above structure, the clients 501 to
A network operating system (NOS) is installed in each of 503, the file database server 504, and the production management data server 520. The resources on the file / database server 504 and the production management data server 520 are managed by the directory service (DS).

Further, in order to make the memory data of each programmable logic controller (PLC) 511 to 513 visible as a virtual file, the following configuration is added. 1) The virtual P is stored in the memory on the production management data server 520.
An LC memory area is secured, and data synchronization is maintained by an event or data link mechanism. 2) Put the server gateway software on the production control data server 520, and PLC by the virtual file mechanism.
When access such as reference or update to the memory is requested, the corresponding command is issued to the PLCs 511 to 513.

That is, according to such a configuration, as shown in FIG.
The common or limited models 12 and 22 shown in FIG. 2 are constructed by the virtual PLC memory area on the production management data server 520, and the distributed computing environment 1 shown in FIG.
3 and 23 are clients 501 to 503, files ...
Database server 504, production management data server 52
0 is built by the respective network operating system (NOS).

FIG. 6 shows an example of a data management table corresponding to the common or limited models 12 and 22 constructed in the embodiment of FIG. In the data management table shown in FIG. 6, each file name (data name) is associated with an address, length, unit, accessible range, and mission.

FIG. 7 shows the file / database server 504 and the production control data server 5 shown in FIG.
Directory Service (DS) for managing resources on 20
Is an example of the directory structure of. This directory structure has a tree structure. Each file server is associated with plan data and the like, and each PLC is associated with a main body, a unit, etc., and the main body is provided with a data memory (DM) and a user memory (UM). ), A contact, etc. are related, and input data, output data, etc. are related to the contact.

FIG. 8 shows another embodiment of the distributed production apparatus according to the present invention.

In FIG. 8, this embodiment is a second network in which a plurality of clients 601 to 603, which are terminals for each business, and a file / database server 604 are connected to a network 600 which is a first network. A plurality of programmable logic controllers (PLCs) 611 to 613 are connected to the network 610, the network 600 and the network 610 are connected via the process server 620, and the file / database server 604 has a storage device 605. Are connected.

Here, the network 610 is a factory interface network service (FI).
NS), C-mode link (SLK, trade name of OMRON Corporation), etc. that handles C mode commands and the like can be used.

In the above configuration, the clients 601-
603, the file / database server 604, and the process server 620 respectively include an open software foundation / distributed computing environment (OSF /
DCE) is implemented. Then, the resources on the file database server 604 and the process server 620 are managed by the directory service (DS) supported by the distributed computing environment (DCE).

Further, in order to make the memory data of each programmable logic controller (PLC) 611 to 613 visible as a virtual file, the following configuration is added. 1) A virtual PLC memory area is secured in the memory on the process server 620 so that data synchronization can be maintained by an event or data link mechanism. 2) The server gateway software is placed on the process server 620, and when access such as reference or update to the PLC memory is requested by the virtual file mechanism, the corresponding command is issued to the PLCs 611 to 613.

That is, according to such a configuration, as shown in FIG.
The common or limited models 12 and 22 shown in FIG. 2 are constructed by the virtual PLC memory area on the process server 620, and the distributed computing environments 13 and 23 shown in FIG.
It is constructed by the OSF / DCE installed in each of the clients 601-603, the file / database server 604, and the process server 620.

FIG. 9 shows still another embodiment of the distributed production apparatus according to the present invention.

In this embodiment, the client 700 as the operation source is connected to the local access library 702 and the remote access library 703 via the interface 701. Here, the interface 701 and the remote access library 703 are shown in FIG. Build the integrated API 11 shown.

A distributed computing environment (DCE) 704 is connected to the remote access library 703, and the distributed computing environment (DCE) 704 is connected to a transmission path 706 via a communication protocol 705.

Further, the transmission path 706 is provided with a distributed computing environment (DCE) via a communication protocol 711.
712 is connected.

In addition, the distributed computing environment (DC
E) 712 includes a local request object access mechanism 713 and a remote request object access mechanism 71.
4 is connected, and further, an object unit 715 and an object management unit 716 are connected to the remote request object access mechanism 714.

Here, the remote request object access mechanism 714, the object part 715, and the object management part 716 are the common or limited model 22 shown in FIG.
To build.

The object management section 716 is connected to the real device 720 via a real device interface (real device i / f) 717 which is a local interface.

In the above configuration, in this embodiment, a programmable logic controller (PLC) is assumed as the real device 720, and the client server is connected to the O server.
Implement SF / DCE. In addition, the server is CS-V
Implement MD (PC-VMD). Where the server is
A single PLC communication unit or a combination of a workstation (WS) and a PLC communication unit may be considered.

All resources on the network are managed by the Directory Service (DS) supported by the Distributed Computing Environment (DCE).

When the resource access is designated, the client judges whether it is local or remote by the directory service (DS), and when it is remote, DCE / R.
By PC, cooperate with DCE / RPC on the target server,
Call the required object module.

Object synchronism is maintained by object management and local interfaces. For that purpose, a configuration such as 1) object update by event from actual device, 2) object update by data link mechanism, and 3) data collection by event from object management is added.

It should be noted that this embodiment shows a configuration in which the model is not set as the operation source.

FIG. 10 shows still another embodiment of the distributed production apparatus according to the present invention.

In this embodiment, the common model 802 is connected to the client 800, which is the operation source, via the integrated API 801. A service management unit 803 is connected to the common model 802, and this service management unit 803
Includes an MMS conversation management unit 803a and a FINS conversation management unit 803b.

The service management unit 803 is a communication management unit 80.
4 is connected. Here, the communication management unit 804 uses the MMS
It comprises an API 804a and a FINSAPI 804b.

Here, the service management unit 803 and communication management unit 804 construct the distributed computing environment 13 shown in FIG.

The communication management unit 804 uses the communication protocol 80.
5 are connected to the transmission lines 806-1 to 806-3.

A communication management unit 812 is connected to the communication path 806 via a communication protocol 811. This communication management unit 812 uses MMSAPI 812a and FIN.
It is equipped with SAPI812b.

The communication management unit 812 is the service management unit 81.
3 is connected. This service management unit 813 uses MMS
Conversation management unit 813a and FINS conversation management unit 813b
It is equipped with.

Here, the communication management unit 812 and the service management unit 813 construct the distributed computing environment 23 shown in FIG.

The service management unit 813 uses the CS model 81.
4 and the CS model 814 is connected to the real device i.
Real device 8 via the access management unit 815 including / f
20 and 830.

Here, the CS model 814 and the access management unit 815 are the common or limited model 2 shown in FIG.
Build 2.

By the way, in this embodiment, different devices such as PLC, RC, and NC are assumed as actual devices, and CS-VMD (PC
In order to support (VMD), the common model 802 is implemented on the client side.

In this embodiment, in order to support the distributed environment using the message service as means, each station is equipped with a communication management unit, a conversation management unit and a service management unit.

In this embodiment as well, as in the embodiment shown in FIG. 9, the server is provided with the CS-VMD (PC-
VMD) is implemented. Here, the server is a PLC communication unit alone or a workstation (WS) and a PL.
A configuration in which C communication units are combined can be considered.

All resources on the network are managed by the directory service (DS) or object directory (OD) supported by the distributed computing environment (DCE).

In this embodiment, the client basically accesses the common model 802, but the local / remote judgment is made by the directory service (DS).
In the remote case, the message service is used to access the model of the partner server.

The synchronization of the object (model) is performed through the access management and the real device interface, and therefore, 1) the object update by the event from the real device 2) the object update by the data link mechanism 3) the event by the object management A configuration such as data collection is added.

[0103]

As described above, according to the present invention,
Since a virtualization model is provided to absorb the differences in specifications between a plurality of different types of devices and the differences in network protocols, and the integrated interface means is configured to support access to the above virtualization model, the following is shown. It produces such an effect.

1) Securing portability for applications, and improving portability and diversion of applications to be developed.

2) Ensure interoperability in the system, and at least user, SE (system engineer)
However, it provides an environment where you do not need to be aware of technical problems regarding the connection and operation of each device when building the system.

3) It enables a shift from access transparency to location transparency, and enables access to resources without notifying location information about resources scattered on the network.

4) Transition from real device access to common model access, and understanding of the common model enables similar access to any device.

[Brief description of drawings]

FIG. 1 is a diagram showing a schematic system configuration of a distributed production apparatus according to the present invention based on the basic configuration of the present invention.

FIG. 2 is a diagram showing an example of an architecture for embodying the configuration shown in FIG.

FIG. 3 is a diagram showing an example of a virtual file model corresponding to the common model or limited model shown in FIG.

FIG. 4 is a diagram showing an example of a VMD model corresponding to the common model or limited model shown in FIG.

FIG. 5 is a block diagram showing an embodiment of a distributed production apparatus according to the present invention.

6 is a diagram showing an example of a data management table corresponding to a common or limited model constructed in the embodiment of FIG.

7 is a diagram showing an example of a directory structure of a directory service (DS) that manages resources on the file database server and the production management data server shown in FIG.

FIG. 8 is a block diagram showing another embodiment of the distributed production apparatus according to the present invention.

FIG. 9 is a block diagram showing still another embodiment of the distributed production apparatus according to the present invention.

FIG. 10 is a block diagram showing still another embodiment of the distributed production apparatus according to the present invention.

FIG. 11 is a diagram in which the problems of the conventional device are arranged as factors that affect application development.

[Explanation of symbols]

11 integrated application programming interface (integrated API) 12 common model or limited model 13 distributed computing environment 14 network architecture 21 real device interface 22 common model or limited model 23 distributed computing environment 24 network architecture 30 virtual file model 30a common model 30b CS Model 31 Virtual file database unit 32 Virtual memory unit 33 Virtual / actual device mapping unit 34-1 Virtual PLC-VMD unit 34-2 Virtual RC-VMD unit 34-3 Virtual NC-VMD unit 35 Common model / CS model mapping unit 36 -1 PLC-VMD section 36-2 RC-VMD section 36-3 NC-VMD section 40 Actual device 41 File database 4 2 memory (PLC memory etc.) PLC1 to PLC3 programmable logic controller RC1 to RC3 communication device NC1 to NC3 numerical control machine tool 100 application (AP) 200 integrated application programming interface (integrated API) 300 virtualization model 300a device model 300b network model 400 Real device 500 Network (first network) 501 to 503 Client 504 File database server 505 Storage device 510 Network (second network) 511 to 513 Programmable logic controller (PLC) 520 Production management data server 600 Network (first Network) 601 to 603 client 604 file data Server 605 storage device 610 network (second network) 611 to 613 programmable logic controller (PLC) 620 process server 700 client (operation source) 701 interface 702 local access library 703 remote access library 704 distributed computing environment (DCE) 705 communication Protocol 706 Transmission line 711 Communication protocol 712 Distributed computing environment (DCE) 713 Local request object access mechanism 714 Remote request object access mechanism 715 Object part 716 Object management part 717 Real device interface (real device i
/ F) 720 Real device 800 Client (operation source) 801 Integrated API 802 Common model 803 Service management unit 803a MMS conversation management unit 803b FINS conversation management unit 804 Communication management unit 804a MMSAPI 804b FINSAPI 805 Communication protocol 806 Transmission line 806-1 806-3 Transmission line 811 Communication protocol 812 Communication management unit 812a MMSAPI 812b FINSAPI 813 Service management unit 813a MMS conversation management unit 813b FINS conversation management unit 814 CS model 815 Access management unit 820,830 Real device

─────────────────────────────────────────────────── ─── Continuation of the front page (51) Int.Cl. ⁶ Identification code Internal reference number FI Technical display location G05B 15/02 7531-3H G05B 15/02 M

Claims (11)

[Claims] 1. A distributed production apparatus in which a plurality of heterogeneous devices are distributedly arranged on various networks, and a virtualization model for absorbing a difference in specifications between the plurality of heterogeneous devices and a difference in protocol of the network, A distributed production apparatus comprising: an integrated interface unit that supports access to a virtualized model. 2. The virtualization model comprises a device model for absorbing a difference in specifications between the plurality of heterogeneous devices, and a network model for absorbing a difference in protocols of the network. The distributed production apparatus according to claim 1, which is characterized in that. 3. The integrated interface means includes access management means for managing access to the virtualization model, location management means for managing the location of the device, and interface control means for controlling an interface for the virtualization model. 2. The distributed production apparatus according to claim 1, further comprising: 4. A distributed production apparatus in which a plurality of heterogeneous devices are distributed and arranged on various networks, comprising an application as an operation source and an actual device as an operation target, wherein the application is an integrated application programming interface, A first common or limited model, a first distributed computing environment, connected to a network via a first network architecture, wherein the real device is a real device interface, a second common or limited model, a second distributed A distributed production apparatus connected to the network via a computing environment and a second network architecture. 5. The distributed production apparatus according to claim 4, wherein the integrated application programming interface comprises processing request management means for managing processing requests from the application. 6. The distributed production apparatus according to claim 4, wherein the first and second common or limited models include an object entity and an object management unit. 7. The distributed production apparatus according to claim 4, wherein the first and second distributed computing environments provide an environment related to access to devices distributed and arranged on the network. 8. The first and second network architectures perform communication management for providing various network protocol services to the first and second distributed computing environments. Distributed production equipment. 9. The distributed production apparatus according to claim 4, wherein the real device interface provides an interface for accessing the real device. 10. A first network is connected to a plurality of clients, which are terminals for each business, and a file / database server, and a second network is connected to a plurality of programmable logic controllers. In a distributed production apparatus in which the first network and the second network are connected via a production management data server, a network operating system is mounted on each of the client, the file / database server, and the production management data server. Resources on both the file / database server and the production management data server are managed by a directory service, and a virtual programmable logic controller memory area is secured in the memory on the production management data server, Other dispersing production apparatus characterized by holding the data synchronous with the data link function. 11. A first network is connected to a plurality of clients, which are terminals for each business, and a file database server, and a second network is connected to a plurality of programmable logic controllers. In a distributed production apparatus in which the first network and the second network are connected via a production management data server, open software / distributed computer is provided to the client, the file database server, and the production management data server, respectively. Implements a working environment, manages resources on both the file / database server and the production control data server by using a directory service, and secures a virtual programmable logic controller memory area in the memory on the production control data server. , Distributed production apparatus characterized by holding the data synchronism by an event or data link function.