190 likes | 207 Views
Distributed Simulation -- An Enabling Technology for the Evaluation of Supply Chains -- Supported by NIST. Jeyendran Venkateswaran, Mohammed Jafferali, Young-Jun Son Systems and Industrial Engineering The University of Arizona (520) 626-9530, son@sie.arizona.edu. Outline of Presentation.
E N D
Distributed Simulation -- An Enabling Technology for the Evaluation of Supply Chains-- Supported by NIST Jeyendran Venkateswaran, Mohammed Jafferali, Young-Jun Son Systems and Industrial Engineering The University of Arizona (520) 626-9530, son@sie.arizona.edu
Outline of Presentation • Overview of manufacturing simulations • Architecture of distributed simulation • Model supply chain interaction • Demonstration of integration of multiple commercial simulation software (Arena™ and ProModel ™)
Spindle rotation, X,Y,Z movement of tool in machine Somewhat continuous processes Different Types of Manufacturing Simulations Enterprise Shop Equipment Real World
Different Types of Manufacturing Simulations Enterprise • High level tasks such as • pick, put, cycle start, etc • Somewhat discrete processes Shop Equipment Real World
Different Types of Manufacturing Simulations • Interface with other enterprise • Focus of this presentation Enterprise Shop Interface/Interaction Equipment Real World
Shop Level Simulation Equipment Simulation Task Task Input Queue Output Queue Big Executor (Shop Level) Eshed IBM ABB AS/RS Cartrac Prolight Fadal robot robot robot Real World or Equipment level simulation Shop Floor Control Simulation
Shop Level Simulation Equipment Simulation Represented by Represented by Represented by Task Task Supplier model in ARENA (federate) Manufacturing in PROMODEL (federate) Distributor in AUTOMOD (federate) Input Queue Output Queue Common Data Repository among Collaborators NIST Adapter Common Interface Common Interface Big Executor (Shop Level) XML documents, Objects & messages XML documents, Objects & messages XML documents, Objects & messages Eshed NETWORK (LAN or INTERNET) IBM ABB AS/RS Cartrac Prolight Fadal XML documents, Objects & messages robot robot robot Run Time Infrastructure (RTI) Real World or Equipment level simulation Evaluation of B2B Collaboration
Requirements to enable Simulation Integration • Given multiple simulation models • Requirements (mechanisms) for the integration of multiple simulation models • Time coordination (current simulation time should be the same) • Interaction (coordination) or communication • Objects (material and information) • Messaging (interactions) • High Level Architecture (HLA) and Run-Time Infrastructure will provide a basis for simulation systems integration • NIST Adapter (common interface)
HLA/RTI to be used directly in Manufacturing Domain • Is complex • Requires too much custom coding from prominent simulation applications in the manufacturing domain • So, what about a reusable, easy-to-use, and common interface => NIST Adapter
Time Management (1) • Tnow: current time in a legacy simulation (federate) • When stand-alone mode • Tnow is updated based on original event calendar • In federation (distributed simulation) • Tnow is constrained by Tnows of other simulations through C and Si • C: current time in distributed simulation (federation) • Si: simulation step size of federate i • User variable • Smaller, more tightly coordinated among federates
How do we implement the interactionand time management? • Each simulation member can run as stand alone
How do we model this interaction? • Each simulation member can run as stand alone
Prototype Virtual Supply Chain Logistics & Administration Assembly Plant Supplier A Outgoing product storage Supplier B Manufacturing Incoming parts storage LEGEND Material flow Warehouse Distributor Transportation system Information flow is opposite direction from the material flow Retailer
Functional Specification using IDEF Control Input Output Function Mechanism
Decomposed Functions Decomposed Functions
Modeling behavior among members using FSA open_transaction_ok_sa open_transaction_as 0 1 2 I O order_as$12345$ I generate_transport_order transport_order_st 3 4 5 T O load_parts_ts I remove_entity load_parts_ok_st 6 7 8 T O close_transaction_as close_transaction_ok_sa 10 9 I O
Implementation • 4 Members have been modeled in Arena and ProModel (AutoMod will be included) • Adapter (NIST) has been implemented in COM objects • Both Arena and ProModel provides a built-in environment to use COM objects as part of their simulation software • Demonstration
What’s next? • Case studies • Evaluation scenarios • Evaluation of virtual enterprises (lead-time, cost, quality) • Develop a generic broker • Information modeling of manufacturing objects • Generic input/output interface from users • Embedding/adding more scientific algorithms • Interaction among members (Petri-net, agent technology, etc) • Decision-making algorithms