17
1 Battle Command Path Ahead 8 February 2006 Carol Wortman & Rob Pitsko Chief Architect, Battle Command PEO C3T

1 Battle Command Path Ahead 8 February 2006 Carol Wortman & Rob Pitsko Chief Architect, Battle Command PEO C3T Battle Command Path Ahead 8 February 2006

Embed Size (px)

Citation preview

Page 1: 1 Battle Command Path Ahead 8 February 2006 Carol Wortman & Rob Pitsko Chief Architect, Battle Command PEO C3T Battle Command Path Ahead 8 February 2006

1

Battle Command Path Ahead

8 February 2006

Carol Wortman & Rob PitskoChief Architect, Battle Command

PEO C3T

Battle Command Path Ahead

8 February 2006

Carol Wortman & Rob PitskoChief Architect, Battle Command

PEO C3T

Page 2: 1 Battle Command Path Ahead 8 February 2006 Carol Wortman & Rob Pitsko Chief Architect, Battle Command PEO C3T Battle Command Path Ahead 8 February 2006

2

Agenda

• What is Battle Command

• Near Term Initiatives – TBES– AD– Server Consolidation– Services– COOP

• Future Vision

Page 3: 1 Battle Command Path Ahead 8 February 2006 Carol Wortman & Rob Pitsko Chief Architect, Battle Command PEO C3T Battle Command Path Ahead 8 February 2006

3

PEO C3T Battle Command

Net CentricNet CentricBC Server SuiteBC Server Suite

Battle Command Common Services / Enterprise Services (Email, Security, Web Portal..)

Interoperability Services ( PASS/DDS) Web Apps, C2 Data & Services, Etc.

Commander & Key Leader SystemStaff User Notebook

Configurable Client Tools:CPoF, JTCW, Web

Battle CommandBattle Command

PlatformPlatform

DIV/BCT

XX

AOC

JTF

Tactical NetworkTactical NetworkTactical NetworkTactical Network

Lower TI

CP LAN,Upper TI

Messaging

Services

TOCSTOCSTOCSTOCSIntegrated Command Post Platform

Infrastructure (Servers, Power, Switches..)Environmental Control (AC)

Tents, Shelters

Tactical (FBCB2/BFT)Logistics (MTS)

Dismounted Force Handhelds

Satellite (JNN, SMART-T, GMF…)Radio (LOS, NTDR, EPLRS, …)

Net OPS, Firewalls

TSG

Page 4: 1 Battle Command Path Ahead 8 February 2006 Carol Wortman & Rob Pitsko Chief Architect, Battle Command PEO C3T Battle Command Path Ahead 8 February 2006

4

Introduction

Task from the Army CIO/G-6 500-Day Strategic Goal 6:

“Deliver an integrated enterprise strategy that influences Joint and Army use of Information Management and Information technology in furthering the warfighting capabilities.”

Page 5: 1 Battle Command Path Ahead 8 February 2006 Carol Wortman & Rob Pitsko Chief Architect, Battle Command PEO C3T Battle Command Path Ahead 8 February 2006

5

Evolution of Battle Command Scope

Common Map Display

BOS based KM

Cross BOS KMIntelligence

OIF1 OIF2 OIF3Time

Net Centric Approach

From Information to Intelligence!

LTG Vines, XVIII Corps CoS

Examples:MSR Evaluation: Three primary MSRs in Iraq. Provide a tool that would consider time of day, week and month and provide analysis of a planned trip by MSR showing percent chance of incident based on historical data.

Incident Best Response: Typical responses are used to respond to critical incidents. These responses have various measures of success and the success differs based on location. When a critical incident occurs, provide a list of responses along with their success percentage for that location.

Page 6: 1 Battle Command Path Ahead 8 February 2006 Carol Wortman & Rob Pitsko Chief Architect, Battle Command PEO C3T Battle Command Path Ahead 8 February 2006

6

Adapting to Technology and Requirement Change

1. Align with Industry best practices and standards

2. Adopt proven solutions & migrate from there (CPoF, JADOCS, JIOC-I)

3. Use “Best of Breed” Web technologies with an Open Controlled Source process to enable cross development between Units and PEO C3T

