Battle Command Migration Partnering Day Purpose Present an

Battle Command Migration Partnering Day Purpose  Present an

Battle Command Migration Partnering Day Purpose Present an initial overview of Battle Command (BC) migration beyond ABCS 6.4 for near and mid-term Define technical vision for future BC systems Maintain relevance of fielded ABCS systems via key technology insertions Maximize ROI by leveraging todays capabilities into tomorrow Establish a system of systems perspective: Across all PEO C3T programs and Joint Interfaces Technology improvements for interoperability and integration Goal is life-cycle cost reduction Provide a System of Systems Path Forward 3 Army Battle Command Systems (ABCS) IMETS Integrated Meteorological Environmental Terrain System MCS Maneuver Control System ABCS Information Server ASAS All-Source Analysis System FBCB2 Force XXI Battle Command - Brigade and Below GCCS-A Global Command and Control System - Army DTSS Digital Topographic Support System JTF HQS BCS3 TAIS Tactical Airspace Integration System Battle Command Sustainment Support System AMDWS Air and Missile Defense Workstation AIS Tactical Operation Centers A FAMILY OF SYSTEMS AFATDS Advanced Field Artillery Tactical Data System 4 Developing the ABCS 6.4 Solution Warfighter Perspective &

User Feedback Graphic Control Measures (GCMs,FSCM,Capability Overlays) Good Enough 69 Good Enough Operational Requirements Display overlays on COP Display the following on the COP: Friendly Locations Range fans and Dead Spaces Good Enough Sensor Coverage FS Control Measures and targets (dynamic transition from planned to Division and Above View/Display and disseminate part of active) the COP (Platform, unit, joint, Scalable Icons/ Graphics coalition, neutral, unknowns) Obstacles SA and overlays Tailorable/ filters by task organization (GCCS-A/Apr 04)/ scalable and Obstacles Status (status, #, active, inactive, breach lanes) 1 up/ 2 down/ flank Turn On / Off Overlays as needed Tailorable/ filters by Geographical/ Based scalable onarea 2525B (current subset) See 50% of all automated Blue Force trackingMapping systems Common tool kit (currently JMTK going to CJMTK); must have (reported every 5 min. ground and every aviation) ability1tomin. exchange between ABCS systems w/out manual translation or reSee 85% of all reported (automatic/manual) Blue Force locations entry of data Selectively aggregate/ disaggregateAbility by Task organization to have seamless exchange of graphics and overlays between Army Drill down/ hierarchical displays byand keyJoint. leader(AFATDS, and CP location AMDPCS,TAIS to TBMCS currently seamless. GCCSManual update capability A/C2PC graphics resolved Apr 04) Air Tracks (fixed wing and rotary) Visual alert on loss of network connectivity Visual indication of non reporting units (GCCS-A with work-a-round) TSM & PM technical feasibility review Commander's Need BOS 866 Technical Supporting Reqts derived & prioritized Top 7 CDRr's Need ORD Rqmnt # 4.1.1 9.1. 1. ORD Requirement Bl ock VI -Ab ili ty to ch at b oth ho rizon tal ly

a nd ve rtic ally am ongs t th e vari ous a utoma ted comma nd and c ontrol systems o n the battle fie ld. 4.1.1 9.1. 3 Bl ock VI - Provid e coll abo ration ca pa bil ity to sup port di sm ou nte d fo rces Colla bo ratio n 4.1.1 9.1. 4 Colla bo ratio n Colla bo ratio n Blk MCS Good # Enough PdM MCS Good Enough V voice over computer collaborat ion tool 4.1.1 9.1. 2 Colla bo ratio n Short Name Bl ock V - Us e vo ice thro ug h the co mp uter . M CS V Pr ovide Colla bo ratio n M CS VI VI Co llab or ation to ol shall include chat both hor izo ntally and vertically Bl ock VI. V ide o-te lecon fer enc ing c apab ili ty. It is en vi si on tha t VTC c apab ili ty w ill no t b e re qui red be lo w Di vi si on. 4.1.2 1.3 Bl ock V - Pro vi de el ectron ic ma il ca pab ili ty M CS V Pr ovide M CS VI Provide Vide o T eleconfer en cin g V C2 CDRs Critical Info Requirements (CCIR) (Alert) T SM Depen -dency TSM Comment BLK

Bandwid th manag eme nt Un known Bandwid th manag eme nt Un known B C2 FRAGOs MC S-toMC S A Bandwid th manag eme nt No t schedul ed unt il Block VI Bandwid th manag eme nt No t schedul ed C2 Running Estimate unt il Block VI B B VI electr onic mail. Commander's SITREPs A M CS VI VI Co llab or ation capability will b e capable o f being used on th e m ove . Bl ock VI - All ow mul tip le si tes of up to 23 M CS VI Allow up VI wo rkstatio ns to b e tie d in o n a se ssio n, to 23 stati ons to d ep end ent on ha rd wa re a nd ba nd width sim ultaneously collaborat e 4.1.1 9.1. 5 T SM System Delta C2 5of8 G 3of8 B Un known Colla bo ratio n A

4.1.2 .1.1 Comm an de r's SIT REPs 4.1.2 1 4.1.1 Cur ren t Enemy Situatio n Constrained by OIF Driven Schedules Summary: Send and r eceive messages (includes rq mnt to send an d receive SI TREPs) . N/ A Di sp lay th e Co mmo n Ope rati onal Picture M CS D isplay (K PP1). MCS will p rovi de th e Com mon CO P Op eration al Pic tur e to en ab le comm and er s to vis ual ize the ba ttle sp ac e a nd ap ply a na lysis, e stimate s, jud gmen t an d i nforma tio n from other uni ts/agenc ie s i n o rde r to de ve lop situ atio na l u nde rstandin g a nd the com ma nd er's visio n fo r ex ecution o f com ba t o pera tio ns (se e FM 3-0 , Op eration s, pg . 5- 3). MCS will pro vi de the Co mmon Ope ration al Pi ct ure to e nab le th e s ta ff to mon i tor exec uti on of the c ommand er s b att le pla n, ma ke mi no r a dj ustme nts, a nd pro vi de re commen da tio ns to the comman de r. The Co mmon Ope ration al Pi ct ure co ns ists o f, a t a mi ni mu m, the friend ly l ocati on/si tua tio n, ene my l oca tio n/situati on, a nd co mb in ed arm s grap hi cs and o ve rlays (ma neu ve r control grap hics an d s pe ci fied mi ssion esse nti al fire sup port coo rd ina tion me asu res, u nit sym bol s, an d missi on g rap hics). IV IV, V, VI T:G CC S-A & ASAS, T/R : FBCB 2 AMDWS, CSSC S, & AFATD S O RD r equire ment is GE. G reen to EPLRS equ ipped F BCB2 , Bla ck to BF T. A ORD Definitions Requirement # Information IAW the 4a(13) & unit SOP (normally 5.c.( 6) consisting of unit status regarding operational capability including

personnel, pacing item maintenance, key items of supply and equipment and unit locations) PIR, FFIR, and EEFI. Commander requires an automated alert when the CCIR has been met. Feeds the Running Estimate. 29-Sep NA ORD Requirement Block # Good Enough System Delta 4.a(13)Provide common COTS system III &IV utilities and office automation tools that assist users in presenting and shar ing data 5.c(6) GCCS-A will be capable of transmitting and receiving data (using the US Message Text Format (USMTF) and Joint Var iable Message Format (JVMF) rules and standards) with other ABCS and Joint systems via the Common Message Processor. The objective data transfer method with other C2 systems will be direct data exchange IAW the DII COE and the JCDB In Blk III SITREPS can be created and sent via e-mail. In Blk IV, SITREPS can also be created and distributed via CMP. This r equirement is not specifically addressed in the GCCS-A ORD. There are requirements reference alerts and providing the Commander Intelligence Post-Jan Information. (4.a(16) Incorporate and use the Defense GCCS-A is adding the MCSLight capability to the Block IV baseline. An alert capability is not included and is beyond good enough. IV Dependency 15-Jan Post-Jan 30 AprMessage System (DMS) for record traffic. Rationale: Users must be 04 alerted when critical information is x received. Information and messages must be processed using DoD standard systems. MCS-Light must make the application available for integr ation into the GCCS-A baseline by Nov 03.

