CN101208649A - Recording and tracing non-trending production data and events in an industrial process control environment - Google Patents
Recording and tracing non-trending production data and events in an industrial process control environment Download PDFInfo
- Publication number
- CN101208649A CN101208649A CNA200680020822XA CN200680020822A CN101208649A CN 101208649 A CN101208649 A CN 101208649A CN A200680020822X A CNA200680020822X A CN A200680020822XA CN 200680020822 A CN200680020822 A CN 200680020822A CN 101208649 A CN101208649 A CN 101208649A
- Authority
- CN
- China
- Prior art keywords
- production
- event
- message
- data
- project
- 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.)
- Granted
Links
- 238000004519 manufacturing process Methods 0.000 title claims abstract description 818
- 238000000034 method Methods 0.000 claims abstract description 130
- 230000008569 process Effects 0.000 claims abstract description 88
- 230000001360 synchronised effect Effects 0.000 claims abstract description 11
- 230000004044 response Effects 0.000 claims description 109
- 230000011218 segmentation Effects 0.000 claims description 107
- 239000000463 material Substances 0.000 claims description 84
- 238000003860 storage Methods 0.000 claims description 44
- 238000010200 validation analysis Methods 0.000 claims description 43
- 238000012545 processing Methods 0.000 claims description 22
- 230000033228 biological regulation Effects 0.000 claims description 16
- 230000005540 biological transmission Effects 0.000 claims description 15
- 238000013502 data validation Methods 0.000 claims description 15
- 238000004458 analytical method Methods 0.000 claims description 14
- 230000015572 biosynthetic process Effects 0.000 claims description 10
- 238000007726 management method Methods 0.000 description 35
- 238000004886 process control Methods 0.000 description 22
- 230000006870 function Effects 0.000 description 12
- 238000012546 transfer Methods 0.000 description 11
- 238000004891 communication Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 6
- 230000012010 growth Effects 0.000 description 5
- 230000010354 integration Effects 0.000 description 5
- 238000012800 visualization Methods 0.000 description 5
- 102100026205 1-phosphatidylinositol 4,5-bisphosphate phosphodiesterase gamma-1 Human genes 0.000 description 4
- 101000691599 Homo sapiens 1-phosphatidylinositol 4,5-bisphosphate phosphodiesterase gamma-1 Proteins 0.000 description 4
- 230000009471 action Effects 0.000 description 4
- 230000002708 enhancing effect Effects 0.000 description 4
- 230000007246 mechanism Effects 0.000 description 4
- 241001269238 Data Species 0.000 description 3
- 230000000712 assembly Effects 0.000 description 3
- 238000000429 assembly Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 238000005259 measurement Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 239000002994 raw material Substances 0.000 description 3
- 235000020140 chocolate milk drink Nutrition 0.000 description 2
- 239000002131 composite material Substances 0.000 description 2
- 238000012790 confirmation Methods 0.000 description 2
- 238000009795 derivation Methods 0.000 description 2
- 238000003745 diagnosis Methods 0.000 description 2
- 230000008676 import Effects 0.000 description 2
- 238000009434 installation Methods 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 2
- 101100314150 Caenorhabditis elegans tank-1 gene Proteins 0.000 description 1
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000003139 buffering effect Effects 0.000 description 1
- 230000008602 contraction Effects 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000032798 delamination Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000018109 developmental process Effects 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 230000005611 electricity Effects 0.000 description 1
- 230000007717 exclusion Effects 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 230000006698 induction Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 230000033001 locomotion Effects 0.000 description 1
- 230000007787 long-term memory Effects 0.000 description 1
- 239000011159 matrix material Substances 0.000 description 1
- 230000015654 memory Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
-
- 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
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/542—Event management; Broadcasting; Multicasting; Notifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/04—Forecasting or optimisation specially adapted for administrative or management purposes, e.g. linear programming or "cutting stock problem"
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
- G06Q10/087—Inventory or stock management, e.g. order filling, procurement or balancing against orders
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/04—Manufacturing
-
- 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
-
- 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/30—Computing systems specially adapted for manufacturing
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Economics (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Strategic Management (AREA)
- Human Resources & Organizations (AREA)
- Tourism & Hospitality (AREA)
- Entrepreneurship & Innovation (AREA)
- Quality & Reliability (AREA)
- Software Systems (AREA)
- Marketing (AREA)
- General Business, Economics & Management (AREA)
- General Engineering & Computer Science (AREA)
- Development Economics (AREA)
- Operations Research (AREA)
- Game Theory and Decision Science (AREA)
- Manufacturing & Machinery (AREA)
- Health & Medical Sciences (AREA)
- Educational Administration (AREA)
- General Health & Medical Sciences (AREA)
- Automation & Control Theory (AREA)
- Primary Health Care (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Multimedia (AREA)
- General Factory Administration (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
A production information reporting/recording system is disclosed herein including a number of features to ensure efficient, flexible and reliable recording of production data in a manufacturing system. Such features include validating the content of event messages to ensure compliance of event report information with a standard. The system also supports caching IDs associated with particular aspects of an event message (e.g., a production request, a process segment) as well as a unique ID corresponding to the ID assigned by the production event database to reduce the need to access the database when assigning unique database IDs to received events. The production event messaging system also supports both asynchronous and synchronous transactional messaging between the sources of events and the production database service. Finally, the system supports including extensions to a base production message schema through the inclusion of metadata that designates a particular production server to parse and apply/store the extension information.
Description
The cross reference of related application
The U.S. Provisional Patent Application sequence number 60/675 that the application requires people such as Weinrich to submit on April 25th, 2005,037 right of priority, title is " RECORDING ANDTRACING NON-TRENDING PRODUCTION DATA AND EVENTSIN AN INDUSTRIAL PROCESS CONTROL ENVIRONMENT ", its full content is quoted as a reference especially at this, comprises whole lists of references wherein.
The application relates to the U.S. Patent Application Serial Number (unallocated) that people such as Weinrich submitted on April 25th, 2006, agency's reel number 235951, title is " VALIDATINGINFORMATION WITHIN PRODUCTION EVENT MESSAGESFOR RECORDING NON-TRENDING PRODUCTION DATA ANDEVENTS ", its full content is quoted as a reference especially at this, comprises whole lists of references wherein.
The application relates to the U.S. Patent Application Serial Number (unallocated) that people such as Weinrich submitted on April 25th, 2006, agency's reel number 251917, title is " CACHINGIDENTIFICATIONS AND ASSOCIATED PRODUCTIONDATABASE GUIDS FOR EXPEDITED ACQUISITION OFLINKING INFORMATION CONTAINED WITHIN MULTIPLEDISTINCT PRODUCTION DATABASE TABLES ", its full content is quoted as a reference especially at this, comprises whole lists of references wherein.
The application relates to the U.S. Patent Application Serial Number (unallocated) that people such as Weinrich submitted on April 25th, 2006, agency's reel number 251918, title is " SUPPORTINGBOTH ASYNCHRONOUS AND SYNCHRONOUS DATATRANSFERS BETWEEN PRODUCTION EVENT INFORMATIONSOURCES AND A PRODUCTION INFORMATION DATABASE ", its full content is quoted as a reference especially at this, comprises whole lists of references wherein.
The application relates to the U.S. Patent Application Serial Number (unallocated) that people such as Weinrich submitted on April 25th, 2006, agency's reel number 251919, title is " SUPPORTINGEXTENSIONS TO PRODUCTION EVENT MESSAGE SCHEMESVIA PRODUCTION DATABASE SERVER VERSIONING ", its full content is quoted as a reference especially at this, comprises whole lists of references wherein.
Technical field
In general, the present invention relates to the field of industrial process computerize control system.Or rather, the present invention relates to collect/handle non-trend process data and guarantee that such information stores is in the long term memory according to industry standard specifications (as ISA-95).
Background technology
Industry relies on supermatic data acquistion and control system growingly, so that guarantee efficient, safe, the running reliably of industrial process, reduces its integral production cost simultaneously.Diversified form is taked in data acquisition, comprise trend with non-trend.In general, the trend data type that is included in the certain characteristics of many sensor measurement industrial processs and regularly when data aggregation and control system are repaid its measurement result, gathers.For example, the trend data that is produced by sensor/recorder comprises: the counting stock of the package of waiting on the mass/volume stream of temperature, pressure, pH, material, the sail line.If one or more trend datas of certain process variable are storage not, by observation post lose give this variable before and after the numerical value value then between these somes interpolation can estimate them usually.
Otherwise non-trend data is not observed the pattern from any to another point, so can't be from nearest adjacent data point estimation.The production data of some tasks of execution is the example of non-trend data in the scope of general production request of identification (as making a collection of chocolate milk) and production request every.Consider and be unable to estimate the value that belongs to the non-trend data of being lost, developed special database, be called the production event server, to receive and to keep detailed production event history.
The production incident is the discrete time incident that takes place during the production run, is usually directed to process measurement, material, equipment, manpower or other resources of production that the later stage may pay close attention to.Following incident is given a definition in ISA 95 standards: material consumption present situation, manufacture of materials present situation, material move present situation, material consumption product present situation, production data, equipment actuality and manpower present situation.
Summary of the invention
The present invention includes the production event information register system of using in the manufacturing environment.Described system comprises that the latter comprises the production data storehouse, comprises one group of form to producing many enhancings of event information system, is used to store the production event information that is produced by manufacturing/production system.
Described production event information provides by producing event object, and described production event object response triggers the production incident, produces and produces event message, and described production event message comprises the data set corresponding with the production incident.Some services in production data storehouse are handled the described production event message that described production event object is produced.These services of producing comprise the production server, are used to handle the information content in the described production event message, and the data set with described production incident correspondence is stored in the described production data storehouse then.
Production information report/register system disclosed herein comprises many features, and they have guaranteed efficient, flexible, the reliable record of production data.An enhancing of producing the event information system is comprised by at least one value application validation criteria to described data set, analyze the content of producing event message.In specific embodiment, data value and data linguistic context have all been used described standard.
Another enhancing comprises some ID that high-speed cache is associated with the some concrete feature of event message (as the request of producing, process stage), and is distributed unique ID of ID correspondence by described production data storehouse.The some concrete unique ID of high-speed cache are beneficial to the visit that reduces described production data storehouse when the link of creating the table entries of previous establishment.Described production event message system also supports the asynchronous and synchronized transaction message between event source and the service of described production data storehouse.Moreover, described system also supports the basis is produced the expansion of massage pattern.In specific embodiment, provide support by in production message, comprising the metadata extend information to some expansions, described production message is specified the concrete server of producing, and comprises the production message of described extend information with analysis and application/storage.
Description of drawings
Though subsidiary claims have been illustrated feature of the present invention particularly, but, together with describing in detail below the referenced drawings, can understand best invention with and purpose and advantage, wherein:
Fig. 1 is a synoptic diagram, has described demonstration management process control exploitation and running environment, has added the multilayer set/hierarchical relationship between the assembly;
Fig. 2 has described multistage object set layout, is used to gather application program and engine on the demonstration system inner platform of the embodiment of the invention;
Fig. 3 has described high level architecture, is used for defining, the production event object of configuration and executive system report and record production incident;
Fig. 4 is an exemplary user interface, is used to produce event object configuration flip-flops setting option, incident setting option and event data;
Fig. 5 is an exemplary user interface, is used to dispose the expansion of producing on the event object and produces attribute;
Fig. 6 is an exemplary user interface, is used to dispose the affirmation standard of producing the event message attribute;
Fig. 7 is the table of induction of rule sets, is used for requirement and comprises at least one information, and it comprises the another kind of form of crossing over the affirmation standard of producing the multiple attribute application of event message;
Fig. 8 is high-level diagram, has described to displaying property a kind of transmission of messages of form, and wherein the service of producing does not provide response;
Fig. 9 is high-level diagram, has described to displaying property a kind of transmission of messages of form, and wherein the service of producing provides response;
Figure 10 is a process flow diagram, has concluded cache operations, relates to being used for finishing the GUID that production data Ku Biaoge writes down;
Figure 11 is a process flow diagram, has concluded one group of step, is used for according to the metadata that provides in the production event message of receiving, handles described production event message by selecting one of many possible production servers;
Figure 12 has concluded the demonstration table group of forming the production data storehouse.
Embodiment
Herein disclosed is a kind of production event information report/register system, it is at the needs of storing manufacturing and production information in enterprise or its some departments reliably.The trackability of the production incident that system disclosed herein support is associated with manufacture process.Described system comprises one group of service of producing event object and being associated, and for data between production facility and the business system and affairs, catches the production event data and is stored in the one group of form that defines in the production data storehouse according to the ISA-95 standard.To making markup language V2 standard, its full content is quoted as a reference especially at this, comprises whole lists of references wherein based on world's batch processing forum (WBF) commercial affairs for displaying production event information report that this paper introduces and record facility.
In displaying property example, some production event module produce the message by the production Event triggered.These message comprise the data of relevant this incident.Described event data is configured to integrated design environment (IDE) in the object rank.Use any of following two kinds of available transfer modes when sending event message: (1) asynchronous (not having response), (2) are (having response) synchronously.Produce event message by analysis, checking, write the production data storehouse then.The scalable message mode arrangements of back-level server side's event message analyzer versioned is also supported to verify and the function of other enhancings.
Therefore described production event information report/register system is supported diversified important production problem is furnished an answer.Such as
What has production carried out?
Is there there what composition material in the final products of each unit?
Does what other product use identical composition material in the past?
Certain specific product of when producing/certain batch?
Used what equipment during treatment product?
Is who operator responsible for this equipment during handling certain specific product?
During handling certain specific product, consumed what basic resources (water, energy etc.)?
The more complicated problems that furnishes an answer by the content of visiting the production data storehouse comprises:
Used how many input material comparison production and how much exported material (mass balance)?
What is certain some critical product property value of particular exam point place in the process of producing this product?
Is what specific purpose tool in the equipment of handling this product?
Which operation of this product:
-by same equipment?
-by same operator's operation?
-use same input material?
Demonstration is produced the following explanation of event information report/register system based on embodiments of the invention, should not be considered as the present invention about the not clearly restriction of the alternate embodiment of introduction of this paper.For example, the present invention is added within management process control and the manufacturing information environment, and wherein each data source is represented by application object.The U.S. Patent Application Serial Number 10/179 that the example of such system was submitted on June 24th, 2002 people such as Resnick, be described in detail in 668, title is " SUPERVISORY PROCESS CONTROL ANDMANUFACTURING INFORMATION SYSTEM APPLICATIONHAVING A LAYERED ARCHITECTURE ", its full content is incorporated herein by reference, and comprises wherein identifying/content and the instruction of whole lists of references of containing.But, consider those skilled in the art will recognize that of disclosed example embodiment, the present invention is applicable to that potentially various alternative management processes control environment, but comprise some identification datas source, they provide real-time processing data, driving one group of motion graphics unit, expression at least a portion is subjected to observation/in check industrial process.
With reference to figure 1, synoptic diagram has been described the set/hierarchical relationship of some assemblies in the demonstration management process Control Network, comprises multiple levels of management process control and manufacturing information system.Before the exemplary network environment is described in more detail, notice usually in this embodiment, for example represent data source with the form of application object 105 and 107.Application object is carried out various functions, comprises receiving status information and carry out any of variety of functions on the application program aspect.A kind of such function is to receive to produce behind the event notification of other application objects that are derived from system's deploy to produce event message.These event messages are forwarded to the production service of being presided over by other networked personal computers that are connected to PROJECT NETWORKS 119.
Continuation is carried out multi-layer management process control and manufacturing information application program jointly collaboratively with reference to figure 1, the first application server personal computer (PC) 100 and the second application server PC 200, comprises first 104 and second portion 106.Application program part 104 comprises equipment integration application object PLC1Network and PLC1.PLC1Network equipment integration object helps configuration data access server (as OPC Data Access Server 116).As the Data Position in PLC1 equipment integration object accesses OPC Data Access Server 116 buffer zones of OPC client computer operation.Data Access Server 116 and equipment integration object are to input of collaboration data ground and buffering from the external procedure Control Component such as PLC or other place equipment.
In an embodiment of the present invention, go up the human interface software of carrying out by the PC that is connected to network 119 (as PC 120) and submit the request that obtains factory floor information to, these information-driven graphic presentation, the equipment state of expression factory floor.The wide variety of applications program object of carrying out on personal computer 100 105 (as PLC1Network, PLC1, App.Object etc.) is the data buffer of visit data access server 116 all.The example of application object comprises for example discrete device, analog machine, place benchmark, event/trigger, production incident etc.In displaying property example, the request and the response data of factory floor information are transmitted between PC100 and 102 (at factory floor) and PC 120 through network 119.
According to embodiments of the invention, applications engine is gathered some application objects (through the logic groups object, this paper is called " zone ").Other platform object of low one-level by management process control and manufacturing information application program is gathered described engine successively.Gather application program part 104 and 106 successively by general bootstrapping assembly 108 and 110.This paper introduces above-mentioned all components below with reference to Fig. 2.
In implementing demonstration system of the present invention, comprise part 104 and 106 multi-level application program communication be linked to the process of decentralised control.Exactly, the first application server personal computer 100 is connected to first programmable logic controller (PLC) 112 through factory floor network 115.Note, connect through the connection presentation logic of describing of factory floor network 115 from PC 100 to PLC 112.Such logic connects both corresponding directly physical communication and connects, and corresponding again indirect physical communication connects.For example, in specific embodiment, PLC 112 comprises the node on the ethernet lan, and personal computer 100 is attached thereto.In other embodiments, PLC 112 directly is connected to the physical communication port on the PC 100.
In the displaying embodiment that Fig. 1 sets forth, PC 100 service data access servers 116.The procedural information that Data Access Server 116 acquisition/extractions are provided by PLC 112, and provide this procedural information to the application object that comprises part 104 and 106 (as PLC1Network, PLC1).Described Data Access Server 116 is opc servers for example.But, those skilled in the art will be not difficult to recognize far-ranging customization and the standardized data formats/protocols by 116 potential execution of Data Access Server.Moreover, the exemplary application object by with being connected of Data Access Server 116, the operation of expression PLC network and PLC oneself.But, these application objects comprise the in fact unlimited object class carried out of scope, and they carry out desired management control and data acquisition/integrated functionality in management process control and manufacturing information environment of applications.
According to embodiments of the invention, certain application object example comprises the function of the trigger of issue production incident correspondence, and other respond these triggers and produce and issue polytype production event message.Such production event instance comprises: material consumption, manufacture of materials, material move, material consumption product, production data, equipment and manpower.
For example, described production event trigger message is delivered to the AppEngine2 of operation on the PC 102 through message exchange protocol.Described production event trigger message is delivered to the suitable for producing event message application object 107 on the PC 102.According to example embodiment, described production event message application object 107 is published to the production event message of correspondence again to be produced service 140[and adds Fig. 1 to], it moves with production data storehouse 142 explicitly being connected on the historical node 144 of PROJECT NETWORKS 119.Producing the operation of service 140 and general production event handling will introduce hereinafter further.
Management process control and management information application program are for example expanded by configuration personal computer 120, it is moving database (as the SQL) server 122 of maintenance management process control and management information application deployment database 124, be used for application object and other relevant informations, comprise from the masterplate of its exemplary application program object.Configuration database 124 also comprises global name table 125, and the position that it is convenient to be independent of object name is bundled into the handle that derive the position, has made things convenient for the message route between the object in the system that Fig. 1 describes.Configuration PC 120 and the database server 122 that is associated are supported: the centralized object of the management and monitoring of multi-user environment, correction history management, centralized license management, the deployment that comprises new object (comprise and produce the event information object) and their associated software and installation is disposed, maintenance and the I/O object masterplate and the illustration of global name table 125.
Comprise that the establishment of application object (comprise and produce event message object (hereinafter further discussing)) and the application deployment of deployment carry out through Integrated Development Environment (IDE) 126.IDE126 is utility routine (may comprise a plurality of assemblies), comprise the process control of application object and engine and manufacturing information application program from its definition, create and be deployed to various platform/engines, comprise for example apps server PC 100 and 102.The developer of management process control and manufacturing information application program has realized comprising application programming function widely by IDE 126: import new object and masterplate type, dispose new masterplate, define new application object and application object is deployed to host application program engine (as the AppEngine1 on the apps server PC 100) from existing masterplate.
The demonstration management Control Network environment that Fig. 1 describes also comprises the one group of active station 130,132 and 134 that is connected to network 119, they provide the view to process or its part, by installing on PC 100 and 120 and being monitored/control as management process control and manufacturing information application program that a component layers object moves.The representative view that raw material PC 130 provides can monitor by the raw material zone of management industrial process.Producing PC 132 has presented by the representative view of management industrial process production division.Finished product PC 134 provides the representative view in the production facility zone that is associated with finished product.Active station 130,132 and 134 each all comprise the guiding main frame that is used for each concrete operations platform.Active station 130,132 and 134 each all comprise the view engine, their process graphics information are to reproduce the pattern description of observed industrial process or its part.
Should be pointed out that system that the above Fig. 1 that introduces of this paper describes only is the example of level framework such as multilayer, management process control and manufacturing information system that being used to realizes demonstrating produces the event message system.The invention is not restricted to disclosed concrete application/system, in fact, needn't shown in displaying property example, the form with the multistage application program realize.Should be pointed out that further that Fig. 1 presents for the set between institute's installation component and/or comprise the logical view of mutual relationship, these assemblies comprise software and physical computing hardware.Described production event message system is suitable for any network topology in fact.For example, in the applicable system of the present invention, configuration utility and management process control visualization applications all operate on the single computer system that is linked to controlled process.
Turn to Fig. 2, class figure has described the hierarchical set layout of delamination software, and software comprises computer executable instructions, is associated with the computing machine (as PC 100 or 120) of control of operating part management process at least and manufacturing information application program.Every computing machine is all moving operating system 200 in the system lowermost level, such as the WINDOWS of Microsoft.Operating system 200 is being arranged bootstrapping object 202.The start-up course of carrying out with operating system 200 is associated, and bootstrapping object 202 is loaded on the computing machine and is activated.As the host of platform class object 204, before the operation of starting platform class object 204, must activate bootstrapping object 202.202 startings of bootstrapping object and termination platform class object 204.The service that bootstrapping object 202 also provides platform class object 204 to utilize is with one or more engine object 206 of starting and stopping being arranged by platform class object 204.
In example embodiment, application object 210 comprises the application programming interfaces of being visited by engine object 206 and scheduler 208.Engine object 206 access application object interfaces are for the initialization application object, start application object and close application object.Scheduler 208 use the application object interfaces be for start the corresponding application program object by scheduled for executing.
At by the agency of behind the primary clustering of the control of demonstration management process and manufacturing information network environment, will pay close attention to the high level architecture view of the production event system that Fig. 3 schematically describes.For example, in controling environment type, the management departure process that Fig. 1 and Fig. 2 describe just disposed, disposed and carried out such system.
Turn to Fig. 3, IDE 126 facilities create and disposed one group of production event application program object 300.For example, create some application objects 300 from the production event object masterplate tool box of supporting multiple production event type, comprise at ISA 95 undefined production event types: material consumption present situation, manufacture of materials present situation, material move present situation, material consumption product present situation, production data, equipment actuality and manpower present situation.It should be noted that, following both is included in the configuration of production event application program object 300: the submodule version of the some derivation of (1) configuration, they will be stored in as the submodule version of father's masterplate in the masterplate tool box that is associated with IDE 126 thereafter, and the example of event object is produced in (2) configuration.Therefore, concrete application-specific production event configuration can be stored and usefulness more repeatedly, produces the event object example to create concrete application-specific.In example embodiment, in masterplate tool box graphic user interface with the formal description of expansion/contraction hierarchical tree the derivation/inheritance between some production event object masterplates.
Above-mentioned production event object type can be divided into " material " and " state " event object.Material event object facility recording materials production incident, and comprise following demonstration object type (corresponding to the some masterplates that provide in the IDE 126 masterplate tool boxes): material consumption product present situation, material consumption present situation, material move present situation and manufacture of materials present situation.State event object facility the record define the production segmentation for information about.For example following type (corresponding to the some masterplates that provide in the IDE 126 masterplate tool boxes) is provided the state event object type: equipment actuality, personnel's present situation and production data.
Produce the type of event object
The object that material consumption product present situation (MaterialConsumableActual) is produced the definition of event object masterplate be identified in used consumables during the production segmentation that defines.Producing the information of collecting in the event object and providing in correspondence comprises: the material of the consumable material that is consumed, quantity and measuring unit.Consumables may can not identify in the tabulation of material usually, and they also may be the article of not counting separately in definition production segmentation.But, these article might cause the direct cost considered in the cost of production segmentation.Depend on the type of industry, consumables can comprise some public utilities, such as electricity and water, general chemistry goods or catalyzer.Material consumption product present situation production incident masterplate has used position or material ID attribute to discern material at least.
The object that material consumption present situation (MaterialConsumedActual) is produced the definition of event object masterplate be identified in material consumption during the production segmentation that defines.Institute's consumable material can be designated the output of raw material, buying material or another process segmentation usually in the tabulation of material.The material consumption present situation is produced event object and is used one of following attribute identification institute consumable material at least: the position, in batches, material ID, list of sequence numbers and son in batches.Consumed also recommended amount attribute of how many resources in order to define.
Material moves present situation (MaterialMovedActual) and produces that material moves in the single production incident of object record of object masterplate definition, and it is the combination of material consumption present situation incident and manufacture of materials present situation incident.Material moves present situation to the moving of material that image tracing is discerned, for example, from the receiving position to the production line on the material of storage buttress move.In this case, material moved the present situation logout material consumption of receiving position and the manufacture of materials of storage buttress.For the destination of marking materials, this object must use one of following attribute at least: the son of the batch of destination locations, destination, destination material ID, destination list of sequence numbers and destination in batches.For the source of marking materials, material moves the present situation object and uses one of following attribute at least: source position, source batch, source material ID, source material list of sequence numbers and source material are in batches.Moved also recommended amount attribute of how many materials in order to define.
Manufacture of materials present situation (MaterialProducedActual) produce the definition of object masterplate object record as the establishment of the final products of production segmentation output.The manufacture of materials present situation is produced object and is used one of following attribute sign material of producing at least: the position, in batches, material ID, list of sequence numbers and sub-batch.Produced also recommended amount attribute of how many materials in order to define.
At by the agency of after the exemplary materials supported by IDE 126 produces event object masterplate group, will pay close attention to demonstration " state " production event object masterplate group.
Equipment actuality (EquipmenActual) produce the definition of object masterplate object record the current device that is associated with productive unit use information.For example, equipment actuality is produced object and may comprised with production segmentation associated device property and tabulate.
Personnel's present situation (PersonnelActual) produce the definition of object masterplate object record in the production segmentation with the related information of personnel.For example, personnel's present situation is produced the workstation that object may the regulation employee identification number and is associated with the production segmentation.
Production data (ProductionData) produce the definition of object masterplate object record in the production run certain point the discrete value of corresponding production data.For example, production data production object has start time and the stand-by time that helps write down the production segmentation that defines.As an alternative, production data production object record the some numerical value when step finishes in the production run.
In alternate embodiment, support generic (Generic) to produce object.It is fundamental objects that described generic is produced the object masterplate, and it only provides all to produce the needed production attribute of object.The user derives the production object type that the production attribute of submodule version and appointment expansion (introducing hereinafter) defines any customization by producing the object masterplate from generic, then the submodule version that derives is saved in the masterplate tool box of IDE 126.Generic is produced object and is used for for example collecting all unconnected information of any production incident with above introduction, and with in the table of data storage in production data storehouse 142.
More than Shi Bie production event object type comprises one group of built-in production attribute.Every type production event object all has its oneself the production property set that is associated.The example of such production attribute comprises: position, material ID, note, lists of persons, process segmentation ID, produce request ID, quantity, segmentation response ID, measuring unit, in batches, son batch, list of sequence numbers etc.Some produces attribute is public to whole production event object types (masterplate).Other attributes only use in certain object.Some attribute is necessary, and other attributes are not.For example, every kind of production event object type all comprises the request of producing ID, process segmentation ID and segmentation response ID.Produce attributes for these three kinds and be used to identify production run, and be provided at link (hereinafter will being introduced) between some associated production incidents of other particular table stored in production data storehouse 142 with reference to the exemplary database pattern that Figure 12 describes.
Attribute is produced in configuration
Dispose common production object option
Mainly turn to Fig. 4, IDE 126 also supports configuration flip-flops setting, incident setting and event data.Produce in object configuration interface in (configuration all produce event objects used) demonstration, one group of configurable field of user is divided into that trigger is provided with 400, incident is provided with 402 and event data 404.Trigger is provided with 400 fields and the user can regulation be produced when event object is disposed in runtime environment and carried out how to activate or trigger.Be provided with in 400 zones at trigger, trigger has two kinds of available options.First option has been specified the method for trigger.If use the input source choice box not selected, so just use MyPEMEvent Trigger trigger event.Select to use the input source frame to allow to use the trigger of input source as incident.Click is browsed icon 406 and is just moved attribute browser session frame, so that select certain attribute as input source.The selection check box 408 that automatically resets just makes the object properties flip-flop states automatically reset.For need not be from the response of event object and wish the incident that triggers this is useful.
How it carried out communication (having/do not have response) with the service of producing 140 when how the production event object used validation criteria and triggering when incident was provided with the configuration of 402 fields specify.
Be provided with in 402 fields in incident, enable validation criteria frame 410 when selecting operation and just make the whole attributes of choosing in the event message of when configuration and triggering production event object, being issued all enable validation criteria.Only the attribute of choosing on validation criteria the configuration dialog box (see figure 6) is just enabled validation criteria.Introduce the validation criteria configuration hereinafter and confirm to produce event message.When mode list frame 412 allows the selection issue to produce event message, producing event object and producing the pattern of serving communication between 140.Select " not having response " to specify the asynchronous communication pattern.Select the synchronous communication pattern of " response is arranged " specify transfer event message, and service node to be produced such as object is handled the response of any affirmation mistake.Overtime frame 414 regulations are produced object with after the response modes message transfer is arranged, and will wait for the time quantum from the production service response before the message of registration miscommunication and the previous transmission of repeating transmission.
Date and time when " event name " that provides during event data 404 field configuration record data and trigger event.Event name frame 416 can be specified and the title of producing the production incident that object is associated the user.Date time zone 418 makes the user select to use the input source option so that " time on date " attribute to be set for the incident that triggers, and perhaps selects to produce automatically to produce date and time automatically.The user clicks to browse in the icon 420 dependency browser session frames and selects attribute.
The production attribute of configuration expansion
Production event handling system disclosed herein also support to above introduce, for producing the expansion of the defined pre-configured production property set of event object type.Such expansion this paper is called " the production attribute of expansion ", increased the additional information that in some tables in production data storehouse 142, to be stored, perhaps as an alternative, the production attribute of expansion is used for explaining other information that the production event message that passes to the service of producing 140 provides.In example embodiment, inherit in the production attribute uncle masterplate of expansion.
Mainly turn to Fig. 5, described among the figure to producing event object and specified the exemplary user interface of extended attribute.Can increase the expansion production attribute of any amount to producing event object.Have for example increase extended attribute dialog box of the interface type of Fig. 5 description by calling, defined some expansions production attributes for producing event object.After this, input attributes name in Property Name frame 500.The user selects data type from the column data type that data type drop-down list box 502 is presented then.The initial value of input source or initial value frame 504 or storage extended attribute or storage input source (if the user has specified use input source check box 506).Browse icon 507 visit to attribute browser session frame is provided, make the user can search extension produce the concrete input source of property value.Whether daily record attribute check box 508 can indicate when the trigger event object user, extended attribute is stored in the production data storehouse 142.Produce attribute (+) or remove existing expansion production attribute (-) in order to increase another kind of expansion, also comprised some control knobs.
The affirmation standard of event information is produced in configuration
In example embodiment, set up to produce the massage pattern that event message adopted and expanded, to support producing the affirmation standard that the information specifies that provides in the property value will be carried out to producing the production property value that comprises in the message that event object produces and expansion.The information specifies one group acknowledge standard setting that provides in the event message that IDE 126 supports the production event object is created.Producing service 140 even initiation client computer also utilizes this validation criteria that the information that comprises in the affirmation production event message is set.The service of producing 140 utilize such affirmation standard in will producing the suitable table that event information is stored in production data storehouse 142 before, guarantee that event information is qualified.
In example embodiment, selected world batch processing forum pattern (ISA-95) as the form of producing 140 production event messages that receive and handle of service.Some alternate embodiments of the present invention may be based on other standards, and even do not have standard at all.But, the standardized information form that provides according to the ISA-95 pattern helps to stipulate some generalization rules, is used to confirm to produce the data that comprise in the event message.Moreover, in an embodiment of the present invention, carried out " context " for the structural intergrity that comprises the production event data integrality of data set (as guarantee to provide in the message) has been provided.In example embodiment, receive that the inner structure of information is confirmed by the XML syntactic analyser that is associated with the service of producing 140.The XML syntactic analyser comprises the definition to the form and the property value of the concrete message that comprises in the message.
In example embodiment, message authentication is based upon to be produced among the event object.When operation, need only with data load S95 and produced event object, just can call the method for producing event object and confirm itself.Can call this affirmation client-side, server end or client-server end both sides.Only can will can not attempt in the affirmation that server end is carried out at client-side.For example, only the suitable table in data and the production data storehouse 142/server end that the row combination compares can carried out the affirmation of " existing " in database table/row.
Data validation
At run duration, all may carry out every each property value of producing event message and to confirm operation, the data that comprised with checking satisfy the user when configuration via the specified affirmation standard of IDE 126.
Turn to Fig. 6, introduced the data validation standard with reference to the demonstration validation criteria configuration user interfaces that is used to produce event object.In example embodiment, all may define validation criteria to producing attribute and expanding production attribute both sides.The validation criteria configuration user interfaces has therefore listed whole production attributes with title and attribute is produced in expansion.The title of demonstration validation criteria configuration user interfaces has identified the one group of configurable validation criteria option that is associated with three types data validation standard.In the embodiment that shows, user definition following three types affirmation standard: pattern match, unique still exist and numerical value optional.Have only when the production event attribute is String data type can the defining mode coupling and numerical value optional.
Below introduced each input field of demonstration validation criteria configuration user interfaces.Confirm whether attribute field 600 appointments will carry out affirmation to the production event attribute that is associated.The validation criteria interface is according to the automatic filling attribute-name of the current definition production event attribute group field 602 to the definition of production event object.
The information specifies pattern that 604 supports of pattern match field provide attribute (it must be the string argument value).By specified based on grand position character string masterplate, described pattern has indicated each position in the character string can have which significant character.Described pattern by a series of alphanumeric, some non-alphanumeric characters and some asterisk wildcard marks (as #, ﹠amp; And @) forms.Being explained as follows of asterisk wildcard mark: #---position must comprise numeral , ﹠amp;---position must comprise letter, @---and the position must comprise alphanumeric.In an embodiment of the present invention, pattern match is supported some non-alphanumeric characters, and such as dash line (-) and underscore (_) character, the two all effectively and literalize.On the other hand, do not allow space and comma.
Unique field 606 is affirmation standard testings of mutual exclusion with there being field 608, and one group of numerical value of current storage compares (at server end) in certain row of certain table in property value that they need will provide in receiving message and the production data storehouse 142 (sign in literary name section 610 and row field 612).Confirm operation for " existence ", one group of numerical value in property value and the named list/row is compared, exist to guarantee this occurrence.For example, property value as external data source (table/row) in project exist carried out in the vital example " existence " test.For example, if need the operator to import order number, and for the Objective of Report, it must be effectively, exists confirming mechanism just to call inquiry to external data source, is included in the table/row of appointment to verify these data.Any project in the named list/row of " unique " affirmation property value that operation demonstration provided and external data source is all inequality.In example embodiment, externally under the situation of data source (being table or the data cell outside the production data storehouse), utilize " Linked Servers " technology of microsoft sql server external data source can be configured to the internal table in production data storehouse 142 seemingly.In case so configuration, just they were tables in the production data storehouse 142 seemingly when confirming mechanism was visited this external data source.Therefore confirm that operation can be applied to the EXCEL electrical form of Microsoft, text etc.
Configuration user interfaces also comprises numerical value Optional Field 614.Confirming mechanism requires the attribute (value) of every kind of regulation all to comprise some data during acquiescence.Property value can not the promptly empty or not appointment for NULL.But, if chosen the numerical value Optional Field, this attribute does not have designated value will can not cause the confirming mechanism failure so.
Context is confirmed
Except user's configurable " data " confirmed operation, example embodiment of the present invention supported also one group " context " producing event message confirmed operation that they are the production event object internal configurations of particular type.Different with data validation (it is thought of as each numerical value of the specified reality of production event attribute), the content of a plurality of production event attributes in the single message of assessment confirmed in context.
As instantiation, a kind of context affirm warranty of form, in the production message of specifying actual numerical value, message comprises one group of at least a attribute of producing attribute.As instantiation, the production event message (moving present situation as material consumption product present situation, material consumption present situation, manufacture of materials present situation and material) that is produced by the production object of relevant material must comprise at least one value of optional attribute value group, to discern the material by institute's reporting event influence uniquely.The array that Fig. 7 describes is that each bar of the event message of four relevant materials has all identified optional attribute value group, in order to confirm that by context operation must be from wherein specifying at least one value.If there is not context to confirm, the data that are associated with manufacture of materials present situation incident may be written to production data storehouse 142, and it does not comprise and is identified in the needed data of material of producing during institute's reporting event.Above example only is exemplary, can expect, multiple context confirms that action type will join in the multiple alternate embodiment of production event report/register system that this paper introduces.
Return Fig. 3, after having disposed production incident (application program) group of objects 300, the user has disposed corresponding production event object example 310 to using the applications engine of moving on the node 315 (as the AppEngine2 on the ApplicationServer2PC102).After this producing event object example 310 moves in running environment.In running environment, produce the trigger event that 310 responses of event object example are received from local and non-local application object 320 and application program (as InTouch application program 325), create also issue by the event messages of the service of producing 140 consumption.Pointed in the description of configuration flip-flops as the above example configuration interface that presents with reference to figure 4, produce event object and be for example some objects from one's body certain attributes or I/O source.
At run duration, the trigger that at every turn scans the production event object example 310 on application programs engine 3s 15 is all estimated.If trigger is high, the production event object of Chu Faing is just created and is produced event message so.Create when producing event message, the production event object of triggering is collected the value of some production event attributes and the affirmation standard configuration that is associated, and these production event attributes are marked as " record " during the configuration of producing event object.During the collection of record attribute, produce object and retrieve input value from appointed positions.But, if this attribute is not defined as input, the value of current storage in this attribute will be used.After this, produce event object 310 and produce event message, in the some suitable table that leaves production data storehouse 142 in to the service of producing 140 issues.Under the situation of original (newly) message, produce new message id to identify this message.In example embodiment, produce service 140 and in the environment of COM+ server 355, move, wherein produce server 140 and call the version of producing server according to the revision identification information that receive production event message is embedded in.Realize producing the production server version analysis of event message pattern particular version and confirm the production event information that comprises in the production event message of receiving.Information after the affirmation is by the service of producing tabulation in production data storehouse 142.
According to example embodiment, support two kinds of production incident transfer modes.There not to be response (asynchronous) message transfer mode, produce event object to message queue service 345 issue event messages, do not wait for any type of affirmation or errored response.Any mistake that occurs in message content is handled all is documented in the table in production data storehouse 142.Otherwise,, produce event object so and will wait for and receive event message and the message of receiving is delivered to the response message that the webserver 340 of the service of production 140 sends if specified response (synchronously) message transfer mode.Produce service 140 responses and indicated the various mistakes that during server-side processes message, occur via the webserver 340.Any affirmation mistake (comprising the relevant details of confirming error reason) that takes place when for example, this response is with the qualified criterion that indicates the record attribute application configuration in producing event message.Hereinafter will introduce further synchronously and Asynchronous Transfer Mode with reference to figure 8 and Fig. 9.
The message transfer mode of two kinds of supports
Asynchronous (not having response) and synchronous (response is arranged) two kinds of message transfer modes between production event information report/register system support production event object 310 disclosed herein and the production service 140.With " response is arranged " pattern (see figure 9), produce event object receive the service of production 140 response, be not only success/status of fail of receiving message by the webserver 340 to sender of the message's circular, and successfully analyze with ining addition, affirmation and the interior success/status of fail that comprises information of storing message.With " not having response " pattern (see figure 8), send message by unidirectional communication path (as passing through message queue), produce service 140 and do not send any response back to the publisher who produces event message.The service of producing 140 determine whether record/report to from produce production event message content that event object 310 receives handle during the various mistakes of appearance.Pattern is used to exist the user interaction situation of (as passing through monitor) " response ", and " do not have response " pattern is used for only wishing to send message and when not worrying it when client computer.The S95 high speed information buffer memory that all can occur the service aspect in both cases.
Turn to Fig. 8, during for example with " not having response " mode operation, on the MessageSupport of client computer 802 assembly 800, call the SendMessage method.MessageSupport assembly 800 uses message queue (MSMQ) service 345 of Microsoft to send specified message to server 804.MSMQ service 345 is configured to assurance/processing and passes on.In case MSMQ service 345 message with client computer 802 convey to server queue 806, production message dispatcher service 808 (a kind of microsoft windows service) are just seen the message in the formation 806, and call production message handler services 810 and retrieve message from formation 806.As hereinafter will further explaining with reference to Figure 11, handler services 810 is analyzed at least a portion retrieved message, and calls the example of the suitable production server 812 of possible a plurality of support versions of producing server, with the process for producing event message.
Searching message and call and produce server 812 carry out (indicated as the issued transaction border that Fig. 8 draws) in single issued transaction context from formation can not lost to guarantee this message.If whether in some way mistake produces server 812 decisions this mistake of report/record.Should be noted that client computer 802 also comprises formation 814, being connected under the interrupted situation between client computer 802 and server 804 is used for storing message.
Turn to Fig. 9,, on MessageSupport assembly 800, call the SendMessage method with specify message with " response is arranged " pattern.MessageSupport assembly 800 uses the calling of the network service 900 of operation on the server 804, and sends message to server 804.Handler services 810 is called in network service 900 on the server 804 again.Handler services 810 is analyzed a part of production event message of receiving (as the extension of message of hereinafter introducing) and is called the event information that comprises in the suitable production server 812 version processing messages.Detected any mistake (as confirming mistake) if produce service 812, so just reported back these mistakes to the production event object of this message of issue.
The production event message of previous failure is retransmitted in the support of described " response is arranged " pattern with same message id.Support two kinds of retransmission cases.Under first kind of situation, do not stoped the production object to be received to producing the response of event message, so retransmit same message because in time-out period, receive response or other mistakes.When doing, event object starting and state can detect such mistake when producing.Under these circumstances, retransmit the last message that sends with same message id.Under second kind of situation, the mistake in receiving response, reported of response and resend message.Under these circumstances, the attribute that resubmits is set to very and triggers again and produce event object.In both cases, producing event object all will be according to current signal reconstruct message, and these information may change since previous (failure/mistake) transmission.
Return Fig. 3, one of the service of producing 140 two kinds of message transfer modes by above introduction receive the production event message.After receiving, produce 140 (comprising specific production server version) of service just according to the content of the given pattern analysis message of use XML appointment.After this, the service of producing 140 is confirmed every kind of attribute by production server 812 versions that call.Before explained as mentioned, and in displaying property embodiment, each was produced event argument approve really and can comprise that data validation (as pattern match, existence/unique and numerical value is optional) and/or context confirm (as comprising one group of attribute data in the one at least).In example embodiment, the affirmation standard definition of the configuration of carrying out on institute's transitive attribute value is included in produces in the event message.In example embodiment, providing validation criteria to define is the expansion of basis to the production massage pattern of the realization of the production server version in possible a plurality of production server versions 360 of the service of producing 140 maintenances.Hereinafter will further introduce producing the expansion of affirmation standard definition and other expansions of event message pattern.
If the mistake of not detecting is produced service 140 so and will be tabulated in production data storehouse 142 by the affirmation information that the production event message of receiving is provided.But, if in " not having response " mode message, detected the affirmation mistake, produce in the service 140 production event message error lists that just wrong project are written on the production data storehouse 142.Otherwise,, so just this mistake is written to " ErrorMessage " of original production event object and " ErrorCode " project and presents to the user if in " response is arranged " mode message, detected mistake.
Confirm object class
By the code module of client and server end and confirming of one group of particular extension (hereinafter further introducing) in conjunction with implementing to ISA-95 standard x ML pattern.In order to implement to confirm in order to report/write down the expansion of production event implementation ISA-95 standard XML basic model, in general be classified as two kinds of scopes: the expansion of the affirmation rule of producing the event message data is violated in definition, and can will confirm that the result joins the expansion of producing event message.
Pointed out before as above that regulation affirmation rule in producing event message will and be expanded the affirmation standard of producing the user configured and system regulation that carry out on the attribute at the production attribute in producing event message with definition.Confirm that rule is the combination of validation criteria expansion and rule definition.The validation criteria expansion is " shape ", and it has defined the affirmation rule that how to define particular type.For example, " quality " validation criteria expanded definition confirm some characteristics that rule must appointment for abundant describing mass.Validation criteria expansion is based on self of XML, and supports commercial affairs to the form of making markup language (B2MML) standard (only being form), this facility usually comprise the growth data of validation criteria and numerical value special use.
Confirm rule be by or client-side or server end on the affirmation code be applied to the validation criteria expanded data.Trigger when producing event object and establishment and process for producing event message, client-side uses the affirmation rule expansion in the message that the existence and the quality of data are carried out early stage affirmation.Server end use to confirm rule carry out all other confirm (as with respect in the production data storehouse 142 specifically the content of table/row confirm), as in the application's book than the introduction of morning.
About relating to some affirmation results' production event message mode expansion, confirm that the result who carries out is stored in the Validation Error expansion of producing event message.Between the production event message pattern of " response is arranged " (synchronously) is used for producing object and the service of producing 140, transmit when producing event message, produce object use produce event message admit one's mistake really the misdata of storage in the mistake expansion when operation in the object to user report affirmation mistake.Otherwise, when using " nothing response " (asynchronous) pattern, produce service 140 and use the wrong growth data of affirmation will confirm that the result is stored in the production data storehouse 142.
In example embodiment, be used to implement the production event message affirmation of above introduction with lower class.
ValidationError: be used to keep Validation Error helper for information about.In the TraceResponseMessage object, may return their array.
ValidationExtension: the inner base class, the commercial affairs that are applied to several generations have the growth data of Validation and other numerical value special uses to making the markup language class to allow them.QualityType and ValueType are exactly the generation class that derives from this class.
ValidationExtensionData: inner classes helps the serialization of ValidationExtension foundation class to arbitrary XML component, perhaps from the deserializing of arbitrary XML component.
ValidationHelper: inner classes, some confirmation methods use it to confirm each field.
ValidationRule: the helper class is used to keep the relevant information of confirming rule.
Also defined two kinds of interfaces:
IValidationError: make the ValidationError class via the addressable interface of COM.
IValidationRule: make the ValidationRule class via the addressable interface of COM.
Also defined a kind of enumerating, ValidationErrorTypeEnum, it comprises the tabulation of the affirmation fault type of whole supports.
Produce the event procedure identifier cache
Continuation, is produced service 140 and is being kept high-speed cache 350 in example embodiment with reference to figure 3, has before stored the interior pairing related GUID of some projects of some tables in production information and production data storehouse 142.In displaying embodiment of the present invention, the ID of some specifying information of storing in the 142 some tables of production data storehouse, and the capable GUID that distributes of some tables that comprises these information is stored in the high-speed cache, when setting up link between some of the different production informations of storage in (as some tables, OK) so that the disconnected position in production data storehouse 142, make that visit may very large some tables and the demand of retrieving GUID reaches minimum.Moreover, when receiving new information, produce service 140 before the information of accessing database, at first in internally cached, search link (as the GUID) information that needs.
According to concrete displaying embodiment, handle some resources (material, equipment and personnel) by production run.These production incidents that are used for process and resource (as material, equipment and personnel) are being carried the identifier that is associated with production run (as producing request, process segmentation definition, segmentation response etc.).Production run is related in many cases.Order is formulated in the request of production, to produce institute's marking materials (as 100 gallons chocolate milk is provided) of limited amount.The process segmentation is corresponding to the specific tasks of carrying out in order to finish the request of production.The segmentation response is corresponding to the concrete example of performed task, and corresponding ID is distributed by client computer and production data storehouse both sides, produces each indivedual example of request, process segmentation and segmentation response with identification.
Producing service 140 identifier information that will produce event procedure is stored in the high-speed cache 360.In displaying property embodiment, the identifier of high-speed cache (and the GUID that is distributed by production data storehouse 142) is used for each the production request of receiving event message and process segmentation.Each event message of receiving all has " ID " field, and being collected by the data user who carries out in the application server selectively provides.On the database aspect, each of these identifiers (produce request ID and process segmentation ID) is all represented in the production data storehouse 142 the unique project in the suitable table, and database 142 data of having used Globally Unique Identifier (GUID) to identify each list item specially and comprise.
With the certain database pattern in production data storehouse 142 (Figure 12 that sees below and introduce), produce request ID and process segmentation ID and be used for relevant/link, and after this locate with receive event message in the data that are associated of segmentation response identifier.Because related algorithm may need the database search of elapsed time/resource and search, so implemented technology below with reference to Figure 10 summary, the sign of storage and accessing database project in high-speed cache 360, when the information that the process segmentation is linked to the relevant item (OK) in the request of production and the process segmentation table is being obtained and stored in the service of producing 140, reduce the demand that visit comprises the table of the request of production and process segmentation ID.
When the demonstration cache management method of summarizing is below received the information (GUID) of the production request that is associated and process segmentation table in retrieval with the item chain in the segmentation Response Table, reduced the number of times of access list.During step 1000, produce service 140 and receive the production event message that comprises the production event data at first.This message may comprise the request of producing ID, process segmentation ID and segmentation response ID (finishing by producing event object).Do not need all, if but they are provided, high-speed cache will use them to quicken relevant and position the record.
During step 1008,, just think that this numerical value does not exist and will be represented as NULL if the production request id field in the event message is empty (numerical value promptly is not provided).Control is delivered to step 1010, has wherein distributed new production required list GUID for this NULL produces request ID.Although this action is not many than the context that the production event message provides, it has guaranteed that really appropriate data during the reporting period are relevant.If do not do like this, when the incident that it is relevant with other is associated, the user can't retrieve the data of this message.Control is delivered to step 1022 then.
If the production request id field in the event message is not empty (the ID value promptly is provided), control is delivered to step 1012 so, and wherein the project of the production request ID correspondence that is provided is provided in high-speed cache 350 in the service of producing.If searching successfully of high-speed cache, handle so and shift to the step of hereinafter introducing 1022.If in the failure of searching of high-speed cache, control is delivered to step 1016 so, and wherein production request ID is applied to the production required list in the production data storehouse 142.
If the production required list searches successfully during step 1016, control is delivered to step 1020 so, wherein from database 142, returned and produced the request pairing Globally Unique Identifier of ID project (GUID) in the production required list, the GUID that produces request ID and production request ID is stored in the high-speed cache 350, so that quote during step 1012 in the future.If the production required list searches failure (promptly produce request ID not in the production required list) during step 1016, so just in the production required list, create to produce pairing new projects of request ID/OK, and produce the new GUID of the pairing production required list of request ID new projects' distribution to this.Control is delivered to step 1020 then, and wherein new GUID and production request ID are stored in the high-speed cache 350, so that quote during step 1012 in the future.
During step 1022, the production request GUID of the production event message of being received and ID are stored in (even this GUID value is produced request ID for NULL) in the storer, so that quote during the final stage (promptly providing the request of production and process segmentation GUID to the pairing segmentation Response Table of the production event message project of receiving) that event message is handled.
The step of processing procedure segmentation ID and the GUID step with the process for producing request ID of above introduction and GUID in essence is identical.During step 1028,, just think that this numerical value does not exist and will be represented as NULL if the process segmentation id field in the event message is empty (numerical value promptly is not provided).Control is delivered to step 1030, has wherein distributed new process segmentation table GUID for NULL process segmentation ID.Although this action is not many than the context that the production event message provides, it has guaranteed that really appropriate data during the reporting period are relevant.If do not do like this, when the incident that it is relevant with other is associated, the user can't retrieve the data of this message.Control is delivered to step 1042 then.
If the process segmentation id field in the event message is not empty (the ID value promptly is provided), control is delivered to step 1032 so, and wherein the pairing project of production request ID that is provided is provided in high-speed cache 350 in the service of producing.If searching successfully of high-speed cache, handle so and shift to the step of hereinafter introducing 1042.If in the failure of searching of high-speed cache, control is delivered to step 1036 so, and wherein process segmentation ID is applied to the process segmentation table in the production data storehouse 142.
If the process segmentation table searches successfully during step 1036, control is delivered to step 1040 so, wherein from database 142, returned the pairing Globally Unique Identifier of process segmentation ID project (GUID) in the process segmentation table, the GUID of process segmentation ID and process segmentation ID is stored in the high-speed cache 350, so that quote during step 1032 in the future.If the process segmentation table searches failure (being that process segmentation ID is not in the process segmentation table) during step 1036, pairing new projects of constructive process segmentation ID/OK in the process segmentation table so, and distribute new GUID to the pairing process segmentation table of this process segmentation ID new projects.Control is delivered to step 1040 then, and wherein new GUID and process segmentation ID are stored in the high-speed cache 350, so that quote during step 1032 in the future.
During step 1042, the process segmentation GUID of the production event message of being received and ID are stored in (even this GUID value is NULL process segmentation ID) in the storer, so that quote during the final stage (promptly providing the request of production and process segmentation GUID to the pairing segmentation Response Table of the production event message project of receiving) that event message is handled.Control is delivered to step 1050 then.
Before entering on relevant step 1050, it should be noted that, the table that the database that comprises in displaying property embodiment is organized/linked by one group of mode of summarizing in Figure 12 is formed, segmentation response ID is used in combination retrieval event data from production data storehouse 142 with production request ID/GUID that is associated and process segmentation ID/GUID.So in this displaying property embodiment, these three kinds of unit cooperate in database schema.The cooperation of these three kinds of Database Unit is mainly by the project in the segmentation Response Table in production data storehouse 142, and it finally comprises some the quoting to be associated request of producing and process segmentation table project, though some may be indirect.For the request of will producing and some projects of process segmentation table are connected to segmentation Response Table project, in the new projects in the segmentation response ID assignment segments Response Table, must know to produce and ask ID and process segmentation ID.When inserting, event data determines that for some projects of corresponding production request and process segmentation table identifier may spend the lot of data storehouse and handle resource.Therefore, filling in the above described manner about the high-speed cache 350 of request of producing and process segmentation ID/GUID information and quoted, with the production request ID that obtains appointment in current production event message potentially and the GUID of process segmentation ID.When arriving step 1050, just known production request ID and the pairing GUID of process segmentation ID that produces event message that receive.Remaining step request of will producing and process segmentation GUID are connected to segmentation response ID.
During step 1048, if the response of the segmentation in the production event message of receiving ID is empty (numerical value promptly is not provided), control is delivered to step 1050 so, and thinks that segmentation response ID value does not exist and will be represented as NULL, to reach the purpose of production process Response Table GUID.Control is delivered to step 1060 then.
During step 1048, if the response of the segmentation in event message ID is not empty (the ID value promptly is provided), control is delivered to step 1052 so, wherein searches segmentation response ID value (note: segmentation response ID is not by high-speed cache) in the segmentation Response Table in production data storehouse 142.If segmentation response ID searches successfully, control is delivered to step 1060 so.
But, if segmentation response ID is not in the segmentation Response Table during step 1052, control is delivered to step 1054 so, and wherein the segmentation response ID for appointment creates new table entry in the segmentation Response Table in production data storehouse 142.ID has distributed newline to the segmentation response, has the new GUID that distributes to it on it.New GUID and segmentation response ID are returned and are used for further processing, and control is delivered to step 1060.
During step 1060, the production data storehouse GUID that produces request ID and the pairing previous retrieval of process segmentation ID has carried out related with the segmentation response ID that produces event message (it makes their whole cooperations).In order in production data storehouse 142, to comprise the GUID that produces request ID and process segmentation ID, upgraded project in the pairing segmentation Response Table of segmentation response ID/OK.Therefore, the user can respond the GUID of ID and the content that this segmentation responds the pairing segmentation Response Table of GUID of ID by segmentation, and some respective items purpose contents in request and the process segmentation table are produced in visit.
To producing the expansion of event message pattern
Another aspect of production event report/register system disclosed herein is to produce event object to content and processing that service 140 event messages that provide are provided.Exactly, define/supported expansion, comprising: contextual relation is got up and production data is linked to the global identifier of raw requests, function, lists of persons and other such data such as moving production message criteria (as ISA-95).Produce the concrete version of server (as routine analyzer) in the metadata expansion by regulation basic message form, make some expansions and easier the modification of support expanded set based on the XML event message.Exactly, the metadata expansion of producing in the event message has identified the version that message format (XML) defines, and produces service 140 and will use it to extract data content from event message.In displaying property embodiment, produce service 140 concrete version pairing " ServerAssembly " indicated releases by sign.
Hereinafter introduce producing the demonstration expansion of massage pattern.The basic version of producing the event message pattern obtains from world's batch processing forum, and below by the agency of support several expansions of additional function, comprise the versioned (server assembling) of producing service software, be used to analyze the content of the production event message pattern of expansion, it may change in time.
1. produce the expansion of event message data source
Production event message itself has feature (GUID) and can be named.Production data storehouse 142 patterns are all used the relation of the corresponding ISA-95 event data of storage in message GUID recording messages incident and the production data storehouse 142 from start to finish.It below is the example of expanding specified parameter via the message data source.
This GUID of MessageID-must be by deriving the class setting.Server will verify that described MessageID is unique in rational time phase.The predetermined purpose of MessageID is to guarantee that same issued transaction is not write down twice by the service of producing 140.If the uncertain issued transaction of client computer successfully takes place, it can retransmit this message with same MessageID.Successfully handled the message that comprises same MessageID recently if produce service 140, it will return and make mistakes.In order to make server avoid registration " repetition MessageID " mistake, client computer can be provided with to be tried to retransmit this message after the characteristic again.Notice is set produces service 142 these message and do not repeat just to handle it if try attribute again, just ignore this and try message again if successfully handled this message.
MessageName-specifies optional any name of this message.
2. produce the expansion of Service events Message Processing
Produce the expansion of Service events Message Processing and make that to finish some the Message Processing management role that is associated with reception and processing messages by the service of producing 140 easier, may comprise resend message.
Retry-introduced in above MessageID part, and specified client is being used previous MessageID resend message.
The optional array of MessageData-regulation string data sends in this expansion of producing event message.
The optional information part in relevant this message data source of MessageSrc-regulation.For example, MessageSrc can be " a manufacture of materials present situation ".
MessageDate-is used for the Optional Field on the date of regulation message.
3. the expansion of production server version sign
In displaying property embodiment, the basis is produced the event message pattern the metadata extended description produce the foundation structure of event message self.The information that such metadata comprises is from discerning specific one a plurality of production server versions, and it will be used to handle the content of producing event message of receiving.These expansions in the particular group, combined with the built-in function of judging and call one production message processing program 810 suitable in one group of production server that the service of production 140 is supported, convenient for the replenishing/revise of the production set of properties supported in the new production server, kept back compatible simultaneously with old production server version.Hereinafter will be presented in support with reference to Figure 11 may create and the process for producing event message in the system of a plurality of production server versions.
The ServerAssembly-regulation should be handled the .NET name of parts of the production service of this message.
BaseVersion-stipulates simple version for this ProductionMessage class.Production message and the service of producing can be verified the message that they come understanding.
DerivedVersion-stipulates simple version for deriving class.Production message and the service of producing can be verified the message that they come understanding.
DerivedName-stipulates simple name for deriving class.
4. confirm expansion
Above the affirmation rule of extensive discussions is indicated in the expansion of producing event message.The following expansion of regulation is so that the message delivery confirmation configuration information of support being identified.For being produced every kind of attribute that event attribute all provides following sign by every kind in the pass-along message.
Whether the ValidationEnabled-regulation should use this affirmation rule to this attribute.Acquiescence is false.
The right matrix section of DBTableName-regulation table/row will check whether it exists in the production data storehouse with the value of understanding attribute.
The right row part of DBColumnName-regulation table/row will check whether it exists in the production data storehouse with the value of understanding attribute.
Whether DBExists-regulation should be " existence " or " not existing " of attribute value and look-up table/row are right.
The Pattern-given application is in the pattern of attribute value.
Whether CanBeNull-regulation attribute value can be NULL or null character string.This is false during acquiescence.
ClientData-is by any number of client transfers.If confirming this numerical value of failure will return in the ValidationError object.
ValueKey-represents the inside definition value of the information that is identified.If confirming this numerical value of failure will return in the ValidationError object.
5. management of manufacture process electronical record and special processing expansion
In expansion, also support unspecified note and sequence number in the ISA-95 message criteria to incident.
Comment-stipulates note, as the growth data transmission of deriving class.
The array of SerialNumbers-regulation sequence number is as the growth data transmission of deriving class.
TxTime-stipulates the time that this issued transaction takes place.
6. response message
This is the response message to the S95 document that sends to the webserver.Because the key element of listing relates to origination message herein, so outside the S95 model domain.
MessageID-sees above.
MessageAssembly-sees above.
BaseVersion--sees above.
DerivedVersion--sees above.
DerivedName-sees above.
The ErrorCode-regulation is described the digital value of this response.In typical case, when success this will be zero, and will be non-zero when wrong.
The ResponseMsg-regulation is described the character string of this response.In typical case, when success this will be empty, and will comprise explanation of error when wrong.
The RetryOrigMessage-regulation should be tried original message again because do not know whether Traceability Service can successfully handle it.
ValidationError
ErrorMsg-is illustrated as the error message what confirms failure.
This character of ErrorPosition-will comprise in the character string zero to be the position of basic point, and it fails to match at this mode position.
Really the type of admitting one's mistake takes place in the ErrorType-regulation by mistake.
It has comprised the character string expression that makes the value of confirming failure ErrorValue-.
ValidRule-causes the current backup of confirming the original ValidationRule object of failure.More information sees above.
Turn to Figure 11, the demonstration group of wherein having summarized some steps, it has described establishment and processing to the production event message that comprises the metadata expansion, metadata expansion regulation is produced the service 140 concrete production server versions that will use, the information that provides in the production event message is analyzed and tabulated.At first, during step 1100, triggered the production event object, produced event message to create.During step 1100, this production event object has been created the production event message in response.Described production event message comprises one group of production event attribute and one group of extension of message.Point out that as above this group extension of message comprises the metadata of confirming that the concrete version of server is produced in expansion and identification, this version be used to analyze with acknowledge message in the attribute information that comprises.After this, during step 1120, one of messaging protocol (promptly having/do not have response) by two kinds of supports will be produced event message and be sent to the service of production 140.
After this, during step 1130, the metadata that handler service 810 is analyzed in the production event message of being received with the appropriate production server version of determining to call, is handled the production event information that comprises in the message of receiving.Next step, during step 1140, handler service is called certain production server version of producing service 140 a plurality of production server versions of being supported.After this, during step 1150, the production server version of being called is received the production event attribute that comprises in the message according to the production event message mode treatment based on XML that is associated.During step 1150, produce server and assert justice really according to providing via the information expansion that comprises in the receiving message itself, confirm the message data of being received.Producing server is not the production event information tabulation (if confirming successfully) that will comprise in the message, exactly mistake is charged to daily record (if confirming to show mistake).According to the type (having/do not have response) of message, the service of producing 140 is not that mistake is stored in the error list in production data storehouse 142 (not having response), returns the failure message that has error code exactly.In example embodiment, called production server example (as producing server 812) by handler service 810 and only continued single message transaction processing.
Therefore, by the agency of be used for the method for process for producing event message, these message may embody the information of dissimilar/form according to some concrete massage patterns.According to embodiments of the invention, the version metadata comprises in producing event message, to identify concrete message version.Produce service 140 and utilize the message version information Recognition and call the multiple concrete version of supporting the production server version, handle this production event message.Producing the server example only continues during production event message issued transaction.But, in alternate embodiment, some production server versions last till produces beyond the message transaction process range.
Turn to Figure 12, the demonstration production data storehouse pattern in production data storehouse 142 has wherein been described, database 142 canned datas with produce the production event message that event trigger produced and be associated by producing the event object response, and by the service of producing 140 tabulate (after confirming).
ConsumableActual table 1200 storage one group record, support have increased the view of the basic S95 consumables present situation object of some global identifiers and UTC (Universal Time Coordinated) row.Each project all comprises external key, and it quotes the row that this project is associated with it in the SegmentResponse table 1202 (hereinafter introducing).
ConsumableActualProperty table 1204 storage one group record, support have increased the view of the basic S95 consumables present situation character object of some global identifiers and UTC row.Each project all comprises external key, and it quotes the row that this project is associated with it in the ConsumableActual table 1200.
EquipmentActual table 1206 storage one group record, support have increased the view of the basic S95 equipment actuality object of some global identifiers and UTC row.Each project all comprises external key, and it quotes the row that project is associated with it in the SegmentResponse table 1202.
EquipmentActualProperty table 1208 storage one group record, support have increased the view of the basic S95 equipment actuality character object of some global identifiers and UTC row.Each character provisional capital is linked through external key and single equipment present situation row.
MaterialConsumedActual table 1210 storage one group record, support have increased the view of the basic S95 material consumption present situation object of some global identifiers and UTC row.Each project all comprises external key, and it quotes the row that project is associated with it in the SegmentResponse table 1202.
MaterialConsumedActualProperty table 1212 storage one group record, support have increased the view of the basic S95 material consumption present situation object of some global identifiers and UTC row.Each character provisional capital is linked to the single row in the MaterialConsumedActual table 1210.
MaterialProducedActual table 1214 storage one group record, support have increased the view of the basic S95 manufacture of materials present situation object of some global identifiers and UTC row.Each project all comprises external key, and it quotes the row that project is associated with it in the SegmentResponse table 1202.
MaterialProducedActualProperty table 1216 storage one group record, support have increased the view of the basic S95 manufacture of materials present situation character object of some global identifiers and UTC row.Each character provisional capital is linked to the single row in the MateriallProducedActual table 1214.
SerialNumberData table 1218 storage one group record, record support is to the view of all sequences in production data storehouse No. 142.Sequence number is some material characters of classifying in their table.Each sequence number project all have to or MaterialConsumedActual table 1210 or MaterialProducedActual table 1214 in certain the row link, it is comprising the part of sequence number as incident.
PersonnelActual table 1220 storage one group record, support have increased the view of the basic S95 personnel present situation object of some global identifiers and UTC row.Each project all comprises external key, and it quotes the row that project is associated with it in the SegmentResponse table 1202.
PersonnelActualProperty table 1222 storage one group record, support have increased the view of the basic S95 personnel present situation character object of some global identifiers and UTC row.Each character provisional capital is linked to the single row in the PersonnelActual table 1220.
ProductionData table 1224 storage one group record, support have increased the view of the basic S95 production data object of some global identifiers and UTC row.Each project all comprises external key, and it quotes the row that project is associated with it in the SegmentResponse table 1202 (hereinafter introducing).
The event name List View is supported in EventEnumeration table 1226 storage one group record, has this incident with some identifiers for referencial use.
ProductionEventMessage table 1227 storage one group record, the view of some unique incidents of storage in the supporting database 142.Each project all comprises external key, and it quotes the row that project is associated with it in the EventEnumeration table 1226.
ProcessSegment table 1228 storage one group record, support have increased the view of the basic S95 process segmentation object of some global identifiers and UTC row.
ProductionEventMessageError table 1230 storage one group record supports to have the some message view of confirming mistake that need reexamination.
ProductionPerformance table 1232 storage one group record, support have increased the view of the basic S95 production performance object of some global identifiers and UTC row.Each project all comprises external key, and it quotes the row in the ProductionSchedule table 1236 (following introduction).
ProductionResponse table 1234 storage one group record, support have increased the view of the basic S95 production segmentation object of some global identifiers and UTC row.Each project all comprises external key, and it quotes the row in the ProductionPerformance table 1232.
SegmentResponse table 1202 storage one group record, support have increased the view of the basic S95 segmentation response object of some global identifiers and UTC row.Each project all comprises one group of external key, and they quote the row in each of ProcessSegment table 1228, ProductionResponse table 1234 and ProductionRequest table 1238 (hereinafter introduce).
ProductionSchedule table 1236 storage one group record, support have increased the view of the basic S95 production scheduling object of some global identifiers and UTC row.
ProductionRequest table 1238 storage one group record, support have increased the view of the basic S95 production request object of some global identifiers and UTC row.Each project all comprises external key, and it quotes the row in the Production Schedule table 1236.
Production data storehouse 142 patterns that should be pointed out that above introduction are exemplary.The potential use that the data that provide via the production event message are provided is in extensive range, can predict some alternate embodiments and will utilize the some groups of tables that substitute to store for information about in database 142.
Consider many possibility embodiment that can use the some principles of this disclosed production event report/register system, be to be understood that some embodiment that this paper introduces about accompanying drawing only mean displaying, and should be considered as limitation of the scope of the invention.For example, those skilled in the art will appreciate that, some key element that is stored in the shown some displaying embodiment of software on the computer-readable medium with form of computer-executable instructions can realize with hardware, vice versa, can carry out the modification of layout and details and not break away from essence of the present invention the some embodiment that show.So, expect that as the present invention of this paper introduction all such embodiment can fall within the scope of following claims and equivalent thereof.
Claims (according to the modification of the 19th of treaty)
1. production event information register system of in manufacturing environment, using, described system comprises:
The production data storehouse comprises being used to store one group of form producing event information;
Produce event object, be used for response and trigger production incident generation production event message, described production event message comprises the data set corresponding with the production incident; And
The service of production data storehouse, be used for the described production event message that described production event object is produced is handled, described production service comprises the production server, be used for before the described production data storehouse storage data set corresponding with described production incident, analyze the information content in the described production event message, wherein said analysis comprises uses validation criteria at least one value of described data set.
2. according to the production event information register system of claim 1, wherein, described validation criteria is corresponding to the store industrial standard of producing event information.
3. according to the production event information register system of claim 1, wherein, described validation criteria regulation comprises at least one non-NULL production property value of the one group of a plurality of production attribute that is associated with production event message type.
4. according to the production event information register system of claim 3, wherein, described production event message type belongs to material.
5. according to the production event information register system of claim 1, wherein, described validation criteria comprises context affirmation rule, and it uses a plurality of production attributes of crossing in the single production event message.
6. according to the production event information register system of claim 1, wherein, described validation criteria comprises the data validation rule, is applied in the described production event message to producing the value of attribute defined.
7. according to the production event message of claim 6, wherein, described data validation rule predetermining is formed the pattern of a string character of described production attribute.
8. according to the production event message of claim 6, wherein, be unique in the grid column of value in described production data storehouse of the described production attribute of described data validation rule predetermining.
9. according to the production event message of claim 6, wherein, the value of the described production attribute of described data validation rule predetermining is present in the grid column in the described production data storehouse.
10. according to the production event message of claim 6, wherein, the value of the described production attribute of described data validation rule predetermining is optional in described production event message.
11. the production event information register system according to claim 1 further comprises message interface, it supports to receive the production event message by asynchronous and synchronous two kinds of production event message transmission modes.
12. according to the production event information register system of claim 1, wherein, described validation criteria is included within the described production event message.
13. according to the production event information register system of claim 1, wherein, the result who uses described validation criteria is stored within the described production event message.
14. according to the production event information register system of claim 1, further comprise the production server of a plurality of versions, wherein produce event message by the metadata expansion of producing event message being stipulated the concrete version of the production server of described a plurality of versions.
15. production event information register system according to claim 1, further comprise high-speed cache, it is right to be used to store event data sign and unique form project label, and wherein said unique form project label is assigned to the project that comprises with in described event data identifies first form in described production data storehouse of the event data that is associated.
16. a method of handling the caused production incident of manufacturing environment, wherein the production data storehouse is stored in one group of form and is produced event information, said method comprising the steps of:
Receive to trigger and produce event notice;
Respond described receiving step by producing event object, produce the production event message that comprises the data set corresponding with the production incident; And
By the information content in the described production event message of production data storehouse service analysis, wherein said analysis comprises uses validation criteria at least one value of the described data set that comprises in the described production event message.
17. according to the method for claim 16, wherein, described generation step is implemented received described triggering production event notice from application object after by described production event object.
18., further be included in described analytical procedure is tabulated described data set afterwards in described production data storehouse step according to the method for claim 16.
19. the method according to claim 16 further may further comprise the steps:
Storage event data sign and unique form project label in producing server cache, described unique form project label are assigned to and comprise and project in described event data identifies first form in described production data storehouse of the event data that is associated; And
Retrieval and the corresponding described unique form project label of described event data sign from described production server cache project, and described unique form project label is stored in the project of second form, so that the described item chain in described second form is received described project in described first form by described unique form project label.
20. computer-readable medium that comprises computer executable instructions, it helps to handle the caused production incident of manufacturing environment, wherein the production data storehouse is stored in one group of form and is produced event information, and described computer executable instructions is convenient to carry out following steps:
Received by producing the production event message that event object produces by production data storehouse server, described production event message comprises the data set corresponding with the production incident; And
Analyze the information content in the described production event message, wherein said analysis comprises by the service of production data storehouse uses validation criteria at least one value of described data set, then the described data set of storage in described production data storehouse.
21. a production event information register system of using in manufacturing environment, described system comprises:
The production data storehouse comprises being used to store one group of form producing event information;
Produce event object, be used for response and trigger production incident generation production event message, described production event message comprises the data set corresponding with the production incident; And
The service of production data storehouse is used for the described production event message that described production event object is produced is handled, and described production service comprises the production server, is used to store the data set of described production incident correspondence, and wherein said production server comprises:
High-speed cache, it is right to be used to store event data sign and unique form project label, and wherein said unique form project label is assigned to and comprises and project in described event data identifies first form in described production data storehouse of the event data that is associated.
22. according to the production event information register system of claim 21, wherein, described form comprises the production solicited message.
23. according to the production event information register system of claim 21, wherein, described form comprises the process segment information.
24. production event information register system according to claim 21, wherein, described production data storehouse comprises first form and second form at least, and described cache stores event data sign and corresponding unique form project label, described unique form project label is corresponding to the project of described first and second forms in one of them, and described first and second forms comprise the event data that is associated with described event data sign.
25. according to the production event information register system of claim 24, wherein, described first form comprises the production solicited message, described second form comprises the process segment information.
26. production event information register system according to claim 25, wherein, described production server comprises computer executable instructions, be used for storing new projects at the 3rd form, comprise the segmentation response message, and comprise first unique form project label and second unique form project label, correspond respectively to the project in described first and second forms.
27. production event information register system according to claim 21, wherein, described high-speed cache comprises that first event data sign and the first unique form project label corresponding with the first form project are right, and described production server comprises computer executable instructions, be used in the new form project of described production server storage, described new form project comprises described first unique form project label, thereby described new form project is linked to the described first form project.
28. a method of handling the caused production incident of manufacturing environment, wherein the production data storehouse is stored in one group of form and is produced event information, said method comprising the steps of:
Receive to trigger and produce event notice;
Respond described receiving step, produce the production event message that comprises the data set corresponding with the production incident; And
Handle the information content in the described production event message, described processing is included in the form project store data inside group in the described production data storehouse with unique form project label, and described treatment step further may further comprise the steps:
At first in the first form project stored in described production data storehouse partial data group at least; And
Secondly producing event data sign and the unique form project label that server cache project stored is allocation of items in described first form.
29. the method according to claim 28 further may further comprise the steps:
Retrieval and the corresponding described unique form project label of described event data sign from described production server cache project, and described unique form project label is stored in the project of second form, thereby the described item chain in described second form is received described project in described first form by described unique form project label.
30. according to the method for claim 29, wherein, described first form comprises the production solicited message, described second form comprises the segmentation response message.
31. according to the method for claim 29, wherein, described first form comprises the process segment information, described second form comprises the segmentation response message.
32. according to the method for claim 31, wherein, described production data storehouse comprises the 3rd form, described the 3rd form comprises the production solicited message, and described method further may further comprise the steps:
From the described production server cache retrieval unique production request form project label corresponding with the production request mark that is provided, and will store into from described unique form project label of described the 3rd form in the project in described second form, thereby the described item chain in described second form be received described project in described the 3rd form by described unique production request form project label.
33. according to the method for claim 28, wherein, described generation step is implemented by producing event object.
34. computer-readable medium that comprises computer executable instructions, it helps to handle the caused production incident of manufacturing environment, wherein the production data storehouse is stored in one group of form and is produced event information, and described computer executable instructions is convenient to carry out following steps:
Receive and produce event message, described production event message comprises the data set corresponding with the production incident; And
Handle the information content in the described production event message, described processing is included in the form project store data inside group in the described production data storehouse with unique form project label, and described treatment step further may further comprise the steps:
At first in the first form project stored in described production data storehouse partial data group at least; And
Secondly producing event data sign and the unique form project label that server cache project stored is allocation of items in described first form.
35. according to the computer-readable medium of claim 34, further comprise computer executable instructions, be used to carry out following steps:
Retrieval and the corresponding described unique form project label of described event data sign from described production server cache project, and described unique form project label is stored in the project of second form, thereby the described item chain in described second form is received described project in described first form by described unique form project label.
36. according to the computer-readable medium of claim 35, wherein, described first form comprises the production solicited message, described second form comprises the segmentation response message.
37. according to the computer-readable medium of claim 35, wherein, described first form comprises the process segment information, described second form comprises the segmentation response message.
38. according to the computer-readable medium of claim 37, wherein, described production data storehouse comprises the 3rd form, described the 3rd form comprises the production solicited message, and further comprises computer executable instructions, is used to carry out following steps:
From the described production server cache retrieval unique production request form project label corresponding with the production request mark that is provided, and will store into from described unique form project label of described the 3rd form in the project in described second form, thereby the described item chain in described second form be received described project in described the 3rd form by described unique production request form project label.
39. according to the computer-readable medium of claim 34, wherein, described generation step is implemented by producing event object.
40. a production event information register system of using in manufacturing environment, described system comprises:
The production data storehouse comprises being used to store one group of form producing event information;
Produce event object, be used for response and trigger production incident generation production event message, described production event message comprises the data set corresponding with the production incident;
The service of production data storehouse, be used for the described production event message that described production event object is produced is handled, described production service comprises the production server, be used for before the described production data storehouse storage data set corresponding, handling the information content in the described production event message with described production incident; And
Multi-mode between described production event object and the service of described production data storehouse is produced the event message interface, and wherein said multi-mode is produced the event message interface and supported the asynchronous and synchronous two kinds of message transactions between described production event object and the service of described production data storehouse to handle.
41., wherein, support first pattern of synchronization message issued transaction to utilize the Internet service transmission to produce event message according to the production event information register system of claim 40.
42. according to the production event information register system of claim 41, wherein, the indication of described first pattern of described production data storehouse service response produces the response message that turns back to described production event object.
43. according to the production event information register system of claim 40, wherein, described production data storehouse service response is supported the indication of second pattern of asynchronous message issued transaction, is created in the result of the form stored in described production data storehouse.
44., wherein, support second pattern of asynchronous message issued transaction to utilize the message queue transmission to produce event message according to the production event information register system of claim 40.
45. production event information register system according to claim 44, wherein, described second pattern is implemented on client computer by messenger service, and the formation that client computer comprises is used for storing message in client computer with comprising being connected under the interrupted situation between the server machine that described production data storehouse is served.
46. according to the production event information register system of claim 45, wherein, server machine comprises:
With the formation that described second pattern is associated, be used for receiving the production event message from described client computer; And
The service of wherein said production data storehouse comprises scheduler program, is used to observe the formation of producing event message.
47. according to the production event information register system of claim 40, wherein, the service of described production data storehouse comprises message processing program, is used to receive the production transmission of messages of asynchronous and synchronous two kinds of patterns.
48. according to the production event information register system of claim 47, wherein, described message processing program is analyzed described at least a portion of receiving message, to determine the production server version, calls it and handles the described message of receiving.
49. according to the production event information register system of claim 40, comprise further and produce the event object configuration interface that the interface that comprises makes the user can specify described multi-mode to produce one of a plurality of massage patterns of being supported at the event message interface.
50. a production event information register system of using in manufacturing environment, described system comprises:
The production data storehouse comprises being used to store one group of form producing event information;
Produce event object, be used for response and trigger production incident generation production event message, described production event message comprises the data set corresponding with the production incident;
The service of production data storehouse, be used for the described production event message that described production event object is produced is handled, described production service comprises the production server, be used to handle the information content in the described production event message, in described production data storehouse the data set of described production incident correspondence is tabulated then, wherein basis provides the production the expanded event message mode producing of the expansion that predetermined production event message is defined and handles described production event message.
51. according to the production event information register system of claim 50, wherein, described production event message mode expansion comprises the message authentication standard definition.
52. according to the production event information register system of claim 50, wherein, described production event message mode expansion comprises the informed source definition.
53. according to the production event information register system of claim 50, wherein, described production event message mode expansion comprises produces the definition of Service events Message Processing.
54. according to the production event information register system of claim 50, wherein, described production event message mode expansion comprises the definition of production server version, one of possible many production server versions that its regulation is kept by the service of described production data storehouse.
55. according to the production event information register system of claim 50, wherein, described production event message mode expansion comprises the expansion of manufacture process electronical record.
56. according to the production event information register system of claim 50, wherein, described production event message mode expansion comprises the response message definition.
57. a method of handling the caused production incident of manufacturing environment, wherein, the production data storehouse is stored in one group of form and is produced event information, said method comprising the steps of:
Receive to trigger and produce event notice;
Respond described receiving step, produce the production event message that comprises the data set corresponding with the production incident, described data set comprises the server version descriptive information;
The service of producing receives described production event message by being associated with described production data storehouse;
By the described server version descriptive information of described production service analysis, and call the production server version and handle described production event message.
58. according to the method for claim 57, wherein, the described server version descriptive information of regulation in to the expansion of producing massage pattern.
Claims (58)
1. production event information register system of in manufacturing environment, using, described system comprises:
The production data storehouse comprises being used to store one group of form producing event information;
Produce event object, be used for response and trigger production incident generation production event message, described production event message comprises the data set corresponding with the production incident; And
The service of production data storehouse, be used for the described production event message that described production event object is produced is handled, described production service comprises the production server, be used to analyze the information content in the described production event message, store the data set of described production incident correspondence then, wherein said analysis comprises uses validation criteria at least one value of described data set.
2. according to the production event information register system of claim 1, wherein, described validation criteria is corresponding to the store industrial standard of producing event information.
3. according to the production event information register system of claim 1, wherein, described validation criteria regulation comprises at least one non-NULL production attribute of the one group of a plurality of production attribute that is associated with production event message type.
4. according to the production event information register system of claim 3, wherein, described production event message type belongs to material.
5. according to the production event information register system of claim 1, wherein, described validation criteria comprises context affirmation rule, and it uses a plurality of production attributes of crossing in the single production event message.
6. according to the production event information register system of claim 1, wherein, described validation criteria comprises the data validation rule, is applied in the described production event message to producing the value of attribute defined.
7. according to the production event message of claim 6, wherein, described data validation rule predetermining is formed the pattern of a string character of described production attribute.
8. according to the production event message of claim 6, wherein, be unique in the grid column of value in described production data storehouse of the described production attribute of described data validation rule predetermining.
9. according to the production event message of claim 6, wherein, the value of the described production attribute of described data validation rule predetermining is present in the grid column in the described production data storehouse.
10. according to the production event message of claim 6, wherein, the value of the described production attribute of described data validation rule predetermining is optional in described production event message.
11. the production event information register system according to claim 1 further comprises message interface, it supports to receive the production event message by asynchronous and synchronous two kinds of production event message transmission modes.
12. according to the production event information register system of claim 1, wherein, described validation criteria is included within the described production event message.
13. according to the production event information register system of claim 1, wherein, the result who uses described validation criteria is stored within the described production event message.
14. according to the production event information register system of claim 1, further comprise the production server of a plurality of versions, wherein produce event message by the metadata expansion of producing event message being stipulated the concrete version of the production server of described a plurality of versions.
15. production event information register system according to claim 1, further comprise high-speed cache, it is right to be used to store event data sign and unique form project label, and wherein said unique form project label is assigned to the project that comprises with in described event data identifies first form in described production data storehouse of the event data that is associated.
16. a method of handling the caused production incident of manufacturing environment, wherein the production data storehouse is stored in one group of form and is produced event information, said method comprising the steps of:
Receive to trigger and produce event notice;
Respond described receiving step, produce the production event message that comprises the data set corresponding with the production incident; And
Analyze the information content in the described production event message, wherein said analysis comprises uses validation criteria at least one value of described data set.
17. according to the method for claim 16, wherein, described generation step is implemented by producing event object.
18., further comprise the step that described data set is tabulated in described production data storehouse according to the method for claim 16.
19. the method according to claim 16 further may further comprise the steps:
Storage event data sign and unique form project label in producing server cache, described unique form project label are assigned to and comprise and project in described event data identifies first form in described production data storehouse of the event data that is associated; And
Retrieval and the corresponding described unique form project label of described event data sign from described production server cache, and described unique form project label is stored in the project of second form, so that the described item chain in described second form is received described project in described first form by described unique form project label.
20. computer-readable medium that comprises computer executable instructions, it helps to handle the caused production incident of manufacturing environment, wherein the production data storehouse is stored in one group of form and is produced event information, and described computer executable instructions is convenient to carry out following steps:
Received by producing the production event message that event object produces by production data storehouse server, described production event message comprises the data set corresponding with the production incident; And
Analyze the information content in the described production event message, wherein said analysis comprises, before the described data set of storage, by the service of production data storehouse at least one value of described data set is used validation criteria in the production data storehouse.
21. a production event information register system of using in manufacturing environment, described system comprises:
The production data storehouse comprises being used to store one group of form producing event information;
Produce event object, be used for response and trigger production incident generation production event message, described production event message comprises the data set corresponding with the production incident; And
The service of production data storehouse is used for the described production event message that described production event object is produced is handled, and described production service comprises the production server, is used to store the data set of described production incident correspondence, and wherein said production server comprises:
High-speed cache, it is right to be used to store event data sign and unique form project label, and wherein said unique form project label is assigned to the project that comprises with in described event data identifies the form in described production data storehouse of the event data that is associated.
22. according to the production event information register system of claim 21, wherein, described form comprises the production solicited message.
23. according to the production event information register system of claim 21, wherein, described form comprises the process segment information.
24. production event information register system according to claim 21, wherein, described production data storehouse comprises first form and second form at least, and described cache stores event data sign and corresponding unique form project label, described unique form project label is corresponding to the project of described first and second forms in one of them, and described first and second forms comprise the event data that is associated with described event data sign.
25. according to the production event information register system of claim 24, wherein, described first form comprises the production solicited message, described second form comprises the process segment information.
26. production event information register system according to claim 25, wherein, described production server comprises computer executable instructions, be used for storing new projects at the 3rd form, comprise the segmentation response message, and comprise first unique form project label and second unique form project label, correspond respectively to the project in described first and second forms.
27. production event information register system according to claim 21, wherein, described high-speed cache comprises that first event data sign and the first unique form project label corresponding with the first form project are right, and described production server comprises computer executable instructions, be used in the new form project of described production server storage, described new form project comprises described first unique form project label, thereby described new form project is linked to the described first form project.
28. a method of handling the caused production incident of manufacturing environment, wherein the production data storehouse is stored in one group of form and is produced event information, said method comprising the steps of:
Receive to trigger and produce event notice;
Respond described receiving step, produce the production event message that comprises the data set corresponding with the production incident; And
Handle the information content in the described production event message, described processing is included in the form project store data inside group in the described production data storehouse with unique form project label, and described treatment step further may further comprise the steps:
At first in the first form project stored in described production data storehouse partial data group at least; And
Secondly producing event data sign and the unique form project label that server cache project stored is allocation of items in described first form.
29. the method according to claim 28 further may further comprise the steps:
Retrieval and the corresponding described unique form project label of described event data sign from described production server cache project, and described unique form project label is stored in the project of second form, thereby the described item chain in described second form is received described project in described first form by described unique form project label.
30. according to the method for claim 29, wherein, described first form comprises the production solicited message, described second form comprises the segmentation response message.
31. according to the method for claim 29, wherein, described first form comprises the process segment information, described second form comprises the segmentation response message.
32. according to the method for claim 31, wherein, described production data storehouse comprises the 3rd form, described the 3rd form comprises the production solicited message, and described method further may further comprise the steps:
From the described production server cache retrieval unique production request form project label corresponding with the production request mark that is provided, and will store into from described unique form project label of described the 3rd form in the project in described second form, thereby the described item chain in described second form be received described project in described the 3rd form by described unique production request form project label.
33. according to the method for claim 28, wherein, described generation step is implemented by producing event object.
34. computer-readable medium that comprises computer executable instructions, it helps to handle the caused production incident of manufacturing environment, wherein the production data storehouse is stored in one group of form and is produced event information, and described computer executable instructions is convenient to carry out following steps:
Receive and produce event message, described production event message comprises the data set corresponding with the production incident; And
Handle the information content in the described production event message, described processing is included in the form project store data inside group in the described production data storehouse with unique form project label, and described treatment step further may further comprise the steps:
At first in the first form project stored in described production data storehouse partial data group at least; And
Secondly producing event data sign and the unique form project label that server cache project stored is allocation of items in described first form.
35. according to the computer-readable medium of claim 34, further comprise computer executable instructions, be used to carry out following steps:
Retrieval and the corresponding described unique form project label of described event data sign from described production server cache project, and described unique form project label is stored in the project of second form, thereby the described item chain in described second form is received described project in described first form by described unique form project label.
36. according to the computer-readable medium of claim 35, wherein, described first form comprises the production solicited message, described second form comprises the segmentation response message.
37. according to the computer-readable medium of claim 35, wherein, described first form comprises the process segment information, described second form comprises the segmentation response message.
38. computer-readable medium according to claim 37, wherein, described production data storehouse comprises the 3rd form, and described the 3rd form comprises the production solicited message, and described computer-readable medium further comprises computer executable instructions, is used to carry out following steps:
From the described production server cache retrieval unique production request form project label corresponding with the production request mark that is provided, and will store into from described unique form project label of described the 3rd form in the project in described second form, thereby the described item chain in described second form be received described project in described the 3rd form by described unique production request form project label.
39. according to the computer-readable medium of claim 34, wherein, described generation step is implemented by producing event object.
40. a production event information register system of using in manufacturing environment, described system comprises:
The production data storehouse comprises being used to store one group of form producing event information;
Produce event object, be used for response and trigger production incident generation production event message, described production event message comprises the data set corresponding with the production incident;
The service of production data storehouse, be used for the described production event message that described production event object is produced is handled, described production service comprises the production server, be used for before the described production data storehouse storage data set corresponding, handling the information content in the described production event message with described production incident; And
Multi-mode between described production event object and the service of described production data storehouse is produced the event message interface, and wherein said multi-mode is produced the event message interface and supported the asynchronous and synchronous two kinds of message transactions between described production event object and the service of described production data storehouse to handle.
41., wherein, support first pattern of synchronization message issued transaction to utilize the Internet service transmission to produce event message according to the production event information register system of claim 40.
42. according to the production event information register system of claim 41, wherein, the indication of described first pattern of described production data storehouse service response produces the response message that turns back to described production event object.
43. according to the production event information register system of claim 40, wherein, described production data storehouse service response is supported the indication of second pattern of asynchronous message issued transaction, is created in the result of the form stored in described production data storehouse.
44., wherein, support second pattern of asynchronous message issued transaction to utilize the message queue transmission to produce event message according to the production event information register system of claim 40.
45. production event information register system according to claim 44, wherein, described second pattern is implemented on client computer by messenger service, described client computer comprises formation, is used at described client computer and the storing message under the interrupted situation that is connected that comprises between the server machine that described production data storehouse is served.
46. according to the production event information register system of claim 45, wherein, server machine comprises:
With the formation that described second pattern is associated, be used for receiving the production event message from described client computer; And
The service of wherein said production data storehouse comprises scheduler program, is used to observe the formation of producing event message.
47. according to the production event information register system of claim 40, wherein, the service of described production data storehouse comprises message processing program, is used to receive the production transmission of messages of asynchronous and synchronous two kinds of patterns.
48. according to the production event information register system of claim 47, wherein, described message processing program is analyzed described at least a portion of receiving message, to determine the production server version, calls it and handles the described message of receiving.
49. production event information register system according to claim 40, comprise further and produce the event object configuration interface that described production event object configuration interface comprises the interface of one of a plurality of massage patterns of making the user can specify described multi-mode to produce to be supported at the event message interface.
50. a production event information register system of using in manufacturing environment, described system comprises:
The production data storehouse comprises being used to store one group of form producing event information;
Produce event object, be used for response and trigger production incident generation production event message, described production event message comprises the data set corresponding with the production incident;
The service of production data storehouse, be used for the described production event message that described production event object is produced is handled, described production service comprises the production server, be used for will be corresponding in described production data storehouse with described production incident data set tabulation before, handle the information content in the described production event message, wherein basis provides the production the expanded event message mode producing of the expansion that predetermined production event message is defined and handles described production event message.
51. according to the production event information register system of claim 50, wherein, described production event message mode expansion comprises the message authentication standard definition.
52. according to the production event information register system of claim 50, wherein, described production event message mode expansion comprises the informed source definition.
53. according to the production event information register system of claim 50, wherein, described production event message mode expansion comprises produces the definition of Service events Message Processing.
54. according to the production event information register system of claim 50, wherein, described production event message mode expansion comprises the definition of production server version, one of possible many production server versions that its regulation is kept by the service of described production data storehouse.
55. according to the production event information register system of claim 50, wherein, described production event message mode expansion comprises the expansion of manufacture process electronical record.
56. according to the production event information register system of claim 50, wherein, described production event message mode expansion comprises the response message definition.
57. a method of handling the caused production incident of manufacturing environment, wherein, the production data storehouse is stored in one group of form and is produced event information, said method comprising the steps of:
Receive to trigger and produce event notice;
Respond described receiving step, produce the production event message that comprises the data set corresponding with the production incident, wherein said data set comprises the server version descriptive information;
The service of producing receives described production event message by being associated with described production data storehouse;
By the described server version descriptive information of described production service analysis, and call the production server version and handle described production event message.
58. according to the method for claim 57, wherein, the described server version descriptive information of regulation in to the expansion of producing massage pattern.
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US67503705P | 2005-04-25 | 2005-04-25 | |
US60/675,037 | 2005-04-25 | ||
PCT/US2006/015810 WO2006116497A2 (en) | 2005-04-25 | 2006-04-25 | Recording and tracing non-trending production data and events in an industrial process control environment |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN2010105128164A Division CN102004950A (en) | 2005-04-25 | 2006-04-25 | Recording and tracing non-trending production data and events in an industrial process control environment |
Publications (2)
Publication Number | Publication Date |
---|---|
CN101208649A true CN101208649A (en) | 2008-06-25 |
CN101208649B CN101208649B (en) | 2010-12-08 |
Family
ID=37215457
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN200680020822XA Active CN101208649B (en) | 2005-04-25 | 2006-04-25 | System and method for processing the production events caused by manufacturing environment |
CN2010105128164A Pending CN102004950A (en) | 2005-04-25 | 2006-04-25 | Recording and tracing non-trending production data and events in an industrial process control environment |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN2010105128164A Pending CN102004950A (en) | 2005-04-25 | 2006-04-25 | Recording and tracing non-trending production data and events in an industrial process control environment |
Country Status (4)
Country | Link |
---|---|
US (4) | US8321045B2 (en) |
EP (1) | EP1880266A4 (en) |
CN (2) | CN101208649B (en) |
WO (1) | WO2006116497A2 (en) |
Cited By (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102243495A (en) * | 2010-04-26 | 2011-11-16 | 西门子公司 | Electronic work instruction designed for isa-95 standard |
CN102809953A (en) * | 2011-05-31 | 2012-12-05 | 通用电气公司 | Systems and methods for alert capture and transmission |
CN104933609A (en) * | 2015-06-09 | 2015-09-23 | 广西家之宝网络科技有限公司 | Online retailer platform with information transmission modes of synchronization and asynchronous |
CN104933521A (en) * | 2015-06-09 | 2015-09-23 | 广西家之宝网络科技有限公司 | ynchronization transmission online retailer system based on ORM framework |
CN104933575A (en) * | 2015-06-09 | 2015-09-23 | 广西家之宝网络科技有限公司 | Data synchronization transmission online retailer platform having non-refreshment interaction units |
CN104933574A (en) * | 2015-06-09 | 2015-09-23 | 广西家之宝网络科技有限公司 | Online retailer platform with information transmission modes of synchronization and asynchronous |
CN105022785A (en) * | 2015-06-09 | 2015-11-04 | 广西家之宝网络科技有限公司 | ORM frame based data synchronization transfer e-business platform |
CN105023168A (en) * | 2015-06-09 | 2015-11-04 | 广西家之宝网络科技有限公司 | An E-business system realizing data synchronous transmission |
CN105046399A (en) * | 2015-06-09 | 2015-11-11 | 广西家之宝网络科技有限公司 | O2O e-commerce platform based on distributed transaction coordination and control |
CN107211014A (en) * | 2014-12-23 | 2017-09-26 | 迈克菲公司 | Use the event response instrument of data exchange layer system |
CN109997158A (en) * | 2016-11-07 | 2019-07-09 | 纽乐吉集团 | For coordinating the mthods, systems and devices of commodity production |
CN114168879A (en) * | 2021-11-23 | 2022-03-11 | 北京房多多信息技术有限公司 | Information processing method, device, equipment and readable storage medium |
Families Citing this family (52)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7865519B2 (en) | 2004-11-17 | 2011-01-04 | Sap Aktiengesellschaft | Using a controlled vocabulary library to generate business data component names |
US7694287B2 (en) | 2005-06-29 | 2010-04-06 | Visa U.S.A. | Schema-based dynamic parse/build engine for parsing multi-format messages |
US7738973B2 (en) * | 2005-11-14 | 2010-06-15 | Rockwell Automation Technologies, Inc. | Distributed historian architecture and interfaces |
US7831317B2 (en) * | 2005-11-14 | 2010-11-09 | Rockwell Automation Technologies, Inc. | Distributed historian architecture |
CN100573374C (en) * | 2006-09-22 | 2009-12-23 | 鸿富锦精密工业(深圳)有限公司 | Manufacturing monitoring system and method |
US20080082761A1 (en) * | 2006-09-29 | 2008-04-03 | Eric Nels Herness | Generic locking service for business integration |
US7921075B2 (en) * | 2006-09-29 | 2011-04-05 | International Business Machines Corporation | Generic sequencing service for business integration |
US9274857B2 (en) | 2006-10-13 | 2016-03-01 | International Business Machines Corporation | Method and system for detecting work completion in loosely coupled components |
US9514201B2 (en) * | 2006-10-13 | 2016-12-06 | International Business Machines Corporation | Method and system for non-intrusive event sequencing |
US7962495B2 (en) * | 2006-11-20 | 2011-06-14 | Palantir Technologies, Inc. | Creating data in a data store using a dynamic ontology |
US8954350B2 (en) * | 2006-11-28 | 2015-02-10 | Ricoh Company, Ltd. | Order supporting apparatus, control method for an order supporting apparatus, order supporting system, and computer readable storage medium |
US8087030B2 (en) | 2006-12-29 | 2011-12-27 | Sap Ag | Processing a received message |
US9112808B2 (en) | 2007-02-06 | 2015-08-18 | At&T Intellectual Property Ii, L.P. | Devices, systems, and methods for providing data |
US8781988B1 (en) * | 2007-07-19 | 2014-07-15 | Salesforce.Com, Inc. | System, method and computer program product for messaging in an on-demand database service |
DE102008002785A1 (en) * | 2008-02-29 | 2009-10-15 | Schneider Electric Automation Gmbh | Event router scheduler module for event-based connection and synchronization of functional modules in service-oriented components, devices, and supporting applications |
US8389920B2 (en) * | 2008-03-13 | 2013-03-05 | Aptina Imaging Corporation | Method and apparatus for breaking surface tension during a recessed color filter array process |
EP3835893B1 (en) * | 2008-05-02 | 2023-07-12 | AVEVA Software, LLC | System for maintaining unified access to scada and manufacturing execution system (mes) information |
US9418005B2 (en) | 2008-07-15 | 2016-08-16 | International Business Machines Corporation | Managing garbage collection in a data processing system |
EP2169495A1 (en) * | 2008-09-18 | 2010-03-31 | Siemens Aktiengesellschaft | Method for modelling a manufacturing process |
US9131004B2 (en) * | 2009-04-26 | 2015-09-08 | Jeffrey Alan Carley | Method and apparatus for network address resolution |
US8918709B2 (en) | 2009-05-29 | 2014-12-23 | Microsoft Corporation | Object templates for data-driven applications |
US8539475B2 (en) * | 2009-09-29 | 2013-09-17 | Oracle America, Inc. | API backward compatibility checking |
US20110131588A1 (en) * | 2009-12-01 | 2011-06-02 | International Business Machines Corporation | Software architecture that can sense and respond to contextual and state information |
US20110289141A1 (en) | 2010-05-20 | 2011-11-24 | Salesforce.Com, Inc. | Methods and systems for providing a user interface in a multi-tenant database environment |
US9176783B2 (en) | 2010-05-24 | 2015-11-03 | International Business Machines Corporation | Idle transitions sampling with execution context |
DE112010005606T5 (en) * | 2010-05-28 | 2013-04-04 | Mitsubishi Electric Corp. | Logging device, logging system and control method for a logging device |
US8843684B2 (en) | 2010-06-11 | 2014-09-23 | International Business Machines Corporation | Performing call stack sampling by setting affinity of target thread to a current process to prevent target thread migration |
US8799872B2 (en) | 2010-06-27 | 2014-08-05 | International Business Machines Corporation | Sampling with sample pacing |
US8799904B2 (en) | 2011-01-21 | 2014-08-05 | International Business Machines Corporation | Scalable system call stack sampling |
US8819077B1 (en) | 2011-06-30 | 2014-08-26 | Emc Corporation | Dynamic data structures |
US8719305B1 (en) * | 2011-06-30 | 2014-05-06 | Emc Corporation | Object type definitions |
US9092466B1 (en) | 2011-06-30 | 2015-07-28 | Emc Corporation | Trait definitions |
US8527552B2 (en) * | 2011-07-07 | 2013-09-03 | Business Objects Software Limited | Database consistent sample data extraction |
US8739026B2 (en) * | 2011-09-06 | 2014-05-27 | Hewlett-Packard Development Company, L.P. | Markup language schema error correction |
US9639898B2 (en) * | 2012-03-28 | 2017-05-02 | Oracle International Corporation | Tax analysis tool |
EP2728475A1 (en) * | 2012-11-02 | 2014-05-07 | Rockwell Automation Technologies, Inc. | Event management |
US9639572B2 (en) | 2013-09-06 | 2017-05-02 | Sap Se | SQL enhancements simplifying database querying |
US9430523B2 (en) | 2013-09-06 | 2016-08-30 | Sap Se | Entity-relationship model extensions using annotations |
US9354948B2 (en) * | 2013-09-06 | 2016-05-31 | Sap Se | Data models containing host language embedded constraints |
US9442977B2 (en) | 2013-09-06 | 2016-09-13 | Sap Se | Database language extended to accommodate entity-relationship models |
US9361407B2 (en) | 2013-09-06 | 2016-06-07 | Sap Se | SQL extended with transient fields for calculation expressions in enhanced data models |
US9619552B2 (en) | 2013-09-06 | 2017-04-11 | Sap Se | Core data services extensibility for entity-relationship models |
US10361927B2 (en) * | 2014-01-14 | 2019-07-23 | International Business Machines Corporation | Managing risk in multi-node automation of endpoint management |
US11488180B1 (en) * | 2014-01-22 | 2022-11-01 | Amazon Technologies, Inc. | Incremental business event recording |
CN104102168B (en) * | 2014-07-14 | 2017-02-01 | 上海航天能源股份有限公司 | Data transmission method for pressure regulation of natural gas pipeline network |
US10148606B2 (en) * | 2014-07-24 | 2018-12-04 | Twitter, Inc. | Multi-tiered anti-spamming systems and methods |
US10462261B2 (en) * | 2015-06-24 | 2019-10-29 | Yokogawa Electric Corporation | System and method for configuring a data access system |
JP6443312B2 (en) | 2015-09-28 | 2018-12-26 | オムロン株式会社 | Management system |
CN105511819B (en) * | 2015-11-27 | 2018-11-02 | 贵州航天风华精密设备有限公司 | A kind of material Quota Management System based on XML schema |
DE102019117954A1 (en) * | 2019-07-03 | 2021-01-07 | Beckhoff Automation Gmbh | Runtime server for the simultaneous execution of several runtime systems of an automation system |
CN112486478B (en) * | 2020-11-26 | 2023-08-11 | 上海万物新生环保科技集团有限公司 | Event processing method and device based on field driving |
US12026172B2 (en) | 2020-12-15 | 2024-07-02 | Bank Of America Corporation | System and method for automatically validating data stored in multiple locations |
Family Cites Families (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5280610A (en) * | 1990-08-14 | 1994-01-18 | Digital Equipment Corporation | Methods and apparatus for implementing data bases to provide object-oriented invocation of applications |
AU753626B2 (en) * | 1997-05-12 | 2002-10-24 | Mlk Software | Method and apparatus for the centralized collection of geographically distributed data |
US6738775B2 (en) * | 1999-11-30 | 2004-05-18 | Base One International Corp. | Database communication system and method for communicating with a database |
US6983317B1 (en) * | 2000-02-28 | 2006-01-03 | Microsoft Corporation | Enterprise management system |
AU2000245419A1 (en) * | 2000-04-01 | 2001-10-15 | Abb Research Ltd | Method and system for recording and saving data from a production plant |
US20020112070A1 (en) * | 2000-12-08 | 2002-08-15 | The Boeing Company | Network controller for digitally controlling remote devices via a common bus |
US7007038B1 (en) * | 2001-04-06 | 2006-02-28 | Ciena Corporation | Defect management database for managing manufacturing quality information |
US7346519B2 (en) | 2001-04-10 | 2008-03-18 | Metropolitan Regional Information Systems, Inc | Method and system for MRIS platinum database |
US20030101107A1 (en) * | 2001-11-29 | 2003-05-29 | Rishi Agarwal | Inventory management system and method |
US7035877B2 (en) * | 2001-12-28 | 2006-04-25 | Kimberly-Clark Worldwide, Inc. | Quality management and intelligent manufacturing with labels and smart tags in event-based product manufacturing |
US7024593B1 (en) | 2002-03-18 | 2006-04-04 | Emc Corporation | End-to-end checksumming for database environments |
US6862486B2 (en) * | 2003-03-04 | 2005-03-01 | Activplant Corporation | System and method for processing data relating to conditions in a manufacturing process |
US7984129B2 (en) * | 2003-07-11 | 2011-07-19 | Computer Associates Think, Inc. | System and method for high-performance profiling of application events |
ATE515746T1 (en) * | 2003-09-15 | 2011-07-15 | Ab Initio Technology Llc | DATA PROFILING |
WO2005052759A2 (en) * | 2003-11-24 | 2005-06-09 | Ebay Inc. | Business language schema design framework |
US20050223368A1 (en) * | 2004-03-30 | 2005-10-06 | Tonic Solutions, Inc. | Instrumented application for transaction tracing |
US20070038642A1 (en) * | 2004-09-15 | 2007-02-15 | Scott Durgin | Method for providing extensible software components within a distributed synchronization system |
US20070088707A1 (en) * | 2004-09-15 | 2007-04-19 | Scott Durgin | Method for providing extensible software components within a distributed synchronization system |
US8214329B2 (en) * | 2008-08-26 | 2012-07-03 | Zeewise, Inc. | Remote data collection systems and methods |
-
2006
- 2006-04-25 CN CN200680020822XA patent/CN101208649B/en active Active
- 2006-04-25 EP EP06751488A patent/EP1880266A4/en not_active Withdrawn
- 2006-04-25 WO PCT/US2006/015810 patent/WO2006116497A2/en active Application Filing
- 2006-04-25 CN CN2010105128164A patent/CN102004950A/en active Pending
- 2006-04-25 US US11/412,158 patent/US8321045B2/en active Active
- 2006-04-25 US US11/411,438 patent/US8117300B2/en active Active
- 2006-04-25 US US11/412,063 patent/US7840293B2/en active Active
- 2006-04-25 US US11/411,439 patent/US7895315B2/en active Active
Cited By (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102243495A (en) * | 2010-04-26 | 2011-11-16 | 西门子公司 | Electronic work instruction designed for isa-95 standard |
CN102809953A (en) * | 2011-05-31 | 2012-12-05 | 通用电气公司 | Systems and methods for alert capture and transmission |
CN107211014A (en) * | 2014-12-23 | 2017-09-26 | 迈克菲公司 | Use the event response instrument of data exchange layer system |
CN107211014B (en) * | 2014-12-23 | 2021-10-29 | 迈克菲公司 | System and method for an event response tool and computer readable medium |
CN104933521A (en) * | 2015-06-09 | 2015-09-23 | 广西家之宝网络科技有限公司 | ynchronization transmission online retailer system based on ORM framework |
CN104933574A (en) * | 2015-06-09 | 2015-09-23 | 广西家之宝网络科技有限公司 | Online retailer platform with information transmission modes of synchronization and asynchronous |
CN105022785A (en) * | 2015-06-09 | 2015-11-04 | 广西家之宝网络科技有限公司 | ORM frame based data synchronization transfer e-business platform |
CN105023168A (en) * | 2015-06-09 | 2015-11-04 | 广西家之宝网络科技有限公司 | An E-business system realizing data synchronous transmission |
CN105046399A (en) * | 2015-06-09 | 2015-11-11 | 广西家之宝网络科技有限公司 | O2O e-commerce platform based on distributed transaction coordination and control |
CN104933575A (en) * | 2015-06-09 | 2015-09-23 | 广西家之宝网络科技有限公司 | Data synchronization transmission online retailer platform having non-refreshment interaction units |
CN104933609A (en) * | 2015-06-09 | 2015-09-23 | 广西家之宝网络科技有限公司 | Online retailer platform with information transmission modes of synchronization and asynchronous |
CN109997158A (en) * | 2016-11-07 | 2019-07-09 | 纽乐吉集团 | For coordinating the mthods, systems and devices of commodity production |
CN114168879A (en) * | 2021-11-23 | 2022-03-11 | 北京房多多信息技术有限公司 | Information processing method, device, equipment and readable storage medium |
Also Published As
Publication number | Publication date |
---|---|
US20060259515A1 (en) | 2006-11-16 |
US8321045B2 (en) | 2012-11-27 |
EP1880266A4 (en) | 2010-09-08 |
US7895315B2 (en) | 2011-02-22 |
CN101208649B (en) | 2010-12-08 |
US20060259514A1 (en) | 2006-11-16 |
EP1880266A2 (en) | 2008-01-23 |
CN102004950A (en) | 2011-04-06 |
WO2006116497A2 (en) | 2006-11-02 |
WO2006116497A3 (en) | 2007-07-26 |
US20060259912A1 (en) | 2006-11-16 |
WO2006116497B1 (en) | 2007-10-25 |
US7840293B2 (en) | 2010-11-23 |
US20060259911A1 (en) | 2006-11-16 |
US8117300B2 (en) | 2012-02-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN101208649B (en) | System and method for processing the production events caused by manufacturing environment | |
CN1755683B (en) | Contextual action publishing | |
US20090024584A1 (en) | Radio frequency identification (rfid) network system and method | |
US8032635B2 (en) | Grid processing in a trading network | |
US7680752B1 (en) | System and method for predictive process management | |
US7423527B2 (en) | Radio frequency identification (RFID) network system and method | |
Moser et al. | Semantic integration of software and systems engineering environments | |
US20040187140A1 (en) | Application framework | |
US20060224702A1 (en) | Local workflows in a business process management system | |
Khalaf et al. | Business processes for Web Services: Principles and applications | |
US20090037899A1 (en) | Radio frequency identification (rfid) network upgrade system and method | |
US20070016557A1 (en) | Methods for enterprise-level data and process access and presentation | |
CN103034920B (en) | System and method for controlling operations of manufacturing facility | |
WO2003102722A2 (en) | Collaborative business plug-in framework | |
CN101714101A (en) | Supervisory process control, method for manufacturing information system application and configuration device | |
US20070027909A1 (en) | Methods and apparatus for comparison of projects | |
Traore et al. | Service-Oriented Computing for intelligent train maintenance | |
US20070028174A1 (en) | Grid processing dynamic screensaver | |
US7778719B2 (en) | Method, system, apparatus, and computer-readable medium for providing configure to service for a semiconductor manufacturing service guide system | |
Moser et al. | Making expert knowledge explicit to facilitate tool support for integrating complex information systems in the atm domain | |
Selfridge et al. | Managing design knowledge to provide assistance to large-scale software development | |
Nordstrom et al. | Model integrated computing-based software design and evolution | |
Ranno et al. | A review of distributed workflow management systems | |
Moser et al. | Efficient integration of complex information systems in the ATM domain with explicit expert knowledge models | |
Rui | Steps towards computerized administration of factory information resources for CIM |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C10 | Entry into substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
C14 | Grant of patent or utility model | ||
GR01 | Patent grant | ||
TR01 | Transfer of patent right | ||
TR01 | Transfer of patent right |
Effective date of registration: 20171110 Address after: American California Patentee after: Schneider Electronic Software Co., Ltd. Address before: Massachusetts, USA Patentee before: Invensys System Inc. |
|
CP01 | Change in the name or title of a patent holder | ||
CP01 | Change in the name or title of a patent holder |
Address after: California, USA Patentee after: Aviva Software Co.,Ltd. Address before: California, USA Patentee before: Schneider Electronic Software Co.,Ltd. |