WO2001002953A1 - Procede d'integration d'une application dans un systeme informatise - Google Patents

Procede d'integration d'une application dans un systeme informatise Download PDF

Info

Publication number
WO2001002953A1
WO2001002953A1 PCT/SE2000/001430 SE0001430W WO0102953A1 WO 2001002953 A1 WO2001002953 A1 WO 2001002953A1 SE 0001430 W SE0001430 W SE 0001430W WO 0102953 A1 WO0102953 A1 WO 0102953A1
Authority
WO
WIPO (PCT)
Prior art keywords
composite
interface
real world
composite object
request broker
Prior art date
Application number
PCT/SE2000/001430
Other languages
English (en)
Other versions
WO2001002953B1 (fr
Inventor
Johan Andersson
Mikael Rudin
Original Assignee
Abb Ab
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US09/348,017 external-priority patent/US6694513B1/en
Priority claimed from SE9902578A external-priority patent/SE516029C2/sv
Application filed by Abb Ab filed Critical Abb Ab
Priority to AU60428/00A priority Critical patent/AU6042800A/en
Priority to EP00946712A priority patent/EP1242877A1/fr
Publication of WO2001002953A1 publication Critical patent/WO2001002953A1/fr
Publication of WO2001002953B1 publication Critical patent/WO2001002953B1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/20—Software design
    • G06F8/24—Object-oriented
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/465—Distributed object oriented systems

Definitions

  • the present invention is concerned with a computerized system for control.
  • the present invention is a method for integrating many and varied types of applications within the computerized system, and the computerized system employing the method.
  • the method and the system may be used for controlling a number of single devices, an object in a process, a complete equipment, in any location including a home, as well as a process or an industrial installation such as a steel mill, a paper mill, and an automated factory.
  • a control system typically includes several computers connected through a communication network, where said applications are distributed in different configurations for different installations.
  • Traditional methods for this integration have entailed extremely lengthy development times resulting, for example, in significant changes in requirements before such control programs have been completed and made ready for use.
  • a second problem with traditional development methods is that it has been difficult and lengthy to update such control programs to include new requirements, such as the integration of additional and new applications .
  • Writing and modifying control system programs to combine newer applications with older, existing applications, which older applications are sometimes called legacy applications has also been difficult, time consuming and expensive.
  • IEC standard DIS ISO/IEC 1346-1 1995 Structuring principles and reference designations contains a reference designation system for the unambiguous identification of parts of any system in the general technical context such as in a manufacturing company, plant or operating company.
  • object, aspect and reference designations in particular are used to refer such parts of any system in the general technical context in accordance with the definitions in DIS ISO/IEC 1346- 1.
  • certain additional types of objects and aspects will be additionally defined in the course of this description.
  • US 5 787 425 describes a concept of client/server relationships between objects in an object-oriented computer program.
  • Objects communicate with each other, for example in order for a first object to access data held by a second object.
  • the first object needs access to some data controlled by the second object, the first object is considered to be a client of the second object, which in turn is considered to be a server.
  • the second object in this example, one of the operations of the first object, the client object, will call or invoke one of the operations of the server object.
  • the operation of the server object thus invoked is then executed to access and/or manipulate the data on behalf of the client object.
  • the server object When the client object and server object both exist and run in the same process (memory space) in the same computer, the server object is described as being "in process”. When the client and server objects run in different processes (memory spaces) in the same computer, the server object is described as being “local”. When the client and server objects run in separate computers, the server object is described as being “remote” .
  • ORB Object Request Broker
  • COM Component Object Model
  • COM is a standard for interoperability between software components introduced in 1993.
  • COM is independent of programming language and supported by many widely used computer operating systems such as Windows, Mac OS, and many types of Unix. It uses a single model for software components to communicate with each other, both inside the same computing process and also across process and network boundaries.
  • COM is also associated with ActiveX (Trademark), a system of software controls that use COM technologies .
  • ActiveX Trademark
  • the COM standard of 1995 is described in The Component Object Model Specification available in the Microsoft MSDN Online Library on the web site maintained by Microsoft. Additional information about COM may be found in, amongst others, an article in Dr.
  • a publication called COMponents by Steve Robinson and Alex Krassel of Panther Software discusses the use of COM objects in object-oriented programming.
  • the article discusses how to use object-oriented programming with known techniques. It presents an example of how a method of a first software object may be invoked by an application running in the same computer system by means of a COM compliant interface in the first software object. The method depends on the application having prior information about the first software object, information such as a CLSID, in order to establish a reference (such as a pointer) to the interface.
  • a method is described for the purpose of improved engineering of software, which means in other words writing software programs, in order to achieve faster performance and lower demand on system overheads .
  • the description of the method includes a terminal interface and a terminal mechanism for interfacing (software) objects.
  • the method also requires further information, a second data connection set, before it may be determined whether a method invokable by a first (software) object through a second (software) object, such as a new object, can participate in a connection and thus provide a method to or from the second (new) software object.
  • a new way to design systems is required to integrate applications, such that different applications can be both fully independent, based on different technologies, and without knowledge of the specifics of each other, and at the same time able to co-operate with each other to perform the collective functionality of the computerized system.
  • An object of the invention is to provide a method to integrate an application in a system for computerized control of a real world object, and a system in which the method is employed. Another object of the invention is a method to integrate an application such that prior information about the application need not be specified. Another object of the invention is to provide a method to represent real world objects in a computerized system in a systematic way, in which different types of information about the real world object may be obtained, linked to the real world object, processed, displayed and acted on, and a system employing same. Another object of the invention is the integration of a large range of applications within the system in a modular manner. Another object of the invention is to provide a method for the integration of later and additional applications into an existing system.
  • Another object of the invention is to provide for the integration of different applications that are implemented using different object and non-object oriented technologies.
  • Another object of the invention is to provide a system and method in which separate applications that are independent and without knowledge about the specifics of each other, are able to co-operate to jointly provide system functionality that is associated with said real world objects.
  • a further object of the invention is to provide a method and system in which control of equipment may be achieved in any location including a home or residence.
  • Composite Object is a part of a computer program included in the computerized system.
  • One or more facets of the real world object such as a physical location, a stage in a process, a control function, an operator interaction, a simulation model, some documentation about the object, etc are described as one or more Aspects of the Composite Object.
  • a central feature of the present invention is that each Composite Object is a container for one or more Aspects of the real world object which represent the real world object.
  • An important new and useful element of the present invention lies in that different applications may be used to implement different Aspects or groups of Aspects of a Composite Object.
  • Each application defines interfaces that are independent of the implementation of the application itself. These interfaces may be used by other applications, implementing other Aspects or groups of Aspects of the Composite Object, such that the applications can co-operate to provide a functionality that is the sum of all Aspects, i.e. the functionality of the Composite Object.
  • the interfaces are specified as COM interfaces, where COM interfaces are implemented by COM objects as described above.
  • the interfaces may be in-process, local, or remote.
  • each application may use any object oriented technology, such as C++ or Java, or non-object oriented technology such as relational databases, sequential files, etc..
  • Aspects Many different types of application may be used to implement Aspects. For example a word processing program may be used by one Aspect to display a functional specification, and by another Aspect to edit operator notes. Similarly a CAD program may be used by an Aspect to display a drawing, and used by another Aspect to display an electrical diagram or by a third Aspect to display a piping and instrumentation diagram. Application programs are not limited in any way to those programs used in traditional process control methods. For example a production management application may be used by one Aspect to display a job order, by another Aspect to run an equipment schedule or by a third Aspect to show material in stock.
  • the present invention thus provides important benefits in several respects including: i) for the developer of a system, who can integrate existing, new, and future possibly not yet anticipated applications, without having to significantly rewrite every application to fit with any particular data model or implementation technology, ii) for the user of the system, who will perceive a seamless integration of vastly different applications that co-operate to provide the full functionality that is associated with the real-world entities that he or she is dealing with and iii) for the owner of the system whose investment is protected because the system may be developed with, or extended by, applications not previously anticipated.
  • the applicability of the present invention is not limited to traditional process control functions and use, but extends as well to many other areas. This includes business and commercial activities such as production management, design and maintenance systems, and business and financial systems. It also includes control of equipment in other locations including equipment or processes in a residence or a home.
  • Figure 1 shows schematically a COM Object with interfaces according to a known standard, COM.
  • Figure 2a shows schematically a Composite Object and Aspects according to an embodiment of the present invention.
  • Figure 2b shows schematically an Aspect Type of an Aspect according to an embodiment of the present invention.
  • Figure 3 shows schematically the handling of a query by a Composite Object through an Aspect Type according to an embodiment of the present invention.
  • Figure 4 shows schematically a scheme of inheritance for Aspects of a Composite Object according to another embodiment of the present invention.
  • Figure 5 shows schematically inheritance for Aspects of a Composite Object in the same Structure according to a preferred embodiment of the present invention.
  • Figure 1 shows a COM object 5 with three known interfaces 1, 2, 3, and a standard interface 4, which interface is known within the COM model as IUnknown .
  • COM is an existing standard.
  • the COM object provides its services via methods, which are grouped into one or more interfaces.
  • Each interface such as interfaces 1- 3 of Figure 1, typically includes methods that supply a specific range of services.
  • a client object can invoke the methods defined by the COM object.
  • the set of interfaces that are supported by a specific COM object may change as the object undergoes revisions and updates, but any interface once defined always stays the same. In this way problems with versions and backwards compatibility are minimized. All COM objects support an interface which is named IUnknown.
  • This interface controls the life time of the object (through reference counting) and allows client objects to obtain information about other interfaces supported by the object.
  • the convention of IUnknown thus allows COM objects to interact without each object previously having information about every possible interface that may be supported by every other object.
  • Figure 1 illustrates a COM object 5 with several interfaces, which interfaces always include an instance of IUnknown.
  • a client object can query a standard COM object 5 for an interface, but in order to do that, the client object has to know the identity of the object (or application) for which it is seeking an interface. If the object supports the interface then a reference to the interface is returned as some form of pointer to where that interface may be found.
  • COM is a published standard and as such is a part of the prior art .
  • a Composite Object represents any real world object.
  • the real world object may be an actual object such as a pump, a motor, a valve, etc., or a more abstract object such as a purchase order, production batch, etc.
  • the present invention is not limited to traditional control or process control areas.
  • Any real world object may be represented, as an object in a process, including a device or process in a home for example, or a person carrying out a stage or role in a process, or intangible objects such as messages, a location, status of information etc..
  • FIG. 2a which shows a first software object, called a Composite Object 40 containing some Aspects 41.
  • Composite Object 40 is a container, holding different Aspectsl, 2, 19, 23 etc. related to the real world object.
  • An Aspect represents one facet of the real world object, and is responsible for all operations on that facet of the object and its data.
  • one Aspect could represent a physical location
  • another Aspect could represent a blue print diagram of the pump
  • another Aspect represents a control for an operation of the pump
  • yet another Aspect represents documentation about the pump.
  • the Aspect that represents the facet has an association to a function of an application that can, referring to the above example, display the blue-print diagram, or control the operation of the pump.
  • Composite Objects and Aspects communicate with each other using a "framework" based on an Object Request Broker such as COM with additions defined according to the present invention.
  • a set of interfaces are defined to allow Aspects to co-operate using standard services. Any individual Aspect may define additional interfaces, to allow for any specific interaction that may be required within a subgroup of Aspects .
  • An Aspect belongs to an Aspect Type (through its category) which lists the set of COM objects that implements the functionality of the aspect.
  • This implementation is provided by an object, referred to as an Aspect System Object (ASO) , which is a COM compliant object.
  • ASO Aspect System Object
  • the Aspect System Object is a second software object which has a specific function, to implement certain Aspects as described below, that is different to the function of the first software object, the Composite Object, the function of which is to represent a real world object by acting as a container for Aspects.
  • the Aspect Type contains the binding information between an Aspect and the one or more applications that implement its functionality.
  • the Composite Object may be queried by a client, through an Object Request Broker such as COM, to find a reference for an interface of the application associated with any of its Aspects.
  • an Object Request Broker such as COM
  • An Object Request Broker such as COM provides a mechanism to communicate a reference for a particular interface.
  • the "framework" provided by Composite Objects and Aspects provides the means to identify the particular interface that the Object Request Broker subsequently communicates.
  • Figure 2b shows a Composite Object 6, an Aspect Category 19a that Aspect 6a belongs to, and an Aspect Type 8 for the Aspect 6a according to an embodiment of the invention.
  • the Aspect Type 8 contains a listing of all Aspect System Objects used by this Aspect, expressed as a class identifier 9 (CLSID) of each ASO and a list of all interface identifiers 7 (IID) for interfaces supported by each ASO.
  • a CLSID such as CLSID 9, identifies a particular application, and, by this means, associates a function of the Aspect with the application that implements the function.
  • Figure 3 shows a Composite Object 10, which includes an interface IUnknown 4a. Also shown is an Aspect System Object 101, which includes another interface IUnknown 4b. Figure 3 also shows a query 13 for an interface and a reference 103 to an interface 102. From Figure 3 it is seen that when a client queries the Composite Object 10 for an interface, the reference 103 that is returned comes from the Aspect System Object 101. The ASO 101 is found through a table look-up using the Aspect Type, as shown in Figure 2b.
  • a Composite Object is uniquely identified through its object identifier.
  • An Aspect is identified by the object identifier of the Composite Object it is associated with, and a unique aspect identifier. If an object has a representation in different systems it uses the same object identifier in all systems.
  • a client of a Composite Object queries the object for an interface.
  • the Composite Object uses the definitions contained by the Aspect Type of the Aspects of the Composite Object to identify the Aspect System Object that implements the requested interface.
  • This ASO is then created and initialized from the Aspect it represents, or, if it is already running, found through a mechanism of locating running objects.
  • a reference to an interface of this ASO is then returned to the client.
  • a COM object is instantiated which represents the Composite Object.
  • the Composite Object which implements an interface of an Aspect is described thus.
  • the Composite Object examines its Aspects, including Aspect 6a, through the Aspect Category 19a, for an Aspect Type 8 which lists an ASO Description 8a that contains an interface identifier 7 of the requested interface. From the same ASO Description 8a the class identifier 9 of the Aspect System Object which implements the interface is obtained.
  • Figure 3 illustrates a request to a Composite Object for an interface.
  • Figure 3 shows a Composite Object 10 which receives query 13 from a client.
  • the Aspect Type 8 is searched, as shown in Figure 2b, to find the Aspect System Object class identifier 9.
  • the Aspect System Object 101 if not already running, is created as indicated by process 14 Initialization in Figure 3.
  • the instantiated Aspect System Object 101 is then queried through the interface IUnknown 4b for a reference to the interface 102, which reference 103 is returned to the client.
  • Aspect System Objects can be defined to be shared or exclusive. This specifies if a client requests an interface several times for the same Aspect, it will get the same interface reference to the object several times. If an Aspect System Object is shared then only one interface reference with a specific aspect identifier is created in each context (typically per process) .
  • An aspect system is an application that implements one or more Aspects, thus allowing Aspects instances to be created and added to Composite Objects
  • the aspect system defines (among other things) which COM objects are used to implement the Aspects .
  • a method to organize Composite Objects after one or more real-world relationships is included, which method is called Structures.
  • Any Composite Object in a system can be arranged in one or more Structures .
  • Composite Objects representing parts of one physical system may be conveniently grouped as a Structure.
  • Composite Objects representing a sensor attached to a blade of a stirring device, the shaft of the stirring device, a temperature sensor in the stirring device and a control unit for the stirrer, etc. may all additionally be identified as belonging to a particular Agitator Structure.
  • the Structure itself is represented as an entity that is separate from the included Composite Objects.
  • Each node in a Structure is represented by a structure Aspect of the Composite
  • Structures means that relations between Composite Objects are represented by Aspects of the Composite Objects. This allows a Composite Object to be represented in multiple Structures and even in multiple positions within one particular Structure. Structures allow Composite Objects to be organized and allows functions such as inheritance, sorting and grouping to be naturally defined.
  • a first object can inherit through a known mechanism of general inheritance by being defined as a child of a second object.
  • the child then inherits those aspects from its parent object (second object) that are marked as to-be-inherited.
  • Aspects refer to Aspect Categories, and through categories to Aspect Types.
  • Aspect systems, Aspect Types and Aspect Categories are all represented as Composite Objects.
  • a Composite Object 18 is a container for some Aspects, including Aspectl.
  • Aspectl refers to an Aspect Category 19.
  • Aspect2 and Aspect4 are marked as to-be-inherited. Because Composite Object 18 contains at least one Aspect from
  • Aspect Category 19 which in this example is Aspectl
  • Composite Object 18 will inherit all Aspects in Category 19 that are marked as to-be-inherited.
  • the Composite Object 18 thus inherits Aspect2 and Aspect4 automatically by means of the to-be- inherited indicator on those Aspects in the Aspect Category 19.
  • the mechanism described above works recursively.
  • the present invention also defines another new method of inheritance, shown schematically in Figure 5.
  • a Structure 20 includes a first Composite Object 25 and two other Composite Objects 26, 27 that are organized in the same Structure.
  • Composite Objects 26, 27 automatically inherit Aspect32 from Composite Object 25 because Aspect32 is marked as to-be-inherited by Composite Objects when organized subordinated in the same Structure.
  • This method of organization within a Structure may be based on any relationship, typically one that reflects a real world function, and is not limited to descriptions such as a class in a hierarchy.
  • the marker for "to-be-inherited-within-the-same- Structure" is placed in the Aspect Category of the respective Aspects .
  • a system employing a method according to the present invention may also take the form of a distributed system because it is designed using methods that facilitate communication between, and execution of, applications running on computers in a distributed system.
  • Distributed system here means a system that is spread over a plurality of computers, computer systems, computer networks, intelligent and non-intelligent devices that are arranged with communication devices so that each part of the system may communicate with any other part.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)
  • Computer And Data Communications (AREA)

Abstract

L'invention concerne un procédé permettant d'intégrer une application dans un système informatisé pour représenter un objet du monde réel, et un système utilisant ce procédé. L'objet du monde réel peut être n'importe quel objet, dispositif, procédé ou article d'un équipement, y compris un équipement d'une installation industrielle ou commerciale, dans un emplacement quelconque. L'objet du monde réel est représenté comme un premier objet logiciel, appelé objet composite, dans une partie d'un programme d'ordinateur. L'invention comprend aussi des aspects qui représentent les données et/ou les fonctionnements d'un objet composite. L'objet composite est un contenant renfermant au moins une donnée, représentant un aspect, de l'objet du monde réel. L'objet composite comprend une information conduisant à au moins une interface destinée à être utilisée par un autre objet, cette interface étant appliquée par un deuxième objet logiciel appelé objet système aspect et accédé par un négociant de requête d'objet, qui est conforme, par exemple, au COM. Le principal avantage de ce procédé et de ce système est que des applications dans le système n'exigent pas d'informations préalables à propos d'autres objets ou applications contenues dans le système. Une extension modulaire et simplifiée du système est possible, ainsi que l'intégration ultérieure d'applications non spécifiées au moment de la conception du système.
PCT/SE2000/001430 1999-07-06 2000-07-05 Procede d'integration d'une application dans un systeme informatise WO2001002953A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
AU60428/00A AU6042800A (en) 1999-07-06 2000-07-05 Method of integrating an application in a computerized system
EP00946712A EP1242877A1 (fr) 1999-07-06 2000-07-05 Procede d'integration d'une application dans un systeme informatise

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US09/348,017 1999-07-06
SE9902578-5 1999-07-06
US09/348,017 US6694513B1 (en) 1999-07-06 1999-07-06 Method of integrating an application in a computerized system
SE9902578A SE516029C2 (sv) 1999-07-06 1999-07-06 Förfarande system och datorprogram för integrering av en applikation i ett datorsystem

