EP1461697A2 - Systeme et procede de communication entre des applications logicielles, en particulier des applications mes - Google Patents

Systeme et procede de communication entre des applications logicielles, en particulier des applications mes

Info

Publication number
EP1461697A2
EP1461697A2 EP02804564A EP02804564A EP1461697A2 EP 1461697 A2 EP1461697 A2 EP 1461697A2 EP 02804564 A EP02804564 A EP 02804564A EP 02804564 A EP02804564 A EP 02804564A EP 1461697 A2 EP1461697 A2 EP 1461697A2
Authority
EP
European Patent Office
Prior art keywords
mes
communication
applications
objects
object model
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
EP02804564A
Other languages
German (de)
English (en)
Inventor
Dirk Langkafel
Elmar Thurner
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Siemens AG
Original Assignee
Siemens AG
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
Application filed by Siemens AG filed Critical Siemens AG
Publication of EP1461697A2 publication Critical patent/EP1461697A2/fr
Ceased legal-status Critical Current

Links

Classifications

    • 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/54—Interprogram communication
    • G06F9/541—Interprogram communication via adapters, e.g. between incompatible applications

Definitions

  • the invention relates to a system for communication between software applications, in particular MES applications, with at least one means of communication, with at least one computer unit for storing the software applications and with at least one framework program coupling the software applications.
  • the invention relates to a related method, a computer program, a computer program product and a data processing device.
  • Manufacturing Execution Systems are systems that, for example, provide information for optimizing production processes.
  • the manufacturing execution systems have to supplement the rough planning data of the ERP systems with plant-specific and current detailed planning data and pass them on to the subordinate automation level.
  • they have the task of taking over production-relevant information from the automation level, preparing it and using it to report the company management level.
  • MES systems thus perform the task of vertical integration between the company management level and the automation level.
  • Typical individual tasks of MES systems are enterprise asset management, maintenance management, information management, scheduling ling, dispatching and trace & track. These tasks are carried out by MES components or MES applications.
  • US Pat. No. 5,557,798 describes a communication interface between software applications, via which the applications can communicate with high performance. The aim is to be able to develop the applications independently and in a modular manner.
  • No. 6,115,646 describes a process automation system based on a heterogeneous, distributed software system and an ORB (Object Request Broker).
  • ORB Object Request Broker
  • CORBA Common Object Request Broker Architecture
  • the aim of this invention is to provide workflow management services.
  • the object of the present invention is to provide a system and a method for communicating software applications, in particular MES applications, which allows in particular heterogeneous applications to be easily integrated and enables efficient data exchange between them.
  • MES applications software applications
  • the above object is achieved for a system by the features of claim 1.
  • the inventors started from the knowledge that the use of a framework (framework program) using standardized interfaces such as OPC (OLE for Process Control), ActiveX, XML (eXtensible Markup Language) or SOAP (Simple Object Access Protocol) made interoperability possible between heterogeneous software applications (e.g. MES applications).
  • OPC OPC
  • ActiveX ActiveX
  • XML eXtensible Markup Language
  • SOAP Simple Object Access Protocol
  • the principle "any data, any time, any where" is implemented for a user in an MES project (project for solving a task, eg order processing within an MES system).
  • MES project project for solving a task, eg order processing within an MES system.
  • a user has access to all data at all times, regardless of where they are in the system.
  • all objects and data of the applications appear in the framework program in a homogeneous manner, since the objects or the data of the applications are mapped to the object model (thus corresponds to a uniform, homogeneous meta-object model) of the framework program. This makes it easier to establish and manage a communication relationship between the applications.
  • a user can configure a communication relationship between applications and does not have to program it extensively.
  • a user receives a homogeneous view of the overall system and does not have to have any special (internal) knowledge of the application programs.
  • a first advantageous embodiment of the present invention for a system is that the communication relationship is transparent to a user and / or other systems of the underlying communication means. Due to the independence and transparency of the underlying communication means, e.g. HTTP (Hyper Text Transfer Protocol, COM, (Component Object Model), DCOM (Distributed Component Object Model), MSMQ (Microsoft Message Queue), from the configured communication relationship, a user can Configure a communication relationship from these commu abstract nicants. A user therefore does not have to worry about implementation details of these means of communication when configuring. Even when integrating or "connecting" the software applications to the framework program (for example by wrapping or using an adapter), users can abstract from the underlying means of communication and need not know any implementation details of the means of communication.
  • HTTP Hyper Text Transfer Protocol
  • COM Component Object Model
  • DCOM Distributed Component Object Model
  • MSMQ Microsoft Message Queue
  • a wrapper maps the API (Application Programmable Interface) of a third-party component (e.g. a MES application from a third party) into the object model of the framework program.
  • a method of the API of the external component becomes a method of the framework program, or an integer data type of the API of the external component becomes an integer data type of the framework program, etc.
  • COM objects Component Object Model
  • the creation of a wrapper for an is to be integrated Component can be automated.
  • a wrapper corresponds to a bridge. Wrappers can be realized very quickly.
  • Adapters are one level higher than wrappers. They offer a unified view of connected applications. An adapter offers functionality to start, operate, etc. the component to be coupled. An adapter corresponds to a "facade" in the language of the design pattern.
  • Another advantageous embodiment of the present invention for a system is that the communication relationship is established with a display device with input aids and / or via an independently working program. This increases the flexibility for a user who increases.
  • a communication relationship can be set up dynamically, ie at runtime.
  • the independently working program can be defined as a batch and used several times.
  • a further advantageous embodiment of the present invention for a system is that the communication relationship between two or more objects is established by connecting the objects, which are shown in different screen areas of the display device, by dragging and dropping with the aid of the input aids.
  • a suitable user interface e.g. with graphic support, drag & drop mechanisms, mouse input, voice input, etc.
  • the above object for a method is achieved by the features of claim 6.
  • the principle "any data, any time, any where" is implemented for a user in an MES project (project to solve a task, e.g. order processing within an MES system). That A user has access to all data at all times, no matter where they are in the system.
  • all objects and data of the applications appear in the framework program in a homogeneous manner, since the objects or the data of the applications are mapped to the object model (thus corresponds to a uniform, homogeneous meta-object model) of the framework program. This makes it easier to establish and manage a communication relationship between the applications.
  • a user can configure a communication relationship between applications and does not have to program it extensively.
  • a user receives a homogeneous view of the overall system and does not have to have any special (internal) knowledge of the application programs.
  • a further advantageous embodiment of the present invention for a method is that the communication relationship is transparent to a user and / or other systems of the underlying communication means. Due to the independence and transparency of the underlying means of communication, eg HTTP (Hyper Text Transfer Protocol, COM, (Component Object Model), DCOM (Distributed Component Object Model), MSMQ (Microsoft Message Queue) from the configured communication relationship, a user can A user does not have to worry about implementation details of these means of communication when configuring a communication relationship.
  • HTTP Hyper Text Transfer Protocol
  • COM Component Object Model
  • DCOM Distributed Component Object Model
  • MSMQ Microsoft Message Queue
  • a wrapper maps the API (Application Programmable Interface) of a third-party component (e.g. an MES application from a third-party provider) into the object model of the framework program.
  • a method of the API of the external component becomes a method of the framework program or an integer data type of the API of the external component becomes an integer data type of the framework program, etc.
  • COM objects Component Object Model
  • the creation of a wrapper for a component to be integrated can be automated.
  • a wrapper corresponds to a bridge.
  • Adapters are one level higher than wrappers. They offer a unified view of connected applications. An adapter offers functionality to start, operate, etc. the component to be coupled. An adapter corresponds to a "facade" in the language of the design pattern.
  • Another advantageous embodiment of the present invention for a method is that the communication relationship is established with a display device with input aids and / or via an independently working program. This increases the flexibility for a user.
  • a batch e.g. dynamic, i.e. a communication relationship can be established at runtime.
  • the independently working program can be defined as a batch and used several times.
  • a further advantageous embodiment of the present invention for a method is that the communication relationship between two or more objects is established by connecting the objects that are displayed in different screen areas of the display device using drag and drop with the aid of the input aids.
  • a suitable user interface e.g. with graphic support, drag & drop mechanisms, mouse input, voice input, etc.
  • Another advantageous embodiment of the present invention is that the method according to the invention is implemented by a computer program. This means that any modifications or adjustments can be made easily.
  • Another advantageous embodiment of the present invention is that the computer program for the method according to the invention is stored on a data carrier or a computer program product (floppy disk, CD, etc.). There- This makes the process regarding logistics and distribution easy to handle.
  • Another advantageous embodiment of the present invention is that the computer program for the method according to the invention is installed on a data processing device. This increases performance.
  • WinCC on a component as a meta object model of the framework program
  • FIG. 6 shows a further example for the mapping of an application (SAP) onto a component as a meta object model of the framework program
  • 7 shows a communication relationship between MES applications
  • FIG 10 screen areas for the configuration of a connection.
  • the illustration according to FIG. 1 shows an overview of the three control levels, as can usually be found in a manufacturing or manufacturing company.
  • the pyramid shape expresses that the information is compressed at the top.
  • the top level is the ERP level (Enterprise Resource Planning).
  • ERP level Enterprise Resource Planning
  • the business and sales tasks are usually carried out in a company (e.g. finance, sales, human resources, reporting), but also cross-production logistics tasks (e.g. order and material management) are carried out at this level.
  • the SAP R / 3 system is an ERP system that is used very frequently at the management level.
  • the lowest level of the pyramid is the automation level (controls).
  • controls programmable logic controllers
  • PLC programmable logic controllers
  • PLS visualization and process control systems
  • the drives, actuators and sensors of the production and / or manufacturing facilities are directly connected to the systems on this level.
  • the link between the ERP level and the automation level is formed by the MES level.
  • the applications at the MES level thus ensure vertical integration between the ERP level and the automation level.
  • the MES applications must supplement the rough planning of the ERP systems with production plant-specific detailed planning and forward them to the systems at the automation level; Management level).
  • Typical MES applications include Quality Management (QM), Maintenance Management (MM), Performance Analysis (PA), Process Management, Labor Management, Asset Management.
  • QM Quality Management
  • MM Maintenance Management
  • PA Performance Analysis
  • Process Management Labor Management
  • Asset Management Asset Management
  • MES systems or ERP systems usually contain a so-called runtime system for the temporal sequence control of the components involved (subcomponents, modules, tasks, processes of the operating system, etc.), as well as a so-called engineering system for creating and editing programs that are used for Execution in the runtime system are provided.
  • the illustration according to FIG. 2 shows an exemplary overview image with software and hardware units for MES solutions.
  • the individual MES applications AI to A3 are connected to a framework program (framework) IF via adapters AD1 to AD3.
  • a user workstation PIW1 is coupled to the framework program IF via a bidirectional information path II and can thus manage and monitor the MES applications which are attached or integrated thereon.
  • the user workstation PIW1 usually consists of a display device (monitor, display, etc.), a data processing system (for example a PC) with a processor and memory devices and input units (keyboard, mouse, etc.).
  • the MES applications AI to A3 and the framework program IF can run on their own data processing units or processors, however, it is also possible that they run on the data processing unit of the PIW1.
  • the respective MES applications AI to A3 are connected to the framework program IF via adapters AD1 to AD3.
  • the adapters are thus the coupling modules between the framework program IF and the applications. Applications that are heterogeneous per se can thus be connected to one another via the adapters, and integration with the framework program IF makes it possible to communicate between the applications and to exchange data.
  • the adapters are software modules that create connections to various applications. In typical integration scenarios, these are integrations to systems from the MES, ERP, SCADA or Controls world.
  • An adapter offers functionality to start and operate a component to be coupled, etc.
  • An adapter allows access to data and functions of the components to be coupled Application or application, provides certain runtime data and allows engineering information to be loaded from the application or application to be connected.
  • Adapters can differ in terms of their structure and scope. For example, adapters can be permanently programmed or they can be configured or modeled. They can also differ with regard to the possibilities of access to the application to be coupled, for example adapters can only allow data access, but it is also possible for adapters to allow access to higher-value business processes.
  • the adapters When starting up, the adapters are loaded with the stored models and status information. At runtime, it is then checked whether and how the different integrated applications or applications fit together. Using a visualization or monitoring component, it is possible to query the status of an adapter and to display it at the user workstation PIWl (also graphically). The system and the user receive a standardized and standardized adapter Before looking at applications (depending on which level of abstraction is available for the adapters).
  • a wrapper maps the API (Application Programmable Interface) of a third-party component (e.g. an MES application) into the object model of the framework program. For example, a method of the API of the external component becomes a method of the framework program or an integer data type of the API of the external component becomes an integer data type of the framework program.
  • API Application Programmable Interface
  • MES Application Programmable Interface
  • MES applications In addition to MES applications, applications from the corporate management level (Enterprise Resource Planning level) and / from the automation level (Controls level) can be integrated via the framework program IF and monitored or monitored via the workstation PIW1 (the acronym PIW stands for Personalized Industrial Workplace) . to get managed.
  • the framework program IF thus forms an integration platform for the entire industrial sector. Different applications from the management level, the MES level and the automation level can be easily and economically integrated with the framework program IF using adapters and / or wrappers.
  • the framework program IF can therefore be seen as a middleware platform and as a manufacturing application integration tool.
  • a user e.g. the plant operator
  • a user can see the respective states of the applications to be monitored via the workstation PIW1, and can also access data and methods of the applications, and can also use this access to connect applications with one another.
  • the framework program IF thus enables, on the one hand, vertical integration of applications from different company levels and, on the other hand, the framework program IF enables horizontal integration of applications at the MES level.
  • the PIWI workstation represents a "one window to the world" for a user on the front end of MES applications or other company applications. This means that the workstation enables integrative access to different, even heterogeneous, interfaces via a common, uniform interface Applications in the company.
  • the user of the workstation PIW1 can thus monitor and manage all integrated MES or other applications from this one workstation.
  • This workplace can be connected to the applications via the Internet, the intranet, LAN (Local Area Network) or other conceivable connections. It is also possible to design this workstation as a mobile station, for example as a mobile device (PDA, cell phone). This mobility would bring even more benefits to a user.
  • PDA Mobile Device
  • FIG. 3 shows the central position of the framework program coupling the software applications.
  • the framework program (IF; FIG 2) can be implemented on a single server or on any number of servers that can be distributed in an IT landscape.
  • FIG. 3 shows that the framework program (IF; FIG 2) is located on a server IFS (Industrial Framework Server).
  • the clients are connected to this central server IFS by the bidirectional information paths 12-18.
  • the clients include the applications from the ERP, MES and automation levels. These applications are shown at the bottom of the figure in FIG. These applications are connected to the framework program (IF; FIG 2) and thus to the server IFS via the adapters AD4-AD6.
  • the adapters AD4 - AD6 are connected to the applications via API interfaces API1 - API3 (API stands for Application Programmable Interface).
  • API Application Programmable Interface
  • An application programmable interface is an interface with a lot of commands.
  • APIs are also used for the implementation of pa Parameter lists from one format to another and when interpreting the arguments in one or both directions. The APIs are, so to speak, the glue between the applications and the adapters.
  • the connection between the adapters AD4 - AD6 with the framework program (IF; FIG 2) (shown in FIG. 3 by the bidirectional information paths 13 - 15) takes place via suitable data formats (eg XML), suitable protocols (XOP, OPC, etc. ) and suitable transport mechanisms (e.g. DCOM or MSMQ).
  • HTTP Hyper Text Transfer Protocol
  • SOAP Simple Object Access Protocol
  • XML eXtensible Markup Language XML eXtensible Markup Language
  • Clients or applications that support ActiveX documents or calls can be integrated particularly advantageously into the framework program (IF; FIG 2) or the server IFS.
  • the applications can also be connected to the framework program using wrappers or other integration mechanisms.
  • the repository IFR (Industrial Framework Repository) can be connected to the server IFS as a further client. 3 shows the connection through the bidirectional information path 12.
  • the IFR repository is used to keep data safe and persistent. This data can be accessed via method calls.
  • the repository includes Objects, methods and runtime data saved.
  • the Personalized Industrial Workplace PIW2 and any existing engineering environment EU are clients of the IFS server.
  • the Personalized Industrial Workplace PIW2 is connected by the bidirectional information path 16 to the framework program (IF; FIG 2) or to the server, the engineering environment EU accordingly by the bidirectional information path 17.
  • the three points show that other clients on the server IFS can hang.
  • FIG. 3 indicates that a further client C, connected by the information path 18, also hangs on the server IFS.
  • the clients IFR, PIW2, EU, C are connected accordingly via APIs or common data formats (e.g. XML), common protocols (XOP, OPC, etc.) and common transport mechanisms (e.g. DCOM, HTTP or MSMQ).
  • common data formats e.g. XML
  • common protocols XOP, OPC, etc.
  • common transport mechanisms e.g. DCOM, HTTP or MSMQ.
  • the adapters AD4 - AD6 used allow access to data and also to methods of the individual applications, which they connect to the framework program (IF; FIG 2). These adapters are very flexible and are not restricted to individual special protocols or special transport mechanisms. If the adapters are used in a runtime environment, they are configured to ensure that certain required data from an application is available in the server environment at the right time. As already mentioned, this can be done using different protocols and transport mechanisms. In a runtime environment there can be several adapters, which can also have small server properties (such as the execution of workflows, the provision of various communication options, ). These adapters can run on the respective application computer. Not only do they have to run on one machine, they can also be distributed.
  • MES applications Manufacturing Execution Systems
  • the system or method according to the invention makes it possible to integrate such heterogeneous applications with the aid of a framework program.
  • the communication between these applications takes place on the basis of communication means such as HTTP, DCOM, MSMQ, etc.
  • the communication, ie the data exchange between the applications is independent of these communication methods. teln, ie the applications can abstract from the application means.
  • the representation according to FIG. 4 shows the object structure of a "component” as a meta-object model of the framework program (IF; FIG. 2) in UML (Unified Modeling Language).
  • the software applications to be integrated and the underlying communication means e.g. HTTP, MSMQ, etc.
  • an object model of the framework program IF; FIG 2.
  • heterogeneous applications have a common object model.
  • This object model is very generic and represents a meta-object model.
  • the core of this object model consists of an object type called "Component".
  • a component can in turn aggregate other components and / or contain special types of components, so-called variables, to which certain values are assigned during operation. Components and variables can also have additional attributes.
  • This object model forms the basis for the adaptation of MES applications or other applications.
  • All applications to be integrated are represented within the framework program (IF, FIG 2) in the representation of this object model.
  • the underlying means of communication are also mapped to this generic object model.
  • In the framework program (IF; FIG 2) all applications and all underlying communication means are now represented in a uniform and homogeneous object model. This makes it very easy and easy to set up communication relationships between the applications. 4, the generic component "Component”, which represents the core of the object model, is shown in UML notation.
  • the rectangular boxes represent parts of the object model.
  • An aggregation is represented by a diamond relationship
  • inheritance is represented by a triangular relationship.
  • FIG. 4 thus shows that a component can consist of several components, furthermore a component can be part of another component.
  • a diamond is connected to a component with attributes and variables. This means that a component can contain attributes and variables. Attributes are descriptive data. All objects in a class have the same attributes, but generally different attribute values. An attribute value is a value assigned to an attribute from its value range.
  • a variable can take values of certain data types (e.g. integer, real etc.).
  • a component can contain several variables. However, a component can also be a superclass of a variable, as represented by the triangular relationship. That is, a variable can be a derived component.
  • the diamond and triangular relationships can also contain cardinalities.
  • mapping mechanisms such as The software applications to be integrated and the underlying means of communication to this generic object structure, i.e. "Component” structure, the framework program (IF; FIG 2) mapped.
  • WinCC is the name for a process monitoring system from Siemens
  • IF underlying framework program
  • the WinCC object model consists of namespaces (NS stands for Name Space) with so-called "tags".
  • Tags are simple data objects, the properties of which can be exchanged between servers and clients. Their properties can be dynamic, but also static.
  • tags can exist in a flat or a hierarchical namespace. Tags can also be assigned access rights (readable, writable, readable / writable).
  • a tag is a placeholder (proxy) for an object of an external application to be integrated.
  • tag is used in languages such as HTML or XML for markings.
  • the left-hand edge of FIG. 5 shows that the WinCC namespace (NS) contains tags 1 and tags 2. Three dots indicate that it can also contain other tags. This structure is mapped to the "component" structure of the meta-object model, as shown on the right-hand edge of FIG. 5, by means of adapters, wrappers or other mechanisms.
  • the namespace NS becomes the component NS, which contains tags 1 and tags 2 as variables. Three dots indicate that component NS can contain further elements. The chosen notation is based on the collaboration diagrams as they are known in UML.
  • FIG. 6 shows how a SAP application is mapped onto the "component" structure (meta-object model of the framework program). 6 is also shown by the centrally mounted arrow that a Abbil ⁇ dung or transformation is shown.
  • the table-like IDOC structure of SAP applications is shown on the left side of FIG. 6 shows the two entries S1 and S2 in the table. Furthermore, an arrow from S1 to S2 shows that there is a reference from the entry S1 to the entry S2.
  • the three dots indicate that an IDOC table can contain other elements.
  • An IDOC table is mapped to a component IDOC of the object model of the framework program (IF; FIG 2).
  • the entries in the table (S1, S2) are each mapped to variables of the component IDOC. The chosen notation is based on the collaboration diagrams as they are known in UML.
  • FIG. 7 shows how a communication relationship between the MES application is set up.
  • the applications and the underlying communication mechanisms are mapped to a uniform "component" structure (meta object model of the framework program).
  • FIG. 7 shows how a communication link between the MES applications MES ⁇ and MES ' ⁇ is set up.
  • the underlying means of communication (HTTP, MSMQ, DCOM, etc.) are also shown mapped to the generic object model of a "Componenf" structure using adapters or wrappers.
  • TS component transport system
  • This component Transport system (TS) abstracts from the underlying means of communication.
  • connection connects any two objects of the object model. Since the connection refers to objects of the generic object model, it knows their semantics and knows which special features are to be created when connecting, ie method objects are handled differently than, for example, pure data objects.
  • the connection is also based on a transport system. The transport system is also part of the generic object model of the framework program (IF; FIG 2).
  • a connection can be unidirectional or bidirectional.
  • Data flow diagrams can be used to configure the communication relationship between applications by connecting the nodes with corresponding data flows.
  • a connection is a generic object that essentially consists of two parts. On the one hand from the wrappers of the specific means of communication and on the other hand from a collection of properties, ie properties that can be set via this means of communication. These properties and the connection itself are in turn “components" of the object model, whereby the properties are simply given by a list of variables.
  • a transport wrapper also contains properties. If MSMQ is used as a means of communication, the name of the message queue used is one such property. The cardinality (1: 2) indicates that the connection from FIG. NEN, but contains at most two transport wrappers. The other aggregation relationships (diamond symbol), as shown in FIG. 8, can also contain cardinalities.
  • a transport wrapper can also include methods. For example, a method of opening a specific transport channel, a method of closing a specific transport channel, a method of sending a string, a method of receiving a string, etc.
  • Communication means are usually mapped to the object model of the framework program by wrappers, but in principle it is also possible to integrate communication means in the framework program by means of adapters.
  • FIG. 9 shows the basic structure of an adapter.
  • Each adapter is a special component with the special property that the component of an adapter runs in its own process.
  • Each adapter comes with a certain default structure, which is again represented as a tree structure of objects in the framework program, ie components and variables, and which provides certain places where the adapter can place certain information externally. Examples of this are status information about the status of the adapter (if the adapter is connected to its application, the application is running, version information, etc.).
  • an adapter can provide information about the external system, ie the external application.
  • the "Object Space" allows an adapter to lay out structures that other adapters or other applications can access.
  • An adapter can also provide information regarding a communication infrastructure to the outside.
  • Communication infrastructure is understood to mean objects to send, receive and transform messages. But also mechanisms for routing and mechanisms for logging the data exchange of the adapter.
  • the communication infrastructure of an adapter also includes so-called in- ports and outports that physically receive or send the messages.
  • An adapter is available as a separate process of the operating system, ie if an adapter crashes, it has no effect on other adapters. An adapter is therefore a separate, closed application that can be executed on its own
  • Adapters and wrappers are mechanisms for integrating software components into a software system.
  • a wrapper forms the API (Application Programmable Interface) of a third-party component or an application to be integrated into the object model of the software system, here the framework program (IF; FIG 2).
  • the framework program IF; FIG 2.
  • a method of the API of the application to be integrated becomes a method of the framework program or an integer data type of the API of the application to be integrated becomes an integer data type of the framework program, etc.
  • a wrapper thus brings the API of the application to be integrated into the language, into the nomenclature and the object world of the framework program.
  • An adapter is one level higher than a wrapper.
  • Adapters represent a standardized view of applications to be integrated, and the framework program in which the application to be integrated is hooked in can abstract from this application.
  • An adapter provides functionality to the system to be integrated, i.e. the application to be integrated, to start, to operate and to act. With the help of the adapter e.g. a user is using a SAP application without being a SAP expert.
  • SAP applications are mapped into the object model of the framework program and are then used as objects of the framework program (component IDOC).
  • two applications can be brought together peer-to-peer without such a connection being necessary. because it has to be programmed peer-to-peer.
  • These connections are configured according to the invention by establishing a connection (see FIG. 7).
  • the illustration according to FIG. 10 shows a configuration interface for setting up a communication link between applications.
  • the display device AZ e.g. a monitor or a display
  • the ML menu bars contain function buttons that the user e.g. can be activated with a click of the mouse. User-defined function buttons can also be stored in the ML menu bars.
  • the configuration interface can also be operated or activated using other input aids (e.g. keyboard, light pen or similar).
  • the configuration surface is divided into the screen areas BB1 - BB3. However, it is also conceivable that there are further or only one or two screen areas.
  • the object structures OB1, OB2 of the applications between which a communication relationship is to be set up are shown in the screen areas BB1 and BB2. However, it is also conceivable that only the structure of the respective adapter is shown in the screen areas BB1 and / or BB2. A user can now connect elements of the two object structures OB1, 0B2 to one another using drag & drop mechanisms. When a user establishes such a communication relationship, information relating to this connection or to the connections is displayed in a screen area BB3. Such information may refer to the name, value, or type of connection set up. It is also conceivable that further information relating to a connection is displayed.
  • the mechanism described in FIG. 10 makes it possible for a user to configure communication relationships between two applications. Communication relationships between two applications are therefore no longer necessary can be programmed individually. This increases the efficiency in the creation of software solutions for MES systems enormously, and system integrators and system developers in particular can increase their efficiency.
  • the system or method according to the invention described above can be implemented as a computer program in languages known therefor.
  • a computer program implemented in this way can also be stored and transported in a known manner via electronic data paths, but also on data carriers.

Landscapes

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

Abstract

Des applications (A1 - A3, MES', MES''), en particulier des applications MES, ainsi que des mécanismes de communication sont illustrés dans le modèle objet du programme-cadre au moyen d'enrouleurs et/ou adaptateurs (IF; IF désignant für Industrial Framework) et peuvent ainsi être manipulés de manière uniformément homogène dans le cadre (IF). L'invention est avantageuse en ce sens que les structures très hétérogènes des applications sont illustrées sur un modèle commun et peuvent être commodément et facilement utilisées par un utilisateur au moyen de mécanismes génériques. Cela signifie que la dépense mise en oeuvre pour la programmation est supprimée et que, de ce fait, cette communication peut être facilement projetée en établissant une connexion du type précité.
EP02804564A 2001-12-12 2002-11-28 Systeme et procede de communication entre des applications logicielles, en particulier des applications mes Ceased EP1461697A2 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
DE10161064A DE10161064A1 (de) 2001-12-12 2001-12-12 System und Verfahren zur Kommunikation zwischen Softwareapplikationen, insbesondere MES-Applikationen
DE10161064 2001-12-12
PCT/DE2002/004376 WO2003050680A2 (fr) 2001-12-12 2002-11-28 Systeme et procede de communication entre des applications logicielles, en particulier des applications mes

Publications (1)

Publication Number Publication Date
EP1461697A2 true EP1461697A2 (fr) 2004-09-29

Family

ID=7708952

Family Applications (1)

Application Number Title Priority Date Filing Date
EP02804564A Ceased EP1461697A2 (fr) 2001-12-12 2002-11-28 Systeme et procede de communication entre des applications logicielles, en particulier des applications mes

Country Status (4)

Country Link
US (1) US7343605B2 (fr)
EP (1) EP1461697A2 (fr)
DE (1) DE10161064A1 (fr)
WO (1) WO2003050680A2 (fr)

Families Citing this family (39)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9785140B2 (en) * 2000-02-01 2017-10-10 Peer Intellectual Property Inc. Multi-protocol multi-client equipment server
US8639542B2 (en) * 2002-06-27 2014-01-28 Siebel Systems, Inc. Method and apparatus to facilitate development of a customer-specific business process model
US7646725B1 (en) * 2004-03-02 2010-01-12 Nortel Networks Limited Self-healing containers
US8862570B1 (en) 2004-03-02 2014-10-14 Rockstar Consortium Us Lp Method and apparatus for open management of multi-media services
US7799273B2 (en) 2004-05-06 2010-09-21 Smp Logic Systems Llc Manufacturing execution system for validation, quality and risk assessment and monitoring of pharmaceutical manufacturing processes
US7444197B2 (en) 2004-05-06 2008-10-28 Smp Logic Systems Llc Methods, systems, and software program for validation and monitoring of pharmaceutical manufacturing processes
JP4410608B2 (ja) * 2004-06-04 2010-02-03 株式会社日立製作所 Ｗｅｂサービス提供方法
EP1699005A1 (fr) * 2005-03-01 2006-09-06 Siemens Aktiengesellschaft Integration de MES et ingenierie de contrôle
EP1880278A1 (fr) * 2005-05-13 2008-01-23 Abb Research Ltd. Maintien de la consistance des donnees entre des applications integrees
DE102006023105A1 (de) * 2006-05-16 2007-11-22 Bödger, Daniel Realisierungsnahe Simulation von Anlagen
US7822802B2 (en) 2006-09-29 2010-10-26 Fisher-Rosemount Systems, Inc. Apparatus and method for merging wireless data into an established process control system
US8380842B2 (en) 2007-04-26 2013-02-19 Mtelligence Corporation System and methods for the universal integration of plant floor assets and a computerized management system
US8036860B2 (en) * 2007-07-23 2011-10-11 International Business Machines Corporation Modeling homogeneous parallelism
EP2071580A1 (fr) * 2007-12-13 2009-06-17 Siemens Aktiengesellschaft Contrôle de la fermeture d'une application d'usine
EP2073155A1 (fr) * 2007-12-20 2009-06-24 Siemens Aktiengesellschaft Contrôle de la réexécution d'une branche de règles
DE102008047238A1 (de) 2008-09-09 2010-04-15 Khs Ag Frameworkbasierte Steuerung für Automatisierungssysteme
EP2237197A1 (fr) * 2009-03-31 2010-10-06 Siemens Aktiengesellschaft Procédé pour l'évaluation d'indicateurs de rendement clé (KPI) dans un système d'exécution de fabrication
US8863152B2 (en) * 2009-07-13 2014-10-14 Hewlett-Packard Development Company, L.P. Communication bridge
US8429671B2 (en) * 2009-10-21 2013-04-23 Exxonmobil Upstream Research Company Integrated workflow builder for disparate computer programs
US10909137B2 (en) 2014-10-06 2021-02-02 Fisher-Rosemount Systems, Inc. Streaming data for analytics in process control systems
US10386827B2 (en) 2013-03-04 2019-08-20 Fisher-Rosemount Systems, Inc. Distributed industrial performance monitoring and analytics platform
US10678225B2 (en) 2013-03-04 2020-06-09 Fisher-Rosemount Systems, Inc. Data analytic services for distributed industrial performance monitoring
US10649424B2 (en) 2013-03-04 2020-05-12 Fisher-Rosemount Systems, Inc. Distributed industrial performance monitoring and analytics
US9665088B2 (en) 2014-01-31 2017-05-30 Fisher-Rosemount Systems, Inc. Managing big data in process control systems
US10649449B2 (en) 2013-03-04 2020-05-12 Fisher-Rosemount Systems, Inc. Distributed industrial performance monitoring and analytics
US9558220B2 (en) 2013-03-04 2017-01-31 Fisher-Rosemount Systems, Inc. Big data in process control systems
US10282676B2 (en) 2014-10-06 2019-05-07 Fisher-Rosemount Systems, Inc. Automatic signal processing-based learning in a process plant
US10866952B2 (en) 2013-03-04 2020-12-15 Fisher-Rosemount Systems, Inc. Source-independent queries in distributed industrial system
US10223327B2 (en) 2013-03-14 2019-03-05 Fisher-Rosemount Systems, Inc. Collecting and delivering data to a big data machine in a process control system
US11112925B2 (en) 2013-03-15 2021-09-07 Fisher-Rosemount Systems, Inc. Supervisor engine for process control
EP3200131A1 (fr) 2013-03-15 2017-08-02 Fisher-Rosemount Systems, Inc. Studio de modélisation de données
US9535808B2 (en) 2013-03-15 2017-01-03 Mtelligence Corporation System and methods for automated plant asset failure detection
US9842302B2 (en) 2013-08-26 2017-12-12 Mtelligence Corporation Population-based learning with deep belief networks
US10168691B2 (en) 2014-10-06 2019-01-01 Fisher-Rosemount Systems, Inc. Data pipeline for process control system analytics
US10503483B2 (en) 2016-02-12 2019-12-10 Fisher-Rosemount Systems, Inc. Rule builder in a process control network
DE102017103017A1 (de) 2017-02-15 2018-08-16 Sig Technology Ag Verpackungsanlagendatenvermittlung sowie Verfahren zum Betreiben einer Verpackungsanlagendatenvermittlung
DE102017103018A1 (de) 2017-02-15 2018-08-16 Sig Technology Ag Verpackungsanlagendatenvermittlung sowie Verfahren zum Betreiben einer Verpackungsanlagendatenvermittlung
US20210335467A1 (en) 2020-04-22 2021-10-28 Iovance Biotherapeutics, Inc. Systems and methods for coordinating manufacturing of cells for patient-specific immunotherapy
DE102022200246A1 (de) 2022-01-12 2023-07-13 Robert Bosch Gesellschaft mit beschränkter Haftung System zum Anbinden einer Maschine an eine Fertigungslinie

Family Cites Families (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5557798A (en) 1989-07-27 1996-09-17 Tibco, Inc. Apparatus and method for providing decoupling of data exchange details for providing high performance communication between software processes
US5724532A (en) 1994-10-27 1998-03-03 Bay Networks, Inc. Method and apparatus for exchanging information between application programs according to a drag and drop operation
JPH0981486A (ja) 1994-11-17 1997-03-28 Texas Instr Inc <Ti> ソフトウェア・アプリケーション・プログラム間の共通の通信インターフェースを与えるオブジェクト指向型方法及び装置
US5995916A (en) * 1996-04-12 1999-11-30 Fisher-Rosemount Systems, Inc. Process control system for monitoring and displaying diagnostic information of multiple distributed devices
US6098116A (en) * 1996-04-12 2000-08-01 Fisher-Rosemont Systems, Inc. Process control system including a method and apparatus for automatically sensing the connection of devices to a network
US5909368A (en) * 1996-04-12 1999-06-01 Fisher-Rosemount Systems, Inc. Process control system using a process control strategy distributed among multiple control elements
US6032208A (en) * 1996-04-12 2000-02-29 Fisher-Rosemount Systems, Inc. Process control system for versatile control of multiple process devices of various device types
US6029181A (en) * 1996-09-26 2000-02-22 Honeywell, Inc. System and method for translating visual display object files from non-component object model (COM) objects to COM objects
US6687761B1 (en) * 1997-02-20 2004-02-03 Invensys Systems, Inc. Process control methods and apparatus with distributed object management
US6434435B1 (en) * 1997-02-21 2002-08-13 Baker Hughes Incorporated Application of adaptive object-oriented optimization software to an automatic optimization oilfield hydrocarbon production management system
US5890155A (en) * 1997-08-22 1999-03-30 Honeywell Inc. System and methods for providing encapsulated and performance-efficient data references in an object-oriented controller and distributed control system employing the same
US6621505B1 (en) * 1997-09-30 2003-09-16 Journee Software Corp. Dynamic process-based enterprise computing system and method
JP3162006B2 (ja) * 1997-11-10 2001-04-25 核燃料サイクル開発機構 抽出系のシミュレーション方法
US6115646A (en) 1997-12-18 2000-09-05 Nortel Networks Limited Dynamic and generic process automation system
US6240326B1 (en) * 1998-04-03 2001-05-29 Johnson Controls Technology Co. Language independent building automation architecture for worldwide system deployment
US6104963A (en) * 1998-04-03 2000-08-15 Johnson Controls Technology Company Communication system for distributed-object building automation system
US6167316A (en) * 1998-04-03 2000-12-26 Johnson Controls Technology Co. Distributed object-oriented building automation system with reliable asynchronous communication
US6119125A (en) * 1998-04-03 2000-09-12 Johnson Controls Technology Company Software components for a building automation system based on a standard object superclass
US6141595A (en) * 1998-04-03 2000-10-31 Johnson Controls Technology Company Common object architecture supporting application-centric building automation systems
US6208345B1 (en) * 1998-04-15 2001-03-27 Adc Telecommunications, Inc. Visual data integration system and method
US6138143A (en) * 1999-01-28 2000-10-24 Genrad, Inc. Method and apparatus for asynchronous transaction processing
US6789252B1 (en) * 1999-04-15 2004-09-07 Miles D. Burke Building business objects and business software applications using dynamic object definitions of ingrediential objects
WO2001002953A1 (fr) 1999-07-06 2001-01-11 Abb Ab Procede d'integration d'une application dans un systeme informatise
US7069101B1 (en) * 1999-07-29 2006-06-27 Applied Materials, Inc. Computer integrated manufacturing techniques
US7159185B1 (en) * 2000-09-14 2007-01-02 Microsoft Corporation Function objects
US6823495B1 (en) * 2000-09-14 2004-11-23 Microsoft Corporation Mapping tool graphical user interface
US7318015B2 (en) * 2001-06-13 2008-01-08 Verizon Business Global Llc Method, system and program product for generating scenarios utilizing graphical objects representing hierarchically arranged elements of a modeled environment
SG109956A1 (en) * 2001-06-19 2005-04-28 Eutech Cybernetics Pte Ltd Method and apparatus for automatically generating a scada system
US7146231B2 (en) * 2002-10-22 2006-12-05 Fisher-Rosemount Systems, Inc.. Smart process modules and objects in process plants

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
None *
See also references of WO03050680A3 *

Also Published As

Publication number Publication date
WO2003050680A3 (fr) 2004-07-22
US7343605B2 (en) 2008-03-11
US20050010931A1 (en) 2005-01-13
WO2003050680A2 (fr) 2003-06-19
DE10161064A1 (de) 2003-07-03

Similar Documents

Publication Publication Date Title
EP1461697A2 (fr) Systeme et procede de communication entre des applications logicielles, en particulier des applications mes
EP1456753B1 (fr) Systeme et procede de modelisation et/ou de realisation d&#39;applications logiciel, notamment d&#39;applications mes
DE69832354T2 (de) Netzwerkverwaltungsrahmenwerk
EP1454280B1 (fr) Systeme et procede de test et/ou de debogage de systemes d&#39;execution destines a resoudre des problemes mes
EP1061422B1 (fr) Système d&#39;ordinateur pour la définition, l&#39;optimisation et la régulation des processus
DE10206902A1 (de) Engineeringverfahren und Engineeringsystem für industrielle Automatisierungssysteme
EP1508093A2 (fr) Transformation d&#39;arbres d&#39;objets en particulier dans des systemes d&#39;execution de fabrication (mes)
EP2902857B1 (fr) Procédé de mise à disposition de fonctions au sein d&#39;un système d&#39;automatisation industriel et système d&#39;automatisation industriel
WO2003050716A2 (fr) Systeme et procede de projection de transformations effectues sur des arbres d&#39;objets
DE10206903A1 (de) Softwareapplikation, Softwarearchitektur und Verfahren zur Erstellung von Softwareapplikationen, insbesondere für MES-Systeme
WO2003050676A2 (fr) Systeme et procede de traçage et/ou d&#39;evaluation d&#39;un echange d&#39;informations
EP3594810A1 (fr) Infrastructure de système informatique ainsi que procédé d&#39;hébergement d&#39;un logiciel d&#39;application
EP2248012A1 (fr) Procédé et système pour intégrer des composants d&#39;automatisation orientés sur les services d&#39;un atelier de montage dans une architecture informatique d&#39;entreprise flexible
EP2648094B1 (fr) Procédé et système de production d&#39;un code source pour un programme informatique pour l&#39;exécution et la simulation d&#39;un processus
CH701481B1 (de) Prozessmanagement.
EP1202167B1 (fr) Méthode pour le développement orienté objet et basé sur un modèle d&#39;interfaces externes pour des systèmes de logiciel distribués
EP2620868A1 (fr) Système de gestion du flux de travail pour réseaux informatiques
DE10033812A1 (de) Verfahren zum Erzeugen von Informationsmodellen
DE102021101201A1 (de) Verfahren zum Einsetzen von Software-Stacks und computerlesbares Speichermedium
DE10109876B4 (de) Verfahren und Einrichtung zum Datenmanagement
EP4332772A1 (fr) Contrôleur capable data distribution service
DE202021106310U1 (de) Computerimplementiertes Prozessmodul
DE10138232A1 (de) System und Verfahren zum Verwalten von Softwareapplikationen, insbesondere MES-Applikationen
DE102008045272A1 (de) Vorrichtung und Verfahren zur Transformation eines Modells
WO2007045384A1 (fr) Serveurs d&#39;application orientes composants

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20040521

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR IE IT LI LU MC NL PT SE SK TR

RIN1 Information on inventor provided before grant (corrected)

Inventor name: THURNER, ELMAR

Inventor name: LANGKAFEL, DIRK

17Q First examination report despatched

Effective date: 20050216

17Q First examination report despatched

Effective date: 20050216

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20070323