FA2550-14-R-8010_Sec_L_Attch_L-2_(Scenarios).pdf

Attachment L-2, Scenarios

3.1.3.3 FACTOR 3 – Communication Planning

3.1.3.3.1 Subfactor 1 - System Usage

– Analyze the Canadian Network Configuration and provide system support (Scenario 1): Reference the following scenario and respond to items a, b and c.

Scenario 1. Canadian users operating on the Extreme Data Rate (XDR) payload in a real world environment are being preempted from their networks.

a. List the probable cause(s) and discuss how these issues affect network operation.

b. Discuss way(s) to determine the probable cause(s) and include what data is checked.

c. Discuss action(s) required to normalize operations.

3.1.3.3.2 Subfactor 2 - System Usage

– Develop AEHF Payload Table/Frequency Plan Recommendations (Scenario 2): Reference the following scenario and respond to item a.

Scenario 2. The Canadians have asked the IPASC to analyze their mission requirements on AEHF 1, 2, and 3. The AEHF satellite frequency plans should support Canadian operations while staying within the constraints of the

MOU.

a. What information does the IPASC need to collect from the Canadians?

3.1.3.3.3 Subfactor 3 - System Usage

– Analyze resource monitoring data and provide recommendations (Scenario 3): Reference the following scenario and respond to item a and b.

Scenario 3. While conducting resource monitoring at the IPASC you notice the payload is near capacity on the UK apportioned beams. You know that the UK is planning additional missions and there is a possibility of insufficient satellite resources.

a. What can be modified to ensure maximum use of the system and discuss how modifications affect system operations.

b. Provide recommendation to UK to resolve resource limitation.

3.1.3.3.4 Subfactor 4 - Coalition Communication Planning

– Analyze Network Configuration to determine supportability (Scenario 4): Reference the following scenario and respond to items a and b.

Scenario 4. Using the Satellite Access Authorization (SAA) attached.

a. Step through the process of reviewing and analyzing the SAA.

b. Identify and correct any errors in the SAA.

3.1.3.3.5 Subfactor 5 - Coalition Communication Planning

– Analyze Coalition Communications Plans and provide recommendation (Scenario 5): Reference the following scenario and respond to items a and b.

Scenario 5. The US, Netherlands and UK have agreed to take a coordinated response to increased Pirate activity on the West coast of Africa to protect the three nations’ interest in the region. “Operation Hijack Capt Hook” will employ Naval forces and shore stations. The US 6th Fleet will take the command and control lead for operations.

Assume that the satellites are in their current locations with the constellation in a ring. Note: The UK is utilizing half of the apportioned resources for other operations. The Netherlands have no other missions allocated at this time.

a. Provide a Venn diagram using the resources assigned to each country.

b. Provide a SAR that supports the Venn diagram with requested networks (see SAR template attached).

3.1.3.4 FACTOR 4 - Communications Security (COMSEC) Manager/Custodian

3.1.3.4.1 Subfactor 1 – Provide Crypto/COMSEC support (Scenario 6): Reference the following scenario and respond to items a and b.

Scenario 6. The Netherlands are installing three new Navy Multi-beam Terminals (NMTs) in five months. The trained person that previously managed installs has moved to another program. The new person called the IPASC and is asking questions pertaining to Crypto/COMSEC.

a. Guide the new planner through the process of preparing the terminals for first contact with the satellite from a Crypto/COMSEC perspective.

b. Describe the necessary steps to ensure the Netherlands terminal receive the keys prior to terminal activation.

3.1.3.4.2 Subfactor 2 - Provide Crypto equipment support

– Provide Crypto equipment support (Scenario 7): Reference the following scenario and respond to item a.

Scenario 7. A NMT terminal operator notifies you that their Simple Key Loader (SKL) was dropped and broken.

They have received a new SKL from supply and it is blank.

a. Guide the operator through the process of how to create a KGV 136 Equipment type in the SKL, assign a benign fill to KVG 136 in the SKL, and load the NMT-IPV Load Endorsement Keys.

