[go: up one dir, main page]

WO2003009071A1 - Systeme et procede d'exportation ou d'importation de donnees d'objet dans un systeme d'execution de fabrication (mes) - Google Patents

Systeme et procede d'exportation ou d'importation de donnees d'objet dans un systeme d'execution de fabrication (mes) Download PDF

Info

Publication number
WO2003009071A1
WO2003009071A1 PCT/US2001/022833 US0122833W WO03009071A1 WO 2003009071 A1 WO2003009071 A1 WO 2003009071A1 US 0122833 W US0122833 W US 0122833W WO 03009071 A1 WO03009071 A1 WO 03009071A1
Authority
WO
WIPO (PCT)
Prior art keywords
database
data
xml
model object
logic
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
PCT/US2001/022833
Other languages
English (en)
Inventor
Huey-Shin Yuan
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.)
Applied Materials Inc
Original Assignee
Applied Materials Inc
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 Applied Materials Inc filed Critical Applied Materials Inc
Priority to PCT/US2001/022833 priority Critical patent/WO2003009071A1/fr
Priority to KR10-2004-7000929A priority patent/KR20040014671A/ko
Publication of WO2003009071A1 publication Critical patent/WO2003009071A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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
    • G06F16/86—Mapping to a database
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G05B19/418—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM]
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/30—Nc systems
    • G05B2219/31—From computer integrated manufacturing till monitoring
    • G05B2219/31166—Access data by name, object, stored in list, database
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/30—Nc systems
    • G05B2219/31—From computer integrated manufacturing till monitoring
    • G05B2219/31323—Database for CIM
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/30—Nc systems
    • G05B2219/31—From computer integrated manufacturing till monitoring
    • G05B2219/31372—Mes manufacturing execution system
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/30—Nc systems
    • G05B2219/32—Operator till task planning
    • G05B2219/32142—Define device, module description using xml format file
    • Y—GENERAL 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
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]
    • Y—GENERAL 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
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/80—Management or planning

