Integrating Innovative Battle Command Capabilities€¦ · Integrating Innovative Battle Command...
12
15 April 2008 BG Nick Justice Program Executive Officer, PEO Command, Control, Communications Tactical Integrating Innovative Battle Command Capabilities
Transcript of Integrating Innovative Battle Command Capabilities€¦ · Integrating Innovative Battle Command...
15 April 2008
BG Nick JusticeProgram Executive Officer,
PEO Command, Control, Communications Tactical
Integrating Innovative Battle Command Capabilities
Agenda
• Understanding the Battle Command (BC) SoSEnvironment
• Translating S&T Understanding into BC SoSSolutions
• Integrating and Validating New BC Capabilities
• Emerging Innovative Battle Command Technology Examples
3
Understanding the Battle Command SoS Environment
• Richly interconnected; increasingly interdependent
• Cross traditional boundaries… functional, organizational, programmatic
• Increasing scale/scope• Increasing complexity
• Uncertain strategic environment demands agile/adaptive responses
• Information as competitive source of power
• Demand for enterprise and extended enterprise-wide solutions
UltraUltra--LargeLarge--Scale SystemsScale SystemsWellWell--bounded Systemsbounded Systems
Joint BattlespaceArmy Battlespace
Driving Factors Solution Characteristics
Army Service-Based Approach for Tactical BC Capabilities
• Establish warfighteroperational needs– Currently reworking with
“Good Enough Take 2”
• Translate a BC technical vision for Service implementation tooperational capabilities– Converging current and future
force service strategies
• Execute technical vision through a System of Systems engineering and integration approach– Extending to an ASAALT-led
cross Army approach
Service Enabled (Enterprise)• Common Viewers (Web, Client,
Platform)• Interoperable Service infrastructure
Tactical – Strategic (Tact Ent Svr)• Support Range Of Military Operations• Integrate services provided by others
(DCGS-A, COIs, FCS, NECC, …)
Service Enabled (SoS)• Centralized service for Data exchange
using standard schemas• System of BFA Systems, Clients start to
interface via services• Services start to replace servers & utilize
common set of data
Network Enabled• Viewers downloaded on demand • Domain Specific Services that utilize
common set of data • Clients interface thru services• Interoperable across Joint, Coalition &
Multi-agency
Battle Command Technical Vision
Army/USMC
BattleCommand Services
IntelServices
Maneuver
Fires
Engineer
Air
Logistics
…
Logisticsothers
Viewers are a Commodity
Data Access
Pt
EnterpriseServices
Tact Ent Svr
2007-2009 2013-20152010-2012
FCS/NECC
BC/DCGS-AJBC-P
Tact Enterprise Services
DDS
Maneuver
Fires
Engineer
Air
Logistics
…Gateway
BattleCommand Services
IntelServices
APC/Sanctuary
EnterpriseServices
Hub
Tact Ent Svr & ISR/ BC Services/GW COTS/GOTS
OSSoftw
are Framework
BC Processing Node
DCGS-A
Battle CMD FY05-07
FCS \NECC
Army/USMC
Army/USMC
X
Service Enabled (Enterprise)• Common Viewers (Web, Client,
Platform)• Interoperable Service infrastructure
Tactical – Strategic (Tact Ent Svr)• Support Range Of Military Operations• Integrate services provided by others
(DCGS-A, COIs, FCS, NECC, …)
Service Enabled (SoS)• Centralized service for Data exchange
using standard schemas• System of BFA Systems, Clients start to
interface via services• Services start to replace servers & utilize
common set of data
Network Enabled• Viewers downloaded on demand • Domain Specific Services that utilize
common set of data • Clients interface thru services• Interoperable across Joint, Coalition &
Multi-agency
Battle Command Technical Vision
Army/USMC
BattleCommand Services
IntelServices
Maneuver
Fires
Engineer
Air
Logistics
…
Logisticsothers
Viewers are a Commodity
Data Access
Pt
EnterpriseServices
Tact Ent Svr
2007-2009 2013-20152010-2012
FCS/NECC
BC/DCGS-AJBC-P
Tact Enterprise Services
DDS
Maneuver
Fires
Engineer
Air
Logistics
…Gateway
BattleCommand Services
IntelServices
APC/Sanctuary
EnterpriseServices
Hub
Tact Ent Svr & ISR/ BC Services/GW COTS/GOTS
OSSoftw
are Framework
BC Processing Node
DCGS-A
Battle CMD FY05-07
FCS \NECC
Army/USMC
Army/USMC
X
Service Enabled (Enterprise)• Common Viewers (Web, Client,
Platform)• Interoperable Service infrastructure
Tactical – Strategic (Tact Ent Svr)• Support Range Of Military Operations• Integrate services provided by others
(DCGS-A, COIs, FCS, NECC, …)
Service Enabled (SoS)• Centralized service for Data exchange
using standard schemas• System of BFA Systems, Clients start to
interface via services• Services start to replace servers & utilize
common set of data
Network Enabled• Viewers downloaded on demand • Domain Specific Services that utilize
common set of data • Clients interface thru services• Interoperable across Joint, Coalition &
Multi-agency
Battle Command Technical Vision
Army/USMC
BattleCommand Services
IntelServices
Maneuver
Fires
Engineer
Air
Logistics
…
Logisticsothers
Viewers are a Commodity
Data Access
Pt
EnterpriseServices
Tact Ent Svr
2007-2009 2013-20152010-2012
FCS/NECC
BC/DCGS-AJBC-P
Tact Enterprise Services
DDS
Maneuver
Fires
Engineer
Air
Logistics
…Gateway
BattleCommand Services
IntelServices
APC/Sanctuary
EnterpriseServices
Hub
Tact Ent Svr & ISR/ BC Services/GW COTS/GOTS
OSSoftw
are Framework
BC Processing Node
DCGS-A
Battle CMD FY05-07
FCS \NECC
Army/USMC
Army/USMC
X
39
Network Technical Vision
Terrestrial Network-centricMBCT
SATCOMNetwork-centricMBCT
1. Everything over IP / Single Network
3. Increased Mobility
2013-20152010-20122007-2009
2. Increased Capacity for Applications
4. Extend Network to Lower EchelonsNetwork ObjectivesNetwork Objectives
Current Network Capability
• Introduction of IP-based transport (TDMA SATCOM) and services (VOIP) – JNN
• Mix of IP and Legacy Circuit-switched Network –JNN/CPP/MBCOTM/SSS…
• IPV6 – All systems• Regional Hubs for reachback to APCs JNN• Additional satellite resources (Ka) JNN• Fixed network with some limited OTM capability
for BDE and above Cdrs JNN/MBCOTM• Limited wireless to extend the network around
and between fixed CPs NOT FUNDED (CPP?)• EPLRS-XF- extends operating band • Standalone NETOPS/Initialization tools JNN
Integrated Network• IP-based transport WAN for interoperability• Common Transport Waveform, IA, and QoS
architecture (NCW + HNW)• Circuit-switch connections pushed to the
edge of the network• Increased SATCOM and LOS data rates• Terrestrial WAN down to all Bns• Improved L-band for FBCB2/BFT• Introduce Mobile WAN for TOCs• Introduce Mobile SATCOM down to
Company for data and limited voice (SNE)• Wireless to extend the network from CPs• Introduce initial integrated NETOPS
Inc 1aInc 1a Inc 1b,2Inc 1b,2 Inc 3Inc 3
11
2233
44
11
22
3344
Distributed Network• Common pure IP-based transport WAN
for FCS and non-FCS-equipped units• Support distributed network for SOA• Add Airborne layer for additional
network robustness, capacity and mobility
• Add additional WAN capability in larger densities at lower echelons via FCS
• Extend network via JTRS GMR/HMS• Add GBS capability down to Company• Fully integrated NETOPS
11
2233
44
5. Simplify Operation
5555
55
39
Network Technical Vision
Terrestrial Network-centricMBCT
SATCOMNetwork-centricMBCT
1. Everything over IP / Single Network
3. Increased Mobility
2013-20152010-20122007-2009
2. Increased Capacity for Applications
4. Extend Network to Lower EchelonsNetwork ObjectivesNetwork Objectives
Current Network Capability
• Introduction of IP-based transport (TDMA SATCOM) and services (VOIP) – JNN
• Mix of IP and Legacy Circuit-switched Network –JNN/CPP/MBCOTM/SSS…
• IPV6 – All systems• Regional Hubs for reachback to APCs JNN• Additional satellite resources (Ka) JNN• Fixed network with some limited OTM capability
for BDE and above Cdrs JNN/MBCOTM• Limited wireless to extend the network around
and between fixed CPs NOT FUNDED (CPP?)• EPLRS-XF- extends operating band • Standalone NETOPS/Initialization tools JNN
Integrated Network• IP-based transport WAN for interoperability• Common Transport Waveform, IA, and QoS
architecture (NCW + HNW)• Circuit-switch connections pushed to the
edge of the network• Increased SATCOM and LOS data rates• Terrestrial WAN down to all Bns• Improved L-band for FBCB2/BFT• Introduce Mobile WAN for TOCs• Introduce Mobile SATCOM down to
Company for data and limited voice (SNE)• Wireless to extend the network from CPs• Introduce initial integrated NETOPS
Inc 1aInc 1a Inc 1b,2Inc 1b,2 Inc 3Inc 3
11
2233
44
11
22
3344
Distributed Network• Common pure IP-based transport WAN
for FCS and non-FCS-equipped units• Support distributed network for SOA• Add Airborne layer for additional
network robustness, capacity and mobility
• Add additional WAN capability in larger densities at lower echelons via FCS
• Extend network via JTRS GMR/HMS• Add GBS capability down to Company• Fully integrated NETOPS
11
2233
44
5. Simplify Operation
5555
55
39
Network Technical Vision
Terrestrial Network-centricMBCT
SATCOMNetwork-centricMBCT
1. Everything over IP / Single Network
3. Increased Mobility
2013-20152010-20122007-2009
2. Increased Capacity for Applications
4. Extend Network to Lower EchelonsNetwork ObjectivesNetwork Objectives
Current Network Capability
• Introduction of IP-based transport (TDMA SATCOM) and services (VOIP) – JNN
• Mix of IP and Legacy Circuit-switched Network –JNN/CPP/MBCOTM/SSS…
• IPV6 – All systems• Regional Hubs for reachback to APCs JNN• Additional satellite resources (Ka) JNN• Fixed network with some limited OTM capability
for BDE and above Cdrs JNN/MBCOTM• Limited wireless to extend the network around
and between fixed CPs NOT FUNDED (CPP?)• EPLRS-XF- extends operating band • Standalone NETOPS/Initialization tools JNN
Integrated Network• IP-based transport WAN for interoperability• Common Transport Waveform, IA, and QoS
architecture (NCW + HNW)• Circuit-switch connections pushed to the
edge of the network• Increased SATCOM and LOS data rates• Terrestrial WAN down to all Bns• Improved L-band for FBCB2/BFT• Introduce Mobile WAN for TOCs• Introduce Mobile SATCOM down to
Company for data and limited voice (SNE)• Wireless to extend the network from CPs• Introduce initial integrated NETOPS
Inc 1aInc 1a Inc 1b,2Inc 1b,2 Inc 3Inc 3
11
2233
44
11
22
3344
Distributed Network• Common pure IP-based transport WAN
for FCS and non-FCS-equipped units• Support distributed network for SOA• Add Airborne layer for additional
network robustness, capacity and mobility
• Add additional WAN capability in larger densities at lower echelons via FCS
• Extend network via JTRS GMR/HMS• Add GBS capability down to Company• Fully integrated NETOPS
11
2233
44
5. Simplify Operation
5555
55
88
2013-20152010-20122007-2009
Enabling Capability Vision
Transformation Enablers
• Achieve common Mounted Battle Command on the Move (MBCOTM) platform across Army and USMC
• Improve Carrier Vehicle armor protection (RWS on TWVs) with initial In Dash C4/EW integration
• Enhance Modular Command Post laydown – CP Standardization
• Engineer SOA- and WIN-T-centric transition of SoS architecture across Ground Forces through expanded use of CHS.
Current Modular Force Enablers
• Transition mobile aerial battle command platform for HLD support
• Field basic Carrier Vehicles (Armored and Unarmored RWS on HMMWVs) with bolt on C4 integration
• Utilize Single Integrated Command Post System solution for TOCs
• Engineer consistent SoS solutions across PEOs including SO1
• Provide interoperable, compatible, and survivable hardware through Common Hardware Systems (CHS)
Future Modular Force Enablers
• Transition to FCS ground mobile command platform
• Achieve fully mobile joint CPs• Introduce Joint Light Tactical Vehicle
(JLTV) with objective In Dash C4/EW integration
• Engineer Future Modular Force transition of SoS architecture including SO3 and Objective FCS
• Continue to utilize CHS for Future Force hardware requirements.
A2C2S maintenance A2C2S maintenance
SWAP enhancements for tactical environment
TOC and BCOTM platform enhancements
FCS
Current Force
88
2013-20152010-20122007-2009
Enabling Capability Vision
Transformation Enablers
• Achieve common Mounted Battle Command on the Move (MBCOTM) platform across Army and USMC
• Improve Carrier Vehicle armor protection (RWS on TWVs) with initial In Dash C4/EW integration
• Enhance Modular Command Post laydown – CP Standardization
• Engineer SOA- and WIN-T-centric transition of SoS architecture across Ground Forces through expanded use of CHS.
Current Modular Force Enablers
• Transition mobile aerial battle command platform for HLD support
• Field basic Carrier Vehicles (Armored and Unarmored RWS on HMMWVs) with bolt on C4 integration
• Utilize Single Integrated Command Post System solution for TOCs
• Engineer consistent SoS solutions across PEOs including SO1
• Provide interoperable, compatible, and survivable hardware through Common Hardware Systems (CHS)
Future Modular Force Enablers
• Transition to FCS ground mobile command platform
• Achieve fully mobile joint CPs• Introduce Joint Light Tactical Vehicle
(JLTV) with objective In Dash C4/EW integration
• Engineer Future Modular Force transition of SoS architecture including SO3 and Objective FCS
• Continue to utilize CHS for Future Force hardware requirements.
A2C2S maintenance A2C2S maintenance
SWAP enhancements for tactical environment
TOC and BCOTM platform enhancements
FCS
Current Force
88
2013-20152010-20122007-2009
Enabling Capability Vision
Transformation Enablers
• Achieve common Mounted Battle Command on the Move (MBCOTM) platform across Army and USMC
• Improve Carrier Vehicle armor protection (RWS on TWVs) with initial In Dash C4/EW integration
• Enhance Modular Command Post laydown – CP Standardization
• Engineer SOA- and WIN-T-centric transition of SoS architecture across Ground Forces through expanded use of CHS.
Current Modular Force Enablers
• Transition mobile aerial battle command platform for HLD support
• Field basic Carrier Vehicles (Armored and Unarmored RWS on HMMWVs) with bolt on C4 integration
• Utilize Single Integrated Command Post System solution for TOCs
• Engineer consistent SoS solutions across PEOs including SO1
• Provide interoperable, compatible, and survivable hardware through Common Hardware Systems (CHS)
Future Modular Force Enablers
• Transition to FCS ground mobile command platform
• Achieve fully mobile joint CPs• Introduce Joint Light Tactical Vehicle
(JLTV) with objective In Dash C4/EW integration
• Engineer Future Modular Force transition of SoS architecture including SO3 and Objective FCS
• Continue to utilize CHS for Future Force hardware requirements.
A2C2S maintenance A2C2S maintenance
SWAP enhancements for tactical environment
TOC and BCOTM platform enhancements
FCS
Current Force
…
Ope
ratio
nal
Cap
abili
ties
Serv
ices
Syst
em o
fSy
stem
s
DIV/BCT
XX
AOC
JTF
Tactical TransportTactical TransportTactical Transport
Command PostsCommand PostsCommand Posts
Satellite (WIN-T, SMART-T, GMF…)Radio (LOS, SINCGARS, EPLRS, JTRS, …)
Net OPS, Firewalls
Net CentricNet CentricBC Server SuiteBC Server Suite
• Enterprise Services: Email, Security, Web Portal, System Updates, Data Dissemination.
• Interoperability Services: Web Apps, C2 Data & Services, Etc.
Commander & Key Leader SystemStaff User Notebook
Command PostCommand Post--Based BCBased BC
Platform/Platform/Dismount BCDismount BC
RobustNetworks
DisadvantagedNetworks
Messaging
Services
Tactical (FBCB2/BFT),Fires (PFED/FOS/Radar…),
Air (IDM, EDM),Logistics (MTS),
Dismounted Force Handhelds
Gateway
ApplicationsServicesNetworksUtilities
Infrastructure
ApplicationsServicesNetworksUtilities
Infrastructure
Instituting Cross-Army SoS Engineering
Tier 1
Tier 2
Tier 3
• Trade studies and analysis in support of capability roadmaps
• Synchronize enterprise level development• Facilitate cross-portfolio issue resolution
Lead: ASAALT
Vision, programmatic, policy, decisions
Execution plan & resolution
Execution/Solution
Lead: ASAALT with PEO SoSE• Requirements flow down, decomposition,
and adjudication• Integrated schedule and CM
PEO/PM SoS Engineering Teams:• Technical Execution,
Implementation • Trades supported by R&D
Community
Lead: PEOs
Req
ts
Res
ourc
e
Acqu
ire
Sus
tain
… …
Managing depth and breadth of SoS Engineering issues vertically (within) and horizontally (between) C4ISR capability portfolios
Managing depth and breadth of SoS Engineering issues vertically (within) and horizontally (between) C4ISR capability portfolios
An S&T Innovator’s ResponseAdapting to the BC SoS Challenge
S&T Transition Challenge
• Establish a Shared Vision– Demonstrate operational understanding
of the Warfighting domain
• Create Product Partnerships– Partner with high impact programs to fill
critical technical/operational gaps
• Align Execution Processes– Link S&T solution rollout with aggressive
Modular Force capability block development and fielding
Evolution v. Revolution in fiscally constrained environment
Service Enabled (Enterprise)• Common Viewers (Web, Client,
Platform)• Interoperable Service infrastructure
Tactical – Strategic (Tact Ent Svr)• Support Range Of Military Operations• Integrate services provided by others
(DCGS-A, COIs, FCS, NECC, …)
Service Enabled (SoS)• Centralized service for Data exchange
using standard schemas• System of BFA Systems, Clients start to
interface via services• Services start to replace servers & utilize
common set of data
Network Enabled• Viewers downloaded on demand • Domain Specific Services that utilize
common set of data • Clients interface thru services• Interoperable across Joint, Coalition &
Multi-agency
Battle Command Technical Vision
Army/USMC
BattleCommand Services
IntelServices
Maneuver
Fires
Engineer
Air
Logistics
…
Logisticsothers
Viewers are a Commodity
Data Access
Pt
EnterpriseServices
Tact Ent Svr
2007-2009 2013-20152010-2012
FCS/NECC
BC/DCGS-AJBC-P
Tact Enterprise Services
DDS
Maneuver
Fires
Engineer
Air
Logistics
…Gateway
BattleCommand Services
IntelServices
APC/Sanctuary
EnterpriseServices
Hub
Tact Ent Svr & ISR/ BC Services/GW COTS/GOTS
OSSoft
war
e Framework
BC Processing Node
DCGS-A
Battle CMD FY05-07
FCS \NECC
Army/USMC
Army/USMC
X
Service Enabled (Enterprise)• Common Viewers (Web, Client,
Platform)• Interoperable Service infrastructure
Tactical – Strategic (Tact Ent Svr)• Support Range Of Military Operations• Integrate services provided by others
(DCGS-A, COIs, FCS, NECC, …)
Service Enabled (SoS)• Centralized service for Data exchange
using standard schemas• System of BFA Systems, Clients start to
interface via services• Services start to replace servers & utilize
common set of data
Network Enabled• Viewers downloaded on demand • Domain Specific Services that utilize
common set of data • Clients interface thru services• Interoperable across Joint, Coalition &
Multi-agency
Battle Command Technical Vision
Army/USMC
BattleCommand Services
IntelServices
Maneuver
Fires
Engineer
Air
Logistics
…
Logisticsothers
Viewers are a Commodity
Data Access
Pt
EnterpriseServices
Tact Ent Svr
2007-2009 2013-20152010-2012
FCS/NECC
BC/DCGS-AJBC-P
Tact Enterprise Services
DDS
Maneuver
Fires
Engineer
Air
Logistics
…Gateway
BattleCommand Services
IntelServices
APC/Sanctuary
EnterpriseServices
Hub
Tact Ent Svr & ISR/ BC Services/GW COTS/GOTS
OSSoftw
are Framework
BC Processing Node
DCGS-A
Battle CMD FY05-07
FCS \NECC
Army/USMC
Army/USMC
X
Service Enabled (Enterprise)• Common Viewers (Web, Client,
Platform)• Interoperable Service infrastructure
Tactical – Strategic (Tact Ent Svr)• Support Range Of Military Operations• Integrate services provided by others
(DCGS-A, COIs, FCS, NECC, …)
Service Enabled (SoS)• Centralized service for Data exchange
using standard schemas• System of BFA Systems, Clients start to
interface via services• Services start to replace servers & utilize
common set of data
Network Enabled• Viewers downloaded on demand • Domain Specific Services that utilize
common set of data • Clients interface thru services• Interoperable across Joint, Coalition &
Multi-agency
Battle Command Technical Vision
Army/USMC
BattleCommand Services
IntelServices
Maneuver
Fires
Engineer
Air
Logistics
…
Logisticsothers
Viewers are a Commodity
Data Access
Pt
EnterpriseServices
Tact Ent Svr
2007-2009 2013-20152010-2012
FCS/NECC
BC/DCGS-AJBC-P
Tact Enterprise Services
DDS
Maneuver
Fires
Engineer
Air
Logistics
…Gateway
BattleCommand Services
IntelServices
APC/Sanctuary
EnterpriseServices
Hub
Tact Ent Svr & ISR/ BC Services/GW COTS/GOTS
OSSoftw
are Framework
BC Processing Node
DCGS-A
Battle CMD FY05-07
FCS \NECC
Army/USMC
Army/USMC
X
39
Network Technical Vision
Terrestrial Network-centricMBCT
SATCOMNetwork-centricMBCT
1. Everything over IP / Single Network
3. Increased Mobility
2013-20152010-20122007-2009
2. Increased Capacity for Applications
4. Extend Network to Lower EchelonsNetwork ObjectivesNetwork Objectives
Current Network Capability
• Introduction of IP-based transport (TDMA SATCOM) and services (VOIP) – JNN
• Mix of IP and Legacy Circuit-switched Network –JNN/CPP/MBCOTM/SSS…
• IPV6 – All systems• Regional Hubs for reachback to APCs JNN• Additional satellite resources (Ka) JNN• Fixed network with some limited OTM capability
for BDE and above Cdrs JNN/MBCOTM• Limited wireless to extend the network around
and between fixed CPs NOT FUNDED (CPP?)• EPLRS-XF- extends operating band • Standalone NETOPS/Initialization tools JNN
Integrated Network• IP-based transport WAN for interoperability• Common Transport Waveform, IA, and QoS
architecture (NCW + HNW)• Circuit-switch connections pushed to the
edge of the network• Increased SATCOM and LOS data rates• Terrestrial WAN down to all Bns• Improved L-band for FBCB2/BFT• Introduce Mobile WAN for TOCs• Introduce Mobile SATCOM down to
Company for data and limited voice (SNE)• Wireless to extend the network from CPs• Introduce initial integrated NETOPS
Inc 1aInc 1a Inc 1b,2Inc 1b,2 Inc 3Inc 3
11
2233
44
11
22
3344
Distributed Network• Common pure IP-based transport WAN
for FCS and non-FCS-equipped units• Support distributed network for SOA• Add Airborne layer for additional
network robustness, capacity and mobility
• Add additional WAN capability in larger densities at lower echelons via FCS
• Extend network via JTRS GMR/HMS• Add GBS capability down to Company• Fully integrated NETOPS
11
2233
44
5. Simplify Operation
5555
55
39
Network Technical Vision
Terrestrial Network-centricMBCT
SATCOMNetwork-centricMBCT
1. Everything over IP / Single Network
3. Increased Mobility
2013-20152010-20122007-2009
2. Increased Capacity for Applications
4. Extend Network to Lower EchelonsNetwork ObjectivesNetwork Objectives
Current Network Capability
• Introduction of IP-based transport (TDMA SATCOM) and services (VOIP) – JNN
• Mix of IP and Legacy Circuit-switched Network –JNN/CPP/MBCOTM/SSS…
• IPV6 – All systems• Regional Hubs for reachback to APCs JNN• Additional satellite resources (Ka) JNN• Fixed network with some limited OTM capability
for BDE and above Cdrs JNN/MBCOTM• Limited wireless to extend the network around
and between fixed CPs NOT FUNDED (CPP?)• EPLRS-XF- extends operating band • Standalone NETOPS/Initialization tools JNN
Integrated Network• IP-based transport WAN for interoperability• Common Transport Waveform, IA, and QoS
architecture (NCW + HNW)• Circuit-switch connections pushed to the
edge of the network• Increased SATCOM and LOS data rates• Terrestrial WAN down to all Bns• Improved L-band for FBCB2/BFT• Introduce Mobile WAN for TOCs• Introduce Mobile SATCOM down to
Company for data and limited voice (SNE)• Wireless to extend the network from CPs• Introduce initial integrated NETOPS
Inc 1aInc 1a Inc 1b,2Inc 1b,2 Inc 3Inc 3
11
2233
44
11
22
3344
Distributed Network• Common pure IP-based transport WAN
for FCS and non-FCS-equipped units• Support distributed network for SOA• Add Airborne layer for additional
network robustness, capacity and mobility
• Add additional WAN capability in larger densities at lower echelons via FCS
• Extend network via JTRS GMR/HMS• Add GBS capability down to Company• Fully integrated NETOPS
11
2233
44
5. Simplify Operation
5555
55
39
Network Technical Vision
Terrestrial Network-centricMBCT
SATCOMNetwork-centricMBCT
1. Everything over IP / Single Network
3. Increased Mobility
2013-20152010-20122007-2009
2. Increased Capacity for Applications
4. Extend Network to Lower EchelonsNetwork ObjectivesNetwork Objectives
Current Network Capability
• Introduction of IP-based transport (TDMA SATCOM) and services (VOIP) – JNN
• Mix of IP and Legacy Circuit-switched Network –JNN/CPP/MBCOTM/SSS…
• IPV6 – All systems• Regional Hubs for reachback to APCs JNN• Additional satellite resources (Ka) JNN• Fixed network with some limited OTM capability
for BDE and above Cdrs JNN/MBCOTM• Limited wireless to extend the network around
and between fixed CPs NOT FUNDED (CPP?)• EPLRS-XF- extends operating band • Standalone NETOPS/Initialization tools JNN
Integrated Network• IP-based transport WAN for interoperability• Common Transport Waveform, IA, and QoS
architecture (NCW + HNW)• Circuit-switch connections pushed to the
edge of the network• Increased SATCOM and LOS data rates• Terrestrial WAN down to all Bns• Improved L-band for FBCB2/BFT• Introduce Mobile WAN for TOCs• Introduce Mobile SATCOM down to
Company for data and limited voice (SNE)• Wireless to extend the network from CPs• Introduce initial integrated NETOPS
Inc 1aInc 1a Inc 1b,2Inc 1b,2 Inc 3Inc 3
11
2233
44
11
22
3344
Distributed Network• Common pure IP-based transport WAN
for FCS and non-FCS-equipped units• Support distributed network for SOA• Add Airborne layer for additional
network robustness, capacity and mobility
• Add additional WAN capability in larger densities at lower echelons via FCS
• Extend network via JTRS GMR/HMS• Add GBS capability down to Company• Fully integrated NETOPS
11
2233
44
5. Simplify Operation
5555
55
88
2013-20152010-20122007-2009
Enabling Capability Vision
Transformation Enablers
• Achieve common Mounted Battle Command on the Move (MBCOTM) platform across Army and USMC
• Improve Carrier Vehicle armor protection (RWS on TWVs) with initial In Dash C4/EW integration
• Enhance Modular Command Post laydown – CP Standardization
• Engineer SOA- and WIN-T-centric transition of SoS architecture across Ground Forces through expanded use of CHS.
Current Modular Force Enablers
• Transition mobile aerial battle command platform for HLD support
• Field basic Carrier Vehicles (Armored and Unarmored RWS on HMMWVs) with bolt on C4 integration
• Utilize Single Integrated Command Post System solution for TOCs
• Engineer consistent SoS solutions across PEOs including SO1
• Provide interoperable, compatible, and survivable hardware through Common Hardware Systems (CHS)
Future Modular Force Enablers
• Transition to FCS ground mobile command platform
• Achieve fully mobile joint CPs• Introduce Joint Light Tactical Vehicle
(JLTV) with objective In Dash C4/EW integration
• Engineer Future Modular Force transition of SoS architecture including SO3 and Objective FCS
• Continue to utilize CHS for Future Force hardware requirements.
A2C2S maintenance A2C2S maintenance
SWAP enhancements for tactical environment
TOC and BCOTM platform enhancements
FCS
Current Force
88
2013-20152010-20122007-2009
Enabling Capability Vision
Transformation Enablers
• Achieve common Mounted Battle Command on the Move (MBCOTM) platform across Army and USMC
• Improve Carrier Vehicle armor protection (RWS on TWVs) with initial In Dash C4/EW integration
• Enhance Modular Command Post laydown – CP Standardization
• Engineer SOA- and WIN-T-centric transition of SoS architecture across Ground Forces through expanded use of CHS.
Current Modular Force Enablers
• Transition mobile aerial battle command platform for HLD support
• Field basic Carrier Vehicles (Armored and Unarmored RWS on HMMWVs) with bolt on C4 integration
• Utilize Single Integrated Command Post System solution for TOCs
• Engineer consistent SoS solutions across PEOs including SO1
• Provide interoperable, compatible, and survivable hardware through Common Hardware Systems (CHS)
Future Modular Force Enablers
• Transition to FCS ground mobile command platform
• Achieve fully mobile joint CPs• Introduce Joint Light Tactical Vehicle
(JLTV) with objective In Dash C4/EW integration
• Engineer Future Modular Force transition of SoS architecture including SO3 and Objective FCS
• Continue to utilize CHS for Future Force hardware requirements.
A2C2S maintenance A2C2S maintenance
SWAP enhancements for tactical environment
TOC and BCOTM platform enhancements
FCS
Current Force
88
2013-20152010-20122007-2009
Enabling Capability Vision
Transformation Enablers
• Achieve common Mounted Battle Command on the Move (MBCOTM) platform across Army and USMC
• Improve Carrier Vehicle armor protection (RWS on TWVs) with initial In Dash C4/EW integration
• Enhance Modular Command Post laydown – CP Standardization
• Engineer SOA- and WIN-T-centric transition of SoS architecture across Ground Forces through expanded use of CHS.
Current Modular Force Enablers
• Transition mobile aerial battle command platform for HLD support
• Field basic Carrier Vehicles (Armored and Unarmored RWS on HMMWVs) with bolt on C4 integration
• Utilize Single Integrated Command Post System solution for TOCs
• Engineer consistent SoS solutions across PEOs including SO1
• Provide interoperable, compatible, and survivable hardware through Common Hardware Systems (CHS)
Future Modular Force Enablers
• Transition to FCS ground mobile command platform
• Achieve fully mobile joint CPs• Introduce Joint Light Tactical Vehicle
(JLTV) with objective In Dash C4/EW integration
• Engineer Future Modular Force transition of SoS architecture including SO3 and Objective FCS
• Continue to utilize CHS for Future Force hardware requirements.
A2C2S maintenance A2C2S maintenance
SWAP enhancements for tactical environment
TOC and BCOTM platform enhancements
FCS
Current Force
RESOURCES
1
2
3
4
5
6
7
8
9
10
C4ISRPriorities
PEO C3T Top 20 S&T Priorities
Prioritizing Tactical C3 S&T Execution
https://t2matrix.kc.us.army.milhttps://t2matrix.kc.us.army.mil
Technology Transition Matrix (T2Matrix)
Institute an open process to align limited S&T resources with prioritized operational needs and increase transition successes
Institute an open process to align limited S&T resources with prioritized operational needs and increase transition successes
Top 4
PEO C3T
Technology
Gaps
Top 4
PEO C3T
Technology
Gaps
Transitioning S&T Solutions to PORsChallenges
–“Operationalizing”• Delivering Warfighter-Focused v.
Technology Policy-Driven Solutions
* 3 year blocks, with near then-year technoloTime
Tech
nolo
gy C
apab
ility
Exponential Technology Growthin Commercial Products
Typical POR with Minimal Growth -
Essentially Frozen at PDR, CDR
A Piecewise Approximation to
The Growth of Technology *
Source: ASB
–Execution Ownership• Strategizing with PMs
early (and often) on S&T transition
Advancing C4ISR SoS M&S Capabilities
Analysis of operational data collected in-theater and used in M&S enabled bandwidth assessments
Insertion of realistic C4ISR effects into live experimentation environments
• Integrated C4ISR Live/Virtual/Constructive Demonstrations and Analyses– Enables C4ISR System of Systems Engineering analyses of
greater scale and accuracy– Relevant across the spectrum of program life cycle– More quickly, more efficiently, resulting in significant cost
savings/avoidance
High-Performance-Computing Army Laboratory for
Live/Virtual/Constructive Experimentation (H.A.L.L.E.)
Instituting Operational Design Reviews
•• TOCFESTTOCFEST–Team C4ISR engineering field study to validate the current
Command Post SoS from 11 Mar to 13 Apr 2008 at Fort Indiantown Gap, PA (FTIG)
Standardizing Command Post baseline architecture – physical and logicalEvaluating technical and operational effects of configuration changesSetting conditions for ongoing C4ISR SoS operational design reviews
SBCT Main CP (CP 2)
SBCT TAC CP (CP1)Battalion CP
XBTJ
C4 Operations
CDRTENTSmall
SICPS
Small SICPSACP
CPP
DTSS
2.4mKu
XBTJ
PAO DVIDSCSS
VSAT
Sustainment
Curren
t
Operatio
ns
Plans
LSD
LSD
LSDLSD
Movement and
Maneuver / Protection
CPP
MED
TM
SS
MED
TM
SS
MED TMSS
10 Kw PU
GRT
SMART-T
10 Kw PU
Large TMSS
MED
TM
SS
JNN ***
MJQ-41(60 kW PP)
Small SICPS
CDRTENT
Small SICPS
Entrance
Fire Support /
Protection
Intelligence
LSD
10 Kw PU
CGS**
ACT-E**
ADAM
10 Kw PUTrojan Spirit
**
**
XBTJXBTJ
C4 OperationsC4 Operations
CDRTENTSmall
SICPS
Small SICPSACPACP
CPP
DTSS
2.4mKu 2.4mKu
XBTJXBTJ
PAO DVIDSPAO
DVIDSCSSVSATCSSVSAT
Sustainment
Sustainment
Curren
t
Operatio
ns
Plans
LSD
Plans
LSDLSD
LSD
LSDLSDLSD
LSD
LSDLSDLSD
LSD
Movement and
Maneuver / Protection
Movement and
Maneuver / Protection
CPP
MED
TM
SSM
ED T
MSS
MED
TM
SSM
ED T
MSS
MED TMSSMED TMSS
10 Kw PU10 Kw PU
GRTGRT
SMART-TSMART-T
10 Kw PU10 Kw PU
Large TMSS
MED
TM
SSM
ED T
MSS
JNN ***JNNJNN ***
MJQ-41(60 kW PP)
MJQ-41(60 kW PP)
Small SICPS
CDRTENT
Small SICPS
Entrance
Fire Support /
Protection
Fire Support /
Protection
Intelligence
LSDLSD
10 Kw PU10 Kw PU
CGS**
CGS**
ACT-E**
ACT-E**
ACT-E**
ADAM
10 Kw PUTrojan Spirit
**
**10 Kw PU
Trojan Spirit
**
**
CPP-A
2.4mKu
CPP-B
Small SICPS
ACP
LSD
Current Ops1 Current O
ps2
MED
TMSS
MED
TMSS
MJQ-48(15 kW PP) CPP-A
2.4mKu 2.4mKu
CPP-B
Small SICPS
ACP
Small SICPS
ACPACP
LSDLSD
Current Ops1 Current O
ps2
MED
TMSS
MED
TMSS
MED
TMSS
MED
TMSS
MJQ-48(15 kW PP)
MJQ-48(15 kW PP)
CPN
CSSVSAT
GRT
MJQ-48(15 kW PP)CPP-A
CPP-B
Small SICPS
ACP
LSDCurrent Ops
Sustainmen
t
MED
TMSS
MED
TMSS
LSD
CPNCPN
CSSVSATCSSVSAT
GRTGRT
MJQ-48(15 kW PP)
MJQ-48(15 kW PP)CPP-A
CPP-B
Small SICPS
ACP
Small SICPS
ACPACP
LSDLSD
Current Ops
Sustainmen
t
MED
TMSS
MED
TMSS
MED
TMSS
MED
TMSS
LSDLSD
Selected BC Enabling Technologies• neXt Generation Communications
(XG) Dynamic Spectrum Access Technology– Maximize access to and use of
required tactical spectrumMaximum Amplitudes
Frequency (MHz)
Am
plid
ue (d
Bm
)
Heavy Use
Sparse Use
Heavy Use
Medium Use
Less than 6% OccupancyLess than 6% Occupancy
Maximum Amplitudes
Frequency (MHz)
Am
plid
ue (d
Bm
)
Heavy Use
Sparse Use
Heavy Use
Medium Use
Less than 6% OccupancyLess than 6% Occupancy
• Disruption Tolerant Networking (DTN)– Assure tactical C2 info
delivery when no network path exists
• Chip Scale Atomic Clock– Deliver precise timing and
positioning for the “last tactical mile”
• Serious Gaming– Enhance C4ISR training
environments, linking Command Post capability usage with realistic tactical scenarios
Questions?