3.1.3.5 FACTOR 5 – Operations

3.1.3.5.1 Subfactor 1 – Provide user troubleshooting support (Scenario 8): Reference the following scenario and respond to items a.

Scenario 8. A Canadian ASMART-T is unable to log on to Flight 7, assume no equipment failures, good weather and look angle.

a. Describe the other critical elements required to establish log on.

3.1.3.5.2 Subfactor 2 – Analyze the Global Scenario to ensure all IP resources requirements are reflected correctly (Scenario 9): Reference the following scenario and respond to item a.

Scenario 9. A new Global Scenario has been developed by the SSE in preparation for major satellite reposition of the Milstar/AEHF-2 constellation.

a. What data points in the Global Scenario must be verified for the IPs to successfully operate?

3.1.3.5.3 Subfactor 3– Provide Global Scenario to support IP communications planning (Scenario 10): Reference the following scenario and respond to items a, b, and c.

Scenario 10. A new Global Scenario has been developed by the SSE. This new Global Scenario is planned for US operations in 30 days and must be delivered to the IPs.

a. What data base items must be filtered from the Global scenario?

b. How is database data points removed from the Global scenario?

c. Once the Global scenario has been prepared for release, what are the transfer procedures?

IPASC SAA

FM: RSSC-EAST

TO: IPASC

INFO: JOINT STAFF WASHINGTON DC//J6Z//

USSTRATCOM OFFUTT AFB NE//CL18//

COMNAVNETSPAOPSCOM//N33//

OR MILSTAR SATELLITE OPERATIONS CENTER SCHRIEVER AFB CO//MSOC// 2498

RSSC WEST PETERSON AFB CO//

RSSC EAST MACDILL AFB FL//

RSSC EUROPE VAIHINGEN GE//

RSSC PACIFIC WHEELER AAF HI//

BT

CLASSIFICATION: UNCLASSIFIED

SUBJECT: MSN XEXXX-XX, EHF SATELLITE ACCESS AUTHORIZATION

REFERENCES: [REFERENCE A, B, AND C, ETC. (AS NECESSARY)/MESSAGE CLASSIFICATION/

MESSAGE DATE TIME GROUP [DTG]/FROM ADDRESSEE/SUBJECT](U)

REF A: SAR IN SUPPORT OF [MISSION NAME] [DESCRIBE THE PURPOSE OF THE EHF MISSION AND

IDENTIFY SUPPORTING UNIFIED COMBATANT COMMAND](U)

1. (U) GENERAL INFORMATION:

A. (U) ACCESS IS AUTHORIZED ON MILSTAR M6 AEHF A2 FROM 310001Z JUL 15 THROUGH 012359Z

AUG 15

B. (U) RSSC PLANNER POC:

(U) SIPRNET: [XXX@XXX.smil.mil]

(U) NIPRNET: [XXX@XXX.mil]

(U) DSN: [XXX-XXX-XXXX] COM: [XXX-XXX-XXXX]

C. (U) SUPPORTED UNIT POC:

(U) SIPRNET: [XXX@XXX.smil.mil]

(U) NIPRNET: [XXX@XXX.mil]

(U) DSN: [XXX-XXX-XXXX] COM: [XXX-XXX-XXXX]

(U) UNIT 24 HOUR POC PHONE NUMBER:

(U) DSN: [XXX-XXX-XXXX] COM: [XXX-XXX-XXXX]

D. (U) DEPLOYED/UNDERWAY :

(U) DSN: [XXX-XXX-XXXX] COM: [XXX-XXX-XXXX]

E. (U) OTHER:

(U) DSN: [XXX-XXX-XXXX] COM: [XXX-XXX-XXXX]

F. (U) ALL UNITS WILL NOTIFY THEIR APPROPRIATE CHAIN OF COMMAND AND

SERVICING RSSC IF THEY DEACCESS/END RESOURCE USAGE PRIOR TO THE MISSION

COMPLETION DTG NOTED IN THIS SAA.

