• No results found

WORKFORCE COMPOSITION CPR. Verification and Validation Summit 2010

N/A
N/A
Protected

Academic year: 2021

Share "WORKFORCE COMPOSITION CPR. Verification and Validation Summit 2010"

Copied!
17
0
0

Loading.... (view fulltext now)

Full text

(1)

WORKFORCE COMPOSITION CPR

PEO IEW&S

Organizational Assessment

VCSA Brief

Date 2010

This briefing is

UNCLASSIFIED/FOUO PREDECISIONAL LIMITED DISTRIBUTION

Army Regulation 25-1 prohibits the use of transmitting and recording

Verification and Validation Summit 2010

AS OF: 11 Sep 2010
(2)

0 1,000,000 2,000,000 3,000,000 4,000,000 5,000,000

FY08 FY09 FY10 FY11 FY12 FY13 FY14 FY15

OMA APA OPA RDTE Supplemental Total OPA 41% RDTE 23% OCO 29% APA 21% OMA 1%

Programs and Dollars

Source of Funds FY10 –FY15

Key Program Metrics

Materiel Solution Analysis/ Preprogram Initiation 13 Technology Development

Phase 3

Engineering and Manufacturing Development 13 Production &

Deployment 93 Operations & Support 39

Classified 7

Product Phases*:

*Some program in multiple phases

Programs: ACAT I 5 ACAT II 6 ACAT III 49 PRE-MDAP / PRE-MAIS 2 QRCs 50 FY10 Funding OCO $1.90B 53% Base $1.60B 47% Supplemental includes all appropriations

PEO IEW&S Funding Profile

As of 1 Sept 2010

(3)

DoD Definition “Systems Engineering”

Systems Engineering is an interdisciplinary approach

encompassing the entire technical effort to evolve and

verify an integrated and total lifecycle

balanced set of

system, people and process solutions

that satisfy

customer needs. Systems engineering is the integrating

mechanism across the technical efforts related to the

development, manufacturing, verification, deployment,

operations, support, disposal of and user training for

systems

and their lifecycle processes. Systems

engineering develops

technical information

to support the

program management decision-making process.

(4)

The Defense Acquisition Management System

IOC

B A

Technology Opportunities & Resources

Materiel Solution Analysis FRP Decision Review FOC Materiel Development Decision User Needs PDR CDR CDD CPD ICD AoA

Pre-Systems Acquisition Systems Acquisition Sustainment

Post CDR Assessment PDR Technology Development Production & Deployment Operations & Support Engineering and Manufacturing Development C or Post PDR Assessment B

Engineering & Manufacturing

Development – Two Major Efforts C

PDR CDR CDD CPD Post CDR Assessment PDR or Integrated System Design

System Capability & Manufacturing Process

Demonstration

Post PDR Assessment

(5)

Technical Reviews

• System Requirements Review – Trace of User Requirements • System Functional Review – Performance Baseline

• Preliminary Design Review – Allocated Functional Baseline • Critical Design Review – Initial Product Baseline

• Test Readiness Review – Plan, Support, Limitations • Functional Configuration Audit – Performance Validated • Physical Configuration Audit – Final Product Baseline • Production Readiness Review – Facilities, Vendor Base,

Materiel etc.

(6)

Qualified People

• Systems Engineer

• Program Systems Engineer

• Science and Technology Manager

Systems Planning, Research,

Development and Engineering Career Fields

Certification

• Training • Education • Experience

(7)

Systems Engineering Plan

PURPOSE: Establish the program systems engineering approach,

providing a firm and well documented technical foundation for the program.

• Program Requirements (User Derived, Statutory, Regulatory Certification)

• Technical Staffing and Organization • Technical Baseline Management • Technical Review Plan

• Integration with Program Management (Contracting, Test, CM, Sustainment, Risk Management)

(8)

Readiness Levels

TRL (Technology Focused) IRL (Platform Focused)

9 Actual Technology Proven Operation

8 Actual Technology Qualified by Demonstration

7 Technology Prototype Demonstration in an Operational Environment

6 Technology Model or Prototype Demonstration in a Relevant Environment