4. Continuous Engineering Using adaptive processes enabling agile technology insertion

Requirements / Needs C4ISR ImplementationTechnology Innovation

ABCS 6.4

MS .NET

Web Services +Network Mature

7 + 1 (ABCS GE)

3

1

2

4

ABCS 6.4BCCSIMF

BCCS – Battle Command Common Services IMF – Information Management Framework HIC / SASO

TIME

Ca

pa

bili

ties Capability Convergence Graph

Page 7: 1 Battle Command Path Ahead 8 February 2006 Carol Wortman & Rob Pitsko Chief Architect, Battle Command PEO C3T Battle Command Path Ahead 8 February 2006

7

Tactical Business Enterprise Services (TBES) – extending ABCS

Architecture Engineering, Detailed Documentation,

Accreditation\Validation, Administrator Training,

HW Procurement & FSR Support

• Active Directory

• Exchange

• SQL Server

• DNS

• SMS/SUS

• Virus Protection

• SharePoint Portal Server integration and web-parts

• Real-Time Collaborative tool suites

• Server/System Backup, Failover and Restoration

Supporting Modularity by Providing Consistent, Engineered & Supported Infrastructure

Services - Microsoft Server Infrastructure

58% of ABCS 6.4 interaction relies on TBES

Page 8: 1 Battle Command Path Ahead 8 February 2006 Carol Wortman & Rob Pitsko Chief Architect, Battle Command PEO C3T Battle Command Path Ahead 8 February 2006

8

CIO G6 – Interim Guidance on Microsoft Directory Services

Windows Server 2003 Active Directory

Guidance Overview Generating Force SIPRNET AD Architecture: One Forest for Theater, one additional

Enterprise Application forest (PEO EIS) Deployable Force NIPRNET and SIPRNET AD Architecture: Separate Forests for each UEy,

UEx, BCT, and selected UAs (PEO C3T – develop system arch & create plan) Enterprise Directory Service (EDS) will provide the foundation for communication and

integration across AD forests. (PEO EIS in coordination with PEO C3T)• Provisioning solution to support moving users and services between forests

XX

Every unit is self supporting

Authentication and authorization service Synchronized Global Address List Centralized management of servers and client computers Centralized administration of users and computers Centralized management of network resources Directory services for applications

Forest: When one or more domains share a directory structure thus enabling centralized management of accounts, resources and security.

Page 9: 1 Battle Command Path Ahead 8 February 2006 Carol Wortman & Rob Pitsko Chief Architect, Battle Command PEO C3T Battle Command Path Ahead 8 February 2006

9

Server Consolidation

hp ProLiant DL580ExtIntUID

2 3 41

StorageServer

rj45 PatchHP BL45p

UID

NIC2

NIC1

NIC3

NIC4

Cisco GESMHP BladeSystem

Pwr/Rst

Co

ns

ole

23x

24x

Netwo rkin g

Mode

Sys

tS

tat

Dp

lxS

pd

Dow

nlin

ksXC

Upl

inks

1 2

3 4

5 6

7 8

9 10

11 12

13 14

15 16

17 18

FP

19 20

21 22

23 24

Cisco

UID

NIC1

NIC2

NIC3

hp BL25p

UID

NIC1

NIC2

NIC3

hp BL25p

UID

NIC1

NIC2

NIC3

hp BL25pHP BL45p

UID

NIC2

NIC1

NIC3

NIC4

UID

NIC1

NIC2

NIC3

hp BL25p

UID

NIC1

NIC2

NIC3

hp BL25p

UID

NIC1

NIC2

NIC3

hp BL25p

Objective

Intermediate

Present

•TBES & ABCS Servers not Integrated

•Mix of Unit and PEO provided equipment

• No TBES FSR support

• Core Services for TBES & ABCS Servers

• Engineered & Configured Options (ex. VTC)

• PEO engineered arch• Trained FSRs and soldier

SAs

• TBES & ABCS Servers Integrated • Engineered & Configured Options • BCCS Architecture for all Phases

of Deployment• CPP Integrated• Consistent HW • Reduced support costs

CORE

OPTIONS

OPTIONS CORE

Page 10: 1 Battle Command Path Ahead 8 February 2006 Carol Wortman & Rob Pitsko Chief Architect, Battle Command PEO C3T Battle Command Path Ahead 8 February 2006

10

TDMA – IP

FDMA – IP + CKT

EHF via SMART-T

X-Band via GMF

L-Band

Alternate Route

LOS

Common Services Server Stacks

BC Svr Notebook

UEx Forest

UA Forest

UA Forest

Server Locations

8 TDMA Nets (7 UAs + DIV) 10 FDMA Links(NOT ALL LINKS SHOWN)

Ku-Band Satellite

TDMA Mesh #1

EHF-Band Satellite

INMARSATL-Band Satellite

L-Band Hub in Sanctuary

LEASECIRCUIT, DISN,MNC-I POP2

STEP Site

Or MNC-I POP2For DISN Services

UA

TDMA Mesh #2UA

MAINX

II

II

II

II

JNN

II

IIII

II

IISmallNode

DMAINXX

XXDTAC

JNN JNN

JNN

KuKu

Ku

Ku Ku

Ku

Ku

Ku

Ku

TDMA

FDMA

ISDNLINES

VendorL-Band Hub

Unit Ku-Band Hub

USMCX

SHF X-Band Satellite

XXDTAC

JNN

TSC-93

SMART-TSMART-T

TSC-85

SMART-T

TDMA - IP

UEx

ABCS 6.4 BCT/UA (EPLRS) ABCS 6.3 BCT/UA

MNC-I

JNNREAR

X

JNNMAIN

X

JNNREAR

X

II Ku

Page 11: 1 Battle Command Path Ahead 8 February 2006 Carol Wortman & Rob Pitsko Chief Architect, Battle Command PEO C3T Battle Command Path Ahead 8 February 2006

11

C4I

SR

Operational Example of the Framework

SIG ACTS

Logo Unit1NameT

O &

Ba

ttle

Po

sitio

n

Weather

News

Unit Sites

SIG

AC

TS

TO

/Bat

tle

Sta

ff

Tre

e

BU

B V

iew

er

Wea

ther

Web

CO

P

TT

P

RF

I

Air

Coo

rd R

eq

Col

late

ral

Dam

age

Est

Bri

dge

Cal

c

Sea

rch

OP

OR

D

Rou

te P

lann

ing

WEB COP

Unit 2Name

Kn

ow

led

ge

Fo

rum

s

Alerts

Logo

Log

ST

AT

For

ums

Web Applications

Infrastructure ServicesSharePoint Portal

Web Server (IIS)

J2EE

Database High Availability

Rep

orts

ABCS Interop

Provided, Developed,

Integrated by PEO C3T

Tailored by Unit from PEO C3T

provided Web Applications

Provided, Supported, Integrated

by PEO C3T

VoIP Mail …Security

Page 12: 1 Battle Command Path Ahead 8 February 2006 Carol Wortman & Rob Pitsko Chief Architect, Battle Command PEO C3T Battle Command Path Ahead 8 February 2006

12

Services Integration Framework

Each BFA domain provides essential data services to the Services

Integration Framework. These services are collected in the

composition data grid for orchestration into the IM Framework services.

CPoF Process Based Collaboration Commanders Intent enables staff to share pertinent

refined BFA specific information.

Services Integration Framework

G2 Domain Process

&Services

G2 Domain Process

&Services

FSO Domain Process

& Services

FSO Domain Process

& Services

G3 Domain Process

& Services

G3 Domain Process

& Services

G4 Domain Process

& Services

G4 Domain Process

& Services

Data Service

G4G4FSOFSO G3G3G2G2

CPOF VoIP Pasteboard

CDRCDR

Services Integration Framework

Data Service

Data Service

Data Service

Page 13: 1 Battle Command Path Ahead 8 February 2006 Carol Wortman & Rob Pitsko Chief Architect, Battle Command PEO C3T Battle Command Path Ahead 8 February 2006

13

Services Considered for ConsolidationPhase 3: Information Management Framework

Enterprise Services • Domain Controller• Directory Services

– MS Active Directory / Server 2003– IIFP (requires SQL Server)

• Email– MS Exchange 2003

• Common Database– MS SQL Server

• Domain Name Services– MS Server 2003 DNS

