1. Service-Oriented Architectures for Smart Manufacturing Project
Nenad Ivezic
Serm Kulvatunyou

2. Cloud-Enabled Service- Oriented Manufacturing
Level 4
ERP
MOM
SCADA
Sensors / Actuators
Production Processes
Level 3
Level 2
Level 1
Level 0
How best to transition?
Wen, Xianhe, and Xiaojun Zhou. "Servitization of manufacturing industries based on cloud-based business model and the down-to-earth implementary path." The International Journal of Advanced Manufacturing Technology 87, no. 5-8 (2016):
ERP – Enterprise Resource Planning
MOM – Manufacturing Operations Management
SCADA – Supervisory Control and Data Acquisition

3. Integrability, Interoperability, and Composability
Enables correct information exchange by using correct protocols.
Interoperability
Enables correct understanding of meaning by using correct conceptual models.
Composability
Enables correct consequences of interaction by using correct behavior models.

4. Integrability, Interoperability, and Composability
Enables correct information exchange by using correct protocols.
Interoperability
Enables correct understanding of meaning by using correct conceptual models.
Composability
Enables correct consequences of interaction by using correct behavior models.
Message standards are key to achieving services interoperability.

5. Why is This Significant?
The number of manufacturing services is growing substantially.
Soon, all manufacturers will need to be using those services.

6. Need: Increased Efficiency of Services Integration
Manufacturers will need to assure their business processes are supported and improved by services
They will be looking for optimal services out there
Ease of integration, configuration, and re-configuration
The services will need to be interoperable and composable, based on standards.

7. Issue: Standards are Hard to Use
Standards are complex
Standards lack support for reuse

8. Key Technical Challenge
We need to re-engineer the message standard development and usage to address the issue.

9. A Leading Message Standards Development Organization: Open Applications Group Inc.
Front Office
Operations
Back Office
Supply Chain
Logistics
Edge Applications
Automotive
Aerospace
Defense
Chemical
High-tech
Construction

10. Who Uses Open Applications Group Integration Specification (OAGIS)?

11. Key Technical Challenge – A Focus
We need to re-engineer the message standard development and usage.

12. Traditional and Model-Driven Approach
The design is a human-readable-only specification
The design is often an afterthought, implementation is priority one
The design is often freely interpreted by human developer leading to an implementation
Model-Driven:
The design is a computer- processable model
The design is central – the model grows, gets extended, evolves
An implementation is directly derived from the model

13. Traditional Message Standards Use (1)
Design Phase
Implementation Phase
Legend:
Manual Effort or Human Readable Document
Automated Process or Computer Processable Resource

14. Traditional Message Standards Use (2)
Business Process Analyst
Human Readable Document
Integration
Requirements
Design Phase
Implementation Phase
Legend:
Manual Effort or Human Readable Document
Automated Process or Computer Processable Resource
Profile Message in Implementation Language L1

15. Traditional Message Standards Use (3)
Business Process Analyst
Core OAGi Standard Message Definitions
in Language L1
Integration
Requirements
Design Phase
Implementation Phase
SW Developer
Application
Schemas
Document Editor
Human Developer-based Message Profiling
Legend:
Manual Effort or Human Readable Document
Automated Process or Computer Processable Resource
Profile Message in Implementation Language L1

16. Traditional Message Standards Use (4)
Business Process Analyst
Business Process Analyst
Human Readable Document
Core OAGi Standard Message Definitions
in Language L1
Integration
Requirements
Integration
Requirements
Hard to Reuse
Design Phase
Implementation Phase
SW Developer
Application
Schemas
Document Editor
Human Developer-based Message Profiling
Hard to Reuse
Legend:
Manual Effort or Human Readable Document
Automated Process or Computer Processable Resource
Profile Message in Implementation Language L1

17. Traditional Message Standards Use (5)
Business Process Analyst
Business Process Analyst
Core OAGi Standard Message Definitions
in Language L1
Integration
Requirements
Integration
Requirements
Hard to Reuse
Design Phase
Implementation Phase
SW Developer
Application
Schemas
Document Editor
Human Developer-based Message Profiling
Hard to Reuse
High-cost re-implementation
Legend:
Manual Effort or Human Readable Document
Automated Process or Computer Processable Resource
Profile Message in Implementation Language L2
Profile Message in Implementation Language L1

18. Model-Driven Message Standards Use (1)
Business Process Analyst
Business Process Catalog
Business Process
Context Model
Human Readable Documents
Business Process Classification Tool
Business Process Context & Semantic Constraints
Specification
Design Phase
Implementation
Phase
Legend:
Manual Effort or Human Readable Document
Automated Process or Computer Processable Resource
Profile Message in Implementation Language L1

