1 / 36

A Look into the Future of Warfare: The Joint Battlespace Infosphere Harold W. Carter University of Cincinnati ececs.uc/~

A Look into the Future of Warfare: The Joint Battlespace Infosphere Harold W. Carter University of Cincinnati http://www.ececs.uc.edu/~hcarter. "The Internet is like a weapon sitting on a table ready to be picked up by either you or your competitors.” (Michael Dell).

yule
Télécharger la présentation

A Look into the Future of Warfare: The Joint Battlespace Infosphere Harold W. Carter University of Cincinnati ececs.uc/~

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. A Look into the Future of Warfare:The Joint Battlespace InfosphereHarold W. CarterUniversity of Cincinnatihttp://www.ececs.uc.edu/~hcarter

  2. "The Internet is like a weapon sitting on a table ready to be picked up by either you or your competitors.” (Michael Dell) “Similar web-based systems will be cheaply available to U.S. adversaries from global vendors. … if the U.S. goal is information superiority, there is no option but to plunge into the issues of web-oriented C2.” (1999 AF SAB, “Building the Joint Battlespace Infosphere”)

  3. Commander’s Perspective Total situational awareness Right forces at the right time Collaborative planning and execution Facilitate post crisis reshaping Global Grid The World Has Changed…To Meet Our Responsibilities we must: Assemble disparate forces and resources into one joint tailored force rapidly and effectively to employ anywhere in the world Leverage Information for the Warfighter 1999 SAB Study:“Building the Joint Battlespace Infosphere”

  4. Information Management Problem !! DecisionMaker AOC ? GCCS DCGS TBMCS GDSS • Current C2ISR tools only get uspart way there • Large, monolithic, rigid enterprises • Unique information infrastructures • Interoperability issues • System admin & configuration overhead • Decision-maker must filter & aggregate • Kosovo Lessons: • “Info fatigue” • “Cyber-rubbernecking” • Brand new enterprise systemscost-prohibitive (time & $$)

  5. http://www.sab.hq.af.mil/Archives/index.htm

  6. JBI Basics The JBI is a system of systems that integrates, aggregates, & distributes information to users at all echelons, from the command center to the battlefield. The JBI is built on four key technologies: • Information exchange • Publish/Subscribe/Query • Transforming datato knowledge • Fuselets • Distributed collaboration • Shared, updateable knowledge objects • Force/Unit interfaces • Templates • Operational capability • Information inputs • Information requirements

  7. Publish & Subscribe Publish Object Subscribe JBI Client Publish Publication Service • Publish: Installation of Objects in “Catalog of Published Objects” maintained by specialized Publication Services. Services also maintain lists of pending Subscriptions • Search: Trade-off Timeliness against Accuracy in Information Delivery • Subscribe: Subscriptions specify metadata values that must match corresponding values in newly Published Objects - forward looking in time • Query: Like Subscription, but without automatic triggering - backward looking in time • Publication Service Processing: • Test each new Published Object against all pending Subscriptions • Test each new Query against all previously Published Objects

  8. JBI Fuselets • JBI Clients that create new knowledge derived from JBI information objects • Small programs that publish JBI objects by refining or fusing information in a relatively simple way • Capture simple decision logic which can be expressed in a natural way (e.g. rules) • Created using scripting languages (e.g. JavaScript) or simple programming tools to adapt JBI information flows to dynamic mission needs • Obtained from a library, configured, and placed in service to accomplish particular job in a JBI • Not currently viewed aseither mobile or intelligent

  9. Example: fuselets that aggregate • Each air base publishes a “base status” object to the JBI. A fuselet that has subscribed to this type of object is triggered and publishes an aggregate “mission base status” object. • Complex aggregation is achieved by cascading fuselets, forming higher-level knowledge. • Represents challenges in control. Ramstein status Publish Fuselet Aviano status Mission base status Taszar status Subscribe

  10. Objects and Metadata Time-stamp: 06222001 OBJ-ID: TBMCS-59 OBJECT METADATA JBI-CLIENT FLEX-1765A SECURITY: UNCLAS OBJ-TYPE: ATO-MSG GEO: 167/34/27W-45/22/57N • Set of attribute/value pairs • Standardized metadata • Mission-standard object type definitions <CAMPAIGN-ID DECISIVE-HALT-2001> <MSGID ATO/TACC> <AIRTASK RECONNAISSANCE> ATTRIBUTESAND VALUES <TASKUNIT 63-TRS/KXXQ/DET-1-FOL> <MSNDAT AF0025/-/PHICO-10/1RF4C/REC> <RECDATA 8AA001/PRY:2/301500Z/-/SLAR> <TRCPLOT 420035N0153545E/RAD:50NM> <INGRESS-ROUTE > <COMMAND-GUIDANCE >

  11. Force Template • Information handshake between the JBI and the combat unit (defines subscribe and publish data to JBI). • Information interface requirements: • Information required to accomplish mission • Example: Required accuracy of targeting information • C2 and ISR capabilities: • ISR inputs to JBI • Example: weapons pod camera • Force capabilities: • Sortie rates (steady state and surge) • Employment restrictions • Munitions (TLAMs) • Current readiness state • Logistics requirements Force Template

  12. units and their native IM systems Comprehensive Information “handshake” Force / Unit Templates Combat Unit • Software descriptions of military units that are to be integrated into the JBI • Describes pub/sub exchange; based on IERs • Drives JBI reconfiguration to incorporate new • Information requirements • Information products/outputs • Communications requirements • Computing systems • Force employment capability • Ammunition inventory • Fuel requirements • Personnel requirements Support Unit • Information requirements • Information products/outputs • Communications requirements • Computing systems JBI • Mandatory unit subscriptions • Mandatory unit publications • Network routing information

  13. C4ISR and the JBI Planning/ Execution Products Fusion Products Command Guidance Combat Support Products User Information Products & DBs Common Transform Control Publish Query Subscribe Representation Task Centric Presentations Automatic Data Capture Automatic Formatting & Filtering Collaborative Problem Solving Command Planning Battlespace InfoSphere Execution Info Support Combat Support

  14. Architectural Concept Meta data Meta data Meta data Publish Subscribe JBI Repository Query SENSORS JBI Subscription Broker C o n n e c t o r s ? ? B A T T L E S P A C E INFO Personnel ? BDA JBI Query Broker Orders of Battle Weather Global Grid, Web, Internet,…. TBMCS Intentions ABCS Targets AFATDS Etc.... JBI Management Services GCSS GCCS-M ACCESS Coalition partners SYSTEMS JBI Platform

  15. JBI Operational Architecture • Focuses on the tasks, information flows, and operational elements that meet the warfighter needs • Defined through such products as: • operational concept documents • command relationship charts • activity models • information exchange requirements • required capabilities matrices • Develops enterprise view and representation of operational processes

  16. JBI Systems Architecture • Identifies the information systems components and interconnections • that make up the JBI development and execution environment. • JBI platform, the run-time component that implements information • exchange among C2ISR systems and fuselets • Systems needed to implement the entire JBI lifecycle • – Unit Infospheres • – Mission-specific JBIs. • Includes tools and reuse repositories to support • Conceptual modeling • Object modeling • Allocation of object model component publication, • subscription & query responsibilities • Performance modeling

  17. JBI Technical Architecture • Identifies applicable portions of existing standards • Joint Technical Architecture • Establishes new standards where there are voids • Standard template for stating JBI object models • Baseline common object models • Mission-specific JBI object models • Unit infosphere object models • Individual C2ISR system object models • Standard template for stating publication, subscription, query, and query response responsibilities at the same levels as for the object model • Interface protocols that define the service calls between the JBI platform and all systems that interface with the platform, including C2ISR systems and fuselets

  18. JBI Platform Architecture Meta data Meta data Meta data JBI Subscription Broker JBI Repository JBI Clients Connector Global Grid, Web, Internet,…. Access Policy JBI Management Services ? JBI Query Broker ACCESS JBI Platform

  19. Advanced JBI Platform:Required JBI Infrastructure • JBI Infrastructure Services / Capabilities Layer • Publish / Subscribe / Query Mechanisms & Support Services • Information Object Representation / Types / Schemas / Metadata / Ontologies • Distributed Object Spaces / Virtual Repositories • White & Yellow Pages for Information & Service Location • Transform • Fuselet Construction, Modification, Composition, and Control Services • Control • JBI Stand Up/Down Services • JBI Client Protocols, Certification & Registration Services • Unit / Force Join & Depart Services • JBI Access, Performance, Control, and Maintenance Services • Information Flow Level QoS Management • Information Assurance / Pedigree Capture / Security & DIW • World Wide Web Layer • Internet Layer • Global Grid Communications Layer

  20. DESIGN: Concentrate design effort on ops functionality Integrate at information level -- focus on content vs. format; de-couple data & applications ACQUIRE: Competitive market economy for info services & products within the JBI; no single-vendor solutions Rapid plug-n-play, standards-based insertion of innovative functionality and technology DEPLOY: Build & evolve agile JTF info framework driven by campaign CONOPS & dynamics of ops environment -- just like force structure EMPLOY: Timely decision-making from decision quality information Unity of effort through shared understanding JBI PayoffsThe JBI will revolutionize the way we… Faster, cheaper Best of breed Customized, Adaptive Services Information Dominance Enabled by Web Infrastructure

  21. JBI Impact • Design • JBI abstraction barrier isolates information layer from delivery concerns • Designers focus on information needed for decision making • Enables designers to emphasize information availability, not location & ownership • Emphasize information content, not data format • Acquire • “Plug & Play” integration at the information level • Open competition on basis of functionality & performance - “best of breed” clients • C2ISR Product lines, not company store • Low cost of entry for innovators • High payoff through information-level synergy • Evolution of functionality through rapid new technology insertion (e.g., MP3)

  22. JBI Impact (Concluded) • Deploy • “Plug & Play” C2ISR component selection & assembly driven by current mission requirements • Information system architecture (the “Information Plan”) co-designed with the CINC’s campaign plan, force structure plan, deployment plan • “Designed” from the start to be responsive to CINC policy & goals • Agility in the face of changing missions, roles, coalitions • Economy of functionality • Employ • See Gen McCarthy’s 1999 JBI summer study outbriefing ! • The existence of a CINC-orchestrated “Information Plan” implies: • Plan execution • Real-time execution assessment • Replanning • Better decisions, faster

  23. Current Status MOE/MOP Design space wfJBI YJBI-1’s wf-JBI • AC2ISRC “Wright-Flyer” JBI • “Integrated” Cat III for JEFX 00 • ISR Battle Management scenario • JBI Task Force • Mapping technical/operational way ahead; securing acquisition funding • Assembling joint partners • Concept Validation Prototypes(Y-JBIs) • Explore design space • Identify most viable components foroperational spirals • Goal is relatively inexpensive evaluation & idea generation

  24. Provides an integrating substrate of information management services to link all C2 functionality New solutions “plug-in” without rebuilding all service layers JBI Evolution • Supplants old infrastructures while providing migration path for existing C2 systems • Significant acquisition, deployment, and employment gains TBMCS GCCS GDSS EmergingC2 tools TBMCS GCCS GDSS Joint Campaign Planning Mobility Planning JBI-1 EffectsBasedOps Y-JBI Battlespace Awareness Infrastructure WEB ENABLED Infrastructure Dissolves Stovepipes & DeliversSeamless Access to Information

  25. SAB RecommendedTechnology Investments JBI-2 • Information Assurance & Survivability • Web Technology:XML, XSL, XQL Spiral Development Process • E-commerce Solutions JBI-1 • Advanced Data/Sensor Fusion • Enterprise Application Integration (EAI) Middleware YJBI-1 Prototype & Demo Evolve Rqmts • Intelligent Agents • Distributed Storage, Indexing, & Retrieval • Digital Libraries • Auto Data Capture & Info Extraction • Data Warehousing • Immersive Virtual Environments • Warfighter Connectivity 2001 2005 2010 Today Near-Term Long-Term Commercial Tech: DoD S&T: LEVERAGE E-BUSINESS SOLUTIONS WITH ROBUST DOD S&T INVESTMENTS

  26. SAB Specific Recommendations • Immediate low-cost prototypes: AFRL/AC2ISRC • JBI Platform technical architecture: ESC • Evaluation of relevant COTS: ESC • Military requirements for C2 Info Integration: AC2ISRC • Common Representation/Templates: DISA/ESC • Long term research: • Advanced JBI Platform: DARPA with AFRL • Advanced fusion concepts: AFRL with DARPA • Information assurance: DARPA with AFRL • Agent-based technology: DARPA with AFRL • Advanced data survivable systems: DARPA/AFRL • Active networks: AFRL • Dynamic User Modeling: DARPA/AFRL

  27. JBI High-Level Approach JBI = f(COTS + GOTS + DoD-specific R&D) COTS T&E DoD R&D + GOTS T&E Integration & Experimentation Integrated Feasibility Demonstrations / Experiments (IFD/E) Adopt / Adapt / Develop to maintain low cost of entry; “Buy, don’t Build”

  28. JBI Roadmap CONOPS CONOPS CONOPS 2000 2001 2002 2003 2004 2005 2006 2007 JEFX 00 JEFX 02 JEFX 04 JEFX 06 DARPA Technical Architecture Technical Architecture Technical Architecture YJBI-1a JBI-2 YJBI-1b JBI-1 Block 10 wfJBI JBI-1 Block 20 YJBI-1c JBI-1 Block 30 YJBI-1d JBIExperimental Testbed COTS Insertion + Foundational DoD Science & Technology

  29. Long-Term Research Areas Summary • Advanced JBI Platform • Fundamental “core services” for Publish, Subscribe, Query, Transform and Control • Common Representation for information standardization • Advanced Fusion Concepts • Integrate traditionally separate research communities for fusion, planning, and IW for a new form of COP • Information Assurance & Survivability • Novel approaches (e.g., NLP and semantic modeling) needed to control exchange of information between classification and coalition domains: MLS/MSL remain critical requirements despite failures of traditional approaches • Vulnerabilities/challenges introduced by JBI-related technologies; e.g., Shared-spaces (JavaSpaces/Jini); XML; Distributed components (CORBA, EJB, Agents, etc.)

  30. Long-Term Research Areas Summary (Continued) • Agent-Based Technology • Agents with network awareness for bandwidth adaptation • Enhanced mobility, control & coordination, and inter-agent communication • Scalability & agent security issues • Information Acquisition and Storage • Automatic data capture & info extraction services • Advanced data storage & retrieval (e.g., geospatial-temporal indexing) • Effective Interfaces • Context Understanding • Multiple, simultaneous-user, interactive environments • Cross-language transformation for seamless coalition collaboration, preferably in real-time • Near real-time, dynamically-composable simulations to support visualization and decision-making

  31. JBI “SWAT Team” • Goal: Seize the JBI opportunity to provide the research, development and technical leadership necessary to formulate and execute a comprehensive program of research and development of the technical architecture for C2ISR by: • Engaging in early experimental prototyping of JBI Platform services as a basis for idea generation, concept refinement, and evaluation. • Performing in parallel systems studies and analysis of long term JBI Platform architecture focusing on downstream functionality for spiral development • Providing the catalyst for the refocus of on-going AFRL/IF R&D activities, or the initiation of new AFRL/IF R&D activities, in partnership with others, in the long-term JBI technology areas recommended by the SAB

  32. JBI “SWAT Team” • Small cadre of full time senior S&Es • Senior mentor • Large support group of part time S&Es from across directorate • Focus on experimental exploration of JBI Platform design space • JBI Core Services • JBI Technical Architecture • Build & maintain AFRL/IF node of JBI Testbed • Serve as hub of AFRL IF Directorate JBI activities • Bridges to each Division • Outreach to each Branch • Long Term JBI Research and other JBI enabling R&D • Requirements pull for the JBI • Early access to evolving JBI concepts in the Testbed • Collaborate and support outside JBI activities • DARPA • AC2ISRC • ESC/MITRE • AFRL/HE • Other Service Labs

  33. Testbed Purpose • Host and facilitate full evolution of the JBI • Support multiple prototypes (incl. wfJBI) for collaborative development and experimentation • Provide an integration environment for legacy and emerging C2ISR systems • Support industry IR&D efforts with access to C2 architectures & systems • Provide JBI component developers regular access to evolving JBI Services – mitigates risk for downstream insertion • Support operational assessment and evaluation

  34. Distributed Testbed Nodes ESC - Hanscom ARFL - Rome • System Architects • System and Technical architecture specifications • Standards & Protocols • Experimentation/Evaluation Node • COTS/GOTS ring-out and analysis • Metrics collection with operational systems • Integration Partner with AFRL • Requirements Analysis & Transition • Translation of ops to technical reqts • Support transition of JBI services/ components to operational fielding • Science & Technology Developer • R&D for enabling technologies • DARPA agent & transition vehicle • Experimentation & Evaluation Node • COTS/GOTS ring-out and analysis • Platform assessment & prototype development • Integration Partner w/ ESC • Emerging / legacy systems into JBI • JBI component technologies • Joint functional components onto JBI service layers • Management / Assessment Center • Requirement communities • Operational communities • Management communities • Experimentation / Demonstration Site OSC - Langley C2B - Hurlburt DBCC - Nellis • Large-Force Employment Node • Robust, realistic scenarios • Operational ring-out • Operational Process Hub • Develop / refine new CONOPS to drive JBI capabilities • Operational Assessment Center • Access to warfighter users on continuous basis • Full array of fielded systems and architectures • Established feedback and evaluation processes • Warfighter Assessment Center • Access to warfighter users on continuous basis • Full array of fielded systems and architectures • Established feedback and evaluation processes

  35. Summary: JBI Vision Globally Interoperable Information “Space” that … Aggregates, integrates, fuses, and disseminates tailored battlespace information to all echelons of a JTF Links JTF sensors, systems & users together for unity of effort Integrates legacy C2 resources Decision-Quality Information Focuses on Decision-Making Enables Affordable Technology Refresh Leverages Emerging Commercial Technologies

  36. Questions? "Information superiority becomes a precondition for fighting to achieve air and space superiority," Lt. Gen. Liu Shunyao, Chief, China Peoples Liberation Army Air Force 28 Feb 2000, AW&ST (“Chinese War Plans Emphasize Air Force's Offensive Role”)

More Related