Transcript Commander’s Perspective

AFRL/IF
Joint Battlespace Infosphere
19 July 2000
Walt Tirenin
[email protected]
(315) 330-1871
Overview




Concept Introduction
R&D Approach
Status/Distributed Testbed
IA&S Issues
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 weboriented C2.”
(1999 AF SAB, “Building the Joint Battlespace Infosphere”)
3
Information Management Problem
!!

Current C2ISR tools only get us
part way there
Decision
Maker
– Large, monolithic, rigid enterprises
– Unique information infrastructures
– Interoperability issues
– System admin & configuration overhead

Decision-maker must filter & aggregate

Kosovo Lessons:
– “Info fatigue”
– “Cyber-rubbernecking”

GCCS
?
GDSS
DCGS
TBMCS
Brand new enterprise systems
cost-prohibitive (time & $$)
4
Traditional system interoperability view

Systems are connected to each other
– With dedicated circuits, or
– With preplanned message interchanges for
each pairwise system-to-system connection
More
interoperability
requirements
quickly become
a LOT MORE
interfaces to
manage
(n-squared problem)
5
The JBI Vision
Globally Interoperable Information “Space” that …
Aggregates,
fuses, and
disseminates
tailored
battlespace
information
to all
echelons of
a JTF
Links JTF
sensors,
systems &
users
together
for unity
of effort
Decision-Quality Information
Focuses on
Decision-Making
Enables Affordable
Technology Refresh
Integrates
legacy C2
resources
Leverages Emerging
Commercial Technologies
6
Inside the
Battlespace InfoSphere
(circa 1999)
Input
Fusion
Products
Combat
Support
Products
Manipulate
to Create
Knowledge
Planning/
Execution
Products
User
Information
Products &
DBs
Common
Publish
Transform
Subscribe
Task
Centric
Presentations
Control
Query
Representation
Collaborative
Interact
Command
Guidance
Problem
Solving
Automatic
Data
Capture
Automatic
Formatting &
Filtering
http://www.sab.hq.af.mil/Archives/index.htm
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 data
to knowledge
– Fuselets

Distributed collaboration
– Shared, updateable
knowledge objects

Force/Unit interfaces
– Templates
» Operational capability
» Information inputs
» Information requirements
8
SENSORS
Architectural Concept
Meta
data
Meta
data
C
o
n
n
e
c
t
o
r
s
Meta
data
JBI Subscription
Broker
?
Publish
Subscribe
Global Grid, Web,
Internet,….
TBMCS
ABCS
AFATDS
B Personnel
A
T
BDA
T
L
E Orders of
Battle
S
P
A Weather
C
E Intentions
I
N Targets
F
Etc....
O
?
?
JBI Query
Broker
JBI Repository
Query
GCSS
GCCS-M
JBI
Management
Services
Coalition partners
ACCESS
SYSTEMS
JBI Platform
Publish & Subscribe
•
Publish: Installation of Objects in “Catalog of Published Objects”
maintained by specialized Publication Services. Services also maintain
lists of pending Subscriptions
• 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
JBI
Client
JBI
Management
Services
ACCESS
JBI
Client
?
?
?
JBI Query
Broker
Meta
data
Meta
data
Meta
data
JBI Subscription
Broker
10
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 as either mobile or intelligent
11
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.
Ramstein status
Publish
Aviano status
Taszar status
Fuselet
Subscribe
Mission base
status
• Complex aggregation is achieved by cascading fuselets, forming
higher-level knowledge.
• Represents challenges in control.
12
Force / Unit Templates
descriptions of military units that
are to be integrated into the JBI
•Information requirements
 Describes pub/sub exchange; based on IERs
•Information products/outputs
 Drives JBI reconfiguration to incorporate new
•Communications requirements
units and their native IM
•Computing systems
Support Unit
systems
•Force employment capability
•Information
 Comprehensive
•Ammunition inventory
Information “handshake” requirements
Combat Unit
 Software