Change in mission, 4a(1) intent, task KPP organization, pr iorities; available for planning x on receipt and display (textually and graphically) on COP for execution; requires alert on receipt and x effective date/time on all products. FRAGO graphics are autoposted to COP display with effective DTG x noted. INTEROPERABILITY WITH JOINT, III &IV SERVICE AND ARMY SYSTEMS: GCCS-A must interoperate and exchange CTP data and satisfy critical IERs (See Appendix F), with GCCS and ABCS. The CTP data set contains critical C2 and SA data including plans and orders, friendly and enemy unit locations and status, deployment and resource data on friendly units, and battlefield geometry. Blk III uses the MCS-Light OPORD templates to Build Or ders. These are Word Templates that can be shared via e-mail or web capabilities. Blk IV will add the MCS-Light Plan Manager application to the GCCS-A software baseline. Estimate of the unit's 4.a(5) capability to complete x the mission (current and future) IAW METTTC (a predictive capability tied to CCIR x and the DSM - allowing rapid comparison to the plan). Access to COA evaluation, war gaming and rehearsal tools. Information on current x Force Protection measures and status. The requirement for a running NA estimate is not specifically addressed in the ORD. There is a requirement to provide COA tools. An automated capability is not planned for Blk 4. Users can utilize CCIR tracker and Sync matrix capabilities to do manual tracking. MCS-Light must make the application available for integr ation into the GCCS-A baseline by Nov 03. GCCS-A currently only distributes 0rders as Word documents. With the VMF injector and the CMP capabilities be 1 M CS Dep endency

