1 / 13

How to exchange messages by PSLX (PPS)

IEC/ISO JWG15 meeting in GENOA. How to exchange messages by PSLX (PPS). 2006-06-14 Yasuyuki Nishioka PSLX / Hosei University. Messaging models. Sender. Receiver. Notify model. (1) Notify. Get-Show model. Initiator. Responder. (1) Get. (2) Show. Data processing model. Add

jaxon
Télécharger la présentation

How to exchange messages by PSLX (PPS)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. IEC/ISO JWG15 meeting in GENOA How to exchange messagesby PSLX (PPS) 2006-06-14 Yasuyuki Nishioka PSLX / Hosei University

  2. Messaging models Sender Receiver Notify model (1) Notify Get-Show model Initiator Responder (1) Get (2) Show Data processing model • Add • / Change • / Cancel Initiator Responder If the message received requires confirmation (2) Confirm

  3. Message Structure Message document Get, Show, Add, Change, Cancel, Notify, Confirm Action type User extensional data Header Domain object class Domain object class Body Domain object Party, Plan, Order, Item, Resource, Process, Lot, Task, Operation Domain object Domain object

  4. Message documents Planning information Organizational information CompanyRecord CustomerRecord SupplierRecord BusinessPlan ProductinPlan CapacityPlan Order information Production information CustomerOrder SupplierOrder ShippingRecord ReceivingRecord ProductionOrder CapacityOrder LotSchedule LotRecord TaskSchedule TaskRecord WorkOrder WorkRecord Engineering information Accounting information ItemRecord ResourceRecord RoutingRecord ProcessRecord InventoryRecord CapacityRecord

  5. Domain object <Item type=“material”> XML schema Abstract model Domain object Primitive element Domain property (single) name=“M001” Property value attribute Domain property (multiple) Property element Qualifier + Property value Qualifier + Property value Property element …. … <Capacity value=“10”> <Time value=“2006-06-12”/> </Capacity> …

  6. Basic property object (multiple value) Basic property object (single value) Basic domain objects List of domain objects name parent status party plan order item resource process lot task operation compose produce consume assign relation location capacity progress spec start end price qty duration priority display description author date Party Plan Order Item Resource Process Lot Task Operation

  7. Basic property object (multiple value) Basic property object (single value) Basic domain objects Profile definition for translation Profile for particular implementation Domain object Qualifier Particular name Resource Equipment Equipment Resource Personnel Personnel Lot Child SubLot

  8. Data processing model • Add • Add domain object(s) by listing of ID or describing conditions of the target • Change • Insert, update or delete of domain property(s) of domain object(s) by listing of ID or describing conditions of the target, while the property is indicated by describing another conditions of the property. • Cancel • Delete domain object(s) Any property can be operated

  9. Header information • Where statement • Describes conditions of domain objects to add, change, cancel or get (query). This also describes class of the message content in Show and Notify message • Select statement • Described conditions of domain properties to get (query), or update in the objects requested by Change model. • Insert / Update / Delete statement • Described conditions of domain properties to insert/update/delete in the objects requested by Change model. • Computational statement • Describes calculation method and the target properties in Get messages. This also describes the properties and the calculation results in Show and Notify messages

  10. Query (Get-Show) example <CustomerRecord action=“Get”> <Header> <Party id=“pps:where” name=“Hosei”> <Party id=“pps:select”><Location/></Party> </Header> </CustomerRecord> Responder Initiator <CustomerRecord action=“Show”> <Header> <Party id=“pps:where” name=“Hosei”> <Party id=“pps:select”><Location/></Party> </Header> <Party id=“2038”> <Location type=“user:city” value=“Tokyo”/> <Location type=“user:country” value=“Japan”/> </Party> </CustomerRecord>

  11. Change properties example <LotRecord action=“Change”> <Header> <Lot id=“pps:where” name=“L234”/> <Lot id=“pps:insert”> <Consume value=“10”> <Time value=“2006-06-12T10:00:00/> </Consume> </Lot> </Header> Responder <Lot id=“001” name=“L234”> <Produce value=“100”> <Time value=“2006-06-10T17:00:00/> </Produce> <Consume value=“10”> <Time value=“2006-06-11T13:40:00/> </Consume> <Consume value=“10”> <Time value=“2006-06-12T10:00:00/> </Consume> </Lot> Initiator Inserted property

  12. We agree with ISA95.00.05 if.. • The scope section describes this is not an implementation specification but abstract models. • The verbs defined are changed to simple and general terms without regarding the OAGIS verbs. • Every Wildcard specification is informative except the concept that wildcard shows a class conditions of the targets. • The target objects of exchange are not limited to the 19 object defined in 6.2 (6.1 needs to be deleted.) • The tables section 6 are unique format that has some rules for the descriptions. • Abstract transaction rules (instead of all tables in sec. 6) are specified and the only additional rules are added for each object.

  13. Push model Process(Add) Process Process(Change) Change Process(Delete) Cancel Publish model Sync(Add) Sync_add Sync(Change) Sync_change Sync(Delete) Sync_delete Verbs

More Related