The program work breakdown structure (WBS) establishes the essential

Slides:



Advertisements
Similar presentations
1 PROJECT MANAGEMENT ROLE OF KEY PERSONNEL Bernd Madauss International Space University Strasbourg February, 2011
Advertisements

Optimize tomorrow today. TM Cost and Affordability approach at Development Planning stage 1.
Presented by: Presented By: MIL-STD 881 Update: NDIA PMSC Neil F. Albert MCR, LLC 12 May 2010.
S Y S T E M S E N G I N E E R I N G.
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
Work Breakdown Structures. Purpose The WBS shows different levels within the product hierarchy. For Government program managers levels 1-3 are of prime.
5-1 DoD Risk Management Policies and Procedures. 5-2 Risk Assessment and Management (DoD ) “Program Managers and other acquisition managers shall.
Integrated Risk Management EMIS Admin Stuff Instructor: Jan Lyons, PhD Warning – have to select from.
Configuration Management
Systems Engineering Management
Management of a Training Program January 12 – 14, 2009.
LSU 10/09/2007Project Tasks & Costs1 Defining the Project Tasks, Cost and Schedule Project Management Unit #3.
Defining the Activities. Documents  Goal Statement defines why helps manage expectations  Statement of Work what gets delivered defines scope  Software.
Trade Study Methods.
LSU 07/24/2004Defining Project Tasks1 Defining the Project Tasks Project Management Unit, Lecture 4.
Engineering Systems of.
@ Industrial Engineering by Bopaya Bidanda David I. Cleland.
Project Management Education
Effective Methods for Software and Systems Integration
Unclassified. Program Management Empowerment and Accountability Mr. David Ahern Director, Portfolio Systems Acquisition AT&L(A&T) 14 April 2009 The Acquisition.
Romaric GUILLERM Hamid DEMMOU LAAS-CNRS Nabil SADOU SUPELEC/IETR.
Chapter 2: Overview of Essentials ISE 443 / ETM 543 Fall 2013.
Introduction to Software Quality Assurance (SQA)
Standard WBS Version 1.0 WBS2-3.pptPage 1 Standard Work Breakdown Structure Legend = Decomposes to lower level WBS elements 4.0 Implementation 4.0 Implementation.
Configuration Management T3 Webinar Feb 21, 2008 Chuck Larsen ITS Program Coordinator Oregon Department of Transportation.
CLEANROOM SOFTWARE ENGINEERING.
Work breakdown structure
From Research Prototype to Production
1 Lecture 3.1: Project Planning: Work Breakdown Structure (WBS) [SEF Ch 9] Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
NIST Special Publication Revision 1
The Challenge of IT-Business Alignment
8-1 Establish Cost/Schedule Performance Impacts Program Requirements Assess Risks Evaluate Risk Handling Options Evaluate Subcontractor Risks Establish.
1-1.
1 Lecture 5.2a: SEF Ch 8 SE Outputs Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
Task: Copyright © 2003 PM tec, Inc; D. Sankey; D. Padelford. All rights reserved. 1 Fast Start For Projects  Electric Dipole Moment Project Facilitator:
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
1 Total Ownership Cost (TOC) and Cost as an Independent Variable (CAIV) Dr. Jeffrey Beach Naval Surface Warfare Center Carderock Division; Survivability,
Project Scope Management Project management Digital Media Department Unit Credit Value : 4 Essential Learning time : 120 hours.
Project Life Cycle.
Apply Project Scope Management Techniques Project Scope Processes – Part 2 Certificate IV in Project Management Qualification Code BSB41507 Unit.
Georgia Institute of Technology CS 4320 Fall 2003.
Robotics & Engineering Design Projective Management Chin-Sung Lin Eleanor Roosevelt High School.
Risk Management 1. Risks and Risk Management Risks are potential events that have negative impacts on safety or project technical performance, cost or.
Pre-Project Components
DPE CSSW Process Model Annex A WP-400 ECSS Case Study.
NASA/Air Force Cost Model presented by Keith Smith Science Applications International Corporation 2002 SCEA National Conference June
NCSX Systems Engineering Management Plan Peer Review Bob Simmons May 15, 2003.
SE&I Pre-Proposal Meeting GSFC - JPL Systems Engineering Management Colleen McGraw.
5 - 1 The Cost Modeling Process Chapter Introduction What makes a good cost model? – Good Statistics – Quality Data – Relevant Data – Analogous.
Alpha Contracting Sole Source Negotiations between Government and Industry (13 CFR (c)(2))
Independent Expert Program Review (IEPR) February 2006.
SRR and PDR Charter & Review Team Linda Pacini (GSFC) Review Chair.
Presented by: Presented By: MIL-STD 881 Update Neil F. Albert MCR, LLC 26 August 2010.
Presented by: Presented By: MIL-STD 881 Update: NDIA PMSC Meeting Neil F. Albert MCR, LLC 4 February 2010.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
Enterprise Approach Used In Cost Estimating Presented by SCEA 2004 National Conference Lisa Stevenson ESC/GAX Robert Nelson.
WEEK 3 Project Planning.
IV&V Facility 7/28/20041 IV&V in NASA Pre-Solicitation Conference/ Industry Day NASA IV&V FACILITY July 28, 2004.
Breakdown Work Structure Applying Management Tools to a Project.
SQA project process standards IEEE software engineering standards
Supportability Design Considerations
SQA project process standards IEEE software engineering standards
IEEE Std 1074: Standard for Software Lifecycle
INCOSE – North Texas Chapter
Defining the Activities
Systems Engineering Management
By Jeff Burklo, Director
Lockheed Martin Canada’s SMB Mentoring Program
PLANNING & SCHEDULING (First Part)
DOE Review of the LCLS Project October 2006
Presentation transcript:

The Work Breakdown Structure is a Product of the Systems Engineering Process The program work breakdown structure (WBS) establishes the essential framework for program and technical planning, cost estimating, resource allocations, performance measurements, and status reporting. The WBS shall define the total system to be developed or produced, display the total system as a product-oriented family tree composed of hardware, software, services, and data, and relate the elements of work to each other and to the end product.

WBS Definitions Program WBS - A program WBS shall be developed to define initially the top three levels of a WBS for the entire acquisition cycle of the system being acquired. A final program WBS shall be prepared by compiling the elements of the contract WBSs with the initial program WBS. Contract WBS - From the initial program WBS, preliminary contract WBSs for individual contracts shall be developed to be negotiated with the contractors involved. The contract WBS shall be extended to lower levels by the contractor using as guidance MIL-HDBK-881.

Specifications shall Conform to the WBS 1. WBS elements may contain both nonrecurring and recurring effort. 2. Integrated logistics support and software shall be accommodated in the appropriate levels of the WBS in accordance with MIL-HDBK-881. 3. Functional cost elements such as engineering, tooling, quality control, and manufacturing are not WBS elements and shall not be represented as such in the WBS.

Example System Configuration Legend SS Subsystem PROC Process HW Hardware SW Software FW Firmware System SS-1 SS-2 SS-3 SS-11 HW SS-12 PROC SS-13 HW SS-31 HW SS-32 SW SS-21 SS-22 SS-221 HW SS-222 FW SS-121 HW SS-122 HW SS-211 HW SS-212 FW SS-213 SW SS-2221 HW SS-2222 SW SS-2121 HW SS-2122 SW

EXERCISE #1 Background: You have recently been assigned to the IPD Team for the Peace Whey program. Peace Whey is a recently approved FMS program which will provide 20 F-16Cs to the Kurdish Air Force (KAF). The specifications for the Kurdish F-16s call for them to be equipped with the Airborne Jamming System (AJS), an electronic warfare system. Your position will be as AJS team leader responsible for the oversight of design and testing of the AJS system, for its integration into the Peace Whey aircraft, and for the AJS lab and flight testing verification. In addition, you must act as the interface between the AJS team and the other teams making up the IPD Team for the Peace Whey program, making certain that the program office is supported in its overall coordination and management tasks. Exercise: Referring to the Statement of Customer Requirements for AJS (Part 1) which you have been provided, develop a Work Breakdown Structure (WBS) for the AJS development and production task as a part of the overall air vehicle development task.

AJS Statement of Customer Requirements Customer: Kurdish Fighter Program (Peace Whey) Operational Need: Fighter aircraft operating in a hostile environment require extensive electronic countermeasures (ECM) to defeat air-launched and ground-launched threats to the survivability of the aircraft. These ECM systems must be capable of generating and broadcasting radio frequency (RF) energy at sufficient power levels and in appropriate patterns to defeat any threat encountered by the aircraft.

AJS Statement of Customer Requirements (Cont.) Description: The AJS shall be capable of installation on a lightweight, high-speed, multi-role fighter and shall be supportable in primitive forward operating bases. The system shall be capable of transmitting radio frequency signal in the microwave frequency range at sufficient power levels and in patterns capable of successfully jamming all identified threats at the required operational range. The AJS system shall consist of the following major components: 1. Core Avionics: Shall consist of the jammer, the radar warning receiver, and the OFP software. Shall be capable of generating the required RF signal in the microwave band at required power levels and of detecting radar emissions from the threat set at the required ranges. 2. RF Switch H/I/J Band: Shall control selection of broadcast frequency bands as required. 3. Fire Control Radar Notch Filter: Shall prevent interference of the Fire Control Radar (FCR) by the AJS system. 4. Forward Transmit Antenna 5. Aft Transmit Antenna and Raydome 6. WRD-650D24 Waveguide 7. Coaxial Cable

AJS Statement of Customer Requirements (Cont.) Schedule: 1. Flight Test: The Safety of Flight(SOF) unit for flight test shall be available for installation 26 months after program go-ahead. 2. First Production Delivery: The first production assembly shall be delivered 36 months after program go-ahead. 3. Delivery Rate: Delivery of AJS units shall be at the rate of 2 units per month. 4. Total Quantity: The total quantity of AJS units shall be 20. Customer Priorities: 1. Power Transmitted. 2. Weight 3. First production delivery. 4. Cost not to exceed $125,000/unit (for 20 units).

See MIL-HDBK-881

Cost, Schedule, and Performance Risk Management The program manager shall establish a risk management program for each acquisition program to identify and control performance, cost, and schedule risks. The risk management program shall identify and track risk drivers, define risk abatement plans, and provide for continuous risk assessment throughout each acquisition phase to determine how risks have changed. Risk reduction measures shall be included in cost-performance tradeoffs, where applicable. The risk management program shall plan for back-ups in high risk areas and identify design requirements where performance increase is small relative to cost, schedule, and performance risk.

Cost as an Independent Variable (CAIV) The acquisition strategy shall address methodologies to acquire and operate affordable DoD Systems by setting aggressive but achievable cost objectives and managing achievement of these objectives. Cost objectives shall be set to balance mission needs with projected out-year resources, taking into account anticipated process improvements in both DoD and defense industries. This concept has become known as “cost as an independent variable,” meaning that cost shall be more of an input, and less of an output, in the process of acquiring DoD systems.

Cost/Performance Tradeoffs Life-cycle cost-performance tradeoffs shall be considered in each phase by a life-cycle cost-performance integrated product team (CPIPT). The organization and activities of the CPIPT is based on the principle that the best time to reduce life-cycle cost is early in the acquisition process and that cost performance tradeoffs analyses shall be conducted before an acquisition approach is finalized.

SEMS Interrelationships