Definitions

  • This invention relates to Manufacturing Execution Systems (MES) and, more particularly, to importing and/or exporting MES model object data.
  • MES Manufacturing Execution Systems
  • MES Manufacturing Execution Systems
  • MES functionality includes (1) batch/lot management, (2) real-time operations management, (3) quality management, (4) resource management (including scheduling, dispatching, equipment monitoring, and preventive maintenance), (5) direct and indirect labor coordination and dispatching, (6) specifications and work instructions, (7) recipe management, (8) detailed material control and genealogy, (9) actual cost tracking, and the like.
  • An MES at some level of abstraction, models the manufacturing operations that it helps monitor and coordinate.
  • An MES is typically an object-oriented application that often exposes the behavior of the application, and specifically the application's objects, through an interface.
  • the modeling effort is costly and time consuming but highly important to the success of the MES. Because these manufacturing operations and related activities tend to be complex, many modern Manufacturing Execution Systems employ databases to hold various types of object data.
  • standards have been developed to describe, at some level of abstraction, the interfaces to the MES components.
  • CIM is a standard known in the MES art for describing a model of the structural setup of a manufacturing operation, e.g., machines, materials, how to process materials, and the like.
  • development systems often include similar physical components and systems to the eventual, desired production system, including for example the same or similar MES.
  • the development system is used to construct, test and tune a model in the MES.
  • the production system (or target system) differs from the development system in some aspects.
  • the production system may use a certain physical component that has a corresponding physical component in the development system but the development component and the production component differ in some attributes, e.g., execution parameters.
  • this difference is inevitable because the production components are too scarce or expensive to use in a development system.
  • the production component may not yet exist in a "released" form, yet manufacturers nonetheless benefit from creating and modeling a production system in anticipation of its eventual release. Consequently, though a development system is often similar to an eventual production system, invariably some differences exist.
  • migration of the data from a development system to a production system is ad hoc and relies on the use of a skilled technician.
  • the technician must first understand an interface to the MES of interest, e.g.., the one from which data is to be exported from, and then he or she must write some form of script to invoke the model objects to obtain the data.
  • This approach is time consuming, costly, and error prone.
  • the script may no longer work (e.g., it may refer to now non-existent or changed objects).
  • One aspect of the invention uses XML to express model object data for an MES application model object.
  • the data for the model object is held in a database.
  • the database definition is used to construct XML tag information and the database values are used to construct XML element contents.
  • the XML tag information is used to construct database references, and the XML element contents are used to load the database.
  • logic parses an XML expression and converts XML tag labels to database address information, and converts XML element contents to database values.
  • a class is derived from an MES model object class, and the class so derived inherits all functionality from the MES model object class.
  • the class further includes import method logic to receive an XML expression of model object data and load the XML-expression of the data in the database.
  • the class further includes export method logic to create an XML expression of model object data in the database.
  • data may be imported into an MES application having at least one model object, by forming an XML expression of the object data.
  • the XML expression is sent to the MES application, and the MES application parses the XML expression to determine the object type, the object parts, and the object data values.
  • the MES application loads the determined object type, the object parts, and the object data values into a database corresponding to the MES application.
  • a DTD expression of the object class definition is formed and the XML expression is validated against the DTD expression.
  • import logic is layered over the model object, and the import logic defines an external interface for loading model object data.
  • the import logic includes logic to invoke the model object to load the model object data into the database.
  • export logic is layered over the model object, the export logic defines an external interface for obtaining model object data.
  • the export logic includes logic to invoke the model object to obtain the model object data from the database.
  • a MES includes a client and server computer.
  • the client has a user interface control for exporting or importing selected model objects of the MES and for constructing a client request to request export or import of selected objects.
  • the server has the MES application executing thereon.
  • the MES application is organized as a relationship of model objects, with each model object having data therefor stored in a database.
  • the application includes import and export logic, responsive to the client request, for forming an XML expression of model object data in response to an export request, and for loading data expressed in XML form into the database in response to an import request.
  • Figure 1 is an architectural diagram of a preferred embodiment of the invention
  • Figure 2 is a flow chart showing the logic for exporting information according to a preferred embodiment of the invention.
  • Figure 3 is flow chart showing the logic for reading information from a database and writing an XML-based version thereof according to a preferred embodiment of the invention
  • Figure 4 is a flow chart showing the logic for importing information according to a preferred embodiment of the invention.
  • Figure 5 is flow chart showing the logic for reading information from an XML document and writing corresponding information to a database according to a preferred embodiment of the invention
  • Figures 6A-6B show class and object expressions for layered export and import software of a preferred embodiment
  • Figure 7 is a system diagram of exemplary hardware for a client or server computer according to exemplary embodiments of the invention.
  • a model object may contain many parts, such as product, material, lot templates linked to process flows, and the like.
  • the model information may define the data interrelationships.
  • the MES model is object-oriented, the data for the various objects is held in a table-based database, such as ones available from Oracle Corporation.
  • a preferred embodiment of the invention facilitates importation and exportation of model data by layering importation and exportation logic over the model.
  • the importation and exportation logic works, even if the underlying model is changed. That is, no tools need to be redeveloped or modified because the model changes, and system administrators do not need to track model changes to ensure that , • importation and exportation functionality works.
  • XML extensible markup language
  • DTD Document Type Definition
  • DTD facilitates the use of an XML document by defining valid structure so that XML documents may be parsed to test their structural validity.
  • XML and DTDs are based on well defined standards, and thus tools may be more easily developed to modify or create information to be imported and/or exported from a system.
  • a user identifies MES model object(s) of a source environment to be exported (e.g., specific instances or all such objects) and, through a graphical user interface (GUI), may requests that it (they) be exported.
  • Software layered over the model objects of the source environment, responds by reading and extracting the relevant information from a database holding the object data and writing the information into an XML document having a DTD corresponding to the selected object class definition.
  • the XML document may then be accessed and/or modified with other tools. For example, an XML editor may be used to view exported information and to allow a user to modify that data as necessary so that it may be imported into another system.
  • XML-forms of information that should be imported, or loaded, into a target system by referring to a DTD that defines the structure of data that may be imported into a system.
  • an XML document may be used to hold object data to be imported into a target environment.
  • Other software layered over the model objects of the target environment, read the XML information, effectively deconstruct it into its parts, and load the information in the target database.
  • the DTD may be used to provide one measure of information validation (i.e., DTD validation against the XML document, as known in the art) before subsequent database validation by the target system.
  • Figure 1 shows an exemplary system on which preferred embodiments of the invention may be manifested.
  • a client computer 102 may communicate with a server computer over a communication network, represented collectively by the paths 106, 108, 110, and 112.
  • the client 102 includes a browser 114.
  • the browser is an Explorer browser, available through Microsoft Corporation.
  • This one embodiment uses an ActiveX control (implemented with conventional technology available through Microsoft Corporation) to provide certain GUI functionality described below. Though no arrow is shown between the Active X control 116 and the browser 114, these two components cooperate in a known way. Other browser and GUI control techniques may be substituted under the principles of the invention without loss of generality.
  • the server 104 includes a first application 118, a second application 120, and XML access application 122, and at least one active server page 124.
  • the first application 118 operates with a first database instance 126, which for purposes of this description can be considered as a source database instance, representative of a development environment.
  • the second application 120 operates with a second database instance 128, which for purposes of this description can be considered as a target database instance, representative of a production environment.
  • the first and second applications 118, 120 and the XML access application 122 all may communicate with at least one XML document 130, which may be manifested as a file, though it also may be manifested in other forms.
  • the active server page 124 provides one way (not the only way) to access the server applications 118, 120 in response to commands from the browser 114.
  • Figure 1 among other things illustrates that information may be exported from one type of MES application 118 and imported into another 120 on the same server, but it should be appreciated that the various applications shown on the one server may, and indeed are expected to be, distributed among several servers. For example, each MES application may have its own server.
  • the first and second applications are object-oriented MES applications constructed according to conventional techniques.
  • the actual type of MES applications and their MES functions are not material to the invention and thus their detailed logic is not described.
  • the MES objects also referred to herein as model objects, or domain objects
  • COM + is a known approach of expressing object behavior and interfaces.
  • the MES object data is held in persistent form in the corresponding database (e.g., application 118 has data in database instance 126).
  • the database instances 126, 128 organize model object data as tables. For example, visualizing a simple table, the leftmost column may correspond to a class, and each column may correspond to a member of the class definition. Each row in the exemplary table would then correspond to an object instance, in which the actual values for a given row and column correspond to that instance's member's value.
  • the data relationships may define further levels of hierarchy and references as is known in the art.
  • the operative issue is that the metadata of the table definitions corresponds to MES model class definitions and that mechanisms are known for getting and setting object information held in the object instance and/or the corresponding database entities.
  • the metadata for the database may express that a given column holds integer values, character data, a reference to another database entity, etc.
  • the XML access application 122 may be an XML editor or other tool that can create and/or present XML documents as described below.
  • an XML editor may be used to modify an XML document that was exported from one application, or another tool may be used to create an XML document consistently with a DTD.
  • the active server page 124 in an exemplary embodiment, is a Microsoft Active Server Page.
  • the ASP 124 provides one way for accessing the applications by paths 132, 134, whereas paths 106 and 108 provide another (in which information is passed to the applications as COM+ arguments).
  • FIG. 2 is a flowchart showing the logic for exporting information according to a preferred embodiment of the invention.
  • the logic starts 200, and with the assistance of the browser (114, Fig. 1) a user selects objects to be exported 205.
  • the ActiveX control (116, Fig. 1), with the assistance of auto-discovery techniques, gathers a list of the model object types (i.e., classes) that support export and/or import functionality. This list is then presented to a user to identify the types of objects that may be exported. The user may then select all objects of a given object type or just specific identified instances. The user also provides a filename in which an XML document representation of the model object data should be held.
  • the Active X control (116, Fig.
  • the server application (118, Fig. 1) validates that the request refers to valid database objects 215.
  • the server application accesses the relevant source database instance (126, Fig. 1) holding the information for the identified object, reads the information corresponding to the request, and writes that data 220 as an XML document (150, Fig.l).
  • the first application (118, Fig. 1) returns 225 status information to the Active X control (116, Fig. 1).
  • the status is then displayed 230 to the user via a browser (114, Fig. 1) to the user who initiated the exportation, and the logic ends 299.
  • Figure 3 is a flow chart more specifically showing the logic of reading objects from a database and writing it as an XML document as described above. The logic starts
  • the client request may identify all or select objects of an identified object type, and an internal list representation of objects to be exported is constructed accordingly.
  • the first, application (118, Fig. 1) then determines
  • the application updates 315 an error information data structure and determines 320 whether the client request has identified other objects to be exported. If the identified object exists in the database (see 310), the first application (118, Fig. 1) reads 325 a complete version of the object's data from the database (126, Fig. 1). This reading is explained in further detail below.
  • the collected information is then formatted and written 330 into an XML document (130, Fig. 1). More specifically, the XML document has tags to mark the data, in which the tag labels correspond to the database entity information and in which the contents correspond to the actual table data.
  • the process of reading may require iteration through the object data, and a check is made 335 to determine whether all the information of a given object being exported has been written to an XML document. As part of the exportation, other information is gathered and eventually reported, such as the number of records exported. If not all of the information has been gathered, the iteration continues 330 to format the object data accordingly. If the object has been fully formatted and written to an XML document (130, Fig. 1), then a check is made 320 whether the exportation request has been completed, i.e., whether there are other objects to be exported. If not, as outlined above, a subsequent data object in the request is selected and the processing continues as described above. If the exportation request has been completed the processing ends 399.
  • the reading and formatting of the object data is greatly facilitated by layering the software over the model software.
  • the MES applications are composed of objects implementing the model provided by that application. These models include "get” and “set” functionality to get and set object state, following well known object-oriented programming convention. These gets and sets have the logic for accessing the underlying database as necessary and the get and set routines are published or otherwise known.
  • a preferred embodiment builds on the above as follows.
  • a new export class is defined as a derived class of the actual model class. As such, the new export class inherits all of the functionality defined in the actual model class, including the gets and sets just mentioned.
  • the new class defines a constructor method (constructor methods are known in the art) in which an object identifier is passed in as a variable and used to get and initialize object data members with the information corresponding to that object identifier. Thus, when an instance of this new class is instantiated it will be constructed with the data corresponding to the object identifier.
  • An instance of the new export class may then in this fashion be constructed, passing in the identifier of the object to be exported, and an export object will be created that will be initialized to contain member data corresponding to the object to be exported.
  • this portion of the new export object is a copy of the actual model object.
  • the new class also includes export method logic that creates the XML document in the following manner. Following the organization of the object's data in the database, an opening tag is written for the highest level database entity for that object, followed by the entities that that entity contains, which may be other entities or data. Closing tags and empty tags are inserted as appropriate, depending on the database contents. The highest tag corresponds to the object class, and each other tag label corresponds to the label used in the database, i.e., the column name of a table. Appendix A shows an exemplary XML document created in this manner. In this example, "ENTITYDETAILS" corresponds to the object name or class, and the tags underneath correspond to the table column names. (This method is only called after other software writes prolog information to the document, identifying a corresponding DTD, a root element, and the like.)
  • a conventional code generator may be used to do the following.
  • the code generator is passed the object name or class (e.g., ENTITYDETAILS in the above example) along with the table name corresponding to that object name, and along with a description of other entities that that object inherits from (in other words, other tables that may be referenced from one of the object members).
  • the generators "script" uses the above to construct C++ code to do the following:
  • Tag label will either be the passed in object name (for the highest level tag) or the column names of the table (which may be determined from the database's metadata).
  • the generation is facilitated in that the organization of the data is already known and expressed as database metadata.
  • the database metadata may be used to also generate a DTD expression of the metadata as well and thus generate a DTD for the object type at issue. See Appendix B for an exemplary DTD corresponding to the object data expressed in XML document of Appendix A.
  • the generated code may need developer modification because the database information is not easily translated into an XML form. For example, if the database information is a reference to another database entity, a developer may need to modify the automatically generated code to reflect and properly handle this type of entity.
  • the interface to the export logic remains the same, i.e., the export methods, and thus the tool to export object data does not need to change when the model changes. Instead, the export tool needs to only instantiate an object from the new export class (derived from the object class to be exported) and to pass to the constructor the object identifier for the object to be exported. The instantiated object will thus automatically have all of the logic to obtain any data of interest.
  • that object's (i.e., the one from the derived class) export method is invoked to write the XML data. As outlined above, this will write the XML file. The corresponding DTD file for this object type was created at the time the export logic code was generated.
  • a DTD is created to represent the object data expressed in the XML document holding exported data.
  • the DTD may also be used by other tools (e.g., XML editor) to facilitate the modification of such an XML document (e.g., for subsequent import in another embodiment) or to create an XML document automatically.
  • a DTD may first be created based on the database metadata, and the DTD form may subsequently be used by code generators to create the XML document write commands to insert the tag information.
  • the example of Appendix B uses conventional XML syntax to show that the entities are parsed character data (PCDATA), it will be appreciated that more restrictive forms of DTDs may be written, e.g., other data forms, such as integer, defining sequence relationships, and the like.
  • Figure 4 is a flowchart showing the logic for importing information according to the a preferred embodiment of the invention.
  • the logic starts 400, and with the assistance of the browser (114, Fig. 1) a user selects objects to be imported 405 and specifies an importation policy, e.g., add information as specified in the request, or update information only if target database does not have the information.
  • the Active X control (116, Fig. 1) locates the appropriate server application, in this example the second application (120, Fig. 1) , and sends the import request 410 to that application.
  • the importation request identifies the XML document holding the data to be imported. This may be from the previously explained exportation process, an edited version thereof, or a document independently created.
  • the server application (120, Fig. 1) validates 415 the XML document with reference to the DTD, i.e., that the XML document has the form defined in the DTD.
  • the server application then accesses the XML document (130, Fig.l), processes the XML document data, and loads 420 the corresponding information into the identified target database instance (128, Fig. 1).
  • the second application (120, Fig. 1) returns 425 status information to the Active X control (116, Fig. 1).
  • the status is then displayed 430 to the user via a browser (114, Fig. 1) to the user who initiated the importation, and the logic ends 499.
  • Figure 5 is a flow chart more specifically showing the logic of loading objects into a database based on the information in an XML document.
  • the logic starts 500 by reading 505 information from the client importation request represented, in part, by the XML document (130, Fig.l) and collecting sufficient information to identify a first selected object in the request.
  • the second application 120, Fig. 1 then attempts to read 510 the data corresponding to that object from the target database (128, Fig. 1).
  • the software determines 515 whether the identified object already exists in the target database. If it does exist, the application analyzes 520 the import policy specified in the client request to determine whether existing data should be over-ridden with the data from the XML document (130, Fig. 1).
  • the software iterates 525 through the XML document (130, Fig. 1) to determine if the document contains more data 525 for other objects to be imported. If either the identified object does not exist in the database (see 515) or if the client requested indicated that existing data should be over-ridden (see 520), the application reads 530 all of the information in the XML document (130, Fig. 1) corresponding to the identified object. The XML information collected for the document is validated 535 against the database. This validation in some cases will be more robust than that done at the DTD-level of validation.
  • the XML document may satisfy DTD validation but fail database validation.
  • the application determines 540 whether all of the data in the XML document is valid against the database metadata. If the data is not valid, the software accumulates 545 this error information in a data structure. If the data is valid, the software updates the target database (128, Fig. 1) with the object data compiled from the XML document. This update 550 includes updating all of the information related to the updated object, for example, in the case of hierarchical objects referring to other data and objects. Then, as outlined above, the software iterates 525 through the XML document (130, Fig. 1) to determine if the document contains more data. If so, the process repeat as described above; if not, the update process ends 599.
  • FIG. 6B illustrates the process.
  • an import class is defined that is derived from the actual MES object class.
  • the derived class like the case above, includes generated and modified code, which in this case has calls to library primitives to parse the XML document to collect table references, e.g., table name and columns, and to collect the actual data from the tag contents.
  • the generated code also has the logic to write to the database as needed.
  • the XML contents will need to be converted to a different type, e.g., integer, and in some cases this conversion may need to rely DTD definition and/or the metadata definition.
  • this code may need developer modification, but also like the above changes to the model will not require changes to the import tool.
  • the instantiated object of the new class is passed the identifier for the object that should receive the data so that that object may be initiated appropriately. That object may then be invoked with "gets” to see what state it has (e.g., see above in conjunction with import policy) and with "sets" as needed.
  • Figure 7 is a high-level diagram of a computer system that may be used for the client or servers shown in figure 1.
  • the system 700 includes one or more processors 702, a memory 704 (potentially organized as virtual memory 706), display device 708, and input/out logic 710 in communication via a bus 712.
  • the embodiments offer several advantages.
  • the embodiments allow XML documents and DTD information to be used to express object data, even in embodiments where the database is not object oriented. This allows the object data to be validated (in a DTD sense) before it is imported.
  • XML and DTD documents use standards that facilitate the development of tools.
  • the import and export utility does not need to change when the model changes and instead continues to work. Exportation and importation are greatly benefited and can be largely automated. Users do not need to develop custom scripts for export or import, nor do they need to enter vast amounts of information manually.
  • the tools may be implemented with known internet and intranet technologies.
  • XML also facilitates the support of internationalization of the information, i.e., so that the intermediary form may be presented in multiple languages.
  • the XML document intermediary form may also be used to perform exportation and importation without having an intermediary file.
  • XML forms other than XML as an intermediary form.
  • ASCII or SGML may be used to convey information in an organized way.
  • XML may foster the use of a specialized language based on XML that may also be used.
  • a preferred embodiment layered import and export logic over the model by deriving classes from the model classes and adding import and export methods thereto, other approaches may be used.
  • the derived class may have both import and export methods for a given object type.
  • the logic may be layered in other ways so that they exploit the gets and sets of the model data yet provide a consistent interface to the tools so that the import and export utility does not need to change when the model changes.
  • the exemplary embodiment above used Active X to convey client requests as COM + arguments, but other approaches may be substituted.
  • the browser may interact with the ASP page to invoke the applications as needed.
  • the imports and export requests may then be performed through corresponding HTML pages.

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Manufacturing & Machinery (AREA)
  • Quality & Reliability (AREA)
  • Automation & Control Theory (AREA)
  • Data Mining & Analysis (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

Le langage XML est utilisé pour exprimer des données d'objet modèle pour un objet modèle d'application MES. Lesdites données de l'objet modèle sont contenues dans une base de données. Pour l'exportation d'informations, la définition de ladite base de données est utilisée pour construire des informations de balisage XML et les valeurs de ladite base de données sont utilisées pour la construction des contenus d'éléments XML. Pour l'importation d'informations, les informations de balisage XML sont utilisées pour la construction des références de base de données, et les contenus d'éléments XML sont utilisés pour le chargement de la base de données. Pour l'exportation d'informations, les noms d'informations d'adresses de la base de données sont utilisés pour la formation des marqueurs de balisage XML, et les données d'objet modèle contenues dans la base de données sont utilisées pour la formation des contenus d'éléments XML. De nouvelles classes sont créées par dérivation de la classe d'objets modèles. Lesdites nouvelles classes héritent de la fonctionnalité des classes d'objets modèles mais elles comprennent en outre de nouveaux procédés d'importation et d'exportation qui enroulent, ou appliquent, de façon efficace la logique d'importation ou d'exportation autour des objets modèles. Des définitions de types de documents (DTD) peuvent être utilisées pour la validation des documents XML qui sont exportés ou importés d'un tel système. Une génération de codes facilite la création des définitions de la nouvelle classe et des DTDs. Pour la génération de codes il est tenu compte des méta-données de la base de données.
PCT/US2001/022833 2001-07-20 2001-07-20 Systeme et procede d'exportation ou d'importation de donnees d'objet dans un systeme d'execution de fabrication (mes) Ceased WO2003009071A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/US2001/022833 WO2003009071A1 (fr) 2001-07-20 2001-07-20 Systeme et procede d'exportation ou d'importation de donnees d'objet dans un systeme d'execution de fabrication (mes)
KR10-2004-7000929A KR20040014671A (ko) 2001-07-20 2001-07-20 제조 실행 시스템에서 객체 데이터를 익스포트하거나임포트하는 시스템 및 방법

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2001/022833 WO2003009071A1 (fr) 2001-07-20 2001-07-20 Systeme et procede d'exportation ou d'importation de donnees d'objet dans un systeme d'execution de fabrication (mes)

Publications (1)

Publication Number Publication Date
WO2003009071A1 true WO2003009071A1 (fr) 2003-01-30

Family

ID=21742714

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2001/022833 Ceased WO2003009071A1 (fr) 2001-07-20 2001-07-20 Systeme et procede d'exportation ou d'importation de donnees d'objet dans un systeme d'execution de fabrication (mes)

Country Status (2)

Country Link
KR (1) KR20040014671A (fr)
WO (1) WO2003009071A1 (fr)

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004102420A1 (fr) * 2003-05-19 2004-11-25 Sap Aktiengesellschaft Importation et exportation de donnees pour dispositifs informatiques
CN100361121C (zh) * 2003-07-11 2008-01-09 北京直真节点技术开发有限公司 一种通用对象建模方法及通用对象管理系统
US7359768B2 (en) 2004-10-29 2008-04-15 International Business Machines Corporation Route input system
EP1923760A2 (fr) 2006-10-20 2008-05-21 Rockwell Automation Technologies, Inc. Interface MES standard pour fabrication en série
EP1849104A4 (fr) * 2004-11-22 2009-11-11 Ibm File d'attente d'exportation pour un systeme logiciel d'entreprise
US7799273B2 (en) 2004-05-06 2010-09-21 Smp Logic Systems Llc Manufacturing execution system for validation, quality and risk assessment and monitoring of pharmaceutical manufacturing processes
EP2315138A1 (fr) * 2009-09-30 2011-04-27 Siemens Aktiengesellschaft Amélioration de la performance d'un système d'exécution de fabrication
KR101081678B1 (ko) 2003-07-31 2011-11-09 후지쯔 가부시끼가이샤 Ｘｍｌ 드리븐 아키텍쳐에서의 정보 처리 방법 및 기억 매체
US8843881B2 (en) 2007-01-12 2014-09-23 Microsoft Corporation Transporting and processing foreign data
EP2874035A1 (fr) * 2013-10-29 2015-05-20 Kabushiki Kaisha Yaskawa Denki Système de production d'équipement industriel avec serveur de production
CN104808639A (zh) * 2015-04-29 2015-07-29 中国石油大学(华东) 一种制药产品制造执行系统及方法
CN109522268A (zh) * 2018-12-03 2019-03-26 中国南方电网有限责任公司 一种基于校验和导入相分离的电网svg导入分析方法
US11380926B2 (en) * 2019-08-14 2022-07-05 The Curators Of The University Of Missouri Fuel cell having corrugated membrane electrode assembly
CN117806600A (zh) * 2024-02-28 2024-04-02 江苏信而泰智能装备有限公司 一种mes的产线测试平台的构建方法、系统及设备

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101304312B1 (ko) * 2011-11-04 2013-09-06 주식회사 미라콤아이앤씨 제조 실행 시스템 및 이를 위한 기록매체

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1995034866A1 (fr) * 1994-06-14 1995-12-21 Telefonaktiebolaget Lm Ericsson Procede et systeme de manipulation de representations intelligentes de materiel reel dans un systeme informatique graphique
US6253366B1 (en) * 1999-03-31 2001-06-26 Unisys Corp. Method and system for generating a compact document type definition for data interchange among software tools
WO2001052055A2 (fr) * 2000-01-10 2001-07-19 Wind River Systems, Inc. Systeme et procede de mise en oeuvre d'un modele objet a partir d'un systeme cible souple execute au moyen de donnees
WO2001057823A2 (fr) * 2000-02-01 2001-08-09 Domain Logix Corporation Appareil et procede utilises pour la gestion d'outil web
WO2002017150A1 (fr) * 2000-08-23 2002-02-28 Pri Automation, Inc. Systeme de commande d'outils accessible sur internet, utilise dans une installation de fabrication de semi-conducteurs

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1995034866A1 (fr) * 1994-06-14 1995-12-21 Telefonaktiebolaget Lm Ericsson Procede et systeme de manipulation de representations intelligentes de materiel reel dans un systeme informatique graphique
US6253366B1 (en) * 1999-03-31 2001-06-26 Unisys Corp. Method and system for generating a compact document type definition for data interchange among software tools
WO2001052055A2 (fr) * 2000-01-10 2001-07-19 Wind River Systems, Inc. Systeme et procede de mise en oeuvre d'un modele objet a partir d'un systeme cible souple execute au moyen de donnees
WO2001057823A2 (fr) * 2000-02-01 2001-08-09 Domain Logix Corporation Appareil et procede utilises pour la gestion d'outil web
WO2002017150A1 (fr) * 2000-08-23 2002-02-28 Pri Automation, Inc. Systeme de commande d'outils accessible sur internet, utilise dans une installation de fabrication de semi-conducteurs

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
KLEIN B: "APPLICATION DEVELOPMENT XML MAKES OBJECT MODELS MORE USEFUL", INFORMATIONWEEK, MANHASSET, NY, US, PAGE(S) 1A-6A, ISSN: 8750-6874, XP002935959 *
SUZUKI J ET AL: "Toward the interoperable software design models: quartet of UML, XML, DOM and CORBA", PROCEEDINGS IEEE INTERNATIONAL SOFTWARE ENGINEERING STANDARDS SYMPOSIUM, XX, XX, PAGE(S) 163-172, XP002170829 *

Cited By (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004102420A1 (fr) * 2003-05-19 2004-11-25 Sap Aktiengesellschaft Importation et exportation de donnees pour dispositifs informatiques
US8275742B2 (en) 2003-05-19 2012-09-25 Sap Aktiengesellschaft Data importation and exportation for computing devices
CN100361121C (zh) * 2003-07-11 2008-01-09 北京直真节点技术开发有限公司 一种通用对象建模方法及通用对象管理系统
KR101081678B1 (ko) 2003-07-31 2011-11-09 후지쯔 가부시끼가이샤 Ｘｍｌ 드리븐 아키텍쳐에서의 정보 처리 방법 및 기억 매체
US8533207B2 (en) 2003-07-31 2013-09-10 Fujitsu Limited Information processing method, apparatus and program in XML driven architecture
US7799273B2 (en) 2004-05-06 2010-09-21 Smp Logic Systems Llc Manufacturing execution system for validation, quality and risk assessment and monitoring of pharmaceutical manufacturing processes
US7359768B2 (en) 2004-10-29 2008-04-15 International Business Machines Corporation Route input system
EP1849104A4 (fr) * 2004-11-22 2009-11-11 Ibm File d'attente d'exportation pour un systeme logiciel d'entreprise
EP1923760A3 (fr) * 2006-10-20 2013-01-16 Rockwell Automation Technologies, Inc. Interface MES standard pour fabrication en série
EP1923760A2 (fr) 2006-10-20 2008-05-21 Rockwell Automation Technologies, Inc. Interface MES standard pour fabrication en série
US8843881B2 (en) 2007-01-12 2014-09-23 Microsoft Corporation Transporting and processing foreign data
CN102034140A (zh) * 2009-09-30 2011-04-27 西门子公司 改善制造执行系统的性能
EP2315138A1 (fr) * 2009-09-30 2011-04-27 Siemens Aktiengesellschaft Amélioration de la performance d'un système d'exécution de fabrication
US8452810B2 (en) 2009-09-30 2013-05-28 Siemens Aktiengesellschaft Method and system for improving performance of a manufacturing execution system
EP2874035A1 (fr) * 2013-10-29 2015-05-20 Kabushiki Kaisha Yaskawa Denki Système de production d'équipement industriel avec serveur de production
US9880546B2 (en) 2013-10-29 2018-01-30 Kabushiki Kaisha Yaskawa Denki Industrial equipment production system and method for configuring a motor controller using public and secret information
CN104808639A (zh) * 2015-04-29 2015-07-29 中国石油大学(华东) 一种制药产品制造执行系统及方法
CN109522268A (zh) * 2018-12-03 2019-03-26 中国南方电网有限责任公司 一种基于校验和导入相分离的电网svg导入分析方法
US11380926B2 (en) * 2019-08-14 2022-07-05 The Curators Of The University Of Missouri Fuel cell having corrugated membrane electrode assembly
CN117806600A (zh) * 2024-02-28 2024-04-02 江苏信而泰智能装备有限公司 一种mes的产线测试平台的构建方法、系统及设备
CN117806600B (zh) * 2024-02-28 2024-07-12 江苏信而泰智能装备有限公司 一种mes的产线测试平台的构建方法、系统及设备

Also Published As

Publication number Publication date
KR20040014671A (ko) 2004-02-14

Similar Documents

Publication Publication Date Title
KR101665152B1 (ko) 컴퓨팅 장치, 비즈니스 데이터의 획득 방법 및 컴퓨터 판독 가능 저장 매체
Florijn et al. Tool support for object-oriented patterns
US7673282B2 (en) Enterprise information unification
US6016394A (en) Method and system for database application software creation requiring minimal programming
US9122664B2 (en) Method for automatically creating transforms
US20130013993A1 (en) Spreadsheet-based templates for supporting the systems engineering process
US20050203718A1 (en) Knowledge management system with integrated product document management for computer-aided design modeling
Milicev Automatic model transformations using extended UML object diagrams in modeling environments
US20060101051A1 (en) Electronic data capture and verification
CA2255017A1 (fr) Methode et mecanisme relatifs a un modele de donnees xml oriente taches
WO2003009071A1 (fr) Systeme et procede d'exportation ou d'importation de donnees d'objet dans un systeme d'execution de fabrication (mes)
Oren et al. A flexible integration framework for semantic web 2.0 applications
Rossi et al. Model-based web application development
Calic et al. Tools for MDA software development: Evaluation criteria and set of desirable features
WO2005055561A2 (fr) Systeme et procede de gestion de la configuration de composants de systemes de support d'operations
CN100416565C (zh) 用于异质环境之间信息交换的自适应程序调用方法
Boldyreff et al. Architectural requirements for an open source component and artefact repository system within GENESIS
US20050114642A1 (en) System and method for managing OSS component configuration
Govedarica et al. Generating XML based specifications of information systems
Whitehead Jr et al. Automatic generation of hypertext system repositories: a model driven approach
CA2255054A1 (fr) Methode et mecanisme relatifs a un modele de donnees oriente taches
Karnok et al. Data type definition and handling for supporting interoperability across organizational borders
Sarafudinov Getting Started with Xomega
Song et al. The design and implementation of code generation based on J2EE in the development of JBPM workflow system
Lu et al. Enforcing data consistency in data integration systems by XQuery trigger service

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): CN JP KR SG

AL Designated countries for regional patents

Kind code of ref document: A1

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

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
WWE Wipo information: entry into national phase

Ref document number: 2003514350

Country of ref document: JP

Ref document number: 1020047000929

Country of ref document: KR

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP