US6701325B2 - Automation system with reusable automation objects and method for reusing automation solutions in engineering tools - Google Patents

Automation system with reusable automation objects and method for reusing automation solutions in engineering tools Download PDF

Info

Publication number
US6701325B2
US6701325B2 US09/950,153 US95015301A US6701325B2 US 6701325 B2 US6701325 B2 US 6701325B2 US 95015301 A US95015301 A US 95015301A US 6701325 B2 US6701325 B2 US 6701325B2
Authority
US
United States
Prior art keywords
automation
objects
module
new
interconnection
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.)
Expired - Lifetime, expires
Application number
US09/950,153
Other versions
US20020073094A1 (en
Inventor
Norbert Becker
Georg Biehler
Matthias Diezel
Albrecht Donner
Dieter Eckardt
Harald Herberth
Manfred Krämer
Dirk Langkafel
Ralf Leins
Ronald Lange
Walter Möller-Nehring
Jürgen Schmoll
Karsten Schneider
Ulrich Welz
Helmut Windl
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
Assigned to SIEMENS AKTIENGESELLSCHAFT reassignment SIEMENS AKTIENGESELLSCHAFT ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: DONNER, ALBRECHT, LANGKAFEL, DIRK, ECKARDT, DIETER, BECKER, NORBERT, BIEHLER, GEORG, DIEZEL, MATTHIAS, HERBERTH, HARALD, KRAMER, MANFRED
Publication of US20020073094A1 publication Critical patent/US20020073094A1/en
Application granted granted Critical
Publication of US6701325B2 publication Critical patent/US6701325B2/en
Adjusted expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00Programme-control systems
    • G05B19/02Programme-control systems electric
    • G05B19/04Programme control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/042Programme control other than numerical control, i.e. in sequence controllers or logic controllers using digital processors
    • G05B19/0426Programming the control sequence
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00Program-control systems
    • G05B2219/20Pc systems
    • G05B2219/23Pc programming
    • G05B2219/23255Object oriented programming, OOP
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00Program-control systems
    • G05B2219/20Pc systems
    • G05B2219/23Pc programming
    • G05B2219/23293Automated assembly of machine control software, reusable software components
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99941Database schema or data structure
    • Y10S707/99944Object-oriented database structure
    • Y10S707/99945Object-oriented database structure processing
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99941Database schema or data structure
    • Y10S707/99948Application of database or data structure, e.g. distributed, multimedia, or image

Definitions

  • the present invention relates to an automation system with at least one automation module, which has at least one automation object.
  • An automation system of the type mentioned above is used in particular in the area of automation engineering.
  • An automation system of this type generally comprises a multiplicity of individual automation objects, in which the automation object is often highly dependent on the engineering system used.
  • the automation objects of one manufacturer often require an engineering system of their own and cannot be used in other systems with automation objects of other manufacturers.
  • the present invention is based on the object of specifying a way of reusing already created automation solutions in engineering. This object is achieved by a method and a system which is able to use the solutions produced in the course of development of an automation solution which are the same or a similar form from a previously created automation engineering solution, based on the same project or an entirely different one.
  • previous engineering systems such as the Siemens engineering system Simatic S 7, there is a module concept. These modules offer a preset set of fixed automation functionalities.
  • the complete automation solution is created by linking together the existing modules and their respective functionalities.
  • New modules must be explicitly programmed, which means additional expenditures, since not only their functionality has to be programmed but also their integration into the tool.
  • the modules are not as tailor-made to the needs of one specific developer for automation solutions as they would be if the developer had derived the modules himself.
  • the method according to the present invention is based on two mutually independent concepts:
  • FIG. 1 shows a block diagram of an exemplary embodiment for the construction of an automation module
  • FIG. 2 shows a schematic representation for the process sequence for creating an automation module as a model
  • FIG. 3 shows an exemplary embodiment of a process sequence for creating an automation module with a central design specification
  • FIG. 4 shows an exemplary embodiment of a process sequence for creating an automation module with a duplicated design specification.
  • FIG. 1 shows a block diagram of an exemplary embodiment for the construction of automation module 1 , which is also referred to hereafter as a “compound.”
  • Compound 1 comprises function modules F 1 .-F 5 , i.e. the following five functional parts:
  • System functionality F 1 internal services which essentially offer a basis for implementation for the other parts;
  • Generic basic functionality F 2 general services which all automation objects have and which facilitate their handling, hidden within which are services such as storing and loading an automation object, inquiring management data etc. However, no technological services such as specific control algorithms are included;
  • Interconnection module F 3 allows interconnection of the compound with other automation objects
  • Parameterization module F 4 allows parameterization of the compound by corresponding parameterization of its parts.
  • Automation object management F 5 services such as insertion and access to the individual automation objects.
  • the automation objects may in this case themselves again be compounds. If one of the “part automation objects” was produced with a central design specification, changes in its model also become effective in the compound.
  • FIG. 2 shows a schematic representation for the process sequence for creating an automation module as a model.
  • the starting point is an automation plan P, which includes an interconnection of automation objects A 1 -An.
  • the automation objects A 1 -An are based on models V 1 , V 3 of a library B.
  • Specially designated in the automation plan P is a selection region S, which selects an interconnection of automation objects A 1 , A 2 , A 3 .
  • the automation objects A 1 -An are linked with their models of the library B.
  • the automation object A 3 was produced with a central design specification, intended to be graphically indicated by the designations KV, KV 3 .
  • the function CC graphically indicated as an arrow, is used to produce a new automation module in the form of the compound C as a new model by selection of the region S in the automation plan P.
  • part solution which comprises interconnected automation objects, which may also themselves be compounds.
  • the set which represents the part solution is selected. This may happen graphically, for example.
  • the creation of the compound is initiated.
  • a new model is produced, into which an empty compound is entered.
  • all the selected automation objects are copied and entered in the compound. All interconnections within the selected set are retained, the other interconnections are cut off. If a selected automation object was produced with a central design specification, this also applies for its copy in the compound.
  • the parameterizing module is generated from the the parameterizing modules of the automation objects
  • the interconnection module is derived from the cut-off interconnections. Both modules can be worked on subsequently by the user.
  • a compound may take place in two ways: an instance of a compound is produced in a plan from a model with a central design specification or with a duplicated design specification. In both cases, the compound can be used like a normal automation object. This is explained in more detail below with reference to FIGS. 3 and 4.
  • FIG. 3 shows an exemplary embodiment of a process sequence for creating an automation module with a central design specification.
  • the model of the automation module C is inserted into an automation plan P, accompanied by the central design specification.
  • Producing an instance with a central design specification means that changes in the model are automatically propagated to the instances.
  • instances can be registered when they are used in the model, so that the follow-up from the model can be carried out by corresponding data exchange. If components of the compound have been produced with a central design specification, this also applies for the parts in the instance.
  • FIG. 4 shows an exemplary embodiment of a process sequence for creating an automation module with a duplicated design specification.
  • Producing an instance with a duplicated design specification means that the model is completely copied and, as a result, the instance becomes independent of the model. Changes in the model are consequently not propagated to the instance. If components of the compound have been produced with a central design specification, this relationship is terminated.
  • the main difference from the previous solution is the capability of aggregating a set of automation objects on an ad-hoc basis to form a new set.
  • the solution described has the following advantages:
  • Simple creation of reusable solutions The developer of the automation solution can create a reusable model by means of visual programming (i.e. drag and drop, etc.);
  • Modules are tailor-made—Each developer can create a collection of models for his application domain;
  • the present invention relates to an an automation system with at least one automation module 1 , which has at least one automation object A 1 -An, and with function modules F 1 -F 6 , which contain means for central management and maintenance of the automation objects A 1 -An.

Abstract

The present invention relates to an automation system with at least one automation module (1), which has at least one automation object (A1-An), and with function modules (F1-F6), which contain means for central management and maintenance of the automation objects (A1-An). As a result, a manufacturer-independent definition of new automation objects, possibly using already existing automation objects, becomes possible, costly separate programming of new automation solutions is no longer necessary at all or is at least significantly simplified.

Description

This is a [X] continuation of copending application Serial No. PCT/DE00/00739 filed Mar. 9, 2000, PCT Publication WO 00/54118, which claims the priority of DE 199 10 311.9, filed Mar. 9, 1999.
FIELD OF THE INVENTION
The present invention relates to an automation system with at least one automation module, which has at least one automation object.
BACKGROUND OF THE INVENTION
An automation system of the type mentioned above is used in particular in the area of automation engineering. An automation system of this type generally comprises a multiplicity of individual automation objects, in which the automation object is often highly dependent on the engineering system used. As a consequence, the automation objects of one manufacturer often require an engineering system of their own and cannot be used in other systems with automation objects of other manufacturers.
In the article by Gerstner, Thomas et al.: “Rationelles Projektieren von Automatisierungssystemen” [Efficient project planning of automation systems], Automatisierungstechnische Praxis—ATP, DE, Oldenbourg Verlag, Munich, Vol. 36, No. 12, pages 42-45, XP000483710, ISSN: 0178-2320, a description is given of a PC-supported engineering tool which reduces the project planning expenditure of automation systems in that extended copying functions and library functions are used and standard plans are supported.
SUMMARY OF THE INVENTION
The present invention is based on the object of specifying a way of reusing already created automation solutions in engineering. This object is achieved by a method and a system which is able to use the solutions produced in the course of development of an automation solution which are the same or a similar form from a previously created automation engineering solution, based on the same project or an entirely different one. In previous engineering systems, such as the Siemens engineering system Simatic S 7, there is a module concept. These modules offer a preset set of fixed automation functionalities. The complete automation solution is created by linking together the existing modules and their respective functionalities.
This module concept has the following disadvantages:
Manufacturer Definition of New Modules
Only the manufacturer of the engineering tool can define new modules. The developer of an automation solution has no possible way of integrating a solution or partial solution into a module.
Explicit Programming of New Modules
New modules must be explicitly programmed, which means additional expenditures, since not only their functionality has to be programmed but also their integration into the tool.
Modules are Very Generic
As a result of the way in which they are developed, the modules are not as tailor-made to the needs of one specific developer for automation solutions as they would be if the developer had derived the modules himself.
The method according to the present invention is based on two mutually independent concepts:
The aggregation of automation objects of a (part) solution to form a new automation object. This can then be used like any other automation object. Such an aggregated automation object is referred to hereafter as a “compound”.
The automatic propagation of changes of automation objects in a library to automation objects in an automation solution. This means that adaptations in a model are automatically followed up in all used instances. This mechanism is referred to hereafter as a “central design specification”.
BRIEF DESCRIPTION OF THE DRAWINGS
The present invention is described and explained in more detail below on the basis of the exemplary embodiments represented in the following figures, in which:
FIG. 1 shows a block diagram of an exemplary embodiment for the construction of an automation module;
FIG. 2 shows a schematic representation for the process sequence for creating an automation module as a model;
FIG. 3 shows an exemplary embodiment of a process sequence for creating an automation module with a central design specification; and
FIG. 4 shows an exemplary embodiment of a process sequence for creating an automation module with a duplicated design specification.
DETAILED DESCRIPTION OF THE INVENTION
FIG. 1 shows a block diagram of an exemplary embodiment for the construction of automation module 1, which is also referred to hereafter as a “compound.” Compound 1 comprises function modules F1.-F5, i.e. the following five functional parts:
System functionality F1: internal services which essentially offer a basis for implementation for the other parts;
Generic basic functionality F2: general services which all automation objects have and which facilitate their handling, hidden within which are services such as storing and loading an automation object, inquiring management data etc. However, no technological services such as specific control algorithms are included;
Interconnection module F3: allows interconnection of the compound with other automation objects;
Parameterization module F4: allows parameterization of the compound by corresponding parameterization of its parts; and
Automation object management F5: services such as insertion and access to the individual automation objects.
The automation objects may in this case themselves again be compounds. If one of the “part automation objects” was produced with a central design specification, changes in its model also become effective in the compound.
FIG. 2 shows a schematic representation for the process sequence for creating an automation module as a model. The starting point is an automation plan P, which includes an interconnection of automation objects A1-An. The automation objects A1-An are based on models V1, V3 of a library B. Specially designated in the automation plan P is a selection region S, which selects an interconnection of automation objects A1, A2, A3. The automation objects A1-An are linked with their models of the library B. In this case, the automation object A3 was produced with a central design specification, intended to be graphically indicated by the designations KV, KV3. To create a new automation module, the function CC, graphically indicated as an arrow, is used to produce a new automation module in the form of the compound C as a new model by selection of the region S in the automation plan P.
In the starting situation there is a certain (part) solution, which comprises interconnected automation objects, which may also themselves be compounds. To produce a compound as a model, the set which represents the part solution is selected. This may happen graphically, for example. Thereafter, the creation of the compound is initiated. For this purpose, a new model is produced, into which an empty compound is entered. After that, all the selected automation objects are copied and entered in the compound. All interconnections within the selected set are retained, the other interconnections are cut off. If a selected automation object was produced with a central design specification, this also applies for its copy in the compound.
When the automation objects are inserted into the compound, two modules are automatically produced for the interconnecting and parameterizing of the compound. The parameterizing module is generated from the the parameterizing modules of the automation objects, the interconnection module is derived from the cut-off interconnections. Both modules can be worked on subsequently by the user.
The use of a compound may take place in two ways: an instance of a compound is produced in a plan from a model with a central design specification or with a duplicated design specification. In both cases, the compound can be used like a normal automation object. This is explained in more detail below with reference to FIGS. 3 and 4.
FIG. 3 shows an exemplary embodiment of a process sequence for creating an automation module with a central design specification. In this case, the model of the automation module C is inserted into an automation plan P, accompanied by the central design specification. Producing an instance with a central design specification means that changes in the model are automatically propagated to the instances. For this purpose, instances can be registered when they are used in the model, so that the follow-up from the model can be carried out by corresponding data exchange. If components of the compound have been produced with a central design specification, this also applies for the parts in the instance.
FIG. 4 shows an exemplary embodiment of a process sequence for creating an automation module with a duplicated design specification. Producing an instance with a duplicated design specification means that the model is completely copied and, as a result, the instance becomes independent of the model. Changes in the model are consequently not propagated to the instance. If components of the compound have been produced with a central design specification, this relationship is terminated.
The main difference from the previous solution is the capability of aggregating a set of automation objects on an ad-hoc basis to form a new set. The solution described has the following advantages:
Simple creation of reusable solutions—The developer of the automation solution can create a reusable model by means of visual programming (i.e. drag and drop, etc.);
Modules are tailor-made—Each developer can create a collection of models for his application domain;
Automatic replication of changes—The “central design specification” technique allows changes in a model to be propagated to all automation solutions concerned. This reduces the maintenance expenditure considerably; and
Reduction in development time—The presence of extensive libraries with tailor-made part solutions means that applications do not constantly have to be developed from scratch.
In summary, the present invention relates to an an automation system with at least one automation module 1, which has at least one automation object A1-An, and with function modules F1-F6, which contain means for central management and maintenance of the automation objects A1-An. As a result, manufacturer-independent of new automation objects, and possibly using already existing automation objects, becomes possible and costly separate programming of new automation solutions is no longer necessary at all or is at least significantly simplified.

Claims (6)

What is claimed is:
1. A method for the aggregation of automation objects using models from a library to form a new automation module wherein interconnection of the automation objects are selected from a selection region in an automation plan which contains an interconnection of the automation objects and the selection of the said region producing the new automation module as a model, further wherein all the interconnections within the selection region are retained and the other interconnections are cut-off, and an interconnection module for the interconnection of the new automation module having further automation objects comprising a first parameterization module for the parameterization of the new automation module automatically produced in the new automation module, said first parameterization module being generated from second parameterization modules of the selected automation objects and the interconnection module being derived from the cut-off interconnections.
2. The method according to claim 1, wherein changes to the models for the automation objects in the library automatically lead via data exchange to corresponding changes to the automation objects in previously used instances in an automation solution.
3. The method according to claim 2, wherein the automation objects are produced in the used instances from the models for the automation objects and are registered in the models, the models containing central design specifications.
4. A system for the aggregation of automation objects based on models of a library to form a new automation module comprising an automation plan including an interconnection of the automation objects, a selection of an interconnection of the automation objects for producing the new automation module as a model being provided in the automation plan, wherein all the interconnection selections are retained and all other interconnections are cut-off, and wherein an interconnection module is derived from the cut-off interconnections, for the interconnection of the new automation module with further automation objects comprising a first parameterization module generated from second parameterization modules of the selected automation objects for parameterization of the new automation module which are provided in the new automation module.
5. The system according to claim 4, wherein a data exchange is provided for the automatic passing on of changes to the models for the automation objects in the library to the automation objects in used instances in an automation solution.
6. The system according to claim 5, wherein central design specifications in the models for producing the automation objects in the used instances are provided, and which a registration of the automation objects in the models is provided.
US09/950,153 1999-03-09 2001-09-10 Automation system with reusable automation objects and method for reusing automation solutions in engineering tools Expired - Lifetime US6701325B2 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
DE19910311A DE19910311A1 (en) 1999-03-09 1999-03-09 Automation system with reusable automation objects and process for reusing automation solutions in engineering tools
DE19910311.9 1999-03-09
PCT/DE2000/000739 WO2000054118A1 (en) 1999-03-09 2000-03-09 Automation system with re-usable automation objects and method for the re-use of automation solutions in engineering tools

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
PCT/DE2000/000739 Continuation WO2000054118A1 (en) 1999-03-09 2000-03-09 Automation system with re-usable automation objects and method for the re-use of automation solutions in engineering tools

Publications (2)

Publication Number Publication Date
US20020073094A1 US20020073094A1 (en) 2002-06-13
US6701325B2 true US6701325B2 (en) 2004-03-02

Family

ID=7900231

Family Applications (1)

Application Number Title Priority Date Filing Date
US09/950,153 Expired - Lifetime US6701325B2 (en) 1999-03-09 2001-09-10 Automation system with reusable automation objects and method for reusing automation solutions in engineering tools

Country Status (8)

Country Link
US (1) US6701325B2 (en)
EP (1) EP1159656B1 (en)
JP (1) JP3955439B2 (en)
CN (1) CN1343329A (en)
AT (1) ATE241160T1 (en)
DE (2) DE19910311A1 (en)
ES (1) ES2199828T3 (en)
WO (1) WO2000054118A1 (en)

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040215355A1 (en) * 2003-04-25 2004-10-28 Dean Mills Modular system and method for programming machine automation controls
US20060142882A1 (en) * 2002-09-16 2006-06-29 Siemens Aktiengesellschaft System for preparing a standard framework for automation appliances
US20060155481A1 (en) * 2004-12-21 2006-07-13 Diamantis Gikas System and method for reusing project planning data
US20070293964A1 (en) * 2005-07-06 2007-12-20 Skorepa Bradley J Method for engineering a control system
US7353221B1 (en) * 1999-03-09 2008-04-01 Siemens Aktiengesellschaft Method for the automatic retrieval of engineering data of systems
US20080086477A1 (en) * 2006-10-06 2008-04-10 Microsoft Corporation Locally storing web-based database data
WO2010121099A1 (en) * 2009-04-17 2010-10-21 Siemens Aktiengesellschaft Dynamic views in a modeling of an automation system
US20140310052A1 (en) * 2013-04-11 2014-10-16 Siemens Aktiengesellschaft Method And Apparatus For Generating An Engineering Workflow
US9189377B1 (en) 2014-06-02 2015-11-17 Bank Of America Corporation Automation testing using descriptive maps
US9697110B1 (en) 2015-12-28 2017-07-04 Bank Of America Corporation Codeless system and tool for testing applications

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE10060206A1 (en) * 2000-12-04 2002-06-13 Siemens Ag Programming device
EP1233318A1 (en) * 2001-02-16 2002-08-21 Abb Research Ltd. Software coumpounds for a distributed control system
JP4744847B2 (en) * 2004-11-02 2011-08-10 株式会社安川電機 Robot control device and robot system
US7478378B2 (en) * 2004-11-29 2009-01-13 International Business Machines Corporation Semantically consistent adaptation of software applications
EP1674954A1 (en) * 2004-12-21 2006-06-28 Siemens Aktiengesellschaft System and method for reusing of design related data
EP1699005A1 (en) * 2005-03-01 2006-09-06 Siemens Aktiengesellschaft Integration of MES and Controls-Engineering
US7797678B2 (en) 2005-04-07 2010-09-14 International Business Machines Corporation Automatic generation of license package for solution components
US7496888B2 (en) * 2005-04-07 2009-02-24 International Business Machines Corporation Solution builder wizard
US7770151B2 (en) 2005-04-07 2010-08-03 International Business Machines Corporation Automatic generation of solution deployment descriptors
US20070093917A1 (en) * 2005-10-20 2007-04-26 Honeywell International Inc. Storing and accessing relay ladder logic modules in a relational database
DE102008019650B4 (en) * 2008-04-18 2011-03-17 Siemens Electronics Assembly Systems Gmbh & Co. Kg Control system for electronics manufacturing and method of operation of this control system
CN107710149B (en) * 2015-06-04 2021-04-30 西门子公司 Method and system for generating PLC code using connectivity model
WO2021243347A1 (en) * 2020-05-29 2021-12-02 Jezewski Joni Solution automation & interface analysis implementations

Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5524253A (en) * 1990-05-10 1996-06-04 Hewlett-Packard Company System for integrating processing by application programs in homogeneous and heterogeneous network environments
WO1997011415A1 (en) 1995-09-19 1997-03-27 Siemens Aktiengesellschaft System for automating the control and regulation of machines and plants in the plastics industry
DE19624929A1 (en) 1996-06-21 1998-01-02 Siemens Ag Process automation system
US5940294A (en) * 1996-04-12 1999-08-17 Fisher-Rosemont Systems, Inc. System for assisting configuring a process control environment
USRE36602E (en) * 1993-11-24 2000-03-07 The Trustees Of The Stevens Institute Of Technology Concurrent engineering design tool and method
US6201996B1 (en) * 1998-05-29 2001-03-13 Control Technology Corporationa Object-oriented programmable industrial controller with distributed interface architecture
US6230309B1 (en) * 1997-04-25 2001-05-08 Sterling Software, Inc Method and system for assembling and utilizing components in component object systems
US6233538B1 (en) * 1997-09-11 2001-05-15 Amada America, Inc. Apparatus and method for multi-purpose setup planning for sheet metal bending operations
US6240326B1 (en) * 1998-04-03 2001-05-29 Johnson Controls Technology Co. Language independent building automation architecture for worldwide system deployment
US6327594B1 (en) * 1999-01-29 2001-12-04 International Business Machines Corporation Methods for shared data management in a pervasive computing environment
US6449659B1 (en) * 1997-07-14 2002-09-10 Microsoft Corporation System for instance customization with application independent programming of controls

Patent Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5524253A (en) * 1990-05-10 1996-06-04 Hewlett-Packard Company System for integrating processing by application programs in homogeneous and heterogeneous network environments
USRE36602E (en) * 1993-11-24 2000-03-07 The Trustees Of The Stevens Institute Of Technology Concurrent engineering design tool and method
WO1997011415A1 (en) 1995-09-19 1997-03-27 Siemens Aktiengesellschaft System for automating the control and regulation of machines and plants in the plastics industry
US5940294A (en) * 1996-04-12 1999-08-17 Fisher-Rosemont Systems, Inc. System for assisting configuring a process control environment
DE19624929A1 (en) 1996-06-21 1998-01-02 Siemens Ag Process automation system
US6230309B1 (en) * 1997-04-25 2001-05-08 Sterling Software, Inc Method and system for assembling and utilizing components in component object systems
US6449659B1 (en) * 1997-07-14 2002-09-10 Microsoft Corporation System for instance customization with application independent programming of controls
US6233538B1 (en) * 1997-09-11 2001-05-15 Amada America, Inc. Apparatus and method for multi-purpose setup planning for sheet metal bending operations
US6240326B1 (en) * 1998-04-03 2001-05-29 Johnson Controls Technology Co. Language independent building automation architecture for worldwide system deployment
US6201996B1 (en) * 1998-05-29 2001-03-13 Control Technology Corporationa Object-oriented programmable industrial controller with distributed interface architecture
US6327594B1 (en) * 1999-01-29 2001-12-04 International Business Machines Corporation Methods for shared data management in a pervasive computing environment

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
Gerstner, T. et al.: "Rationelles Projektieren von Automatisierungssystem", Dec., 1994, pp. 42-45.
Mick, R. "Client/server computing comes to the plant floor.", Sep., 1993, pp. 41-42; 47-49.
Selch, M., et al.: "Step 7-The Future-Oriented Programming System for the New Simatic Programmable Controllers", Mar./Apr., 1994, pp. 5-6.
Selch, M., et al.: "Step 7—The Future-Oriented Programming System for the New Simatic Programmable Controllers", Mar./Apr., 1994, pp. 5-6.

Cited By (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7353221B1 (en) * 1999-03-09 2008-04-01 Siemens Aktiengesellschaft Method for the automatic retrieval of engineering data of systems
US20060142882A1 (en) * 2002-09-16 2006-06-29 Siemens Aktiengesellschaft System for preparing a standard framework for automation appliances
US7757205B2 (en) * 2002-09-16 2010-07-13 Siemens Aktiengesellschaft System for preparing a standard framework for automation appliances
US20040215355A1 (en) * 2003-04-25 2004-10-28 Dean Mills Modular system and method for programming machine automation controls
US20060155481A1 (en) * 2004-12-21 2006-07-13 Diamantis Gikas System and method for reusing project planning data
US20070293964A1 (en) * 2005-07-06 2007-12-20 Skorepa Bradley J Method for engineering a control system
US7447555B2 (en) * 2005-07-06 2008-11-04 Skorepa Bradley J Method for engineering a control system
US20080086477A1 (en) * 2006-10-06 2008-04-10 Microsoft Corporation Locally storing web-based database data
WO2010121099A1 (en) * 2009-04-17 2010-10-21 Siemens Aktiengesellschaft Dynamic views in a modeling of an automation system
CN102246109A (en) * 2009-04-17 2011-11-16 西门子公司 Dynamic views in a modeling of an automation system
CN102246109B (en) * 2009-04-17 2014-02-26 西门子公司 Dynamic views in a modeling of an automation system
US8700192B2 (en) 2009-04-17 2014-04-15 Siemens Aktiengesellschaft Dynamic views in a modeling of an automation system
US20140310052A1 (en) * 2013-04-11 2014-10-16 Siemens Aktiengesellschaft Method And Apparatus For Generating An Engineering Workflow
US9600792B2 (en) * 2013-04-11 2017-03-21 Siemens Aktiengesellschaft Method and apparatus for generating an engineering workflow
US9189377B1 (en) 2014-06-02 2015-11-17 Bank Of America Corporation Automation testing using descriptive maps
US9697110B1 (en) 2015-12-28 2017-07-04 Bank Of America Corporation Codeless system and tool for testing applications

Also Published As

Publication number Publication date
JP3955439B2 (en) 2007-08-08
DE19910311A1 (en) 2000-09-14
CN1343329A (en) 2002-04-03
DE50002260D1 (en) 2003-06-26
ES2199828T3 (en) 2004-03-01
EP1159656B1 (en) 2003-05-21
ATE241160T1 (en) 2003-06-15
WO2000054118A1 (en) 2000-09-14
US20020073094A1 (en) 2002-06-13
JP2002539512A (en) 2002-11-19
EP1159656A1 (en) 2001-12-05

Similar Documents

Publication Publication Date Title
US6701325B2 (en) Automation system with reusable automation objects and method for reusing automation solutions in engineering tools
Bruno et al. Process-translatable Petri nets for the rapid prototyping of process control systems
CA2332009C (en) System and methods for object-oriented control of diverse electromechanical systems using a computer network
US5864875A (en) Data management system for problems, releases and parts
US7451007B2 (en) Integration of MES and controls engineering
Baldassari et al. PROTOB: An object oriented methodology for developing discrete event dynamic systems
Gruver et al. Intelligent Manufacturing:: Programming Environments for CIM
Smith et al. A shop floor controller class for computer-integrated manufacturing
Pawletta et al. A devs-based approach for modeling and simulation of hybrid variable structure systems
McLean Interface concepts for plug-compatible production management systems
Yim et al. A Petri net-based simulation tool for the design and analysis of flexible manufacturing systems
Timmermans Modular design of information systems for shop floor control
US20070093917A1 (en) Storing and accessing relay ladder logic modules in a relational database
Weber et al. Specification of concurrently executable modules and distributed modular systems
Motschnig-Pitrik Contexts and views in object-oriented languages
Menga et al. Prototyping discrete part manufacturing systems
Senehi et al. Reference Architecture for Machine Control Systems Integration: Interim Report
Chaxel et al. Mobile database nodes for manufacturing information management: a STEP based approach
Scoggins THE METHODOLOGIES OF SYSTEM ANALYSIS AND DESIGN FOR COMPUTER INTEGRATED MANUFACTURING (CIM)(FACTORY AUTOMATION)
Klostermeyer et al. PABADIS-an agent based flexible manufacturing concept
Van't Erve Generative computer aided process planning for part manufacturing: An expert system approach
Lee An integrated methodology for the analysis and design of cellular flexible assembly systems
Kosanke et al. CIMOSA process model for enterprise modelling
Boucher et al. Simulation and Supervisory Control Software for Design and Control of Manufacturing Cells
Lee Simulation code generation on WWW using object-oriented manufacturing resource model

Legal Events

Date Code Title Description
AS Assignment

Owner name: SIEMENS AKTIENGESELLSCHAFT, GERMANY

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BECKER, NORBERT;DIEZEL, MATTHIAS;ECKARDT, DIETER;AND OTHERS;REEL/FRAME:012582/0907;SIGNING DATES FROM 20010711 TO 20010920

STCF Information on status: patent grant

Free format text: PATENTED CASE

FPAY Fee payment

Year of fee payment: 4

FPAY Fee payment

Year of fee payment: 8

FPAY Fee payment

Year of fee payment: 12