Framework of a Simulation Based Shop Floor Controller Using HLA Pramod Vijayakumar Systems and Industrial Engineering University of Arizona.

Slides:



Advertisements
Similar presentations
Distributed Scheduling in Supply Chain Management Emrah Zarifoğlu
Advertisements

Database Architectures and the Web
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 9 Distributed Systems Architectures Slide 1 1 Chapter 9 Distributed Systems Architectures.
Distributed Systems 1 Topics  What is a Distributed System?  Why Distributed Systems?  Examples of Distributed Systems  Distributed System Requirements.
Flexible Manufacturing Systems (FMS)
Objektorienteret Middleware Presentation 2: Distributed Systems – A brush up, and relations to Middleware, Heterogeneity & Transparency.
Object-Oriented Analysis and Design
Lecturer: Sebastian Coope Ashton Building, Room G.18 COMP 201 web-page: Lecture.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
Distributed Systems Architectures
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 11 Slide 1 Architectural Design.
Establishing the overall structure of a software system
Building Parallel Time-Constrained HLA Federates: A Case Study with the Parsec Parallel Simulation Language Winter Simulation Conference (WSC’98), Washington.
Integration of Applications MIS3502: Application Integration and Evaluation Paul Weinberg Adapted from material by Arnold Kurtz, David.
Architectural Design, Distributed Systems Architectures
EMBEDDED SOFTWARE Team victorious Team Victorious.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 11 Slide 1 Architectural Design.
Manufacturing system Ali Vatankhah.
Manufacturing Control system. Manufacturing Control - Managing and controlling the physical activities in the factory aiming to execute the manufacturing.
Applying Distributed Systems concepts to SCADA By Padmanabha Kamath.
Client/Server Architectures
Chapter 7: Architecture Design Omar Meqdadi SE 273 Lecture 7 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
ASP.NET  ASP.NET is a web development platform, which provides a programming model, a comprehensive software infrastructure and various services required.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 12 Slide 1 Distributed Systems Architectures.
Chapter 4 System Models A description of the various models that can be used to specify software systems.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Chapter 10 Architectural Design.
Architectural Design, Distributed Systems Architectures
IMPROUVEMENT OF COMPUTER NETWORKS SECURITY BY USING FAULT TOLERANT CLUSTERS Prof. S ERB AUREL Ph. D. Prof. PATRICIU VICTOR-VALERIU Ph. D. Military Technical.
Architectural Design To explain the advantages and disadvantages of different distributed systems architectures To discuss client-server and distributed.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Architectural Design l Establishing the overall structure of a software system.
High Level Architecture Overview and Rules Thanks to: Dr. Judith Dahmann, and others from: Defense Modeling and Simulation Office phone: (703)
Architectural Design lecture 10. Topics covered Architectural design decisions System organisation Control styles Reference architectures.
PROSA, a reference architecture for holonic manufacturing systems dr. ir. Jo Wyns KULeuven / RealSoftware PMA KULeuven
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Architectural Design l Establishing the overall structure of a software system.
Architectural Design 10/24/2015ICS 413 – Software Engineering1.
Architectural Design Yonsei University 2 nd Semester, 2014 Sanghyun Park.
The High Level Architecture Introduction. Outline High Level Architecture (HLA): Background Rules Interface Specification –Overview –Class Based Subscription.
Advanced Computer Networks Topic 2: Characterization of Distributed Systems.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 11 Slide 1 Architectural Design.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 13. Review Shared Data Software Architectures – Black board Style architecture.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 11 Slide 1 Architectural Design.
Chapter 7: Architectural Design Chapter 11 in textbook 1.
CSC480 Software Engineering Lecture 10 September 25, 2002.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
©Ian Sommerville, Robin Abraham 2004CS 361, Summer 2004 Slide 1 Architectural Design.
© Chinese University, CSE Dept. Distributed Systems / Distributed Systems Topic 1: Characterization of Distributed & Mobile Systems Dr. Michael R.
Service Oriented Architecture + SOAP -Robin John.
Copyright © 2002 OSI Software, Inc. All rights reserved. PI Application Framework Example Applying the Application Framework.
IE550 2/18/2016 Design for Production in Existing Facilities (DPEF) Richard A. Wysk The Pennsylvania State University IE550 Manufacturing Systems.
CSC 480 Software Engineering Lecture 17 Nov 4, 2002.
Slide 1 Chapter 8 Architectural Design. Slide 2 Topics covered l System structuring l Control models l Modular decomposition l Domain-specific architectures.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Chapter 5:Architectural Design l Establishing the overall structure of a software.
Distributed Systems Architectures Chapter 12. Objectives  To explain the advantages and disadvantages of different distributed systems architectures.
Distributed Systems Architectures. Topics covered l Client-server architectures l Distributed object architectures l Inter-organisational computing.
7. Modular and structured design
Software architecture
Cmpe 589 Spring 2006.
Software Engineering Architectural Design Chapter 6 Dr.Doaa Sami
CSC 480 Software Engineering
Princess Nourah bint Abdulrahman University
Software Architecture
Architectural Design.
Software Engineering with Reusable Components
Chapter 7 Software Engineering.
King Saud University College of Engineering IE – 462: “Industrial Information Systems” Fall – 2018 (1st Sem H) Introduction (Chapter 1) part.
Design.
Distributed Systems and Concurrency: Distributed Systems
Presentation transcript:

