Session 2 Dr. Dan C. Surber, ESEP

Slides:



Advertisements
Similar presentations
Systems Engineering From a Life Cycle Perspective John Groenenboom Director Engineering – Mesa Boeing Rotorcraft Dec 12, 2007.
Advertisements

10 Golden Questions for Concept Exploration & Development Dr. Dan C. Surber (317)
1 PROJECT MANAGEMENT ROLE OF KEY PERSONNEL Bernd Madauss International Space University Strasbourg February, 2011
S Y S T E M S E N G I N E E R I N G.
More CMM Part Two : Details.
1 Introduction to System Engineering G. Nacouzi ME 155B.
EMIS Chapter 6. EMIS Chapter 6 EMIS Chapter 6 Fig 6.2 shows where the SEMP fits into the earliest program stages. Fig 6.5 has an.
ABET 1 SAYS - Your Senior Design Course Should Include Engineering design is the process of devising a system, component, or process to meet desired needs.
Trade Study Training Need and Goals Need Consistent methodologies and practices performing trade studies Pros/cons, advantages/disadvantages, customer/management.
Systems Engineering Management
BAE SYSTEMS Overview of Systems Engineering at BAE SYSTEMS & ALENIA MARCONI SYSTEMS 8/10/2015/MS By Leigh Watton Friday 27th July 2001.
Engineering Systems of.
LSU 07/07/2004Communication1 Communication & Documentation Project Management Unit – Lecture 8.
Effective Methods for Software and Systems Integration
Chapter 2: Overview of Essentials ISE 443 / ETM 543 Fall 2013.
Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure.
From Research Prototype to Production
Software System Engineering: A tutorial
1 Process Engineering A Systems Approach to Process Improvement Jeffrey L. Dutton Jacobs Sverdrup Advanced Systems Group Engineering Performance Improvement.
1 Lecture 5.2a: SEF Ch 8 SE Outputs Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
Managing CMMI® as a Project
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 systems analysis 1 what is systems analysis? preparation of the system’s requirements/definition,
Page 1 JUSTIFY define and validate REQUIRE- MENTS define initial management DOCUMENTS define INFRA- STRUCTURE allocated maintenance changes management.
Critical Design Review (CDR)
Solar Probe Plus A NASA Mission to Touch the Sun March 2015 Instrument Suite Name Presenter's Name.
SRR and PDR Charter & Review Team Linda Pacini (GSFC) Review Chair.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
1 Lecture 2.3: SE Process (SEF Ch 3) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
1 ME Spring 2015 Systems Engineering, Part II Session 8 5 February 2015 Mr. Larry Hopp, CPL © Copyright 2013.
ME Summer 2013 Systems Engineering, Part II Session July 2013 Mr. Larry Hopp, CPL.
1 ME Spring 2013 Introduction to Systems Engineering Session 3 Dr. Dan C. Surber, ESEP © Copyright 2013.
EMIS Chapter 5 Much of Chap 5 and 6 varies depending on the contract type. Two major types are important so we’ll digress to Contracting 101 for.
THE VALUE (SUPPLY) CHAIN STRETCHES FROM THE BEGINNING OF YOUR SUPPLIER’S SUPPLY CHAIN THROUGH ALL OF YOUR PROCESSES THAT CREATE VALUE FOR YOUR CUSTOMERS.
Camera PDR/CD1 Planning 19 September 2008
Session 10 Dr. Dan C. Surber, ESEP
Session 22 & 23 Dr. Dan C. Surber, ESEP
Supportability Design Considerations
Chapter 2 How important is determining (or creating) the need first?
Key Management Issues for Software Reviews
ISA 201 Intermediate Information Systems Acquisition
Chapter 6: Database Project Management
ME Fall 2014 Introduction to Systems Engineering
Software and Systems Integration
SE and SSE Trade-Off Analyses
DAG CH 3 Figure 11: Weapon System Development Life Cycle
ISA 201 Intermediate Information Systems Acquisition
Session 5b Dr. Dan C. Surber, ESEP
DAG CH 3 Figure 17: Weapon System Development Life Cycle
DAG CH 3 Figure 23: Weapon System Development Life Cycle
INCOSE – North Texas Chapter
DAG CH 3 Figure 13: Weapon System Development Life Cycle
Raytheon Parts Management
MRL 6 Artifacts (at End of TMRR) Page 1 of 6
DAG CH 3 Figure 19: Weapon System Development Life Cycle
DAG CH 3 Figure 18: Weapon System Development Life Cycle
DAG CH 3 Figure 28: Weapon System Development Life Cycle
Lockheed Martin Canada’s SMB Mentoring Program
DAG CH 3 Figure 15: Weapon System Development Life Cycle
Chapter 2 How important is determining (or creating) the need first?
EMIS 7307 Chapter 6.
Project Management Process Groups
Chapter 11: Software Configuration Management
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
Some Practical Considerations for Systems Engineers in a Lean-Agile Airborne Weapons System Program June 12, 2018 Ken Garlington.
Engineering Processes
ESHAC #8 Safety Readiness Review Thomas Hansson, ESH
DAG CH 3 Figure 21: Weapon System Development Life Cycle
DAG CH 3 Figure 27: Weapon System Development Life Cycle
DAG CH 3 Figure 22: Weapon System Development Life Cycle
DAG CH 3 Figure 25: Weapon System Development Life Cycle
Presentation transcript:

Session 2 Dr. Dan C. Surber, ESEP ME 59700 Fall 2014 Introduction to Systems Engineering Session 2 Dr. Dan C. Surber, ESEP © Copyright 2013

Lecture Topics Phase GatesMgmt Design ReviewsTechnical People, Methods, Tools, & Environment Baselines Samples of Checklists 5 reviews for this course

Design Reviews Do we understand the requirements? Do we understand the essential interfaces? Do we have all the necessary functionality? Are the requirements allocated & testable? Does the design meet the requirements – feasible, maintainable, safe, reliable? What are the TPMs we need to track? What are the RISKS & how do we mitigate? Are we ready to TEST? Did we build it right? Did we build the right system? The system must be OPERATIONALLY SUITABLE & OPERATIONALLY EFFECTIVE

Typical Design Reviews Most reviews can also be performed at the system, subsystem, product, component, and assembly or part levels. System Requirements Review System Functional Review System Architecture Review Preliminary Design Review Detailed (Critical) Design Review System Test Readiness Review System Validation Review Production Readiness Review Shipping Readiness Review What is the FOCUS? Requirements being satisfied by the defined solution set, within the architecture boundaries and constraints defined by management/contract and technology readiness.

Phase Gates Purpose Technical focus Subcontractor/Suppliers Management oriented Cost & Schedule + RISKS Plan to get to the “next” gate Technical focus Have we done the right things Do we have the right mix of disciplines Do we have the right technologies Where are the choke points – apply resources Subcontractor/Suppliers Cost & schedule On track technically

Typical Phase Gates for MGMT System Requirements Review System Functional/Design Review Preliminary Design Review Critical Design Review Test Readiness Review Production Readiness Review Shipping Readiness Review

PMTE People Methods Tools Environment Right knowledge, skills, abilities? = Training Plan Right people at the right time? = Staffing Plan Key Stakeholders? = Stakeholder Involvement Plan & Artifacts Methods Proven Processes? = Process Tailoring & Support, Stakeholders Key Events, Activities, Criteria? = IMP, IMS, SEMP/SEP Tools Company standard? = Templates, Enablers, Checklists Standards? = Project/Engineering Notebook, Reference Architectures Environment Leadership buy-in & support? = Senior Management Reviews Metrics? = Earned Value Measurement, Measurement Analysis, Decision Making? = Trade offs, Technical Performance Measures, Risk & Opportunity Management

Baselines Main thrust of SE is orderly synthesis Setting & Maintaining BASELINES Requirements baseline Functional baseline Allocated baseline Production baseline Controlled changes with full understanding of change impact – Change Management (CM) Data Management (DM) Configuration Control Board (CCB)

Knowledge Development & Review Concepts Artifact Collection of Artifacts Independent Review (pre-gate) Peer Review Design Walk Through Phase Gate Review Artifact Baseline Established Design Baseline Established Configuration Baseline Established

Phase Gate Reviews Incremental KNOWLEDGE DEVELOPMENT COST SCHEDULE & RESOURCES RISKS & MITIGATIONS TECHNICAL BASIS TO PROCEED to next SRR SFR/SDR PDR CDR TRR PRR Gate 1 Gate 2 Gate 3 Gate 4 Gate 5 Gate 6 See Session 002a slide

Concept Review Checklist CONOPS Conditions of operation Conditions of maintenance & support Mission analysis & Scenarios (Normal, Abnormal, Emergency, Catastrophic) Extracted functional analysis and interface analysis System Need User performance, design constraint, environment, and interface requirements Mission event timeline, phases, system states/modes System requirements (performance, environmental, interface, design constraint) Concept Architecture people, facilities, hardware, software, data, support equipment & tools, technical data, training, logistics concepts

Example in Text book Blanchard, p. 96, Figure 3.27 Others DAU SE Handbook Domain specific Company specific (within its process) Have at least a “general” set of topics Checklists are “don’t forgets” – the gator is watching!

Example from MIL-STD-1521B Mission/Requirements Analysis Functional Flow Analysis Preliminary Requirements Allocation System/Cost Effectiveness Analysis Trade Studies Logistics Support Analysis Specialty Discipline Studies System Interface Studies System Performance Specification Program Risk/Opportunity Analysis Integrated Test Planning Producibility Analysis Technical Performance Measures Data Management Plans Configuration Management Plans System Safety Program Plan (SSPP) Human Factors Analyses Value Engineering Studies Life Cycle Cost Analysis/CAIV Prelim Manufacturing Plans Manpower Requirements & Personnel Analysis Milestone Schedule IMP/IMS Supply Chain Management & supplier selections Specific actions/plan to get to next gate: SRR/SFR/SDR

See “Class Projects 1-5.doc” file Class Project Briefs 5 topics for each briefing Uses information built up through home work & readings 5 minutes to brief the 5 topics WRITTEN material is GRADED VERBAL material is graded CLASSMATES get to ask questions See “Class Projects 1-5.doc” file

Suggestions Use the assignment description as a checklist Ensure you meet the threshold criteria for your briefing (5 topics) – See handout with topics to be covered at each review Use figures, charts, graphs Avoid charts with LONG text Bullets are better, faster, cheaper

Review from RESOURCES Download the file “10 Golden Questions”. Use it to help identify the information needed for your selected system. Make sure you can state the “purpose” for the selected system, its mission system and its support system. Make sure you can draw a context diagram for your selected system. Sketch a CONOPS for your system (mission) Identify examples of each of the four types of requirements.