exploring the role of future systems on the battlefield · ppt file · web view2012-10-03 ·...

11

The Multilateral The Multilateral Interoperability Interoperability

ProgrammeProgramme

““Imitation is the Sincerest Form of Imitation is the Sincerest Form of Flattery”Flattery”

(Part 2)(Part 2)COL Stuart A. WhiteheadCOL Stuart A. Whitehead

DirectorDirectorTRADOC Program Integration Office for TRADOC Program Integration Office for

Battle CommandBattle Command

Information Age Metrics Working Group Information Age Metrics Working Group

22 of 15 of 15

WMA Integration WG

Warfighter Mission Area Integrated Warfighter Mission Area Integrated Work Group (WMA IWG) OrganizationWork Group (WMA IWG) Organization

Capability / PolicyWorking Group

(CPWG)

WMA Coordination & Integration

Element (CIE)

Force Development &

Resources Working Group

(FDRWG)

Program Execution

Working Group(PEWG)

Transition Working Group

(TWG)

Cross Discipline Work Parties as

required

Other Army/Joint Bodies

Battle Command GOSC

Battle Command CoC

LWN CoC

Joint Combat Capability Developer

Architecture Working Group

(AWG)

Data Architecture

Sub Group(DASG)

33 of 15 of 15

Functions of WMA Management Functions of WMA Management OrganizationOrganization

Capability / PolicyWorking Group

(CPWG)

WMA IWG

Force Development &

Resources Working Group

(FDRWG)

Program Execution

Working Group(PEWG)

Architecture Working Group

(AWG)

Coordination and Integration Element (CIE):• Monitor program schedule• Integrated life cycle systems engineering• Coordinate integrated program schedule (Synch Matrix/ Roadmap) • Meeting coordination

• Architectures• Data strategy• COI Data Standardization• Capability Block design• Engineering

• Unifying Strategy• Program, Plans Definition/validation• Capability Block Execution • Review new submissions• Tech insertion• Legal basis•

• Force Development• Resources available• POM Development• Allocation based on working groups recommendations & forwarded to CoC • Fielding $$$

• Policy Adherence• Capabilities Definition & Evaluation• Requirements Hierarchy/Traceability• Prioritization• Capability Blocking• Concept of Operation• Concept of Employment• Recommends change• SIM/STIM/Testing Guidance• DOT_LPF• Force Development

• Fielding Schedule •Testing strategy• Test events• External event coordination• SIM/STIM• Training Development• Fielding Synchronization

Army G3/ARCIC Army G6/AIMDASA(ALT)/PEO-C3T Army G8/CAC G8

• Data strategy• COI Data Standardization• Engineering

Data ArchitectureSub Group

(DASG)Army G6/SECJoint/Service participation

NETWARCOMAFC2ISRCMCCDCJFCOM J6/J8

TransitionWorking Group

(TWG)o/o Army G3

44 of 15 of 15

Program IntegrationProgram Integration“NETW

ORK”

FY04 FY08 FY10 FY12 FY14

Army Bde’sModular ConstructEvaluation UABCT w/ Spiraled CapabilitiesFCS UA

UAsUAs

WNWSRW

SOSCOEICS

Unattended Ground SensorsNLOS–Launch System

Intelligent Munitions SystemNLOS C (Preproduction)

Comms Relay PayloadEnhanced EO/IR/LD (UAV)

UAVsNLOS-Cannon (Block 0)

Unmanned Ground Vehicles Battle CommandGIG-3 variants

+ + +

Limited Fusion

SOSCOE

Fusion

SOSCOE

Comms Relay

NDLSOSCOE

FCSProcured in POM 06 -11

M-UAsM-UAs M-UAsM-UAs M-UAs M-UAs

18 of 18FCS Core Systems 3 of 18 4 of 18 7 of 18

E E E

Spiral 1 Spiral 3 Spiral 4Spiral 2

E

DCGS-AWIN-T

CRP Platform

+MBCOTMWIN-T(-)

Complementary Systems (+)

GSTAMIDSGCSS-A

Movement Tracking System

ISR

Sensor to Shooter

C2

AH-64 BLK IIILLDR/MK VII

Q36Excalibur

Shadow PIP

JTRS CL 1JTRS CL 5C2PC / JC2

ACSER/MP

Armed UAV

CDA (Soldier)A2C2S

Combat ID

+

2

FCS Core

Systems;

Capabilities

Capability AssessmentSoftware BlockingABCS 6.4 InteroperabilityJC2 Block 1The NetworkTechnical InsertionsFunding DecisionsTesting SchedulesFielding Plans

55 of 15 of 15

Program AlignmentProgram AlignmentFY 04 FY 05 FY 06 FY 07 FY 08 FY 09 FY 10 FY 11 FY 12 FY 13 FY 14