Framework of a Simulation Based Shop Floor Controller Using HLA Pramod Vijayakumar Systems and Industrial Engineering University of Arizona

Topics Covered Control Architecture of Mfg Systems Simulation based control Integration of simulations Proposed system Work Ahead

Control Architecture - Centralized All planning and information processing performed at a single Location The Advantages are Less no of Computers Global decisions are easy to make Works well with a product mix which is fairly stable Disadvantages Central computer needs to have high computing power (Mainframe) Failure of the central controller paralyses the system Low fault tolerance Reconfigurations difficult

Hierarchical Top down approach for passing control Status is send upward and decisions are send downward Advantages Modularity Modularity Computation is more distributed Planned Extension possible Disadvantages Rigid Master Slave Relationships Low fault tolerance Modification possible is limited

Heterarchical It has a flat structure characterized by peer communication High Level of autonomy and no master slave relationships Advantages High levels of distribution of control Easy to make modifications High fault tolerance Computers with significantly less processing powers Disadvantages High number of conflicts Behaviour could be unpredictable

Implementation philosophies AGENTS Software that is AutonomousAdaptive Goal oriented HOLONS similar to agents Holon could be part of another holon or many holons More cooperation SIMULATION Used for modeling and analysis Representation of the real system Could be used in real time to control a system

Roles of Simulation Simulation Dynamic Scheduler Status Update Instructions Decision Maker Mfg System Present Strategy And status Better Strategy

Proposed Change

Advantages Individual Models means better analysis and debugging Models are reusable More distributed control Easy to extend the model Easy To make Modifications to the model

Integrating Simulations Different vendors different representations Coordination with respect to time Standard Method for exchanging information

High Level Architecture ( HLA) The efforts were initiated by DMSO An Architecture to allow dissimilar simulations to talk The 3 main components are Rules –Regarding the federate and federation behaviour Interface Specification –Regarding the interactions between the federates and RTI Object Model Template –Data model for the Federation (FOM) and Federate (SOM )

Run Time Infrastructure Acts as the mediator between all the simulations 6 Basic Functions Federation Management –Creating, Joining, Resigning and Destroying federates Declaration Management –Publishing and Subscribing data Object Management –Attribute updates and interactions Ownership management –Transfer of ownership of objects and attributes Time management –Coordinating time of federates and managing time-stamped delivery of events Data Distribution management –Manages object instances

Process Planning AND/OR Graphs Precedence Relations exhibited Alternative ways of machining a single part – AND Node Redundancies can be built into the model – OR Node Each Node represents an operation to be carried out. The graph determination is an offline activity Node contains –NC Filename –Tools Required –Fixtures –Processing Machine M1SA M3 JAM4 M2 NC Filename, Tools, Fixtures, Machine Names

Proposed Architecture MH MP RMHMR Guide MT Manager MT Visualization Status

Proposed System Characteristics Loose Master Slave Relationships Peer to peer communication Extendable architecture Modular design Good Fault Tolerance Reusable Code Manufacturing System Raw Part AND/OR Graph Finished Part

Federates in the system Equipment Material Processor Material Transporter Material Handler –Controls the equipment –Keeps check of the tools and fixtures –Monitors the machine and updates status –Interacts with the Resolver or Managers for part Resolver –Resolves the AND/OR Nodes –One resolver for each cell –Interacts with the Material Processor for the part –Communicates with peer resolvers in case of “foreign machines” in the cell

Federates in the system Guide –Has a supervisory role –Make the initial assignment of ownership and initial AND/OR resolution –Comes into play in the case of “foreign machines” MT Manager –Interacts with the Material Transporter and Material Processor MH Manager –Interacts with the Material Handler and Material Processor Visualization Federate –Gives a Current status summary of the entire system

Scheduling and Operation Resolver MP1 MP3 Do you want to process the part MP2 Do you want to process the part Yes No Yes You Win

Work Ahead Algorithms for the different federates –Roughly determined as SPT for MP Federate Due Date of the part for Resolver Transportation time for MT Manager Handling time for MH Manager Message formats for communication Structure of Databases

Summary A modular approach suggested to simulation based control of manufacturing systems An easily extendable and modifiable architecture Online Collection of data for analysis possible