Publications (2)

Publication Number Publication Date
WO2001002953A1 true WO2001002953A1 (fr) 2001-01-11
WO2001002953B1 WO2001002953B1 (fr) 2001-02-08

Family

ID=26663613

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2000/001430 WO2001002953A1 (fr) 1999-07-06 2000-07-05 Procede d'integration d'une application dans un systeme informatise

Country Status (3)

Country Link
EP (1) EP1242877A1 (fr)
AU (1) AU6042800A (fr)
WO (1) WO2001002953A1 (fr)

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003032099A1 (fr) * 2001-10-05 2003-04-17 Abb Ab Transmission de messages dans un systeme
WO2003050680A2 (fr) * 2001-12-12 2003-06-19 Siemens Aktiengesellschaft Systeme et procede de communication entre des applications logicielles, en particulier des applications mes
WO2004053609A1 (fr) * 2002-12-12 2004-06-24 Abb Research Ltd Systeme de commande pour commander une pluralite d'objets du monde reel, et procede pour traiter des messages issus de l'utilisateur d'un mobile connecte au systeme de commande
WO2004057470A1 (fr) * 2002-12-19 2004-07-08 Abb Ab Requete distribuee d'objets du monde reel
WO2004057471A1 (fr) * 2002-12-19 2004-07-08 Abb Ab Acces a des objets composes sur la base de l'url
WO2004070491A2 (fr) * 2003-02-07 2004-08-19 Abb Research Ltd. Procede et systeme de gestion et d'extraction d'informations en matiere d'energie
WO2007066166A1 (fr) * 2005-12-08 2007-06-14 Abb Research Ltd Procede et systeme pour le traitement et l'affichage d'instructions de commande
EP1936548A1 (fr) * 2006-12-15 2008-06-25 Abb Research Ltd. Système de gestion d'effectif
DE112007000461T5 (de) 2006-02-24 2009-01-02 Abb Ab Kontrolle eines Objekts der realen Welt in verbundenen Systemen
DE112006003953T5 (de) 2006-07-11 2009-08-20 Abb Research Ltd. Ein Lebenszyklusmanagementsystem für intelligente elektronische Geräte
DE112008000526T5 (de) 2007-02-27 2010-01-07 Abb Research Ltd. Verfahren und System zum Erzeugen eines Kontrollsystembenutzerinterface
US7664815B2 (en) 2002-02-22 2010-02-16 Lars Gundersen Communication method and system
US7692537B2 (en) 2004-12-20 2010-04-06 Abb Ab Method and system for automatically deciding what alarm, generated in an industrial plant, to hide or to present to an operator
WO2013000506A1 (fr) 2011-06-28 2013-01-03 Abb Ab Transfert de responsabilité dans un environnement multisystème
EP3279755A1 (fr) 2016-08-02 2018-02-07 ABB Schweiz AG Procédé de surveillance d'une installation de traitement modulaire complexe avec une pluralité de modules de traitement interconnectés
EP3318935A1 (fr) 2016-11-08 2018-05-09 ABB Schweiz AG Procédé de fonctionnement d'un module de traitement dans une installation de traitement modulaire
US10303144B2 (en) 2014-08-11 2019-05-28 Abb Schweiz Ag Object creation in process control systems

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1997022925A1 (fr) * 1995-12-15 1997-06-26 Object Dynamics Corp. Dispositif, systeme et procede de conception et de construction de composants et systemes logiciels en tant qu'ensembles de pieces independantes

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1997022925A1 (fr) * 1995-12-15 1997-06-26 Object Dynamics Corp. Dispositif, systeme et procede de conception et de construction de composants et systemes logiciels en tant qu'ensembles de pieces independantes

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
STEVE ROBINSON, ALEX KRASSEL: "COMponents", PANTHER SOFTWARE, 8 August 1997 (1997-08-08), pages 1 - 24, XP002932729, Retrieved from the Internet <URL:http://www.panthersoft.com/> [retrieved on 20001004] *

