Cloud Manufacturing Theory

Contents
Aim of study
Literature search
!
!
!
Contribu8ons
!
!
!
Cloud Architecture
Cloud Manufacturing and suppor8ng Technologies
Cloud Service is discussed
! Manufacturing Resources
! Manufacturing Capabili8es
Service oriented interoperable cloud manufacturing is proposed (ICMS)

! Novel manufacturing plaBorm is proposed
Service Methodologies are developed
! It supports customer and enterprise user
2 case studies suppor8ng novel manufacturing plaBorm
Benets of interoperable cloud manufacturing
! Openness , sot eciency , resource sharing , produc8on scalability
Conclusion
Goal
!
This study presents an interoperable manufacturing perspec8ve based on

Cloud manufacturing, ICMS.
!
Cloud manufacturing is a new concept extending and adop8ng the concept of

Cloud compu8ng for manufacturing. The aim of CM is to transform manufacturing
businesses to a new paradigm in that manufacturing capabili8es and resources are
componen8zed, integrated and op8mized globally.
Literature Review
Cloud Compu8ng Structure

IaaS
Physical
machines
Virtual
machines
PaaS
Opera8ng
system
Database
Web server
SaaS
SoSwares
Applica8ons
Literature Review
Cloud Compu8ng
!
Key characteris8c of CCompu8ng is that of pay-as-you-go.
Customer-oriented manufacturing is a promising approach to improving the

service quality and compe88veness, in par8cular for the small and medium-
sized enterprises (SMEs)
Manufacturing Capability and Resources

!
CMService
Cloud Manufacturing Service

!
Self-contained, congurable and

on-demand manufacturing
service package to fulll users
original needs.
CMService can be random,

short- term, long-term, or
strategic.
MCapability
MResource
Zhang et al. (39)

CMService
MCapability
Manufacturing Capability
!
MResource
Zhang et al. (39)
ability of transforming one

form into another in
manufacturing domain. It is
realized via related
MResources.

Design Capability
CMService
domain-specic design knowledge, exper8se

Produc8on Capability
MCapability
speed and quality of output or service

Experimenta8on Capability
experimenta8on knowledge and specialists
Management Capability
planning, organizing, sta- ing, leading and
controlling of an organiza8on
MResource
Communica8on Capability
data & knowledge exchange- ability between
applica8ons/devices
Zhang et al. (39)

CMService
MCapability
!
Manufacturing Resource
!
MResource
Zhang et al. (39)
material and nonmaterial

manufacturing supplies
including equipment,
machine, device and
intelligent proper8es.

MResource
CMService
HARD
RESOURCE
MCapability
MResource
Zhang et al. (39)
SOFT
RESOURCE
Equipment
SoSware
Controlling
device
Knowledge
Materials
Skill
Storage
Personal
Computer
Experience
Transport
Network
MCDM (Mcapability Descrip8on Model )

!
Resource descrip8on model (RDC)

!
MCDM includes the capability of both an individual enterprise and an alliance

made up of mul8ple par8cipants.
10
MCDM
11
RsoSDC
Design Capability
CMService
MCapability
domain-specic design knowledge,

exper8se
Produc8on Capability
RsoSPC
speed and quality of output or service
RhardPC
Experimenta8on Capability
RsoSEC
experimenta8on knowledge and specialists
RhardEC
Management Capability
MResource
RhardDC
planning, organizing, sta- ing, leading and

controlling of an organiza8on
Communica8on Capability
data & knowledge exchange- ability
between applica8ons/devices
RsoSMC
RhardMC
RsoSCC
RhardCC
ICMS / Need for ICMS

!
Why ICMS is proposed?

!
MCapabili8es and business opportuni8es can be integrated and broadcasted in a

larger resource pool, which enhances the compe8veness of the en8re consor8um.
More manufacturing objects can be achieved with minimum investment and

