Introduction
Revision History
| Date | Author | Summary |
|---|---|---|
| 15-MAR-2023 | Maj. Lucero | Revised draft |
| 16-MAR-2023 | TSgt. Bernadotte | Added emergency scenarios and procedures |
| 04-FEB-2024 | TSgt. Bernadotte | Change CCL to MEL |
Emergency Procedures
-
Maintain Control – Remain calm and identify the location of all crew members if possible
-
Analyze the Situation – Determine what has to be done according to local procedures and how much time you have
-
Take Appropriate Actions – Execute pre-coordinated actions to ensure the crew reaches safety
🤕 Crew Member Safety 🔌 CVAH Physical Issues 👨💻 CVAH Logical Malfunction 🚨 DAL System Emergency ☠ Adversary Presence
CVA/H Malfunctions vs. Emergencies
Malfunctions include, but are not limited to: | A malfunction becomes an Emergency when: |
|---|---|
| Loss of connectivity | Weapon system components/capabilities outside an individual VM are degraded or lost |
| Configuration issues | Multiple individuals encounter same weapon system malfunction |
| Missing toolsets | Individual troubleshooting efforts do not result in a weapon system fix |
| Hardware issues | |
| Damaged equipment |
Cyber Crew Lead Responsibilities
- Ensure all operators are aware of local governing procedures for emergencies at the beginning of operations:
- Geological and meteorological disturbances
- Shelter in place locations
- Active shooter procedures
- Fire evacuation procedures
- Notify all operators of the emergency
- Notify HHQ of emergency event according to Tactical Plan Communication Contracts