1Q 2Q 3Q 4Q1Q 2Q 3Q 4Q1Q 2Q 3Q 4Q1Q 2Q 3Q 4Q1Q 2Q 3Q 4Q1Q 2Q 3Q 4Q1Q 2Q 3Q 4Q1Q 2Q 3Q 4Q1Q 2Q 3Q 4Q1Q 2Q 3Q 4Q1Q 2Q 3Q 4Q

Cap B1

Cap B2

SWB 1

SWB 2

SWB 3PREP

FCS SPIRAL 1

FCS SPIRAL 2

FCS SPIRAL 3

SPIRAL 4FCS

SWB 4PREP

SWB 5PREP

SWB 6PREP

SWB 7PREP

SWB 8PREP

Capabilities Blocking (in service periods)

Software Blocking(prep and test periods)

FCS Spirals(tech insertions)

Cap B3

Cap B4

66 of 15 of 15

Capability MigrationCapability Migration

TransitionTransition

CapabilitiesCDRs 7+1Software Blocking

Capability BlockCapability BlockIn-Svc FY-FYIn-Svc FY-FY

Modularity101st…

SystemsGCCSABCS 6.4

CapabilitiesCDRs 7+1CollaborationSoftware Blocking

Capability BlockCapability BlockIn-Svc FY-FYIn-Svc FY-FY

Modularity3IDUExUEy

SystemsNECCCPOFFCS (spirals)ABCS 6.4

77 of 15 of 15

Battle Command System Battle Command System MigrationMigration

Cap Block 1Cap Block 1In-Svc 06-09In-Svc 06-09

TAIS

Transition ATransition A Transition BTransition B Transition CTransition C

MCSC2PC

AFATDSAMDPCS

BCS3

AISPASS B1, IDM-T

GCCS-A

ISYSCON

Transition DTransition D Transition ETransition E

ABCS 6.4ABCS 6.4

FBCB2


TOC SrvrPASS B5, IDM-T

(JBCIEDMv3)

NECCv5

FCS BC(Sp 4)

WIN-T

JBC-P

ASAS-LIMETS


FCS Sp 2

AFATDSAMDPCS

BCS3


(JBCIEDMv1)

NECCv3

WIN-T

JBC-P

DCGS-A(ISR comp.)


FCS Sp 3

AFATDSAMDPCS

BCS3


(JBCIEDMv2)

NECCv4

WIN-T

JBC-P

DCGS-A(ISR comp.)


FCS Sp 1

AFATDSAMDPCS

BCS3


(JC3IEDM)

NECCv2

ISYSCONv4 orWIN-T

JBC-P

DCGS-A(ISR comp.)


JTCW

TAIS

FCS Sp 1eval

AFATDSAMDPCS

BCS3


(C2IEDM)

NECCv1

ISYSCON orWIN-T

JBC-P

DCGS-A(ISR comp.)

ASAS-L or

CPOF

DTSS DTSSDTSS J-GES J-GES J-GES

TAIS TAIS TAIS

88 of 15 of 15

Capability Battle RhythmCapability Battle RhythmOptimum Cycle PhasesOptimum Cycle Phases

Capability Development Capability Development Architecture Documentation Architecture Documentation Material Development Material Development Testing/Materiel Release Testing/Materiel Release FieldingFielding

Phases (12 months)

Phases (18 months)

COA #1

COA #2

Fielding (36)Test & Eval (12)

Capability (12)Architectures (12)

Material Dev (12)

99 of 15 of 15

Example Capability Block Example Capability Block ScheduleSchedule

Start JCIDS Analysis/JROC

AV-1

Operational Capabilities & Mission Threads

OVs: 1,2,3,4,5,6c,7

TV-1

SVs: 1,2,3,5,6,7,10c,11

Contract Rqmts Definition

Functional Capabilities & Technical & Performance Requirements

(Draft CPD Development Starts)

Software Development

Individual System Test

SoS Test Threads

Test Plan & Test Proc Dev

SoS Integration &

Pre-Delivery Test-Fix-Test

SoS Integration at CTSF

Test Unit Training

IAIC & JITC

OpEval & Final Rpt

Training Products Dev

Release Date BCTC Fielding &Training

EDATE

SoS Delivered to Unit

Training Packages

NETT Training

Battle Staff Integration Training

Individual Training: PMs, Trainers

Operational Unit Training

Collective Tng (CTC) Event

Ready Trained Unit

Sep 06

Jun 06

Sep 07