eort.
ICMS provides a user with a big range of exible manufacturing capabili8es.
!
!
Customized and original requirements can be gured out easily, compared with
the tradi8onal manufacturing prac8ce.
For industry, it oers new opportuni8es especially for SMEs.
12
ICMS
13
ICMS / User Cloud Layer

!
At the UC Layer, the CMService consumer is divided into two categories:

!
Customer User (CU)
Enterprise User (EU)
14
ICMS / Customer Enterprise User Rela8ons

!
When customer comes to an enterprise that Enterprise itself cannot fulll.

!
Enterprise search for qualied providers in EIA (Enterprise interface agent )
15
ICMS / User Cloud Layer /

!
SCM searches for most convenient op8ons with help of AI

!
SCM have original and customized requirements from user
In manufacturing Cloud, each enterprise might give dierent services.
The user is able to recognize related MResources and allocate the temporary
partner for the task, with the help of SCM.
16
ICMS / Smart Cloud Manager
17
SCM Analyze poten8al solu8ons and inform appropriate enterprises and also
gives feedback to the reques8ng user.
User assump8on is be to able to op8mize the solu8on based on his/her

original needs and op8ons and nalize request.
informa8on
Product
ICMS / Work Flow

!
18
Users communicate with SCM, EIA and CIA to reach most appropriate
Mcapabili8es.
User recognizes needs
Manufacturing Request
SCM Analyze and Searches

for poten8al solu8ons &
Available op8ons create feedback
User is will select one
op8on based on his/her
original requirements and
nalize request.
Final Request
SCM transmit message to Cloud
ICMS / SCM (SMART CLOUD MANAGER)

!
The SCM module is constructed by intelligent agents.

!
Ar8cial Intelligent agent technology is capable of suppor8ng manufacturing

decisions
However, manufacturing decisions are dicult to make due to
complexity of manufacturing processes,
variety of machines/devices,
uncertainty of resources status.
Thus, to fully u8lize AI and human exper8se/knowledge, a decision-making model

is proposed.
19
ICMS / SCM (SMART CLOUD MANAGER)

!
The SCM module consists of

!
!
!
!
!
EIA : collects EUs requests

CIA : collects CUs requests
BA :
! communicates with provider database
! maps requirements to available CM services
SA
Firewall module
20
ICMS / Manufacturing Cloud

!
Service Applica8on Cloud
Storage Cloud
Physical Resources Domain
21

!
Service Applica8on Cloud

!
The opera8onal processes throughout the supply chain stay in form of CMService
applica8ons at this layer.
The plug-and-play ability of service applica8ons enables exibility and adaptability

to cope with uncertain and changing manufacturing market.
22

!
Smart AGENTS
!
Database maintains the product/ project data as well as the informa8on

of the MResources meshed in SACloud.
To model and recognize these applica8on modules, three smart agents

are developed, i.e., Resource Recogni8on Agent (RRA), Change
Detec8on Agent (CDA) and Billing Agent (BiA).
23

!
Resource Recogni8on Agent (RRA) is responsible for adjus8ng, iden8fying new capability
and termina8on of exis8ng ones.
Change Detec8on Agent (CDA) is in charge of detec8ng and upda8ng resource changes,
such as its availability, price adjustment, facility maintaining, etc. Thus, the up-to-date
data of resource can be supplied while SCM is searching for applica8ons for the CUser.
Billing Agent (BiA) works with Storage Cloud and SCM directly. When ST is generated, BiA
provides the service quote based on the pre-dened service descrip8on in SC.
24

!
Storage Cloud
Physical Resources Domain
25
ICMS
!
Comprised of 3 models working in the background
Cloud Service Provider Model

Cloud Service Model
Service Request Model
26
ICMS
!
The enterprise which provides CMnfServices is dened as a Service Provider.

!
!
!
Service Provider Model clearly describes and presents CMService, CProvider and CUsers requests,
SPM is an ecient data model.
Note that one company has a unique Enterprise En8ty, while its Service en88es.
27
ICMS / Proper8es
!
En8ty Enterprise outlines the proper8es of a CManufacturing via en88es

