ASA(ALT) System of Systems Engineering & … of Systems Engineering & Integration (SoSE&I) 3 . To be...
-
Upload
vuongxuyen -
Category
Documents
-
view
223 -
download
0
Transcript of ASA(ALT) System of Systems Engineering & … of Systems Engineering & Integration (SoSE&I) 3 . To be...
ASA(ALT) System of Systems
Engineering & Integration (SoSE&I) Directorate
May 29, 2013
Mr. Terry Edwards
Executive Director
Agenda
• SoSE&I Directorate Overview • COE
– FACE & VICTORY Supporting COE
• Network Integration Evaluation • Agile Process and Industry Participation • Capability Set 13 Synchronized Fielding • Summary
SoSE&I – System of Systems Engineering & Integration COE – Common Operating Environment
FACE – Future Airborne Capability Environment VICTORY – Vehicular Integration for C4ISR/EW Interoperability
NIE – Network Integration Evaluation RTSCE – Real Time, Safety Critical, Embedded RTIF – Real Time Interoperability Framework
CS – Capability Set
2
System of Systems Engineering & Integration (SoSE&I)
3
To be the focal point for System of Systems Engineering and Integration across the Army’s materiel development community
Provide coordinated system of systems analysis, engineering, architectural and integration products to facilitate how the Army efficiently shapes, manages, validates and synchronizes the fielding of integrated materiel capabilities
• Develop Army SoS Integrated Architectures to deliver current and future Capability Sets. • Provide SoS engineering expertise to support current Army decisions. • Support Program Objective Memorandum (POM) process to implement SoS architecture decisions and fund integrated capability sets. • Ensure acquisition programs comply with SoS architecture through integrated testing. • Lead the ASAALT implementation of the Agile Process. • Lead technology integration efforts for the Army. • Ensure the coordinated fielding of integrated capability sets.
Vision Mission Statement
Goals
SoSE&I Leadership Organization Chart
Deputy for Acquisition
& System Mgt MG Harold Greene
ADASM Ross Guckert
SoSE&I Executive Director
Terry Edwards
Chief of Staff COL Kevin
Pope
Director SoSI COL Robert Carpenter
DDASM BG Michael Williamson
ASA(ALT) CIO COL Darrell
Gregg
Director SoSE COL John Zavarelli
SoSE&I Deputy Director Richard Cozby
4
SoS Engineering and Integration Model
5
SoSE&I Key Activities
• SoS Architecture for Tactical Formations in support of: – Program Objective Memorandum (POM) Build – Portfolio Shaping – NIE – Capability Set Fielding
• Systems Engineering program support • Common Operating Environment (COE) • Lab Based Risk Reduction for NIE • Integration & Interoperability Evaluation (I2E) • Network Evaluation Environment (NIE) • Capability Set Fielding Synchronization
6
Common Operating Environment (COE)
7
Inte
r-A
gen
cy Jo
int
Arm
y
Coaliti
on
ASA(ALT) V5.02 11/02/12
Systems Capability Development Reference Framework
8
What is the COE?
9
GENERATING FORCE
TACTICAL EDGE
• Mobile/Handheld CE-PEO Soldier • Mounted CE - PEO C3T • Command Post CE - PEO IEW&S & C3T • Data Center/Cloud/Generating Force CE - PEO EIS • Sensor CE - PEO IEW&S • Real Time /Safety Critical/Embedded CE - PEO Aviation
ASA(ALT) Strategy: Each CE Converge to Common
Foundation then Evolve
CE LEADS:
Organized into Six Computing Environments (CEs)
The COE is an approved set of Computing Technologies &
Standards that enable secure and interoperable
applications to be developed and executed rapidly across a variety
of computing environments or CEs.
What is VICTORY?
• Common Data Bus enables Plug & Play integration of C4ISR/EW
• Shared smart displays • Common Time & location
distribution • Multiple Independent Levels
of Security (MILS)-based IA solution
• Processing hardware determined by platform owner
• Development and integration of new applications consistent with COE
• Standards and framework for integrating elements from multiple COE Computing Environments co-existing on a platform
* Source: VICTORY Briefing, Apr 2011
* VICTORY Next Generation Enhancements
VICTORY provides the interface protocols, standards, data formats and architectures that are the means to achieve the initial goals set for VICTORY.
• A software computing environment to enable product lines for military Aviation • The FACE architecture is comprised of a set of “segments” where variance occurs • Horizontal and vertical interfaces defined as part of FACE
What is FACE?
FACE – Future Airborne Capability Environment OFP – Operational Flight Program
CE – Computing Environment
11
Network Integration Evaluation (NIE)
12
13
• A Series of Semi-Annual Evaluations Designed to Assess Capabilities and Integrate & Mature the Army’s Network
• Aligns Networked Programs in One Place, Integrated into the Broader Capability Set Architecture
• Combines Test & Evaluation to Integrate Network Components in one Operational Venue
• Provides Valuable Soldier Feedback
• Leverages Industry and Evaluate Emerging Network Capabilities
• Validate Capability Set Prior to Fielding
• Refines TTPs/SOPs of the baseline
• Establish and refine supportable concept and SOP
Network Integrated Evaluation What is the NIE? What We Have Accomplished
• Executed 4 NIEs: 143 Systems Under Evaluation
(SUEs) evaluated, 18 Systems Under Test (SUTs)
completed
• Established an Integrated Network Baseline
• Aligned PORs to Capability Sets
• Validated Capability Set 13 Prior to Fielding
• Reduced the Integration Burden on the Warfighter
• Cost avoidance through integrated OT events and
integration of systems
• Findings restructured two programs (JTRS Ground
Mobile Radio (GMR) and Nett Warrior) – Army cost
avoidance: ~$6B
Achieve a global, single Joint standards-based and versatile Network by 2020 with an effective modernization & sustainment strategy that meets Combatant
Commander’s and Senior leader’s requirements across the full range of military and business operations
Why NIE? (The Army culture adapting to current information environment) 1. One stop shop to do the required Operational testing
(one unit at the same place so less cost and less turbulence in the Army)
2. Integrated network, baselined and upgraded, new systems and technologies tested prior to fielding in theater.
3. Testing new technologies that could provide leap-ahead capabilities to the deploying warfighter.
Agile Process Overview
14
Phase 0
Define Gaps and Near Term
Requirements
Lead: TRADOC
Phase I
Solicit Potential Solutions
Lead: ASA(ALT)
Phase II
Candidate Assessment
Lead: ASA(ALT)
Phase III
Evaluation Preparation
Lead: BMC /ATEC
Phase IV
Integrated Rehearsal
Lead: ASA(ALT)/ATEC
Phase V
Integrated Evaluation
Lead: BMC/ATEC
Phase VI
Network Implementation
Plan
Lead: ARSTAF
0 1 2 3
Decision Point 1 determines Potential Solutions based on five assessment criteria. Industry is contacted on next step.
Decision Point 2 Recommended Approved Selection List of who will participate at NIE. Industry contacted.
Decision Point 3 Approved HQDA Position on Solution Way Forward and Procurement. Industry contacted after this decision.
Decision Point 0 recommends Objectives developed in conjunction with TRADOC approved Gaps and Near Term Requirements.
Systems Under Evaluation
Tech Interchange Meeting (SUE TIM)
ACP 3 STAR GOSC
Horseblanket Architecture Development
VALEX COMMEX LOADEX
PILOT
New Equipment Training
LM 1-2 STAR
GOSC
NIE XX.X
Sources Sought & Govt Tech Call memo
ACP 3 Star GOSC
RFP Contract Award
CSA/VCSA Azimuth Checks
LandWarNet/ Mission Command Directorate 15 UNCLASS/FOUO
Phase 0
Define Gaps and Near
Term Requirements
Lead: TRADOC
Phase I
Solicit Potential Solutions
Lead: ASA(ALT)
Phase II
Candidate Assessme
nt Lead:
ASA(ALT)
Phase III
Evaluation Preparation
Lead:
BMC /ATEC
Phase IV
Integrated Rehearsal
Lead:
ASA(ALT)/ATEC
Phase V
Integrated
Evaluation
Lead: BMC/ATEC
Phase VI
Network Implementation
Plan
Lead: ARSTAF
0
NIE Life Cycles
JUL AUG SEP OCT NOV DEC JAN FEB MAR APR MAY JUN JUL AUG SEP
1 2 3
JUN MAY
NIE 13.2 2013
0
DEC JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC JAN FEB
1 2 3
NOV OCT NIE 14.1
2014 Where we are now
DP 0 – 17 July 2012 DP 1 – 19 September 2012 DP 2 – 2 November 2012 DP 3 – September 2013
DP 0 – 6 December 2012 DP 1 – 27 February 2013 DP 2 – 7 May 2013 DP 3 – February 2014
0
JUL AUG SEP OCT NOV DEC JAN FEB MAR
1 2
JUN MAY NIE 14.2
Mid-Tier Joint Integration
DP 0 – 6 Jun 2013 DP 1 – Sept 2013 DP 2 – Nov 2013 DP 3 – Sept 2014
OCT NOV DEC JAN FEB
# Decision Point
Phase 0
Define Gaps and Near
Term Requirements
Lead: TRADOC
Phase I
Solicit Potential Solutions
Lead: ASA(ALT)
Phase II
Candidate Assessme
nt Lead:
ASA(ALT)
Phase III
Evaluation Preparation
Lead:
BMC /ATEC
Phase IV
Integrated Rehearsal
Lead:
ASA(ALT)/ATEC
Phase V
Integrated
Evaluation
Lead: BMC/ATEC
Phase VI
Network Implementation
Plan
Lead: ARSTAF
Phase 0
Define Gaps and Near
Term Requirements
Lead: TRADOC
Phase I
Solicit Potential Solutions
Lead: ASA(ALT)
Phase II
Candidate Assessme
nt Lead:
ASA(ALT)
Phase III
Evaluation Preparation
Lead:
BMC /ATEC
Phase IV
Integrated
Rehearsal Lead:
ASA(ALT)/ATEC
Request for Proposal (RFP) prior to DP 0* Sets conditions for a
JOINT NIE (14.2)
NIE “Firsts”
Horseblanket Architecture Development
Joint/Coalition Planning
NIE Executi
on
16
ARMY 2020
NIE 13.1
NIE 13.2
NIE14.1
Mission Command Movement &
Maneuver Fires Intelligence Sustain Protection
Warfighting Functions
• Air • Land • Sea • Space • Cyber • Human
NIE 14.2
NIE 15.1
- CS 15 Bridge / Intelligence, Surveillance & Reconnaissance
- Joint Participation / LVC-IA
- CS 15 Validation / Doctrinal Concept Assessments /
CYBER
- Expanded JIIM NIE/ BCT Design (3rd BN) /LVC-IA
- CS 14 Bridge / Intelligence Surveillance and Reconnaissance Baseline,
- Battle Command Transport Convergence – Intel and Log; Operational Energy
- CS 14 Validation / Intelligence, Surveillance & Reconnaissance
- Training & Leader Development / Emerging LVC Initiatives / Instrumented HST w/
network
- CS 16 Bridge / Joint Fires
- Expanded JIIM
NIE 15.2 - CS 16 Validation / Joint fires
- Expanded JIIM
NIE is more than a field evaluation … it is the integration, training and validation leading to DOTMLPF recommendations for the Army
Strategic Domains
Direction for Future Integration Evaluations
The TRIAD
17
Training & Doctrine Command – Brigade
Modernization Command
- Responsible for development and execution of the operational evaluations; Compiles final report for signature and provides to Department of the Army for review and approval
Assistant Secretary of the Army (Acquisition, Logistics, &
Technology) – System of Systems
Integration - Responsible for determining Material Solutions for the Army’s Acquisition Process
Army Test & Evaluation Command – Operational Test Command
- Responsible for the planning and execution of operational testing for Programs of Record and DOD oversight programs.
Agile Process and Industry Participation
18
Feedback is not a “Criticism” of your system. It is meant to help you understand what the Army observed for your technology’s strengths and weaknesses
Take Aways for Industry
Awareness of The Agile Process A tool for rapid decisions by informed Senior Leadership Designed as a step by step process through phases Helps the Army fill significant Gaps and Objectives Provides fairness in the selection of systems entering NIE
How to submit a White Paper The information you provide is how we assess your readiness to come to the NIE Clearly identify the gap your system will address Insure you can meet key dates and equipment quantities Submit a complete package on time Check FedBizOps for updates and clarifications
Two way Communication is Critical Requires Active participation in: Face to Face Meetings -Systems Under Evaluation Technical Information Meeting(SUE TIM) is the SME review of the White Paper
that leads to a mutual agreement of what comes to the NIE -The Bull Pen is a comprehensive information exchange covering critical topics from architecture design to spectrum management
Virtual Meetings Use for rapid dissemination of information (Schedule, Equipment, FSR Support, Updates)
19
NIE Key Dates
NIE 14.2 Mid-June 2013 - NIE 14.2 "Sources Sought" and "Gov Call for Mature Solutions" Release 22-29 July 2013 - NIE 14.2 Systems Under Evaluation (SUE) Technical Interchange Meeting (TIM) Late Sep 2013 – NIE 14.2 SUE Selection Notification 7-11 Oct 2013 – NIE 14.2 Bull Pen 2-13 Dec 2013 – SUE delivery to Ft. Bliss/WSMR 20 Jan-28 Mar 2014 – NIE 14.2 New Equipment Training (NET) 28 Apr- 23 May 2014 – NIE 14.2 NIE 15.1 Sept 2013 - RFP Mid Nov 2013 - NIE 15.1 "Sources Sought" and "Gov Call for Mature Solutions" Release 13-17 Jan 2014 - NIE 15.1 Systems Under Evaluation (SUE) Technical Interchange Meeting (TIM) Mid March 2014 – NIE 15.1 SUE Selection Notification 31 Mar – 4 Apr – NIE 14.2 Bull Pen 27 May – 6 Jun 2014 – SUE delivery to Ft. Bliss/WSMR 14 Jul – 19 Sep 2014 – NIE 15.1 New Equipment Training (NET) 20 Oct – 14 Nov 2014 – NIE 15.1
20
Capability Set 13 Synchronized Fielding
21
22
The Capability Set Team
HQDA G-3/5/7 and G8
4
FORSCOM G-3/5/7, G8 and Force Management
3
Trail bosses
ASC
Trail Bosses Coordinate: • Schedules • Logistics • Training • Issues Resolution • Status/Tracking • Communication
TCM
23
AARs from redeploying units gathered by TRADOC, TRADOC Capabilities Managers, and the Center for Army Lessons Learned established the Baseline for Capability Sets
Over 55+ Operational Needs Statements
• Mission Command on the Move: (7 ONS) • Increased Situational Awareness (SA) and
Position Location Information (PLI) for Mounted and Dismounted Elements: (3 ONS)
• Dismounted Radios (MBITR, PRC-150, PRC-152, PRC-117F, PRC-117G): (34 + ONS)
• SIPR / NIPR Access Point (SNAP) Terminals RF-7800 B/W: (4 ONS)
• C5ISR: (1 ONS) • Last Tactical Mile • COIST • Precision Fires Manager • DCGS-A • Mobile Battery Charging
CS 13 Meeting Operational Needs
Major CS 13 Components
24
WIN-T Inc II
FBCB2-BFT II JCR
AN/PRC-117G (v4)
HMS ManPack Radio Rifleman’s Radio
NETT Warrior
Software Block 11-12
Summary
• Budget will drive our strategy for the out years. • SOSE&I is delivering the arch and analysis to shape the future
SOS architectures – Shape the Portfolio and POM investments. – Shaping the COE standards and respective implementation strategies – Shaping the future formation architectures over time both for the Tactical and
Generating Force
• Continue to refined the Agile process and the execution of the NIEs
– Clearly define the gaps and opportunities to industry. – Align technologies with PMs early in the process to facilitate agile procurement of
selected technologies.
• Refining the SoS engineering space; engineering models, artifacts and products.
• Workforce development of the SE and SOS engineering community across ASA(ALT)
25
Questions
ASA(ALT) SOSE&I SharePoint Knowledge Center: https://sp3.kc.army.mil/sosei/kmportal/default.aspx