PROSA, a reference architecture for holonic manufacturing systems dr. ir. Jo Wyns KULeuven / RealSoftware PMA KULeuven

Slides:



Advertisements
Similar presentations
Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
Advertisements

©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 12Slide 1 Software Design l Objectives To explain how a software design may be represented.
Some questions o What are the appropriate control philosophies for Complex Manufacturing systems? Why????Holonic Manufacturing system o Is Object -Oriented.
© Chinese University, CSE Dept. Software Engineering / Software Engineering Topic 1: Software Engineering: A Preview Your Name: ____________________.
Software Process Models
Design Concepts and Principles
University of Minho School of Engineering Department of Production and Systems Uma Escola a Reinventar o Futuro – Semana da Escola de Engenharia - 24 a.
TRANSIMS Research and Deployment Project TRACC TSM Staff Dr. Vadim Sokolov Dr. Joshua Auld Dr. Kuilin Zhang Mr. Michael Hope.
0 General information Rate of acceptance 37% Papers from 15 Countries and 5 Geographical Areas –North America 5 –South America 2 –Europe 20 –Asia 2 –Australia.
Software Engineering COMP 201
Introduction To System Analysis and Design
Software Reuse Building software from reusable components Objectives
1 IBM SanFrancisco Product Evaluation Negotiated Option Presentation By Les Beckford May 2001.
1 SOFTWARE LIFE-CYCLES Beyond the Waterfall. 2 Requirements System Design Detailed Design Implementation Installation & Testing Maintenance The WATERFALL.
1 SYSTEM and MODULE DESIGN Elements and Definitions.
Design Patterns CS is not simply about programming
Intelligent Agent Systems. Artificial Intelligence Systems that think like humans Systems that think rationally Systems that act like humans Systems that.
Architectural Design Principles. Outline  Architectural level of design The design of the system in terms of components and connectors and their arrangements.
Eindhoven Universityof Technology The Netherlands.
Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display. Design Patterns.
Reuse Activities Selecting Design Patterns and Components
Architectural Design Establishing the overall structure of a software system Objectives To introduce architectural design and to discuss its importance.
UML and Object Oriented Concepts
Manufacturing Control system. Manufacturing Control - Managing and controlling the physical activities in the factory aiming to execute the manufacturing.
Introduction To System Analysis and design
OO Frameworks Department of Computer Science Kent State University.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 18 Slide 1 Software Reuse.
Software Engineering Muhammad Fahad Khan
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
1 Physical Ensemble Engineering Christof, Heinz, Insup, Seth, Teruo.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 12 Slide 1 Distributed Systems Architectures.
Object-oriented Software Engineering with Reuse Contracts Koen De Hondt, Carine Lucas, Kim Mens, Tom Mens, Patrick Steyaert, Roel Wuyts Programming Technology.
Design Patterns OOD. Course topics Design Principles UML –Class Diagrams –Sequence Diagrams Design Patterns C#,.NET (all the course examples) Design Principles.
1 CS 456 Software Engineering. 2 Contents 3 Chapter 1: Introduction.
European Network of Excellence in AI Planning Intelligent Planning & Scheduling An Innovative Software Technology Susanne Biundo.
Lecture 9: Chapter 9 Architectural Design
Introduction To System Analysis and Design
SOFTWARE DESIGN.
Guided Notes Ch. 9 ADT and Modules Ch. 10 Object-Oriented Programming PHP support for OOP and Assignment 4 Term project proposal C++ and Java Designer.
Architectural Design lecture 10. Topics covered Architectural design decisions System organisation Control styles Reference architectures.
Model Driven Development An introduction. Overview Using Models Using Models in Software Feasibility of MDA MDA Technologies The Unified Modeling Language.
Chapter 8 Object Design Reuse and Patterns. Object Design Object design is the process of adding details to the requirements analysis and making implementation.
Dale Roberts Object Oriented Programming using Java - Introduction Dale Roberts, Lecturer Computer Science, IUPUI Department.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 18 Slide 1 Software Reuse.
CSC480 Software Engineering Lecture 10 September 25, 2002.
Framework of a Simulation Based Shop Floor Controller Using HLA Pramod Vijayakumar Systems and Industrial Engineering University of Arizona.
Profile Organisation & Management (O&M). Types of students Researchers: are curious Designers: are creative and constructive Managers: deal with processes.
Investigation of Autonomy and Coordination Xiaobing Zhao Computer Integrated Manufacturing (CIM) Lab Systems and Industrial Engineering The University.
Testing OO software. State Based Testing State machine: implementation-independent specification (model) of the dynamic behaviour of the system State:
CSE 303 – Software Design and Architecture
The 5th International Conference on Internet of Things 2015 Coex, Soeul, S. Korea Oct , 2015 Internet of Processes Vladimír Kebo, Center of Advanced.
Banaras Hindu University. A Course on Software Reuse by Design Patterns and Frameworks.
Lesson 1 1 LESSON 1 l Background information l Introduction to Java Introduction and a Taste of Java.
February 19, February 19, 2016February 19, 2016February 19, 2016 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific.
From Use Cases to Implementation 1. Structural and Behavioral Aspects of Collaborations  Two aspects of Collaborations Structural – specifies the static.
ETICS An Environment for Distributed Software Development in Aerospace Applications SpaceTransfer09 Hannover Messe, April 2009.
Software Architecture Architecture represents different things from use cases –Use cases deal primarily with functional properties –Architecture deals.
A MULTI-AGENT RFID-ENABLED DISTRIBUTED CONTROL SYSTEM FOR A FLEXIBLE MANUFACTURING SHOP Present by : Ali Vatankhah.
From Use Cases to Implementation 1. Mapping Requirements Directly to Design and Code  For many, if not most, of our requirements it is relatively easy.
Chapter 9 Architectural Design. Why Architecture? The architecture is not the operational software. Rather, it is a representation that enables a software.
Design Patterns: MORE Examples
Definition CASE tools are software systems that are intended to provide automated support for routine activities in the software process such as editing.
Self Healing and Dynamic Construction Framework:
Software Reuse Objectives
CSSSPEC6 SOFTWARE DEVELOPMENT WITH QUALITY ASSURANCE
Design for Ease in Contraction and Extension
Planning and Scheduling in Manufacturing and Services
Presented By: Darlene Banta
From Use Cases to Implementation
Presentation transcript:

PROSA, a reference architecture for holonic manufacturing systems dr. ir. Jo Wyns KULeuven / RealSoftware PMA KULeuven the key to support evolution and reconfiguration

Manufacturing control logistical planning technological planning, late design decisions resource allocation downloading of NC- programs tracking of materials, tools, people,... etc. => but broad in space and time

Problem statement Disturbances –machine break-down –rush order –missing tools –missing materials –absenteism –etc. On-line manufacturing control algorithm Changes –new technology –new markets –new products –new organisational structures –etc. Manufacturing control system architecture

Reference architecture Manufacturing control system System architecture Reference architecture HW/SW, implementation blueprint, components, interactions style, types of components and interactions executeabstraction, communication, indicate vital components reduce development time, increase quality, unif. terminology buildingplans, sketches, specifications building style, construction elements,... What Goal Analogy

Requirements low price (build & maintain) predictable operational performance broad working range (flexible, robust, availability,...) Manufacturing control system System architecture Reference architecture reuse of components customised logistical and technological solutions extendable & adaptable decoupling generic applicability self-similarity

Evaluation of reference architectures Direct comparison hierarchical and heterarchical architectures Objective evaluation –compose list of requirements –find metrics Critique of end-users, developers, researchers,... REMARK: Paradigm dependency

Hierarchical control (ex.)

Heterarchical control (ex.)

Hierarchical vs. heterarchical control Every child node has only 1 parent. Master - Slave Low Adaptability Low support for Evolution => for large systems => not for dynamic systems (changes/disturbances) Distributed No supervisory control Negociation No global optimisation => for homogeneous systems => not for large systems

Lessons learned New approach shall provide –Dynamic structure –Decoupling of system structure from control algorithm –Reactive scheduling and process planning –Generic applicability

Holonic manufacturing systems (HMS) Manufacturing holon Holon whole, autonomy part, co-operation Stability decoupling self-similar

PROSA: basic holons

Basic holons

Aggregation hiding details in aggregated structures open-ended at top and bottom multiple aggregations (not tree-shaped) not static, may change dynamically resource, product, order aggregations

Aggregation

Specialisation Different types of resources: –Processing resources, workstations, –Transport resources, transport system –... Different types of orders and products: –Stock orders, customer orders –Different product families

Specialisation

Staff holons Basic holons + aggregation + specialisation –only heterarchical control (aggregation contains no control functionality) –distributed system But... –centralised problem solving is sometimes easier (e.g. scheduling) –hierarchical structures in factories

Staff holons Expert gives advise to the basic holons Holonisch manufacturing system –distributed system: robust and adaptable –ability for centralised functions Behaviour: hierarchical, heterarchical, and mengvormen zijn mogelijk

Staff holons (3)

Flexible assembly system Apply PROSA to real machines (robots & PLC) Switch between real machines and simulation (virtual factory) Logistical decisions –replaceable dynamic market mechanism –reactive centralised scheduler and schedule execution

Flexible assembly system

Example

Horizontal self-similarity Specialisation uses inheritance (OO) All kind of resource holons share common interface and behaviour; idem for order holons and product holons => Special cases/types can be handles similar to nominal ones e.g. rush order; first-of order; high volume vs. high quality product;

Vertical self-similarity Holarchy is a resource holon on itself; resource holon can internally be a holarchy Homogeneity in internal functioning of holarchies Resource holon is independent of holarchy to which it belongs e.g. belong to multiple holarchies at the same time (human)

Self-similarity (3)

Conclusion PROSA: Product-Resource-Order-Staff Architecture –necessary basic holons –optional staff holons –generalisation of hierarchical and heterarchical architectures –software framework

Conclusion Evolution & reconfiguration –decoupling of control algorithm from system architecture –decoupling of logistical and technological aspects –self-similarity

New opportunities On-line technological planning and design decisions Hybrid control algorithms Self-generating manufacturing control systems

More details on PROSA Van Brussel, H., J. Wyns, P. Valckenaers, L. Bongaerts, P. Peeters, (1998) Reference Architecture for Holonic Manufacturing Systems: PROSA, Computers In Industry, Special Issue on Intelligent Manufacturing Systems, Vol. 37, No. 3, pp. 255 – 276. Wyns, J. (1999), Reference architecture for holonic manufacturing systems - The key to support evolution and reconfiguration, Ph.D. thesis, ISBN , K.U.Leuven.

Software framework Translate reference architecture into software Framework –co-operating abstract classes –basis for implementing a specific manufacturing control system Add classes to support implementation

Integration with scheduling Planning = advise: –what, when, how? –not: invent standard for planning advise –but: design pattern for integration Solution: multiple decision taking algorithms + one selection algorithm in order holons

Integration with scheduling

Man-machine interface