How to exchange messages by PSLX (PPS) Yasuyuki Nishioka PSLX / Hosei University IEC/ISO JWG15 meeting in GENOA

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

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

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

Domain object Domain property (single) Domain property (multiple) … Property value Qualifier + Property value …. Primitive element attribute Property element … Abstract model XML schema <Item type=“material”> name=“M001”

List of domain objects Party Plan Order Item Resource Process Lot Task Operation Basic 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 Basic property object (single value) price qty duration priority display description author date Basic property object (multiple value)

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

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

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

Query (Get-Show) example Initiator Responder

Change properties example Responder Inserted property Initiator

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

Verbs 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