Presented by:
Systems Engineering and Leveraging Commercial Applications at CERDEC
Mr. Gary BlohmDirector, US Army RDECOM Communications Electronics Research, Development and Engineering Center
12 March 2010
Panelist IntroductionPanelist Introduction
Panelist MembersMr. 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 LanghauserDirector, Training and Technology Center (STTC) / RDECOM
Ms. Maureen WellerU.S. Army Corps of Engineers, Dallas HQS
COL Ken WheelerDeputy Program Executive Officer (DPEO), Simulation, Training & Instrumentation’
Forum Moderator
Mr. Gary BlohmDirector, Communications Electronic Research, Development and Engineering Center (CERDEC / RDECOM)
AgendaAgenda
• 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 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.
• 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.
Top 5 Systems Engineering Issues in the Defense Industry
VICTORYVehicular Integration for C4ISR/EW inTerOpeRabilitY
• 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
Develop Architecture Create Open Standards PEO/PM Implementation
Common Data Bus Ethernet Network
Common Displays
Time & Location Distribution
Information Assurance
Backup Slides
NDIA Task Force 2005
c
RevisedRegulatory Policy DoDI 5000.02
RevisedRegulatory Policy DoDI 5000.02
• Evolutionary Acquisition Revised
• Life-Cycle Sustainment Plan
• Updated DoD Earned Value Management ReportingProcedures
• Accounting for Military Equipment
• Cost of Energy
• Contract Incentives Strategy
• Approval of Acquisition Strategy prior to Release ofRFP (MS A & B)
• Detailed Systems Engineering Policy
Summary of changes:
c
Enclosures to the DoDI 5000.02 (2008)
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 IT Considerations
E5 Integrated T&E
E6 Resource Estimation
E7 Human Systems Integration
E8 Acquisition of Services
E9 Program Management
E10 MDA Program Certification
E11 Management of Defense Business Systems
E12 Systems Engineering
}TablesUpdated
new
Encl 12, Systems Engineering (New)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
11
Open Standard = VICTORY
Platform Limits
Com
plex
ity
Weig
htPow
er
Size
RadiosFBCB2
CREW
Sensors
Crew Compartm
entFlexibility
If current trend continues
When is a standard “Open” ?
• Vendor neutral
• Vendor platform independent
• Managed by a standards body
• Implementable by multiple sources
• Openly published
VICTORY Benefits
• Government accepted standards
• Open competitive environment
• Minimize integration costs
• Allows rapid introduction of new capabilities
• Facilitates technology transition
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:
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:
Functional Decomposition of SIDs
Technology Areas(TFTs)
• Lethality• Protection• Networks• Sensors• Power & Energy• Mobility &
Logistics• Human
Dimension & Training
S&T Projects to Address SID’s(ATO-Rs and
ATO-Ds)
with identified System and
Technical KPPs
2
1
Crosswalk Technologies
Crosswalk Technologies
Selection Criteria
34
5
FYXXS&T
Programs
Step 1: Flow Needs/Capabilities into functional areasStep 2: Decompose the functions of effectsStep 3: Crosswalk technologies into functional areasStep 4: Define Technology Gaps (ATO-Rs) and Select System Level Projects (ATO-Ds)Step 5: Prepare S&T plan for SID area with associated KPPs at the system and technology area
RDECOM moving toward objective SE driven portfolio process
RDECOM moving toward objective SE driven portfolio process
Top Related