Attachment L-08 - SAMPLE PROBLEMS 23R5108 _rev 1.docx

Attachment L-09 N00024-23-R-5108 Sample Problem:

Our Navy operates in a battlespace that is quickly growing in lethality and complexity. The Navy continues to face extreme challenges with rapidly emerging threats. As part of the fight to maintain superiority, your organization is tasked with developing training for a new EW capability, referred to as Project Stingray.

Project Stingray is a new Combat System software capability that provides the ability to ensure faster detection, more accurate identification, targeting and tracking. This new capability will also make recommendations to enhance the effectiveness of missile dissuasion weapons and tactics. This tactical capability requires the EW operator to analyze system data, make decisions, and disseminate data based on the Stingray software recommendations while ensuring alignment with tactics, techniques, and procedures. The training portion of this project is being developed in parallel with the tactical capability and must be fielded within 18 months.

Address the following:

1 – Describe the approach and associated processes to ensure the training solution will support the TSTC LVC CRD use cases (Exhibit 1, TSTC LVC CRD Use Cases Feb 2018, Version 1). Ensure training stakeholders for shipboard and shore-based training needs are addressed. Define, if any, deltas between the solution and use cases. Detail how requirements flow will be addressed.

2 – Define the management and engineering planning approach for the project. Include scope, cost and schedule, risk and risk management, resource management, testing, cyber security, safety, and communications anticipated with all participants and users. Include alignment to or recommended tailoring of the TRM Version 3 (Attachment J-10). Develop a draft POA&M including key milestones, external inputs, and critical path for this effort.

3 – In support of LVC training, describe, in technical detail the approach that ensures tracks are internally identified as training or live tracks using a method that is transparent to the trainee.

4 – Describe a testing approach that will ensure the Stingray training capability is ready for fielding with the Stingray tactical capability. Define risks as well as mitigation strategies.

5 – Detail the approach to effectively communicate the training capability to end users at ship and shore-based commands. Include how to use the training software as well as how to exercise the system appropriately to utilize this new capability.

Evaluation Response Guide

1. Demonstrate the management and technical knowledge required to execute the task.

1. Detail processes and engineering skill sets required.

1. Detail a software design & development capability.

1. Demonstrate an understanding of the system performance requirements.

1. Define the degree of risk associated with the methodology(ies) to be applied to the problem set and analytical techniques the Offeror applies to risk discovery with corresponding risk mitigation.

1. Define the required test and evaluation skills and processes.

1. Detail cyber security compliance requirements and compliance process.

1. Demonstrate an understanding of the documentation and logistics required to support the capability.

1. Detail any differences in your approach to each of the training systems, highlighting any unique interfaces or communications requirements.

1. Detail external resources and products necessary to integrate and deliver the training capability.

The responses to the above should provide a sound and executable path forward to delivering this training capability to the Fleet.

Exhibit 1, TSTC LVC CRD Use Cases Feb 2018, Version 1 (extract below – pages 7-15 )

2. (U) Capability description and training use cases.

The LVC capabilities leverage a portfolio of independent training simulators and embedded training capabilities. It is important to understand LVC does not replace these independent programs I platform synthetic training capabilities which will still be most frequently used in disaggregated (non-distributed) modes to train and assess crews at all stages in their separately defined readiness / qualification continuums. The use cases proposed in this document (section 2.1thru 2.6) provide a common point of reference for typical types and levels of training system aggregation. They form a series of building blocks which will be combined to support the Fleet Forces Command (FFC) and Commander, Pacific Fleet (CPF) distributed training Concept of Employment (CONEMP) scenarios envisioned.

These use cases define actionable training problem spaces which have somewhat common sets of technical challenges and performance requirements. They are presented in general ascending order of technical & integration difficulty. In general, participation in an LVC training event can be defined as one of three different entity perspectives: the live participant's perspective, the virtual participant's perspective, and the constructive participant's perspective. These participants are brought together to interact in a common time and space environment in the LVC training event.

Live training participants are those operational units and platforms physically deployed in the exercise environment. By definition the crewmembers of a live training participant are part of the training audience and they interact via their normal combat I mission system interfaces. Though their training experience may be enhanced by simulation supported interactions with virtual and constructive units, the live participant's sensors are simultaneously monitoring the surrounding live environment (which includes the other live participants and live background entities in the vicinity). Live exercise participants do not require a dual navigation capability because all watchstanders are oriented to the real environment & surrounding entities. The number one safety priority for the live participant is physical deconfliction with other live participants and background traffic as well as the real-world navigation hazards.

Virtual training participants are units and platforms exercising in a synthetic presentation of a remote environment (other than the real environment which surrounds them) via sensor simulation or stimulation. Ships inport, manned aircraft simulators or a transiting ship at sea conducting a BMD exercise are examples of virtual training participants. The crewmembers manning these devices interact through their normal combat/ mission system interfaces (or a high fidelity simulation of those interfaces) and are members of the training audience. Virtual units may interact with other virtual units, constructive entities as well as suitably equipped and cooperating live participants that are physically present in the remote exercise environment. A ship at sea requires a dual navigation capability to participate as a virtual platform in an LVC exercise. The bridge and selected combat system watchstanders must remain safely oriented to the surrounding real world tasks & navigation while a portion of the combat system watchstanders are isolated to participate as an independently navigating virtual platform in a completely separate remote exercise environment. Safety considerations and crew size constraints (often just one crewmember) naturally prohibit the incorporation of actual flying aircraft as virtual participants in a LVC exercise.

Constructive participants are synthetic representations of entities (with varying functionality & fidelity) that are generated for presentation to virtual or live participants in order to support achievement of training objectives. A constructive participant can be completely scripted, automated or controlled (closely or loosely) by training instructors / support personnel. The personnel (where required) who control the constructive participants are not members of the training audience. Constructive participants typically represent threat units, supporting blue units as well as background traffic. Live, virtual and constructive participants can all create (publish) constructive entities in the

Attachment L-08 N00024-23-R-5108 distributed simulation (such as emissions, weapons, munitions, countermeasures, etc) defined by common object models in the training environment.

Live participants interact with each other's live sensors as they would in any normal tactical operation. All other interactions in the LVC environment are governed by a common set of rules and must be supported by the continuous exchange of 'simulation support data' in the distributed simulation. Detections are modeled independently by sensor simulations on live, virtual and constructive participants and injected into the combat/mission systems data network where they are subjected to the same processes as live detections and then presented to the training audience (on Live and virtual participants) at their interfaces in the same manner as tactical data.

The LVC Fleet Training Operational View-1(OV-1) 2020, shown in figure (1) depicts initial capability. In 2025, for LVC to be coherently executable by all platforms at the strike group level, each participating platform, system and capability must have a synthetic training capability as well as a suitable path (driven by range and exercise scale/data rate) for continuous exchange of simulation support data. A high level summary of the critical technical tasks which must be accomplished is presented below. These are not actual technical requirements (they are not intended to define organizational responsibility for provision), but rather a summary of distributed simulation support capabilities that must be in place in order to present a single common & coherent training picture to a training audience distributed across multiple ships, aircraft and simulators to meet Fleet Training Wholeness (FTW) 2025 objectives.

Virtual and Constructive (VC) participants:

· Must generate a representation of their combat/mission systems performance as it interacts with the other entities and environmental features in the scenario

· Must generate synthetic platform navigation oriented to the environment of the live participants

· Must be provided synthetic paths for tactical (including voice) communications circuits

· Must be provided synthetic paths for participation on tactical links CEC, TDL, CDL

· Must have access to a simulation support data link to share their geographic position & vector in the training environment via standardized simulation support data distribution messages

· Must have access to a simulation support data link to share the actual state & mode of all active sensors

· being operated via standardized simulation support data distribution messages

· Must generate and share (via simulation support data link) a representation of all weapons being employed via standardized simulation support data distribution messages

· Must have access to a simulation support data link which provides a continuously updated ground truth representation of all live entities in the operating area (Blue, OPFOR Targets, background shipping, clutter, environmental impacts)

