EP1597675A1 - Systeme et procede de gestion et d'echange de donnees d'un projet technique, d'une installation technique et des differents composants d'une installation - Google Patents

Systeme et procede de gestion et d'echange de donnees d'un projet technique, d'une installation technique et des differents composants d'une installation

Info

Publication number
EP1597675A1
EP1597675A1 EP04714740A EP04714740A EP1597675A1 EP 1597675 A1 EP1597675 A1 EP 1597675A1 EP 04714740 A EP04714740 A EP 04714740A EP 04714740 A EP04714740 A EP 04714740A EP 1597675 A1 EP1597675 A1 EP 1597675A1
Authority
EP
European Patent Office
Prior art keywords
data
information
format
proprietary
standardized
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
EP04714740A
Other languages
German (de)
English (en)
Inventor
Peter Drath
Peter Bort
Alexander Fay
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.)
ABB Research Ltd Switzerland
ABB Research Ltd Sweden
Original Assignee
ABB Research Ltd Switzerland
ABB Research Ltd Sweden
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 ABB Research Ltd Switzerland, ABB Research Ltd Sweden filed Critical ABB Research Ltd Switzerland
Publication of EP1597675A1 publication Critical patent/EP1597675A1/fr
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/80—Information retrieval; Database structures therefor; File system structures therefor of semi-structured data, e.g. markup language structured data such as SGML, XML or HTML
    • G06F16/84—Mapping; Conversion

Definitions

  • the present invention relates to a system and a method for managing and exchanging data, a technical project and / or a technical system and / or individual system components and, in particular, an automation project for a technical system, with the present invention an efficient and consistent interaction several different applications or data processing tools is guaranteed and achieved.
  • a project in the sense of the invention claimed here can, for example, include planning, development, construction, testing, test acceptance, commissioning, operation, but also maintenance and repair as well as, if necessary, the expansion and modification of a technical system and / or include individual system components, i.e. a technical system and / or individual system components in all their life cycle phases.
  • the project data of an automation project for a technical system include in particular the entire life cycle of the aforementioned system from planning through implementation to operation and during the operation of the system.
  • the aforementioned data can include, for example, measurement, monitoring, performance and / or evaluation data of the respective system, but also information about servicing and / or maintenance measures as well as technical developments or improvements to the system.
  • Data is recorded in particular during the engineering process or during the planning and design phase, at the beginning of the respective life cycle of a plant.
  • the data generated here essentially describe the structure and implementation of the respective technical system.
  • the modification or change of the generated or recorded plant-specific data record and / or the recording or generation of new data relating to planned and / or changes made to the respective technical system are carried out essentially in the operating phase of the respective system.
  • Plant can lead.
  • a common database for all processing tools or applications relating to the life cycle of a system must be used when using or using several different processing tools.
  • This can be, for example, a central database or several distributed databases with a common data model or object model.
  • n tools where n denotes the number of tools used, n * (n-1) / 2 data interfaces must be set up, maintained and maintained if every tool involved or used is to have the possibility to exchange or interact with any other tool and to define or define a separate interface format for each exchange.
  • a data format is usually selected or defined and standardized, for example as a company standard, as a national standard and / or as an international standard, and thus a central standard data format is generated, via which the mutual data exchange of the processing tools or applications used.
  • Each of these interfaces converts project and / or project planning data or other data relating to the system, its components and / or its automation system from the proprietary tool-internal format into the standardized data format and makes them available to all other tools via export functions.
  • each of these interfaces converts project and / or project planning data or others the system, its components and / or it Automation system-related data from the standardized format into the tool-internal, proprietary format and makes it available to the respective tool by means of import options.
  • different processing tools can read in, analyze, visualize, edit, change and / or supplement the data or information relevant to them from a file and write them back into the file.
  • Registry files in which information can be written and / or read by various tools and the operating system
  • STEP Standard for the Exchange of Product Data
  • EXPRESS STEP exchange language
  • EP 0770943 B1 describes an in-house standardized description of the data of an automation project and the system to be automated. Also in A. Fay: Methods for Supporting the Migration of Process Control System Software, Automation Practice 44, Oldenbourg-Verlag, Kunststoff, Issue 6/2002, pp. 39-44, a description of an in-house standard specified part of the engineering data of an automation project, with particular reference being made to the advantages, such as reducing the interface effort to several engineering tools.
  • the respective data or files can be easily read by people with comparatively little effort and information can be found and interpreted correspondingly easily.
  • individual applications or processing tools can be created in a comparatively simple manner, with which the aforementioned files can be processed, that is to say read and written.
  • the Exlensible Markup Language is a well-known meta-language for the definition and description of languages, data formats and / or structures, in particular also for the definition and description of a data exchange format.
  • XML schemas rules can be defined as to how an XML document should be structured in its logical structure, for example with regard to elements and hierarchy. With the help of XML schemas, it can be checked, for example, whether an XML file is structured in accordance with such rules defined in the XML schema (so-called “well-formedness”).
  • XML files read, check for well-formedness, convert to another, possibly proprietary data format or object model and / or convert an existing object model or the data or information describing it into a well-formed XML file.
  • XML files usually have all of the above characteristics, which a standard data format should have.
  • the language XSLT XML Stylesheet Language Translation
  • XSLT was defined in the context of XML as a programming language for converting XML documents into other standardized formats.
  • XML Because of its known advantages and possibilities, XML is used or recommended in many areas where there is a need to exchange data between different processing tools in a standardized format. The possibility of the advantageous use of XML for such tasks in any application areas is generally known and was also the declared goal of the development of XML.
  • XML is mentioned and used as a meta-language for defining an exchange format for project and / or project planning data of an automation project, in that for each processing tool that uses a proprietary data format internally and interacts with the standardized data model, a separate one Conversion module is created, which carries out the conversion from the proprietary to the standardized data format or vice versa.
  • the aforementioned conversion module can either be executed as an independent tool that is connected to the respective associated processing tool, for example an engineering tool, or can be integrated or integrated into the respective processing tool, for example an engineering, service or validation tool, if necessary combined with an import and / or export functionality.
  • the programming language XSLT can also be used to convert XML files into files with other standardized or proprietary formats, whereby changes to the proprietary data format disadvantageously require interventions in the program code of the specified or used conversion modules.
  • the aforementioned changes to the proprietary data format may be necessary, for example, through changes in the functionality of the respective processing tool, through a change in the implementation of the respective processing tool into the overall concept and / or with changes in the standardized data format.
  • the aforementioned changes can be brought about, for example, by integrating a further processing tool into the standardized data format. Due to the ever shorter innovation cycles, the associated shorter cycle times and frequent changes of the tool generations or versions used as well as the increasing requirements with regard to the integration of further tools or applications, the aforementioned problem is becoming increasingly important.
  • Interventions in existing applications and / or processing tools are particularly consistent and - as already stated - the information or data describing a technical system and its automation system over the entire life cycle of the system, which can usually extend over several decades should or should be maintained, problematic, since this would require interventions and modifications of decades-long applications and processing tools, especially their program codes. As a rule, however, there is no longer any expertise available or available for this.
  • This task is carried out by a system and a procedure for the administration and exchange, in particular also for the generation, modification and storage of data of a technical project, a technical system and / or individual system components, but especially an automation project for a technical system solved the features of the independent claims.
  • Advantageous refinements of the system according to the invention and of the corresponding method are specified in the dependent claims and the description below.
  • the present invention includes a data processing system with a conversion device for converting data from a proprietary data format into a standardized data format and vice versa, the conversion of detailed information of the respective application domain being independent.
  • the conversion information of the various application domains is not stored here as graphical rules, but rather is given in the form of assignments between data objects, the assignments of the type 1: 1, 1: n, m: 1 or m: n, with m and n as any natural integers greater than 1.
  • the system according to the invention for managing and exchanging data in particular also for generating, modifying and storing data of a technical project, a technical system and / or individual system components, in particular an automation project for a technical system, has at least one data processing system with conversion device for converting project and / or project planning data and / or operating data of the respective technical system and / or the associated automation system from a proprietary format into a standardized format and vice versa.
  • the con- The conversion device in this case comprises at least one means for data assignment, which is set up to assign at least one piece of second information specified in the standardized data format, preferably XML, to at least one piece of first information specified in the proprietary " format, and / or vice versa Data conversion to which is set up to find or find the corresponding data assignment assigned to it from any set of data assignments for any first information specified in the proprietary data format, and to use the data assignment found to specify the proprietary first information into the data assignment specified in the assigned data assignment to convert standardized second information and / or vice versa for any standardized second information in the data assignments contained in the conversion device to track down or find computing data assignment and to convert the standardized second information into the proprietary first information specified in the assigned data assignment.
  • An advantageous embodiment provides that the conversion device is set up to search for and track down the corresponding data assignment assigned to it from the set of existing data assignments for the first information specified in the proprietary data format, and to use the data assignment found to find the proprietary one convert the first information into the standardized second information specified in the data assignment and search for and find the corresponding data assignment assigned to it for the standardized second information in the data assignments contained in the conversion device and, via this, the standardized second information into a proprietary one specified in the data assignment to convert third information.
  • the data are preferably stored both in the proprietary and in the standardized format in a predetermined, defined structure, in particular a hierarchical structure and / or a tree structure.
  • Both the proprietary and the standardized format are preferably human-readable and human-interpretable and / or contain descriptive identifiers for the respective data.
  • the specified conversion device is configurable insofar as it can be separated into two independent components, namely a component a) for assigning data and a generic component b) for converting data, the generic component b) providing the conversion function and usually can be implemented as a program component that can be executed on a data processing system in a common programming language and with corresponding program code means.
  • the data assignments specified in component a), in particular a file, which are used to adapt the conversion device to the respective application domain or the respective application area and / or the processing tool used in each case, as well as the data formats to be converted, can be individually adapted and configured ,
  • the data assignments are stored in the form of a simple table. If a simple assignment via a table is not possible, then the conversion can also take place via a hierarchically structured mapping structure which, for example, as in the German patent applications with official file number DE 102 54 530.8, DE 102 54 531.6 and DE 102 54 532.4 is used in parsers for textual programming languages.
  • the above-mentioned separability or configurability has the advantage that component a) of the conversion device, which has at least one means for data assignment, and component b) of the conversion device, which has at least one means for data conversion, are developed, developed and maintained independently of one another can be.
  • the generic component b) can be adapted at any time, for example, to currently available or customary program code means, operating system environments, development methods and / or techniques, which if more than one project data and / or system data is used Decades will almost certainly be required several times during the life cycle of a technical system. However, the data assignments of the application domain specified in component a) remain unaffected.
  • the data assignments can be changed easily, for example in the advantageous tabular implementation by changing one or more entries in the table without having to change the actual program code.
  • the aforementioned changes can be made manually and / or automatically.
  • Automated implementation can be implemented here, for example, using a processing tool that supports manual graphic mapping or that automatically determines mapping relationships by means of rule-based parsing of the proprietary data structures and enters them in a corresponding mapping table.
  • the standardized data format has to be changed and / or expanded because, for example, a further processing tool that has additional data and objects reads in, changes and / or creates the standardized data format, preferably XML, in the processing tool.
  • Verbund should be involved. According to the state of the art, this would require that for all processing tools that are also intended to use or want to use these additional data and objects for reading and / or writing, the corresponding conversion components would have to be adapted or expanded by intervening in the possibly decades-old program codes, what usually requires expert knowledge and expensive program code resources, for example suitable compilers and / or debuggers.
  • this extension can be accomplished simply by simply adding and / or changing the data assignments specified, for example, in a table in a standard data format file. This does not require expert knowledge, programming knowledge or costly program code resources.
  • a method for managing and exchanging data, relating to a technical project, a technical system and / or individual system components, in particular relating to an automation project, by means of at least one data processing system with conversion device for converting data a proprietary data format into a standardized data format and vice versa is claimed.
  • the conversion device allows at least one piece of first information specified in the proprietary data format to be assigned at least one piece of second information specified in the standardized format and / or vice versa.
  • the method using a generic component of the conversion device with at least one means for converting data, for any first information specified in the proprietary data format, the corresponding data assignment assigned to the first information is found or found from the set of existing data assignments, and the proprietary data assignment is found using the data assignment found first information is converted into the standardized second information specified in the assigned data assignment and / or, conversely, the desired data assignment assigned to the second information is searched for and found for any standardized second information in the data assignments contained in the conversion device, and the standardized second information is found in the proprietary first information specified in the data assignment is converted.
  • a first proprietary information can accordingly be converted into another proprietary information by means of data assignments.
  • the generic component used preferably acts independently of the standardized and the proprietary data format.
  • the data can be stored or stored both in the proprietary and in the standardized data format, preferably using a predetermined, defined structure, in particular a hierarchical structure and / or tree structure.
  • Figure 1 Exemplary system for managing and exchanging data between two different processing tools using a mapping table.
  • Figure 2 Exemplary process diagram relating to the administration
  • FIG. 3 Exemplary process diagram relating to the administration and the exchange of objects and their contents between object libraries of two different processing tools with a complete mapping table.
  • Figure 4 Exemplary process diagram, regarding the administration and the
  • Figure 5 Exemplary process diagram, regarding the administration and the
  • the aforementioned system here has a data processing system 2 with conversion device 4 and means for data allocation and conversion of data from at least one proprietary format into at least one standardized format and vice versa.
  • a transformation between any two data formats can be represented by means of semantic mapping tables 10 or mapping tables, which are also generally referred to below as mapping tables.
  • the data processing system 2 also has an input device 2a, a display device 2b and a data memory 2c with which it interacts.
  • the mapping tables 10 do not necessarily have to be structured flat, but rather can also have a hierarchical structure.
  • the mapping tables 10 comprise assignments between data and / or objects of the data formats of a first tool, Tool A, and a second tool, Tool B, and are to be understood as semantic links or references. If, for example, a "circle" object is read from a tool A, this object can be assigned to the "DynamicCircle" object supported by tool B. If, as shown in FIG. 1, the file exchange format is standardized, for example as in the case of an XML file 12, the syntactically correct reading of the data present in the standardized format is made considerably easier.
  • mapping tables 10 One advantage of the mapping tables 10 is that the respective application, in the example Tool A or Tool B shown here, can not only read the XML file 12 in a syntactically correct manner but can also extract or extract the required semantic information from the respective mapping table 10. This means that the tool B "understands” the XML file 12 through the "glasses" of the mapping table 10, that is, it can interpret it correctly and thus can work directly with the XML file 12. It follows that changes in turn in the XML file 12 can be written back, whereby tool A can become aware of changes to the file which were caused by tool B.
  • mapping tables 10 can be created and / or changed before or during the method, depending on the application area, manually by the user of the various applications, or the corresponding mapping tables 10 can be used with the applications or processing tools used in each case. to be delivered. In special cases, the mapping table 10 can also be created automatically.
  • mapping tables 10 A prerequisite for the use of mapping tables 10 is the existence of a clear association between at least some of the existing data or information, the term data or information including the associated objects, their attributes and their relations.
  • mapping tables 10 according to the method is explained by way of example using some exemplary embodiments.
  • Tool A uses a tool-specific "object library A” (data library) 20 to create project data.
  • the objects data or information contained in "object library A” 20)
  • Tool B the same procedure is followed, whereby the “object library B” 22 can have a structure that differs from the “object library A” 20.
  • the two aforementioned different processing tools if they have been implemented in terms of program technology, can be carried out on the data processing system 2 (see FIG. 1) with a conversion device 4 (see FIG. 1) or on other data processing devices if they are with the data processing system 2 Conversion device 4 interact via corresponding network connections, such as LAN, WAN, in particular Internet connections and / or radio connections.
  • a data transfer from a first processing tool, Tool A, to a second processing tool, Tool B, is effected by means of relationships between the elements of the libraries “Object Library A” 20 and “Object Library B” 22, the two tools, relating, for example, to objects, attributes and / or information can be created and stored in a separate relation table or mapping table 10. If, as shown in FIG. 2, an XML file 12 is now read in by the second processing tool, Tool B, and an object “Pump” 26 from the "" Object library A "20 is found, tool B can assign this object” Pump “26 to its own object” P37 "28 with the aid of the specified mapping table 10.
  • mapping table 10 can be formed .
  • the exchange of any files and / or data or information between the two tools, Tool A and Tool B is now possible.
  • any first information of the “ Object library A "20 assign a second piece of information to the own" object library B "22.
  • the aforementioned information can be, for example, measurement or control data, evaluation results, in particular of another tool, performance data, or maintenance data.
  • a file with "project data A” 30 is thus directly readable for tool B in the form of another file with "project data B" 32. Since the assignment 34 between the data is unambiguous, tool B can write changes from the “project data B” 32 directly back into the XML file 12 and thus make them available to the tool A.
  • mapping table 10 is only created with assignments between used data of a specific project data record, only an incomplete mapping table 10 will generally result.
  • the data exchange can only take place specifically for the file of this project or the data exchange between projects whose data are completely described by the mapping table 10.
  • An advantage of the invention is that it is harmless if a second tool, Tool B, cannot process all the data made available by a first tool, Tool A.
  • Tool B there is an empty relation 40 between these data. 4 receives the first information "Documents" 42 from the "object library A" 20 in the mapping table 10 have no relation to a second piece of information 44 from Tool B. Tool B thus only receives knowledge of those data which are known from a relation.
  • both tools work with the same XML file 12, advantageously no data is lost, and data loss is avoided.
  • tool B processes only a subset of the data in the XML file 12, the remaining part of the XML file 12 or its data remain unaffected.
  • the empty relations 40 only confirm the completeness of the relations and are negligible for further considerations. In some cases it can even be advantageous to automatically add the "Object library B" 22 when reading information from the "project data A" 30 or the "object library A” 20 and thus to reduce the number of empty relations 40. In this way can "learn" Tool B from Tool A.
  • mapping tables 10 which can be exchanged, expanded and maintained without programming knowledge and / or expert knowledge regarding the the applications or tools used are required or are required.
  • mapping tables 10 can advantageously be used to support iterative engineering for several or all phases of the engineering, in order in this way to ensure a continuous or continuous flow of information.
  • the engineering process is accordingly advantageously designed to be data-oriented rather than tool-oriented or tool-oriented.
  • the engineering phases are processed by separate tools or tools, which, however, are enabled by a standardized data interface to read, visualize, edit, process the resulting documents of other engineering phases and to process their own results and / or information to expand. Since the original tool can read this extended information again and process it further without a reassignment being necessary, since a corresponding reassignment is already covered by the mapping table 10, this can advantageously support iterative engineering and increase its efficiency.
  • the XML file 12 does not have to have, as is usual with generic databases, an initially defined, predetermined and well-defined structure which meets all current and future requirements of the tools or tools used in the sense of a well-defined meta model or a meta database.
  • the mechanisms of the XML file format allow the data format to be expanded at any time in the life cycle of a system without influencing and / or changing the readability of the XML file 12 for the other tools or tools.
  • mapping tables 10 the data that are in the limited problem area of each of the tools are linked or assigned to the data that are already contained in the XML file 12.
  • Each tool or tool or application also sees the XML file 12 through its own “glasses” or its own “filter” and thus receives its own view of the data (view model).
  • File 12 stored and can be further processed in subsequent tools or applications by further mapping tables 10. In this way, the XML-based system project file grows and with the help of different mapping tables 10 each tool is presented individually, that is to say in its own way.
  • mapping tables 10 act as a kind of information filter that masks the XML project file, for example.
  • mapping tables 10 are available outside of the tools as variable configuration means, which can be created with comparatively little effort and limited specialist or expert knowledge.
  • mapping table 10 which is interchangeable, expandable, readable by a suitable generic data format such as XML and thus also maintainable.
  • FIG. 5 The aforementioned aspect of the invention is exemplified in FIG. 5 on the basis of a selection of tools involved in engineering, Tool1 to Tool 4.
  • an empty XML file 12 is initially available in simplified form.
  • a process engineer determines an R-I flow diagram (flow diagram of pipes and installations) from his specifications and creates this in Tool 1 using an object library.
  • Each of the elements of the flow diagram in particular tanks, pumps, valves, pipelines, etc., are objects of the drawing and have individual properties with their associated values, such as, for example, volume, diameter etc.
  • This information is obtained using a predetermined mapping or mapping table, mapping -Table 1, stored in the XML file 12.
  • a process control engineer needs a range of information from the RI flow diagrams, such as measuring points, control loops, sensors and actuators.
  • Mapping table 2 is used to assign the objects of the RI flow diagram for the objects of interest to the control technician, such as sensors, actuators, control loops etc.
  • a second tool, Tool 2 consequently receives a limited section of the information of interest from the XML file 12. From this, the control engineer develops the control software, for example, selects passeride devices from a device library, configures the communication systems and / or develops operator graphics. The resulting data are in turn written back to the XML file 12.
  • Tool 3 is the operating software that is shown to an operator during operation. From here, the operator can drive his system, identify irregularities, start and end processes or initiate various measures for maintenance or accident prevention. From this software, the operator can access all information that has arisen in the development cycle of the system. The selection, which information this is, is made by the mapping table 3. Mapping tables thus allow the information that can be called up to be restricted.
  • a fourth tool, Tool 4 is a service tool that is available to a system maintenance technician. From here he can call up the relevant information about the devices and functions of his system. The selection of the information available to him can be determined via mapping table 4.
  • mapping tables enables separate XML files 12, in the example shown here XML 1, XML 2, XML 3 and XML 4 or generally an extract of data from the system Extract XML file 50 that contains only the relevant information in extracts.
  • the same mapping tables in the example shown here mapping table 1, mapping table 2, mapping table 3 and mapping table 4, can be used that the respective tools, in the example shown here tool 1, tool 2, tool 3 and Tool 4.
  • mapping tables 10 to be included in XML file 12.
  • An advantage of this embodiment of the invention is that the number of files' is reduced, which simplifies the transmission.
  • the mapping tables 10 also include information about which tool accesses soft information in the XML file 12, for example. This can be used, for example, if the name of an information in the XML file 12 changes - the corresponding tools that use this information can be found quickly and their data assignments can be changed automatically. There is no need to change the tools themselves. If, on the other hand, the name of an object changes in a proprietary database of a specific tool, only the quantity of mapping tables 10 assigned to this tool has to be found and the assignments to the object in question have to be changed.
  • a further advantageous embodiment of the invention consists in adding additional information to the individual entries of the mapping tables 10, which are used for coordination and sensible distribution of the data. If, for example, a tool changes the value of an attribute in the XML file 12, the conversion device 4 (cf. FIG. 1) will immediately search all mapping tables 10 for references to this attribute in the XML file 12 and provide them with a marking , which indicates that this attribute has changed. When accessing the XML file 12, the other tools thus immediately receive the information which data have changed outside of the program since their last access.
  • the aforementioned marking can be done, for example, by flags (electronic flags) that indicate this change.
  • the corresponding tool or the respective application can leave a corresponding character in the XML file 12, for example by resetting the aforementioned marking with which it signals that its data is up to date.
  • This type of design enables the current overall condition of the system to be determined comparatively easily.
  • the file also shows which tools and system parts have not yet been brought up to date with the XML file 12 or the respective project, since a clear assignment is possible via the mapping tables 10.
  • all of the data and information generated in the entire life cycle of the system can each be provided with a time stamp or a marking and / or some other information.
  • the XML file 12 then no longer represents only the current state but also the entire history, that is to say the temporal course or the temporal development of the respective project over its entire life cycle or only over part of its life cycle.
  • the XML file 12 forms a kind of log book of the system.
  • a further advantageous embodiment of the invention enables the information of the mapping tables 10 to be stored separately in its own format, preferably in an easily readable format such as XML. This can be done in particular in individual files, a group of files, a database or a collection of files.
  • the file exchange can advantageously be file-based or by data streams, for example by means of a network using a data exchange protocol directly between different applications.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