Sep 08(

Apr 05

Jun 08

Sep 09

SoS Eng Starts

1010 of 15 of 15

Block FY 03 FY 04 FY 05 FY 06 FY 07 FY08 FY 09 FY 10 FY 11 FY 12 FY 13 FY1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2

SWBBlk-1 SWB-1Blk-2 1

CAPBlk-2Blk-3 3Blk-4 1Blk-5 Major Interoperability Releases 2Blk-6 Requirements (oper & cont) 3Blk 7 Development 1

Test Events/IntegrationsUnit Reset & TrainingUnit Ready/Available (Deployable)FCS Design-Integration Test

OIF TNG 4 5 6 7CONTINGENCY TNG 1 2 3 4 5 6

Aligned with USMC FEDOS Technical Tests yearlyProbably aligned exactly with FCS spin OffsSupports ARFORGEN fielding rate

FCS Spin Out 1 FCS Spin Out-1 Experiment FieldSpin Out 2 FCS Spin Out-2 ExperimentSpin Out 3 FCS Spin Out-3Spin Out 4 FCS Spin Out+AL2-4

Transition (Capability Block Alignment)

ABCS 6.4SWB-2

2CAP-2CAP-3

CAP-4CAP-5

CAP-6CAP-7

Capability Battle Rhythm: 12 Month Capability Battle Rhythm: 12 Month CyclesCycles

26

4

1111 of 15 of 15

2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 20141Q 2Q 3Q 4Q1Q 2Q 3Q 4Q1Q 2Q 3Q 4Q1Q 2Q 3Q 4Q1Q 2Q 3Q 4Q1Q 2Q 3Q 4Q1Q 2Q 3Q 4Q1Q 2Q 3Q 4Q1Q 2Q 3Q 4Q1Q 2Q 3Q 4Q1Q 2Q 3Q 4Q

BC System Fielding and Deployment Priorities (draft IAW Battle Rhythm)

Cap B1

Cap B2

Cap B3

Cap B4Cap Block In-ServicePeriods

Reset

OIF 4 Rotational Units

Deploy & Fight Reset


Deploy & Fight

Reset


Deploy & Fight

Reset


Deploy & Fight

Reset

Contingency Unit Set 1

Deploy & Fight

Reset


Deploy & Fight

Reset

Contingency Units Set 3

Deploy & Fight

Reset


Deploy & Fight

Reset


Deploy & Fight

Reset


Deploy & FightField

& Train

Field &

Train

Field &

Train

Field &

Train

Field &

Train

Field &

Train

Field &

Train

Field &

Train

Field &

Train

Field &

Train

Reset

OEF 6 Rotational Units

Deploy & FightField

& Train

Reset


Deploy & FightField

& Train

Reset

SFOR/KFOR Units

Deploy & FightField

& Train

Reset


Deploy & FightField

& Train

Legend

Capability Block 2

Capability Block 1

Capability Block 3Capability Block 4

Cap Blk Operational Decision

$

$ Cap Blk Resource Decision

1212 of 15 of 15

Targets

Force Structure Is the Common Force Structure Is the Common DenominatorDenominator

Default FS

PL

GNR

LDR

TCM

TC

LDR

TCM

LDR

TCM

TC

GNR

LDR

TCM

GNR

MaterielPeople

AB1032

AB1032

AB1032

Plans/Orders/Obj

Because numerous data items ultimately link to the force

structure skeleton – use it as the basis to integrate data.

1313 of 15 of 15

Global Force ManagementGlobal Force Management

A Common Data Model: WhatA Common Data Model: What M1A2 Main Battle TankM1A2 Main Battle Tank

A Unique Identifier: WhichA Unique Identifier: Which 32 bit identifier for the platoon32 bit identifier for the platoon

Organizational Relationship Organizational Relationship defined by force structuredefined by force structure 11stst Tank, 2 Tank, 2ndnd PLT, C Co., 4 PLT, C Co., 4thth BN, BN,

6969thth Armor Armor

NetworkNetwork

Now we can link people, crews, supplies, missions, to their Now we can link people, crews, supplies, missions, to their task organized forces and dynamically track them over time.task organized forces and dynamically track them over time.

1414 of 15 of 15

Battle Command MigrationBattle Command Migration( LandWarNet Operational Roadmap)( LandWarNet Operational Roadmap)

Current

FCS

Army CurrentTactical and OperationalSystems

Bridge

Joint Battle Management Command and ControlJoint Battle Management Command and Control leads to a Joint, integrated, network enabled battle command capabilityleads to a Joint, integrated, network enabled battle command capability

JointSystems

NECC

ABCS Family

Future

Army FutureTacticalSystems

NECC

“Leader Centric –Network Enabled”

1515

Questions? Questions?

COL Stuart A. WhiteheadCOL Stuart A. WhiteheadDirectorDirector

TRADOC Program Integration Office for TRADOC Program Integration Office for Battle CommandBattle Command

exploring the role of future systems on the battlefield · ppt file · web view2012-10-03 ·...

Documents