· Must have access to a simulation support data link which provides a continuously updated ground truth representation of all other virtual & constructive entities in the operating area (Blue, OPFOR Targets, background shipping)

Live Participants (underway-inflight):

· Must navigate and operate safely in the live environment

· Must have access to a simulation support data link which provides a continuously updated ground truth representation of all virtual and constructive entities in the operating area (Blue, OPFOR Targets, background shipping, clutter, environmental impacts)

· Must have a training system capable of processing the attributes of published synthetic entities and injecting coherent representations into the platform’s combat/ mission systems for presentation to the crew

· Must have access to a simulation support data link to share (with virtual and constructive participants) their geographic position & vector in the training environment via standardized simulation support data distribution messages

· Must have access to a simulation support data link to share (with virtual and constructive participants) the actual state & mode of all platform active sensors being operated via standardized simulation support data distribution messages

· Must generate and share (via simulation support data link) a representation of all simulated weapons being employed via standardized simulation support data distribution messages

· Must have access to artificial paths for LOS tactical communications and link circuits (TDL, GCCS,CDL) connectivity with virtual & constructive participants

· Must have access to sim CEC DDS for interaction with virtual and constructive participants

-;:.. CJ•

°'lli'ol S.IWa(C) OTHR lceN'¥PC tttl -•/,l/lplltQ/CI