2. (U) LDR SERVICES AUTHORIZED: N/A

3. (U) MDR SERVICES AUTHORIZED:

A. (U) NET 1: NAVY DSX

1) (U) SDB NUMBER: NAVY 00492

2) (U) CJCSI 6250.01 MISSION PRIORITY: 4C

3) (U) PRECEDENCE: P2

4) (U) SERVICE ID(S): 432/433

5) (U) DATES/TIMES: 310001Z JUL 08 THROUGH 012359Z AUG 15

6) (U) SERVICE TYPE: DUAL SIMPLEX

7) (U) NETWORK TYPE: DATA

8) (U) DATA RATE: 1024Kbps

9) (U) AUTHORIZED SERVICE INFORMATION:

| TERM | TERM | SAT | BEAM | UL COMM | UL | DL COMM | FENCE | TX & RX |

| ID | TYPES | | OF SVC | MODE | TS | MODE | ID | |

| 2730 |NMT SHIP | A2 | DUCA-B2 | 16+320 | 185 | 424+5120 | 4 | TX & RX |

| 2791 |NMT SHORE| M5| DUCA-B1 | 16+320 | 184 | 424+5120 | 4 | TX & RX |

10) (U) CROSSLINKS: YES

11) (U) COMMUNICATIONS CONTROLLER (CC): 2791

12) (U) ALTERNATE CC: 2730

13) (U) NETWORK DOWNLINK HOPS: 8

B. (U) ANTENNA CONTROLLER(S) AND ALTERNATE(S): 2791

C. (U) BEAM MOVEMENT AUTHORIZED: NO

D. (U) BEAM LOCATION(S):

|A2|DUCA-B2|30.40N|-19.60W|

|M5|DUCA-B1|39.11N| 17.01E|

E. (U) MDR REMARKS: N/A

4. (U) XDR SERVICES AUTHORIZED:

A. (U) NET 1: VOICE NET

1) (U) SDB NUMBER: NAVY 00493

2) (U) CJCSI 6250.01 MISSION PRIORITY: 4C

3) (U) PRECEDENCE: P2

4) (U) SERVICE ID(S): 8139

5) (U) DATES/TIMES: 310001Z JUL 15 THROUGH 012359Z AUG 15

6) (U) SERVICE TYPE: NETWORK

7) (U) COALITION: NO

8) (U) GROUP SESSION KEY: 20

9) (U) NETWORK TYPE: VOICE

10) (U) DATA RATE: 2.4 KBPS

11) (U) TERM LOGON:

|TERM |PROBE | UL | DL | ANT |

| ID |TYPE |XC2 | XC3| AUGMENT|

|2730 | 1 | 1+8 |2+64| NO |

|2791 | 1 | 1+8 |2+64| NO |

|30198 | 1 | 1+8 |2+64| NO |

|34200 | 1 | 1+8 |2+64| NO |

12) (U) AUTHORIZED MEMBER/SERVICE INFORMATION:

| TERM | TERM | SAT | BEAM | UPLINK | U/L |1ST | DOWNLINK | D/L | TX & RX |

XC2 |

| ID | TYPES | | OF SVC | MODE |FENCE|HOP| MODE |FENCE|

|RROW|

| 2730 |NMT SHIP | A2 | MRCA-2 | SDPSK 4+128| 0 | 0 | FSDPSK 8+160 | 0 | TX & RX |

NO |

| 2791 |NMT SHORE | A2 | MRCA-2 | SDPSK 4+128| 0 | 2 | FSDPSK 8+160 | 0 | TX & RX |

NO |

| 30198 |NMT SHIP | A2 |BSMRCA-3A| SDPSK 4+128| 0 | 0 | FSDPSK 8+160 | 0 | TX & RX |

NO |

| 34200 |NMT SHIP | A2 |BSMRCA-5A| SDPSK 4+128| 0 | 2 | FSDPSK 8+160 | 0 | TX & RX |

NO |

13) (U) RROW: N/A

14) (U) CROSSLINKS: NO