•Fuel requirements
•Personnel requirements
•Information
products/outputs
•Communications
requirements
•Computing systems
JBI
•Mandatory unit subscriptions
•Mandatory unit publications
•Network routing information
13
JBI Payoffs
The JBI will revolutionize the way we…
DESIGN:
– Concentrate design effort on ops functionality
Faster,
cheaper
– 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
Best
of breed
– 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
Customized,
Adaptive
Services
Information
Dominance
– Unity of effort through shared understanding
Enabled by Web Infrastructure
14
JBI Evolution


Provides an integrating substrate • Supplants old infrastructures while
of information management
providing migration path for existing
services to link all C2 functionality
C2 systems
New solutions “plug-in” without
• Significant acquisition, deployment,
rebuilding all service layers
and employment gains
TBMCS GCCS
GDSS
TBMCS GCCS GDSS Emerging
C2 tools
Y-JBI
Infrastructure
Infrastructure
Joint
Campaign
Planning
Battlespace
JBI-1
InfoSphere
Mobility
Planning
Effects
Battlespace
Based
Awareness
Ops WEB-ENABLED
Dissolves Stovepipes & Delivers
Seamless Access to Information
15
SAB Recommended
Technology Investments
Commercial Tech:
DoD S&T:
• E-commerce
Solutions
• Information
Assurance &
Survivability
JBI-2
• Web Technology:
XML, XSL, XQL
JBI-1
• Advanced Data/Sensor
Fusion
• Enterprise
YJBI-1
Application
Integration (EAI)
Middleware
• Intelligent Agents
• Distributed Storage,
Indexing, & Retrieval
• Digital Libraries
• Auto Data Capture &
Info Extraction
• Data Warehousing
• Immersive Virtual
Environments
2001
Today
2005
2010
Near-Term
Long-Term
• Warfighter
Connectivity
LEVERAGE E-BUSINESS SOLUTIONS WITH ROBUST DOD S&T INVESTMENTS 16
JBI Investment Strategy

Requires a multi-track approach:
– Experimentation and testing
– Long-term S&T investment
– Migration of C2ISR functionality

Long-term S&T investment areas:
– Repository: Structured Common Representation, Metadata, Pedigree,
Data Warehouse, Digital Library, Distributed/Virtual Object
Spaces/Storage
– Interaction: Publish/Subscribe/Query, Information Extraction, Input,
Collaboration, Dynamic User Modeling
– Information Processing: Fusion, Fuselets, Filtering, Data Mining,
Natural Language Translation
– JBI/Enterprise Management & Control: Middleware Services, QoS,
IA&S, Force Templates, Lifecycle, Client Access/Interface
– JBI Enabling Technologies: Agent Technology, Advanced Networking
and Communication Technologies, HPC, Modeling & Simulation
17
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”
18
JBI Roadmap
2000
2001
2002
2003
2004
CONOPS
JEFX 02
2006
CONOPS
Technical Architecture
JEFX 00
2005
CONOPS
Technical Architecture
JEFX 04
2007
Technical Architecture
JEFX 06
YJBI-1a
wfJBI
YJBI-1b
YJBI-1c
JBI-2
JBI-1 Block 10
JBI-1 Block 20
YJBI-1d
JBI-1 Block 30
JBI Experimental Testbed
COTS Insertion + Foundational DoD Science & Technology
DARPA
19
Current JBI Status
 AC2ISRC
“Wright-Flyer” JBI
– “Integrated” Cat III for JEFX 00
– ISR Battle Management scenario
– JEFX spiral 2 successful 9 Jun 00
 JBI Task Force
 PAWG
 JBI Repository Study - Summer 2000
 Concept Validation Prototypes
(Y-JBIs)
– Explore design space
– Identify most viable components for
operational spirals
– Goal is relatively inexpensive
evaluation & idea generation
wf-JBI
MOE/MOP
YJBI-1’s
Design
space
wfJBI
20
JBI Distributed Testbed