L'invention concerne un système et un procédé de gestion et d'échange de données relatives à un projet technique, une installation technique et/ou les différents composants d'une installation, relatives notamment à un projet d'automatisation. Ce système présente une installation de traitement de données (2) comprenant un dispositif convertisseur (4) destiné à la conversion des données d'au moins un format de données exclusif dans un format de données standard et vice-versa. Le dispositif convertisseur (4) permet d'affecter une première information donnée dans le format de données exclusif à une deuxième information donnée dans le format de données exclusif par au moins une affectation de données d'au moins un format de données standard et/ou vice-versa. De plus, le dispositif convertisseur (4) est destiné à détecter pour au moins une première information donnée dans le format de données exclusif, issue de la quantité présente d'affectations de données, l'affectation de donnée correspondante associée et de convertir, à l'aide de cette affectation de données, la première information exclusive concernée en une deuxième information standard, spécifiée dans l'affectation de données et/ou pour au moins une deuxième information standard, de détecter, voire trouver, dans les affectations de données contenues dans le dispositif convertisseur (4), l'affectation de données correspondantee et de convertir, à l'aide de l'affectation de données associée, la deuxième information standard en une première information exclusive spécifiée dans l'affectation de données.
EP04714740A 2003-02-28 2004-02-26 Systeme et procede de gestion et d'echange de donnees d'un projet technique, d'une installation technique et des differents composants d'une installation Ceased EP1597675A1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
DE10308725A DE10308725A1 (de) 2003-02-28 2003-02-28 System und Verfahren zum Verwalten und zum Austausch von Daten eines technischen Projektes, einer technischen Anlage sowie einzelner Anlagenkomponenten
DE10308725 2003-02-28
PCT/EP2004/001884 WO2004077305A1 (fr) 2003-02-28 2004-02-26 Systeme et procede de gestion et d'echange de donnees d'un projet technique, d'une installation technique et des differents composants d'une installation