15) (U) FENCE CONTROLLER (FC): 3002

16) (U) COMMUNICATIONS CONTROLLER (CC): 2791

17) (U) ALTERNATE CC: 30198

18) (U) (SUB or SUB-SUB FENCE SET-UP AUTHORIZED: NO

FENCE PRIVILEGED TERM ID: NA

FENCE CONTROLLER TERM ID: NA

19) (U) NETWORK UPLINK HOPS: 1

20) (U) NETWORK DOWNLINK HOPS: 1

B. (U) NET 2: ADNS PTP #1

1) (U) SDB NUMBER: NAVY 00493

2) (U) CJCSI 6250.01 MISSION PRIORITY: 4C

3) (U) PRECEDENCE: P2

4) (U) SERVICE ID(S): 8140

5) (U) DATES/TIMES: 310001Z JUL 15 THROUGH 012359Z AUG 15

6) (U) SERVICE TYPE: PTP

7) (U) COALITION: YES

8) (U) GROUP SESSION KEY: NA

9) (U) NETWORK TYPE: DATA

10) (U) DATA RATE: 2048 KBPS

| ID |TYPE | XC2 | XC3 | AUGMENT|

|2730 | 0 | 8+160 |4+392| NO |

|34200 | 0 | 8+160 |4+392| NO |

| TERM | TERM | SAT | BEAM | UPLINK | U/L |1ST | DOWNLINK | D/L | TX & RX |

| ID | TYPES | | OF SVC | MODE |FENCE|HOP| MODE |FENCE|

|RROW|

| 2730 |NMT SHIP | A2 | LGEC | FSDPSK 8+160| 2P | 0 | SDPSK 4+128 | 2P | TX & RX |

NO |

| 34200 |NMT SHIP | A2 |BSMRCA-3A| FSDPSK 8+160| 2P | 0 | SDPSK 4+128 | 7P | TX & RX |

15) (U) FENCE CONTROLLER (FC): 3002

16) (U) COMMUNICATIONS CONTROLLER (CC): 2791

17) (U) ALTERNATE CC: 30198

18) (U) NETWORK DOWNLINK HOPS: 1

19) (U) (SUB or SUB-SUB FENCE SET-UP AUTHORIZED: NO

20) (U) NETWORK UPLINK HOPS: 98

21) (U) NETWORK DOWNLINK HOPS: 12

C. (U) NET 3: ADNS PTP #2

2) (U) CJCSI 6250.01 MISSION PRIORITY: 6B

3) (U) PRECEDENCE: P2

4) (U) SERVICE ID(S): PTP

5) (U) DATES/TIMES: 310001Z JUL 15 THROUGH 012359Z AUG 15

6) (U) SERVICE TYPE: PTP

7) (U) COALITION: YES

8) (U) GROUP SESSION KEY: NA

9) (U) NETWORK TYPE: DATA

10) (U) DATA RATE: 1544 KBPS

|2730 | 0 | 8+160 |4+392| NO |

|30198 | 0 | 8+160 |4+392| NO |

| TERM | TERM | SAT | BEAM | UPLINK | U/L |1ST | DOWNLINK | D/L | TX & RX |

| ID | TYPES | | OF SVC | MODE |FENCE|HOP| MODE |FENCE|

|RROW|

| 2730 |NMT SHIP | A2 | DUCA B-2 | FSDPSK 8+160| 2P | 0 | SDPSK 4+128 | 2P | TX & RX |

| 30198 |NMT SHIP | A2 |BSMRCA-3A| FSDPSK 8+160| 6P | 0 | SDPSK 4+128 | 6P | TX & RX |

YES |

15) (U) FENCE CONTROLLER (FC): 3002

16) (U) COMMUNICATIONS CONTROLLER (CC): 2730

17) (U) ALTERNATE CC: 30198

D. (U) NET 4: ADNS PTP #3

2) (U) CJCSI 6250.01 MISSION PRIORITY: 4C

3) (U) PRECEDENCE: P2

4) (U) SERVICE ID(S): N/A

