Transforming Legacy Systems To Obtain Information Superiority Dr. David E. Corman, Thomas Herm, Dr. Kirby Keller, Charles Satterthwaite {David.Corman, Thomas.Herm, Kirby.Keller}@MW.Boeing.com The Boeing Company P.O. Box 516 MC S270-4265 St. Louis, MO 63166-0516 {
[email protected]} Air Force Research Laboratory 2241 Avionics Circle, Bldg. 620 Wright-Patterson AFB, OH 45433-7334
Abstract The United States and its allies are being challenged by the advantages (and threats) of the Global Information Age. In response to these challenges, a new force structure is being proposed which is built upon global awareness, global engagement, and rapid deployment of specific (effects based) forces. Revolutionary advances in information resources and technology are key contributors to this force structure. In the face of a constrained DOD budget, an unprecedented system demand for lean operations in both peacetime and wartime, and the emergence of threats requiring immediate response, it is imperative that innovative technologies be developed to enable legacy weapon systems to exploit the information revolution, achieve information dominance, and meet the required operational tempo. This paper presents an embedded-system architecture, open system middleware services, and a software wrapper schema that will enable legacy systems to fully exploit evolving information technology capabilities in the context of an Network Centric Information Architecture (NCIA). The Global Information Age Current tactical environments are dominated by low bandwidth links and low capacity networks. Information available to the war-fighter is limited and often not timely. Advances in commercial Information Technology (broadband RF communications, wireless optical, fiber, optical switches, and routers) have the potential to enable new tactical architectures characterized by high-speed links and high capacity networks. Similarly, processor improvements, including optical processing, offer potential for increased automation and speed in handling and fusing of the available data to provide the right information to the war-fighter at the right time. Realizing this potential can be the decisive factor in battlefield success. Concepts such as Dominant Battlespace Information are now seen as major contributors to warfighting success. The Joint Battlespace Infosphere (JBI) is being developed as a primary means to achieve information dominance by delivering the right information to the right user at the right time. The JBI may be viewed as the repository of all information that is digitally available to anyone regardless of format or media, location, classification level, or who owns it. This includes data in all knowledge bases, data warehouses, structured files, and text files. In addition to historic data, the JBI includes real-time data feeds provided by theater and national
intelligence and surveillance systems located in space, in the air, or on the ground. In the Air Force vision, weapon systems and the supporting command and control system elements can be considered nodes or IP addresses on a wide-area network. Through this wide-area network connectivity, the JBI can be accessed, searched, and manipulated to create new products. In other words, acting like nodes on the Internet, weapon and command and control systems are provided unparalleled on-demand access to a fused set of intelligence information provided by the collective set of tactical, theater, and national surveillance and intelligence systems - the JBI. Furthermore, the potential of each node to contribute to this collective situational awareness is fully enabled. Each node becomes both: 1) a server of raw data, collected by its on-board sensors and transmitted, to the JBI; and 2) a client of other information servers. Moreover, lines of demarcation between war-fighting and C2 nodes become less visible as discrete timelines for planning, execution, and assessment cycles merge. The JBI cannot materialize out of thin air. Creating a “legacy-free” world of sensors, communication links, C3 systems, and weapon platforms is cost and risk prohibitive. The terminus of the information network – the embedded system / warfighting node - is our primary focus in this paper. It is here where the costs for a “legacy-free” infrastructure become truly staggering – much akin to the last few kilometers in the information network bringing broadband to the end-user. Evolutionary development, capturing and expanding the legacy embedded systems heritage, is the only viable migration path to connect legacy systems to the JBI. However, since most legacy weapon systems have been developed using point designs for connectivity, we must develop ways to "open them up" to take advantage of new technology and enable seamless information exchange. This paper describes recent advances in "smart agent" technology that will enable "controlled" access to information optimized on a platform and mission basis. A key point here is the use of “information” as contrasted with data. We develop the concept of the “guardian agent” which serves as: 1) the link between the JBI and legacy embedded systems; 2) an integrator of tactical data into a coherent set of timely information; 3) a filter that works to manage the information flow to the warfighter based on information “pull”; and 4) an element of an information security strategy. This concept is central to distributed command and control, and flexible and timely employment of current weapon systems. IEIST JBI Vision for Legacy Platforms IEIST – Linking Legacy Systems to the JBI The Insertion of Embedded Infosphere Support Technologies (IEIST) is an Air Force Research Laboratory initiative, being conducted with support from The Boeing Company. IEIST promises to deliver dramatic improvements in the exchange of information between deployed tactical elements including airborne C2 and information nodes
Onboard Node Guardian Agent Support Node - IEIST Software Augments OFP - Hosted Off-board Platform - Gateway and Advocate for Platform - Interface to WSOA Services
Existing Comm Link(s)
IEIST Software Wrapper Platform OFP WSOA /B old Stroke
Other Infosphere Node(s)
Internet XML
Figure 1. IEIST Guardian Agent Concept
world-wide. IEIST focuses on the development of off-board software agents, designed to augment embedded tactical systems and plug into the evolving JBI, whilst still providing interoperability with legacy systems and communication links, Figure 1. These Guardian Agent support nodes will be re-locatable anywhere within the JBI and will allow the use of readily available off-board processing and networking resources to augment the scarce embedded resources. Conservation of host resources - communications and processing bandwidth and operator effort – coupled with operational effectiveness will be the primary drivers in IEIST development. A small software object, the Host Agent, will be integrated into the host Operational Flight Program using proven software “wrapper” technologies in order to provide requisite communications back to the Guardian and to interface with the operator. Figure 2 provides amplifying information on the key elements of an IEIST “Tactical Node”. The “Tactical Node“ refers to the augmented embedded system, i.e. the tactical embedded system plus the augmenting infrastructure, which enables the embedded system to become a full contributor to and consumer of JBI information. The figure shows that each tactical node includes a Guardian Agent (GA), a Tactical Communications Manager (including links), a Force Template (FT) and a Host Agent. Host Agent (HA)
OFP
•Defines tactical system information needs •Sets priorities and deadlines for QoS logic •Responsible for receiving information updates needed by the weapon system from GA •Located on the weapon system
Wrapper Force Template (Aircraft Specific)
Tactical Aircraft Host Agent
P V I
Force Templates •Information required by a specific platform •Information sent by a specific platform •Access to F-15 GA Fuselets (F-15 GA Personality)
Tactical Communications Manager •Converts HA needs, prioritites & deadlines into content needed to control Tactical Link(s) •Provides network capabilities to GA
Guardian Agent (GA) •Determines needed/available information •Adjusts content/quality for QoS •Specific to a platform •Located off-board the platform •Scalable and relocatable •Consists of executable processes - fuselets
C R E W
Tactical Communications Manager
Tactical Link(s) Tactical Communications Manager
TAGA Personality from FT
Tactical Aircraft Guardian Agent (TAGA) (Relocatable/Scalable)
A G E N T
JBI Communications Manager
JBI
Figure 2. IEIST Program Elements The GA identifies and accesses information of interest across the JBI, evaluates the tactical utility of the accessed information, and transmits the information to the tactical node using available communications. Similarly, the GA extracts information of interest from the tactical node and publishes it to interested elements across the JBI. It also brokers cooperative actions between its associated platform and other tactical nodes with specific focus on aiding the associated platform in establishing and executing cooperative actions with unmanned vehicles. This capability supports the controlled, but flexible and rapid, decision aiding/making among
tactical elements that is so important in the pursuit of Time Critical Targets. The GA is scaleable to the tactical need and relocatable anywhere within the JBI. It will be automated, requiring human intervention only in the most stressing tactical situations such as those in which potential for collateral damage is highest. In such critical scenarios, GA operation will be assigned to C2 elements where the requisite immediate asset allocation and airspace deconfliction decisions can be made. The GA design is generic in nature allowing reuse over a wide range of systems. The FT developed for each tactical system, contains a complete description of the information needs and generation capabilities of the tactical node. The FT will be used to tailor the GA to the specific requirements and capabilities of each tactical system. Achieving information superiority must be considered within the context of an evolving information architecture that preserves legacy data links such as Link 16. Our GA design provides communications between the GA and all other JBI nodes through a CORBA interface with maximum reliance on XML message format for system flexibility and reuse. The CORBA interface lies above and is compatible with existing datalink layers. The Tactical Communications Manager (TCM) will utilize evolving quality of service (QoS) based delivery and data compression technologies to tailor information exchange to the tactical situation and available communications bandwidth through bandwidth monitoring and negotiation to optimize network availability. The GA concept also includes use of emerging JBI services and fuselets that will tailor information capture and delivery to the mission needs. Prototype fuselets to be implemented in IEIST include: 1) Hierarchical Controller that provides automated re-allocation and optimization of strike assets based on real-time information updates; 2) Fusion Elements that provide smart filtering and integration of information, 3) Threat Evaluator that determines the impact of threat actions based on own-ship mission plans and vulnerabilities, and 4) Navigation and Discovery services for locating sources of information using CORBA services to match the right data producers and consumers. Figure 3 shows example JBI services under consideration for IEIST.
Potential Core Service Support for IEIST JBI Subscribe to Details of UCAV, Force Template
1. Information Security Management
Core Service Examples
Intrusion Tolerant Services
2. Get/ Access Fusion Engine
Fuselet Engines (fusion, planning alerting)
3. Find Platforms in neighborhood of flight path
UCAV GA - Plan Monitor - Comm Mgt - GUI
Decision Support - Assess impact of threat tracks - Alert crew F-15 GA/HA - Plan Monitor - Comm Mgt - Source Identification - Decison aiding - GUI
Location Services - Spatial Map of Active Battlefield Elements
Figure 3. Example IEIST JBI Services
IEIST will also develop corresponding “Host Agent’ capabilities for a number of tactical systems. The Host Agent is a relatively small software entity, which resides on the tactical node and operates in conjunction with the Operational Flight Software. The Host Agent will provide an interface between extant tactical system and the Guardian Agent, using legacy tactical data links for communications. It will include QoS logic similar to the Guardian Agent and will also satisfy any operator interface requirement associated with the additional IEIST functions. Host Agents for the F-15E, Unmanned Combat Air Vehicle (UCAV) and C2 node (airborne or ground based) are under development. Additional tactical systems may be added as the IEIST scenarios evolve. IEIST responds to the critical need to concurrently evolve the JBI and embedded systems to ensure each responds to the specific needs of the other. Figure 4 graphically depicts this evolution in which IEIST Technologies, adapted to both legacy and emerging tactical systems through the specifics of their Force Templates, are being developed compatible with evolving JBI standards. These technologies will populate ground-based and airborne C2 elements located anywhere within the JBI. Through a series of demonstrations, IEIST will continue to increase the scope, fidelity and operational utilities of these technologies while concurrently developing a set of JBI service requirements. Early integration of IEIST into evolving JBI experiments and prototypes will ensure that embedded nodes and the JBI remain compatible and mutually beneficial and that those JBI services, most useful to tactical systems, will be developed fully responsive to tactical needs. IEIST Quarterly
IEIST Complements OnOn-Going JBI Development Airborne C2
F-15
C2
UCAV
WSOA Bold Stroke JBI
F-15
F-15
Tactical Systems
UCAV JTIDS
Host Agent Fuselets
Legacy Aircraft
Evolving Concepts
UCAV
F-15
Force Templates
Data Links
C2
IEIST Technologies UCAV
JBI Services
Guardian Agent Fuselets Comms Manager
Location Services
Naming Services
Weather Services
TBD IEIST Services
Software Wrappers
IEIST JBI Service Requirements
Figure 4. IEIST/JBI Evolution As IEIST evolves, tactical decision aids and fuselets will be developed and tested in the IEIST context. Early emphasis is being given to basic capabilities such as Navigation and Discovery and Plan Monitor. Figure 5 shows the Navigation and Discovery process in which the Guardian Agent navigates the JBI in order to discover potential sources of information. In order to support
this functionality, each entity registers with the JBI when it becomes available and whenever it has a major change of state. For example, an ESM platform would initially register with the JBI and provide its planned mission and sensor coverage. As other “tactical” assets register, they would evaluate the ESM platform capabilities against their mission needs and if the ESM platform shows potential for supplying tactically significant information, the registering asset’s GA would subscribe to the ESM platform. Subsequently, the GA would evaluate each sensor report from the ESM platform for impact to the host asset. Only those ESM reports, which are of significance to the tactical asset, would be passed on. In Fuselet Functionality - Navigation and Discovery another example, the “tactical” Expected/contracted Plan monitor fuselet functionality assets might determine that the sources for threat data: Support UCAV operator ESM platform coverage does Manned No Threat escort not intersect their mission Alert to operator No Threat Input to planner needs. Later the ESM asset Onboard sensors might be re-positioned. It Threat Discovers would register this reJSTARS as an available positioning which would source trigger a re-evaluation by each •Execution planned or contracted publish and subscribe (P & S) •Intelligently exploit infosphere and P & S capability tactical assets resulting in •Based on opportunity (e.g. space asset SAR map becomes available) •Planned contract no longer supported, search for alternate source (JSTARS reassigned) revision of the ESM subscribers •Intelligent discovery and cueing of commander to key information •Required functionality list. Clearly the methodology •Know role of battlefield platform •Know command and control structure (push info - who is likely to need this information) for Navigation and Discovery is •Build and maintain likely info sources/consumers •Know how to access info and build network to fuse/process data one, which requires joint evolution between tactical assets and the JBI. Figure 5. IEIST Navigation and Discovery The majority of GA tasks center around the Plan Monitor, Figure 6. The GA continuously monitors the host flight status and plans and evaluates each item of information received from the JBI for its tactical significance. Continuing with the example in Fuselet Functionality - Plan Monitor which the GA has subscribed to an ESM asset. Each time the ESM Classic Example of Fuselet: - Function that notifies client if threat will impact ingress to target. assets publishes a report, the GA Route Plan evaluates it in a multi-step process. Info to First, the GA calls upon a JBI Fuselet Threat Location Operator service to identify the exact nature Threat Model of the emission source, i.e. to identify the threat. The GA then GA accesses A/C certified tools, including signature information, to evaluate the impact of changes in the en-route environment on A/C compares the threat to the survivability and probability of mission success. • Plan Monitor fuselet makes decision to publish threat change to HA laydown, which was used to create based upon thresholds provided in Force Template. the tactical plan. If the threat was • Auto-router fuselet provides new route to HA based on receipt of updated threat intelligence. known and was active at the time • Threat Analysis fuselet determines the danger or risk to a HA as a result of new intelligence. of plan generation, there is no new information contained in the ESM report and it is neglected. On the other hand, if the threat is new or Figure 6. Plan Monitor
was thought to be inactive, it must be evaluated against the plan. If analysis of the threat indicates it poses a hazard to the host, the GA will take action to notify the host and either alter the plan or to eliminate the threat. In either case, additional decision aids and fuselets come into play either to replan the route or to negotiate for additional assets to neutralize the threat. As IEIST progresses the number and fidelity of fuselets and decision aids will expand. In particular, the prosecution of Time Critical Targets poses a myriad of information exchange and real-time decision-making problems. Revolutionary advances are occurring in information technology that can automate and support real-time decision-making. While these have largely been targeted to commercial applications, they offer great promise for dramatic reductions in activity timelines, and improving the quality of real-time decision-making. As illustrated in Figure 7, under IEIST and other initiatives, Boeing is working to adapt techniques such as Common Object Request Broker Architecture (CORBA), adaptive middleware, and intelligent agents to legacy systems, particularly those that comprise the last parts of the "kill chain". The bottom right hand panel identifies specific technologies with greatest potential fit this problem area. These include software wrappers based on application of AFRL Incremental Upgrade for Legacy Systems (IULS) technology for gluing new applications to legacy systems, QoS based middleware to optimize use of networks and processors, and use of CORBA over Link 16 - in effect turning the link into an open system bridge for real-time collaborative planning by C2 and attack nodes. Emerging Information Technologies
New Decision Aids
Off-The-Shelf Boeing Technologies
Emerging Commercial Technologies
REACT
REACT Fuselets/Decision Fuselets/Decision Aids
Object-Oriented Application
Communications & Networking
Framework
CRAD Programs Incremental Upgrade to Legacy Systems (IULS) Develop, demo, tr ansition software “wrapper” technology - Affordable migration path to Open Systems Architecture -
Product Line
Component Model
Weapon System Open Architecture (WSOA) Demo Program - AF RL / OSJTF / DARPADARPA-ITO ITO-- WSSTS DO 5 ●
Collaborative sensor-t o-shooter enroute planning ●
Attack Aircraft
JBI Services
UCAV
●
Adv anced Display/ Core Processor COTS Proc Leg acy OFP A ( da)
•Target Allocation to Multiple Weapons •Support Collaborative Planning •RTIC/RTOC Screener •Multi-sensor Resource Management •QofS Communications Management
•Autonomous Target Recognition /Acquisition •Mobile Threat Location •Real-time Attack Planner •Multi-element Target Assignment Planner
Wrapp er
•Location Services Spatial Map of Active Battlefield Elements •Corps Level Services
Single Component Development Policies • Configurable for Product Specific Functionality and Execution Environment
Architecture Specific Service Software • Configurable to variable hardware configurations • Supportive of reusable applications
Airborne C2
Hardware (CPU, Memory, I/O)
Common OFP Components (C++)
COTS Pr oc
COTS Pr oc
Leg acy OFP (Jo vial)
New Functions (C++)
Em ulat or
Object Request Broker
●
●
COTS Ba ckp la ne ●
• Repla ce 1750A-based CCU with COTS • Rehost legacy OFP via emulator • Implement new functions in C++
• Demonstrated automated generation of legacy software wrapper using IULS toolset BOEING PROPRIETARY
• Configurable for Product Specific Component Selection and Distribution Environment Component Integration Policies
Operating System Board Support Package
• COTS-based real-time Adaptive middleware services • RT- CORBA
Open Sys tems CCU
COTS Proc
• “Wrap” lega cy function (OWS) • Combine with new COSSI OFP • Flight Demo
Infrastructure Services
•Automated Attack Approval •Resource Allocation & Planning •Analysis of Intelligence Data •Real-time Target Assignment/Air Space Deconfliction •Improve Fusion Algorithm •Information Generation •Predict Behavior of Non-cooperative Entities •Dynamic Sensor Management
COTS Proc
Time critical target update causes re-t ask of enroute stri ke Collaborative planning between C2 node and strike asset JTIDS messages configured for “browser” support B ack-seater “browses” updated t arget folder /imagery and t hreats JTIDS /SATCOM li nks used to support tactical “Net Meeti ng” Mission rehearsal generated on ground for re-planned strike and i njected into broadcast
• First extension of Bold Stroke “virtual backplane” across multiple systems BOEING PROPRIETARY Phantom Works
P hantom Works
IULS
Operator
WSOA Real--Time Java for Embedded Systems – Real TM
Leveraging Leveraging COTS COTS Technologies Technologies For For Software Software Product Product Line Line Affordability Affordability
Real World Model
Avionics Interfaces
IEIST Focus - Embedded System Aspects of JBI Airborne C2
C2
F-15
Component Integration Model
Platform
Tactical Systems
●
F-15
F-15
Infrastructure Services
Commercial and Standards-Based
WSSTS DO 8
UCAV
WSOA Bold Stroke JBI
C2
UCAV
IEIST Technologies F- 15
Host Agent Fu sel ets
Data Li nks
Guardi an Agent Fu sel ets
Evolving Conce pts
So ftware Wrappe rs
UCAV JTI DS
Force Te mplates Legacy Aircra ft
UCAV
JBI Services
● Comms Manager
Locati on Servic es
Naming Servic es
Weat her Servic es
TB D IEIST Servic es
AFRL New-S tart ❏ Assess Java RT for embedded avionics ❏ Participate in standards bodies ❏ Extend BoldStroke API ❏ Build Java components ❏ Collect performance metrics Kickoff meeting held 14 Nov ‘00
IEIST JBI Service Requirements
BOEING PROPRIETARY
BOEING PROPRIETARY Phantom Works
IEIST
0.0 Plan Campaign
1.0 Conduct Battlespace Surveillance
8.0 Provide Weapons & Support Assets
2.0 Target Prioritization & ATO Prep
Phantom Works
RTJES
•Guardian Agent via JBI Protocol •Internet Backplane over Link 16 •Browser •CORBA 3.0 &
Surveillance or of Prioritized Targets
4.0 Plan Attack
&
5.0 Conduct Precision Surveillance & Tracking
Kill Chain Process Flow
6.0 Precision Target Attack
7.0 Assess Target Damage
•Wrapper Technologies •Collaborative Planning •Quality of Service Image Transmission •Real-time Java •Real-time BDA •Transition to Operational Platforms
Figure 7. Shortening the TCT Kill Chain
Shortening the TCT Kill Chain will also require the capability to monitor and replan the mission in the aircraft or by an operator station. This requires the ability to: 1) Monitor elements of attack plan; 2) Support crew in awareness of the available ordnance, threat, targets and attack execution; 3) Provide mixed initiative interface to support crew/operator in editing, creating, and distributing plan adjustments; 4) Cue crew/operator recommendations/plan adjustments; 5) Provide means for crew/operator to empower unmanned vehicles to replan/react to changing conditions; and, 6) Provide automated replanning and execution capability that can interleave planning and execution in a dynamically changing environment. The intelligent agent paradigm is clearly applicable to this problem domain. Plan monitoring components will require capability to monitor the JBI to extract real-time status of assets within theater. IEIST Tactical Nodes will offer the opportunity to include legacy embedded systems in these evolving solutions. Information assurance considerations may require IEIST components to be distributable and replicated at various air and ground nodes. Replication of GA components at multiple security domains is one technique to provide additional information security. Summary and Conclusions The IEIST effort began in April 2000 and continues through 2004. It will produce a series of laboratory demonstrations of increasing sophistication. Demonstrations focus on evolving IEIST technologies in the context of Network Centric Warfare and quantifying increases in operational capabilities. Initial efforts have been targeted at the first demonstration planned for September 2001. This demonstration will include a flight of F-15Es, and a squadron of UCAVs under the control of an airborne C2 node. The scenario includes: detection by the UCAVs of an emergent threat along the F-15 route, publication of the threat to the F-15s, evaluation of tactical alternatives by the F-15s, cooperative planning and neutralization of the threat by the UCAVs, transmission of UCAV Battle Damage Assessment to the F-15s and finally completion of the original mission objectives by the F-15s. All tactical communications will utilize a simulated Link 16 interface. Subsequent scenarios will incorporate more advanced war-fighting concepts with greater participation and decision making from the C2 node. Progress to date includes development of the basic Guardian Agent and Host Agent designs, integration with battle-field level simulations and demonstration of a limited portion of the scenario. Substantial progress has also been made in defining prototype fuselets and identifying the impact of weapon system needs on NCW services. References [USAF, 1999] United States Air Force Scientific Advisory Board Report on “Building the Joint Battlespace Infosphere”, Volume 1: Summary, SAB-TR-99-02, December 17,1999. [USAF, 1999] United States Air Force Aerospace Command Control Intelligence, Reconnaissance (C2ISR) Campaign Plan 2000, December 23, 1999. [USAF, 1997] Chairman of the Joint Chiefs of Staff, “Joint Vision 2010”, May, 1997. [USAF, 2000] Chairman of the Joint Chiefs of Staff, “Joint Vision 2020”, June, 2000.
Satterthwaite, C. P., Space Surveillance And Early Warning Radars: Buried Treasure For The Information Grid, 5th International Command and Control Research and Technology Symposium, Naval Post Graduate School, Monterey, CA., June 2000.