!
Provider_ID(unique), Company_Name, Provider_- Size, Provider_Capability,

Provider_Loca8on, Provider_Contact, Prior_Experience, Provider_Evalua8on and
Provider_Descrip8on.
28
ICMS / Proper8es
!
En8ty Prior_Experience records the service history of one SProvider which is visible to the Cloud
administrator and provider itself, but not en8rely to the users.
En8ty Provider_Evalua8on documents the feedback from these service consumers.
!
Based on these two en88es, the performance of the service experiences are modelled explicitly.
29
ICMS / Sub-en88es
!
En8ty Provider_Capabili8es describes the MCapability of a SProvider via sub-en88es

which are compliant with the aforemen8oned MCDM model. .
!
These en88es can be connected to a standardized data model directly, for example ISO14949-201
for machine tools, and ISO 10303-45 for engineering proper8es to set up explicit model.
30
Cloud Service Model
ICMS
!
As the second category of enterprise aoributes, the recogni8on of the specic CMService
is modeled via En8ty Cloud_Service_Specica8on and its en88es.
!
i.e., Service_ID, Service_Cost, Price, Time, Shipping_Price, Shipping_Time, Service_Status,

Service_Document, Data_Object, Pre_Condi8on, Availability, Resource, Quality_Evalua8on,
Technical_Support_Capability, Warran8es and Service_Descrip8on
31
Cloud Service Model
ICMS / Service Cost

!
En8ty Service_Cost documents the value of CMService in the monetary

form.
!
!
!
!
It provides an explicit model of the value that has been used to accomplish a
service object.
Service_Cost is only visible for SProviders to understand their MCapability
internally, and to make reasonable price for external CUsers.
Service_Cost is described with the help of en88es Cost_Per_Unit and
Cost_Quan8ty.
The Service_Cost model structure is inherited by four subtypes, which divides
the service cost into four categories, Cost_Material, Cost_Machining,
Cost_Labour, and Cost_Management.
32
Cloud Service Model
ICMS
!
En8ty Service_Status contains the informa8on about the running stages aSer a
CMService is launched.
!
Stages of implementa8on are described via en88es Ini8al, Ready, Running, Skipped,
Completed, Overload, Paused, and Cancelled.
33
Cloud Service Model
ICMS
!
En8ty ST_Document keeps the path and version of a ST le as above-men8oned.

!
When a CUser is working on a ST, all versions of the ST are recorded by this en8ty.
Thus, the service history is maintained.
34
Cloud Service Model
ICMS
!
En8ty Data_Object records the technical document(s) related to the CMService.

!
The op8onal aoribute of this en8ty is En8ty Project, which is compliant with the top
level of a neutral data format dened in ISO 10303.
35
Cloud Service Model
ICMS
!
36
En8ty Pre_Condi8on denes the requirements prior to the start of CMService.

!
Limita8ons or prepara8ons of the service input are recorded and published,

!
e.g., limits of size, material prepara8on, heat treatment and so forth.
Cloud Service Model
ICMS
!
En8ty Availability represents the availability and working condi8on of a CMService.

!
!
!
dynamically updated by CDA.

CUser is informed by the trust-worthy situa8on of availability without major delays.
CUsers are able to select the available CMService only, or queue in the list wai8ng for the preferred
package 8ll it is ready-to-be-used.
37
Cloud Service Model
ICMS
!
En8ty Resource denes the manufacturing resource that is required for a specic service.
!
!
Its structural aoributes (Hard_Resouce and SoS_Resource) are compliant with the resource
representa8on of En8ty Enterprise.
Thus, the resource specica8ons, from both service point of view and enterprise point of view, are
shaped and integrated in SCloud.
38
Cloud Service Model
ICMS
!
Quality evalua8on, Technical Support capability, warran8es also gured out,

in the Cloud service model.
!
All these components set up an explicit model.
39
ICMS / SRM Objec8ve