Display O nly Blo ck I V A x CAPES will provide the capability to do COAs, but the capability to do running estimates against the products produced by CAPES will not be part of Blk IV. ABCS 6.4 software delivery to system test in April 04 Field ABCS 6.4 across force within 48 months 5 Current ABCS Product-Centric System Implementation Presentation Services Visualization Stovepipe BFA user interface Role Based Presentation Application Services Others Maps/Overlays Planning/Execution Air Defense Planning MVR Planning Air Defense Control COA & Wargaming Tactical Logistics Airspace Control Rehearsal/AAR Movement Tracking Airspace Planning Comms NW Planning Logistics Planning Fire & Effects Control Comms NW Status Readiness Status NBC Combat Power Engineer Overlay Management Symbology BFA specific instrastrucure BFA specific implementations of common reqts PM AMDWS/ToC Terrain Analysis COP/SA PM WIN-T PM ATC

PM EIS PM GCC2 migrating to EIS PM Intel & Effects migrating to DCGS-A Fire & Effects Planning Task Organization Training Stovepipe BFA implementation of common Requirements Reports L2-4 Fusion Weather BFA unique applications Infrastructure Services Internet Services PM Intel & Effects PM GCC2 Data Initialization & Loading OPORD/PLAN System Services Web Server OS/File System Web Portal/ Collaboration Server Info Assurance Authentication, Encryption Collaboration Auditing Messaging & Mediation Pub & Sub C2 Messaging Email Server Mapping Conferencing, Chat, Whiteboard Storage Map Engine Data Model DB/Data Store Data Distribution Network & Discovery Services Enterprise Mgmt Svc DNS, DHCP, NTP *User Account/ Role Manager Directory

System Manager Discovery Alerts and Notifications *Service Registry Failover Independent Infrastructure X 10 Symbology Rendering Stovepipe platforms/HW, OS and SW environments 6 What Have We Learned? Disparate data formats Interoperability Utilization of Bandwidth Collaboration Difficult to configure Too many systems to train Stovepipe Design Different user interface for each system Many servers providing similar functionality More expensive to maintain Training impacts Must leverage current capability to address these issues as ABCS evolves toward JC2 and FCS. 7 What Happened since Good Enough? JTCW C2PC CPoF ABCS Good Enough FBCB2 JC2 GCCS-A JBC-P Joint Web COP DACT FCS WEEMC Various NCES Horizontal Fusion (18th ABN & JBFSA) GCCS-M Need to incorporate initiatives into ABCS. Must maintain compatibility with ABCS 6.4. 8 Path Forward Today

Near-Term Future GCCS JC2 XXX ABCS ABCS6.4 6.4 XX X FBCB2 + ABCS JC2 with technology insertions X FBCB2 UA FCS BC JBC-P Migration Plan under development 9 Migration Plan Key Drivers and Goals Army at War Modularity Joint Migration Plan ABCS Sustainment Team produces requirements, architecture, and schedule NetCentricity Goals Lower lifecycle cost Reduce Complexity Smaller footprint Common User Interface Reduced training and cognitive burden Fewer soldiers needed to run/maintain the System of Systems Technology Insertions 10 BC System Convergence Vision Cap Block 1