5) (U) DATES/TIMES: 310001Z JUL 15 THROUGH 012359Z AUG 15

6) (U) SERVICE TYPE: PTP

7) (U) COALITION: YES

8) (U) GROUP SESSION KEY: 20

9) (U) NETWORK TYPE: DATA

10) (U) DATA RATE: 1544 KBPS

|30198 | 0 | 8+160 |4+392| NO |

|34200 | 0 | 8+160 |4+392| NO |

22) (U) AUTHORIZED MEMBER/SERVICE INFORMATION:

| TERM | TERM | SAT | BEAM | UPLINK | U/L |1ST | DOWNLINK | D/L | TX & RX |

| ID | TYPES | | OF SVC | MODE |FENCE|HOP| MODE |FENCE|

|RROW|

| 30198 |NMT SHIP | A2 |BSMRCA-4A| FSDPSK 8+160| 6P | 0 | SDPSK 4+128 | 6P | TX & RX |

NO |

| 34200 |NMT SHIP | A2 |BSMRCA-3A| FSDPSK 8+160| 7P | 0 | SDPSK 4+128 | 7P | TX & RX |

15) (U) FENCE CONTROLLER (FC): 34200 FID 7, 30198 FID 6

16) (U) COMMUNICATIONS CONTROLLER (CC): 34200

17) (U) ALTERNATE CC: 30198

E. (U) ANTENNA CONTROLLER(S) AND ALTERNATE(S): 30198 (BSMRCA-5A), 34200 (BSMRCA-

3A)

(U) BEAM MOVEMENT AUTHORIZED: YES

F. (U) BEAM LOCATION(S):

(U) SAT/BEAM NAME/LAT/LONG

|A2| MRCA-2 |30.40N|-19.60W|

|A2| BSMRCA-4A |30.40N|-21.50W|

|A2| BSMRCA-3A |35.23N|-22.60W|

G. (U) XDR REMARKS: N/A

5. (U) REMARKS:

A. (U) ALL UNITS WILL COMPLETE AN EHF AFTER ACTION REPORT (AAR) WITHIN 10 DUTY DAYS

AFTER EACH TACTICAL EHF MISSION FOLLOWING THE GUIDELINES OUTLINED IN THE

CURRENT AEHF SYSTEM GUIDENCE.

B. (U) TO AID IN TIMELY NOTIFICATION OF PROBLEMS AND TO RESTORE SERVICES DUE TO EHF

ANOMALIES, THE NECOS/CC SHALL INFORM THE APPROPRIATE RSSC OF ANY SERVICE

OUTAGES. THE RSSC WILL THEN CONTACT THE PROPER SATCOM OPERATIONS CENTER TO

DETERMINE IF A SATELLITE OR CONSTELLATION PROBLEM EXISTS. THE NECOS/CC WILL

INITIALLY NOTIFY THE RSSC VIA PHONE WHEN ANOMALIES OCCUR, BUT WILL FOLLOW-UP

WITH A FORMAL MESSAGE. NAVY UNITS WILL SEND A COMSPOT TO PSOC, NNSOC,

APPROPRIATE CHAIN OF COMMAND, AND INFORM JOINT STAFF/J6Z AS WELL AS THE UNIFIED

COMBATANT COMMAND AND APPROPRIATE RSSC.

C. (U) COMM MODE (BURST RATE): TERMINALS WILL ALWAYS USE THE COMM MODE AT THE

LEAST ROBUST MODULATION MODE NECESSARY TO ESTABLISH COMMUNICATIONS NOT TO

EXCEED THE MODULATION MODE LISTED IN THE NETWORK DEFINITION. THE NECOS/CC

MAY DIRECT CHANGES TO THE COMM MODE BEING USED AS LONG AS THE COMBINED HOPS

BEING USED BY ALL TERMINALS DOES NOT EXCEED THE VALUE AUTHORIZED IN THIS SAA.

D. (U) SPOT BEAM CONTROL: SPOT BEAM MOVEMENTS (SPOT A, B, C, DUCA, NSB-A, NSB-B) WILL