!
It explains the users query model components.

!
As a bridge between users original demand and CMService in the MCloud, it

provides a neutral and standardized methodology to document the query.
40
ICMS
!
En8ty Request_ID gives a unique serial number for a CUsers request.

!
!
!
When a new query case is created, a permanent Request_ID is assigned.

Users are able to resume, modify, and review the request case.
All the related Cloud behavior and history are traceable based on a Request_ID.
41
ICMS
!
En8ty Request_Status maintains the opera8onal condi8on of a request.

!
The variables of a process status are Created, Under_Evalua8on, Approved,

Running, Wai8ng, Terminated, and Finished.
42
ICMS
!
Op8onal En8ty Preferred_Resource keeps the users predilec8on of resource and facility,
!
for example specic machine tools, tes8ng method or design soSware.
The structure of this en8ty is compliant with the Hard_Resource and SoS_Resource en88es of
SProvider model aforemen8oned.
Thus, the users request can be directly connected to the MCapabili8es in the Cloud.
43
ICMS / SRM Benets

!
Thanks to the service request, CMService and SProvider models, the data is
modelled from the ini8aliza8on to implementa8on stage in the SCloud.
Informa8on packages can be submioed, retrieved, and maintained over the

Internet regardless the loca8ons of the central database and server.
For data storage queries, customers private data is not maintained in the
SCloud directly.
In the background, data centers are hosted by third par8es that are
integrated as SProviders in the MCloud.
!
Thus, the storage task is integrated as one of the CMServices in the virtualized
service pools.
44
ICMS Benets
!
45
Data Interoperability:
Issue
Benet
Applica8ons are provided

by mul8ple providers
using dierent
programmed languages
and document formats,
leading to a
heterogeneous data
environment.
Data loss and errors oSen
occur during format
conversions.
ICMS standardized (STEP-

based) communica8on
methodologies have
been deployed to
support collabora8ve
interac8ons in the Cloud
environment.
ICMS oers explicit
specica8ons of
manufacturing resources
in the MCloud.
ICMS Benets
!
46
Globaliza8on / Subcontrac8ng
Issue
Not exible environment
for manufacturing.
There are boundaries,
borders, obstacles.
Benet
ICMS provides a more
distributed and exible
environment which
knocks down the
boundaries between
organiza8ons/
enterprises.
Internet of Things,
manufacturing services/
capabili8es are
virtualized in the MCloud.
ICMS Benets
!
47
Customized Service & Specialized Demand
Issue
Benet
Customiza8on is
becoming more and
more important in
modern manufacturing,
especially for SMEs.
In a machine shop,
specic cuoer/ machine
tools are required for a
par8cular job.
Enhanced customiza8on
With SCM, it is easy to
locate required facili8es
in the resource pool.
Specialized objects are
achieved without
addi8onal investment
on costly facili8es and
exper8se.
ICMS Benets
!
48
Facility U8liza8on
Issue
Resource u8liza8on is not
achieved eec8vely.
Benet
Resource can be shared in a
Cloud.
Manufacturing resources/
capabili8es can be beoer
u8lized.
Produc8on tasks can be easily
balanced.
From the users perspec8ve,
CUsers are able to choose the
available qualied providers for
urgent jobs, or to wait for the
preferred facility in the queue.
the facility u8liza8on is
improved by widely shared
environment and reasonable
schedule.
ICMS Benets
!
49
Global Op8miza8on
Issue
Benet
Service solu8on is not considered

from global perspec8ve.
Since services are broadcasted in

