EP1508093A2 - Transformation d'arbres d'objets en particulier dans des systemes d'execution de fabrication (mes) - Google Patents

Transformation d'arbres d'objets en particulier dans des systemes d'execution de fabrication (mes)

Info

Publication number
EP1508093A2
EP1508093A2 EP02804562A EP02804562A EP1508093A2 EP 1508093 A2 EP1508093 A2 EP 1508093A2 EP 02804562 A EP02804562 A EP 02804562A EP 02804562 A EP02804562 A EP 02804562A EP 1508093 A2 EP1508093 A2 EP 1508093A2
Authority
EP
European Patent Office
Prior art keywords
rules
transformation
trees
software system
objects
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
EP02804562A
Other languages
German (de)
English (en)
Inventor
Elmar Thurner
Dirk Langkafel
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
Siemens Corp
Original Assignee
Siemens AG
Siemens Corp
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, Siemens Corp filed Critical Siemens AG
Publication of EP1508093A2 publication Critical patent/EP1508093A2/fr
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Definitions

  • the invention relates to a system and a method for transforming object trees, in particular in MES systems, the source and target object trees being represented in a common meta object model of a software system, and the software system being stored on at least one computer unit.
  • the invention relates to a system and a method for projecting the above-mentioned transformation, as well as a corresponding computer program, a data carrier and a data processing device.
  • heterogeneous applications e.g. If MES applications are connected to one another, then the objects or object trees of the respective applications are usually represented in different ways in the meta model of the software system, even if the objects or object trees match semantically. This different representation makes communication between the applications difficult.
  • Manufacturing Execution Systems From “Software for automation - creating transparency about processes", article by ' Dirk Kozian in Electronics for Automation 11, November 17, 1999 is known for the automation of production or manufacturing processes so-called Manufacturing Execution Systems (MES) ' use. These systems integrate the automation level (controls) with the ERP systems (ERP: Enterprise Resource Planning) at the corporate management level. Manufacturing execution systems are systems that, for example, provide information for optimizing production processes. On the one hand, the manufacturing execution systems must use the rough planning data of the ERP systems in order to get plant-specific and current detailed planning Supplement data and forward it accordingly to the subordinate automation level. On the other hand, they have the task of taking production-relevant information from the automation level, preparing it and forwarding it to the 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, dispatching and trace & track. These tasks are carried out by MES components or MES applications.
  • XML eXtensible Markup Language
  • the XML family defines a standard procedure for transforming XML documents: XSL Transformations (XSL stands for Extensible Stylesheet Language). Tree transformations can also be described with XSL Transformations, but only if the objects of the trees are in XML format and the respective XML format is known to a user. If a user has a If you want to transform an object tree, you need the associated representation of the objects in XML format and you must define the transformation at the XML level. This means effort, because the user must first get the corresponding XML formats of the objects.
  • the object of the underlying invention is to provide a system and a method which make it possible to carry out transformations of object trees directly at the domain level of the user, the definition of the transformations being convenient and simple for the user.
  • the above object is achieved for a system by the features of claim 1.
  • the transformation of the objects or the object trees takes place in the domain world of the user, i.e. the user can abstract from the underlying format of the objects.
  • Another advantage is the transformation of object structures into a form that is understandable for recipients (e.g. other applications) of these object structures. It is often the case that semantically identical objects (e.g. a production order) are represented differently in a common meta object model.
  • the transformations also create uniform representations for objects with the same semantics. This enables communication between different applications via a pure data exchange.
  • a first advantageous embodiment of the present invention for a system is that a user can carry out the transformation in the underlying domain. If the transformation takes place directly at the domain level of the user, the user can abstract from the internal formats of the objects or object trees. The effectiveness of a user is increased because the user known world (known nomenclature, known objects etc.) in the creation of solutions. A user therefore does not have to transform the objects to be transformed at the level of their internal format and then translate them back into the domain world.
  • the rules are represented as objects of the software system.
  • the objects appear to a user as part of the software system.
  • a user can also handle the rules like objects, e.g. link graphically.
  • Another advantageous embodiment of the present invention for a system is that the rules can be defined by the user. This increases the flexibility for a user and a user can define rules that are appropriate for the underlying structures and problems.
  • Another advantageous embodiment of the present invention for a system is that operators and / or already existing rules can be used to define the rules. This makes it easier for a user to create and / or change rules.
  • a framework defines the architecture of a family of software systems, provides the basic building blocks for creating these systems and determines their interaction. Frameworks save development time and costs.
  • a framework defines the architecture of a family of software systems, provides the basic building blocks for creating these systems and determines their interaction. Frameworks save development time and costs.
  • Another advantageous embodiment of the present invention for a system is that the source and target object tree are specified by the object models of the adapters. Adapters are one level higher than wrappers. They offer a unified view of connected applications. An adapter offers functionality to start, operate, etc. the components to be coupled. An adapter corresponds to a "facade" in the language of the design pattern.
  • 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 a software system. For example, a method of the API of the third-party component becomes a method of the software system or an integer data type of the API of the third-party component becomes an integer data type of the software system, etc.
  • the objects of the applications to be integrated are integrated into the meta-object using adapters. project model of the software system and represented in the meta object model as the source or target object tree. If the adapters now specify the structure of these trees, a subsequent transformation from source to target object tree can be carried out very easily, possibly even automatically.
  • the above-mentioned object for a system for projecting transformations of object trees is achieved by the features of claim 8.
  • the configuration environment for defining the transformations supports the user very efficiently. A user then no longer has to program, but can configure the transformations.
  • configuration environments with a graphical user interface and / or drag-and-drop mechanisms for connecting objects are very convenient for a user.
  • the above object is achieved for a method by the features of claim 9.
  • the transformation of the objects or the object trees takes place in the domain world of the user, ie the user can abstract from the underlying format of the objects.
  • Another advantage is the transformation of object structures into a form that is understandable for recipients (eg other applications) of these object structures. It is often the case that semantically identical objects (eg a production order) are represented differently in a common meta object model.
  • the transformations also create uniform representations for objects with the same semantics. This enables communication between different applications via a pure data exchange.
  • a first advantageous embodiment of the present invention for a method is that a user carries out the transformation in the underlying domain. If the transformation takes place directly at the domain level of the user, the user can abstract from the internal formats of the objects or object trees. The effectiveness of a user is increased because he is in his known world (known nomenclature, known objects, etc.) when creating solutions. A user therefore does not have to transform the objects to be transformed at the level of their internal format and then translate them back into the domain world.
  • the rules are represented as objects of the software system.
  • the objects appear to a user as part of the software system.
  • a user can also handle the rules like objects, e.g. link graphically.
  • Another advantageous embodiment of the present invention for a method is that the rules are defined by a user. This increases the flexibility for a user and a user can Define rules that are appropriate for the underlying structures and problems.
  • Another advantageous embodiment of the present invention for a method is that operators and / or already existing rules are used to define the rules. This makes it easier for a user to create and / or change rules.
  • a framework defines the architecture of a family of software systems, provides the basic building blocks for creating these systems and determines their interaction. Frameworks save development time and costs.
  • 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.
  • 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 a software system.
  • a method of the API of the third-party component becomes a method of the software system
  • an integer data type of the API of the third-party component becomes an integer data type of the software system, etc.
  • the objects of the applications to be integrated are converted into the meta-object model of Software system and represented in the meta object model as a source or target object tree. If so the adapters specify the structure of these trees, a subsequent transformation from source to target object tree can be done very easily, possibly even automatically.
  • the above-mentioned object for a method for projecting transformations of object trees is achieved by the features of claim 16.
  • the configuration environment for defining the transformations supports the user very efficiently. A user then no longer has to program, but can configure the transformations.
  • configuration environments with a graphical user interface and / or drag-and-drop mechanisms for connecting objects are very convenient for a user.
  • 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. This makes the process easy to handle in terms of logistics and distribution.
  • 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.
  • 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 towards the top.
  • the top level is the ERP level (Enterprise Resource Planning).
  • ERP 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 company management level.
  • the lowest level of the pyramid is the automation level (controls).
  • 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; (Company management level).
  • Typical MES applications are a. 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
  • FIG. 1 three points each express that further elements (applications, systems, etc.) can be located on one level.
  • 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 over Adapter AD1 to AD3 connected to a framework program (Framework) IF.
  • a user workstation PIW1 is coupled to the framework program IF via a bidirectional information path 11 and can thus manage and monitor the MES applications 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, but 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, operate a component to be coupled, etc.
  • An adapter allows access to data and functions of the application or application to be coupled, provides certain runtime data and allows engineering information to be loaded from the application or Application. Adapters can differ in terms of their structure and scope.
  • adapters can be permanently programmed or they can be configured or modeled. They can also differ with regard to the options for accessing the application to be coupled. For example, adapters can only allow access, but it is also possible that adapters allow access to higher-value business processes.
  • the adapters When starting up, the adapters are loaded with the stored models and status information. It is then checked at runtime 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 display it at the PIW1 user workstation (also graphically). Adapters give the system and the user a standardized and uniform view of 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 eg the plant operator
  • a user can view the respective states of the applications to be monitored, and he can also access data and methods of the applications, and furthermore he can use this access to connect applications to 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 workstation PIW1 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, via a common, uniform user 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 use this workstation as a mobile station, e.g. to be designed 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 based on a server IFS (Industrial Framework Server) is located. On this central server IFS hang through the bidirectional Information paths 12-18 connected to the clients.
  • 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 when converting 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
  • the SOAP protocol (Simple Object Access Protocol) based on XML eXtensible Markup Language) can also be used for the integration of the adapters AD4-AD6 into the framework program (IF; FIG 2) or the associated server IFS.
  • 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. Via method calls this data can be accessed. Objects, methods and runtime data are stored in the repository.
  • 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 it is indicated 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 means of communication such as HTTP, DCOM, MSMQ, etc.
  • the communication, ie the data exchange between the applications is independent of these means of communication, ie the applications can abstract from the application means.
  • FIG. 4 shows an example of the transformation of objects or object trees.
  • semantically identical objects can be represented differently.
  • the diagram according to FIG. 4 schematically shows the surface of a configuration environment for transforming objects or object trees with a display device AZ 1.
  • the object trees shown in the screen areas BB1 and BB2 represent semantically identical objects (for example a production order), but are represented differently .
  • the source tree QB consists of a root 1 and an underlying element 2, which in turn has sub-elements S1 and S2.
  • the target tree ZB has 1 as the root and 2 ⁇ and 2 ⁇ as the underlying elements.
  • Element 2 is connected to element S1 , element 2 ⁇ to element S2.
  • the tree representations QB or ZB belong to applications (e.g. MES applications) that are mapped to the meta-model of the underlying software system (e.g. frameworks) using adapters. Because the two tree structures, although they are semantically the same objects represent, are represented in a different form in the meta-object model, communication between the applications to which they belong is not yet effectively possible in this form. Effective communication is made possible by mapping one object tree onto the other. 4, the source tree QB is transformed into the tree ZB. How this transformation takes place is shown in screen area BB3.
  • the elements S1 and S2 represent objects (eg variables) that have the same meaning in the two trees QB and ZB.
  • the screen area BB3 shows how a transformation can be carried out, which expresses that the objects S1 and S2 of the source tree QB and the target tree ZB belong together semantically.
  • the display device AZ1 can contain a menu bar ML1 as a further screen area, on which functions (for example by buttons) are shown that a user can use for the transformation.
  • a monitor or a display is usually used as the display device.
  • input aids such as a mouse or keyboard, a user can operate and activate the elements of the display device.
  • the display device AZ1 can also contain further screen areas. For example, it is also conceivable for the screen area BB3 to be subdivided further, but there may also be further menu bars ML1.
  • transformations Once transformations have been defined by the user, they can be saved and used again for later applications. A user can also define rules to perform these transformations. A user can also save these rules and use them again for later transformations. It is also conceivable that a rule becomes part of the meta object model of the underlying software system and is then available to a user as an object.
  • the rule objects mentioned are created automatically when a transformation is defined. Mathematical functions (addition, subtraction, sine, cosine, etc.), but also timers or other adapters (eg Excel) can be used to define transformations. Via drag and drop mechanisms the transformations and the rules can be created very easily.
  • the transformation described above converts two semantic representations (eg object trees) that have been brought into the meta-object model by the adaptation.
  • the objects or the object trees are mapped directly onto one another and not the representations of these objects in any format structures.
  • the transformation can thus take place in the domain world of the user, and a user can abstract from the internal representation of the objects, ie from the internal formats.
  • the configuration or engineering environment described here can be implemented, for example, as a client in a framework or in the software system. However, it is also possible for this environment to be implemented on a stand-alone PC.
  • the illustration according to FIG. 5 shows an example of the transformation of objects or object trees with the aid of mathematical objects.
  • the screen areas BB1 ⁇ and BB2 ⁇ contain object trees OB1 and OB2, which are to be converted into one another.
  • OB1 contains the component K1 in its structure as an element
  • OB2 contains the component K2 in its structure as an element.
  • a transformation is to be produced between these components K1 and K2 ⁇ .
  • Kl ⁇ contains the variables VI and V2
  • K2 x contains the variables S and D.
  • the menu bar ML2 shows operators, eg addition, subtraction, division, sine, which can be used to define a transformation. Additional mathematical operators can also be provided to define a transformation, such as multiplication, tangent, arc tan. gens, cosine, exponential function, logarithm, root function, signum, absolute function, etc.
  • timers can also be used to define transformations. Timers deliver, for example, the current time or definable time cycles, which can be manipulated using the mathematical operations mentioned, for example. For example, it is conceivable to add up values that come from a timer with other values and only then forward them.
  • the screen area BB3 * shows that the two variables VI and V2 of the component Kl and Kl ⁇ are added together.
  • the result of this addition (represented by the variable R1) is linked to the variable S of the component K2 ⁇ or K2.
  • a rule object is created that can also be used for later transformations.
  • These control objects can be stored and used, for example, in the communication structure of an adapter (see FIG. 6).
  • the connections for the transformation are automatically generated by the drag & drop-like connection of object trees to one another or objects of object trees by pushing them onto the work surface BB3 ⁇ . This means that this connection is created in the background for the objects to be connected.
  • FIG. 6 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.
  • 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 ports and outports, which 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, 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.
  • the IDOC adapter maps SAP applications into the object model of the framework program and is then used as objects of the framework program (component IDOC).
  • two applications e.g. MES applications
  • MES applications can be brought together peer-to-peer without such a connection having to be programmed peer-to-peer.
  • These connections are configured according to the invention by establishing a connection.
  • the rules used in the transformation can be part of an adapter or the rules can be stored as information on an adapter and incorporated into the system.
  • FIG 7 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 system and method are used to map the software applications to be integrated and the underlying communication means (eg HTTP, MSMQ, etc.) to an object model of the framework program (IF; FIG 2).
  • the underlying communication means eg HTTP, MSMQ, etc.
  • 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.
  • 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.
  • Component which represents the core of the object model, in UML notation.
  • the rectangular boxes represent parts of the object model.
  • An aggregation is represented by a diamond relationship, by a triangular relationship the inheritance (is a relationship) is shown.
  • the illustration according to FIG. 7 thus shows that a component can consist of several components; furthermore, one 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 are based on this generic object structure, i.e. the adapter or wrapper. "Componenf 'structure, the framework program (IF; FIG 2) mapped.
  • the invention relates to a system and a method for transforming object trees, in particular in MES systems, the source and target object trees being represented in a common meta-object model of a software system, in particular a framework.
  • the source object tree is transformed into the target object tree by rules.
  • the transformation takes place directly on the objects of the meta object model (component).
  • This enables communication via pure data exchange between coupled applications.
  • 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)
  • Theoretical Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Economics (AREA)
  • Software Systems (AREA)
  • Educational Administration (AREA)
  • Game Theory and Decision Science (AREA)
  • Development Economics (AREA)
  • General Engineering & Computer Science (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Stored Programmes (AREA)

Abstract

L'invention concerne un système et un procédé de transformation d'arbres d'objets (OB1, OB2), en particulier dans des systèmes d'exécution de fabrication (MES). Selon ledit procédé, les arbres d'objets source (QB) et les arbres d'objets cible (ZB) sont représentés dans un méta-modèle d'objets commun d'un système logiciel, en particulier d'un cadre d'applications (IF). L'arbre d'objets source (QB) est transformé en l'arbre d'objets cible (ZB) par l'intermédiaire de règles. Cette transformation intervient directement sur les objets du méta-modèle d'objets (composant), ce qui permet une communication entre des applications couplées, au moyen d'un simple échange de données.
EP02804562A 2001-12-12 2002-11-28 Transformation d'arbres d'objets en particulier dans des systemes d'execution de fabrication (mes) Ceased EP1508093A2 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
DE10161115A DE10161115A1 (de) 2001-12-12 2001-12-12 Transformation von Objektbäumen, insbesondere in MES-Systemen
DE10161115 2001-12-12
PCT/DE2002/004374 WO2003050679A2 (fr) 2001-12-12 2002-11-28 Transformation d'arbres d'objets en particulier dans des systemes d'execution de fabrication (mes)

Publications (1)

Publication Number Publication Date
EP1508093A2 true EP1508093A2 (fr) 2005-02-23

Family

ID=7708991

Family Applications (1)

Application Number Title Priority Date Filing Date
EP02804562A Ceased EP1508093A2 (fr) 2001-12-12 2002-11-28 Transformation d'arbres d'objets en particulier dans des systemes d'execution de fabrication (mes)

Country Status (4)

Country Link
US (1) US20050022171A1 (fr)
EP (1) EP1508093A2 (fr)
DE (1) DE10161115A1 (fr)
WO (1) WO2003050679A2 (fr)

Families Citing this family (15)

* 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
CN100580623C (zh) * 2005-05-13 2010-01-13 Abb研究有限公司 在集成应用之间保持数据一致性的方法和装置
DE102005053440A1 (de) * 2005-11-09 2007-05-10 Siemens Ag Verfahren und Vorrichtung zur Vernetzung einer Produktionsanlage
US20090089757A1 (en) * 2007-10-01 2009-04-02 Fujitsu Limited Configurable Web Services System and a Method to Detect Defects in Software Applications
US8332870B2 (en) * 2008-09-30 2012-12-11 Accenture Global Services Limited Adapter services
US8788295B1 (en) 2008-09-30 2014-07-22 Accenture Global Services Limited Reusable product system
US8719119B1 (en) 2008-09-30 2014-05-06 Accenture Global Services Limited Post deployment query system
US8595103B1 (en) 2008-09-30 2013-11-26 Accenture Global Services Limited Deployment and release component system
WO2010046734A1 (fr) * 2008-10-21 2010-04-29 Accenture Global Services Gmbh Unité de transformation de modèle
US8413109B2 (en) * 2010-01-20 2013-04-02 Sap Ag Systems and methods for metamodel transformation
US20120311038A1 (en) 2011-06-06 2012-12-06 Trinh Trung Tim Proximity Session Mobility Extension
US10225354B2 (en) * 2011-06-06 2019-03-05 Mitel Networks Corporation Proximity session mobility
US8813026B1 (en) * 2011-09-30 2014-08-19 Emc Corporation Methods and apparatus for storing information for components of a system in model component files to provide a world view of the system
EP2639753A1 (fr) * 2012-03-13 2013-09-18 Siemens Aktiengesellschaft Contrôle de processus de fabrication
EP2963599A1 (fr) * 2014-06-30 2016-01-06 Siemens Aktiengesellschaft Gestion de l'exécution d'un ordre de fabrication

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6292932B1 (en) * 1999-05-28 2001-09-18 Unisys Corp. System and method for converting from one modeling language to another

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6023578A (en) * 1997-05-09 2000-02-08 International Business Macines Corporation Systems, methods and computer program products for generating an object oriented application for an object oriented environment
US6208345B1 (en) * 1998-04-15 2001-03-27 Adc Telecommunications, Inc. Visual data integration system and method
US6306178B1 (en) * 1998-10-22 2001-10-23 Fountainhead Prosthetic device using a cam-shaped wheel
US6308178B1 (en) * 1999-10-21 2001-10-23 Darc Corporation System for integrating data among heterogeneous systems
US6523042B2 (en) * 2000-01-07 2003-02-18 Accenture Llp System and method for translating to and from hierarchical information systems
US6823495B1 (en) * 2000-09-14 2004-11-23 Microsoft Corporation Mapping tool graphical user interface
US7043687B2 (en) * 2000-12-27 2006-05-09 G. E. Information Services, Inc. Document/message management
US7162534B2 (en) * 2001-07-10 2007-01-09 Fisher-Rosemount Systems, Inc. Transactional data communications for process control systems

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6292932B1 (en) * 1999-05-28 2001-09-18 Unisys Corp. System and method for converting from one modeling language to another

Also Published As

Publication number Publication date
US20050022171A1 (en) 2005-01-27
WO2003050679A3 (fr) 2004-11-18
DE10161115A1 (de) 2003-07-03
WO2003050679A2 (fr) 2003-06-19

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'applications logiciel, notamment d'applications mes
EP1061422B1 (fr) Système d'ordinateur pour la définition, l'optimisation et la régulation des processus
DE10206902A1 (de) Engineeringverfahren und Engineeringsystem für industrielle Automatisierungssysteme
EP1508093A2 (fr) Transformation d'arbres d'objets en particulier dans des systemes d'execution de fabrication (mes)
EP1497714A2 (fr) Systeme et procede de projection de transformations effectues sur des arbres d'objets
EP2648094B1 (fr) Procédé et système de production d'un code source pour un programme informatique pour l'exécution et la simulation d'un processus
WO2013076250A1 (fr) Procédé de simulation, système de simulation et produit programme d'ordinateur pour commander un système d'automatisation de la production à architecture orientée services
DE10206903A1 (de) Softwareapplikation, Softwarearchitektur und Verfahren zur Erstellung von Softwareapplikationen, insbesondere für MES-Systeme
WO2009101212A1 (fr) Procédé et système pour intégrer des composants d'automatisation orientés sur les services d'un atelier de montage dans une architecture informatique d'entreprise flexible
WO2003050676A2 (fr) Systeme et procede de traçage et/ou d'evaluation d'un echange d'informations
EP1634130B1 (fr) Dispositif et procede pour programmer et/ou pour executer des programmes pour des systemes d'automatisation industriels
EP3948446A1 (fr) Génération et distribution de structures de données de configuration pour des systèmes de commande
EP4332772A1 (fr) Contrôleur capable data distribution service
EP2620868A1 (fr) Système de gestion du flux de travail pour réseaux informatiques
EP2171582A1 (fr) Télécommande de programme de navigation
EP1536328B1 (fr) Système de traitement de données avec la gestion automatisable et procédé pour la gestion automatisée d'un système de traitement de données
EP1515207A1 (fr) Objet d'automatisation et méthode pour la description d'un objet d'automatisation en utilisant une métalangage
WO2022233571A1 (fr) Procédé de configuration assistée par ordinateur d'un terminal, terminal et procédé de fonctionnement dudit terminal
EP3652657B1 (fr) Dispositif et procédé d'accouplement d'une machine dotée d'une pluralité d'applications
DE10033812A1 (de) Verfahren zum Erzeugen von Informationsmodellen
WO2024235445A1 (fr) Dispositif d'échange de données dans un système et procédé mis en œuvre par ordinateur
DE10109876B4 (de) Verfahren und Einrichtung zum Datenmanagement
DE102021101201A1 (de) Verfahren zum Einsetzen von Software-Stacks und computerlesbares Speichermedium
DE102008045272A1 (de) Vorrichtung und Verfahren zur Transformation eines Modells

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: 20040518

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

RIC1 Information provided on ipc code assigned before grant

Ipc: G06F 9/44 19800101ALI20051207BHEP

Ipc: G06F 9/46 19800101AFI20030623BHEP

17Q First examination report despatched

Effective date: 20070131

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: 20090719