BE ACCOMPLISHED BY THE SPOT BEAM CONTROLLER or ANTENNA CONTROLLER AS

DESIGNATED BY THE UNIFIED COMBATANT COMMAND OR AS LISTED IN THIS SAA.(USERS

WILL NOT SUPPRESS OR MASK BEAMS WITHOUT UCC APPROVAL). AT MISSION COMPLETION,

THE AC TERMINAL WILL LEAVE THE BEAM(S) IN IDLE STATE, APR=3.

E. (U) PRECEDENCE LEVELS: TERMINAL OPERATORS ARE REMINDED THAT ANY CIRCUIT AT

PRECEDENCE OF P-1 OR P-2 MUST BE ESTABLISHED AS A NETWORK, NOT A PTP. A PTP MAY

ONLY BE ESTABLISHED AS A P-3 UNLESS THERE IS A VALIDATED AND APPROVED SAA

AUTHORIZING ESTABLISHMENT AT A HIGHER PRECEDENCE. ANY NON-APPROVED P-1 OR P-2

PTP WILL BE TORN DOWN BY THE PSOC/NAVSOC AS UNAUTHORIZED EHF USAGE.

DERIVED FROM: AEHF CLASSIFICATION GUIDE, 31 AUGUST 2009

DECLASSIFY ON: WRITTEN APPROVAL FROM THE U.S. PSM AND THE PARTICIPANT PSM

BT

Combined EHF LDR/MDR/XDR SAR Message Format v6

FM: [REQUESTING COMMUNICATIONS PLANNER]

TO: [COMBATANT COMMAND COMMUNICATIONS PLANNER]

[COMPONENT COMMAND]

[SUPPORTING RSSC AS REQUIRED]

INFO: [OTHERS AS REQUIRED]

BT

CLASSIFICATION: [TOP SECRET/SECRET/CONFIDENTIAL/UNCLASS]

SUBJECT: (U) EHF SATELLITE ACCESS REQUEST

CHANGE: (U) [IDENTIFY CHANGE SAR IF NECESSARY, FORMAT: CHANGE # XX FOR EHF ACCESS] REFERENCES: (U) [REFERENCE A, B, AND C, ETC. (AS NECESSARY)/MESSAGE CLASSIFICATION/

MESSAGE DATE TIME GROUP [DTG]/FROM ADDRESSEE/SUBJECT]

NOTE: ROUTINE REQUIREMENTS MUST BE SUBMITTED NO LATER THAN 30 DAYS PRIOR TO

REQUESTED SATELLITE ACCESS TIME. EXCEPTIONS WILL BE HANDLED ON A CASE-BY-CASE

BASIS.

1. (U) GENERAL INFORMATION:

A. (U) MISSION NAME/DATES: [FULL MISSION NAME]

(U) START: [DD0001ZMMMYY] END: [DD2359ZMMMYY]

B. (U) PURPOSE OF SAR: [PURPOSE OF SATELLITE ACCESS; I.E., TRAINING, CONTINGENCY

OPERATIONS]

C. (U) COMM PLANNER POC:

(U) SIPRNET: [XXX@XXX.smil.mil]

(U) NIPRNET: [XXX@XXX.mil]

(U) DSN: [XXX-XXX-XXXX] COM: [XXX-XXX-XXXX]

D. (U) 24-HOUR POC PHONE NUMBER:

(U) DSN: [XXX-XXX-XXXX] COM: [XXX-XXX-XXXX]

E. (U) DEPLOYED/UNDERWAY:

(U) DSN: [XXX-XXX-XXXX] COM: [XXX-XXX-XXXX]

F. U) OTHER:

(U) DSN: [XXX-XXX-XXXX] COM: [XXX-XXX-XXXX]

2. (U) LDR SERVICES REQUESTED:

A. (U) REQUESTED EHF CONSTELLATION: [MILSTAR (SAT#), AEHF (SAT#), UFO/E/EE (SAT#)]

B. (U) NET 1: [NETWORK NAME]

2) (U) SDB NUMBER: [STRATCOM 00000]

3) (U) CJCSI 6250.01 MISSION PRIORITY: [1A]

4) (U) PRECEDENCE: [P1]

5) (U) DATES/TIMES: [DD0001ZMMMYY THROUGH DD2359ZMMMYY]

6) (U) SERVICE TYPE: [NETWORK]

7) (U) LDR PROCESS: [NORMAL]

8) (U) NETWORK TYPE: [VOICE]

8) (U) DATA RATE: [2400 BPS]

9) (U) CROSSLINKS: [NO]

10) (U) CHANNEL TYPE: [C0]

11) (U) NECOS: [TERM ID]

12) (U) ALTERNATE NECOS: [TERM ID]

13) (U) STRATEGIC SERVICE REQUESTED: [NO/YES]

(U) TACTICAL REQUESTED MEMBER/SERVICE INFORMATION: [LIST FOR EACH TERMINAL]

(U) TERM ID/TERM TYPE/TX & RX MODE/TERM LAT/LONG:

i.e. [3300/A SMART-T/TX & RX/35.08N/78.59W] i.e. [2770/NMT SHORE/TX & RX/21.29N/158.05W]

(U) STRATEGIC REQUESTED MEMBER/SERVICE INFORMATION: [LIST FOR EACH TERMINAL]

(U) TERM ID/TERM TYPE/SAT/UL&DL BEAM/UL TS/TX&RX/LC2 ROBUST/DL LC3/DL BURST

RATE:

i.e [5555/MMPU/6/EC/EC/T4/RX/300 BPS/MOST/FSK 4] i.e [5222/MMPU/6/EC/TAC HIGH/T4/RX/75 BPS/MOST/FSK 6]

NOTE: DATA ENTRIES BELOW THIS LINE ARE OPTIONAL FIELDS

14) (U) DESIRED SPOT BEAM CONTROLLER(S/ALTERNATES: [TERM ID/EACH BEAM]

**[PIM DATA AS REQUIRED]

15) (U) USER EQUIPMENT TYPE: [UET TO BE USED FOR SERVICE]

16) (U) TDF: [FOR AF TERM TYPES ONLY]

17) (U) ARMY FLOW CONTROL: [FOR ARMY TERM TYPES ONLY]

18) (U) NAVY SERVICE TYPE: [FOR NAVY TERM TYPES ONLY]

C. (U) NEXT NETWORK: [REPEAT STEPS 1-18 (ABOVE) FOR EACH NETWORK]

D. (U) LDR REMARKS: [AS NEEDED]]

3. (U) MDR SERVICES REQUESTED:

C. (U) REQUESTED MILSTAR/AEHF FLIGHT: [FLIGHT 4, 5, 6, 7, 8 or 9]

D. (U) NET 1: [NETWORK NAME]

10) (U) SDB NUMBER: [PACOM 00000]

11) (U) CJCSI 6250.01 MISSION PRIORITY: [2C]

12) (U) PRECEDENCE: [P2]

13) (U) DATES/TIMES: [DD0001ZMMMYY THROUGH DD2359ZMMMYY]

14) (U) SERVICE TYPE: [DUAL SIMPLEX]

15) (U) NETWORK TYPE: [DATA]

16) (U) DATA RATE: [1024 KBPS]

17) (U) CROSSLINKS: [NO]

18) (U) COMMUNICATIONS CONTROLLER (CC): [TERM ID]

19) (U) ALTERNATE CC: [TERM ID]

20) (U) REQUESTED MEMBER/SERVICE INFORMATION: [LIST FOR EACH TERMINAL]

(U) TERM ID/TERM TYPE/FENCE/TX & RX MODE/TERM LAT/LONG:

i.e. [3300/A SMART-T/YES/TX & RX/49.23N/08.40E] i.e. [2770/NMT SHORE/YES/TX & RX/48.49N/09.11E]