Cited By (40)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7644152B2 (en) 2001-10-05 2010-01-05 Abb Ab Communication of messages in a system
WO2003032099A1 (fr) * 2001-10-05 2003-04-17 Abb Ab Transmission de messages dans un systeme
US7343605B2 (en) 2001-12-12 2008-03-11 Siemens Aktiengesellschaft System and method for communicating between software applications, particularly MES (manufacturing execution system) applications
WO2003050680A2 (fr) * 2001-12-12 2003-06-19 Siemens Aktiengesellschaft Systeme et procede de communication entre des applications logicielles, en particulier des applications mes
WO2003050680A3 (fr) * 2001-12-12 2004-07-22 Siemens Ag Systeme et procede de communication entre des applications logicielles, en particulier des applications mes
US7664815B2 (en) 2002-02-22 2010-02-16 Lars Gundersen Communication method and system
CN100409189C (zh) * 2002-12-12 2008-08-06 Abb研究有限公司 处理来自连接到控制系统的移动用户的消息的方法
WO2004053609A1 (fr) * 2002-12-12 2004-06-24 Abb Research Ltd Systeme de commande pour commander une pluralite d'objets du monde reel, et procede pour traiter des messages issus de l'utilisateur d'un mobile connecte au systeme de commande
US7873371B2 (en) 2002-12-12 2011-01-18 Abb Research Ltd. Control system controlling a plurality of real world objects, and a method for handling messages from a mobile user connected to the control system
WO2004057470A1 (fr) * 2002-12-19 2004-07-08 Abb Ab Requete distribuee d'objets du monde reel
CN100407145C (zh) * 2002-12-19 2008-07-30 Abb股份有限公司 基于统一资源定位符访问特征对象
US8185603B2 (en) * 2002-12-19 2012-05-22 Abb Ab Method for accessing a function of a real-world object
WO2004057471A1 (fr) * 2002-12-19 2004-07-08 Abb Ab Acces a des objets composes sur la base de l'url
US7877745B2 (en) 2002-12-19 2011-01-25 Abb Ab Distributed query of real world objects
US8396903B2 (en) 2003-02-07 2013-03-12 Abb Research Ltd. Method and system for organizing and retrieving energy information
WO2004070491A3 (fr) * 2003-02-07 2004-12-29 Abb Research Ltd Procede et systeme de gestion et d'extraction d'informations en matiere d'energie
WO2004070491A2 (fr) * 2003-02-07 2004-08-19 Abb Research Ltd. Procede et systeme de gestion et d'extraction d'informations en matiere d'energie
DE102005060696B4 (de) * 2004-12-20 2016-10-27 Abb Ab Verfahren und System zur automatischen Entscheidung, welcher Alarm, der in einer industriellen Fabrik generiert wird, einem Benutzer verborgen oder vorgelegt werden soll
US7692537B2 (en) 2004-12-20 2010-04-06 Abb Ab Method and system for automatically deciding what alarm, generated in an industrial plant, to hide or to present to an operator
WO2007066166A1 (fr) * 2005-12-08 2007-06-14 Abb Research Ltd Procede et systeme pour le traitement et l'affichage d'instructions de commande
DE112007000461T5 (de) 2006-02-24 2009-01-02 Abb Ab Kontrolle eines Objekts der realen Welt in verbundenen Systemen
US9678504B2 (en) 2006-02-24 2017-06-13 Abb Ab Real world object control in connected systems
US8443355B2 (en) 2006-07-11 2013-05-14 Abb Research Ltd. Life cycle management system for intelligent electronic devices
DE112006003953T5 (de) 2006-07-11 2009-08-20 Abb Research Ltd. Ein Lebenszyklusmanagementsystem für intelligente elektronische Geräte
EP1936548A1 (fr) * 2006-12-15 2008-06-25 Abb Research Ltd. Système de gestion d'effectif
US8479097B2 (en) 2007-02-27 2013-07-02 Abb Research Ltd. Method and system for generating a control system user interface
US9361002B2 (en) 2007-02-27 2016-06-07 Abb Research Ltd. Method for loading and displaying different process displays on a user interface of an industrial control system
US8356257B2 (en) 2007-02-27 2013-01-15 Abb Research Ltd. Method and system for generating a control system user interface
DE112008000512T5 (de) 2007-02-27 2010-04-08 Abb Research Ltd. Verfahren und System zur Erzeugung eines Kontrollsystembenutzerinterface
US8417357B2 (en) 2007-02-27 2013-04-09 Abb Research Ltd. Method and system for generating a control system user interface
DE112008000499T5 (de) 2007-02-27 2010-04-08 Abb Research Ltd. Verfahren zum Laden und Anzeigen verschiedener Prozessanzeigen auf einem Benutzerinterface eines industriellen Kontrollsystems
DE112008000526T5 (de) 2007-02-27 2010-01-07 Abb Research Ltd. Verfahren und System zum Erzeugen eines Kontrollsystembenutzerinterface
US9092122B2 (en) 2007-02-27 2015-07-28 Abb Research Ltd. Method and system for generating a control system user interface
US8332773B2 (en) 2007-02-27 2012-12-11 Abb Research Ltd. Method and system for generating a control system user interface
DE112008000527T5 (de) 2007-02-27 2010-01-14 Abb Research Ltd. Verfahren und System zum Erzeugen eines Kontrollsystembenutzerinterfaces
WO2013000506A1 (fr) 2011-06-28 2013-01-03 Abb Ab Transfert de responsabilité dans un environnement multisystème
US10303144B2 (en) 2014-08-11 2019-05-28 Abb Schweiz Ag Object creation in process control systems
EP3279755A1 (fr) 2016-08-02 2018-02-07 ABB Schweiz AG Procédé de surveillance d'une installation de traitement modulaire complexe avec une pluralité de modules de traitement interconnectés
US10528042B2 (en) 2016-08-02 2020-01-07 Abb Schweiz Ag Method of monitoring a modular process plant complex with a plurality of interconnected process modules
EP3318935A1 (fr) 2016-11-08 2018-05-09 ABB Schweiz AG Procédé de fonctionnement d'un module de traitement dans une installation de traitement modulaire