5 Component and/or Breadboard Validation in a Relevant Environment

4 Component and/or Breadboard Validation in a Laboratory Environment

3 Analytical and Experimental Critical Function Proof-of-Concept

2 Technology Concept and/or Application

1 Basic Principles Observed and Reported

5 Operational System Fabrication, Launch Completed & Operations Commenced 4 Prototype/Demonstrator Subjected to Representative Environments

3 System Physical Mockup or Prototype, Subjected to Test Environment 2 Detailed System Design Completed

1 Concept Systems Analyses Completed

MRL 3 MRL 4 MRL 5 MRL 6 MRL 7 MRL 8 MRL 9 MRL 10

Mfg Concepts

Indentified Mfg Processes Indentified Key Processes Identified Producibility Assessment Initiated Mfg Processes Developed Mfg Equipment in Relative Environment Producibility Assessment Ongoing Cost Drivers Identified Critical Mfg Processes Demo’d Mfg Equipment in Relevant Environment Producibility Assessment Ongoing Cost Drivers Analyzed Long Lead Items

Identified Prototype Mfg System Mfg Processes in Validation Producibility Improvement Underway Trade Studies Conducted Supply Chain Validated Long Lead Plans

in Place

Process Maturity Demo All Materials Ready for LRIP Mfg Processes Proven for LRIP

Supply Chain Established Mfg Processes Proven Overall Mfg Process Operates at Target Quality, Cost and Lead

Times All key Processes

Meet Process Control Targets Highest Production Readiness System in Production & Meets Engineering Performance & Reliability Overall Mfg Process Operates at 6-Sigma Quality, and Meets cost and

Lead Time Estimates

(9)

Top Five SE Issues

As identified by NDIA task group:

• Key SE practices known to be effective are not consistently applied across all phases of the program life cycle.

• Insufficient SE is applied early in program life cycle, compromising foundation for initial requirements and architecture development. • Requirements are not always well-managed, including effective

translation from capabilities statements into executable requirements to achieve successful acquisition programs.

• Quantity and quality of SE expertise is insufficient to meet demands of government and defense industry.

• Collaborative environments, including SE tools, are inadequate to effectively execute SE at joint capability, system of systems (SoS), and system levels.

(10)

Systems Engineering Initiatives

• Systems Engineering Plan (SEP) required at each milestone • MDA is approval authority for the SEP

• Where USD(AT&L) is MDA, and program on the DT-only portion of T&E Oversight List, SEPs must be submitted to OSD

• PEOs must have lead systems engineer

• Event-driven technical reviews required – with SMEs independent of program, unless waived by MDA

• Configuration management to establish and control product attributes and the technical baseline

• Spectrum Supportability determination required

• ESOH risk management required to be integrated with overall SE process

• NEPA and EO 12114 (Environmental Effects Abroad of Major Federal Actions) analysis required of PM, approved by CAE

• PM support of Mishap Accident Investigations

• Corrosion Prevention Control Plan for ACAT I programs at MS B and C • PMs to employ modular open systems approach to design

• Data Management Strategy (DMS) required to assess long-term technical data needs of the system – included in Acquisition Strategy

DoDI 5000.2 8 Dec 2008

(11)

Risk Management: SE Fundamental

• Identify areas that may impact future cost, schedule,

performance

• Assess the likelihood and consequence to

characterize/prioritize

• For critical risks, establish inchstones for mitigation to

acceptable risk level and track progress

(12)

Typical Risk Assessment

1 2 3 4 5 E D B Li k e lihoo d 1 2 3 4 5 Consequence

Risk A: Meeting KPPs (RETIRED)

Risk B: Production Capacity

Driver: Facilities

Impact: Outyear Quantities

Mitigation Plan:

Increased DCMA oversight

Red Team Assessment of production capacity

Production improvement plan • Fund additional production facilities • Implement improved supply chain

Retirement: Demonstrate production rate

Risk C: (RETIRED)

Risk D: Platform Integration

Driver: Changes at the platform level that may impact subsystem

Impact: Cost and Schedule

