Transcript CoAX Binni 2001 - Building on Success

“Building on CoAX 2001 Success”;
Patrick Beautement, QinetiQ
Patrick Beautement, QinetiQ, [email protected]
Jeffrey M. Bradshaw, PhD, Institute for Human and Machine Cognition, [email protected]
Michael Kirton, PhD, QinetiQ, [email protected]
Prof Austin Tate, Artificial Intelligence Applications Institute, [email protected]
1
Overview - CoAX Binni 2001
• CoAX TIE seen as:
• successful,
• still having momentum,
• being a suitable core for any follow-on.
• Aim of this briefing:
• explain what we did,
• suggest how it can be exploited for 2002 demos.
2
Overview - Issues
• Everyone understood the military context / value of all
contributions (singly and collectively).
• TIE aims clearly stated:
• overall (integrated agents - working collaboratively),
• for each stage / demonstration,
• for each partner (about 17).
• Expressed in the CoAX scenario / overview document.
• Success due to:
• mutual respect, goodwill and commitment,
• good communication, shared vision / understanding,
• willingness to be flexible / use RAD techniques,
• technical competence / inventiveness.
3
Overview - Issues - Technical
• Provision of working infrastructure:
• hardware / network / IP etc,
• software / Grid / JVMs etc.
• Integration tasks:
• agent message markup,
• enabling interoperability between partners technical
contributions,
• ensuring technical contributions are compatible,
• configuration management / versioning,
• knowing how to run the software!
4
Overview - Issues - Staging (1)
• Agreed aim / coherent story / 'so-what' factor:
• agreed approach to be used (live demo / screencam etc),
• scenario / storyboard design,
• agree staging (who, what, where, how and WHY!).
• Scripts:
• technical script (s) / technical operators,
• narrator's script (s) / narrator.
• Presentations:
• scene-setting / overview presentation,
• integrating partner's presentations.
• Overview Handout(s).
5
Overview - Issues - Staging (2)
• Rehearsals.
• For the demonstration:
• stage management of:
– machines, projectors and screens (video switching),
– narrators and operator co-ordination.
• timings,
• changeovers.
• Fall-back options, eg:
• screencams,
• PowerPoint engineering.
6
Overview - Issues - Follow-up
• DVD / CD for distribution.
• Posters.
• Web-site maintenance.
7
8
Exploitation for 2002 ...
• Agree the unified and coherent story that needs to be told:
• what is the military context?
• what needs to proven / shown (metrics etc) and why?
• how will it be done?
• Give due attention to the:
• storyboarding / scripting / stage management,
• integration.
• Keep the technology in its place and use it to tell a militarily
valid story.
• Understand:
• the part to be played by each partner's contribution,
• the overall architecture (and how it all fits together) ...
9
CoAX 2002 Demo - Agent Domains
Common / Shared Intel
Coalition / JTFHQ
Deconflict
Decision Desktop
JFMC HQ
Db5 Rel ???
Browser
Event Panels
'Combat Support System'
SitViewer
Intel feed / 'fusion'
JFAC HQ
AL Plan
Db3
Browser
Event Panels
Rel AODB
FAST / MBP Plans
Sys Admin
Log
data
KPAT
Weather Cell
Weather
Local
data
Observers
Task Force COC
ASW ???
SitViewer
Db1
Process Panel
(Draft 30 Nov 2001)
Event Panels
Db6
JAOC / Combat Ops
FAST / MBP Ops
Db4
Browser
SitViewer
Browser
Rel ???
Event Panels
Rel CODB
D'AO
D'GO
D'agent
Db2
e-Gent
Other
Gao Obs
GRID / Agent-enabled Infrastructure / Admin Tools
UK National HQ
Dbi
Intel UK
Arabello HQ
Dbii
Weather
Intel ASW
Ariadne
CAMPS Dbiii SitViewer
CODB
EMAA
US National HQ
AODB
CYBERSPACE
Intel US
Gao
ALDB
Laki
Dbiv
Gao Intel
e-Gent
10
End of Presentation
11