Publications (1)

Publication Number Publication Date
EP1597675A1 true EP1597675A1 (fr) 2005-11-23

Family

ID=32842010

Family Applications (1)

Application Number Title Priority Date Filing Date
EP04714740A Ceased EP1597675A1 (fr) 2003-02-28 2004-02-26 Systeme et procede de gestion et d'echange de donnees d'un projet technique, d'une installation technique et des differents composants d'une installation

Country Status (4)

Country Link
US (1) US8290990B2 (fr)
EP (1) EP1597675A1 (fr)
DE (1) DE10308725A1 (fr)
WO (1) WO2004077305A1 (fr)

Families Citing this family (37)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102005058802A1 (de) * 2005-12-09 2007-06-14 Abb Technology Ag System und Verfahren zur automatischen Prüfung von Planungsergebnissen
WO2008013520A1 (fr) * 2006-07-22 2008-01-31 Honeywell International Inc. Migration de système de commande
US8688749B1 (en) 2011-03-31 2014-04-01 Palantir Technologies, Inc. Cross-ontology multi-master replication
US8515912B2 (en) 2010-07-15 2013-08-20 Palantir Technologies, Inc. Sharing and deconflicting data changes in a multimaster database system
US20110137694A1 (en) * 2008-01-18 2011-06-09 Michael Schlereth Planning Device and Method for Planning a Technical Installation
US9354629B2 (en) * 2009-02-19 2016-05-31 Fisher-Rosemount Systems, Inc. Methods and apparatus to configure a process control system using an electronic description language script
EP2507724A1 (fr) * 2009-12-04 2012-10-10 ABB Research LTD Système et procédé d'intégration de données d'outils d'ingénierie
DE102010011190A1 (de) * 2010-03-11 2011-09-15 Abb Ag Verfahren und System zur Aufbereitung und Bereitstellung von Informationen zum Betrieb einer technischen Anlage
CN103189882A (zh) * 2010-08-31 2013-07-03 Abb技术有限公司 用于工程化工具之间的协作、消息传递和信息交换的系统和方法
DE102011101154A1 (de) * 2011-05-11 2012-11-15 Abb Technology Ag Verfahren und Einrichtung zur einheitlichen Benennung von gleichen Parametern unterschiedlicher Feldgeräte eines Automatisierungssystems
JP5851962B2 (ja) * 2011-09-19 2016-02-03 株式会社東芝 中継サーバ
US8782004B2 (en) 2012-01-23 2014-07-15 Palantir Technologies, Inc. Cross-ACL multi-master replication
DE102012202040B4 (de) * 2012-02-10 2023-04-06 Siemens Healthcare Gmbh Automatisches Konfigurieren von Copy&Paste-Profilen
EP2713301A1 (fr) * 2012-09-27 2014-04-02 Siemens Aktiengesellschaft Procédé et système de liaison d'une commande pour une machine sur un système informatique placé en amont
US9081975B2 (en) 2012-10-22 2015-07-14 Palantir Technologies, Inc. Sharing information between nexuses that use different classification schemes for information access control
US9501761B2 (en) 2012-11-05 2016-11-22 Palantir Technologies, Inc. System and method for sharing investigation results
EP2778413B1 (fr) 2013-03-15 2016-03-02 Kaeser Kompressoren Se Entrée de schéma R&I pour un procédé de contrôle et/ou de surveillance d'un système de compresseurs
EP2778412B1 (fr) * 2013-03-15 2019-12-25 Kaeser Kompressoren Se Développement d'un modèle supérieur pour contrôler et/ou surveiller un système de compresseurs
US8886601B1 (en) 2013-06-20 2014-11-11 Palantir Technologies, Inc. System and method for incrementally replicating investigative analysis data
US9569070B1 (en) 2013-11-11 2017-02-14 Palantir Technologies, Inc. Assisting in deconflicting concurrency conflicts
US9009827B1 (en) 2014-02-20 2015-04-14 Palantir Technologies Inc. Security sharing system
US9021260B1 (en) 2014-07-03 2015-04-28 Palantir Technologies Inc. Malware data item analysis
US9785773B2 (en) 2014-07-03 2017-10-10 Palantir Technologies Inc. Malware data item analysis
US10572496B1 (en) 2014-07-03 2020-02-25 Palantir Technologies Inc. Distributed workflow system and database with access controls for city resiliency
KR102601511B1 (ko) * 2015-05-28 2023-11-14 에이치디한국조선해양 주식회사 선박 데이터 통합 관리 방법 및 장치
DE102015209895A1 (de) * 2015-05-29 2016-12-01 Kuka Roboter Gmbh Verfahren zur Konvertierung von zumindest einer ersten Sicherheitskonfigurationsdatei
CN106682011B (zh) * 2015-11-06 2019-12-10 北京国双科技有限公司 利用图形展示数据的方法和装置
US10621198B1 (en) 2015-12-30 2020-04-14 Palantir Technologies Inc. System and method for secure database replication
KR102473668B1 (ko) * 2016-03-02 2022-12-01 삼성전자주식회사 발광 소자 실장 기판 및 이를 이용한 발광 패키지
US10671038B2 (en) 2016-07-15 2020-06-02 Fisher-Rosemount Systems, Inc. Architecture-independent process control
US10262053B2 (en) 2016-12-22 2019-04-16 Palantir Technologies Inc. Systems and methods for data replication synchronization
US10068002B1 (en) 2017-04-25 2018-09-04 Palantir Technologies Inc. Systems and methods for adaptive data replication
US10430062B2 (en) 2017-05-30 2019-10-01 Palantir Technologies Inc. Systems and methods for geo-fenced dynamic dissemination
US11030494B1 (en) 2017-06-15 2021-06-08 Palantir Technologies Inc. Systems and methods for managing data spills
US10380196B2 (en) 2017-12-08 2019-08-13 Palantir Technologies Inc. Systems and methods for using linked documents
US10915542B1 (en) 2017-12-19 2021-02-09 Palantir Technologies Inc. Contextual modification of data sharing constraints in a distributed database system that uses a multi-master replication scheme
DE102019128104A1 (de) * 2019-10-17 2021-04-22 Mhp Management- Und It-Beratung Gmbh Fertigungssteuerungssystem

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5119465A (en) * 1989-06-19 1992-06-02 Digital Equipment Corporation System for selectively converting plurality of source data structures through corresponding source intermediate structures, and target intermediate structures into selected target structure
US5557780A (en) * 1992-04-30 1996-09-17 Micron Technology, Inc. Electronic data interchange system for managing non-standard data
EP1122652A1 (fr) * 2000-02-03 2001-08-08 Mitsubishi Denki Kabushiki Kaisha Système pour l'intégration de données

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5404488A (en) * 1990-09-26 1995-04-04 Lotus Development Corporation Realtime data feed engine for updating an application with the most currently received data from multiple data feeds
US5708828A (en) * 1995-05-25 1998-01-13 Reliant Data Systems System for converting data from input data environment using first format to output data environment using second format by executing the associations between their fields
US6295541B1 (en) * 1997-12-16 2001-09-25 Starfish Software, Inc. System and methods for synchronizing two or more datasets
US20020184308A1 (en) * 1999-08-23 2002-12-05 Levy Martin J. Globalization and normalization features for processing business objects
EP1117049A1 (fr) * 2000-01-14 2001-07-18 Sun Microsystems, Inc. Conversion dynamique de données
US6785673B1 (en) * 2000-02-09 2004-08-31 At&T Corp. Method for converting relational data into XML
US7031956B1 (en) * 2000-02-16 2006-04-18 Verizon Laboratories Inc. System and method for synchronizing and/or updating an existing relational database with supplemental XML data
US7124144B2 (en) * 2000-03-02 2006-10-17 Actuate Corporation Method and apparatus for storing semi-structured data in a structured manner
US7114147B2 (en) * 2000-03-09 2006-09-26 Electronic Data Systems Corporation Method and system for reporting XML data based on precomputed context and a document object model
JP2002024211A (ja) * 2000-06-30 2002-01-25 Hitachi Ltd 文書管理方法およびシステム並びにその処理プログラムを格納した記憶媒体
US7024413B2 (en) * 2000-07-26 2006-04-04 International Business Machines Corporation Method of externalizing legacy database in ASN.1-formatted data into XML format
US20020059566A1 (en) * 2000-08-29 2002-05-16 Delcambre Lois M. Uni-level description of computer information and transformation of computer information between representation schemes
DE50111786D1 (de) * 2000-12-15 2007-02-15 Siemens Ag Verschlüsselung von Steuerungsprogrammen
DE10138533A1 (de) 2000-12-15 2002-07-11 Siemens Ag Bereitstellung von Projekt- und/oder Projektierungsdaten eines Automatisierungsprojekts in einem durch eine standardisierte Meta-Sprache, insbesondere XML, definiertem Format
US7392237B2 (en) * 2001-04-26 2008-06-24 Siemens Medical Solutions Usa, Inc. Identifier code translation system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5119465A (en) * 1989-06-19 1992-06-02 Digital Equipment Corporation System for selectively converting plurality of source data structures through corresponding source intermediate structures, and target intermediate structures into selected target structure
US5557780A (en) * 1992-04-30 1996-09-17 Micron Technology, Inc. Electronic data interchange system for managing non-standard data
EP1122652A1 (fr) * 2000-02-03 2001-08-08 Mitsubishi Denki Kabushiki Kaisha Système pour l'intégration de données

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
WO2004077305A1 (fr) 2004-09-10
US20070005805A1 (en) 2007-01-04
DE10308725A1 (de) 2004-09-09
US8290990B2 (en) 2012-10-16

