1 / 11

Force Templates: A Blueprint for Coalition Interaction within an Infosphere

Force Templates: A Blueprint for Coalition Interaction within an Infosphere. Lt Col. Robert E. Marmelstein Joint Battlespace Infosphere (JBI) Information Directorate Air Force Research Laboratory. Meta data. Meta data. Meta data. JBI Subscription Broker. JBI Query Broker.

bethany-santiago
Download Presentation

Force Templates: A Blueprint for Coalition Interaction within an Infosphere

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. Force Templates: A Blueprint for Coalition Interaction within an Infosphere Lt Col. Robert E. Marmelstein Joint Battlespace Infosphere (JBI) Information Directorate Air Force Research Laboratory

  2. Meta data Meta data Meta data JBI Subscription Broker JBI Query Broker JBI Repository Introducing the JBI GCCS Applications, Systems, Sensors (JBI Clients) Fuselet TBMCS Publish/ Subscribe/ Query Query Publish Subscribe ? JBI Management Services ? ? ACCESS JBI Platform (Core Services) Force Template Global Grid, SIPRNET, Internet,….

  3. JBI Stand-Up Issues • How are units registered with the JBI? • What is the minimum set of Information Objects (IOs) needed to integrate new units into a JBI? • Who publishes, or subscribes to, a given IO? • What conditions are associated with the above? • How are fuselets introduced into the JBI? • How are publisher access controls specified and managed?

  4. Force Templates • Information handshake between the JBI and a combat unit (defines the subscribe and publish data to JBI). • Two purposes: integration and control • Standardization for templates for like units. • Force Template defines (at a minimum): • What information does the unit require? Example: Imagery with an Area of Interest • What information can the unit provide? Example: Weapons pod camera • What are the constraints on that information? Example: Photos published between 1400Z and 1500Z JBI Force Template New Unit

  5. Force Templates vs. Passes Force Templates Passes Purpose Register entities with the JBI Register clients with the JBI Approval of JFC or parent the parent entity Registration of owner entity’s force template with the JBI Activation Prerequisites JBI Interface Force Template Controller Client Adapter Consolidated--cannot be decomposed Distributed, Hierarchical, Decomposable Content Characteristics • Entity Information Requirements • and Products; • Related Constraints; • Passes for clients owned by • the entity • Info Object Advertisements • Subscription Requests • Client-level Constrains Minimum Contents

  6. Entities Clients Theater-level Force Template CINC JTF-level Force Template JTF JTF Unit Unit Unit Unit Unit-level Template • Represent units or organizations • Reflects Joint Force ‘building blocks’ • Decompose into clients & other entities • Register with JBI using Force Templates • Represent platforms, systems, or • individuals • Interact directly with the JBI • Do not decompose further • Use Passes to register with the JBI

  7. Local Civil Authorities Coalition Military JTF NGO US State Dept Problem - Rapidly Forming Ad-hoc Coalition Teams The Challenge: Quickly Enabling Disparate Parties to Cooperate and Interoperate to Solve a Common Problem Each Team Member Provides: • Information • Services • Personnel • Assets Barriers to Team Formation Differences in: • Doctrine • Policy • Infrastructure • Trust • Processes • Vocabulary • Command Structure

  8. Force Template Composition Info Requirements Info Products Related Constraints Ontologies Business Rules Process Models Entity Description Web Services Fuselets Agents Security Credentials Info Pedigree Necessary Desired Speculative

  9. Entity-Client ModelAssumptions • The JBI platform has visibility and control over its inputs and outputs • Entities use Force Templates to maintain nominal control over their clients • Consistent with JFC policies • Consistent with JBI Information Staff directives • Some conflicts may need to be externally resolved • Force Template may change during the mission • In response to top-down or bottom-up requests • A given change request may impact multiple force templates (subscriber & publisher)

  10. Information Broker FT Controller (parent) Response Updates JBI Client Clients can request permission to publish, or subscribe to, new information objects JBI Side Unit Side Change Request Change Request Force Template Authority The Broker forwards the change request to the appropriate Authority This individual has the power to approve force template changes for a given Entity The Controller is the gatekeeper for making changes to the Force Template FT Controller FT Conflict Update The Adapter propagates changes resulting from client requests to the Force Template though its Controller Request Response Adapter The Force Template contains passes for associated clients The Pass contains valid advertisements and subscriptions for a given client Pass

  11. Summary • The JBI represents the way ahead for supporting Coalition C2 operations • Force Templates are a mechanism for: • Quickly integrating units into the JBI • Exercising control over JBI clients • Force Template complexity will grow as JBI must support increasingly diverse, ad-hoc coalitions • Entity-Client interaction model is first step in defining requirements for Force Templates • Model is in early stages of development • Critical to overall JBI systems engineering effort

More Related