19. Model-Driven Message Standards Use (2)
Business Process Analyst
Business Process Catalog
OAGi Standard Repository
Business Process
Context Model
Human Readable Documents
Business Process Classification Tool
Core Component Model
Business Process Context & Semantic Constraints
Specification
Syntax Independent OAGi Standard Message Definitions
Design Phase
Implementation
Phase
Legend:
Manual Effort or Human Readable Document
Automated Process or Computer Processable Resource
Profile Message in Implementation Language L1

20. Model-Driven Message Standards Use (3)
Business Process Analyst
Business Process Catalog
Integration Engineer
OAGi Standard Repository
Business Process
Context Model
Human Readable Documents
Business Process Classification Tool
Core Component Model
Semantic Restriction
Context
Usage Situation
Business Process Context & Semantic Constraints
Specification
Syntax Independent OAGi Standard Message Definitions
Business Information Entity
Syntax Independent, Context Specific Profile Message
Design Phase
Implementation
Phase
Legend:
Manual Effort or Human Readable Document
Automated Process or Computer Processable Resource
Profile Message in Implementation Language L1

21. Model-Driven Message Standards Use (4)
Business Process Analyst
Business Process Catalog
Integration Engineer
OAGi Standard Repository
Business Process
Context Model
Human Readable Documents
Business Process Classification Tool
Core Component Model
Semantic Restriction
Context
Usage Situation
Business Process Context & Semantic Constraints
Specification
Syntax Independent OAGi Standard Message Definitions
Business Information Entity
Syntax Independent, Context Specific Profile Message
Design Phase
Implementation
Phase
Language L1 Specification
Syntax Specific Generation
Legend:
Manual Effort or Human Readable Document
Automated Process or Computer Processable Resource
Profile Message in Implementation Language L1

22. Model-Driven Message Standards Use (5)
Business Process Analyst
Business Process Catalog
Integration Engineer
OAGi Standard Repository
Business Process
Context Model
Human Readable Documents
Business Process Classification Tool
Core Component Model
Semantic Restriction
Context
Usage Situation
Business Process Context & Semantic Constraints
Specification
Syntax Independent OAGi Standard Message Definitions
Business Information Entity
Syntax Independent, Context Specific Profile Message
Design Phase
Implementation
Phase
Language L2 Specification
Language L1 Specification
Syntax Specific Generation
Low-cost re-implementation
Legend:
Manual Effort or Human Readable Document
Automated Process or Computer Processable Resource
Profile Message in Implementation Language L2
Profile Message in Implementation Language L1

23. Model-Driven Message Standards Use (6)
Business Process Analyst
Business Process Catalog
Integration Engineer
OAGi Standard Repository
High Potential for reuse
Business Process
Context Model
Human Readable Documents
Business Process Classification Tool
Core Component Model
Semantic Restriction
Context
Usage Situation
Business Process Context & Semantic Constraints
Specification
Syntax Independent OAGi Standard Message Definitions
High Potential for reuse
Business Information Entity
Syntax Independent, Context Specific Profile Message
Design Phase
Implementation
Phase
Language L2 Specification
Language L1 Specification
Syntax Specific Generation
Legend:
Manual Effort or Human Readable Document
Automated Process or Computer Processable Resource
Profile Message in Implementation Language L2
Profile Message in Implementation Language L1

24. Model-Driven Message Standards Use (7)
Business Process Analyst
Business Process Catalog
Integration Engineer
OAGi Standard Repository
High Potential for reuse
Business Process
Context Model
Human Readable Documents
Business Process Classification Tool
Core Component Model
Semantic Restriction
Context
Usage Situation
Business Process Context & Semantic Constraints
Specification
Syntax Independent OAGi Standard Message Definitions
High Potential for reuse
Business Information Entity
Syntax Independent, Context Specific Profile Message
Design Phase
Implementation
Phase
Syntax Specific Generation
Semantic Refinement
Tool (SRT)
Low-cost re-implementation
Legend:
Manual Effort or Human Readable Document
Automated Process or Computer Processable Resource
Profile Message in Implementation Language L2
Profile Message in Implementation Language L1

25. Model-Driven Message Standards Use (8)
Business Process Cataloging
& Classification System (BPCCS)
Business Process Analyst
Business Process Catalog
Integration Engineer
OAGi Standard Repository
High Potential for reuse
Business Process
Context Model
Human Readable Documents
Business Process Classification Tool
Core Component Model
Semantic Restriction
Context
Usage Situation
Business Process Context & Semantic Constraints
Specification
Syntax Independent OAGi Standard Message Definitions
High Potential for reuse
Business Information Entity
Syntax Independent, Context Specific Profile Message
Design Phase
Implementation
Phase
Syntax Specific Generation
Semantic Refinement
Tool (SRT)
Low-cost re-implementation
Legend:
Manual Effort or Human Readable Document
Automated Process or Computer Processable Resource
Profile Message in Implementation Language L2
Profile Message in Implementation Language L1