Mitigation Plan:

 ICD finalized

 Fit Checks

 System delivered to SIL • DT testing on platform

Retirement: IOT&E

Risk E: No solution to Low Temp Requirement

Driver: Non-compliance to spec

Impact: Cost and Schedule

Mitigation Plan:

Interim Waiver

• Continue to Investigate fixes • Implementation of Fix

Retirement: Retest

(13)

Typical Risk Mitigation Plan

Step Action Purpose Date

0 PRR Confirm ready for production Complete 1 Response to PRR findings Addressed process issues Complete 2 Increase Oversight by DCMA Provide early insight into production process and

procedure problems Complete 3 Place Final Spec under contract Resolve SPEC Discrepancies Complete 4 Begin FRACAS Reporting Monitor Post-production failures for trend analysis Nov 10 5 Regression Test Confirm production compliance with Spec

Requirements Jul 11 6 Physical Configuration Audit Establish Configuration Baseline Sep 11 7 Supply Support Implement strategy that reduces pressure on

production capacity Mar 12

0.9 0.8 0.7 0.6 0.5 0.4 0.3 0.2 0.1 0 R is k F a c to r (R F ) Dec 09 3rd Qtr10 1st Qtr 12 3rd Qtr12 0 1 7 Today FY13 2 3 5 4 4th Qtr 10 3rd Qtr 11 4th Qtr 11 2nd Qtr 11 1st Qtr 11 6 Risk B: Production Capacity

(14)

System of Systems Engineering (SoSE) Initiative

Army SOSE:

Provide the leadership and materiel developers with the

necessary engineering/architectural products to

manage

and shape the Army’s materiel portfolio

, to ensure a

System Engineering discipline across the Materiel

Developer community throughout the acquisition life cycle

and grow the System Engineering capability within the

Army – through education, engineering policy, guidelines

and adoption of best industry practices… “Build the Bench”.

“A Robust Systems Engineering Capability Across Systems

Require Attention to Policy, People and Practice”

(15)

Architectures

Goals

•Establish a unified governance structure for

system Architecture within ASA(ALT)

•Align the Architecture Products to support Army

and Acquisition processes

•Align System Architecture capability within

ASA(ALT)

Tasks: 1.4.1 Provide strategic level SoS engineering and architectural products

•1.4.1.1 Document and publish the current strategic level Systems architecture for each SoS

•1.4.1.2 Develop and publish the future strategic level Systems architecture for each SoS at designated times in the future

•1.4.1.3 Develop and publish the strategic Systems Engineering Plan (SEP) for each SoS

•1.4.1.4 Establish and publish the standards and policies for SoS interfaces and data

•1.4.1.5 Identify, maintain and publish the official list of SoS and associated subsystems

•1.4.1.6 Provide input to the technical standards of performance for each SoS

Authoritative System Architectures Authoritative Data Sources Acquisition Analysis

(16)
(17)

•Systems Engineering has been a focus area for DoD leadership since 2005

•Systems Engineering is a key enabler in managing to complex program success and satisfying Warfighter requirements

•Risk management is a cornerstone of Systems Engineering and Program Management

•SoSE is the way of the future for DoD

References

Related documents

procedure was repeated separately for each of the three CES engagement groups; recreation, natural heritage and cognitive, to examine whether characteristics associated with

The absence of studies and knowledge concerning the environmental impacts of the different methods of syn- thesis of nZVI led to this work, where LCA was used as an ecodesign

In terms of worst-case performance, CGM with maximum-error optimization clearly outperforms all the other algorithms with respect to the maximum angular and RMS errors, while

Then you turn left on TWEEDE Weteringdwarsstraat, ring the doorbell on number 65 (you need to walk up a few steps and there is just one doorbell , which says Martin / Bed

At the same time, functions of finite mean oscillation are generally integrable only in the first power; it is possible to construct an example of a function of class FMO that is

These limits give convenient estimates for the maximum forced response of mistuned bladed disks, but in most cases are too conservative and do not take into account the effects of

This new palindromic QR algorithm is strongly backward stable and requires less operations than the standard QZ algorithm, but is restricted to matrix classes where a prelimi-