Transcript RDECOM template - NDIA - Central Florida Chapter

Presented by:
Systems Engineering and Leveraging Commercial
Applications at CERDEC
Mr. Gary Blohm
Director, US Army RDECOM Communications Electronics Research, Development and Engineering Center
12 March 2010
Panelist Introduction
Forum Moderator
Mr. Gary Blohm
Director, Communications Electronic Research, Development and Engineering Center (CERDEC / RDECOM)
Panelist Members
Mr. Frank Apicella
SES, U.S. Army Evaluation Center, US Army Test and Evaluation Command (ATEC)
Mr. Doug Richardson
PEO Special Reconnaissance, Surveillance and Exploitation Systems (US SOCOM)
CAPT Harry (Smokey) Robinson
Commanding Officer, Naval Air Warfare Center Training Systems Division (NAWCTSD) / NSA Orlando
COL Craig Langhauser
Director, Training and Technology Center (STTC) / RDECOM
Ms. Maureen Weller
U.S. Army Corps of Engineers, Dallas HQS
COL Ken Wheeler
Deputy Program Executive Officer (DPEO), Simulation, Training & Instrumentation’
Agenda
• DOD System Engineering Environment
• Top 5 Systems Engineering Issues in the Defense Industry
• Vehicular Integration for C4ISR/EW Interoperability (VICTORY)
• Increased use of Commercial Capabilities / Applications
DOD System Engineering
Environment
• DOD is a complex engineering environment
– Strong emphasis on System Engineering in the department
– System of Systems practices emerging
– Interoperability - interdependencies have never been stronger
– Engineering the product – engineering the interfaces
Systems Engineering is defined in the DoD's Defense Acquisition Guidebook as 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.
Top 5 Systems Engineering
Issues in the Defense Industry
• Key Systems Engineering practices known to be effective are not
consistently applied across all phases of the program life cycle.
• Insufficient Systems Engineering is applied early in the program life cycle,
compromising the foundation for initial requirements and architecture
development.
• Requirements are not always well-managed, including the effective
translation from capabilities statements into executable requirements to
achieve successful acquisition programs.
• Collaborative environments, including SE tools, are inadequate to
effectively execute SE at the joint capability, System-of-Systems (SoS)
and system levels.
• The quantity and quality of Systems Engineering expertise is
insufficient to meet the demands of the government and the defense
industry.
VICTORY
Vehicular Integration for C4ISR/EW inTerOpeRabilitY
Common Data Bus Ethernet Network
Common Displays
Time & Location Distribution
Information Assurance
Develop Architecture
•
•
Gigabit Ethernet Switches with copper media
High bandwidth connections within the vehicle
•
•
•
Displays w/custom presentation of information
Touch screens for user input (WMI)
Processing and data storage capability
•
•
•
GPS antenna and receiver for each classification level
Common displays receive time & location / publish on network
Allows for fewer GPS devices to support C4ISR/EW systems
•
MILS solution protects data in intra-vehicle network
– Two physically separated enclaves (secret and unclassified)
Common display with trusted separation kernel
– Runs software at both classification levels
•
Create Open Standards
PEO/PM Implementation
Backup Slides
NDIA Task Force 2005
Revised
Regulatory Policy DoDI 5000.02
Summary of changes:
c • Evolutionary Acquisition Revised
• Life-Cycle Sustainment Plan
• Updated DoD Earned Value Management Reporting
Procedures
• Accounting for Military Equipment
• Cost of Energy
• Contract Incentives Strategy
• Approval of Acquisition Strategy prior to Release of
RFP (MS A & B)
c • Detailed Systems Engineering Policy
Enclosures to the DoDI 5000.02
(2008)
E1 References, continued
E2 ACAT and MDA
E3 Statutory, Regulatory, and Contract Reporting Information and
Milestone Requirements
E4
E5
E6
E7
IT Considerations
Integrated T&E
Resource Estimation
Human Systems Integration
E8 Acquisition of Services
E9 Program Management
E10 MDA Program Certification
E11 Management of Defense Business Systems
E12 Systems Engineering
new
}
Tables
Updated
Encl 12, Systems Engineering
(New)
• Systems Engineering Plan (SEP) required at each milestone
–
MDA is approval authority for the SEP
• PEOs must have lead systems engineer – oversees SE across PEOs portfolio;
reviews SEPs; assesses performance of subordinate systems engineers with PEO and
PM
• Event-driven technical reviews required – with SMEs independent of program, unless
waived by MDA
• Requires PMs to employ modular open systems approach to design (MOSA)
• Spectrum Supportability determination required
• Requires Corrosion Prevention Control Plan for ACAT I programs at MS B and C
• Requires configuration management to establish and control product attributes and
the technical baseline
• Data Management Strategy (DMS) required to assess long-term technical data needs
of the system – included in Acquisition Strategy
• ESOH risk management required to be integrated with overall SE process;
Programmatic ESOH Evaluation (PESHE) required of all programs regardless of ACAT
• NEPA and EO 12114 (Environmental Effects Abroad of Major Federal Actions) analysis
required of PM, approved by CAE
• Addresses PM support of Mishap Accident Investigations
Open Standard = VICTORY
When is a standard “Open” ?
•
Vendor neutral
•
Vendor platform independent
•
Managed by a standards body
•
Implementable by multiple sources
•
Openly published
Platform
Limits
VICTORY Benefits
•
Government accepted standards
•
Open competitive environment
Sensors
•
•
•
CREW
Minimize integration costs
FBCB2
Radios
Allows rapid introduction of new
capabilities
If current trend continues
Facilitates technology transition
11
RDECOM moving toward objective
SE driven portfolio process
1
2
Functional Decomposition of SIDs
Effects
Detect
Decide
Deliver
Assess
Needs/Capabilities:
• ASAALT IBCT Pilot (PEO
System Integration)
• PEOs/PMs: i.e. Abrams
• JCIDS: i.e. CIEDs
• S&T Initiatives/Thrusts: i.e.
Fuel Reduction, Cluster
Munitions Ban
• Others:
Technology Areas
(TFTs)
• Lethality
• Protection
• Networks
• Sensors
• Power & Energy
• Mobility &
Logistics
• Human Dimension
& Training
3
Crosswalk
Technologies
Crosswalk
Technologies
4 Selection Criteria
S&T Projects to
Address SID’s
(ATO-Rs and
ATO-Ds)
5
FYXX
S&T
Programs
with identified
System and
Technical KPPs
Step 1:
Step 2:
Step 3:
Step 4:
Step 5:
Flow Needs/Capabilities into functional areas
Decompose the functions of effects
Crosswalk technologies into functional areas
Define Technology Gaps (ATO-Rs) and Select System Level Projects (ATO-Ds)
Prepare S&T plan for SID area with associated KPPs at the system and technology area