Similar Documents

Publication Publication Date Title
WO2004077305A1 (fr) Systeme et procede de gestion et d'echange de donnees d'un projet technique, d'une installation technique et des differents composants d'une installation
DE602005005924T2 (de) Einheitliches Datenformat für Messgeräte
EP1723513B1 (fr) Procede pour configurer un programme informatique
EP1215589A2 (fr) Provision de données de projets dans un format d'une meta-langue standardisée
EP1176482A1 (fr) Méthode et logiciel pour la génération d'un système de régulation ou de commande
DE102007040823A1 (de) Editier- und Berichts-Tool für Grafische Programmiersprachenobjekte
EP0697640B1 (fr) Dispositif de données pour dispositif à raccorder au réseau de communication et méthode de génération de disposition de données
DE10149693A1 (de) Objekte in einem Computersystem
DE69907714T2 (de) Komponentbasiertes quellcodegeneratorverfahren
DE10026478A1 (de) Verfahren zur Generierung anwendungsspezifischer Eingabedateien
DE102012001406A1 (de) Automatische Konfiguration eines Produktdatenmanagementsystems
EP2290593A1 (fr) Procédé d'assistance d'une planification d'une installation technique
EP1442340A1 (fr) Chargement de donnees dans un systeme d'automatisation
EP1515207A1 (fr) Objet d'automatisation et méthode pour la description d'un objet d'automatisation en utilisant une métalangage
EP3850443B1 (fr) Procédé d'intégration des données des actifs d'une installation technique dans une plate-forme, plate-forme numérique et produit programme informatique
DE10131956A1 (de) Verfahren und System zur Inbetriebsetzung von MES-Komponenten
DE4310615C2 (de) Entwurf elektrischer Vorrichtungen mit mehreren Entwurfswerkzeugen, die zumindest teilweise untereinander inkompatibel sind
EP2329374A1 (fr) Module de test et procédé destiné à tester un intergiciel de mapping o/r
EP1621945B1 (fr) Garantie de la consistance de données dans un système d'automatisation
DE10138533A1 (de) Bereitstellung von Projekt- und/oder Projektierungsdaten eines Automatisierungsprojekts in einem durch eine standardisierte Meta-Sprache, insbesondere XML, definiertem Format
EP1237075A1 (fr) Préprocesseur pour une définition de type de document, système pour manipuler des documents de language de balisage, méthode et produit de programme pour ordinateur
DE102004023634B4 (de) Verfahren zur Vollständigkeits- und Konsistenzprüfung einer Informationsbibliothek
EP3355186A1 (fr) Génération et exécution de modules logiciels
EP1600854A2 (fr) Procédé pour travailler avec les langages de programmation Kontaktplan et Funktionsplan et éditeur graphique approprié
EP1795999A1 (fr) Procédé et système destinés à la transformation d'éléments d'un programme de commande établi dans une représentation de plans de contact à l'intérieur d'une représentation de plans de fonctions

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

AK Designated contracting states

Kind code of ref document: A1

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

AX Request for extension of the european patent

Extension state: AL LT LV MK

RIN1 Information on inventor provided before grant (corrected)

Inventor name: DRATH, RAINER

Inventor name: FAY, ALEXANDER

Inventor name: BORT, PETER

DAX Request for extension of the european patent (deleted)
REG Reference to a national code

Ref country code: DE

Ref legal event code: R003

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