1 / 21

Support concept for creation and use of doctrines

How to Present Planning Items in a Combat Direction System Annette Kaster, FGAN-FKIE, Werthhoven, Germany IST-036/RWS-005 Halden, Norway. Support concept for creation and use of doctrines.

tamarr
Download Presentation

Support concept for creation and use of doctrines

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. How to Present Planning Items in a Combat Direction SystemAnnette Kaster, FGAN-FKIE, Werthhoven, GermanyIST-036/RWS-005 Halden, Norway Support concept for creation and use of doctrines

  2. Ergonomic support concept for creation and use of marine doctrinesPrototype demonstrationRepresentation and visualisation issues Content

  3. AAWS Combat Direction System ASuW LINK APAR Smart-L VLS Mk 41 (24 SM-2, Blk IIIA, 32 ESSM) RAM a (Blk 0/1) RAM f (Blk 0/1) ASW NAV COMMS EW target system: F124 Combat System (CS) T1 Configuration of Sensors and Effectors

  4. Doctrines ... T3 ... configure the system behaviour ... allow depending on situation data (tactical, technical, environmental) • a timely confirmation of weapon systems • a definition of essential parameter adjustments =>considerable influence on system behaviour ... support the user in time-critical situations ... considerate mission situations (threat, geography, etc.) ... control a multitude of parameters (situation data ~ 27.000, operational parameters ~ 760) situation dependent events „trigger“ doctrines time dependent events „trigger“ „TimeTables“

  5. Doctrines T3 • structure: Trigger -> Condition --> Action ON .. -> IF ... --> THEN Trigger/Condition: time, OperatorAction, any kind of events Action: modification of values of operational parameters, Operator Notification, Activation (De-) of doctrines • Example Doctrine: Air_Threat_Warning_Red • on ATW Shift • If ATW = RED • thenEffector Params = ready • ON = "Check Chaff Course; Comms to plain, weapons to state ready "

  6. process:doctrine creation/ administration/ use PreparedDoctrineDatabase Doctrine developer: Creation of basic doctrines and time tables On land Mission planner: Selection of doctrines Mission Determination of"Formal parameters" MissionDoctrine Database user: Use of doctrines On board

  7. "UkENDo"-Demonstrator (architecture)  User interfaces: time tables and doctrines technical und tactical data and mission data Doctrine editor Doctrine database simulation control, monitoring and activation and deactivation of doctrines monitoring and control of system parameter    doctrines Situational data Inference engine • scenario • own ship data • cinematics • mission data • object relations • system-parameter • notification Main control unit trigger actions visualisation of situational parameters (text/graphics/flow charts/ process diagrams) visualisation of situational data (GIS/displays) DB management time control

  8. Scenario Transit >> HOSTILE / SUSPECT SURFEX Ende SURFEX Start ADEX Ende Area Silkworm Harm / Kormoran EMCON Plan automatic-iff-interrogation IFF wartime ID codes >> FAKER / JOKER Mirage Sea Harrier ADEX Start Radarsteuerung Hafengrenze 12-Meilen-Zone Vorbereitung ADEX Transit Vorbereitung ADEX 12-Meilen-Zone Hafenlinie

  9. 27 0900 28 0000 29 0000 1200 1500 1800 2100 0300 0600 0900 1200 1500 1800 2100 0300 0600 0900 Open Ocean Explorer UkENDo ADEX Yellow Phase SurfEX Yellow Phase Transit Yellow Phase Transit Mission Phase Set Sensor Parameter AAW Set Sensor Parameter AAW Set Sensor Parameter AAW Set Sensor Parameter AAW Set Effector Parameter AAW Set Effector Parameter AAW Set Effector Parameter AAW Set Effector Parameter AAW Prep. Transit Yellow Phase Prep. ADEX Yellow Phase Prep. SurfEX Yellow Phase Transit START SurfEX STOP SurfEX START ADEX START Transit STOP Sea Harrier Threat Mirage Threat PA 200 Threat (Harm/Kom.) ADEX STOP Entering Leaving Area Harbour Starvanger Entering Leaving Area 12 miles Legende Radar Mode Norm Short Air Threat Warnings Aktivierung EMCON Ausführung Operation Firing Sequence Timetable Entering Leaving Silkworm SubTimetable Group of Doctrines Scenario - Time Frame

  10. "UkENDo"-Demonstrator (architecture)  User interfaces: time tables and doctrines technical und tactical data and mission data Doctrine editor Doctrine database simulation control, monitoring and activation and deactivation of doctrines monitoring and control of system parameter    doctrines Situational data Inference engine • szenario • own ship data • cinematics • mission data • object relations • system-parameter • notification Main control unit trigger actions visualisation of situational parameters (text/graphics/flow charts/ process diagrams) visualisation of situational data (GIS/displays) DB management time control

  11. Doctrine editor: ergonomical aspects • Uniformed structure of all forms for definition of doctrines/TT • user guided dialog • task oriented handling • reuse of components • definition of rules components in the language of the user • recurring elements for ergonomic consistency • selective lists for consistent input • reuse of rules • user support by presettings (defaults, range of values, ...) • graphical displays for formatted inputs • explanation component • modification of rules all the time • automatic set-up of the rule base

  12. Doctrine database: ergonomical aspects • Overview of the actual planning state • different views for doctrines • hierarchical representation of doctrines • TimeTable -> SubTimeTable -> Timed Action • Doctrine-group -> doctrine -> Immediate Action • Fading in and out of hierarchical levels • user guided dialog • Context related representation • Effective recherches

  13. Doctrine editor:setup / structure / functionality Bild Doktrinen-Editor

  14. Doctrine database:setup / structure / functionality

  15. User interfaces: time tables and doctrines technical und tactical data and mission data Doctrine editor Doctrine database simulation control, monitoring and activation and deactivation of doctrines monitoring and control of system parameter    doctrines Situational data Inference engine • scenario • own ship data • cinematics • mission data • object relations • system-parameter • notification Main control unit trigger actions visualisation of situational parameters (text/graphics/flow charts/ process diagrams) visualisation of situational data (GIS/displays) DB management time control "UkENDo"-Demonstrator (architecture)

  16. Situation database: user interface

  17. User interfaces: time tables and doctrines technical und tactical data and mission data Doctrine editor Doctrine database simulation control, monitoring and activation and deactivation of doctrines monitoring and control of system parameter    doctrines Situational data Inference engine • szenario • own ship data • cinematics • mission data • object relations • system-parameter • notification Main control unit trigger actions visualisation of situational parameters (text/graphics/flow charts/ process diagrams) visualisation of situational data (GIS/displays) DB management time control "UkENDo"-Demonstrator (architecture)

  18. demonstrator: main control unit

  19. Demonstrator: output component

  20. The variety and magnitude of data and the unpredictability of mission requirements demand support in controlling, interpreting and visualising the system state as well as the parameter adjustments.- Manual intervention has to be enabled- Complete automation is not conceivable due to the complexity of mission situations.Current constraints:- automation opposed to user-orientation- UI development in several components by various companies- restricted tools for the design of the UI especially for graphicsIssues to be addressed:- Visualisation of the system state with regard to the qualitative effect of parameter values (reading access).- Optimised tools for safe and situation related direct control of parameter adjustments (writing access). Representation and Visualisation issues Consequences, Problems and Further Research

  21. - Representation of operational parameters’ adjustments; development of "orientation guides" and procedures considering the diversity of parameter values and their logical groupings- Representation procedures for clarifying the coaction of various parameters (e.g. parameters in "function chains", mission- and user-conditional dependencies)- Representation of the actual system state and an anticipated system state (projection) after parameter changes- Change of single parameter values either manually on the basis of the presented system state or automatically by the use of doctrines. Representation of critical effects in the overall context of parameter settings.- Representation of conflict cases, e.g. detection of doctrines that are inconsistent with manually modified parameter values or that are inconsistent with automatically created doctrines. Representation and Visualisation issues Aspects to be Considered

More Related