|
|
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
ANNEX C
(U) LOGGING ELECTRONIC KEY TRANSFERS
1. (U//FOUO) CONTROLLING AUTHORITY (CA) RESPONSIBILITIES - The COMSEC
Material Control System is not involved in accounting for electronic key, that is, key converted from
tape for OTAD or that is field generated. Each commander who directs field generation of a key
becomes its Controlling Authority (CA) and is responsible for identifying and tracking it.
Additionally, when the electrical equivalent of a tape key is distributed electronically by other than
its CA to units that do not normally hold it, the CA must be advised and must record such
distribution.
2. (U//FOUO) RECORD KEEPING - Activities that generate/convert, transmit, relay, and receive
electronic key must track these functions until each key has served its purpose. Shown below is a
suggested form for recording production and handling of electronic key in tactical applications.
Activities responsible for keeping such records may use any other form(s) or accounting means that
fulfill their operational requirements, for example, DA Form 5251-1 (CONAUTH Key Management
Worksheet) or DA Form 5251-1-R (CMCS Key Management Worksheet).
_________________________________________________________
(Classification)
(Logging Command)
(Year)
(U) ELECTRONIC KEY GENERATION AND DISTRIBUTION LOG
ID & Type
CA
Eff. Pd.
Cl.
To/At
From/At
0752ID210
52ID
1-7 AUG
S
1st BDE/52ID
311500Z JUL
KY-57/58a
0752ID210
52ID
1-7 AUG
S
521ID
311500Z JUL
KY-57/58b
0752ID210
52ID
1-7 AUG
S
1st BDE/52ID
2nd Bde/ 52ID
311500Z JUL.
311500Z JUL
KY-57/58c
U6343D03
HQ
10-16 NOV
C
2100CS
USAFE
091320Z NOV
KG-84Ad
0752ID210
52ID
1-7 AUG
S
3d Bde/52ID
2281399Z JUL
KY-57/57e
U634D03
HQ
10-16 NOV
C
2100CS
USAFE
081210Z NOV
KG-84Af
a. Typical entry for sender of field-generated key.
______________
b. Typical entry for receiver of field-generated key.
(Classification)
c. Typical entry for relayer of field-generated key.
d. Typical entry of sender for electronic key converted from tape.
e. Typical entry for physical issuer of field-generated key.
f. Typical entry for physical issuer of electronic key converted from tape.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
C-1
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
THIS PAGE IS INTENTIONALLY BLANK
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
C-2
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
ANNEX D
(U) KG-84A/C AND KIV-7/7HS OTAD PROCEDURES
1. (U//FOUO) INTRODUCTION - The KG-84A/C and KIV-7/7HS provide for encryption of
teletypewriter and digital data. They operate in full duplex, half duplex, and simplex modes and may
be used on point-to-point circuits and multi-station nets. When controlled by a DTD or a KYX-15, a
KG-84 or KIV-7 is capable of distributing electronic key via 0TAR or OTAT. A KIV-7 can also
perform OTAR functions using only a KOI-18 tape reader; see paragraph 4.b. on page D-3 below.
NOTE: (U) Throughout the remainder of this Annex, KG-84A and KG-84C equipment is
referred to as “KG-84”, and KIV-7 and KIV-7HS equipment is referred to as “KIV-7”.
2. (U) PURPOSE AND SCOPE - This annex provides standard procedures for initially keying (cold
starting) the KG-84 and KIV-7 and for accomplishing point-to-point circuit OTAR, net OTAR,
OTAT with common KEK or start-up KEK, and OTAT with multiple KEKs.
NOTE: (U) Although the tape key fill routines stated below specify use of the KOI-18 tape
reader, key may also be filled into KG-84 and KIV-7 equipment from KYK-13 and KYX-15
common fill devices and DTDs.
CAUTION: (U) Prior to cold starting KG-84/KIV-7 equipment or performing OTAR or
OTAT procedures, ensure that any fill device to be used is functioning properly and has
sufficient battery energy to complete the operation.
NOTE: (U) Substantive notes and procedural statements in this Annex are UNCLASSIFIED//
FOR OFFICIAL USE ONLY. Innocuous statements, such as “wait” and “communicate
normally” are UNCLASSIFIED.
3. (U) KG-84 AND KIV-7 COLD START - Cold starting of KG-84/KIV-7 point-to-point circuits
and multi-station nets should only be required when the circuit/net is established or when a
COMSEC equipment fails.
CAUTION: (U//FOUO) Cold starting KG-84/KIV-7 nets/circuits without updating the KEK
that is being used as a temporary OTAR TEK (i.e., without performing step 2 in paragraphs 3.a.
or 3.b. or step 3 in paragraph 3.c.) is a reportable cryptographic COMSEC incident.
a. (U//FOUO) Cold Starting Point-to-Point Circuits
NET CONTROL STATION
OUTSTATION
1. Prior to circuit activation, load appropriate
Prior to circuit activation, load appropriate
segment of KEK or start-up KEK in KG-84/KIV-7
segment of KEK or start-up KEK in
U and X1 fill positions.
KG-84/KIV-7 U and X1 fill positions.
2. Update key in NCS KG-84/KIV-7 X1 fill
Update key in OS KG-84/KIV-7 X1 fill
position.
position.
FOR OFFICIAL USE ONLY
ORIGINAL
D-1
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
NET CONTROL STATION
OUTSTATION
3. Replace key in NCS and OS KG-84/KIV-7 X1
Wait.
fill position by MK OTAR.
b. (U//FOUO) Cold Starting Multi-station Nets with Start-up KEK or Common KEK
NET CONTROL STATION
OUTSTATION
1. Prior to net activation, load appropriate segment
Prior to net activation, load appropriate
of KEK or start-up KEK in KG-84/KIV-7 U and X1
segment of KEK or start-up KEK in KG-84/
fill positions.
KIV-7 U and X1 fill positions.
2. Update key in NCS KG-84/KIV-7 X1 fill
Update key in OS KG-84/KIV-7 X1 fill
position.
position.
3. Replace key in NCS and OS KG-84/KIV-7 X1
Wait.
fill position by AK OTAR.
c. (U//FOUO) Cold Starting Multi-station Nets with OS-unique KEK
NET CONTROL STATION
OUTSTATION
1. Prior to net activation, load designated segment
Prior to net activation, load designated
of each OS's KEK in KYX-15 fill position 16 and
segment of KEK in KG-84/KIV-7 U and X1
sequentially lower.
fill positions.
2. Load KEK for first OS to be OTARed in KG-84
Wait.
or KIV-7 U and X1 fill positions.
3. Update key in NCS KG-84/KIV-7 X1 fill
Update key in OS KG-84/KIV-7 X1 fill
position.
position.
4. Replace key in KG-84/KIV-7 X1fill position of
Wait.
first OS to be rekeyed via AK OTAR.
5. Repeat steps 1 thru 4 for next OS to be rekeyed
OS being OTARed performs steps 1 thru 4.
using its KEK.
6. Repeat step 5 for each other OS to be OTARed.
Repeat step 5 for each other OS to be
OTARed
4. (U//FOUO) KG-84 AND KIV-7 POINT-TO-POINT OTAR (MK) - Only the routine prescribed
in paragraph a. below is available for performing KG-84 MK OTAR. However, KIV-7 MK OTAR
may be done by either the “regular” routine stated in paragraph a. or the “front panel” routine that is
prescribed in paragraph b.
NOTE: (U//FOUO) To accomplish OTAR on point-to-point circuit, both KG-84 or KIV-7
must hold identical TEK and KEK, and the circuit must be active.
FOR OFFICIAL USE ONLY
ORIGINAL
D-2
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
NOTE: (U//FOUO) Referring to KG-84/KIV-7 point-to-point circuit OTAR procedures as
“MK” is semantically inconsistent, because the process is accomplished without actions
by receiving terminal operators and is, therefor, “non-cooperative”.
a. (U//FOUO) Regular KG-84 and KIV-7 MK OTAR - The NCS executes the following
steps:
1. If tape TEK is used, connect KOI-18 to KYX-15.
2. Set KYX-15 MODE switch on "LD".
3. Turn “ON” empty KYX-15 toggle switch to store new TEK.
NOTE: TEK is stored in lower numbered toggle switches.
4. Press and release KYX-15 INITIATE button.
5. Within 20 seconds, pull TEK tape thru KOI-18.
NOTE: KYX-15 PARITY light flashes.
6. Turn KYX-15 MODE switch to "OFF/CK".
7. Disconnect KOI-18 from KYX-15.
8. Notify OS to expect OTAR and to refrain from transmitting until it is complete.
9. Connect KYX-15 to KG-84/KIV-7.
10. Turn KYX-15 MODE switch to “MK”.
11. Turn “ON” KYX-15 toggle switch for new TEK.
12. Press KYK-15 INITIATE button.
NOTE: If the KG-84/KIV 7 DATA LENGTH switch is set to “SYNCHRONOUS DATA”, the
FULL OPR and RCY RDY lights blink, indicating an out of sync condition and that a successful
OTAR has occurred. If the KG-84/KIV-7 DATA LENGTH switch is set to “ASYNCHRONOUS
DATA”, those lights keep cycling, indicating an out of sync condition. If these indicators are not
observed and the circuit remains in crypto synchronization, repeat steps 11 and 12.
13. Turn KG-84/KIV-7 MODE switch to “V--X”.
14. Raise and release KG-84/KIV-7 INITIATE/IND TEST switch.
15. Turn KG-84/KIV-7 MODE switch to “OPR”.
16. Turn KYX-15 MODE switch to “Z SEL”.
17. Press and release KYX-15 INITIATE button.
18. Turn KYX-15 MODE switch to “OFF/CK”.
FOR OFFICIAL USE ONLY
ORIGINAL
D-3
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
19. Turn “OFF” KYX-15 toggle switch for TEK.
20 Disconnect KYX-15 from KG-84/KIV-7.
21. Log date and time of OTAR and zeroization of TEK.
b. (U//FOUO) KIV-7 Front Panel MK OTAR - This is an optional procedure for P-T-P
circuits that allows a NCS using a KIV-7 (even if the OS uses a KG-84) to pre-load up to ten OTAR
TEKs and to perform an OTAR when a KYX-15 or AN/CYZ-10 is not available. To perform a KIV-
7 front panel MK OTAR using punched paper tape OTAR TEK that is drawn thru a KOI-18, the
NCS uses steps 1-3 and 10-32. To perform the operation using electronic OTAR TEK that is stored
in a KYK-13, the NCS uses steps 1 and 4-32.
NOTE: (U//FOUO) No KIV-7 front panel AK OTAR procedure has been developed.
1. On KIV-7, press “ONLINE” to go offline.
2. If tape OTAR TEK is used, connect KOI-18 to KIV-7.
3. Pull OTAR TEK tape segment thru KOI-18, and skip to step 10.
4. If electronic OTAR TEK is used, connect KYK-13 containing new OTAR TEK to KIV-7.
5. Turn lower KYK-13 switch to position of new OTAR TEK.
6. Turn upper KYK-13 switch to “ON”.
7. Scroll KIV-7 menu until display reads “LOAD” & press INITIATE button.
8. Scroll KIV-7 menu to select X10 fill position.
NOTE: Any empty X fill position will work, but for remainder of these procedures, X10
will be used as location of OTAR TEK, and working TEK will be in fill position X01.
NOTE: KIV-7 display reads “=LD X10”.
9. Press INITIATE button.
NOTE: If key loading was successful, KIV-7 display reads “LoadGood”. If display reads
“LoadFail”, check KYK-13 for connection error and repeat steps 4 - 9.
10. Press KIV-7 ONLINE button to establish communications.
NOTE: KIV-7 display reads “FDX TR”.
11. Scroll KIV-7 menu to “TXrekey” & press INITIATE button.
FOR OFFICIAL USE ONLY
ORIGINAL
D-4
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
12. Scroll KIV-7 menu to “=KEY X10” & press INITIATE button.
NOTE: KIV-7 display reads “REKEYING” for few seconds, the “Snd Good”, then “FDX”,
then FDX TR”.
NOTE: KIV-7 ONLINE light flashes and audio tones cycle in pattern, indicating that KIV-7
is attempting to establish communications using old OTAR TEK.
13. Press KIV-7 ONLINE button until display reads “OFF-LINE”.
14. Scroll KIV-7 menu to “SEL KEY” & press INITIATE button.
NOTE: KIV-7 display reads “REKEYING”, then “Snd Good” and then “FDX>
15. Scroll KIV-7 menu to “-KEY X10” & press INITIATE button.
NOTE: KIV-7 display reads “Key Good”.
16. Press KIV-7 ONLINE button.
NOTE: KIV-7 should establish communications. If OTAR is successful, KIV-7 display reads
“FDX TR”. Then go to step 22.
17. If OTAR not successful, press KIV-7 ONLINE button until display reads “OFFLINE”.
18. Scroll KIV-7 menu to “-SELKEY” & press INITIATE button.
19. Scroll KIV-7 menu to select key “=KEY X01.
20. Press KIV-7 ONLINE button.
NOTE: KIV-7 attempts to establish communications, and display reads “FDX TR”
constantly.
21. Repeat steps 10-16.
22. Press KIV-7 ONLINE button until display reads “OFFLINE”.
23. Scroll KIV-7 menu to “-SEL KEY” & press INITIATE button.
24. Scroll KIV-7 menu to fill position “-KEY X01”& press INITIATE button.
25. Scroll KIV-7 to “Return” & press INITIATE button.
26. Scroll KIV-7 menu to “-XFR V---X” & press INITIATE button.
27. Scroll KIV-7 menu to “-V--- X01”. & press INITIATE button.
NOTE: KIV-7 display reads “V---X Good”.
28. Press KIV-7 ONLINE button.
NOTE: KIV-7 establishes communications.
FOR OFFICIAL USE ONLY
ORIGINAL
D-5
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
29. Press KIV-7 ONLINE button until display reads “OFF-LINE”>
30. Scroll KIV-7 menu to “-ZEROIZE” & PRESS initiate button.
31. Scroll KIV-7 menu to “=ZEO X10” & press INITIATE button.
NOTE: KIV-7 display flashes “ZEROIZED”.
32. Press KIV-7 ONLINE button.
NOTE: KIV-7 establishes communications with OS. OTAR process is complete.
5. (U//FOUO) KG-84 AND KIV-7 NET AK OTAR
a. (U//FOUO) Allocating Net KEKs - If more than one KEK is used in a net, OTAR must be
accomplished by the longer, sequential method, but if a common KEK or start-up KEK is assigned
for all net OSs, the shorter, simultaneous method can be used. In either case, the effective net TEK
must be held in the NCS and OS KG-84/KIV-7 equipment, and the updated version of each OS KEK
or the updated net KEK or start-up KEK, must be retained in the NCS KYX-15 between OTAR
cycles.
NOTE: (U//FOUO) When storing KEKs to support AK OTAR, the general prohibition against
holding key in fill devices does not apply. When performing OTAR with a KYX-15, up to
fifteen OSs can be rekeyed in sequence, without changing the KYX-15. If a net has more than
fifteen active OSs, the OTAR cycle must be broken into two or more 15-OS groups. Under
that circumstance, the NCS should consider using the simultaneous OTAR routine.
b. (U//FOUO) KG-84 and KIV-7 AK OTAR - The NCS executes the following steps:
NOTE: (U) Like the KG-84/KIV-7 point-to-point OTAR process, the KG-84/
KIV-7 net OTAR process is “non-cooperative”.
NOTE: (U//FOUO) No KIV-7 Front Panel AK OTAR procedure has been developed.
1. Load new TEK into KYX-15 fill position 1.
NOTE: NCS KYX-15 must now hold new TEK in fill position 1 and current KEK for each OS or
group of OSs in fill positions 16 - 2.
2. Poll net and notify OSs to be ready for an OTAR and to refrain from transmitting until OTAR is
complete.
3. Turn KYX-15 MODE switch to “AK”.
4. Turn “ON” KYX-15 toggle switches for KEK of each OS to be rekeyed.
5. Turn “ON” KYX-15 toggle switch for TEK.
FOR OFFICIAL USE ONLY
ORIGINAL
D-6
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
6. Press and release KYX-15 INITIATE button.
NOTE: At conclusion of each AK operation, KG-84/KIV-7 XMT RDY and RCV RDY lights
flash.
7. Turn “OFF” all KYX-15 toggle switches.
8. Turn KYX-15 MODE switch to “OFF/CK”.
9. Turn KG-84/KIV-7 VAR SEL switch to vacant X fill position.
10. Turn KG-84/KIV-7 MODE switch to “V---X”.
11. Raise and release KG-84/KIV-7 INITIATE/IND switch.
12. Turn KG-84/KIV-7 MODE switch to “OPERATE”.
13. Poll net.
NOTE: Only OSs that were rekeyed can respond.
14. If there are stragglers who failed to respond, set KG-84/KIV-7 VAR SEL switch to position of
old TEK.
15. Call straggler OSs.
16. Turn “ON” KYX-15 toggle switches for straggler station KEKs.
17. Turn KYX-15 MODE switch to “AK”.
18. Repeat steps 5. thru 12.
19. When all stragglers have been rekeyed, call net and authorize return to regular communications.
20. Set KYX-15 MODE switch to “VU”.
21. Turn “ON” KYX-15 toggle switches for all OX KEKs.
CAUTION: Do not perform step 22. until all authorized OSs have been rekeyed.
22. Push KYX-15 INITIATE button.
23. Turn “OFF” KYX-15 toggle switches for all OS KEKs.
24. Turn “ON” KYX-15 toggle switch for new TEK
25. Turn KYX-15 MODE switch to “Z SEL”.
26. Press and release KYX-15 INITIATE button.
27. Disconnect KYX-15 from KG-84/KIV-7.
28. Record date / time of OTAR cycle, note any OSs dropped from or added to net, log fact that all
net KEKs have been updated and TEK zeroized from KYX-15, and note KG-84/KIV-7 location of
net TEK.
FOR OFFICIAL USE ONLY
ORIGINAL
D-7
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
6. (U//FOUO) KG-84 AND KIV-7 OTAT - Depending on how KEK is assigned within a KG-84
or KIV-7 secured net, OTAT may be accomplished either sequentially or simultaneously. In nets that
use common KEK or start-up KEK, OTAT is done by the simultaneous “MK/RV” procedure, and in
nets that use multiple KEKs, OTAT is done by the sequential “MK/RV” procedure. Both of these
routines are cooperative, in that they require specific actions by OS operators. With either routine,
each OS receiving key must be able to communicate securely with the NCS and must hold KYX-15
or AN/CYZ-10 for extracting the received key.
a. (U//FOUO) OTAT with Common KEK or Start-up KEK (MK/RV) - The following
procedural steps are required to accomplish simultaneous OTAT on nets in which all OSs hold the
same KEK:
NOTE: (U) AN/CYZ-10 may be used in place of KYX-15.
NET CONTROL STATION
OUTSTATION
1. Connect KYX-15 containing TEK to be
Communicate normally.
transferred to KG-84/KIV-7.
2. Turn "ON" KYX-15 toggle switch of key to be
Communicate normally.
transferred.
3. Poll net, notify OSs to prepare for MK/RV
Communicate normally.
OTAT, and identify tag assigned to key to be
transferred.
4. Direct OSs to turn KG-84/KIV-7 COMM MODE
Respond in polling order and set KG-84/
SWITCH to SIMPLEX mode, to acknowledge, and
KIV-7 COMM MODE switch to
then to refrain from transmitting until OTAT routine
SIMPLE.X,
is complete.
5. Turn KG-84/KIV-7 COMM MODE switch to
Wait.
SIMPLEX.
6. Direct OSs to connect KYX-15 to KG-84/KIV-7
Connect KYX-15 to KG-84/KIV-7 and turn
and turn "ON" KYX-15 toggle switch for vacant fill
“ON” KYX-15 toggle switch for vacant fill
position
position.
7. Direct OSs to turn KYX-15 MODE switch to
Turn KYX-15 MODE switch to "RV" and
"RV" and to push KYX-15 INITIATE button.
push INITIATE button.
8. Turn KYX-15 MODE switch to "MK".
Wait.
9. After 20 seconds, press KYX-15 INITIATE
After KYX-15 PARITY light blinks once,
button.
set KYX-15 MODE switch to "OFF/CK".
10. Wait.
Push KYX-15 INITIATE button and watch
for PARITY light to and watch for PARITY
light to blink.
FOR OFFICIAL USE ONLY
ORIGINAL
D-8
NAG-16F
NET CONTROL STATION
OUTSTATION
11. Wait.
Turn "OFF" KYX-15 toggle switch for
received key.
12. Poll net and query whether OTAT was
Respond in polling order and advise
successful.
whether OTAT was successful
13. Call net and direct return to normal
Communicate normally.
communications.
14. Turn "OFF" all KYX-15 toggle switches.
Turn "OFF" all toggle switches.
15. Turn KYX-15 MODE switch to “OFF/CK”.
Turn KYX-15 MODE switch to "OFF/CK".
16. Disconnect KYX-15 from KG-84/KIV-7.
Disconnect KYX-15 from KG-84/KIV-7.
17. Log OTAT date, time, and tags of keys
Log OTAT date, time, tags of keys received
transferred.
and sender.
b. (U//FOUO) OTAT with Multiple KEKs (MK/RV) - The following procedural steps are
required to accomplish sequential OTAT on nets that use multiple KEK:
NET CONTROL STATION
OUTSTATION
1. Connect KYX-15 containing key transferred and
Communicate normally.
KEKs of OSs that are to receive key to KG-84/
KIV-7.
2. Turn “ON” KYX-15 toggle switch of key to be
Communicate normally.
transferred.
3. Poll net, notify OSs to prepare for OTAT, and
Respond in polling order, then refrain from
direct them to refrain from transmitting until OTAT
transmitting until OTAT routine is
routine complete.
complete.
4. Load KEK of first OS to receive key to KG-84/
Wait.
KIV-7.
5. Alert OS that will receive key to standby for MK/
Addressed OS responds. Other OSs refrain
RV OTAT,
from transmitting.
6. Call receiving OS and advise “tag” of key to be
Record tag of key to be received.
transmitted.
7. Direct receiving OS to connect KYX-15 to KG-
Connect KYX-15 to KG-84/KIV-7 and turn
84/KIV-7 and to turn “ON” KYX-15 toggle switch
“ON” KYX-15 toggle switch for vacant fill
for vacant fill position.
position.
8. Direct OS to turn KYX-15 MODE switch to
Turn KYX-15 MODER switch to “RV” and
“RV” and to push KYX-15 INITIATE button.
push INITIATE button.
9. Turn KYX-15 MODE switch to “MK”.
Wait.
UNCLASSIFIED
ORIGINAL
D-9
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
NET CONTROL STATION
OUTSTATION
10. After 20 seconds, press KYX-15 INITIATE
After KYX_15 PARITY light blinks once,
button.
set KYX-15 MODE switch to “OFF/CK”.
11. Wait.
Push KYX-15 INITIATE button, and watch
for PARITY light to blink.
12. Wait.
Turn “OFF” KYX-15 toggle switch for
received key.
13. Call receiving OS and query whether OTAT was
Respond, and advise NCS whether OTAT
received.
was successful.
14. Repeat steps 6. thru 13. for each additional key
Repeat steps 6. thru 13., as directed by NCS.
to be transferred.
15. Repeat steps 4. thru 14. to transfer keys to other
Other OSs repeat steps 4. thru 14., as
OSs.
directed by NCS.
16. Call net and direct return to normal
Communicate normally.
communications.
17. Turn “OFF” all KYX-15 toggle switches.
Turn “OFF” all KYX-15 toggle switches.
18. Turn KYX-15 MODE switch to “OFF/CK”.
Turn KYX-15 MODE switch to “OFF/CK”.
19. Disconnect KYX-15 from KG-84/KIV-17.
Disconnect KYX-15 from KG-84/KIV-7.
20. Log OTAT date, time, tags of transferred keys,
Log OTAT date, time, tags of received keys,
and recipients.
and sender.
FOR OFFICIAL USE ONLY
ORIGINAL
D-10
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
ANNEX E
(U) KY-57/58/67 OTAD PROCEDURES
1.(U//FOUO) INTRODUCTION - The KY-57/58/67 family of tactical secure voice equipment
includes the remotely controlled KY-58 that is normally installed in ships, aircraft, vehicles, and
fixed locations, the manpack KY-57, and the KY-67 radio/COMSEC equipment that is normally
used in U.S. Marine Corps tanks. These three COMSEC equipment types are functionally similar.
2. (U//FOUO) PURPOSE AND SCOPE - This annex provides standard procedures for initially
keying (cold starting) KY-57/58/67 equipment, for generating key, and for accomplishing OTAR and
OTAT on multi-station nets and point-to-point circuits.
NOTE: Although the tape key fill routines stated below specify use of the KOI-18 tape reader,
key may also be filled into KY-57/58/67 equipment from KYK-13 and KYX-15 common fill
devices and AN/CYZ-10 data transfer devices.
CAUTION: Prior to cold starting KY-57/58/67 equipment or performing OTAR or OTAT
procedures, ensure that any fill device to be used is functioning properly and has sufficient
battery energy to complete the operation.
3. (U) KY-57/58/67 COLD START
a. (U//FOUO) Using Start-up KEK or Common KEK - To cold start a KY-57/58/67 secured
net or circuit that is being established with start-up KEK or that uses common KEK
held by all OSs, use the following steps:
NET CONTROL STATION
OUTSTATION
1. Prior to net activation time, load designated
Prior to net activation time, load desig-
segment of KEK or start-up KEK in KY-57/58/67
nated KEK in KY-57/58/67 fill positions 1
fill positions 1 and 6.
and 6.
2. Update key in KY-57/58/67 fill position 1.
Update key in KY-57/58/67 fill position 1.
3. Perform an AK OTAR to replace key in fill
Wait.
position 1.
NOTE: (U//FOUO) Failure to perform step 2 is a reportable COMSEC incident.
b. (U//FOUO) Using Multiple KEKs - To cold start a KY-57/58/67 secured net that uses a
unique KEK for each OS or a combination of OS-unique and common KEKs, use the following
steps:
NOTE: In a mixed environment, each KEK held by a group of OSs is treated like a separate
OS-unique KEK.
NOTE: Failure to perform step 2. is a reportable COMSEC insecurity.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
E-1
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
NET CONTROL STATION
OUTSTATION
1. Prior to net activation time, load designated
Take no action.
segment of each OS KEK in KYX-15 fill
positions 16 thru 2.
2. Load KEK to be used into KY-57/58/67 fill
Prior to net activation time, load desig-
positions 1 and 6.
nated segment of KEK ub KY-57/58/67
fill positions 1 and 6.
3. Update key in KY-57/58/67 fill position 1.
Update key in KY-57/58/67 fill position 1.
4. Perform AK OTAR for first OS (or net, if
Wait.
common net KEK is used) to replace key in fill
position 1.
5. Repeat steps 2 - 4 for other OSs, using their
Wait.
KEKs.
NOTE: (U//FOUO) Failure to perform step 3. is a reportable COMSEC insecurity.
4. (U//FOUO) KY-57/58/67 KEY GENERATION - To generate key with a KY-57/58/67
equipment, the NCS performs the following steps:
1. Turn "ON" KY-57/58/67 power switch.
2. Set KY-57/58/67 MODE switch to "C".
3. Connect KYX-15 to the KY-57/58/67.
4. Set KYX-15 MODE switch to "VG".
5. Turn "ON" KYX-15 ADDRESS SELECT toggle switch for vacant fill position.
6. Depress KYX-15 INITIATE button.
NOTE: Beeps are audible in KY-57/58/67 handset and KYX-15 PARITY light goes "ON".
7. Turn "OFF" KYX-15 ADDRESS SELECT toggle switch.
NOTE: If KEY is being generated for an OTAR TEK, omit step 8.
8. Log identifier given to generated key.
9. Repeat steps 4 through 8 as often as necessary to generate additional required keys.
10. Set KYX-15 MODE switch to "OFF/CK".
11. Disconnect the KYX-15 from KY-57/58/67.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
E-2
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
5. (U//FOUO) KY-57/58/67 AK OTAR - This procedure is the recommended method for
KY-57/58/67 secured nets/circuits. It is used when each net or circuit is established and when the
NCS wishes to affect an immediate change of the effective TEK. To accomplish an AK OTAR the
NCS performs the following steps:
NOTE: (U) The AK OTAR procedure is "non-cooperative", in that it requires no actions by
outstation (OS) operators, other than responding to NCS calls.
NOTE: (U//FOUO) OSs must load KEK in KY-57/58/67 fill position 6, and the NCS must
store all net KEKs in a KYX-15 or DTD between OTAR cycles.
1. Connect KOI-18 to KYX-15.
NOTE: Omit steps 1 thru 5, if TEK to be transferred is already in KYX-15.
2. Turn "ON" KYX-15 ADDRESS SELECT toggle switch for vacant fill position numbered
lower than that used for KEK (normally 1 for TEK and 16 thru 2 for TEK).
NOTE: TEK must be stored in lowest numbered fill positions and KEK must be stored in
highest numbered fill positions.
3. Set KYX-15 MODE switch to "LD".
4. Press KYX-15 INITIATE button.
5. Within 20 seconds, pull TEK tape thru KOI-18.
NOTE: KYX-15 PARITY light flashes. (If light fails to flash repeat steps 1 thru 5 or check
KOI-18 and KYX-15 for proper operation.)
6. Poll net and notify OSs to standby for AK OTAR and to refrain from transmitting until
notified by the NCS.
CAUTION: Do not proceed until all OSs have responded.
7. Connect KYX-15 to KY-57/58/67.
8. Turn "ON" KYX-15 ADDRESS SELECT toggle switches for OS KEKs.
9. Turn "ON" KYX-15 ADDRESS SELECT toggle switch for TEK to be transferred.
10. Set KYX-15 MODE switch to "AK".
11. Press KYX-15 INITIATE button.
12. Turn "OFF" KYX-15 KEK ADDRESS SELECT toggle switches.
13. Turn KY-57/58/67 KEY FILL switch to fill position 5.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
E-3
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
14. Poll net.
NOTE: Only OSs that received TEK will respond. If all OSs respond, omit steps 15.thru 19.
15. If there are stragglers, turn KY-57/58/67 KEY FILL switch to old TEK fill position.
16. Call straggler OSs.
17. Turn "ON" KYX-15 ADDRESS SELECT toggle switches for straggle OS KEKs.
18. Set KYX-15 MODE switch to "AK".
19. Repeat steps 8 thru 18.
20. When all OSs have responded, poll net and authorize OSs to resume normal operation.
21. Set KYX-15 MODE switch to "OFF/CK".
22. Turn "ON" KYX-15 toggle switches for rekeyed OS KEKs.
23. Turn "OFF" KYX-15 toggle switch for TEK.
24. Set KYX-15 MODE switch to "VU".
CAUTION: Do not perform step 24 until all authorized OSs have received new TEK.
25. Press and release KYX-15 INITIATE button.
NOTE: KYX-15 PARITY light blinks.
26. Set KYX-15 MODE switch to "OFF/CK".
27. Turn "OFF" all KYX-15 toggle switches.
28. Disconnect KYX-15 from KY-57/58/67.
29. Record date and time of OTAR cycle, note any OSs dropped from or added to net, log KEK
updates, and record KY-57/58/67 fill position number of new TEK.
6. (U//FOUO) KY-57/58/67 MK OTAR - This procedure is used when the NCS wishes to transfer
net or circuit TEK that will become effective at a future time. To accomplish a KY-57/58/67 MK
OTAR, use the following steps:
NOTE: (U//FOUO) The KY-57/58/67 MK OTAR procedure is "cooperative", in that it
requires actions by OS operators. In netted applications MK OTAR can be accomplished
sequentially, if multiple KEKs are used within a net, or simultaneously, if all OSs hold
common KEK. The simultaneous method is attractive for large, slow-speed nets.
NOTE: (U//FOUO) For both NCS and OSs, the KEK in use at the time of an MK OTAR must
be loaded in KY-57/58/67 fill position 6. When the sequential MK OTAR method is used, the
NCS must store all KEKs in a KYX-15 or DTD between OTAR cycles and must load them,
one at a time, into fill position 6 of the KY-57/58/67 being used.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
E-4
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
NET CONTROL STATION
OUTSTATION
1. Load TEK to be transferred into KYX-15.
Communicate normally.
2. Connect KYX-15 to KY-57/58/67.
Communicate normally.
3. Load KEK being used into KY-57/58/67 fill
Communicate normally.
position 6.
4. Poll net and direct OSs to refrain from transmit-
Respond in polling order, and load KEK
ting until notified by NCS.
being used into KY-57/58/67 fill position
6 (if not already loaded).
5. Direct receiving OS to prepare for MK OTAR.
Acknowledge
CAUTION: Do not proceed until all OSs have
responded.
6. Turn "ON" KYX-15 toggle switch for TEK to
Wait.
be transferred.
7. Direct receiving OS (or net, if simultaneous
Turn KY-57/58/67 KEY FILL switch to
method is being used) to turn KY-57/58/67 KEY
fill position 6, and respond (in polling
FILL switch to fill position 6 and to acknowledge.
order, if simultaneous method is being
used).
8. Turn KY-57/58/67 KEY FILL switch to fill
Wait.
position 6.
9. Set KYX-15 MODE switch to "MK".
Wait.
10 Call receiving OS (or net, if simultaneous
First turn KT-57/58/67 MODE switch to
method is being used) and direct OS(s) to turn
"RV" and then turn KY-57/58/67 KEY
KY-57/58/67 MODE switch to "RV" and KEY
TILL switch to vacant fill position.
FILL switch to vacant fill position.
11. Wait 10 seconds and press and release
Wait and listen for beeps in handset.
KYX-15 INITIATE button.
12. Wait.
Turn KY-57/58/67 MODE switch to "C".
If beeps are not heard, wait one minute
and turn KEY FILL switch to fill
position 6.
13. Wait two seconds and turn KY-57/58/67 KEY
Wait.
FILL switch to fill position 5.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
E-5
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
NET CONTROL STATION
OUTSTATION
14. Call receiving OS (or net, if simultaneous
Respond (in polling order, if simultaneous
method is being used.
method is being used).
NOTE: This brief use of future TEK is autho-
NOTE: This brief use of future TEK is
rized and is not a reportable COMSEC incident.
authorized and is not a reportable
COMSEC incident.
15. If sequential method is being used and receiv-
Perform steps 6. thru 14.
ing OS fails to respond, repeat steps 6 thru 13.
NOTE: Omit step 15 if OS responds.
16. If sequential method is being used, repeat
Perform steps 5. thru 15.
steps 5 thru 15, for each other OS to receive key.
NOTE: If simultaneous method is being used,
omit step 15.
17. If simultaneous method is being used and any
Wait.
OSs fail to respond, turn KY-57/58/67 KEY FILL
switch to fill position 6.
18. Call stragglers.
Stragglers respond in polling order.
19. Turn "ON" KYX-15 toggle switch for net
Wait.
KEK.
20. Direct stragglers to turn KY-57/58/67 MODE
Stragglers set KY-57/58/67 MODE switch
switch to "RV" and KEY FILL switch to vacant
to "RV" and KEY FILL switch to vacant
fill position.
fill position.
21. Wait 10 seconds and press KYX-15 INTIATE
Stragglers listen for beeps in handset.
button.
22. Wait.
Stragglers turn KY-57/58/67 MODE
switch to "C".
23. Wait 2 seconds and set KY-57/58/67 KEY
Wait.
FILL switch to fill position 5.
24. Call stragglers.
Respond in straggler polling order.
25. If any OS fails to respond, repeat steps 19
Affected stragglers perform steps 19
thru 25.
thru 24.
NOTE: If there are no stragglers, omit steps 19
thru 24.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
E-6
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
NET CONTROL STATION
OUTSTATION
26. When all OSs have received transferred TEK,
Set KY057/58/67 KEY FILL switch to
direct OSs to turn KY-57/58/67 KEY FILL switch
effective TEK and respond in polling
to effective TEK (not TEK just transferred) and to
order.
acknowledge.
27. When all OSs have responded, poll net and
Respond in polling order, and resume
authorize return to normal communications.
normal communications.
28. Set KYX-15 MODE switch to "OFF/CK".
Communicate normally.
29. Turn "OFF" all KYX-15 toggle switches.
Communicate normally.
30. Disconnect KYX-15 from KY-57/58/67.
Communicate normally.
7. (U//FOUO) KY-57/58/67 OTAT - The OTAT procedure is used to transfer TEK from one KYX-
15 or DTD to another, via a KY-57/58/67 secured net or circuit. Received TEK can be used on any
KY-57/58/67 secured net or circuit and, in COMSEC emergencies, on nets and circuits secured by
other COMSEC equipment. In COMSEC emergencies, the OTAT procedure may also be used to
transfer KEKs. To accomplish KY-57/58/67 OTAT, use the following steps:
NOTE: (U//FOUO) KY-57/58/67 OTAT is "cooperative", in that it requires action by OS
operators. It is possible only when the sending and receiving stations hold common KEK and
TEK. In netted applications where multiple OSs hold common KEK, the NCS must identify
which OS(s) are supposed to receive the transferred key, but cannot prevent reception by other
net stations that hold the KEK.
NET CONTROL STATION
OUTSTATION
1. Verify that KEK to be used is loaded in
Communicate normally.
KYX-15 fill position 6.
2. Load key(s) to be transferred in KYX-15,
Communicate normally.
starting with fill position 1.
3. Connect KYX-15 to KY-57/58/67.
Communicate normally.
4. Poll net and notify OSs to standby for OTAT
Respond in polling order.
and to refrain from transmitting until notified.
CAUTION: Do not proceed until all OSs have
responded.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
E-7
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
NET CONTROL STATION
OUTSTATION
5. Direct OSs that will receive key to turn KY-57/
Turn KY-57/58/67 KEY FILL switch to
58/67 KEY FILL switch to fill position 6 and to
fill position 6 and connect KYX-15 to
connect KYX-15 to KY-57/58/67.
KY-57/58/67.
NOTE: If KYX-15 or CYZ-10 is not
available, notify NCS.
6. Turn KY-57/58/67 KEY FILL switch to fill
Wait.
position 6
7. Turn KYX-15 MODE switch to
Wait.
8. Turn "ON" KYX-15 ADDRESS SELECT tog-
Wait.
gle switch to key to be passed.
9. Record tag of key to be transferred.
Wait.
10. Pass tag for key to be passed
Receiving OSs record tag of key to be
to receiving OSs and direct them to acknowledge.
passed, and respond in polling order.
11. Direct receiving OSs to select KYX-15 fill
Turn "ON" selected KYX-15 ADDRESS
position to receive transferred key, to turn
SELECT toggle switch, turn KYX-15
KYX-15 MODE switch to "RV", and to
MODE switch to "RV", and respond in
acknowledge.
polling order.
12. Direct receiving OSs to press and release
Press and release KYX-15 INITIATE
KYX-15 INITIATE button.
button.
NOTE: Beeps are audible in headset/
handset and KYX-15 PARITY light
blinks.
13. Press and release KYX-15 INITIAT button.
Wait.
14. Call receiving OSs using KEK (in KY-57/58/
Respond in polling order.
67 fill position 6).
15. Direct receiving OSs to load received key into
Load received key into KY-57/58/67 fill
KY-57/58/67 fill position 5.
position 5.
16. Turn KY-57/58/67 KEY FILL switch to fill
Wait.
position 5.
17. Call receiving OSs using transmitted key.
Respond in polling order.
NOTE: If not called by NCS in one
minute, turn KY-57/58/67 KEY FILL
switch to fill position 6 and wait.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
E-8
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
NET CONTROL STATION
OUTSTATION
NOTE: This brief use of transferred key is
NOTE: This brief use of transferred key is
authorized and is not a reportable COMSEC
authorized and is not a reportable
incident.
COMSEC incident.
18. If all receiving OSs do not respond, turn
Stragglers respond in polling order.
KY-57/58/67 KEY FILL switch to fill position 6,
advise stragglers that steps 11 thru 17 will be
repeated, and direct them to acknowledge.
19. Repeat steps 10 thru 16 for stragglers.
Stragglers respond as directed by NCS.
NOTE: If there are no stragglers omit steps 18
and 19.
20. Call net, announce that OTAT of key (tag) is
Respond in polling order.
complete, advise if additional keys are to be
transferred, and direct OSs to acknowledge.
21. If additional keys are to be transferred, repeat
React as directed by NCS.
steps 4 - 20.
NOTE: If no further keys are to be transferred,
omit step 21.
22. When all keys are transferred direct receiving
Acknowledge in polling order, and then
OSs to acknowledge and to turn KY-57/58/67
turn KY-57/58/67 KEY FILL switch to
KEYFILL switch to effective TEK.
effective TEK.
23. Turn KY-57/58/67 KEY FILL switch to effec-
Wait.
tive TEK.
24. Poll net, authorize OSs to resume normal net
Acknowledge in polling order, and resume
operation, and direct OSs to acknowledge.
communications.
25. Turn "OFF" all KYX-15 ADDRESS
Turn "OFF" all KYX-15 ADDRESS
SELECT toggle switches.
SELECT toggle switches.
26. Turn KYX-15 MODE switch to "OFF/CK".
Turn KYX-15 MODE switch to
"OFF/CK".
27. Disconnect KYX-15 from KY-57/58/67.
Disconnect KYX-15 from KY-57/58/67.
28. Log OTAT activity.
Log OTAT activity.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
E-9
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
THIS PAGE IS INTENTIONALLY BLANK
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
E-10
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
ANNEX F
(U) KYV-5, KY-99, KY-99A, AND KY-100 OTAD PROCEDURES
1. (U) INTRODUCTION - The cryptographically compatible KYV-5, KY-99/99A, and KY-100
Advanced Narrowband Digital Voice Terminal (ANDVT) equipment are designed to secure voice
point-to-point circuits and multi-station nets. ANDVT terminal configurations are identified below.
NOTE: (U//FOUO) The AN/CSZ-1A SUNBURST Processor is a portable tactical secure
communications unit that is cryptographically compatible with ANDVT equipment, but that
may not serve as an OTAR NCS. The CSZ-1A is capable of automatic rekeying (AK) OTAR,
but not of manual rekeying (MK) OTAR or of OTAT.
a. (U) TACTERM - The ANDVT tactical terminal (TACTERM) is intended for airborne,
shipboard, ground vehicular, and fixed-plant applications. It is comprised of the KYV-5 COMSEC
Module and the CV-3591 Basic Terminal Unit. The Z-ANG/Z-ANH remote control unit permits
operation in aircraft.
b. (U) MINTERM - The KY-99 and KY-99A miniature terminal (MINTERM) are light-
weight, battery-powered terminals that are intended for half-duplex, man-pack applications.
NOTE: (U//FOUO) The principal functional differences between the KY-99 and KY-99A are
that the latter does not have a lock/unlock function, but has a separate logic that is
cryptographically compatible with the KY-57/58/67 (VINSON) cryptosystem. Separate keys
must be used for ANDVT and VINSON applications.
c. (U//FOUO) AIRTERM - The KY-100 (AIRTERM) was developed for use in fixed and
rotary wing aircraft and small watercraft where KYV-5s cannot be used. The AIRTERM has a two-
chassis configuration consisting of a KY-100 main terminal that is mechanically similar to the KY-58
and a Z-AVH remote control unit that permits remote operation of the KY-100. The KY-100
incorporates all of the capabilities of the KY-99A, including a VINSON mode, and an emergency
backup key (EBK) that allows a zeroized terminal to be used for voice privacy in COMSEC
emergencies associated with law enforcement operations.
NOTE: (UFOUO) A crypto-ignition key (CIK) was designed into the KY-100 to declassify
keyed but unmanned terminals; however, this function proved unreliable and has been disabled.
2. (U) PURPOSE AND SCOPE - This annex provides standard procedures to cold start ANDVT
equipment, to generate key, and to accomplish OTAR and OTAT.
CAUTION: (U) Prior to cold starting ANDVT equipment or performing OTAR or OTAT
procedures, ensure that any fill device to be used is functioning properly and has sufficient
battery energy to complete the operation.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
F-1
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
3. (U) ANDVT COLD START
a. (U//FOUO) Using Start-up KEK or Common KEK - To cold start an ANDVT secured net
or circuit that is being established with start-up KEK or that uses common KEK held by all OSs, use
the following steps:
NET CONTROL STATION
OUTSTATION
1. Prior to net activation, load designated segment
Prior to net activation, load designated
of KEK or start-up KEK in ANDVT fill positions 1
segment of KEK or start-up KEK in
and U.
ANDVT fill positions 1 and U.
2. Update key in ANDVT fill position 1.
Update key in ANDVT fill position 1.
3.a. Set KV-5 DATA/VOICE switch to “NET” or
Set KYV-5 DATA/VOICE switch to “NET”
“P-T-P”, as appropriate.
or “P-T-P”, as appropriate.
3.b. Set KY-99/99A/100 FUNCTION switch
Set KYV-99/99A/100 FUNCTION switch
to “CT”.
to “CT”.
4. Set ANDVT KEY FILL switch to fill position 1.
Set ANDVT KEY FILL switch to fill
position 1.
5. Poll net.
Respond in polling order.
6. After all OSs have responded, replace key in
Wait.
ANDVT fill position 1 via non-cooperative AK
OTAR.
NOTE: (U//FOUO) Failure to perform step 2. is a reportable COMSEC incident.
b. (U//FOUO) Using Multiple KEKs - To cold start an OTARing ANDVT secured net that
uses multiple KEKs (either a unique KEK for each OS or a combination of OS-unique and common
KEKs), the NCS and OS use the following steps:
NET CONTROL STATION
OUTSTATION
1. Prior to net activation, load designated segment
Take no action.
of each KEK in KYX-15 fill positions 16 thru 2.
2. Load KEK of first OS to get new TEK in
Prior to net activation, load designated
ANDVT fill positions 1 and U.
segment of KEK in ANDVT fill positions 1
and U.
3. Update key in ANDVT fill position 1.
Update key in ANDVT fill position 1.
4.a. Set KYV-5 DATA/VOICE switch to “NET”.
Set KYV-5 DATA/VOICE switch to
“NET”.
4.b. Set KY-99/99A/100 FUNCTION switch to
Set KY-99/99A/100 FUNCTION switch to
“CT”.
“CT”.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
F-2
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
NET CONTROL STATION
OUTSTATION
5. Set ANDVT KEY FILL to fill position 1.
Set ANDVT KEY FILL to fill position 1.
6. Poll net.
Respond in polling order.
7. After all OSs have responded, replace key in
Wait.
ANDVT fill position 1 via non-cooperative OTAR.
NOTE: (U//FOUO) Failure to perform step 3. is a reportable COMSEC incident.
4. (U//FOUO) ANDVT KEY GENERATION - To generate key with an ANDVT, uses the
following steps:
1. Connect KYX-15 to ANDVT.
2. Turn "ON" ANDVT power switch.
NOTE: To generate key, ANDVT must contain any valid key in X1 key fill position.
3. Set KYX-15 MODE switch to "VG".
4. Turn "ON" KYX-15 toggle switch for vacant fill position.
5. Press and release KYX-15 INITIATE button.
NOTE: KYX-15 PARITY light flashes, and “pass” tone is audible in handset. KYV-5 XMIT CIPH
light goes out briefly, and KYV-5 displays “CC”. KY-99/99A/100 displays “NCD VG”.
6. Record purpose or tag of generated key on KYX-15 writing surface corresponding to fill position
in which it is stored.
7. Set KYX-15 MODE switch to "OFF/CK".
8. Press and release KYX-15 INITIATE button.
NOTE: KYX-15 PARITY light blinks.
9. Turn "OFF" KYX-15 toggle switch.
10. Repeat steps 4 thru 9 as often as necessary to generate additional required keys.
11. Disconnect KYX-15 from ANDVT.
5. (U//FOUO) ANDVT NON-COOPERATIVE AK OTAR - This is the recommended means for
replacing TEK on ANDVT secured nets and circuits. It may be accomplished either simultaneously,
for all OSs that hold KEK in common, or sequentially, one OS or group of OSs at a time, depending
on how KEK is allocated. Although the sequential method requires more net time, it is frequently
used in small, high-speed nets, because it is less prone to error and because it allows the NCS to
withhold new TEK from OSs that have been captured. To accomplish non-cooperative AK OTAR,
the NCS performs the following steps:
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
F-3
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
NOTE: (U) This procedure is “non-cooperative”, since it requires no actions by OS operators
(other than responding to NCS polls and calls). To support OTAR, an ANDVT net or circuit
must be active, with all net OSs in secure communication with the NCS.
NOTE: (U) Between OTAR cycles, the NCS stores all KEKs in a KYX-15, but each OS stores
its KEK in its ANDVT.
1. Connect KYX-15 containing new TEK and all OS KEKs to ANDVT.
2. Load TEK to be transferred into ANDVT fill position and record its number.
3. Set KYX-15 MODE switch to "AK".
4. Poll net, notify OSs to prepare for a non-cooperative AK OTAR, and direct them to refrain from
transmitting until OTAR routine is complete.
5. Turn "ON" KYX-15 toggle switch of one OS KEK.
6. Turn "ON" KYX-15 toggle switch of TEK being transferred.
7. Press KYX-15 INITIATE button.
NOTE: KYV-5 CT light goes out briefly, data preamble sidetone is audible in handset, and
ALARM light flashes.
NOTE: KY-99/99A/100 displays "TX AK", and transmit modem tone is audible in handset.
8. Turn "OFF" KYX-15 toggle switch for OS KEK.
9. Using new TEK, call receiving OS (or poll net, if simultaneous OTAR approach is being used).
10. If receiving OS (or any OSs) failed to respond, repeat steps 6 thru 9, using old TEK and each
straggler's OS KEK.
CAUTION: Before completing step 11, ensure that all OSs have received the new TEK.
11. Turn "OFF" KYX-15 toggle switch for new TEK.
12. Turn KYX-15 MODE switch to "VU".
13. Turn "ON" KYX-15 toggle switch for KEK of OS that received TEK (or the common net KEK,
if used).
NOTE: All other KYX-15 toggle switches must be "OFF".
14. Press and release KYX-15 INITIATE button.
NOTE: KYX-15 PARITY light flashes.
NOTE: KYV-5 XMIT CIPH goes out briefly, and KYV-5 displays "CC" for a few seconds.
NOTE: KY-99/99A/100 displays "NCD VU", and "pass" tone is audible in handset.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
F-4
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
16. Turn KYX-15 MODE switch to "OFF/CK".
17. If sequential OTAR method is used, repeat steps 6 thru 15, using a different OS KEK, until all
OSs have received new TEK and all KEKs are updated.
NOTE: If simultaneous OTAR method is used, omit this step.: If simultaneous OTAR method is
used, omit this step.
18. Poll net and direct resumption of communications.
19. Turn KYX-15 MODE switch to "OFF/CK".
20. Disconnect KYX-15 from ANDVT.
21. Record time and date of OTAR cycle, location of new TEK in ANDVT, and changes in net
composition, if any.
6. (U//FOUO) ANDVT COOPERATIVE AK OTAR - This procedure is the recommended means
of passing non-extractable TEK to distant ANDVT equipment, for use at a later time or so that the
receiving equipment may enter another cryptonet. To accomplish cooperative AK OTAR, use the
following steps:
NOTE: This procedure is “cooperative”, since it requires actions by each OS operator.
It may be accomplished either sequentially or simultaneously, depending on how KEK is
allocated in the net.
NET CONTROL STATION
OUTSTATION
1. Connect KYX-15 containing key to be transferred
Communicate normally.
and all OS KEKs to ANDVT.
2. Turn "ON" KYX-15 toggle switch for key being
Communicate normally.
transferred.
3. Turn "ON" KYX-15 toggle switch for net KEK
Communicate normally.
(with simultaneous procedure) or one OS KEK
(with sequential procedure).
4. Poll net, notify OSs to prepare for cooperative
Respond in polling order, and record
AK OTAR, advise OSs that will receive key of its
purpose of key to be received.
purpose (advise tag if key is not future TEK for use
on passing net), and direct OSs to refrain from
transmitting until OTAR is complete.
5. Turn KYX-15 MODE switch to "AK".
Wait.
6. Direct OSs to set KYV-5 DATA/VOICE switch
Set KYV-5 DATA/VOICE switch or KY-
or KY-99/99A/100 FUNCTION switch to “RK”
99/99A/100 FUNCTION switch to “RK”
and to wait.
and wait.
NOTE: KYV-5 XMT CIPH light goes out.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
F-5
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
NET CONTROL STATION
OUTSTATION
7. Press KYX-15 INITIATE button.
Wait.
NOTE: KYX-15 PARITY light flashes.
NOTE: If successful transfer occurred,
KYV-5 displays constant "CC".
NOTE: KYV-5 XMIT CIPH light goes out briefly
and comes back on, and AK preamble sidetone is
NOTE: If successful transfer occurred, KY-
audible in handset.
99/99A/100 displays "LOAD" (with "1"
flashing).
NOTE: KY-99/99A/100 displays "TK AK", and
transmit modem signal is audible in handset.
8.a. Wait.
KYV-5 OS turn KEY FILL switch to vacant
fill position and push KYV-5 INITIATE
switch.
NOTE: KYV-5 loads received key into
selected fill position and displays "01".
8.b. Wait.
KY-99/99A/100 OS press button to select
vacant KEY button to select vacant KEY
FILL position, and press KY-99/99A/100
INIT button to enter key.
NOTE: At first push, KY-99 99A/100
displays flashing "LOAD #" (# is selected
fill position). At second push, KY-99/99A/
100 stores key and displays "KEY #"
briefly. "Pass" tone is audible in handset.
9. Poll net (if simultaneous OTAR procedure used)
Turn KYV-5 DATA/VOICE switch to
or call OS (if sequential procedure used) and direct
“NET” or KY-99/99A/100 FUNCTION
OS(s) to turn KYV-5 DATA/VOICE switch to
switch to “CT” and respond, in polling
“NET” or KY-99/99A/100 FUNCTION switch to
order, to confirm successful key transfer.
“CT” and to respond in polling order.
CAUTION: Before completing step 10, ensure that
all OSs that should respond do so.
10. Turn "OFF" KYX-15 toggle switch for
Wait.
transmitted key.
11. Turn KYX-15 MODE switch to “VU”.
Wait.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
F-6
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
NET CONTROL STATION
OUTSTATION
12. Turn "ON" KYX-15 toggle switch for net KEK
Wait.
or OSs that received key.
NOTE: All other KYX-15 toggle switches must be
"OFF".
13. Press KYX-15 INITIATE button
Wait.
NOTE: KYX-15 PARITY light flashes and a "pass"
tone is audible in handset. KYV-5 XMIT CIPH light
goes off briefly.
NOTE: KYV-5 XMIT CIPH light goes off briefly.
NOTE: KY-99/99A/100 displays "NCD VU".
14. Turn "OFF" KYX-15 toggle switches.
Wait.
15. If sequential OTAR procedure is used, repeat
Perform actions as steps 6 thru 17 require.
steps 6 thru 17, using KEK of called OS, until key is
transferred to all OSs.
NOTE: If net KEK is used, omit this step.
16. If other keys are to be transferred, repeat steps 5
Perform actions as steps 5 thru 15 require.
thru 15 until all keys have been transferred.
17. Call net and direct resumption of
Acknowledge in polling order and resume
communications.
communications.
18. If transferred key is future net TEK, load it into
Communicate normally.
desired ANDVT fill position, and record its
location.
NOTE: If transferred key is not future TEK, omit
this step.
19. Turn KYX-15 MODE switch to "OFF/CK".
Communicate normally.
20. Disconnect KYX-15 from ANDVT
Communicate normally.
21. Record time and date of OTAR activity,
including tags of keys transferred that are not future
TEKs for use on transmitting net or circuit.
7. (U//FOUO) ANDVT OTAT - This procedure is used to transfer key that will be extracted at the
OSs and used to key another COMSEC equipment, either an ANDVT that is used on another net or
circuit or, in COMSEC emergencies, any COMSEC equipment capable of using 128-bit key. To
accomplish ANDVT OTAT, use the following steps:
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
F-7
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
NOTE: (U//FOUO) ANDVT OTAT must be performed sequentially. It is “cooperative”, since
it requires actions by OS operators. If a common KEK is used, all net OSs have the potential to
receive the transferred key, but the NCS may specify those that are required to do so.
NOTE: (U//FOUO) Except during COMSEC emergencies, KEKs may not be transmitted
electrically.
NET CONTROL STATION
OUTSTATION
1. Connect KYX-15 containing key to be transferred
Communicate normally.
to ANDVT.
2. Turn "ON" KYX-15 toggle switch for key to be
Communicate normally.
transferred.
3. Turn "ON" KYX-15 toggle switch for net KEK or
Communicate normally.
unique KEK for one OS that will receive key.
3. Turn "ON" KYX-15 toggle switch for net KEK or
Communicate normally.
unique KEK for one OS that will receive key.
4. Poll net, alert OSs that OTAT activity is about to
Respond in polling order.
take place, and direct them to refrain from
transmitting until the routine is complete.
5. Call net or receiving OS and advise "tag" of key
Respond (in polling order, if net KEK is
to be transmitted.
used), and record "tag" of key to be
received.
6. Turn KYX-15 MODE switch to "AK".
Wait.
7. Direct receiving OS(s) to connect KYK-13 or
Connect KYK-13 or KYX-15 to ANDVT,
KYX-15 to ANDVT, to select vacant KYX-15/
turn "ON" vacant KYX-15 or KYK-13
KYK-13 fill position, and to record its number.
toggle switch, and record its number.
8. Direct receiving OS(s) using KYX-15 to turn its
OSs using KYX-15 turn MODE switch to
MODE switch to "LD".
"LD".
9. Direct receiving OS(s) to turn KYV-5 DATA/
Turn KYV-5 data/voice switch or KY-99/
VOICE switch or KY-99/99A/100 FUNCTION
99A/100 FUNCTION switch to “RK” and
switch to “RK” and to press KYX-15/KYK-13
press KYX-15/KYK-13 INITIATE button.
INITIATE button.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
F-8
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
NET CONTROL STATION
OUTSTATION
10. Press KYX-15 INITIATE button.
Wait.
NOTE: KYX-15 PARITY light flashes.
NOTE: KYK-13/KYX-15 PARITY light
flashes.
NOTE: KYV-5 XMIT CIPH light goes out briefly,
and AK preamble sidetone is audible in handset.
NOTE: KYV-5 displays "EO" briefly then
"CC".
NOTE: KY-99/99A/100 displays: KY-99/99A/100
displays audible in handset.
NOTE: KY-99/99A/100 displays "TK AK"
and transmit modem signal is audible in
handset.
11. Poll net (if common KEK used) or call OS (if
Turn KYV-5 DATA/VOICE switch to
multiple KEKs are used) and direct OS(s) to set
“NET” or “P-T-P” (as appropriate) or KY-
KYV-5 DATA/VOICE switch to “NET” or “P-T-P”
99/99A/100 FUNCTION switch to “CT”,
(as appropriate) or to turn KY-99/99A/100
and to respond in polling order, if key was
FUNCTION switch to “CT”, and verify that key
received
was received.
CAUTION: Ensure that receiving OS (or all
addressed OSs, if common KEK used) verify receipt
of key, before completing step 12.
12. Turn "OFF" all KYX-15 toggle switches.
Wait.
13. Turn KYX-15 MODE switch to "VU".
Wait.
14. Turn "ON" KYX-15 toggle switch of net KEK
Wait.
or KEK of OS that received key.
15. Press KYX-15 INITIATE button.
Wait.
NOTE: KYX-15 PARITY light flashes
NOTE: KYV-5 XMIT CIPH light goes out briefly,
KYV-5 displays "CC", out briefly, KYV-5
displays "CC", and "pass" tone is audible in handset.
NOTE: KY-99/99A/100 displays "NCD VU" and
"pass" tone is audible in handset.
16. Turn "OFF" KYX-15 toggle switch.
Wait.
17. If multiple KEKs are used, repeat steps
Comply as required by steps 6 thru 16.
6 thru 16, using KEK of each other OS to receive
key, until all desired OSs verify key receipt.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
F-9
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
NET CONTROL STATION
OUTSTATION
18. If additional keys are to be transferred, repeat
Comply as required by steps 6
steps 6 thru 17.
19. Record date and time, tag, recipient(s) or all
Record date and time of each key received.
OTATed key.
20. Poll net and direct resumption of normal
Respond in polling order and resume
communications.
normal communications.
21. Turn KYX-15 MODE switch to "OFF/CK".
Communicate normally.
22. Disconnect KYX-15 from ANDVT.
Communicate normally.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
F-10
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
ANNEX G
(U) KY-68 OTAD PROCEDURES
1. (U) INTRODUCTION - The KY-68 Digital Secure Voice Terminal (and its fixed-plant
functionally equivalent, the KY-78) are capable of both OTAR and OTAT, when they are installed in
connection with TRI-TAC and MSE systems and in sole-user applications.
NOTE: (U//FOUO) In the sole-user mode of operation, two KY-68s are connected
back-to-back, with no intervening switching equipment. Both keyboards are disabled, and
signalling is accomplished automatically. When the calling terminal goes off-hook, the
receiving terminal rings, and conversation can begin when the receiving terminal goes
off-hook. The sole-user mode does not permit plain text operation.
2. (U) PURPOSE AND SCOPE - This annex provides standard procedures for accomplishing
OTAR on sole-user KY-68 circuits and OTAT on sole-user and TRI-TAC/MSE circuits secured by
the KY-68.
CAUTION: (U) Prior to performing OTAR or OTAT on KY-68 circuits, ensure that any fill
device to be used is functioning properly and has sufficient battery energy to complete the
operation.
3. (U//FOUO) SOLE-USER KY-68 OTAR - This procedure is used to remotely rekey sole-user
KY-68 terminals. KY-68s can also be rekeyed by the operator at the associated TRI-TAC or MSE
switch, but that process is beyond the scope of this manual. To accomplish sole-user KY-68 OTAR,
the calling terminal operator uses the following steps, after the answering terminal operator answers
the call:
NOTE: (U) Sole-user KY-68 OTAR requires that both KY-68s hold the same KEK and TEK.
1. Load KEK into higher numbered KYX-15 fill position.
2. Load new TEK into lower numbered KYX-15 fill position.
3. Connect KYX-15 to KY-68 with fill cable.
4. Call receiving terminal in secure mode and inform receiving operator that OTAR will occur.
5. Set KYX-15 MODE switch to "AK".
6. Turn "ON" KYX-15 toggle switch for KEK and TEK.
NOTE: All other KYX-15 toggle switches must be "OFF".
7. Push and release KYX-15 INITIATE button.
NOTE: The OS KY-68 now holds the new TEK, but the NCS KY-68 does not. To supply TEK for
future secure calls, the NCS operator must load the new TEK into his KY-68 from the KYX-15.
8. Turn KYX-15 MODE switch to "OFF/CK".
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
G-1
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
9. Disconnect KYX-15 from KY-68.
4. (U//FOUO KY-68 OTAT - To transfer key from one KYX-15 to another via TRI-TAC/MSE or
sole-user KY-68s, use the following steps:
NOTE: (U) KY-68 OTAR is “cooperative”, because it requires actions by the
receiving terminal operator.
CALLING TERMINAL
ANSWERING TERMINAL
1. Load appropriate TRI-TAC, MSE or sole-user
Take no action.
KEK in vacant KYX-15 fill position.
2. Load keys to be transferred in vacant KYX-15
Take no action.
fill positions.
3. Call receiving KY-68, advise number of keys to
Respond, load KEK in vacant KYX-15 fill
be transferred and their tags, and direct receiving
positions, and record key tags in sequence
KY-68 to verify that KEK is held.
given.
4. Connect KYX-15 to KY-68.
Connect KYX-15 to KY-68.
5. Wait.
Turn "ON" KYX-15 toggle switch for KEK.
NOTE: All other KYX-15 toggle switches
must be "OFF".
6. Wait.
Turn KYX-15 MODE switch to "LD".
7. Wait.
Move KY-68 VAR STOR switch to
"LOAD" and release.
NOTE: Two PARITY tones are audible.
8. Turn "ON" KYX-15 toggle switch for first or
Select KYX-15 fill position for key to be
next key to be transferred.
received, and turn "ON" its toggle switch.
NOTE: Other KYX-15 toggle switches must be
NOTE: Other KYX-15 toggle switches
"OFF".
must be "OFF".
9. Turn KYX-15 MODE switch to "LD".
Turn KYX-15 MODE switch to "RV".
10. Move KY-68 VAR STOR switch to "LOAD".
Wait.
NOTE: Two PARITY tones are audible.
11. Turn KYX-15 toggle switch for key to be
Wait.
transferred.
12. Turn "ON" KYX-15 toggle switch for UIRV or
Wait.
KEK.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
G-2
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
CALLING TERMINAL
ANSWERING TERMINAL
13. Turn KYX-15 MODE switch to "MK".
Push and release KYX-15 MODE
INI-
TIATE button.
NOTE: Circuit loses sync, and static is audible at
NCS.
14. Wait for sync loss, then push and release
Wait.
KYX-15 INITIATE button.
NOTE: KYX-15 PARITY light flashes and circuit
NOTE: KYX-15 PARITY light flashes and
syncs.
circuit syncs.
15. Move KYX-15 MODE SELECT switch to
Turn KYX-15 MODE switch to "OFF/CK".
"OFF/CK".
16. Wait.
Move KY-68 VAR STOR switch to
"LOAD" and release.
NOTE: KYX-15 PARITY light flashes.
17. Repeat steps 5 thru 16 for each additional key to
Repeat steps 5 thru 16 for each additional
be transferred.
key to be transferred.
18. Disconnect KYX-15 from KY-68.
Disconnect KYX-15 from KY-68.
19. Return KY-68 to "on-hook" position.
Return KY-68 to "on-hook" position.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
G-3
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
THIS PAGE IS INTENTIONALLY BLANK
UNCLASSIFIED//FOR OFFICIAL USE ONLY
G-4
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
ANNEX H
(U) KW-46 OTAD PROCEDURES
1. (U) PURPOSE - This annex provides standardized instructions for accomplishing OTAT and CV
OTAR on KW-46 secured broadcasts.
2. (U//FOUO) LOADING KEY - Broadcast Control Station (BCS), BCS on-air monitor, and
Receiving Stations (RS) must load the same CV into KW-46 fill position CV-1 and the same KEK
into fill position CV-2, using following steps:
NOTE: (U) Procedures for loading CVs and KEKs are stated in terms of the KOI-18; however,
key may also be loaded using the KYK-13, the KYX-15, and the AN/CYZ-10. All numbered
steps and associated notes and cautions are “UNCLASSIFIED//FOR OFFICIAL USE ONLY”.
CAUTION: (U) Prior to loading key into a KW-46 or performing OTAR or OTAT procedures,
ensure that any fill device to be used is functioning properly and has sufficient battery energy
to complete the operation.
1. Connect KOI-18 to KW-46 with fill cable.
2. On KW-46 depress "21" (for CV) or "22" (for KEK), "ENTER", "VERIFY", and "EXECUTE".
NOTE: KW-46 BUSY and KEY I/O lights come on.
NOTE: BCS, BCS on-air monitor, and RS must have KEK in same KW-46 fill position. If BCS
directs that KEK be loaded into a fill position other than 22, load commands change accordingly,
for example, load command 23 for KEK-
3. Pull key tape through KOI-18.
NOTE: KW-46 BUSY and KEY I/O lights go out.
3. (U) OTAT/OTAR PROCEDURES - KW-46 OTAT/OTAR procedures are stated below.
NOTE: (U//FOUO) Because most of the procedural steps for accomplishing OTAT and OTAR
are similar, they are presented in a single list. OTAT uses steps 1 - 24 and 29 thru 33, and
OTAR uses steps 1 - 16 and 25 - 33. BCS on-air monitor follows procedure for RS. All
numbered steps and associated notes and cautions are UNCLASSIFIED//FOR OFFICIAL
USE ONLY”
BROADCAST CONTROL STATION
CAUTION: BCS KWT-46 must be set to red mark input (no traffic).
1. Press “53”.
NOTE: Display reads “LINK CM”.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
H-1
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
2. Press “000001”, “ENTER”, “VERIFY”, “VERIFY”, and “EXECUTE”.
NOTE: LINK light goes out. (RS LINK light also goes out.)
3. Press “51”.
NOTE: Display reads “ACC ID”, and DATA light comes on.
4. Enter 4-digit octal number assigned as key ID.
CAUTION: 4-digit key ID must be identical to that assigned in key transfer notice message
and cannot be all zeros or ones.
5. Press “ENTER” and “VERIFY”.
NOTE: Display reads “ACC ID”.
6. Press "VERIFY".
NOTE: Display reads 4-digit key ID.
7. Press “EXECUTE”.
NOTE: Steps 8.a - 8.g cover loading key to be transferred from KYK-13; steps 9.a - 9.g cover
loading such key from KYX-15; and steps 10.a - 10.e. cover loading it from KOI-18. See Annex J
for corresponding AN/CYZ-10 procedures.
8.a. Connect KYK-13 to KWT-46 (with fill cable, if desired).
8.b. Turn KYK-13 ADDRESS SELECT switch to fill position of key to be passed.
8.c. Turn "ON" KYK-13 MODE switch.
8.d. On KWT-46 press "35".
NOTE: KWT-46 display reads "ACSV RK".
8.e. On KWT-46 press "ENTER", "VERIFY", and "EXECUTE".
NOTE: KYK-13 PARITY light and KWT-46 BUSY and KEY I/O lights blink.
8.f. Turn “OFF” KYK-13 MODE switch.
8.g. Disconnect KYK-13 from KWT-46.
9.a. Connect KYX-15 to KWT-46 with fill cable.
9.b. Turn “ON” KYX-15 toggle switch for key to be transferred.
9.c. Turn KYX-15 MODE switch to “LD”.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
H-2
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
9.d. On KWT-46 press “35”.
NOTE: KWT-46 display reads “ACSV RK”.
9.e. On KWT-46 press “ENTER”, “VERIFY”, and “EXECUTE”.
NOTE: KYX-15 PARITY light and KWT-46 BUSY and KEY I/O lights blink.
9.g. Disconnect KYX-15 from KWT-46.
9.f. Turn KYX-15 MODE switch to "OFF/CK".
10.a. Connect KOI-18 to KWT-46 with fill cable.
10.b. On KWT-46 press "35".
NOTE: KWT-46 display reads "ACSV RK".
10.c. On KWT-46 press "ENTER", "VERIFY", and "EXECUTE".
NOTE: KWT-46 BUSY and KEY I/O lights come on.
10.d. Pull tape thru KOI-18.
NOTE: KWT-46 BUSY and KEY I/O lights go off.
10.e Disconnect KOI-18 from KWT-46.
BROADCAST CONTROL STATION
RECEIVING STATION
11. On KWT-46 press "53".
NOTE: KWR-46 LINK light comes on for
approximately 50 seconds during transfer and goes
NOTE: KWT-46 display reads "LINK CM"
out on completion. KWR-46 UVRQ/REKEY light
and its DATA light comes on.
comes on, and KWR-46 becomes subject to
two-person integrity (TPI) rules unless received key
is not intended for use by receiving unit. In that
situation, a single operator may zeroize KWR-46
UVRQ fill position if done immediately.
12. On KWT-46 press "001150"
Wait.
NOTE: KWT-46 DATA light goes out.
13. On KWT-46 press “ENTER”,
Wait.
“VERIFY”, “VERIFY”, and “EXECUTE”.
14. Repeat steps 3. - 13. for each additional
Repeat steps 3. - 13. for each additional key to be
key to be transmitted.
transmitted.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
H-3
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
RECEIVING STATION
15. On KWR-46 press “54”.
NOTE: KWR-46 display reads “VARP”.
16. On KWR-46 press “ENTER”.
NOTE: KWR-46 display reads 4-digit octal number BCS assigned in key transfer notice
message; see step 4.
NOTE: If OTAR, omit steps 17 - 24 and proceed with step 25.
17. Connect KYK-13/KYX-15 to KWR-46 fill port.
RECEIVING STATION
18. On KWR-46 press “59”.
NOTE: KWR-46 display reads “ORKV”.
19. On KWR-46 press “ENTER”, “VERIFY”, and “EXECUTE”.
NOTE: KWR-46 BUSY and KEY I/O lights come on.
NOTE: Use steps 20.a & 20.b for KYK-13 key extraction or steps 21.a & 21.b for KYX-15 key
extraction. See Annex J for AN/CYZ-10 procedures.
20.a Turn KYK-13 ADDRESS SELECT toggle to location chosen to receive OTAT key.
20.b Turn “ON” KYK-13 MODE switch.
21.a Turn “ON” KYX-15 toggle switch chosen to receive OTAT key.
21.b Turn “ON” KYX-15 MODE switch.
22. Press KYK-13 OR KYX-15 INITIATE button.
NOTE: KYK-13/KYX-15 PARITY light blinks and KWR-46 BUSY, and KEY I/O light goes out.
CAUTION: As long as KWR-46 UVRQ/REKEY light is on, KWR-46 is subject to TPI rules.
Key remains available until a positive action is taken to zeroize it. This is done by the “85” - RSET
RK”
23. Turn “OFF” KYK-13/KYX-15 MODE switch.
24. Disconnect KYK-13/KYX-15 from KWR-46.
25. On KWR-46 press “7”.
NOTE: KWR-46 display reads “LRKV”.
NOTE: To load OTAR CV in a CV fill position other than CV-1 or CV-2 use steps 25 - 27.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
H-4
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
26. On KWR-46 press “3” (for CV-3), “ENTER”, “VERIFY”, and “EXECUTE’.
CAUTION: As long as UVRQ light is on, KWR-46 is subject to TPI rules.
27. On KWR-46 press “85”.
NOTE: KWR-46 display reads “RSET RK”.
28. On KWR-46 press “ENTER”, “VERIFY”, and “EXECUTE’.
NOTE: KWR-46 UVRQ/REKEY light goes out and KWR-46 is no longer subject to TPI rules.
NOTE: Repeat steps 3-37 for each additional key to be passed via OTAT or OTAR. BCS must
allow at least one minute for RSs to extract or park each transmitted key.
NOTE: After last key is passed, wait at least 2 minutes before going back to traffic.
BROADCAST CONTROL STATION
RECEIVING STATION
29. On KWR-46 press “53”.
Wait.
NOTE: KWT-46 display reads “LINK CM”.
30. On KWT-46 press “001000”, “ENTER”,
Wait.
“VERIFY”, “VERIFY”, and “EXECUTE”.
NOTE: KWR-46 LINK light comes on.
NOTE: KWR-46 on-line monitor LINK light
comes on, and UVRQ/REKEY light blinks off
briefly and then comes back on.
31. On KWT-46 remove red mark and resume
Wait.
traffic
NOTE: Traffic flow resumes.
32. On KWR-46 (on-air monitor) press “85”.
Take no action.
NOTE: KWR-46 display reads “RSET RK”.
33. On KWR-46 on-air monitor press
Take no action.
“ENTER”, “VERIFY”, and “EXECUTE”.
NOTE: KWR-46 UVRQ/REKEY light goes
out.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
H-5
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
THIS PAGE IS INTENTIONALLY BLANK
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
H-6
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
ANNEX I
(U) OTAR AND OTAT USING AN/CYZ-10
1. (U) INTRODUCTION
a. (U//FOUO) Capabilities - The AN/CYZ-10 data transfer device is capable of emulating the
KYX-15 net control device, the KYK-13 electronic transfer device, and the KOI-18 tape reader
(without being able to read punched tape) in support of OTAR and OTAT. It is also capable of
introducing unencrypted (i.e., RED) key or encrypted (i.e., BLACK) key into a STU-III, STU-IIIA,
STE, or Allied STU-IIB data port and extracting it, in the same form, at a distant STU-III, STU-IIIA,
STU-IIB, or STE terminal.
NOTE: (U) Although the procedures are identical for transferring RED and BLACK key from
one DTD to another via a secure telephone, this document only applies to RED key transfers.
b. (U) Purpose - This annex states abbreviated procedures for accomplishing processes that
affect OTAR and OTAT on nets/circuits that are secured by the KG-84A/C, KY-57/58/67, and
KYV-5 and KY-99/99A/100, and OTAT on KW-46 secured broadcasts, KY-68 secured voice
circuits, and STU-III/IIIA/IIB/STE secured telephone circuits.
NOTE: (U//FOUO) The procedures presented in this annex are based on NSA developed
“F4.09” software for the DTD. Procedural changes will be made when “Common Tier 3"
software is implemented.
2. (U//FOUO EMULATING COMMON FILL DEVICES - To configure a CYZ-10 to emulate a
KYX-15 or KYK-13, use the following steps:
1. From main menu, select “Appl” and “Fill”.
2. From fill main menu, select “Utility”, “Setup”, “Protocol”, “Cfd” and either “13” or “15”, as
appropriate.
3. (U//FOUO) LOADING DTD FROM KOI-18 - To load a DTD from a KOI-18, use the following
steps:
1. Set up DTD to emulate KOI-18, and select Abort.
2. From DTD fill main menu, select “Recv”.
3. Connect DTD to KOI-18.
4. Press RCV key on DTD.
5. Pull key tape through KOI-18.
6. Enter key tag as prompted by DTD.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
I-1
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
4. (U) LOADING DTD FROM ANOTHER DTD
a. (U//FOUO) Data Standard - Setup both DTDs to “DS-101”, using “Utility”, “Setup”, and
“Protocol” from fill main menu.
b. (U//FOUO) Sending DTD performs following steps:
1. From fill main menu, select “Xmit” and “Issue”.
2. Use P UP and P DN keys to scroll thru key data base and ENTR key to select key(s) to be
transferred.
3. Select “Send”, when finished selecting key(s), and select “Direct”.
4. Connect sending and receiving DTDs.
5. Press SEND key.
c. (U//FOUO) Receiving DTD performs following steps:
1. From fill main menu, select “Recv”.
2. Press RCV key.
NOTE: Key tag data will also be transferred to receiving DTD.
3. Disconnect sending and receiving DTDs.
5. (U//FOUO) LOADING COMSEC EQUIPMENT FROM DTD - To load an OTAR capable
COMSEC equipment from a DTD, use the following steps:
1. Set up DTD to emulate KYX-15 or KYK-13.
2. From DTD fill main menu, select “Xmit”.
3. Use DTD P UP and P DN keys to scroll thru key data base and ENTR key to select key(s) to
be transferred.
4. Select “Send”, when finished selecting key(s).
5. Connect DTD to COMSEC equipment.
6. Press DTD CLR key.
7. Press DTD SEND key.
8. Press "initiate" on COMSEC equipment.
9. Disconnect DTD from COMSEC equipment.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
I-2
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
6. (U//FOUO) PERFORMING MK OTAR - When using a DTD in lieu of a KYX-15 to accomp-
lish MK OTAR on a KG-84A/C or ANDVT secured point-to-point circuit (or to recover from KEK
updating error on a ANDVT secured circuit, the NCS must perform the appropriate COMSEC
equipment steps and the following steps with the DTD:
1. Set up DTD to emulate KYX-15.
2. From fill main menu, select “Net” and “Mk”.
3. Use DTD P UP and P DN keys to scroll thru key data base and ENTR key to select keys to be
transferred.
4. Connect DTD to COMSEC equipment.
5. Press SEND key.
6. Disconnect DTD to COMSEC equipment.
7. (U//FOUO) PERFORMING AK OTAR - To accomplish AK OTAR on a KG-84A/C, KIV-7/
7HS. KY-57/58/67, RT-1523/A, or KYV-5/KY-99/99A/100 secured multi-station net using a DTD in
lieu of a KYX-15, the NCS performs the appropriate COMSEC equipment steps and the following
steps involving the DTD:
1. Set up DTD to emulate KYX-15.
2. From fill main menu, select “Net” then “Ak”.
3. Press CLR key, and use DTD P UP and P DN keys to scroll thru KEK(s) to be used, and
ENTR key to select KEK(s).
4. Press SEND when finished selecting KEKs.
5. Press CLR key, and use ENTR key to select TEK to be transferred.
6. Select “Send”.
7. Connect DTD to COMSEC equipment.
8. Press SEND key.
9. Disconnect DTD from COMSEC equipment.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
I-3
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
8. (U//FOUO) PERFORMING OTAT - To accomplish OTAT on a KG-84A/C, KY-57/58/67, or
ANDVT secured net or circuit using an DTD in lieu of a KYX-15, the DTDs at both the NCS and
OS(s) must be set up to emulate KYX-15s.
a. (U//FOUO) NCS performs appropriate COMSEC equipment steps and following DTD steps:
1. From fill main menu, select “Net” then “Mk” or Ak”, as appropriate.
2. Use DTD P UP and P DN keys to scroll thru key data base and ENTR key to select key to be
transferred.
3. Connect DTD to COMSEC equipment.
4. Press SEND key.
5. After selected key has been transferred, repeat steps 2 thru 4 for each additional key to be
transferred.
6. After all keys have been transferred, disconnect DTD from COMSEC equipment.
b. (U//FOUO) OSs performs appropriate COMSEC equipment steps and following steps
involving the DTD:
1. From fill main menu, select “Net” then “Ak”.
2. Connect DTD to COMSEC equipment.
3. Press RCV key.
4. When OTAT transmissions are completed, disconnect DTD from COMSEC equipment.
9. (U) TRANSFERRING KEY AND TAG FROM ONE DTD TO ANOTHER VIA STU-III/
STU-IIIA/STU-IIB/STE TELEPHONE CIRCUITS
NOTE: (U//FOUO) To transfer a RED key of any classification from one DTD to
another using the data ports of attached STU-III, STU-IIIA, STU-IIB, or STE equip-
ment, both secure telephones must be configured the same, with one of the following
rates and modes: 2400 baud asynchronous, 4800 or 9600 baud synchronous. When
both ends use STEs over Integrated Services Digital Network circuits, the STEs can
be set up to 64,000 baud in synchronous mode. Additionally, the DTDs at the receiving
and sending locations must be set for the "STU" protocol. If excessive transmission
delays inhibit the DTDs from completing the key exchange, change both DTDs Time
Out to the "Slow" option, to allow the DTDs more time to negotiate the exchange.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
I-4
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
a. (U//FOUO) Sending Operator performs following steps:
1. Connect DTD to STU-III/STU-IIIA/STU-IIB/STE.
NOTE: A special connector cable (NSN 5810-O1-391-4212), that is not furnished with the
DTD, is required to connect the DTD to the STU-III/STU-IIIA/STU-IIB/STE data port. These
items may be ordered from USACCSLA Ft. Huachuca, AZ, Code: SELCL-IA,
POC: Mr. Riensche, DSN: 870-8335, COML: (520) 538-8335.
2. Call intended receiver using STU-III/STU-IIIA/STU-IIB/STE secure voice mode and inform
operator that tagged COMSEC key is to be transferred.
3. Verify with receiving operator that his DTD is set to “RS-232” mode and is connected to
STU-III/STU-IIIA/STU-IIB/STE in use.
NOTE: If not, from the fill main menu, select “Utility”, “Setup”, “Protocol”, and “Stu”.
4. Shift STU-III/STU-IIIA/STU-IIB/STE to secure data mode.
5. From DTD fill main menu, select “Xmit” and “Issue”.
6. Use ENTR and P DN keys to select keys to be transferred.
7. Press “SEND” when finished selecting keys.
8. Press DTD SEND key.
9. When all tagged keys have been transmitted, disconnect DTD from STU-III/STU-IIIA/
STU-IIB/STE.
10. Return STU-III/STU-IIIA/STU-IIB/STE to secure voice mode.
b. Receiving Operator performs following steps:
1. Respond to sending operator's call and verify that DTD is attached to STU-III/STU-IIIA/
STU-IIB/STE being used.
NOTE: See NOTE following paragraph 8.a., step 1regarding the special connector cable.
2. Verify that DTD is in “RS-232” protocol mode.
NOTE: If not, from DTD fill main menu, select “Utility”, “Setup”, “Protocol”, and “Stu”.
3. From fill main menu, select “Recv”.
4. Press either DTD ENTR key or RCV key.
5. When all tagged keys have been received, disconnect DTD from STU-III/STU-IIIA/
STU-IIB/STE.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
I-5
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
6. Return STU-III/STU-IIIA/STU-IIB/STE to secure voice mode and verify to sender that key
was received.
10. (U) TRANSFERRING JOINT TACTICAL INFORMATION DISTRIBUTION SYSTEM
(JTIDS) KEY AND TAG FROM ONE DTD TO ANOTHER VIA STU-III/STU-IIIA/STU-IIB/
STE TELEPHONE CIRCUITS USING THE “FILL” THREAD OF JFILL USER APPLICA-
TION SOFTWARE (UAS)
NOTE: (U//FOUO) The DTD Joint fill (JFILL) routine has two branches or threads,
i.e., the “FILL” thread and the “JTIDS” thread. DTD common tier three (CT3) UAS
may also be used to transfer JTIDS key and data.
NOTE: (U//FOUO) To transfer a RED JTIDS key from one DTD to another using
the data ports of attached STU-III, STU-IIIA, STU-IIB, or STE equipment, both secure
telephones must be configured the same, with one of the following rates and modes:
2400 baud asynchronous, 4800 or 9600 baud synchronous. When both ends use STEs
over Integrated Services Digital Network circuits, the STEs can be set up to 64,000
baud in the synchronous mode.
a. (U//FOUO) Sending Operator performs following steps:
1. Connect DTD to STU-III/STU-IIIA/STU-IIB/STE, using connector cable identified in
NOTE following paragraph 9.a., step 1.
2. Call intended receiver using STU-III/STU-IIIA/STU-IIB/STE secure voice mode and inform
operator that tagged JTIDS key is to be transferred via JFILL (JTIDS) - JFILL (JTIDS) routine.
3. On DTD press “U” or select “Util” and press ENTR.
4. On DTD press “S” or select “Setup” and press ENTR.
5. On DTD press “P” or select “Protocol” and press ENTR.
6. On DTD press “R” or select “RS232” and press ENTR.
7. On DTD press “S” or select “Stu” and press ENTR.
8. On DTD press “X” or select “Xmit” and press ENTR.
9. On DTD press “S” and ENTR or press “A” to select all keys to select keys to transmit.
NOTE: If “A” is selected, skip to step 12.
10. On DTD use P UP, P DN and ENTR to select keys to transmit.
11. On DTD press “Q” or select “Quit” and press ENTR to end key selection process.
12. On DTD observe “Connect to Station...” message.
13. On DTD press “SEND”.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
I-6
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
14. On DTD observe “STU-III” Connection Complete” message.
15. On DTD press “CLR”.
16. On DTD observe “Attempting to Connect” message and various other transfer messages.
17. When transfer is complete, disconnect DTD from STU-III/STU-IIIA/STU-IIB/STE.
b. (U//FOUO) Receiving Operator performs following steps:
1. On STU-III/STU-IIIA/STU-IIB/STE acknowledge readiness to receive RED JTIDS key(s)
using JFILL (JTIDS) - JFILL (JTIDS) routine.
2. Connect DTD to STU-III/STU-IIIA/STU-IIB/STE.
3. On DTD press “U” or select “Util” and press ENTR.
4. On DTD press “S” or select “Setup” and press ENTR.
5. On DTD press “P” or select “Protocol” and press ENTR.
6. On DTD press “R” or select “RS232” and press ENTR.
7. On DTD press “S” or select “Stu” and press ENTR.
8. On DTD press “R” or select “Recv” and press ENTR.
9. On DTD observe “Connect to Station...” message.
10. On DTD press “Rcv”.
11. On DTD observe “STU-III Connection Complete” message.
12. On DTD press “CLR”.
13. On DTD observe “Attempting to Connect” message.
14. On STU-III/STU-IIIA/STU-IIB/STE press SECURE DATA button.
15. On DTD observe various transfer messages.
16. On STU-III/STU-IIIA/STU-IIB/STE when transfer is complete press SECURE VOICE
button.
17. On STU-III/STU-IIIA/STU-IIB/STE acknowledge receipt of transferred keys.
18. Disconnect DTD from STU-III/STU-IIIA/STU-IIB/STE.
NOTE: (U//FOUO) Key transfer is complete when Retransmit menu is displayed on
transmitting DTD and “Connect to Station” is again displayed on receiving DTD.
NOTE: (U) Sending and receiving operators must record key transfers as required by
their respective Services.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
I-7
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
11. (U) TRANSFERRING JTIDS KEY AND TAG FROM ONE DTD TO ANOTHER VIA
STU-III/STU-IIIA/STU-IIIB/STE TELEPHONE CIRCUITS USING JFILL (FILL) - JFILL
(FILL) UAS
NOTE: (U) See the second NOTE following paragraph 10. on page I-6.
a. (U//FOUO) Sending Operator performs following steps:
1. Connect DTD to STU-III/STU-IIIA/STU-IIB/STE, using connector cable identified in
NOTE following paragraph 9.a., step 1.
2. Call intended receiver using STU-III/STU-IIIA/STU-IIB/STE secure voice mode and inform
operator that tagged JTIDS key is to be transferred via JFILL (Fill) - JFILL (Fill) routine.
3. On DTD press Abort.
4. On DTD press “F” or select “Fill” and press ENTR.
5. On DTD press “U” or select “Util” and press ENTR.
6. On DTD press “S” or select “Setup” and press ENTR.
7. On DTD press “P” or select “Protocol” and press ENTR.
8. On DTD press “S” or select “Stu” and press ENTR.
9. On DTD press Abort.
10. On DTD press “X” or select “Xmit” and press ENTR.
11. On DTD press “I” or select “Issue” and press ENTR.
12. On DTD press P UP, P DN and ENTR to select keys to transmit.
13. On DTD press “E” or select “SEND” and press ENTR.
14. On DTD press “D” or select “Direct” and press ENTR.
15. On DTD observe “Connection to Station...” message.
16. On DTD press “SEND”.
17. On DTD observe “STU-III Connection Complete” message.
18. On DTD press “CLR”
19. On DTD observe “Attempting to Connect” message and various other transfer messages.
19. When transfer is complete, disconnect DTD from STU-III/STU-IIIA/STU-IIB/STE.
b. (U//FOUO) Receiving Operator performs following steps:
1. On STU-III/STU-IIIA/STU-IIB/STE acknowledge readiness to receive RED JTIDS key(s)
using JFILL (Fill) - JFILL (Fill) routine.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
I-8
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
2. Connect DTD to STU-III/STU-IIIA/STU-IIB/STE.
3. On DTD press Abort.
4. On DTD press “F” or select “Fill” and press ENTR.
5. On DTD press “U” or select “Util” and press ENTR.
6. On DTD press “S” or select “Setup” and press ENTR.
7. On DTD press “P” or select “Protocol” and press ENTR.
8. On DTD press “S” or select “Stu” and press ENTR.
9. On DTD press Abort.
10. On DTD press “R” or select “Recv” and press ENTR.
11. On DTD observe “Connect to Station...” message.
12. On DTD press “RCV”.
13. On DTD observe “STU-III Connection Complete” message.
14. On DTD press “CLR”.
15. On DTD observe “Attempting to Connect” message.
16. On STU-III/STU-IIIA/STU-IIB/STE press’ SECURE DATA button.
17. On DTD observe various transfer messages
18. On STU-III/STU-IIIA/STU-IIB/STE when transfer is complete, press SECURE VOICE
button.
19. On STU-III/STU-IIIA/STU-IIB/STE acknowledge receipt of transferred JTIDS key(s).
20. Disconnect DTD from STU-III/STU-IIIA/STU-IIB/STE.
NOTE: (U//FOUO) Key transfer is complete when the Retransmit menu is displayed on
transmitting DTD and “Connect to Station” is again displayed on receiving DTD.
NOTE: (U) Sending and receiving operators must record key transfers as required by
their respective Services.
12. (U) TRANSFERRING JTIDS KEY AND TAG FROM ONE DTD TO ANOTHER VIA
STU-III/STU-IIIA/STU-IIB/STE TELEPHONE CIRCUITS TRANSMITTING FROM JFILL
AND RECEIVING ON CT3 UAS
NOTE: (U) See the second NOTE following paragraph 10. on page I-6.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
I-9
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
a. (U//FOUO) Sending Operator performs following steps (using JFILL):
1. Connect DTD to STU-III/STU-IIIA/STU-IIB/STE, using connector cable identified in
NOTE following paragraph 9.a., step 1.
2. Call intended receiver using STU-III/STU-IIIA/STU-IIB/STE secure voice mode and inform
operator that tagged JTIDS key is to be transferred using JFILL to CT3 routine.
3. On DTD press Abort.
4. On DTD press “F” or select “Fill” and press ENTR.
5. On DTD press “U” or select “Util” and press ENTR.
6. On DTD press “S” or select “Setup” and press ENTR.
7. On DTD press “P” or select “Protocol” and press ENTR.
8. On DTD press S” or select “Stu” and press ENTR.
9. On DTD press Abort.
10. On DTD press “X” or select “Xmit” and press ENTR.
11. On DTD press “I” or select “Issue” and press ENTR.
12. On DTD press P UP, P DN and ENTR to select keys to transmit.
13. On DTD press “E” or select “SEND” and press ENTR.
14. On DTD press “D” or select “Direct” and press ENTR.
15. On DTD observe “Connect to Station...” message.
16. On DTD press “SEND”.
17. On DTD observe “STU-III Connection Complete” message.
18. On DTD press “CLR”.
19. On DTD observe “Attempting to Connect” message and various other transfer messages.
20. When transfer is complete, disconnect DTD from STU-III/STU-IIIA/STU-IIB/STE.
b. (U//FOUO) Receiving Operator performs following steps (using CT3):
1. On STU-III/STU-IIIA/STU-IIB/STE acknowledge readiness to receive RED JTIDS key(s)
using JFILL to CT3 routine.
2. Connect DTD to STU-III/STU-IIIA/STU-IIB/STE.
3. On DTD start CT3 application, beginning at RSL Main Menu.
4. On DTD press “R” or select “Recv” and press ENTR.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
I-10
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
5. On DTD press “U” or select “Unassigned” and press ENTR.
6. On DTD use P DN and ENTR to select source UNKNOWN.
7. On DTD press “R” or SELECT “RS232 Protocol and press ENTR.
8. On DTD press “N” or select “No” and press ENTR AT DEFAULT PROMPT.
9. On DTD observe “Connect to...” message
10. On DTD press ENTR or Down Arrow key.
11. On DTD observe “Set Desired Position” message prompt.
12. On DTD press ENTR or Down Arrow key.
13. On STU-III/STU-IIIA/STU-IIB/STE press SECURE DATA button.
14. On DTD observe various transfer messages.
15. On STU-III/STU-IIIA/STU-IIB/STE when transfer is complete press SECURE VOICE button.
16. On STU-III/STU-IIIA/STU-IIB/STE acknowledge receipt of transferred JTIDS key(s).
17. Disconnect DTD from STU-III/STU-IIIA/STU-IIB/STE.
NOTE: (U//FOUO) Key transfer is complete when Retransmit menu is displayed on
transmitting DTD and “Connect to Station” is again displayed on receiving DTD.
NOTE: (U) Sending and receiving operators must record key transfers as required by
their respective Services.
13. (U) TRANSFERRING JTIDS KEY AND TAG FROM ONE DTD TO ANOTHER VIA
STU-III/STU-IIIA/STU-IIB/STE TELEPHONE CIRCUITS USING CT3 - CT3 UAS
NOTE: (U) See the second note following paragraph 10. on page I-6.
NOTE: (U//FOUO) If a key tag is transmitted that already exists on the CT3 DTD, an error
message offering the user a variety of choices will be displayed. In some circumstances, a
rollback and COMSEC error might occur requiring the that the DTD be powered off. This
will cause the loss of all data transferred.
NOTE: (U//FOUO) When beginning the actual data transfer, the receiving DTD displays the
“Attempting to Connect” message during the time that the transmitting DTD is preparing the
data for transfer. The amount of time is variable, depending on the amount of data to be
prepared. Although this wait may be longer than the receiving operator may expect, do not
disrupt the connection.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
I-11
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
a. (U//FOUO) Sending Operator performs following steps, using RSL Main Menu:
1. Connect DTD to STU-III/STU-IIIA/STU-IIB/STE, using connector cable identified in
NOTE following paragraph 9.a., step 1.
2. Call intended receiver using STU-III/STU-IIIA/STU-IIB/STE secure voice mode and inform
operator that tagged JTIDS key is to be transferred using CT3 to CT3 routine.
3. On DTD press “X” or select “Xmit” and press ENTR.
4. On DTD press “D” or select “Database” and press ENTR.
5. On DTD press “U” or select “STU3” and press ENTR.
6. On DTD press “M” or select “Manual” and press ENTR.
7. On DTD press “S” or select “Sel_dbases” and press ENTR.
8. On DTD press “K” or select “Key” and press ENTR.
9. On DTD press “A” or select “All” and press ENTR or press “S” or select “Sel_items” and
press ENTR.
NOTE: If “A” is pressed or “All” is selected, skip to step 12.
10 On DTD use P UP, P DN and ENTR to select keys to transmit.
11. On DTD press “D” or select “Done” and press ENTR.
12. On DTD observe “Preparing...” and “Connect to...” messages.
13. On DTD press ENTR or DN Arrow.
14. On DTD observe “Attempting to Connect” message and various other transfer messages.
15. When transfer is complete, disconnect DTD from STU-III/STU-IIIA/STU-IIB/STE.
b. (U//FOUO) Receiving Operator performs following steps:
1. On STU-III/STU-IIIA/STU-IIB/STE acknowledge readiness to receive tagged JTIDS key
using CT3 - CT3 routine.
2. Connect DTD to STU-III/STU-IIIA/STU-IIB/STE.
3. On DTD press “R” or select “Recv” and press ENTR.
4. On DTD press “D” or select “Database” and press ENTR.
5. On DTD press “U” or delect “STU3” and press ENTR.
6. On DTD observe “Connect to...” message.
7. On DTD press ENTR or the DN arrow.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
I-12
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
8. On STU-III/STU-IIIA/STU-IIB/STE press SECURE DATA button.
9. On DTD observe various transfer messages.
10. On STU-III/STU-IIIA/STU-IIB/STE when transfer is complete, press SECURE VOICE
button.
11. On STU-III/STU-IIIA/STU-IIB/STE acknowledge receipt of transferred keys.
12. Disconnect DTD from STU-III/STU-IIIA/STU-IIB/STE.
NOTE: (U//FOUO) Key transfer is complete when the Retransmit menu is displayed on
transmitting DTD and “Connect to Station” is once again displayed on receiving DTD.
NOTE: (U) Sending and receiving operators must record key transfers as required by
their respective Services.
14. (U) TRANSFERRING ALL JTIDS DATA BASES FROM ONE DTD TO ANOTHER VIA
STU-III/STU-IIIA/STU-IIB/STE TELEPHONE CIRCUIT USING CT3 TO CT3 UAS
NOTE: (U) See the second NOTE following paragraph 10. on page I-6.
NOTE: (U//FOUO) If a key tag is transmitted that already exists on the CT3 DTD, an error
message offering the user a variety of choices will be displayed. In some circumstances, a
rollback and COMSEC error might occur requiring that the DTD be powered off. This will
cause the loss of all data transferred.
NOTE: (U//FOUO) When beginning the actual data transfer, the receiving DTD displays the
“Attempting to Connect” message during the time that the transmitting DTD is preparing the
data for transfer. The amount of time is variable, depending on the amount of data to be
prepared. Although this time may be longer than the receiving operator may expect, do not
disrupt the connection.
a. (U//FOUO) Sending Operator performs following steps, beginning at the RSL Main
Menu:
1. Connect DTD to STU-III/STU-IIIA/STU-IIB/STE, using connector cable identified in
NOTE following paragraph 9.a., step 1.
2. Call intended receiver using STU-III/STU-IIIA/STU-IIB/STE secure voice mode and inform
operator that all JTIDS data is to be transferred using CT3 to CT3 routine.
3. On DTD press “X” or select “Xmit” and press ENTR.
4. On DTD press “D” or select “Database” and press ENTR.
5. On DTD press “U” or select “STU3” and press ENTR.
6. On DTD press “M” or select “Manual” and press ENTR.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
I-13
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
7. On DTD press “A” or select “All_dbases” and press ENTR or press “S” and select
“Sel_dbases” and press ENTR.
NOTE: If “A” or “All dbases” is selected, skip to step 12.
8. On DTD select desired database for transmission.
9. On DTD press “A” or select “All” and press ENTR or press “S” and select “Sel_items” and press
ENTR.
NOTE: If “A” if “All” is selected, skip to step 12.
10. On DTD use P UP, P DN and ENTR to select items to transmit.
11. On DTD use “D” or select “Done” and press ENTR.
12. On DTD observe “Preparing...” or “Standby...” and “Connect to...” messages.
13. On DTD press ENTR or Down arrow.
14. On DTD observe “Attempting to connect” message and various other transfer messages.
14. When transfer is complete, disconnect DTD from STU-III/STU-IIIA/STU-IIB/STE.
b. (U//FOUO) Receiving Operator performs following steps:
1. Respond to sending operator’s call and acknowledge readiness to receive JTIDS data bases
using CT3 to CT3 routine.
2. Connect DTD to ATU-III/STU-IIIA/STU-IIB/STE.
3. On DTD press “R” of select “Recv” and press ENTR.
4. On DTD press “D” or select “Database” and press ENTR.
5. On DTD press “S” or select STU3 and press ENTR.
6. On DTD observe “Connect to...” message.
7. On DTD press ENTR of Down arrow.
8. On STU-III/STU-IIIA/STU-IIB/STE press SECURE DATA button.
9. On DTD observe various transfer messages.
10. On STU-III/STU-IIIA/STU-IIB/STE when transfer is complete, press SECURE VOICE
button.
11. On STU-III/STU-IIIA/STU-IIB/STE acknowledge receipt of transferred JTIDS data bases.
12. Disconnect DTD from STU-III/STU-IIIA/SUU-IIB/STE.
NOTE: (U//FOUO) Key transfer is complete when the Retransmit menu is displayed on
transmitting DTD and “Connect to Station” is once again displayed on receiving DTD.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
I-14
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
NOTE: (U) Sending and receiving operators must record key transfers as required by their
respective Services.
15. (U) TRANSFERRING JTIDS KEY AND TAG FROM ONE DTD TO ANOTHER VIA
STU-III/STU-IIIA/STU-IIB/STE TELEPHONE CIRCUIT USING FILL UAS
NOTE: (U) See the second NOTE following paragraph 10. on page I-6.
a. (U//FOUO) Sending Operator performs following steps, using the FILL UAS routine:
1. Connect DTD to STU-III/STU-IIIA/STU-IIB/STE, using connector cable identified in
NATO following paragraph 9.1., step 1.
2. Call intended receiver using STU-III/STU-IIIA/STU-IIB/STE secure voice mode and inform
operator that tagged JTIDS key is to be transferred using FILL UAS routine.
3. On DTD press “U” or select “Util” and press ENTR.
4. On DTD press “S” or select “Setup” and press ENTR.
5. On DTD press “P” or select “Protocol” and press ENTR.
6. On DTD press “S” or select “Stu” and press ENTR.
7. On DTD press Abort.
8. On DTD press “X” or select “Xmit” and press ENTR.
9. On DTD press “I” or select “Issue” and press ENTR.
10. On DTD using P UP, P DN and ENTR to select keys to transmit.
11. On DTD select “SEND” and press ENTR.
12. On DTD press “D” or select “Direct” and press ENTR.
13. On DTD observe “Connect to Station...” message.
14. On DTD press “SEND”.
15. On DTD observe “STI-III Connection Complete” message.
16. On DTD press CLR.
17. On DTD observe “Attempting to Connect” message and various other transfer messages.
18. When transfer is complete, disconnect DTD from STU-III/STU-IIIA/STU-IIB/STE.
b. (U//FOUO) Receiving Operator performs following steps:
1. On STU-III/STU-IIIA/STU-IIB/STE acknowledge readiness to receive tagged JTIDS key
using FILL UAS routine.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
I-15
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
2. Connect DTD to STU-III/STU-IIIA/STU-IIB/STE.
3. On DTD press “RCV”.
4. On DTD observe “STU-III Connection Complete” message.
5. On DTD press “CLR”.
6. On DTD observe “Attempting to Connect” message.
7. On STU-III/STU-IIIA/STU-IIB/STE press” SECURE DATA key.
8. On DTD observe various transfer messages.
9. On STU-III/STU-IIIA/STU-IIB/STE when transfer is complete, press SECURE VOICE
button.
10. On STU-III/STU-IIIA/STU-IIB/STE acknowledge receipt of transferred keys.
11. Disconnect DTD from STU-III/STU-IIIA/STU-IIB/STE.
NOTE: (U//FOUO) Key transfer is complete when Retransmit menu is displayed on
transmitting DTD and “Connect to Station” is again displayed on receiving DTD.
NOTE: (U) Sending and receiving operators must record key transfers as required by
their respective Services.
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
I-16
UNCLASSIFIED
NAG-16F
THIS PAGE IS INTENTIONALLY BLANK
UNCLASSIFIED
ORIGINAL
UNCLASSIFIED//FOR OFFICIAL USE ONLY
NAG-16F
(U) FIELD GENERATION AND
OVER-THE-AIR DISTRIBUTION
OF COMSEC KEY IN SUPPORT OF
TACTICAL
OPERATIONS AND EXERCISES
UNCLASSIFIED//FOR OFFICIAL USE ONLY
ORIGINAL
FOR OFFICIAL USE ONLY
OHA Regional Hospital Evacuation and Mass Fatality 2009 TTX Situation Manual
PREFACE
The Ohio Hospital Association (OHA) Regional Hospital Evacuation and Mass Fatality 2009 TTX is
sponsored by The Ohio Hospital Association and the Ohio Department of Health with funding
support from the Health Services and Resources Administration, U.S. Department of Health and
Human Services, Catalog of Federal Domestic Assistance (CFDA) Number 93.889. This Situation
Manual (SitMan) was produced with input, advice, and perspective from a statewide hospital
workgroup assisting with hospital evacuation and fatality management planning and exercise
development, which followed the guidance set forth in the Federal Emergency Management
Agency (FEMA), Homeland Security Exercise and Evaluation Program (HSEEP).
The OHA Regional Hospital Evacuation and Mass Fatality 2009 TTX SitMan provides exercise
participants with all the necessary tools for their roles in the exercise. This document was
developed with the advice and assistance of the members of the OHA Regional Hospital
Evacuation and Mass Fatality 2009 TTX planning team. It is tangible evidence of the Ohio
Hospital Association’s commitment to ensure hospitals are prepared to manage emergencies
and disasters.
The OHA Regional Hospital Evacuation and Mass Fatality 2009 TTX is an unclassified exercise.
The control of information is based more on public sensitivity regarding the nature of the
exercise than on the actual exercise content. Some exercise material is intended for the
exclusive use of exercise planners, facilitators, and evaluators, but players may view other
materials deemed necessary to their performance. The SitMan may be viewed by all exercise
participants.
All exercise participants should use appropriate guidelines to ensure the proper control of
information within their areas of expertise and to protect this material in accordance with
current jurisdictional directives. Public release of exercise materials to third parties is at the
discretion of the Ohio Hospital Association.
Preface
i
The Ohio Hospital Association
FOR OFFICIAL USE ONLY
FOR OFFICIAL USE ONLY
OHA Regional Hospital Evacuation and Mass Fatality 2009 TTX Situation Manual
This page is intentionally left blank.
Preface
ii
The Ohio Hospital Association
FOR OFFICIAL USE ONLY
FOR OFFICIAL USE ONLY
OHA Regional Hospital Evacuation and Mass Fatality 2009 TTX Situation Manual
HANDLING INSTRUCTIONS
1.
The title of this document is the OHA Regional Hospital Evacuation and Mass Fatality 2009
TTX Situation Manual (SitMan).
2.
The information gathered in this SitMan is For Official Use Only (FOUO) and should be
handled as sensitive information not to be disclosed. This document should be safeguarded,
handled, transmitted, and stored in accordance with appropriate security directives.
Reproduction of this document, in whole or in part, without prior approval from the Ohio
Hospital Association is prohibited.
3.
At a minimum, the attached materials will be disseminated only on a need-to-know basis
and when unattended, will be stored in a locked container or area offering sufficient
protection against theft, compromise, inadvertent access, and unauthorized disclosure.
4.
For more information, please consult the following point of contact (POC):
Exercise Point of Contact:
Barb Lyon
ARMADA, Ltd
Cell (740) 513-8574
blyon@armadausa.com
Ohio Hospital Association Contact:
Carol Jacobson
Director of Emergency Management
614-221-7614
carolj@ohanet.org
Handling Instructions
iii
The Ohio Hospital Association
FOR OFFICIAL USE ONLY
FOR OFFICIAL USE ONLY
OHA Regional Hospital Evacuation and Mass Fatality 2009 TTX Situation Manual
This page is intentionally left blank.
Handling Instructions
iv
The Ohio Hospital Association
FOR OFFICIAL USE ONLY
FOR OFFICIAL USE ONLY
OHA Regional Hospital Evacuation and Mass Fatality 2009 TTX Situation Manual
CONTENTS
Preface
i
Handling Instructions
iii
Introduction
1
Background
1
Purpose
1
Scope
1
Target Capabilities
1
Exercise Objectives
2
Participants
2
Exercise Structure
3
Exercise Guidelines
3
Assumptions and Artificialities
3
Exercise Schedule
4
Modules
5
Contents
v
The Ohio Hospital Association
FOR OFFICIAL USE ONLY
FOR OFFICIAL USE ONLY
OHA Regional Hospital Evacuation and Mass Fatality 2009 TTX Situation Manual
This page is intentionally left blank.
Contents
vi
The Ohio Hospital Association
FOR OFFICIAL USE ONLY
FOR OFFICIAL USE ONLY
OHA Regional Hospital Evacuation and Mass Fatality 2009 TTX Situation Manual
INTRODUCTION
Background
The Ohio Hospital Association (OHA) was awarded SY09 FY08 ASPR dollars through the Ohio
Department of Health to develop hospital evacuation and fatality management planning
templates for Ohio hospitals to utilize within their facilities. In addition, OHA was asked to
design, conduct, and evaluate regional hospital evacuation and fatality management tabletop
exercises that would test the newly created planning documents. These regional tabletop
exercises are being conducted to reveal strengths and gaps in local, regional and statewide
plans.
Purpose
The purpose of this exercise is to provide participants an opportunity to evaluate current
response concepts, plans and capabilities in response to a possible medical evacuation and
mass fatalities due to severe weather. The exercise will focus on local and regional
coordination, critical decisions and integration of existing Memorandums of Understanding
(MOU).
Scope
In this
6 hour tabletop exercise alert and notification, decision-making processes,
Memorandums of Understanding and interagency coordination will be discussed and evaluated
in response to severe weather that affects a local hospital. Exercise players will include hospital
personnel, first responders and EMS, American Red Cross staff, emergency management, public
health officials and other organizations identified within each region. All participating hospitals
will assume the role of the affected hospital.
Target Capabilities
The National Planning Scenarios and the establishment of the National Preparedness Priorities
have steered the focus of homeland security toward a capabilities-based planning approach.
Capabilities-based planning focuses on planning under uncertainty, since the next danger or
disaster can never be forecast with complete accuracy. Therefore, capabilities-based planning
takes an all-hazards approach to planning and preparation which builds capabilities that can be
applied to a wide variety of incidents. States and Urban Areas use capabilities-based planning to
identify a baseline assessment of their homeland security efforts by comparing their current
capabilities against the Target Capabilities List (TCL) and the critical tasks of the Universal Task
List (UTL). This approach identifies gaps in current capabilities and focuses efforts on identifying
and developing priority capabilities and tasks for the jurisdiction.
Introduction
1
The Ohio Hospital Association
FOR OFFICIAL USE ONLY
FOR OFFICIAL USE ONLY
OHA Regional Hospital Evacuation and Mass Fatality 2009 TTX Situation Manual
The capabilities listed below have been selected by the OHA Regional Hospital Evacuation and
Mass Fatality
2009 TTX planning team. These capabilities provide the foundation for
development of the exercise objectives and scenario, as the purpose of this exercise is to
measure and validate performance of these capabilities and their associated critical tasks.
• Communications
• Fatality Management
• Medical Surge
• On-site Incident Management
• Planning
Exercise Objectives
Exercise design objectives are focused on improving understanding of a response concept,
identifying opportunities or problems, and/or achieving a change in attitude. The exercise will
focus on the following design objectives selected by the exercise planning team:
Objectives:
• Assess the adequacy of local and regional plans that detail a response to a potential
medical evacuation. Identify shortfalls in resources, limits in capabilities and conflicts in
these medical evacuation plans.
• Discuss the decision-making process regarding medical evacuation versus shelter-in-
place options.
• Assess the adequacy of local and regional plans that detail a response to a mass fatality
incident. Identify shortfalls in resources, limits in capabilities and conflicts in these mass
fatality plans.
• Discuss the decision-making process regarding the management of multiple fatalities.
• Review inter-agency mutual aid support and Memorandums of Understanding as they
apply to the scenario.
• Clarify, evaluate or resolve any questions related to interagency coordination and
integration.
Introduction
2
The Ohio Hospital Association
FOR OFFICIAL USE ONLY
FOR OFFICIAL USE ONLY
OHA Regional Hospital Evacuation and Mass Fatality 2009 TTX Situation Manual
Participants
• Players respond to the situation presented based on expert knowledge of response
procedures, current plans and procedures, and insights derived from training.
• Observers support the group in developing responses to the situation during the
discussion; however, they are not participants in the moderated discussion period.
• Facilitators provide situation updates and moderate discussions. They also provide
additional information or resolve questions as required. Key planning committee
members may also assist with facilitation as subject matter experts (SMEs) during the
tabletop exercise.
Exercise Structure
This will be a basic, moderated tabletop exercise. Information will be provided to all players at
the same time. Players will participate in the following 5 distinct modules:
• Module 1: Initial Response
• Module 2: On-going Response
• Module 3: MOUs/Partnerships
• Module 4: Interagency Coordination
• Module 5: Hot Wash
Each module will begin with a situation briefing or update and will offer a list of questions
for discussion. Participants should feel free to openly ask questions of other players,
express thoughts and/or opinions. The facilitator and evaluators will capture the responses.
Exercise Guidelines
• This is an open, low-stress, no-fault environment. Varying viewpoints, even
disagreements, are expected.
• Respond based on your knowledge of current plans and capabilities (i.e., you may use
only existing assets) and insights derived from training.
• Decisions are not precedent setting and may not reflect your organization’s final
position on a given issue. This is an opportunity to discuss and present multiple options
and possible solutions.
• Issue identification is not as valuable as suggestions and recommended actions that
could improve response and preparedness efforts. Problem-solving efforts should be
the focus.
• Assume cooperation and support from other responders and agencies.
Introduction
3
The Ohio Hospital Association
FOR OFFICIAL USE ONLY
FOR OFFICIAL USE ONLY
OHA Regional Hospital Evacuation and Mass Fatality 2009 TTX Situation Manual
• The situation updates, written material and resources are the basis for discussion. There
are no situational injects.
Assumptions and Artificialities
In any exercise a number of assumptions and artificialities may be necessary to complete play in
the time allotted. During this exercise, the following apply:
• The scenario is plausible, and events occur as they are presented.
• There is no “hidden agenda”, nor any trick questions.
• All players receive information at the same time.
Introduction
4
The Ohio Hospital Association
FOR OFFICIAL USE ONLY
|
||
|
|
|