the Cloud, service solu8on can
be improved and op8mized
based on the virtualized service
modules implemented in the
Cloud.
SCM predicts the service
performance features
beforehand, e.g., cost/8me
caused by preparing, machining,
transpor8ng and packing stages.
So much so, the global solu8on is
op8mized based on par8cular
factors or users preferences.
ICMS Benets
!
50
Cost-Saving
Issue / Opportunity
Manufacturing cost can be high.
Benet
Op8mized business solu8on is easily
found according to op8mized
results.
It is more likely to nd supplier with
beoer performance, cheaper labor,
higher produc8vity, and beoer
geographical loca8on.
As a consequence of 8me-cri8cal or
cost-cri8cal op8miza8on strategies,
the performance of the service
solu8on is predicted and improved
from a higher level and in a bigger
scope of Cloud.
Besides the cost of the service itself,
the cost of strategic decision is
reduced as well.
ICMS Benets
!
51
Beoer Enterprise Performance

Opportunity
Opportunity for beoer user
and enterprise performance
Benet
ICMS improves not only the
experience of the CUsers but
also the enterprises
performance as a CMService
provider.
The MCapabili8es are
accessible in the Cloud,
bringing more business
opportuni8es.
ICMS via SCM, a SProvider is
able to increase its
produc8on volume and react
rapidly to market changes.
CASE STUDIES
!
The rst case study shows the ability of integra8ng CMServices, and
The second case study demonstrates how a CManufacturing environment

can provide user with mul8ple op8ons and improve enterprise performance
at the same 8me.
52
1st Case Study

!
Customer launches a customer interface remotely.

!
log-in, see service history, status
It can be viewed within web browsers, e.g., e, Safari and Firefox
53
1st Case Study / Case

!
User requires a series of services including product design, simula8on, CNC milling,
precision welding and grinding.
CIA collects these data and transmits the data into a XML format to enable Internet
communica8ons
Note that the XML document which is transmioed from the client side is compliant
with the EXPRESS-G schemas but in a at data structure.
This means that the meta-model only keeps the informa8on of en8ty instance and
temporarily suspends aoributes and inheritance logics.
54
1st Case Study / Phases

!
The service is constructed by ve service phases that are mapped to the ve

stages of produc8on.
Mul8ple service providers are matched and stated by the SCM.
Due to the sequence of dierent routes, the service procedure is presented in

the owchart.
The service is illustrated as nodes and the transmirng methods as edges.
55
1st Case Study / Sequence

!
To op8mize the solu8ons and provide a customized result, SCM analyses the
feedback from the SCloud and evaluates the selec8ons based on the users
preference (e.g., cost-cri8cal and 8me-cri8cal rules).
SCM computes all possible paths through service nodes and their edges.
The sequen8al rela8onships between nodes can be represented in the table

!
!
Value 1 indicates there is an opera8onal sequence from node X to node Y.

The lowest cost combina8on is found and suggested to the user. Since there are 36
combina8ons in this case, itera8ve algorithm is deployed.
56
1st Case Study / Results & Evalua8on

!
Service 8me, shipping 8me and cost is formulized to have a standard.
The results are mapped into a general chart visible to the user via the User
Interface.
The op8mized solu8on is marked for the user. At this stage, the user is able
to follow the SCM recommenda8on or customize the selec8on.
57
2nd Case Study / Scope

!
The second case study concerns a manufacturing service provider named

BE, who has factories around the world.
An example product is selected to demonstrate how industrial service is

virtualized and implemented in the MCloud.
58
2nd Case Study / Case

!
!
!
!
ID T14859 Driver, is a ring-shape part with mul8ple holes at dierent angles.

An order of thirty parts are processed at BE Australia branch.
BE has sites in Australia (BEAU) and New Zealand (BENZ), both of which are
SProviders and capable of machining this part.
The MCapabili8es of the two sites are iden8ed.
59
2nd Case Study / Internal Usage

!
Due to the geographical and currency dierences, it is hard to evaluate

machining tasks in the two sites.
In this case study, ICMS serves as a community Cloud for the organiza8on.
BE plays a role of service provider and user at the same 8me.
It provides clear, explicit knowledge of the opera8onal processes.
From the providers perspec8ve, BE is able to understand its own services

and review/op8mize them as required.
As a CUser, the enterprise is able to choose the suitable service provider,

which can be a partner/contractor connected by the MCloud or the
enterprise itself.
60
Conclusion
!
A Cloud-based manufacturing system, called ICMS is proposed to achieve a

collabora8ve manufacturing environment.
!
it is possible to realize remote collabora8on, coordina8on, and interac8on

among par8cipants.
three-layer CManufacturing structure is proposed with a virtualiza8on

methodology.
61
Conclusion
!

!
3 models are proposed to structure Service provider, Service and service

requests.

Cloud Service Model
62
Conclusion
!

!
Two case studies evaluate the proposals.
63
Conclusion
!
ICMS connects distributed companies by provisioning their MCapabili8es as

CMServices.
With shared capaci8es, knowledge and competencies, it is possible to for a

business to take on more substan8al projects that are otherwise not
possible for one business to do.
64
Further Study
!
In a long term, more advanced manufacturing technologies can be brought

into the CManufacturing context to improve eciency, interoperability,
sustainability and exibility of a manufacturing business.
Addi8onal op8miza8on tools can be possibly adopted in the Cloud to

improve the global performance of ICMS.
65
66
Thanks for your aoen8on

Cloud Manufacturing Theory

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cloud Manufacturing Theory

Uploaded by

Copyright:

Available Formats

Contents

Service oriented interoperable cloud manufacturing is proposed (ICMS)

This study presents an interoperable manufacturing perspec8ve based on

Cloud manufacturing is a new concept extending and adop8ng the concept of

Cloud Compu8ng Structure

Key characteris8c of CCompu8ng is that of pay-as-you-go.

Customer-oriented manufacturing is a promising approach to improving the

Manufacturing Capability and Resources

Cloud Manufacturing Service

Self-contained, congurable and

CMService can be random,

Zhang et al. (39)

Manufacturing Capability and Resources

Zhang et al. (39)

ability of transforming one

Manufacturing Capability and Resources

domain-specic design knowl- edge, exper8se

speed and quality of output or service

Manufacturing Capability and Resources

Zhang et al. (39)

material and nonmaterial

Manufacturing Capability and Resources

Zhang et al. (39)

MCDM (Mcapability Descrip8on Model )

Resource descrip8on model (RDC)

MCDM includes the capability of both an individual enterprise and an alliance

domain-specic design knowl- edge,

speed and quality of output or service

experimenta8on knowledge and specialists

planning, organizing, sta- ing, leading and

ICMS / Need for ICMS

Why ICMS is proposed?

MCapabili8es and business opportuni8es can be integrated and broadcasted in a

More manufacturing objects can be achieved with minimum investment and

For industry, it oers new opportuni8es especially for SMEs.

ICMS / User Cloud Layer

At the UC Layer, the CMService consumer is divided into two categories:

Customer User (CU)

Enterprise User (EU)

ICMS / Customer Enterprise User Rela8ons

When customer comes to an enterprise that Enterprise itself cannot fulll.

Enterprise search for qualied providers in EIA (Enterprise interface agent )

ICMS / User Cloud Layer /

SCM searches for most convenient op8ons with help of AI

SCM have original and customized requirements from user

In manufacturing Cloud, each enterprise might give dierent services.

ICMS / Smart Cloud Manager

User assump8on is be to able to op8mize the solu8on based on his/her

ICMS / Work Flow

User recognizes needs

SCM Analyze and Searches

SCM transmit message to Cloud

ICMS / SCM (SMART CLOUD MANAGER)

The SCM module is constructed by intelligent agents.

Ar8cial Intelligent agent technology is capable of suppor8ng manufacturing

However, manufacturing decisions are dicult to make due to

complexity of manufacturing processes,

uncertainty of resources status.

Thus, to fully u8lize AI and human exper8se/knowledge, a decision-making model

ICMS / SCM (SMART CLOUD MANAGER)

The SCM module consists of

EIA : collects EUs requests

ICMS / Manufacturing Cloud