PERA Methodology.

Slides:



Advertisements
Similar presentations
Course: e-Governance Project Lifecycle Day 1
Advertisements

Multimedia Specification Design and Production 2013 / Semester 1 / week 7 Lecturer: Dr. Nikos Gazepidis
CS487 Software Engineering Omar Aldawud
Ch 3 System Development Environment
1 Prescriptive Process Models. 2 Prescriptive Models Prescriptive process models advocate an orderly approach to software engineering Prescriptive process.
Sharif University of Technology Session # 3.  Contents  Systems Analysis and Design Sharif University of Technology MIS (Management Information System),
Reference Architecture for Enterprise Integration CIMOSA GRAI/GIM PERA Dima Nazzal.
1 Introduction to System Engineering G. Nacouzi ME 155B.
Nov. 14, 2007 Systems Engineering ä System ä A set or arrangement of things so related as to form a unity or organic whole. ä A set of facts, principles,
Iterative development and The Unified process
Development Processes and Product Planning
TECH 101 Product Design and Manufacturing. TECH 1012 System Life-Cycle Engineering 2 Major phases in almost all products and in many cases services –Acquisition.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
System Engineering Instructor: Dr. Jerry Gao. System Engineering Jerry Gao, Ph.D. Jan System Engineering Hierarchy - System Modeling - Information.
Enterprise Architecture
TDT4252 Modelling of Information Systems Advanced Course
T5: Enterprise Architecture and Methodology Fall 2013 Chin-Sheng Chen Florida International University.
The Database Development Process
CSI315 Web Applications and Technology Overview of Systems Development (342)
EENG 1920 Chapter 1 The Engineering Design Process 1.
Industrial Engineering Roles In Industry
1M.Sc.(I.T.), VNSGU, Surat. Structured Analysis Focuses on what system or application is required to do. It does not state how the system should be implement.
Lecture 4 Title: The Scope Management Plan
Chapter 10 Information Systems Analysis and Design
Odyssey A Reuse Environment based on Domain Models Prepared By: Mahmud Gabareen Eliad Cohen.
Prepared by the (Institute of Industrial Engineers – Industry Advisory Board)
MODA-TEL An IST project on Model Driven Architectures for Telecommunications System Development and Operation.
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
1 CIM OSA CIMOSA Computer Integrated Manufacturing Open System Architecture 1 David CHEN IMS-LAPS, University Bordeaux 1.
Enterprise Systems Architectures EGN 5621 Enterprise Systems Collaboration (Professional MSEM) Fall, 2012.
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
Chapter 15 Introduction to Systems Development. Learning Objectives Learn how information systems are developed Understand importance of managing SD process.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 systems analysis 1 what is systems analysis? preparation of the system’s requirements/definition,
SPE-RFI-R : FEB.1999 : NUL-ITD-Iwata 2-01 Needs for Software Development Model Hiromichi Iwata Information Technologies.
Software Engineering Emphasis for Engineering Computing Courses William Hankley Computing & Information Sciences Kansas State University.
CIS 210 Systems Analysis and Development Week 6 Part I Structuring Systems Data Requirements,
1)History of water fall model. 2)Features of water fall model. 3)Phase of water fall model. 4)Brief description of phases. 5)Advantages. 6)Disadvantages.
Lecture 3 : Hard Systems Modelling UFCE8V-20-3 Information Systems Development SHAPE Hong Kong 2010/11.
Software Engineering Lecture 10: System Engineering.
Defining and Managing Project Scope. MOV Scope Phases Time Estimates Resources Tasks Schedule Budget Sequence Project Planning Framework.
Introduction to System Analysis and Design MADE BY: SIR NASEEM AHMED KHAN DOW VOCATIONAL & TECHNICAL TRAINING CENTRE.
Enterprise Architectures. Core Concepts Key Learning Points: This chapter will help you to answer the following questions: What are the ADM phase names.
The Database Development Process 1. Objectives Definition of terms Describe system development life cycle Explain prototyping approach Explain roles of.
Software Engineering cosc 4359 Spring 2017.
Biotechnology Plant Design:
A Comparative Survey of Enterprise Architecture Frameworks
Definition of CIM “CIM is the integration of the total manufacturing enterprise through the use of integrated systems and data communications coupled.
UNIFIED PROCESS.
Information Technology (Spz.)
Information Technology (Spz.)
Information Technology (Spz.)
Information Technology (Spz.)
Information Technology (Spz.)
Information Technology (Spz.)
Information Technology (Spz.)
Information Technology (Spz.)
Information Technology (Spz.)
Information Technology (Spz.)
Information Technology (Spz.)
Information Technology (Spz.)
Information Technology (Spz.)
Information Technology (Spz.)
Information Technology (Spz.)
Information Technology (Spz.)
A Comparative Survey of Enterprise Architecture Frameworks
Copyright © Simon Wallace
A Description from the Viewpoint of Industrial Automation
Introduction To software engineering
System architecture, Def.
Presentation transcript:

PERA Methodology

Purdue Enterprise Reference Architecture What Is PERA ? Purdue Enterprise Reference Architecture The Purdue Enterprise Reference Architecture was developed by the Purdue Laboratory for Applied Industrial Control at Purdue University (USA) as part of the work of the industry - Purdue University consortium for CIM (Computer Integrated Manufacturing). The Purdue reference model started in 1986. PERA Methodology

Purdue Enterprise Reference Architecture What Is PERA ? Purdue Enterprise Reference Architecture A "Model" of the Full Enterprise Life Cycle. Developed by Major Industries and Academia Proposed International Standard Designed for Process, Manufacturing and Services Industries PERA Methodology

PERA Concepts The PERA Enterprise Model including the three main components of any enterprise: Production Facilities People Control and Information Systems PERA Methodology

PERA Concepts PERA provides a life cycle model which demonstrates how to integrate Enterprise Systems, Physical Plant Engineering and Organizational Development from enterprise concept to dissolution.   There are only 3 major components of any enterprise: Physical Plant People Information Systems PERA provides a life cycle model which demonstrates how to integrate Enterprise Systems, Physical Plant Engineering and Organizational Development from enterprise concept to dissolution. Since the physical plant is the most obvious component of an enterprise, many people think of a corporation only in terms of its physical assets. However, although they do not show up on a balance sheet, people are often more important than physical assets to a company's long term competitive position. Information, communications and control systems comprise the third component. Without an effective "nervous system" provided by a modern enterprise information and communication system, the enterprise will be sluggish and soon overtaken by more agile competitors. PERA clearly defines the roles and relationships among physical plant, people, and information systems.   PERA Methodology

PERA Diagrams PERA Master Planning PERA Framework Both of the above PERA diagrams emphasize the importance of considering Human and Organizational aspects, as well as Control and Information Systems, at every phase of the enterprise. PERA Methodology

PERA Master Planning Diagram The PERA Master Planning Methodology provides a methodical approach to planning which can be used at any phase in the life cycle of an enterprise. PERA Methodology

PERA Framework Diagram The PERA Framework provides a framework for planning each phase of the enterprise. As such it encompasses all other planning, design, and analysis tools. PERA Methodology

PERA Reference Model PERA Reference Model for Computer Integrated Manufacturing (CIM) This two-volume set provides a generic model for the Control and Information System of any manufacturing facility. It contains two major sub-models: A data flow model showing how data flows between all functions in an enterprise. A "hierarchical model" which shows how the functions are divided up between the various "levels" of management (i.e. what your boss does vs. what you do). PERA Methodology

PERA Phases The PERA Model breaks the enterprise life cycle into "phases" as follows. The following are crucially important rules of project management associated with project phasing. Define clear "deliverables" at the end of each phase Don't proceed to the next phase before formal signoff by all interested groups. Don't backtrack on information defined in the previous phase unless the design is unsafe or won't work. PERA Methodology

PERA include 8 high level phases and 28 low level phase PERA High Level Phases 1 Enterprise Definition & Feasibility Study 2 Enterprise Master Planning 3 Preliminary Engineering Detailed Engineering 4 PERA include 8 high level phases and 28 low level phase Construction 5 Operations and Maintenance 6 Renovation or Decommissioning 7 Enterprise Dissolution 8 PERA Methodology

Comments on PERA Liked Did not like The focus on preparing the master plan Emphasis on defining the role of human covers all phases of the enterprise life cycle lack of modeling formalisms. methodology is not clearly defined PERA Methodology