Cap Block 2 Cap Block 3 Cap Block 4 In-Svc 06-09 In-Svc 08-11 In-Svc 10-13 In-Svc 12-15 GCCS-A C2PC MCS CPOF TAIS AFATDS AMDPCS BCS3 ASAS-L IMETS JC2v1 JC2v2 TAIS AFATDS AMDPCS BCS3 ASAS-L or DCGS-A AFATDS AMDPCS BCS3 DCGS-A DCGS-A DCGS-A (ISR comp.) (ISR comp.) (ISR comp.) (ISR comp.) DTSS FBCB2 DTSS JBC-P DTSS JBC-P ISYSCON ISYSCON or WIN-T ISYSCONv4 or WIN-T AIS PASS B1, IDM-T ABCS 6.4 JTCW

Cap Block 5 Cap Block 6 In-Svc 14-17 In-Svc 16-19 JC2v3 JC2v4 JC2v5 AFATDS AMDPCS BCS3 AFATDS AMDPCS BCS3 FCS BC J-GES JBC-P (Sp 4) J-GES J-GES JBC-P WIN-T JBC-P WIN-T WIN-T TOC Srvr TOC Srvr TOC Srvr TOC Srvr TOC Srvr PASS B2, IDM-T (C2IEDM) PASS B3, IDM-T (JC3IEDM) PASS B4, IDM-T (JBCIEDMv1) PASS B5, IDM-T (JBCIEDMv2) PASS B5, IDM-T (JBCIEDMv3) FCS Sp 1eval Transition A FCS Sp 1 Transition B FCS Sp 2

Transition C FCS Sp 3 Transition D Transition E 11 Layered Approach to BC Software Architecture OSI Layers TCP/IP Layers User-Centric Design, Common Role-based User Interface Application Presentation Application Session Transport Network Transport Network Data Link Physical C2 Layers (HCI) Mapping/Overlays, Planning, Logistics, Airspace Mgmt & Deconfliction, Attack Analysis, Weapons Management, Target/Effects Queuing Messaging, Collaboration, Discovery, IA, Data Dissemination, Comms Network Management, QOS, Real-time Services Network Access Presentation Services LAN, Hardware (including servers) Routers, Hubs, Switches, Routing Protocols Battle Command Services Network Infrastructure Services Reduce cognitive burden by automating Battle Command and Network Infrastructure Services. 12 BC Path Forward Near-Term Thrusts Consolidation Of Servers/Services Reduce Server Duplication Centralize Servers/Service C2 Bridge To The Future Expose ABCS Capabilities As Services Leverage Middleware Services Compliant with NCES

Positions BC Server For Transition To JC2 And FCS Spirals Common Presentation Services Leverage CPOF HCI Goodness Role-Based User-Centric Design 13 Cleaning Up Product-Centric Issues Current Near Term Complex Drives the need for*: Duplicative Unique Stovepipes Consistent Acquisition Strategy & Management Practices Heavy Training Burden Product-Centric Systems Engineering and Acquisition Unified Systems Engineering and Integration Common Architecture, Software and Hardware Solutions Usability Strategy and Solutions 14 Server Consolidation 15 Application Consolidation on JTCW Framework GCCS-A CPOF r n/injecto Applicatio c n/inje catio Appli Ap pl ic AFATDS n/ Common Role-based User Interface Ap pl ica AMDWS unique or Ap tio ca pli Common JTCW Client

r to ec j n i in j AFATDS unique technical fire control t or je c n i / io n Tactical ec t at plic Ap ISYSCON BC Server to r or MCS JTCW je ct Tactical Strategic JC2 Applicatio n/injecto r Application/injector BCS3 at io n/ BCS3 EIS app ti o n/ in Strategic AD mgmt C-RAM AMDWS TAIS TAIS Infrastructure and Application Service