Also Published As

Publication number Publication date
WO2001002953B1 (fr) 2001-02-08
EP1242877A1 (fr) 2002-09-25
AU6042800A (en) 2001-01-22

Similar Documents

Publication Publication Date Title
US6694513B1 (en) Method of integrating an application in a computerized system
WO2001002953A1 (fr) Procede d&#39;integration d&#39;une application dans un systeme informatise
US6920457B2 (en) Virtual database of heterogeneous data structures
ES2207756T3 (es) Maquina generica de estado de software y metodo de construir objetos dinamicos para un programa de aplicacion.
US5926637A (en) Service interface repository code generation data
US5848273A (en) Method for generating OLE automation and IDL interfaces from metadata information
Nicol et al. Object orientation in heterogeneous distributed computing systems
US5793965A (en) Method and apparatus for determining the type of an object in a distributed object system
US6083277A (en) Filtering an object interface definition to determine services needed and provided
EP1299780B1 (fr) Gestion d&#39;outils automatisee dans un environnement multiprotocole
EP1770463B1 (fr) Association incrémentale de métadonnées avec des données de production
JP4429908B2 (ja) セントラルマスタデータ管理
US7478405B2 (en) Object connectivity through loosely coupled publish and subscribe events
US5884317A (en) Service interface repository
US5960421A (en) Service interface repository internationalization
US20030172368A1 (en) System and method for autonomously generating heterogeneous data source interoperability bridges based on semantic modeling derived from self adapting ontology
EP1653353A1 (fr) Association entre des données permanentes doublés
US7016918B2 (en) Object oriented data processing
US7478406B2 (en) Data access method for a control system
KR20020050160A (ko) 오브젝트 통합 관리 시스템
CN101151865B (zh) 多协议多客户端设备服务器
Silva et al. The agent pattern for mobile agent systems
Schmied et al. Vertical integration via dynamic aggregation of information in OPC UA
US7756963B2 (en) Automated tool management in a multi-protocol environment
WO2000042529A1 (fr) Systeme pour composer des applications sur la base de modeles semantiques explicites, d&#39;agents autonomes diriges par les evenements, et de serveurs mandataires de ressources

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ CZ DE DE DK DK DM DZ EE EE ES FI FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

AK Designated states

Kind code of ref document: B1

Designated state(s): AE AG AL AM AT AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ CZ DE DE DK DK DM DZ EE EE ES FI FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: B1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

B Later publication of amended claims
121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
REEP Request for entry into the european phase

Ref document number: 2000946712

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2000946712

Country of ref document: EP

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

WWP Wipo information: published in national office

Ref document number: 2000946712

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: JP

DPE2 Request for preliminary examination filed before expiration of 19th month from priority date (pct application filed from 20040101)