Shop Floor Information Management

&
SOA

Ankita Raj06502901
Kritika Singh 09609097 
Vini Goel  09609062 
 Intelligent Manufacturing
Information Systems


W AS . .
Heterogeneity of data structures
.
and information
 systems - Problem


Existing solutions led to static

process logic coding within
monolithic Manufacturing
Execution System (MES) utilizing
2
elaborate
Shop Floor interfaces
Information Management & SOA for 09/28/10

rudimentary integration
LA C K
ED

Flexib ility S ca la b ility

3 Shop Floor Information Management & SOA 09/28/10

 
O W . . .


4 Shop Floor Information Management & SOA 09/28/10

  Sub-system vendors at control level
Similar service orientation as for ERP
U M P T IO N S level modules


More control transfer



Programmable Logic Controls or open

PC terminals


 WHY?
Knowledge is concentrated
Shortest Reaction Times


5 Shop Floor Information Management & SOA 09/28/10

 Machine Vendors
Services:


 Online maintenance
 Education support
 Planning
 Optimization of production and logistics systems
or other e-Industrial/tele-services.
 Recent development RFID



Vertical Integration from ERP to Machine level


6 Shop Floor Information Management & SOA 09/28/10

 Current Architecture Proposals
 EA (Enterprise Architecture)
 PERA (Purdue Enterprise Reference Architecture)
 GERAM (Generalized Enterprise Reference Architecture
and Methodology)
 CIMOSA (Computer Integrated Manufacturing Open
System Architecture)
 GRAI Integrated Method
 INTEROP (Interoperability Research for Networked
Enterprise Applications and Software)
 ATHENA (Advanced Technologies for interoperability of
Heterogeneous Enterprise Networks and their
Applications)


ü Modeling Standardization
7 ü Modularization
Shop Floor Information Management & SOA 09/28/10
ü Abstraction
 Shop Floor: Model Driven
Service
Architecture

 Methodological considerations started with the Domain
dimensions like Business, Architecture and Application
which :
 Was a Platform Specific instead of being a Platform
Independent Model
 Lacked Business Readability


 Business, Architecture and Application were replaced by

classical hierarchy levels:
• Enterprise Level
• Shop Floor Control
Level
• Shop Floor Field Level

8 Shop Floor Information Management & SOA

 09/28/10
 Methodology : Shop Floor
Domain

9 Shop Floor Information Management & SOA 09/28/10

 PSFM: Particular Shop
Floor Model
 PSFM at the end of the Design phase can exist at two
PPO RTS abstraction levels :
• Platform/computer independent
• Platform specific, constitutes the ESFM
(Executable Shop Floor Model) which
should be fully aligned with the
assets either already existing or
under construction.


 PSFM :
• Supports long term platform,
infrastructure and service provider
decisions through as-is and to-be
comparisons
• This high level model has to interact
10 Shop Floor Information Managementwith
& SOAthe ESFM concerning process
09/28/10
definition
 SFTB: Shop Floor Tool Box
 SFTB is an ANSI/ISA 95 compliant tool box which enables
fast and standardized
modelling of particular shop floor scenarios.
 Consists of an abstract service repository of basic and
complex services (what dimension), concrete service
providers(who dimension), binding mechanisms and
data entities (with dimension).
 Achieved support, focus on functionality and connectivity
of the system as a whole


 Knowledge gained from the PSFM and ESFM

should be fed back into the Shop Floor Tool-Box,
which more and more becomes a valuable
knowledge base.

11 Shop Floor Information Management & SOA 09/28/10
 MDSA Implementation

D E T A IL E D P R O D U C T IO N S C H E D U L IN G
R E A L IZ A T IO N M O D E L

12 Shop Floor Information Management & SOA 09/28/10

 RELATIONSHIP BETWEEN SERVICE
PARTITIONS

13 Shop Floor Information Management & SOA 09/28/10

 S ta tic stru ctu re o f th e
S ch e d u le N e w O rd e rs
C o lla b o ra tio n

14 Shop Floor Information Management & SOA 09/28/10

 Hence …
 A SOA is flexible enough to realize decentralized control
structures where appropriate and to integrate a broad
range of service providers in a loosely coupled way
 With the proposed MDSA methodology two gaps could be
closed, resulting in business and IT alignment
• Gap to the implementation layer
• Gap to the business layer
 Outcome as ANSI/ISA 95 compliant model-driven
methodology for manufacturing operations
management which is
• feasible
• user friendly of the proposed
methodology
•
 The methodology is flexible enough to embed given
shop floor scenarios and components smoothly into
the framework with the help of predefined modeling
15 constructs.
Shop Floor Information Management & SOA 09/28/10

Thank you !!