IMS Mission Project: DMS Adapter Status

1
IMS Mission ProjectDMS Adapter Status

• Frank Riddick
• Manufacturing Simulation and Visualization Group
• Manufacturing Systems Integration Division
• National Institute of Standards and Technology

2
Overview
IMS Mission Project Distributed Manufacturing
Simulation Brief MISSION Architecture
Overview DMS Adapter Interface Overview Motivation
for the DMS Adapter Use of XML, XSL, and
COM Distributed Supply Chain Simulation
Scenario Questions
3
Modelling and Simulation Environments for Design
Planning and Operation of Globally Distributed
Enterprises (MISSION)

• The goal of MISSION is to integrate and utilize
  new,knowledge-aware technologies of distributed
  persistent data management, as well as
  conventional methods and tools, in various
  enterprise domains, to meet the needs of globally
  distributed enterprise modelling and simulation.
• Mission Web Site http//www-plt.ipk.fhg.de/mis
  sion
• Intelligent Manufacturing Systems (IMS) is an
  industry-led, international research
  development program established in 1995 to
  develop the next generation of manufacturing and
  processing technologies.
• IMS Web Site http//www.ims.org

4
What is included within the scope of distributed
manufacturing simulation?

• 1) Multiple simulation software processes that
  are independently executing and interacting with
  each other. Software may have been developed by
  different software vendors. Modules may run on
  different computer systems in geographically
  dispersed locations.
• 2) A distributed computing environment where
  other non-simulation manufacturing software
  applications are running and interacting with one
  or more simulation systems. Engineering systems
  may interact with simulation systems through
  service requests.
• 3) A distributed manufacturing simulation system
  comprised of multiple functional modules that
  together form a system, such as model builders,
  simulation engines, display systems, analysis
  tools, etc.

5
Why do we need to build distributed manufacturing
simulation systems?

• Model supply chains across multiple organizations
  where some of the information about the inner
  workings of each organization may be hidden from
  supply chain members
• Model multiple levels of manufacturing systems
  where lower level simulations generate
  information that feeds into higher level models
• Multiple types of systems in a single factory
  with different simulation requirements such that
  an individual simulation vendors product does
  not provide the capabilities to model all
  capabilities of interest

6
High Level View of the Mission Architecture
7
Distributed Manufacturing Data Repository
8
Design, Engineering, Production Planning, and
Simulation Model Development Environment
9
Distribute Manufacturing Simulation
ExecutionArchitecture
10
Federation Manager

• Federation Manager
• Facilitates startup synchronization,
  initialization data distribution, federation
  health monitoring, statistical data collection,
  and federation debugging.

11
Goals For the Adapter

• Simplify the protocol necessary for legacy
  simulations to be integrated
• Maintain storage for object instances, both local
  and remote
• Provide the capability to use the same adapter in
  multiple federations without recompilation.
• Support Adapter parameterization with
  externally defined data
• Perform housekeeping tasks without the
  intervention of the legacy simulation
• Work cooperatively with the Federation Manager to
  manage time advancement and synchronization

12
(No Transcript)
13
Adapter MethodsTime advancement and Simulation
Execution

• Initialize
• Terminate
• AdvanceSimulation
• SimulationAdvanceCompleted
• GetExecutionState
• GetSimulationTime
• GetProperty
• SetProperty

14
Adapter MethodsMessage Management

• GetNextMessage
• AllMessagesReceived
• SendMessage

15
Adapter MethodsObject Management

• CreateObject
• UpdateObject
• DeleteObject
• GetObject
• GetObjectValue
• SeizeObject
• ReleaseObject
• SelectObjects

16
Additional Methods under Consideration
17
Typical Simulation Setup

• Monolithic
• Inadequate integration mechanisms
• Proprietary model development language
• Closed persistent storage mechanisms

18
Integration using the HLA

• Complex RTI interface
• FOM approach brittle w.r.t. simulation model
  evolution
• Implicit invocation architecture is unusual
  w.r.t. simulation processing model
• Adaptation code difficult to write and usually
  not reusable

19
Integration using the Adapter

• Simpler integration interface
• Less Adaptation code
• Less complex adaptation code
• Generic Federate Ambassador implementation

• Object instances Storage
• Information modelling decisions decoupled from
  integration mechanism development

20
Microsoft COM- Component Object Model

• Somewhat Language Neutral
• Uses IDL to define the interface to an object
• Claimed to platform independent(DCOM)
• Should be straight forward to port to platform
  independent technologies (Corba, Java RMI) if
  necessary
• Several simulation vendors claim to support COM
  integration

21
XMLThe eXtensible Markup Language

• W3C Standard
• Facilitates semantic description vs. the display
  oriented description capabilities provided by
  HTML
• In wide use in a multitude of domains
• Provides a good mechanism for machine and human
  interpretation in one format

22
Extensible Stylesheet Language (XSL)

• A W3C standard
• XSL is a language for expressing stylesheets. It
  consists of two parts
• 1.a language for transforming XML documents, and
• 2.an XML vocabulary for specifying formatting
  semantics.Provides for the identification,
  selection, modification, and translation of XML
  files
• Facilitates searching and updating specific
  information in an XML file

23
MISSION Supply Chain
24
Example Model of Information Flow in a Supply
Chain