SAGS(LVC/

p- - (LCI LC

S-,11/SS(C}

-AO'(CI

MOCICTF,.,,.._,(LJ

ECTTRN-NCTE

l;Ct ,i Mob/lo 1"/Z""Gon

IA()B{CJ SURTASS (CJ NIFC-CAF1S

Mul</-CSG ESF (LVCJ

--(VC)

En/Mncod OPFOR (VCJ

/ADS SAM•LC

C

UAS

1/C Lo,CASCII

FAC,'F/AC ILQ

-jlq Live aircraft & subs can participate but are not fully integrated into scenario

Figure (1) LVC Fleet Training Capability 2020, OV-1

Note: The below training use cases 2.1through 2.5 are FST or VC exercises routinely conducted today. Detailed descriptions are contained in the N96 Total Ship Training Capability (TSTC) Training Requirements Document (TRD) and the N98/N96 Total Ship and Aviation Training Capability (TSATC) Projected Training Environment (PTE). The training use cases in section 2.6 are new LVC requirements, enabled by this document.

2.1 ORGANIC VC TRAINING: SINGLE STATIC UNIT, INTERNAL SCENARIO GENERATION AND CONTROL (SG&C)

This use case is applicable to basic and sustainment phase tactical team and sub-team training in which close coordination and interaction is required to gain or sustain crew proficiency in order to achieve the design performance of the combat system/mission system. Typical examples are a ship in port in training mode or an aviation flight training simulator in a building ashore. It includes realistic presentation to sensors, systems, and crewmembers that have a role in the mission under training. This use case permits independent practice/ repetition of complex tactical procedures required to demonstrate competence in unit mission essential tasks. Key characteristics of this use case are:

· Exercise control: Internal unit/platform simulator control with one or more local instructor interfaces (no external interface).

· Exercise Safety:

· Systems safety - Training events involving hardware in the loop/ software in the loop shall not include or unintentionally precipitate the actuation of physical systems (gun mounts etc), emission of energy, deployment of weapons or expendables.

· Simulation data boundary integrity - ensure that simulation support data does not leak beyond the proscribed boundaries of the exercise. Prevent unintended consequences in neighboring elements, systems or external networks which are not part of the exercise.

· No concurrent tactical tasks

· All tactical systems are always oriented to a synthetic platform location

· Displayed tracks and data are all training tracks

· Links (11, 16, CEC/NIFC-CA, CDL, etc.) are organically simulated and include only the one unit in training and the supporting constructive (Cooperating Units (CU), Participating Units (PU), Joint Units (JU)) controlled by a scenario ground truth generator.

· Sensing is a function of the unit's installed sensor element's SIM/ Training mode capabilities. Data collection from the combat system and communications channels are fused with SG&C truth data and available for replay and debrief .

2.2 DISTRIBUTED VC TRAINING: SINGLE STATIC UNIT, EXTERNAL SG&C

This use case is applicable to the Basic, Integrated, Advanced and Sustainment training phases where close coordination / interaction of the ship's crew is required to gain or sustain crew proficiency and achieve the design performance of the ship's combat system. A FST-U as it is today is an example of this use case. It includes realistic presentation to sensors, systems, and individuals that have a role in the mission under training. It facilitates the demonstration of systems knowledge, tactical competence and unit level command decision-making required to accomplish unit mission essential tasks. The NCTE connection to shore based SG&C resources permits enhanced constructive entity flexibility and capacity in support of the exercise. This use case enables the training audience to learn from the training event outcomes and refine TTPs / operating modes etc. to maximize success in the expected operating situation. Key characteristics of this use case are:

· Exercise control: Internal unit/platform simulator control with one or more local instructor interfaces (no external interface). External unit/platform simulator control with one or more remote instructor interfaces.

· Exercise Safety:

· Systems safety- Training events involving hardware in the loop/ software in the loop shall not include or unintentionally precipitate the actuation of physical systems (gun mounts etc), emission of energy, deployment of weapons or expendables.

· Simulation data boundary integrity - ensure that simulation support data does not leak beyond the proscribed boundaries of the exercise. Prevent unintended consequences in neighboring elements, systems or external networks which are not part of the exercise.

· No concurrent tactical tasks

· Required platform tactical systems use synthetic location and motion

· Displayed tracks and data are all training

· Links (11, 16, CEC/NIFC-CA, CDL, etc.) are all provided via NCTE paths and include only the one unit in training and the supporting constructive and I or virtual (CU, PU, JU) in the scenario. Live links may also be used in some circumstances.

· Ship sensing is a function of the unit's installed sensor element's SIM/ Training mode capabilities. Data collection from the combat system and communications channels are fused with SG&C truth data and available for replay and debrief.

2.3 DISTRIBUTED VC TRAINING: MULTIPLE STATIC UNITS, EXTERNAL SG&C

This use case is applicable to Integrated, Advanced and Sustainment phase training where close coordination and interaction of multiple units (ships/ aircraft etc.) are required to gain or sustain crew proficiency and achieve tactical success at the Surface Action Group (SAG) or force level. A strike group FST as it is today (with ships inport interacting with various aviation simulators ashore) is an example of this use case. It includes realistic presentation to sensors, systems, and individuals that have a role in the mission under training. It facilitates the demonstration of systems knowledge, tactical competence, multi-unit coordination and command decision-making (up to Strike Group level) required to accomplish essential Naval tasks in a relevant situation. Additionally it enables learning from the training event outcomes and refinement of TTPs / operating modes etc. to maximize success in the expected operating situation. Key characteristics of this use case are:

· Exercise control: External unit/platform simulator control with one or more remote instructor interfaces. May also include one or more local instructor interfaces.

· Exercise Safety:

· Systems safety- Training events involving hardware in the loop/software in the loop shall not include or unintentionally precipitate the actuation of physical systems (gun mounts etc), emission of energy, deployment of weapons or expendables.

· Simulation data boundary integrity - ensure that simulation support data does not leak beyond the proscribed boundaries of the exercise. Prevent unintended consequences in neighboring elements, systems or external networks which are not part of the exercise.

· No concurrent tactical tasks

· All unit tactical systems using synthetic location and motion

· Displayed tracks and data are all training

· Links (11, 16, CEC/NIFC-CA, CDL etc.) are all provided via NCTE paths and include both the live units in training and the supporting constructive and/ or virtual (CUs, PUs, JUs) in the scenario. Live links are used to the maximum extent practicable.

· Sensing isa function of the unit’s installed sensor element's SIM/ Training mode capabilities. Data collection from the combat system, link, chat, and communications channels are fused with SG&C truth data and recorded information from other units and available for replay and debrief.

2.4 ORGANIC VC TRAINING: SINGLE MOBILE UNIT, INTERNAL SG&C (ADDITIVE ENVIRONMENT OR 'SUBSTITUTIVE' I.E. 'REMOTESYNTHETIC' LOCATION)* SUBSTITUTIVE CASE NOT SUITABLE FOR AIRCRAFT ACTUALLY IN FLIGHT

This use case is applicable to Basic, Advanced and Sustainment phase tactical team and sub-team training in which close coordination and interaction is required to gain or sustain crew proficiency in order to achieve the design performance of the combat system. Current examples would include an F-35 running an internally generated air-to-air training scenario or a ship conducting unit training while at sea. It includes realistic presentation to sensors, systems, and crew positions that have a role in the mission under training. This use case permits independent practice I repetition of complex tactical procedures required to demonstrate competence in unit mission essential tasks. Key characteristics of this use case are:

· Exercise control: Internal unit/platform simulator control with one or more local instructor interfaces (no external interface)

· Exercise Safety:

· Safety of navigation - physical deconfliction with obstacles and other live entities in the surrounding environment.

· Systems safety - Training events involving hardware in the loop/ software in the loop shall not include or unintentionally precipitate the actuation of physical systems (gun mounts etc) , emission of energy, deployment of weapons or expendables.

· Simulation data boundary integrity - ensure that simulation support data does not leak beyond the proscribed boundaries of the exercise. Prevent unintended consequences in neighboring elements, systems or external networks which are not part of the exercise.

· Limited concurrent tactical tasks (basic SA and safety of navigation)

· Unit tactical systems use the real location and motion, synthetic location and real motion (or both in parallel). Certain live system services (directional links, sensors, weapons systems etc.) will likely not be available during the exercise to crew stations not in training, especially in the substitutive case.

· For the stations in training, all displayed tracks and data are training in substitutive case while, in the additive case, they are a mix of synthetic and live.

· Links (11, 16, CEC/NIFC-CA, COL etc.) are organically simulated and include only the one unit in training and the supporting constructive (CUs, PUs, JUs) controlled by the TSTC SG&C. MH-60R organic aircraft simulators or the local SG&C constructive helo may be used optionally to stimulate HAWKLINK COL and Link-16.

· Ship sensing isa function of the unit's installed sensor element's SIM/ Training mode capabilities.

· Data collection from the combat system and communications channels are fused with SG&C truth data and available for replay and debrief.

2.5 DISTRIBUTED VC TRAINING: SINGLE MOBILE UNIT, EXTERNAL SG&C (ADDITIVE ENVIRONMENT OR 'SUBSTITUTIVE' I.E. 'REMOTESYNTHETIC' LOCATION)* SUBSTITUTIVE CASE NOT SUITABLE FOR AIRCRAFT ACTUALLY INFLIGHT This use case is applicable to Basic, Advanced, Integrated and Sustainment phase tactical team training in which close coordination and interaction is required to gain or sustain crew proficiency in order to achieve the design performance of the combat system. Current transiting & deployed BMD exercises are examples of this use case. This use case facilitates remote SG&C (including virtual and constructive players) for practice I repetition of complex tactical procedures required to assess and maintain competence in unit mission essential tasks. It includes realistic presentation to sensors, systems, and individuals that have a role in the mission under training. Current examples of this use case are BMD training and sustainment exercises for forward deployed BMD capable ships. Synthetic tracks and cooperating constructive units from Navy Continuous Training Environment (NCTE) are transmitted to on board platform training systems via dedicated simulation support data distribution paths. Key characteristics of this use case are:

· Exercise control: External unit/platform simulator control with one or more remote instructor interfaces. Surface ships may also include one or more local instructor interfaces.

· Exercise Safety:

· Safety of navigation - physical de-conftiction with obstacles and other live entities in the surrounding environment.

· Systems safety - Training events involving hardware in the loop/ software in the loop shall not include or unintentionally precipitate the actuation of physical systems (gun mounts etc), emission of energy, deployment of weapons or expendables.

· Simulation data boundary integrity - ensure that simulation support data does not leak beyond the proscribed boundaries of the exercise. Prevent unintended consequences in neighboring elements, systems or external networks which are not part of the exercise.

· Maintain Safety of Navigation and Situational Awareness.

· Platform tactical systems use the real location and motion, synthetic location and real motion (or both in parallel). Certain live system services (directional links, sensors, weapons systems etc.) will not be available during the exercise to crew stations not in training, especially in the remote substitutive training location use case.

· For the stations in training, all displayed tracks and data are synthetic in substitutive case while, in the additive case, they are mix of synthetic and live. This additive case reflects CFFC documented LVCconcepts.

· Links (11, 16, CEC/NIFC-CA, CDL etc.) are all provided via NCTE paths and include both the live unit in training and the supporting constructive and/ or virtual (CUs, PUs, JUs) in the scenario. MH-60R organic aircraft simulators or the local SG&C constructive helo may be used optionally to stimulate HAWKLINK CDL and Link-16.

· Ship sensing is a function of the unit's installed sensor element's SIM/ Training mode capabilities (as amplified in sections 2 and 3 of this document).

· Data collection from the combat system, link, chat and communications channels are fused with external SG&C truth data via the internal SG&C and available for replay and debrief.

2.6 DISTRIBUTED LVCTRAINING: MULTIPLEMOBILE UNITS

The new use cases described in section 2.6 have been added to better differentiate the anticipated impact of scale on common exercise perception at sea. Although similar in principle to the use case described in the preceding section (2.5) the expansion to include multiple ships training at sea on a range in a common distributed scenario will introduce additional non-trivial technical requirements.

2.6.1.DISTRIBUTED LVC TRAINING: MULTIPLEMOBILEUNITS, EXTERNAL SG&C (ADDITIVE ENVIRONMENT)

This use case is applicable to Integrated, Advanced and Sustainment phase training where close coordination and interaction of multiple units (ships/ aircraft etc.) are required to gain or sustain crew proficiency and achieve tactical success at the Surface Action Group (SAG) or force level. This use case facilitates remote SG&C (including virtual and constructive players) for practice I repetition of complex tactical procedures required to assess and maintain competence in unit mission essential tasks. Conducted on a range, it includes realistic presentation to sensors, systems, and individuals that have a role in the mission under training. Synthetic tracks and cooperating constructive units from Navy Continuous Training Environment (NCTE) are transmitted to training system equipped & participating platforms underway or in flight (via dedicated simulation support data distribution paths) where they are combined with locally sensed data from the surrounding environment. In this additive case tactical links will be active locally, exchanging simulation support data via normal tactical paths. This use case facilitates the demonstration of systems knowledge, tactical competence, multi-unit proficiency and command decision-making (up to Strike Group level) required to accomplish essential Naval tasks in a relevant situation. Additionally it enables learning from the training event outcomes and refinement of TTPs / operating modes etc. to maximize success in the expected operating situation. Key characteristics of this use case are:

· Exercise control: External uniUplatform simulator control with one or more remote instructor interfaces. Surface ships may also include one or more local instructor interfaces.

· Exercise Safety:

· Safety of navigation - physical de-confliction with obstacles and other live entities in the surrounding environment.

· Systems safety- Training events involving hardware in the loop/ software in the loop shall not include or unintentionally precipitate the actuation of physical systems (gun mounts etc), emission of energy, and deployment of weapons or expendables.

· Simulation data boundary integrity - ensure that simulation support data does not leak beyond the proscribed boundaries of the exercise. Prevent unintended consequences in neighboring elements, systems or external networks which are not part of the exercise.

· Limited concurrent tactical tasks (basic Situational Awareness and safety of navigation)

· Ship tactical systems use the real location, navigation and motion. Geographic colocation of participating live units is required. Certain live system services(directional links, sensors, weapons systems etc.) will not be available during the exercise to crew stations not in training.

· For the crew in training (in this additive use case) the tracks and data displayed are mix of synthetic and live. The individual unit combat system will be generating both live and sim tracks as well as receiving remote link tracks. The unit combat system will have the capability to correlate tracks, change ID and conduct other manipulations to maintain an accurate tactical picture.

· Local ship TSTC will convert "live" threats, background entities and non-NCTE linked blue entities sensed in the surrounding environment (tracked by ownship's sensors & systems) into scenario ground truth data for consumption by sensor and weapons models resident in the remote NCTE constructive and /or virtual (CUs, PUs, JUs) participating in the training event.

· Local ship TSTC must also collect and forward locally sensed environmental measurements (particularly for USW exercises) for consumption by sensor and weapons models resident in the remote NCTE constructive and /or virtual (CUs, PUs, JUs) participating in the training event.

· Links (11, 16, CEC/NIFC-CA, COL,etc.) are all provided via a mix of NCTE and local live tactical paths. Live units in training (especially supporting aircraft) may use live local links. The simulated link contributions of remotely generated constructive and /or virtual (CUs, PUs, JUs) in the scenario must be supported via NCTE data paths. MH-60R organic aircraft simulators or the local SG&C constructive helo may be used optionally to stimulate HAWKLINK COL and Link-16.

· Sensing is a function of the unit's installed sensor element's SIM/ Training mode capabilities (as amplified in sections 2 and 3 of this document).

· Data collection from the combat system, link, chat and communications channels are fused with SG&C truth data via the internal SG&C and other participating platform information and is available for replay and debrief. Data is available for offboard data analysis.

2.6.2.DISTRIBUTEDLVC TRAINING: MULTIPLEMOBILE UNITS, AT SEA, EXTERNAL SG&C(SUBSTITUTIVE ENVIRONMENT)* NOT SUITABLE FOR AIRCRAFT ACTUALLY INFLIGHT

This use case is applicable to Integrated, Advanced and Sustainment phase training where close coordination and interaction of multiple units (ships/ aircraft etc.) are required to gain or sustain crew proficiency and achieve tactical success at the Surface Action Group (SAG) or force level. This use case is very similar to inport use case described in section 2.5 in that it facilitates remote SG&C (including virtual and constructive players) for practice / repetition of complex tactical procedures required to assess and maintain competence in unit mission essential tasks. A key difference is that in this case the ships are underway on a range and navigating IAW independent real world requirements. As a result, simulation support data (including the synthetic environment, all the entities in it, and the interactions between entities) must be distributed via the ship's long haul satellite connections such as; Integrated Shipboard Network System (ISNS) or Consolidated Afloat Networks and Enterprise Services (CANES). It includes realistic presentation to sensors, systems, and individuals that have a role in the mission under training. It facilitates the demonstration of systems knowledge, tactical competence, multi-unit coordination and command decision-making (up to Strike Group level) required to accomplish essential Naval tasks in a relevant situation. Additionally it enables learning from the training event outcomes and refinement of TTPs / operating modes etc. to maximize success in the expected operating situation. Key characteristics of this use case are:

· Limited concurrent tactical tasks (basic Situational Awareness and safety of navigation)

· Ship tactical systems in training use the synthetic course, speed, position and real motion. Certain live system services (directional links, sensors, weapons systems etc.) will not be available during the exercise to crew stations not in training.

· The exercise environment, the entities that populate it and unit navigation within the environment are entirely synthetic. Geographic colocation of participating units is not required.

· For the stations in training, all displayed tracks and data are synthetic in this substitutive case.

· Links (11, 16, CEC/NIFC-CA, CDL etc.) are all provided via NCTE paths and include both the live unit in training and the supporting constructive and/ or virtual (CUs, PUs, JUs) in the scenario. MH-60R organic aircraft simulators or the local SG&C constructive helo may be used optionally to stimulate HAWKLINK/CDL and Link-16.

· Ship sensing is a function of the unit's installed sensor element's SIM/ Training mode capabilities (as amplified in sections 2 and 3 of this document).

· Data collection from the combat system, link, chat and communications channels are fused with SG&C truth data via the internal SG&C and other participating platform information and is available for replay and debrief. Data is available for offboard data analysis.

image5.png image6.png