CloudManA Platform for Portable Cloud Manufacturing Services

Soheil Qanbari, Samira Mahdizadeh, Soroush Vedaie, Schahram Dustdar

IEEE BigData 2014

Distributed Systems GroupTU Vienna

dsg.tuwien.ac.at

Cloud Manufacturing

"Distributed manufacturing execution model, where underlying resources(Humans, Software, Things) envisaged in the Internet of Things (IoT),are elastically exposed and utilized as cloud services, then composedand orchestrated for a manufacturing task in an on- demand fashion."

Manufacturing Product Bill of Materials (BOM)

3

Car Bill of Materials (Parts to Assemble)

Production Plan

Car Structure & Specification

Languages/Technologies today

B2MML(Business-to-Manufacturing Markup Language) provides animplementation of the ISA-95 standard in terms of XSD schemadefinitions.

Product Data eXchange (PDX) standard for the e-supply chain:Provides a communicating product content information betweenOriginal Equipment Manufacturers (OEMs), Manufacturing Servicesproviders and component suppliers.

Standard for the Exchange of Product (STEP) is an ISO standard forthe computer-interpretable representation and exchange of productmanufacturing information.

4

What’smissing?

What is Missing?

5

Nonfunctional behavior and qualityof service (QoS) (High availability)

Dynamic Product Configuration

Manufacturing Service Portability

Automation of Deployment & Mgmt

OASIS TOSCA Standard:

6

Node Template

Node Type

Properties

Relationship

Relationship Type

ManagementOperations

ImplementationArtifacts

Mutiple DeploymentArtifacts

Embedd ManagementLogic

Embedds DeploymentLogic

Reusable, Portable,Tracable Plans

Vendor-neutralEcosystem

ApplicationTopology

Automation of

Deployment

Portable

Plans

Policy

Template

Expose Non-Functional Properties

Exposes QoS

Defines the structureof observable

properties

Policy-LanguageAgnostic

TOSCA-Based Manufacturing Policies

Nonfunctional behavior and quality of service (QoS) are defined inTOSCA policies.

Policies are AND-combined <-> enforced by TOSCA-basedmanufacturing build plans.

Policies in TOSCA independent of a policy language (e.g., Ponder2).

Example:

sensors on production lines monitor device operations and send theevents to the TOSCA container, where an obligation policy agentinterprets the event’s meaning and correlates it to a running instance.The agent then identifies the model from which this instance wasderived to get the policy, evaluates the product’s nonfunctionalbehavior against this policy, and invokes the corresponding actions.7

TOSCA Plans as Manufacturing Workflows

8

TOSCA plans know how to instantiate & orchestrate, and terminatethe process models and production flow.

Manufacturing process contains tasks referring to the operations ofmanufacturing service interfaces from collaborating manufacturers.

CloudMan: A Platform for PortableManufacturing Services

9

CloudMan Stakeholders/Ecosystem

10

OEMs: Original Equipment Manufacturers produce devices.

Cloud Platform Providers: Offer computing resources.

Product Developers: Model TOSCA-based BoMS.

Manufacturers: Provide production lines, shopfloor.

Coordinators: Orchestrate federated manufacturing.

Auditors: Watch production KPI metrics for QA.

CloudMan API Requirements

RQ1. APIs executable on Multiple Cloud-enabled Manufacturing Systems.

RQ2. Discovering Product Resources and Materials through Query Interface.

RQ3. Match-making APIs to Map/Utilize TOSCA-based BOMS to Services toProduction Resources.

RQ4. Ensuring end-to-end BOMS-centric Manufacturing Resource Coverage

RQ5. Manufacturing Monitoring through multi-Production Lines Watch Interface

RQ6. Managed Interoperability of Production Flow among Multiple Factories

11

5 Interconnected Layers (CloudMan's Face, Body, Brain,Heart & Skeleton)

Layer 1. Manufacturing Virtual Applications (MVA) "Face"

Layer 2. Manufacturing Core Services (MCS) "Body"

Layer 3. Manufacturing Execution System (MES) "Brain"

Layer 4. Manufacturing Service Bus (MSB) "Heart"

Layer 5. Manufacturing Infrastructure (MI) "Skeleton"

12

CloudMan Architecture

13

CloudMan Face (MVA Layer):

* On-demand Manufacturing Orders.* Product Topology Definition.* 3rd-Party Engagement.* Vertical Manufacturing Application.* Real-time Manufacturing Dashboard.

CloudMan Body (MCS Layer):

* ESB is in place to Connect Layers.* Routing and Queuing of Messages.* Choreography of Events.* Authorize MFG Service Access.* Real-time KPI Monitoring.

CloudMan Brain (MES Layer):

* TOSCA-based BOMS Container.* Deploy TOSCA-based BOMS.* Resource Demand/Supply Control.* Production Plan Scheduling.* Invoke Manufacturing Services.

14

CloudMan Heart (MSB Layer):

* Route Commands to Machines.* Determine Message Receipent.* Manage Data Flow Transmission.* Load balance Production Lines.* Failure Detection.

CloudMan Skeleton (MRL Layer):

* Encapsulates Machines, Sensors, etc.* Utilize Things as Services.* Machine to Machine Communication.* Dynamic Preventive Maintanence.* Gateways and Device APIs.

CloudMan Data Architecture

16

Conclusion

Portable Composite Manufacturing Services

Elastic Manufacturing Resource Allocation/Sharing

Vendor-neutral Manufacturing Service Policy-enforcement

Orchestration of Production Plans amongCollaborating Manufacturers/Production Lines

Thanks for your attention!

Schahram Dustdar

Distributed Systems GroupTU Wien

dsg.tuwien.ac.at