Open joebayles opened 6 years ago
These are amplifiers which are not transmitted via SIDC.
Agreed, but regardless, they should be supported.
@twornicki has a path forward, will share.
@twornicki @ottenw @wmcgrane
While engagement is not currently transmitted in the SIDC, the standard spends four pages explaining what this should look like. What messages would transmit the following codes? This is imperative for implementers to fully support MIL-STD-2525 and/or APP-6.
Engagement amplifier bar structure: A:BBB-CC Part 1 - A - Engagement Location Part 2 - BBB - Engagement State Part 3 - CC - Weapon Deployment
Code | Location |
---|---|
Local | |
R | Remote |
B | Mixture |
Code | State |
---|---|
ASN | Assign/Cover |
ENG | Engage |
MIF | Missile in Flight |
CF | Cease Fire |
CE | Cease Engage |
HF | Hold Fire |
TE | Terminate Engagement |
BE | Break Engagement |
MBE | Management by Exception |
M<T | MBE Less than Threshold |
MLT | Multiple Engagements |
MIF | Mixture |
Code | Weapon |
---|---|
M | Missile |
BM | Ballistic Missile |
CM | Cruise Missile |
GN | Gun |
T | Torpedo |
A | Attack Aircraft |
C | Combat Air Patrol |
D | Defensive Counter-Air |
UW | Undersea Warfare |
MW | Mine Warfare |
SW | Surface Warfare |
EA | Electronic Attack |
ED | Electronic Defense |
UV | Unmanned Vehicle |
CW | Close-in Weapon System |
L3 | LAMPS |
VA | Vertical Launch ASROC |
## | Number of Engagements (02+) |
FYI @jeconley
@joebayles @Twornicki @wmcgrane This category of amplifiers was brought in either by Navy or Air Force, so I'll guess the message standard would be MIL-STD-6016 Link 16
This was brought in by a USN MIL07-64 change proposal. How the information is transferred is unknown by me.
That makes sense, it's a Dr. Jake submitted change proposal from back when he was contracted to support Missile Defense Agency (MDA).
There are several graphics in the beginning of the standard that do not make it into the codes, to include:
See below for examples
Suggest we discuss how to support this.