ISA 95 Working Group Process Centric Exchanges Gavan W Hood July 23, 2015 GWH 2.1

What is the problem In the first set of published ISA 95 web services from Rockwell the following concepts were involved alongside B2MML, the need still exists for these companion services: An end point configuration service that configured the message dialog semantics, data formats, compression, mapping, custom extensions Simple noun – verb implementation like exists today in Oagis model but has generated multiple message definition's, this could simplified to an attribute on the http request (following REST spec) Ability to add custom interfaces that allowed for scenarios not handled by B2MML Higher level functions that aggregated lower level functions into single event. Many of the extra functions presented were implemented as companions interfaces alongside the B2MML interface /messages which kept the B2MML representation clean.

Why is this a problem The B2MML specification has become more complex than it needs to be and will become more complex if additional changes are incorporated directly in the B2MML schema. The ability to support different dialogs (sequences of messages in a transaction, higher level events etc becomes more difficult), especially if more advanced concepts like mulit-step business processes which have multiple publishers and subscribers are represented. (where we are headed)

How 1.Include a set of system middleware level system services in ISA 95. that allow users to publish the sets of message exchange dialogs (work flows), custom messages as profiles.( These service definitions may best be implemented companion specification to B2MML). Maybe B2MMLConfiguration service. 2.Allow more flexibility in message definition. Extend B2MML schema to support one or more elements under a users element / complex type, Distinguish the complex type from core B2MML types within a user namespace. (similar to current extension but all new root element) The elements would be able to be validated as top level schema elements (representing message body) 3.Allow decomposition of B2MML elements into smaller root element. E.g: A message that has only MaterialActual. 4.Establish a user forum for publication, review and approval of user defined extensions and profiles. – This would require publication of documentation, schema files and must pass a prescribed validation test.