21) (U) DESIRED ANTENNA CONTROLLER(S) AND ALTERNATE(S): [TERM ID/EACH

BEAM] **[PIM DATA AS REQUIRED]

13) (U) USER EQUIPMENT TYPE: [UET TO BE USED FOR SERVICE]

14) (U) ARMY FLOW CONTROL: [FOR ARMY TERM TYPES ONLY]

15) (U) NAVY SERVICE TYPE: [FOR NAVY TERM TYPES ONLY]

E. (U) NEXT NETWORK: [REPEAT STEPS 1-15 (ABOVE) FOR EACH NETWORK]

D. (U) MDR REMARKS: [AS NEEDED]

4. (U) XDR SERVICES REQUESTED:

A. (U) REQUESTED AEHF FLIGHT: [FLIGHT 7, 8 or 9]

B. (U) NET 1: [NETWORK NAME]

1) (U) SDB NUMBER [CENTCOM 00000]

2) (U) CJCSI 6250.01 MISSION PRIORITY [6B]

3) (U) PRECEDENCE: [P3]

4) (U) DATES/TIMES: [DD0001ZMMMYY THROUGH DD2359ZMMMYY]

5) (U) SERVICE TYPE: [ NETWORK]

6) (U) NETWORK TYPE: [DATA]

7) (U) DATA RATE: [ 8.192 MBPS]

8) (U) CROSSLINKS: [YES]

9) (U) COMMUNICATIONS CONTROLLER (CC): [TERM ID]

10) (U) ALTERNATE CC: [TERM ID]

11) (U) REQUESTED MEMBER/SERVICE INFORMATION: [LIST FOR EACH TERMINAL]

(U) TERM ID/TERM TYPE/TX & RX MODE/FENCE/TERM LAT/LONG

i.e. [3300/A SMART-T/ TX & RX/YES/49.23N/08.40E] i.e. [2770/NMT SHORE/TX & RX/YES/48.49N/09.11E]

12) (U) COALITION: [YES or NO]

13) (U) SESSION KEY: [TBD]

14) (U) DESIRED ANTENNA CONTROLLER(S) AND ALTERNATE(S): [TERM ID/EACH BEAM]

**[PIM DATA AS REQUIRED]

15) (U) DUAL KEY/DL-ONLY LOGON: [DL ONLY PROBE TYPE/DL ONLY XC3 MODE]

16) (U) RROW: [YES or NO]

17) (U) USER EQUIPMENT TYPE: [UET TO BE USED FOR SERVICE]

18) (U) TERMINAL DATA FORMAT: [FOR AF TERM TYPES ONLY]

19) (U) ARMY FLOW CONTROL: [FOR ARMY TERM TYPES ONLY]

20) (U) NAVY SERVICE TYPE: [FOR NAVY TERM TYPES ONLY]

21) (U) SUB or SUB-SUB FENCE SET-UP REQUESTED: [YES, NO/ Sub or Sub-Sub Fence]

FENCE PRIVILEGED TERM ID: [IDENTIFIES THE FP TERMINAL REQUESTED TO SET-UP

FENCE]

FENCE CONTROLLER TERM ID: [IDENTIFIES THE FC TERMINAL REQUESTED TO

CONTROL FENCE (MAY BE SAME AS FP TERM)]

FENCE ACTIVATION/DEACTIVATION DATE/TIME:

[DD0000Z MMM YY THROUGH DD2359Z MMM YY]

C. (U) NEXT NETWORK: [REPEAT STEPS (1-21 ABOVE) FOR EACH NETWORK]

D. (U) XDR REMARKS: [AS NEEDED]

5. (U) REMARKS: [ADD REMARKS AS NEEDED]

A. (U) OPERATIONAL IMPACT: [ADD OPERATIONAL IMPACT, INCLUDE SPECIFICS TO

SUPPORT INDICATED OPERATION. LIST IMPACT IF SAR IS NOT APPROVED]

DERIVED FROM: [APPLICABLE SECURITY PROTECTION GUIDE(S)]

DECLASSIFY ON: