1 / 22

UkENDo: Doctrine Support Concept for AAWS Combat Direction System

This research project explores the development of a support concept for the creation and use of doctrines in the UkENDo AAWS Combat Direction System. It focuses on problem identification and the configuration of sensors and effectors to improve system optimization. The project also aims to shift the intelligence for system configuration from on-board users to doctrine developers, allowing for automatic adaptation and adjustment to operational parameters based on specific situations.

staggers
Télécharger la présentation

UkENDo: Doctrine Support Concept for AAWS Combat Direction System

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. Research project „UkENDo“ Support concept for creation and use of doctrines

  2. UkENDo - Problem

  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. APC - Air Picture Compilation • TMAC • MLET • LTH • MSAT • HATD • CLID • DI • DACD • SFPA • DOM • TVIEW • VI • VKD • VA • VACD NRTH • IFFH • ADH • DLILFT • DLISAT • DLIIP • SLP TEQR - Threat Evalution Quick Reaction TIC TAG DQR FüWES-Software F124 CDS (TSA) TSA - Tactical Situation Analysis • IFFH

  5. Principal task of „Doctrines“ T3 Configuration of system behaviour based on decision rules(Configuration of technical systems/set up of parameter sets ) Particular decision rules ( named as doctrines in CDS F 124 ) set up total paramter sets with new values - dependent on definite situations. • system optimization of on board systems • user support in time critical situations • consideration of mission situations (threat, geography, etc.)

  6. Theoretical Approach (1) T3 Doctrines - shift the „intelligence“ for system configuration from on board user to doctrine developer - support the user in system configuration - allow an automatical adaptation of system configuration - admit to adjust to „operational parameter“ and parameter settings - structure: Trigger -> Condition --> Action ON .. -> IF ... --> THEN Trigger/Condition: time, OperatorAction, any kind of events Action: modification of values of operatinal parameters, Operator Notification, Activation (De-) of doctrines

  7. Theoretical Approach (2) T3 Operational Parameter (OP`s) - variable parameters within implemented algorithms - admit the optimisation of an algorithm on specific missions - offer the opportunity: ... of automatic systemconfiguration(by doctrines) ... of automatic systemconfiguration (by manual setting of OP´s or triggers of a doctrine) - can be: ... simple manipulated variable (z.B. Time Out) ... complex structures

  8. Project parts T2 • Selection of exemplary doctrines in the areas sensor control, identification, classification (TSA (tactical situation analysis)) und combat planning (APS (action plan synthesis)) • parameter settings based on doctrines • actions "Operator Notification" and "Doctrine Activation" • special doctrine releases (Trigger) "Operator Input" and "Time" • presentation of potential weaknesses • concept of use for the work with doctrines • development of a demonstrator for the support concept

  9. Doctrine editor T5 Requirements: • Input of the basic data (functionalities, Op.Params) • rough planing of an operation • detailed planing of an operation (system configuration according to the serial plan) • reaction to changes in the operational plan • reaction to requirements of the mission Functionality: • input and processing of meta rules • input and processing of basic data • preparation of the rule packages for the specific application • connection to a scenario generator

  10. Access-tab. Access-tab. t t UkENDo-Demonstrator 1) loading objects + initial values (Oper. Param + Sit. Data) 2) start for szenario/mission Input Szenario/environment Doctrine editor doctrines reactions to events if Trigthen Oper. Sett. Szenario generator Own ship data Input • Output: • list • graphic • text message • diagram (process diagram) • trace (history) • (depending on typ of param) 2) inference engine • Oper. Par. • effectors • sensors • Oper. Notification • Sit. Data • szenario • cinematics • Oper. Param • Def. Settings • main controller • DB manager • timer trigger 1) Initial values 2)Default Settings Working Memory • TSA module (Tactical situation analysis) • relation between objects output mission (order, rules of engagement) input

  11. Access-tab. Access-tab. t t UkENDo-Demonstrator 1) loading objects + initial values (Oper. Param + Sit. Data) 2) start for szenario/mission Input Scenario/environment UI for inputting and editingtime tables and rules Doctrine editor doctrines reactions to events if Trigthen Oper. Sett. Scenario generator Own ship data Input • Output: • list • graphic • notice • text message • diagram (process diagram) • trace (history) • (depending on typ of param) UI for inputting and editing scenario and own ship data, Operational Parameters default settings ... UI for(defining simulation time,starting simulation and) monitoringrules activity 2) inference engine • Sit. Data • szenario • cinematics • Oper. Param • Def. Settings • main controller • DB manager • timer • Oper. Par. • effectors • sensors trigger UI for monitoring the change in Operational Parameters and Situational Data due to mission progress UI for displaying Operator Notifications 1) Initial values 2)Default Settings Working Memory • TSA module (Tactical situation analysis) • relation between objects output mission (order, rules of engagement) input

  12. Access-tab. Access-tab. t t UkENDo-Demonstrator 1) loading objects + initial values (Oper. Param + Sit. Data) 2) start for szenario/mission Input Scenario/environment UI for inputting and editing time tables and rules Doctrine editor doctrines reactions to events if Trigthen Oper. Sett. Scenario generator Own ship data Input • Output: • list • graphic • notice • diagram (process diagram) • trace (history) • (depending on typ of param) 2) inference engine • Sit. Data • szenario • cinematics • Oper. Param • Def. Settings • main controller • DB manager • timer • Oper. Par. • effectors • sensors trigger 1) Initial values 2)Default Settings Working Memory • TSA module (Tactical situation analysis) • relation between objects output mission (order, rules of engagement) input

  13. Access-tab. Access-tab. t t UkENDo-Demonstrator 1) loading objects + initial values (Oper. Param + Sit. Data) 2) start for szenario/mission Input Scenario/environment Doctrine editor doctrines reactions to events if Trigthen Oper. Sett. Scenario generator Own ship data Input • Output: • list • graphic • notice • text message • diagram (process diagram) • trace (history) • (depending on typ of param) UI for inputting and editing scenario and own ship data, Operational Parameters default settings ... 2) inference engine • Sit. Data • szenario • cinematics • Oper. Param • Def. Settings • main controller • DB manager • timer • Oper. Par. • effectors • sensors trigger 1) Initial values 2)Default Settings Working Memory • TSA module (Tactical situation analysis) • relation between objects output mission (order, rules of engagement) input

  14. Access-tab. Access-tab. t t UkENDo-Demonstrator 1) loading objects + initial values (Oper. Param + Sit. Data) 2) start for szenario/mission Input Scenario/environment Doctrine editor doctrines reactions to events if Trigthen Oper. Sett. Scenario generator Own ship data Input • Output: • list • graphic • notice • text message • diagram (process diagram) • trace (history) • (depending on typ of param) UI for (defining simulation time, starting simulation and) monitoring rules activity 2) inference engine • Sit. Data • szenario • cinematics • Oper. Param • Def. Settings • main controller • DB manager • timer • Oper. Par. • effectors • sensors trigger 1) Initial values 2)Default Settings Working Memory • TSA module (Tactical situation analysis) • relation between objects output mission (order, rules of engagement) input

  15. Access-tab. Access-tab. t t UkENDo-Demonstrator 1) loading objects + initial values (Oper. Param + Sit. Data) 2) start for szenario/mission Input Scenario/environment Doctrine editor doctrines reactions to events if Trigthen Oper. Sett. Scenario generator Own ship data Input • Output: • list • graphic • notice • text message • diagram (process diagram) • trace (history) • (depending on typ of param) 2) inference engine • Sit. Data • szenario • cinematics • Oper. Param • Def. Settings • main controller • DB manager • timer • Oper. Par. • effectors • sensors trigger UI for monitoring the change in Operational Parameters and Situational Data due to mission progress UI for displaying Operator Notifications 1) Initial values 2)Default Settings Working Memory • TSA module (Tactical situation analysis) • relation between objects output mission (order, rules of engagement) input

  16. IST-05 Reference Model

  17. UkENDo picturedin the IST-05 Reference Model • Dataspace • Operational Parameters + Situational Data (as input for engine/rule system) • Operational settings (output from rules, inference results) • technical situation (system configuration/own ship data - fromsome database, e.g. ACCESS) • tactical situation (scenario, objects/relations between objects, mission/ROE - from a scenario generator, ACCESS DB)) • Doctrines (all) (input from user) • Doctrines PDB (input from user) • Doctrines MDB (input from user)

  18. UkENDo picturedin the IST-05 Reference Model Engines ILOG-Rules (rule system/inference system) LOTUS Notes (data file management system as frontend to rule system/rule editor) MS-ACCESS (Operational Parameter, own ship data, relation between objects, mission: Input to rule system - may be used as visualisation system ?) Scenario generator (provides tactical situation) xIRIS (used for presenting the tactical situation)

  19. UkENDo picturedin the IST-05 Reference Model Input devices keyboard, mouse

  20. UkENDo picturedin the IST-05 Reference Model Output devices display screen

  21. UkENDo picturedin the IST-05 Reference Model • Visualising • technical situation (system status) • tactical situation (scenario, mission) • rule structure/sequence (for editing, modifying, ...) • inference process (rules output) • operator notifications • most important for Navy Operator: • Operational Parameter (effectors/sensors) in form of: • list • graphic • text message • diagram (process diagram) • trace (history) • (depending on typ of param)

  22. UkENDo picturedin the IST-05 Reference Model Users Navy officers Navy operators edit/modify rules edit/modify rules structure, sort rules to create PDB/MDB trigger the MDB by scenarios for tests/simulations Enter Operational Parameter; Enter/change default settings Operational Parameter values observe output (react Monitor the system state like Navy operators/ simulations) (change in Oper. Par/Sit. Data) monitor tactical situation react to Operator Notification

More Related