26. Why These Two Tools?
Semantic Refinement Tool & Business Process Cataloging and Classification System have been selected to
Boot-strap Model-Driven approach to message standards
Enable low-hanging fruit and engage industry early in the R&D process

27. Semantic Refinement Tool -- Objective
To enable model-driven development of the new type of message standard that is
more precise,
more automated,
less complex.

28. Semantic Refinement Tool: Accomplishments (1)
Developed a new syntax-independent data model and structure for OAGIS standard
To allow standards developers to reliably store, develop, use, and share message specifications – based on CCS (ISO ) standard
Designed a cloud-based architecture for collaborative message specification management

29. Semantic Refinement Tool: Accomplishments (2)
NIST developed and verified a prototype Manufacturing Standards Semantic Refinement Tool (MSSRT) with feedback from OAGi members.
NIST transitioned the prototype to JustTransform to develop a cloud- based multi-tenant implementation

30. Semantic Refinement Tool: Accomplishments (3)
Developed testing method to ensure that language-specific representations of the standard are functionally equivalent to the language-independent representation
Developed analysis method for conformance of profiles with respect to the standard message specification

31. Business Process Cataloging and Classification System: Objective
To enable model-driven development of the business context specification that allows
high-precision message specification,
broad coverage of business process context properties,
search, discovery, and evolution of business processes

32. Business Process Cataloging and Classification System: Accomplishments (1)
Created the BPCCS meta- model based on ebRIM (ISO/TS ) standard
Designed method for Business Process Model-based message profiling and business process search

33. Business Process Cataloging and Classification System: Accomplishments (2)
Developed and verified a BPCCS prototype with feedback from OAGi industry members.
Validating prototype for message profiling and business process search

34. Business Process Cataloging and Classification System: Accomplishments (3)
Enabled business process discovery and matching
Business Process
Classification Scheme
Node
Context Aspect
Context Dimension
Why?
When?
Who?
Where?
What?
How?
BusinessGoal
BusinessEvent
Role
Activity
Geo Location
Org. Unit
Process Cat.
Inf. Object …
Application
APQC PCF
SCOR
OAGIS BODs
ISA-95
Industry
NAICS
ISIC
ISO 3166
EDI CL 3035 OY US 44
10279
Zachman
Framework
ebXML, CCTS, UN/CEFACT UCM

35. Industry Interactions, Workshops
Collaboration with the Smart Manufacturing Leadership Coalition (SMLC), MESA International, Cyber-Physical Systems Public Working Group
New Workshop Series:
2015 WS on Open Cloud Architectures for Smart Manufacturing
2016 WS Drilling down on Smart Manufacturing -- Enabling Composable Apps
2017 WS Enabling Composable Service-Oriented Manufacturing Systems

36. Industry Collaborators
OAGi
Land O’ Lakes
Oracle
Boeing
iBASEt
Trisotech
AgGateway
E2open
ADM

37. Industry Panel Today OAGi – David Connelly, CEO
Land O’ Lakes – Scott Nieman, Enterprise Integration Architect
Oracle -- Michael Rowell, Application Architect & OAGIS Architect
Boeing -- Jeff Rice, Lead Application Architect

38. Semantic Refinement Tool Demo

39. Summary
The project helps industry address interoperability challenges for Service- Oriented Manufacturing (SOM)
Industry requires improved message standards and their development processes
The project team worked with industry and responded with
New model-driven approach to development and use of message standards
Software tools in support of the new approach
Industrial collaborations and standards development leadership
New research workshop series on Composable SOM

40. BACKUP SLIDES

41. Who Uses OAGIS?

42. Static and Dynamic Aspects of Service Interfaces
Static aspect
Syntax and semantic information defining data exchange by messages
Referred to as message schema
Dynamic aspect
Process information defining dynamics of message exchange protocol
Referred to as interaction structure

43. Changes the Interface Standards Development Processes Must Accommodate
We are moving from enterprise-centric to service-centric view of the world
Today
Business model is Static, Direct
Resources are Proprietary, Localized
Access is by Ownership
Provisioning is Permanent, Fixed
Allocation is Predictable, Schedule-driven
Enterprise Architecture is Hierarchical
Applications Architecture is Monolithic
Tomorrow
Business model is Dynamic, Mediated
Resources are Shared, Distributed
Access is by Contract, On-demand
Provisioning is Temporary, Reconfigurable
Allocation is Variable, Customer-centric
Enterprise Architecture is Flattened
Applications Architecture is Compositional
Standards development organizations cannot afford to continue to abstract from complexities of interface standards lifecycle.

44. Future Outlook
Enhancing the MSSRT tool with semantic awareness and further standard life cycle management support
Enhancing the BPCCS tool for semantic management capabilities
Taking SOA to the shop floor – developing a Cyber Physical Manufacturing Service modeling framework