1 / 20

The Work Breakdown Structure is a Product of the Systems Engineering Process

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

marcy
Download Presentation

The Work Breakdown Structure is a Product of the Systems Engineering Process

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Work Breakdown Structure is a Productof 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.

  2. 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.

  3. 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.

  4. 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

  5. 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.

  6. 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.

  7. 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

  8. 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).

  9. See MIL-HDBK-881

  10. Cost, Schedule, and Performance RiskManagement 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.

  11. 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.

  12. 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.

  13. SEMS Interrelationships

More Related