Consolidation TAIS unique Airspace Mgmt Common Hardware, Software, and Architecture TAIS AMPS unique functions AMPS Platform Platform FBCB2 TIMS JBC-P 16 What is CPOF? $62M $62Mbeing being Invested by Invested byDARPA DARPA Since 1998 Since 1998 CPOF Servers CPOF Workstation An executive level decision support system that provides situational awareness and collaborative tools to support decision making, planning, rehearsal and execution management. Designed to allow operators to interactively collaborate, and share workspaces and plans. May04 MOA Between Army and DARPA CPOF Network Fielded to 1st CAV and 3ID "We do virtually every rehearsal using the CPOF tool." MG Peter Chiarelli PM GC C2 Actively Working Transition To Support Apr06 Handoff 17 Objective ABCS Service-Based Framework Presentation Services Visualization Role Based Presentation Common User Interface Validated by Usability Analysis Application Services Others Maps/Overlays Planning/Execution Air Defense Planning

MVR Planning Air Defense Control COA & Wargaming Tactical Logistics Airspace Control Rehearsal/AAR Movement Tracking Airspace Planning Comms NW Planning Logistics Planning Comms NW Status Readiness Status NBC Combat Power Engineer Overlay Management Common infrastructure & application services Common BFA service & BFA unique extensions Shared service provided by system external to ABCS Symbology Terrain Analysis COP/SA Data Initialization & Loading OPORD/PLAN Fire & Effects Control Fire & Effects Planning Task Organization Training Reports Common Service Implementation of BFA functions L2-4 Fusion Weather Limited BFA unique extensions Infrastructure Services Internet Services System Services Web Server OS/File System Web Portal/

Collaboration Server Info Assurance Authentication, Encryption Collaboration Auditing Messaging & Mediation Pub & Sub C2 Messaging Email Server Mapping Conferencing, Chat, Whiteboard Map Engine Storage Data Model DB/Data Store Data Distribution Symbology Rnedering Network & Discovery Services Enterprise Mgmt Svc DNS, DHCP, NTP *User Account/ Role Manager Directory System Manager Discovery Alerts and Notifications *Service Registry Failover Common service based joint Infrastructure Common platforms/HW, OS and SW environment hosting BFA services 18 Where Were Headed Single Authority for Battle Command Systems Engineering Single Army/Marine Corps Land/Littoral C2 Solution Maximizing commonality of architecture and services Taking advantage of communications and network infrastructure Incorporation of usability engineering in a common presentation layer design Translating BC Vision into a Viable System Architecture Leveraging ABCS 6.4 Capabilities 19

Recently Viewed Presentations

  • The Georgia Grade 8 Writing Assessment

    The Georgia Grade 8 Writing Assessment

    Georgia High School Writing Test (GHSWT)
  • Types of Release - University of Minnesota Duluth

    Types of Release - University of Minnesota Duluth

    Most states = no attorney, no family Victims? Parole Guidelines Prior to 1970s, decisions based on hearings and whims of board members Even here, based on "seriousness" and "prior record" Risk instruments Risk score x Offense severity Federal = Salient...
  • Electric Machine Design Course

    Electric Machine Design Course

    - Inner, outer or axial SPM rotors (surface permanent magnets) - Back emf seldom sinusoidal, usually sort of flat-topped - Magnet configuration can be arc shaped or bread-loaf shaped ... Electric Machine Design Course Last modified by:
  • ECO Overview New Mexico

    ECO Overview New Mexico

    Background for this effort Purpose of Publisher Work Update on work with publishers and developers What is being done by assessment developers and publishers to address OSEP reporting needs? ...
  • Viruses - Socorro Independent School District

    Viruses - Socorro Independent School District

    Increases risk for opportunistic infections. ... They believe that the chimpanzee version of the immunodeficiency virus (called simian immunodeficiency virus or SIV) most likely was transmitted to humans and mutated into HIV when humans hunted these chimpanzees for meat and...
  • Write down at least three ways the Coronation Street set ...

    Write down at least three ways the Coronation Street set ...

    Write down at least three ways the Coronation Street set could reflect the inner city. ... This has a number of knock on effects and the inner city areas begins to become more and more run down, with increasing issues...
  • This is a Sample of a Title Page - Global Health Care

    This is a Sample of a Title Page - Global Health Care

    This is a Sample of a Title Page Author: Creative Network Last modified by: Vivien Maier Created Date: 1/9/2003 9:54:06 PM Document presentation format: On-screen Show Company: Abbott Laboratories Other titles
  • Forms of information

    Forms of information

    Partial Matches. Most database programs allow you to have criteria using partial matches such as contains, begins with, or ends with. If you can't, you might see the * symbol used - this is called a wildcard