1 / 33

ISTAR Testbed The Experimentation Facility for the ISTAR Community 21ISMOR, 2 nd September 2004

ISTAR Testbed The Experimentation Facility for the ISTAR Community 21ISMOR, 2 nd September 2004. Kym Rawlings Steve Brooker Programme Manager ISTAR Testbed Technical Director Synthetic Environments & Experimentation. Presentation overview. Background: What is the ISTAR Testbed?

morela
Download Presentation

ISTAR Testbed The Experimentation Facility for the ISTAR Community 21ISMOR, 2 nd September 2004

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. ISTAR TestbedThe Experimentation Facility for the ISTAR Community21ISMOR, 2nd September 2004 Kym Rawlings Steve BrookerProgramme Manager ISTAR Testbed Technical DirectorSynthetic Environments & Experimentation

  2. Presentation overview • Background: • What is the ISTAR Testbed? • Why do we need it? • What is its scope? • Where does it fit in? • Technical issues: • Designing the Testbed • Key features • Documenting the Testbed • Lessons Learned so far (Experiment Conduct) • Ensuring stakeholder engagement • Maximising exploitation of results • Summary

  3. Presentation overview • Background: • What is the ISTAR Testbed? • Why do we need it? • What is its scope? • Where does it fit in? • Technical issues: • Designing the Testbed • Key features • Documenting the Testbed • Lessons Learned so far (Experiment Conduct) • Ensuring stakeholder engagement • Maximising exploitation of results • Summary

  4. ISTAR Testbed Build Use Capability Use Time A two year research programme for DEC(ISTAR) with two parallel aims: • To Design and Build an ISTAR concept evaluation and live experimentation capability for long term use. • To Experiment, i.e. to use the capability to address high priority ISTAR issues.

  5. The Military Need for the ISTAR Testbed • Significant new ISTAR systems entering service from 2005 onwards • Integration effort is required to realise full collection potential, in order to enhance Commander's SA • TT&Ps must be developed to facilitate the ISTAR “System of Systems” capability. “Heavy investment in front line capabilities will not be fully realised without a commensurate improvement in our ability to provide near real time, 24 hour information in all weathers…. Currently, our ISTAR assets provide discrete capabilities; there is no Joint ISTAR capability.”

  6. ISTAR TESTBED Scope INTELWEB DIS DIS DIS NSO JARIC MIL SRV OGDs NSO JARIC MIL SRV OGDs NSO JARIC MIL SRV OGDs PJHQ PJHQ PJHQ JOCS Sp Grps Sp Grps Sp Grps JTFHQ JTFHQ JTFHQ MCC MCC MCC LCC LCC LCC ACC ACC ACC SFCC SFCC SFCC LogCC LogCC LogCC Tsk Grp Tsk Grp Tsk Grp Div Div Div CAOC CAOC CAOC Ship Ship Ship Bde Bde Bde Sqn Sqn Sqn RNCCIS RAFCCIS Unit Unit Unit Aircraft Aircraft Aircraft Bowman Falcon Cormorant Levels of Command ISTAR ASSETS GLUE

  7. Types of Experiment Burden of proof Quality of knowledge Domain of the ISTAR Testbed # 1 # 2 # 3 Confidence Experimentation Campaign Expt Tests Trials Exercises Demos No. of good ideas Visualisations No. of hypotheses Quantity of knowledge Discovery

  8. Links to other Experimentation Facilities W Mars mega I S T A R CONOPS Evaluation Team Isosceles DEC ISTAR Live Experimentation The ISTAR Testbed • A DEC(ISTAR) research programme addressing Future ISTAR system-of-system issues • NITEworks • A MOD-industry partnership addressing NEC • Dstl Joint Command Battlespace Management Applied ResearchTechnology Demonstrator (JCBM ARTD) • C2 systems lab

  9. Presentation overview • Background: • What is the ISTAR Testbed? • Why do we need it? • What is its scope? • Where does it fit in? • Technical issues: • Designing the Testbed • Key features • Documenting the Testbed • Lessons Learned so far (Experiment Conduct) • Ensuring stakeholder engagement • Maximising exploitation of results • Summary

  10. ISTAR Testbed – Initial Design Concept • Live Experiments • Real Operators • Real Infrastructure • Real CIS Apps • Simulated Assets • Simulated Processes • Deployable • Flexible • Modular • Plug & Play • Open Architecture

  11. Synthetic Environment Development and Exploitation Process (SEDEP) ISTAR Testbed ITT Phase ISTAR Testbed PD Phase Repository ISTAR Testbed DBE Phase 0. Analyse User’s Needs 1. Define Fed. User Requirements 2. Define Fed. System Requirements 3. Design Federation 4. Implement Federation 5. Integrate & Test Federation 6. Operate Federation 7. Perform Evaluation

  12. Incremental ITB Design 4. Implement 5. Integrate DBE 6. Operate 7. Evaluate ISTAR Testbed ITT Phase 0. Analyse User’s Needs PD ISTAR Testbed PD Phase 3. Design Federation Repository ISTAR Testbed DBE Phase ISTAR Testbed Post DBE Phase

  13. ISTAR Testbed Core Architecture Concept MITL Experiment Preparation and Set-Up ISTAR (Procedures and Assets) Federation Management Analysis Planning Execution Battlespace Input and scenario databases Execution Output Documented interface to enable interaction between a range of components Encompasses range of interfaces: e.g., Tactical, RPR FOM……. Design uses proven methods and technologies to provide a robust ISTAR Testbed environment

  14. ISTAR Testbed Key Features (1) • Continuous close involvement of Customer 2 • Appropriate utilisation of simulated and real processes to meet study requirements • Detailed CONOPS representation for ISTAR Systems Management and Interoperability • Flexibility in modelling using a suite of simulation tools • Defined V&V process for conduct of experiments • Use of standard interfaces supports interfacing with other testbeds • Design focused on interface definition accommodates extendibility

  15. ISTAR Testbed Key Features (2) • Multiple levels of fidelity for System Representation • Reuse of available model data to minimize costs • Maximal reuse of legacy system models • Established process to address operational security and characterisation of highly classified data • Flexible scenario definition • Multiple levels of scenario fidelity • Re-locatable to ease interface and Customer 2 availability issues

  16. Experimentation Environment Design – built on DoDAF Current Real World Operational View Experiment World Systems View Technical View Operational View Future Real World Operational View Systems View Technical View Systems View Technical View

  17. OV-5 Operational Activities (Real World)

  18. OEV-5 Operational Activities (Exp World)

  19. SEV-04 System Functions (Exp World)

  20. SEV-2 System Communications (Exp World)

  21. Presentation overview • Background: • What is the ISTAR Testbed? • Why do we need it? • What is its scope? • Where does it fit in? • Technical issues: • Designing the Testbed • Key features • Documenting the Testbed • Lessons Learned so far (Experiment Conduct) • Ensuring stakeholder engagement • Maximising exploitation of results • Summary

  22. Experiment Conduct Lessons (1) • Should not underestimate requirements and time for initial training and player briefing. • HICON involvement in data production highly desirable. • A respected military experiment director works well for player briefing and marshalling. • Strong directorship needed when encouraging players to throw aside current practice. • A single experiment should not attempt to combine :- • experimentation to support concept/process development • experimentation to evaluate concept/process. • If experiment time is short extensive care is needed to develop the starting state. • Measuring/ observing reaction to specific situations (e.g. asset overload) needs careful preparation/prediction and dynamically controlled injection/observation.

  23. Experiment Conduct Lessons (2) • The role of observers varies significantly with the type of experiment • The players will get there on time (or earlier) and want to start straight away. • System switch-on at the end of each day causes problems (both time and reliability) – security procedures to overcome this are required. • Remote monitoring of player activity by EXCON is highly desirable. • Need to be able to accommodate simple data changes during the experiment. • Control of visitors is important (disruption, photographs, handouts) • Anything planned for the final afternoon is ‘risky’.

  24. Presentation overview • Background: • What is the ISTAR Testbed? • Why do we need it? • What is its scope? • Where does it fit in? • Technical issues: • Designing the Testbed • Key features • Documenting the Testbed • Lessons Learned so far (Experiment Conduct) • Ensuring stakeholder engagement • Maximising exploitation of results • Summary

  25. Stakeholder Input Selection of Stakeholders and Capturing Issues ISTAR Customer Community with Problems, Issues and Options ISTAR Customer Community with Solutions JDCC AWC MWC DGD&D DPA DLO PJHQ DIS EC The Use List MOD Customer Community requiring ISTAR representation as a service NITE-works ACID JETTS JCBM-ARTD

  26. Ongoing Stakeholder Engagement Issues Issues Issues Issues Issues Issues Issues Investigation Experiments Investigation Investigation Investigation Experiments Experiments time STAKEHOLDER ENGAGEMENT Experimental campaign

  27. Stakeholder Involvement with the ISTAR Testbed Experimentation Process Implement Components Readiness Review Experimental Design Data Preparation Resource Preparation Technical Design Test Bed Preparation Experiment Setup Conduct Experiment After Action Review Analyse Results Prepare Report Agree Aim Review Design Support Experiment

  28. Presentation overview • Background: • What is the ISTAR Testbed? • Why do we need it? • What is its scope? • Where does it fit in? • Technical issues: • Designing the Testbed • Key features • Documenting the Testbed • Lessons Learned so far (Experiment Conduct) • Ensuring stakeholder engagement • Maximising exploitation of results • Summary

  29. Maximising Exploitation of Results ISTAR Testbed Programme Experimental campaign Investigation Investigation 1 Investigation 5 Investigation 2 Investigation 4 Investigation Investigation 3 NITEworksNEC Themes NITEworks ISTAR Themes Collective Training Programme AFRICAN SHIELD GIBRALTAR FORUM JOINT FALCON (ACC/LCC) CYPRUS FORUM RAPID ALLIANCE (US/UK) JOINT VENTURE Supported Recommendations across all 6 Lines of Development

  30. A spin-off benefit • In most military collective training exercises the intelligence staff get used to help control the exercise. • That means that the intelligence staff only get their own specific training and then live operational experience. • The involvement of real operators in ISTAR Testbed experiments provides them with a valuable additional collective training experience.

  31. Presentation overview • Background: • What is the ISTAR Testbed? • Why do we need it? • What is its scope? • Where does it fit in? • Technical issues: • Designing the Testbed • Key features • Documenting the Testbed • Lessons Learned so far (Experiment Conduct) • Ensuring stakeholder engagement • Maximising exploitation of results • Summary

  32. Summary The ISTAR Testbed will: • Look to 2010 and beyond • Assist the development of Future ISTAR capability by visualising new concepts, new doctrine and new procedures • Define new equipment requirements and prototype these where required • Demonstrate the implications of new concepts doctrine and procedures on existing and future organisations • Help define manpower requirements • Demonstrate both individual and team training needs • Deliver a SE into the bargain

  33. W Mars mega Concept Evaluation I S T A R DEC ISTAR Team Isosceles Live Experimentation Questions? Contacts: EDS Defence QinetiQ Raytheon Kym Rawlings Chris Girdlestone John McCulloughkym.rawlings@eds.comcgirdlestone@qinetiq.comjmccullough@raytheon.com

More Related