PEO C3T - Microsoft Army Conf 06

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

• What is Battle Command
• Near Term Initiatives
• TBES
• AD
• Server Consolidation
• Services
• COOP
• Future Vision

3
PEO C3T Battle Command
Tactical Network
Satellite (JNN, SMART-T, GMF) Radio (LOS, NTDR,
EPLRS, ) Net OPS, Firewalls
Platform
Tactical (FBCB2/BFT) Logistics (MTS) Dismounted
Force Handhelds
Lower TI
Messaging
TSG
Services
XX
JTF
DIV/BCT
AOC
Net Centric BC Server Suite
Battle Command Common Services / Enterprise
Services (Email, Security, Web Portal..) Interoper
ability Services ( PASS/DDS) Web Apps, C2 Data
Services, Etc.
Battle Command
TOCS
Commander Key Leader System Staff User
Notebook Configurable Client Tools CPoF, JTCW,
Web
Integrated Command Post Platform Infrastructure
(Servers, Power, Switches..) Environmental
Control (AC) Tents, Shelters
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.
5
Evolution of Battle Command Scope
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.
6
Adapting to Technology and Requirement Change
4

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

Capability Convergence Graph
3
Capabilities
Web Services Network Mature
ABCS 6.4BCCS IMF
2
MS .NET
1
ABCS 6.4
7 1 (ABCS GE)
TIME
C4ISR Implementation
Technology Innovation
Requirements / Needs
IMF Information Management Framework
BCCS Battle Command Common Services
7
Tactical Business Enterprise Services (TBES)
extending ABCS
Microsoft Server Infrastructure
Services -

• 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
58 of ABCS 6.4 interaction relies on TBES

• Architecture Engineering,
• Detailed Documentation,
• Accreditation\Validation,
• Administrator Training,
• HW Procurement
• FSR Support

8
CIO G6 Interim Guidance on Microsoft Directory
Services
Windows Server 2003 Active Directory

• 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.

Every unit is self supporting

• 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

9
Server Consolidation
Present
Intermediate
Objective
CORE
OPTIONS
CORE

• TBES ABCS Servers Integrated
• Engineered Configured Options
• BCCS Architecture for all Phases of Deployment
• CPP Integrated
• Consistent HW
• Reduced support costs

OPTIONS

• Core Services for TBES ABCS Servers
• Engineered Configured Options (ex. VTC)
• PEO engineered arch
• Trained FSRs and soldier SAs

• TBES ABCS Servers not Integrated
• Mix of Unit and PEO provided equipment
• No TBES FSR support

10
Server Locations
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
Ku-Band Satellite
UEx
MNC-I
LEASECIRCUIT, DISN, MNC-I POP2
Unit Ku-Band Hub
SHF X-Band Satellite
INMARSATL-Band Satellite
L-Band Hub in Sanctuary
EHF-Band Satellite
ISDNLINES
TSC-85
JNN
XX
DMAIN
SMART-T
VendorL-Band Hub
SMART-T
JNN
JNN
XX
DTAC
TSC-93
JNN
SMART-T
JNN
SmallNode
Ku
Ku
Ku
Ku
JNN
Ku
JNN
Ku
Ku
Ku
Ku
Ku
UA
UA
TDMA - IP
8 TDMA Nets (7 UAs DIV) 10 FDMA
Links (NOT ALL LINKS SHOWN)
TDMA Mesh 1
TDMA Mesh 2
ABCS 6.3? BCT/UA
ABCS 6.4 BCT/UA (EPLRS)
11
Operational Example of the Framework
Unit Sites
Unit 2Name
Unit1Name
Logo
Logo
Tailored by Unit from PEO C3T provided Web
Applications
SIG ACTS
WEB COP
TO Battle Position
Knowledge Forums
Weather
Alerts
News
Web Applications
Provided, Developed, Integrated by PEO C3T
Collateral Damage Est
TO/Battle Staff Tree
SIG ACTS
BUB Viewer
Weather
Web COP
TTP
RFI
Air Coord Req
Bridge Calc
Search
OPORD
Route Planning
Log STAT
Forums

Reports
Infrastructure Services
SharePoint Portal
J2EE
ABCS Interop
Provided, Supported, Integrated by PEO C3T
Web Server (IIS)
Database
High Availability

VoIP
Mail
Security
12
Services Integration Framework
CPoF Process Based Collaboration Commanders
Intent enables staff to share pertinent refined
BFA specific information.
Pasteboard
CPOF VoIP
G4
FSO
G3
G2
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.
Services Integration Framework
Data Service
Data Service
Data Service
Data Service
13
Services Considered for ConsolidationPhase 3
Information Management Framework
IM 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 Common Services (BCCS)
14
COOP Plan (AKO Fwd)
Managing Services through all phases Provides
Backup Recovery from Failover

• 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

Hub
JNN
JNN
Enterprise Services
JNN
BC Services
TBES
Sanctuary
Single Point of Entry
Unit Virtual Site Data
Unit Virtual Site Data
Unit Virtual Site Data
TOC/AKO Fwd HW Platform
15
Battle Command Technical Vision
FY05-07
FY11-16
FY08-10
others
Battle Command
Intel Services
Logistics
Army Marine Common Viewers
Viewers are a Commodity
Intel Services
Battle Command Services
Battle Command Services
Maneuver
Fires
Maneuver
Engineer
Fires
Air
FCS/JC2
Engineer
Logistics
Air

Logistics

DCGS-A
Lower TI
DDS
DDS
Note Some system 1 to 1 interfaces still exist
TBES
TBES
Battle Cmd

• 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

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.

17
Thanks You