• Automatic Upgrades– SMS/MS SUS

• Anti-virus– Norton Anti-Virus

• Time Synchronization– SNTP

Asynchronous Collaboration• Web Portal Technologies

– File Sharing (SharePoint, SQL Server)– Web Applications – Unit Web Sites

Real Time Collaboration• JITC Certified Collaborative Tools

– IWS (101 & MNC-I use)– CENTCOM requires DCTS

• VOIP

Battle Command Server (BCS)• Publish And Subscribe Service (PASS)• Command & Control Registry (C2R)

– C2R Planner (Management UI)– Netscape Directory Server (LDAP)– COE Alerts

• C2PC Gateway• Near Real Time Service (NRTS) • MCS DB (requires SQL Server)

Battle Command Battle Command Common Services Common Services

(BCCS)(BCCS)

IM Framework

Page 14: 1 Battle Command Path Ahead 8 February 2006 Carol Wortman & Rob Pitsko Chief Architect, Battle Command PEO C3T Battle Command Path Ahead 8 February 2006

14

COOP Plan (AKO Fwd)

Unit Virtual Site&

Data

Single Point of EntryUnit Virtual

Site&

Data

Unit Virtual Site&

Data

TBES

BC Services

JNN JNN

Sanctuary

EnterpriseServices

Hub

JNN

• Unit Prior to Deploying pushes Virtual Servers and Data to AKO Fwd

• When unit server goes off-line, AKO Fwd virtual server maintains operations

• AKO Single Point of Entry manages what server is currently active

• When Unit gets in place, and data is synchronized to its servers it becomes the primary.

• Data continues to be synchronized between the unit and AKO Fwd virtual server

• If the unit server goes off-line (planned or unplanned) the AKO Fwd virtual server maintains operations

TOC/AKO Fwd – HW Platform

Managing Services through all phasesProvides Backup

Recovery from Failover

Page 15: 1 Battle Command Path Ahead 8 February 2006 Carol Wortman & Rob Pitsko Chief Architect, Battle Command PEO C3T Battle Command Path Ahead 8 February 2006

15

Service Centric• Common Viewers (Smart clients –

CPoF, JTCW, Thin client – Web)• Services start to replace servers &

utilize common set of data• Clients interface thru services

Server Centric• Centralized service for Data

exchange using standard schemas• System of BFA independent servers

and clients

Network Centric• Viewers downloaded on demand

(rich thin clients) • Domain Specific Services that

utilize common set of data • Clients interface thru services

Battle Command Technical Vision

Note: Some system 1 to 1 interfaces still exist

BattleCommand Services

IntelServices

Maneuver

Fires

Engineer

Air

Logistics

Army & Marine Common Viewers Battle

Command Services

IntelServices

Maneuver

Fires

Engineer

Air

Logistics

Logisticsothers

Viewers are a Commodity

EnterpriseServices

Battle Command

DCGS-A

PASS

AMDWS

TAIS

BCS3

AFATDS

MCS

GCCS-A

FBCB2

IMETS

DTSS

ASAS-L

CPoF

Lower TI DDS

TBES

DDS

EnterpriseServices

TBES

Gateway

FY05-07 FY11-16FY08-10

FCS/JC2

Battle Cmd

Page 16: 1 Battle Command Path Ahead 8 February 2006 Carol Wortman & Rob Pitsko Chief Architect, Battle Command PEO C3T Battle Command Path Ahead 8 February 2006

16

Available Reference Documents

• 101st AASLT Division Account Naming 1 JUN• FM 6-02 32 TI NAMING APPENDIX B UEy UEx UA DOMAINS

543 10 MAR 05 0635• IM Framework Information Paper NOV 2005• Interim Guidance on MS Directory Services_ CIO_G-6• DRAFT 2005 TBES Deployment Doc. May_10rp• TBES Services White Paper Final Draft NOV 2005• PEO C3T AD Implementation 2005

• These documents will be available for your use after the close of the conference. They will reside with the slides.

Page 17: 1 Battle Command Path Ahead 8 February 2006 Carol Wortman & Rob Pitsko Chief Architect, Battle Command PEO C3T Battle Command Path Ahead 8 February 2006

17