Sites & Responsibilities:
– WSC – focal point for
coordinating
distributed testbed
activities and JBI
evolution as a whole
– AFRL/CUBE –
prototype development,
experimentation, &
integration
– C2B – operational
assessment, evaluation
& feedback
– DBCC (Nellis) - robust
employment scenarios
– Future: JBC (JFCOM),
DARPA, SPAWAR, ITC,
Industry IR&D partners, …
DARPA
Near-term
Future
Testbed = Facilities, HW/SW, network connectivity, manpower, processes, sensor
feeds, databases, M&S, legacy C2 systems
21
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
22
IA&S Challenges

Vulnerabilities/challenges introduced by JBIrelated technologies (e.g., Shared-spaces
(JavaSpaces/Jini); XML; Distributed components
(CORBA, EJB, Agents, etc.); Commercial
Middleware & Enterprise Integration
Technologies)
– The good news is the JBI concept provides
rapid refresh of technology; the bad news is …

Policy specification, propagation, enforcement,
and maintenance
– Complicated across heterogeneous & dynamic
domains; allies/coalition partners

Potential “fuselet”-based aggregation of data into
information of varying/unknown sensitivity levels
23
IA&S Challenges


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 difficulties/failures with traditional
approaches
– How do you do:
– collaboration
– seamless management/operation of a JBI
 across multiple security levels and coalition
systems?
Incorporation of Units via Force Templates
– Certification/Accreditation of the composed
mission-specific JBI on-the-fly (risk profile)
– Including coalition partners
24
IA&S Challenges





I&A and audit to support such things as pedigree of
information/directives published into “shared” spaces
– In an environment of complex information flows
Integrity of information, availability, and appropriate
confidentiality controls are essential
– Though not new, complicated by highly distributed,
shared notions of information management
Validation & revocation of subscriptions based on
dynamic need-to-know conditions
Impact on JBI of the recent policy on Mobile Code, not
to mention threats from malicious Mobile Code
… and many more challenges [ insert favorite here ]
“The success of the JBI will depend on a sound system for IA”
(1999 AF SAB, “Building the Joint Battlespace Infosphere”)
25
SAB Report Findings on IA



SAB’s JBI study gave little attention to security
issues
– Such issues are extremely broad, and require a
dedicated SAB study to pursue
Web has carried all systems well beyond the
ability of current defensive technology
– As with any new technology, defense lags
attack
– Like all DOD enterprise systems, as JBI
evolves, IA must strive to catch up
“The SAB study team especially recommends
research relevant to distributed component
architectures, such as CORBA, EJB, and agents”
26
SAB Report Findings on IA




The SAB team focused on three particular areas:
Intrusion Detection: Need to move beyond
current signature-based techniques to “nonsignature” methods for detection of novel attacks
Response Selection: Need attack assessment
and response selection at “execution speed”
– Implies control technology for automated
response selection
– Require new theoretical models of systems
under attack (e.g., Process Control
Approaches to Cyber Attack Detection)
Multilevel Security: DOD has not made great
progress in MLS after many years of effort
– Would provide increased flexibility for systems
such as JBI
27
Approach for IA&S

Development of IA&S for JBI must track with
development of overall JBI
– As architectural & design options are iteratively
defined & solidified, specific security solutions
can then be developed and incorporated in parallel
– Evaluate JBI prototypes (YJBIs) for “securability”
as well as functionality and performance
– Identify any major “gotchas” soon as possible
– Security must be brought “up the ramp” together
with the rest of the JBI community
– Plan & implement security from the start but ...
We can’t secure what we don’t know!
28
Conclusion: JBI Impact

Tailored to match the needs of the mission; versus
the mission constrained by capabilities of the system

Provides an underlying, consistent information
management framework; eliminates the need for
duplicate, custom-built structures across stove-piped
systems
– Individual development & acquisition efforts can focus
on the unique functionality of each component
– Reduces incompatibility/interoperability problems

Complexities of system integration and information
management are abstracted away at the operator level

Reduces information overload, improves decision
quality, by providing relevant info at the required time
and level of detail — No more, no less
29
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”)
30