DTIC ADA457962: Transforming Legacy Systems to Obtain Information Superiority

10 Pages·0.36 MB·English

by  Defense Technical Information Center

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
Report Documentation Page Form Approved
OMB No. 0704-0188
Public reporting burden for the collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and
maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information,
including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington
VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to a penalty for failing to comply with a collection of information if it

does not display a currently valid OMB control number.
1. REPORT DATE 3. DATES COVERED
2001 2. REPORT TYPE 00-00-2001 to 00-00-2001
4. TITLE AND SUBTITLE 5a. CONTRACT NUMBER
Transforming Legacy Systems to Obtain Information Superiority
5b. GRANT NUMBER
5c. PROGRAM ELEMENT NUMBER
6. AUTHOR(S) 5d. PROJECT NUMBER
5e. TASK NUMBER
5f. WORK UNIT NUMBER
7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) 8. PERFORMING ORGANIZATION
Air Force Research Lab,2241 Avionics Circle Bldg. 620,Wright-Patterson REPORT NUMBER
AFB,OH,45433-7334
9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSOR/MONITOR’S ACRONYM(S)
11. SPONSOR/MONITOR’S REPORT
NUMBER(S)
12. DISTRIBUTION/AVAILABILITY STATEMENT
Approved for public release; distribution unlimited
13. SUPPLEMENTARY NOTES
The original document contains color images.
14. ABSTRACT
15. SUBJECT TERMS
16. SECURITY CLASSIFICATION OF: 17. LIMITATION OF 18. NUMBER 19a. NAME OF
ABSTRACT OF PAGES RESPONSIBLE PERSON

a. REPORT b. ABSTRACT c. THIS PAGE 9
unclassified unclassified unclassified
Standard Form 298 (Rev. 8-98)
Prescribed by ANSI Std Z39-18
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.
IIEEIISSTT JJBBII VViissiioonn ffoorr LLeeggaaccyy PPllaattffoorrmmss
IEIST – Linking Legacy Systems to GGuuaarrddiiaann AAggeenntt SSuuppppoorrtt NNooddee OOnnbbooaarrdd NNooddee
the JBI --HHoosstteedd OOffff--bbooaarrdd PPllaattffoorrmm --IIEEIISSTT SSooffttwwaarree AAuuggmmeennttss OOFFPP
--GGaatteewwaayy aanndd AAddvvooccaattee ffoorr PPllaattffoorrmm --IInntteerrffaaccee ttoo WWSSOOAA SSeerrvviicceess
IIEEIISSTT SSooffttwwaarree
The Insertion of Embedded WWrraappppeerr
PPllaattffoorrmm OOFFPP
EExxiissttiinngg CCoommmm
Infosphere Support Technologies
LLiinnkk((ss)) WWSSOOAA//BBoolldd SSttrrookkee
(IEIST) is an Air Force Research
Laboratory initiative, being conducted
with support from The Boeing OOtthheerr IInnffoosspphheerree
NNooddee((ss))
Company. IEIST promises to deliver
dramatic improvements in the
exchange of information between
IInntteerrnneett
deployed tactical elements including XXMMLL
airborne C2 and information nodes
FFiigguurree 11.. IIEEIISSTT GGuuaarrddiiaann AAggeenntt CCoonncceepptt
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 Wrapper P C
•Responsible for receiving information updates Force V R
needed by the weapon system from GA Template Tactical Aircraft I
E
•Located on the weapon system (Aircraft Host Agent
Specific) W
Force Templates
•Information required by a specific platform Tactical Communications Manager
•Information sent by a specific platform
•Access to F-15 GA Fuselets (F-15 GA Personality) Tactical Link(s)
Tactical Communications Manager
Tactical Communications Manager
•Converts HA needs, prioritites & deadlines
A
into content needed to control Tactical Link(s)
•Provides network capabilities to GA TAGA Tactical Aircraft G
Personality Guardian Agent (TAGA) E
Guardian Agent (GA)
from FT (Relocatable/Scalable) N
•Determines needed/available information
•Adjusts content/quality for QoS T
•Specific to a platform
JBI Communications Manager
•Located off-board the platform
•Scalable and relocatable
JBI
•Consists of executable processes - fuselets
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.
PPootteennttiiaall CCoorree SSeerrvviiccee SSuuppppoorrtt ffoorr IIEEIISSTT
UCAV GA
-Plan Monitor
JBI -Comm Mgt
-GUI
Subscribe to Details of
UCAV, Force Template
Decision Support
-Assess impact
1. Information Security of threat tracks
Management 2A.c Gceest/s 3P.l aFtifnodrm s -Alert crew
Fusion in neighborhood
Engine of flight path F-15 GA/HA
-Plan Monitor
Core -Comm Mgt
-Source Identification
Service -Decisonaiding
-GUI
Examples Intrusion Fuselet Location Services
Tolerant Engines -Spatial Map of Active
Services (fusion, planning Battlefield Elements
alerting)
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
IIEEIISSTT CCoommpplleemmeennttss OOnn--GGooiinngg JJBBII DDeevveellooppmmeenntt
Airborne
C2 F-15 C2 UCAV
WSOA F-15
Bold Stroke
JBI
F-15 C2 UCAV
Tactical IEIST Technologies
Systems
F-15 UCAV
Force JTIDS UCAV
Templates
Legacy Host JBI Services
Aircraft Agent
Fuselets
Guardian
Data Agent
Links Fuselets
Comms Location Naming Weather TBD IEIST
Manager Services Services Services Services
Evolving Software
Concepts 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
FFuusseelleettFFuunnccttiioonnaalliittyy -- NNaavviiggaattiioonn aanndd DDiissccoovveerryy another example, the “tactical”
EExxppeecctteedd//ccoonnttrraacctteedd PPllaann mmoonniittoorr ffuusseelleettffuunnccttiioonnaalliittyy assets might determine that the
ssoouurrcceess ffoorr tthhrreeaatt ddaattaa:: SSuuppppoorrtt UUCCAAVV ooppeerraattoorr ESM platform coverage does
MMaannnneedd NNoo TThhrreeaatt
eessccoorrtt AAlleerrtt ttoo ooppeerraattoorr not intersect their mission
NNoo TThhrreeaatt IInnppuutt ttoo ppllaannnneerr needs. Later the ESM asset
OOnnbbooaarrdd
sseennssoorrss might be re-positioned. It
DDiissccoovveerrss TThhrreeaatt would register this re-
JJSSTTAARRSS aass
aann aavvaaiillaabbllee positioning which would
ssoouurrccee
trigger a re-evaluation by each
••EExxeeccuuttiioonn ppllaannnneedd oorr ccoonnttrraacctteedd ppuubblliisshh aanndd ssuubbssccrriibbee ((PP && SS))
••IInntteelllliiggeennttllyy eexxppllooiittiinnffoosspphheerreeaanndd PP && SS ccaappaabbiilliittyy tactical assets resulting in
••BBaasseedd oonn ooppppoorrttuunniittyy ((ee..gg.. ssppaaccee aasssseett SSAARR mmaapp bbeeccoommeess aavvaaiillaabbllee))
••PPllaannnneedd ccoonnttrraacctt nnoo lloonnggeerr ssuuppppoorrtteedd,, sseeaarrcchh ffoorr aalltteerrnnaattee ssoouurrccee ((JJSSTTAARRSS rreeaassssiiggnneedd)) revision of the ESM subscribers
••IInntteelllliiggeenntt ddiissccoovveerryy aanndd ccuueeiinngg ooff ccoommmmaannddeerr ttoo kkeeyy iinnffoorrmmaattiioonn
••RReeqquuiirreedd ffuunnccttiioonnaalliittyy list. Clearly the methodology
••KKnnooww rroollee ooff bbaattttlleeffiieelldd ppllaattffoorrmm
••KKnnooww ccoommmmaanndd aanndd ccoonnttrrooll ssttrruuccttuurree ((ppuusshh iinnffoo --wwhhoo iiss lliikkeellyy ttoo nneeeedd tthhiiss iinnffoorrmmaattiioonn)) for Navigation and Discovery is
••BBuuiilldd aanndd mmaaiinnttaaiinn lliikkeellyy iinnffoo ssoouurrcceess//ccoonnssuummeerrss
••KKnnooww hhooww ttoo aacccceessss iinnffoo aanndd bbuuiilldd nneettwwoorrkk ttoo ffuussee//pprroocceessss ddaattaa one, which requires joint
evolution between tactical
assets and the JBI.
FFiigguurree 55.. IIEEIISSTT NNaavviiggaattiioonn aanndd DDiissccoovveerryy
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
FFuusseelleett FFuunnccttiioonnaalliittyy --PPllaann MMoonniittoorr
which the GA has subscribed to an
ESM asset. Each time the ESM
Classic Example ofFuselet:
assets publishes a report, the GA - Function that notifies client if threat will impact ingress totarget.
evaluates it in a multi-step process.
Route Plan
First, the GA calls upon a JBI
Threat Location Fuselet Info to
service to identify the exact nature Operator
of the emission source, i.e. to Threat Model
identify the threat. The GA then
GA accesses A/C certified tools, including signature information, to
compares the threat to the evaluate the impact of changes in the en-route environment on A/C
survivability and probability of mission success.
laydown, which was used to create
•Plan Monitor fuselet makes decision to publish threat change to HA
the tactical plan. If the threat was based upon thresholds provided in Force Template.
•Auto-router fuselet provides new route to HA based on receipt of
known and was active at the time updated threat intelligence.
•Threat Analysis fuselet determines the danger or risk to a HA as a result
of plan generation, there is no new of new intelligence.
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
New Decision Aids Off-The-Shelf Boeing Technologies
Technologies
REACT EEmmeerrggiinngg CCoommmmeerrcciiaall TTeecchhnnoollooggiieess CRAD Programs
•••••AATSRMQuaTotuirptIfrglpCSatceio- /Ccrts rRakAteo TfnCmlt••••••••lOsooomARARIIPDClcmnrlruueneyaa f eRsapotbSntandooilrcilraeoo-iyocmutmscmrnriarsvteoam aciate itetusBitetco ione eirF v ooeR Sec nRdAMeTfuhnres e lsAa a PInulGMiMonrvosltElgEtiattcenooaeaaeinanp rncltrnA ntl e lMakaiiAoAeiAroglngg afAgnes aWegetoNsn minmp&ioCrCecaopgiengaee tnnrnPh pn-oeDmclmttTmovTaonaeaneotnslnant p i/FteFnArgairt uiuSvpesas •/•••PEAcAMRMleenaecuetn ouqDialtlblntoulie-teeeiienitl-srcisoeeimott tmlTienoessmfoh nlAur/ie/ecstnaDttD iTatto cLTnakroa egecPrUegaltcaecC tiRnto i i nAAenscessVorsigiiAgononiimrtninboenon rtn AAe Cii2dd•SB•ssLCpaoaotcttrlipaeatfslii oMeLnled avS pEee lrol evSfmi ecASreevcsenit tricJ-svevBesi Ices •c•C•m•A oCSCRrionudcoOTfmdhpni-Tgl ipfCemtiuoSewgOOrr-cueatbatRiurtrbarvaierBoscejbee nAie sl odaesecSf l Prtp r tvr-oeaeelFiOac cnavulier-drfasttsiariai cfmeibS aomSlnbteeeratl rAeeamenv pdhdwidpcaa laeArpoi dcrtSrpwaidvotpkfaiesotl-rwnieBcasaarestieSoSdnooHHLTLfTaaftrretBBeddewIIeCwnnvAwwoocvAcaaOOffaoaaerrahrrehrraafddppmrreefssrfr een aSSttnef((arrrroemCCuuaaoouu gor PPppttgccPiirPuppnnttlUUidluuioodoggnrn,,orrnr rr aMMSSeeogttaiogg yy bgcPPSSeedbissdi ammaaeettie CeerreccuiCtlvvuookkmmslisirriiaaOoccc tiOyyc ggeetFy,,ntF eessytII T Ts//LoOOLo S&))rSirinn NeeeCtwoomCrkop••mino CCpgnSoooCinennnoeffngmiinFlggCttepuuu S ornrIoCaaencnolmbbeteiPmllntoceeettprp n iffIgoaoooononlnrdrritene t auPPayngIer rntrctnoaod afnitDnrddEEo A taDRdtLuuisennvotn ei rvcciaovEvuinMslnett n ciii x t WtMrrclPSSrPueoesooior ppooobrIepncnOln eedSluuldommmtip eicceMcttcerrdiiefeiirveieoaifofoaienedcninitlcennoeeesccststtrlsl IncIIrEEeAIISmTiLAry•••LCaeSSsbDigcrite2onca“eatCFrWCtkirmcnOaaTTnlcWAsiyoOLaFfegedtsrmTrtPvalDgaSh pa a a(ApbpFFPtnec d”icelry-Doaner vO c)looAedeUebe jmD efglCwCccciofsatpooO TopiRtpCeGcTmFeIuughlE•raSuqFmuAyo,dyuoaF Ippgs rn/ meerPr-ssf Seda1lolsDoIc5duCanraeTeotUeibtmn eB noettBfcaw sersTem lnodeo--rLWcole nmlC endkeetPSC JctSoCei s B2mOorEErg ohOSOFOo I ,nnuAtc(tT atMSFArnHCieCoSgstogo oeS(smmecaBr ooPllPUOs+oknsosmnr eCIoeOaryta+gttoaL WgstmAOrlcI)inr teebbssEVsieFraSssoeoIP)teegiNnettfUaidd dtGopwc an dda P yat uhRees r oStetOoFoddf -ywtLPm1 5wO sRrSStapaaIFeeEt-rp1yye5nmeTJpJTd BIssLSS“AeDs••S oe•gIrySttwrc R vRIaCsR(meS ieetc2ruitIeeYneoeeapUhpsnsUmmrmClploeaeivAsnUpmrisFVLcCtacNS - 1ee ge5AAeeatrlSAA mOVer1nCsvU irgEiCF”7toOLic)nPmOc Ae5gTae ss npgnh SusV(t0cJCeeale oaippAynPcOwttyrvc ToWSe-OSoi Sareeehbccfyerl )auFsaBvtntaiuccsnPtcehFcoecmeer Ckttvrupsdtels(OPiinClasso N ao Th-CCcnSe+g nteT aeCC iw+BnoPSooymsU)retUnD oroiusc vff nImwiEc l a CIeJJWiStts+ohTBBor +rCkIIsOTS WPWPRRWWrreoeoeeSSaCagaagoSSprpllrllaTTa--oaobTmTmnSSnori i a SmDDSmt--ivyyeOOAeAe sss F eFJt Jtn88eaesaR•RommvrvF“s-LLtvaiy ao r is- OsrTTOs//ttMMh tW ue poOepOamffooxolet seteSbSBerrnrn JnaeJO Esc nETTEAArikooFIFpmNrumrSnlt Gac ce/o/nb b h hp PfeDD elRie”BiaOtdn OtdoaAeAenPldcdidccnRrRR eegoStItEudsudtPPrTAsor r AAASmeSkeRe u-- yYy ll((llllllIIlWstWsiTTTrCCJ“BttJsMgipttAKNeTahTunbrilo2a-eiooooooSOOmrrjeeSIrcIptl sgeFioDDeulnokac pcsmeaeamOSoSw-tsnORvoiAePbEBCmk bstoketcd--d s/r sefLmooomnr dtSaxuo‘os seeeiaosA r fArdtf0 tA silWWetfrrtliobtaai llNtefa edn eir0se”ecdeir–ntTeen –scret)scii hac)m nso edcdatv Csisdr“relJ SSriutsege w p caba DOd es-obtDJp /pBeaarvSSaitpurrpPaeeM-mrsplorsetoavdolt l gheStioaeeaecaaw“a rTTlk a iaelcf rnodnN nlmtadneim igststgoantoSSRnn nc nv teeoSgeauerrerfaimmk stTirisinpnmo tst s osoydsg”hktgMe DD trdWp e fnaouera euas u ateoor baonniksntplterrcreetnOOeekcdeddidte sdtd kisewdea c aennA1 f at rto egeot554ouadPerd”ns sn nsI e d s
CEvonoclvepintsg WSoraftpwpearrse BOEING PIERIOSTP RJBIIE STeArvRicYe RequirementsPhantom Works BOEING PROPRIETARY Phantom Works
IEIST RTJES
00..00 88..PP00rroovviiddee •Guardian Agent via JBI Protocol
PPllaann WWeeaappoonnss •Internet Backplane over Link 16
CCaammppaaiiggnn &&AA SSssuussppeeppttssoorrtt •Browser
•CORBA
11..00 22..00 33..00 44444444........00000000 55..00 66..00 •Wrapper Technologies
SSSSBBBBuuuuCCCCaaaarrrrttttvvvvooootttteeeellllnnnneeeeiiiiddddllllssssllllppppuuuuaaaaccccaaaannnnttttcccccccceeeeeeee PPPP&&&&rrrriiii ooooAAAATTTTrrrrTTTTaaaaiiiittttrrrrOOOOiiiiggggzzzz eeeeaaaaPPPPttttttttiriririrooooeeeeppppnnnn && SoSoSoSoffffuuuu rPTrPTrPTrPTvvvvrrrraaaaeeeeiiiirrrrooooiiiiggggllllrrrrlllleeeeiiiiaaaattttttttnnnniiiisssszzzzcccceeeeeeeedddd oorr AAAAPPPPttttllllttttaaaaaaaannnncccckkkk &&&& SSSS&&&&PPPPuuuuCCCCr r r r rrrrTTTTevevevevoooorrrrcccceeeennnnaaaaiiiiiiiiddddssssllllcccclllliiiiuuuukkkkaaaaoooocccciiiinnnnnnnnnnnnttttcccc ggggeeee PPPPTTTTAAAArrrreeeeaaaattttccccrrrrttttiiiiggggaaaasssscccceeeeiiiikkkkooootttt nnnn ••CQoulalalibtyo roaft Siveer vPilcaen Inminagge Transmission
•Real-time Java
77..00 •Real-time BDA
AAsssseessss
TTaarrggeett •Transition to Operational Platforms
Kill Chain Process Flow DDaammaaggee
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.