NTP 2 NAVAL TELECOMMUNICATIONS PROCEDURES
NAVY SUPER HIGH FREQUENCY SATELLITE COMMUNICATIONS

72 Page 73 74
NTP 2 SECTION 1 (D)

ORIGINAL 5-1

CHAPTER 5
ADMINISTRATIVE PROCEDURES

• 501-General
• 502-ICDB Submissions
• 503-Emergent Requirements
• 504-Reporting Requirements

502. ICDB SUBMISSIONS The CINCs are the advocates for all SATCOM requirements for their respective AOR/ area of operation (AOO). Each CINC will consolidate, validate, and prioritize all requests for use of SATCOM systems within the AOR/ AOO. All DOD SATCOM requirements will be forwarded to the Joint MILSATCOM Panel Administrator (JMPA) for requirements processing. Non-DOD and Federal agencies' SATCOM access requirements will be submitted to ASD( C3I). If ASD( C3I) concurs in the requirement, it will be forwarded to the Joint Staff (J6) for review and action. When a routine requirement is received by the JMPA, it will be distributed to the appropriate system managers and DISA. The system managers and DISA will prepare a technical assessment within six weeks for routine requirements. Technical assessments that discuss the capability of current programmed systems to satisfy the requirement will be forwarded to the JMPA. Requirements that cannot be satisfied by current or programmed systems or that will only be partially satisfied will be indicated as such. The JMPA reviews SATCOM requirements using the technical assessments and makes a recommendation for approval or disapproval to the Joint Staff. When the Joint Staff renders a decision, the JMPA will enter all approved SATCOM requirements into the ICDB and provide timely notification to users whether requirements were approved or disapproved. The JCSC will initiate a review of all SATCOM requirements in the ICDB every two years to ensure all ICDB requirements are current and accurately stated.

503. EMERGENT REQUIREMENTS An urgent SATCOM requirement is submitted directly to the Joint Staff with information copies to the JMPA. The request will contain justification for urgent processing. The technical assessment by system managers and DISA will be expeditiously prepared and forwarded and the Joint Staff, with input from the JMPA, will approve or disapprove the request. 73

73 Page 74 75
NTP 2 SECTION 1 (D)

ORIGINAL 5-2

504. REPORTING REQUIREMENTS A. SHF Quicklook Reports. SHF Quicklook Reports shall be submitted daily to the controlling FLTCINC and NCTAMS by all SHF-equipped ships when emanations were active during the previous raday. The sample message provided below includes the minimal information. Additional information may be required by the Numbered Fleet Commander.

PRIORITY PRECEDENCE 
FM ORIGINATING UNIT 
TO CONTROLLING FLTCINC 
SUPPORTING NCTAMS 
INFO CNO WASHINGTON DC// N63// 
COMSPAWARSYSCOM SAN DIEGO CA// PMW176// 
COMNAVSPACECOM DAHLGREN VA// N3/ N5// 
SPAWARSYSCEN CHARLESTON SC// 542// 
DSCS NETWORK MANAGER WASHINGTON DC// 
(SUPPORTING DISA RCC)// 
(NUMBERED FLEET COMMANDER)// 
BT 
CLASSIFICATION// N02300// 
MSGID/ GENADMIN/( ORIGINATING COMMAND)// 
SUBJ/ SHF QUICKLOOK REPORT FOR RADAY DA/ MON/ YR// 
REF/ A/ COMNAVSPACECOM/ 970901// 
AMPN/ REF A IS NTP 2 SECTION 1 (D) NAVY SHF SATCOM// 
POC/( AS APPROPRIATE)// 
RMKS/ 1. PER REF A, THE FOLLOWING PROVIDES SHF QUICKLOOK 
REPORT FOR RADAY DA/ MON/ YR. 
A. SHIPS POSITION: (Note 1) 
(1) CURRENT 
(2) PROJECTED NEXT 72 HOURS 
B. SHIPS CONFIGURATION (Note 2) 
(1) TERMINAL TYPE 
(2) ANTENNA TYPE 
(3) MODEM TYPE 
(4) MULTIPLEXER TYPE 
(5) ANTENNA DIPLEXER FREQUENCY RANGE 
C. DSCS ASSIGNMENT (Note 3) 
(1) DSCS SATELLITE AND CHANNEL ASSIGNED 
(2) AGGREGATE DATA RATE OF TERMINATION 
D. TERMINATION DATA (Note 4) 
(1) PRIMARY TECHNICAL CONTROL 
(2) DATE/ TIME OF TERMINATION ACTIVATION 
E. TERMINATION/ CIRCUIT STATUS (Note 5) 
CIRCUIT DATA RATE STATUS 

74 Page 75 76
NTP 2 SECTION 1 (D)

ORIGINAL 5-3

2. OTHER INFORMATION AS APPROPRIATE// (Note 6) DECL/ XXX// BT

Note 1: Include current latitude and ocean area name. Additionally, include projected movement location over the next 72 hours.

Note 2: For satellite terminal type include TSC-93B, WSC-6 (V) 1, WSC-6( V) 2, WSC-6( V) 4, or fly away SHF satellite terminal. For antenna type, include nomenclature and dish size (e. g., 4-foot or 7-foot and whether single or dual antenna configured. For modem type include MD-1030, SLM-4650, CQM-248A, STeL 1105, OM-55, MD-945, etc.) Indicate the modem in use shipboard for termination as well as any other modems that might be onboard. Provide modem type that is in use at the satellite earth terminal ashore as well. For multiplexer type, include the number, types, and version of multiplexers installed shipboard (e. g., FCC-100, TD-1389, TSSP, TIMEPLEX, etc.)

Note 3: Indicate satellite, satellite channel, and frequency assigned. Also include total aggregate of termination (e. g., 16 kbps, 32 kbps, 50 kbps, 64 kbps, etc.)

Note 4: Indicate shore station that is providing satellite uplink/ downlink and shore station that is the point of baseband multiplexing. Additionally, provide date/ time (ZULU) of termination activation.

Note 5: List noun name, DISA Command Communications Service Designator (CCSD) (if known), and individual data rate for all circuits channelized in the termination baseband. Additionally, report status up, down, and any outage logged during the previous 24 hours. If out of time of report, so state to include time.

Note 6: Report any information pertaining to status, difficulty, lessons learned, or request for operational/ technical assistance.

B. After Action Reports (AAR). AARs are required 10 days after the mission ends. AARs are used to evaluate system performance, identify procedural and technical conflicts, and solicit recommendations for improvements. The message format and a sample AAR are provided below.

1. AAR Format 
PRIORITY PRECEDENCE 
FM USER 
TO RSSC 
CSPE (IF NOT SENDER) 
GNC 
GATEWAY 
INFO COMARSPACE COLORADO SPRINGS CO// MOSC-ZO/ OS// 

75 Page 76 77
NTP 2 SECTION 1 (D)

ORIGINAL 5-4

ALL OTHERS (AS DIRECTED) 
BT 
CLASSIFICATION// N02XXX// 
SUBJ/ AFTER ACTION REPORT FOR MISSION XXXX-XX// 
A. CLAS MSG XXXXXXZ XXX XX RSSC SUBJ: GMF SATELLITE ACCESS 
AUTHORIZATION MISSION XXXX-XX (RECEIVED XXXXXXZ XXX XX) 
B. PHONECON XXXXXXZ XXX XX FROM, UNIT/ TO, UNIT SUBJ: 
C. XXX TCCC MSG XXXXXXZ XXX XX XXX SUBJ: 
1. POC/ ORGANIZATION/ DSN/ COMMERCIAL 
2. MISSION NAME 
3. MISSION ACCESS TIME: 
A. AUTHORIZED FROM XXXXXXZ XXX XX / TO XXXXXXZ XXX XX 
B. CTUAL: FROM XXXXXXZ XXX XX / TO XXXXXXZ XXX XX 
4. NETWORK TYPE: E. G., POINT TO POINT, HUB-SPOKE, MESH, 
GATEWAY 
5. POWER (IN WATTS): 
TML PREDICTED ACTUAL 
A. XXX XX. X XX. X -XX. X 
B. XXX XX. X XX. X -XX. X 
6. PLANNING AND COORDINATION (Note) 
7. CONTROL COMMUNICATIONS (Note) 
8. OUTAGES IN EXCESS OF 15 MINUTES AND RFO 
9. COMMENTS// 
BT 

2. AAR Sample 
X XX 
FM USER 
TO RSSC CONUS WASHINGTON DC// MOSC/ OMC-CO// 
RSSC EUROPE VAIHINGEN GE// MOSC-OME-EU// 
RSSC PACIFIC WHEELER AAF HI// MOSC-OMP-PA// 
DSCS NETWORK MANAGER WASHINGTON DC// 
DISAGOSC WASHINGTON DC// D361// 
CSPE (IF NOT SENDER) 
GNC 
INFO COMPSPACE COLORADO SPRINGS CO// MOSC-ZO/ OS// 
ALL OTHERS (AS DIRECTED) 
BT 
CLASSIFICATION// N02XXX// 
SUBJ/ AFTER ACTION REPORT FOR MISSION C345-94// 
A. UNCLAS MSG 201100Z FEB 94 CSPE SUBJ: GMF SATELLITE ACCESS 
AUTHORIZATION MISSION C345-94 (RECEIVED 131345Z MAR 94) 
B. UNCLAS MSG 110902Z MAR 94 RSSC SUBJ: GMF SATELLITE ACCESS 
AUTHORIZATION MISSION C345-94 (RECEIVED 131345Z MAR 94) 

76 Page 77 78
NTP 2 SECTION 1 (D)

ORIGINAL 5-5

C. PHONECON 050900Z MAR 94 BETWEEN RSSC AND CSPE SUBJ: 
VERIFICATION OF SAR DATA. 
1. CPT MAJOR/ 6789 CSS/ DSN 123-4567/ COMMERCIAL (123) 456-7890 
2. MISSION NAME: HAPPY TIMES 
3. MISSION ACCESS TIME: 
A. AUTHORIZED: FROM 2217100Z MAR 94 TO 272400Z MAR 94 
(CONTINUOUS) 
B. ACTUAL: FROM 221710 MAR 94 TO 271800Z MAR 94 
4. NETWORK TYPE: HUB-SPOKE 
5. POWER (IN WATTS): 
TML PREDICTED ACTUAL 
A. B11 N/ A 45-60 
B. C21 N/ A 70-90 
C. D31 N/ A 150-175 
6. PLANNING AND COORDINATION: ADEQUATE (Note) 
7. CONTROL COMMUNICATIONS: ADEQUATE (Note) 
8. OUTAGES IN EXCESS OF 15 MINUTES AND RFO 
TML FROM TO RFO 
D31 240023Z 2400850Z MAR 94 FINAL POWER AMPLIFIER 
TRIPPED 
9. COMMENTS 
A. REFERENCE PARAGRAPH 6, MISSION CUT SHEETS NOT AVAILABLE 
AT TERMINAL D31 PRIOR TO START OF EXERCISE. MISSION 
TERMINATED EARLY, DEACCESS/ TERMINATION COORDINATED 
WITH GNC. 
B. REFERENCE PARAGRAPH 7, TERMINAL C21 FM ORDERWIRE FAILED 
251315Z MAR 94, CONTROL COMMUNICATIONS WITH GNC 
MAINTAINED VIA B11 UTILIZING TSSP ORDERWIRE THRU END OF 
EXERCISE.// 
BT 

Note: The following Grading Scale is used in the report to document the level of problems encountered during satellite usage.

· Excellent -Granted when no problems of any kind were encountered with respect to mission planning and coordination either on the part of the units/ terminals, GMF Manager, or GNC.

· Adequate -Granted when only minor problems arise with respect to mission planning and coordination (e. g., minor problems with SAR, SAA). May require further explanation in remarks.

· Poor -Granted when major problems arise with respect to mission planning and coordination (e. g., major problems with SAR, SAA or Terminal Deployment Orders, Cut Sheets, uncoordinated and unexplained extended delays with initial access, terminal directed to 77

77 Page 78 79
NTP 2 SECTION 1 (D)

ORIGINAL 5-6

deaccess/ terminate satellite access for configuration violations, etc.) Further explanation required in remarks.

C. Communications Spot Report (COMSPOT). A COMSPOT is a report submitted to the controlling NCTAMS and DISA by all fleet units experiencing difficulties that have caused, or are expected to cause, a communications outage in excess of 30 minutes. Any changes in status, including restoration of communications, will also be reported. The following is an example of a COMSPOT.

PRECEDENCE (NORMALLY IMMEDIATE) DATE-TIME GROUP 
FM (ORIGINATOR) 
TO NCTAMS 
DSCS NETWORK MANAGER WASHINGTON DC// 
DISAGOSC WASHINGTON DC// D361// 
INFO (CHAIN OF COMMAND) 
BT 
CONFIDENTIAL// N02790// (THIS CLASSIFIED SAMPLE FORMAT IS FOR 
EXAMPLE ONLY) 
MSGID/ COMSPOT/ ORIGINATOR// 
REF/ A/ COMSPOT/ ORIGINATOR OF COMSPOT/ DATE-TIME GROUP// 
COMEV/( EVENT)/( START TIME)/( END TIME)/( SYSTEM)// 
AMPN/( FREE TEXT)// 
RMKS/( FREE TEXT)// 
DECL/ XXX// 

D. Research, Development, Test, and Evaluation (RDT& E) Report. RDT& E activities granted access to a DSCS satellite will submit an R& D test report once each day during extended access periods or within 24 hours following an access period of less than one day. The report is submitted as shown in the following example.

PRECEDENCE (NORMALLY ROUTINE) DATE-TIME GROUP 
FM (ORIGINATOR) 
TO DSCS NETWORK MANAGER WASHINGTON DC// 
DISAGOSC WASHINGTON DC// D361// 
INFO (APPROPRIATE FLTCINC) 
COMSPAWARSYSCOM SAN DIEGO CA// PMW176// 
COMNAVCOMTELCOM WASHINGTON DC// N3/ N32// 
(APPROPRIATE NCTAMS)// N5// 
(ALL UNITS CONDUCTING THE TEST) 
BT 
UNCLAS// N02844// 
MSGID/ GENADMIN/ ORIGINATOR/ SERIAL NUMBER/ MONTH// 
SUBJ/ SHF SATELLITE R& D TEST (REQUIREMENT OR REPORT)// 
REF/ A/ NTP 2 SEC 1/ COMNAVSPACECOM// 971101// 
AMPN/ SATELLITE TERMINATION REQUEST// 

78 Page 79 80
NTP 2 SECTION 1 (D)

ORIGINAL 5-7

RMKS/ 1. (PERIOD OF REQUIREMENT) 
2. (TERMINATING STATION) 
3. (PLANNED POSITION) 
4. (TYPE OF TRAFFIC AND MODULATION) 
5. (ADDITIONAL INFORMATION OR REMARKS) 
(A) TEST OF NET ENTRY PROCEDURES FOR USS BLUE RIDGE USING OM-55( 
V)/ USC MODEM. 
(B) SHIP WILL ESTABLISH COORDINATION ORDERWIRE VIA ALTERNATE 
PATH PRIOR TO ACCESSING SATELLITE.// 
BT 

E. Hazardous Condition (HAZCON) Reports. HAZCON reports are used when a loss of service or severe degradation of communications is probable unless preventive action is taken. It must be viewed as an urgent notification of a major problem that has occurred or is projected to occur. Failure of any combination of primary, backup, spare communications equipment, or power facilities when failure of another like component would cause link outage, facility outage, or severe degradation warrants a HAZCON report. Other situations such as a partial or complete evacuation of a DCS facility, loss of diversity on a radio link, or loss of facility are considered to be HAZCONs. There are two types of HAZCON reports: formatted and nonformatted.

1. Formatted HAZCON Reports a. Formatted report procedures are prepared for computer processing and strict procedures are required to ensure complete understanding of the information. A formatted report will contain specific line symbols. These symbols are as follows:

(((( Indicates beginning of report S Identifies the reporting facility S or L Station facility HAZCON or link HAZCON / Separates data elements RMKS Beginning of narrative remarks (6 lines) 1. Date/ time the HAZCON commenced. 2. Specific location. 3. A concise statement of the situation and the affected communications. 4. Estimated time of repair (ETR) or N/ A if unknown. After five days HAZCONs must have an ETR. 5. Description of action taken or action to be taken. In the event of a complete failure, include restoral plans. 6. Operational Managing Agency and a request for assistance if needed. XXXX Identifies the end of narrative remarks. ))) Indicates the end of report. 79

79 Page 80 81
NTP 2 SECTION 1 (D)

ORIGINAL 5-8

b. Formatted HAZCON reports are submitted after the condition has existed for 24 hours and are updated every 24 hours by submitting a HAZCON update report. This report is submitted in the same format as a HAZCON report except the S/ L line will read UPDATE; the third line will contain updated information; the fourth line will list the ETR, new or unchanged; the fifth line will address any new developments; and the sixth line will include an explanation for the change. The following is an example of a HAZCON formatted report.

(((( 
SNWS 
SNWSHAZ/ RMKS NEW HAZCON 
1. 021030Z MON YR 
2. NAVSATCOMMFAC NORTHWEST VA 
3. AN/ FSC-78( V) SYSTEM POWER AMPLIFIER NR 1 DOWN FOR 
SKED PMS. 
4. 021230Z MON YR 
5. SHOULD POWER AMPLIFIER NR 2 FAIL POWER AMPLIFIER NR 
1 WILL BE BROUGHT ON LINE. 
6. COMNAVCOMTELCOM: NO ASSISTANCE REQUIRED. 
XXXX 
)))) 

c. The formatted HAZCON termination report is the same as the preceding reports except it only contains four narrative lines. Termination is placed in the S/ L line. The first and second lines will remain the same as the HAZCON and HAZCON UPDATE. The third line contains the date-time group (DTG) of the HAZCON termination, and the fourth line consists of the action taken to correct the HAZCON.

2. Nonformatted HAZCON Reports a. Nonformatted HAZCON reports are submitted in near-real time to the nearest RSSC. The nonformatted report is basically the same as the formatted HAZCON report, except there are no opening/ closing parentheses, L-line, or four XXXXs. Line A is the first narrative line and is used for the date/ time of the HAZCON; line B is a description of the HAZCON; line C contains the ETR if known or "N/ A" (it must be updated in five days); line D indicates parts required to repair along with noun-nomenclatures; line E cites the responsible Operations and Maintenance Agency, and required assistance if needed; and line F is used for remarks. Nonformatted HAZCON update reports are submitted the same as nonformatted HAZCON reports, except that the first line will read "RMKS UPDATE" and any updated information will be provided in narrative lines B, C, D, E, and F. Line A remains the same as in the original HAZCON. The following is an example of nonformatted HAZCON report.

SNWS 
SNWSHAZ/ REMKS NEW HAZCON 
A. 201820Z MON YR 
B. LOSS OF PRIMARY POWER 

80 Page 81 82
NTP 2 SECTION 1 (D)

ORIGINAL 5-9

C. 222000Z MON YR 
D. 080702 POWER CABLE 
E. COMNAVCOMTELCOM 
F. NONE 

b. Nonformatted HAZCON termination reports are the same as other nonformatted HAZCON reports except that only three narrative lines are used. "RMKS TERMINATION" in line one indicates the HAZCON has terminated. Line A contains the HAZCON DTG. Line B is the date/ time of termination. Line C consists of the corrective action taken to clear the HAZCON.

F. Detailed Outage Report (DOR). The purpose of the DOR is to provide detailed information regarding an outage. These reports are used to assist in analysis and resolution of specific communications problems within the DCS. They are submitted at the request of a Regional Satellite Support Center (RSSC) or a DISA activity in the event an outage is prolonged, and troubleshooting is ongoing or concluded with positive or negative results to aid in restoral of communications. The following is an example of information contained in a DOR.

1. DOR Format

2. DOR Example. The following information is an example of a completed DOR.

DETAILED OUTAGE REPORT (DOR); DATE 
DOC DIR EUR DE NWS 
1. 11BS04 
2. 271849Z MON YR 
3. 272031Z MON YR 
4. HIGH SIGNAL/ NOISE, KY-801 
5. 1858Z DOWNLINK MONITOR (NWS) SAME INDICATIONS 
1859Z DOC/ DIR/ EUR NOTIFIED 
1915Z NEGATIVE QSO WITH DISTANT END 
1920Z COMMS ESTABLISHED WITH D/ E 

81 Page 82 83
NTP 2 SECTION 1 (D)

ORIGINAL 5-10

1925Z D/ E UPLINK MONITOR UP AND GOOD 
1927Z D/ E SWAPS UP CONV -STILL NO GO 
1933Z D/ E SPARES OFF MODEM 
1938Z CONDITIONS UNCHANGED 
1942Z D/ E RPTS THEIR UPLINK MONITOR HAS BEEN GOOD ALL 
ALONG 
1950Z THISTA CONTACTS DOC TO LOOK AT DOWNLINK 
1953Z DOC RPTS DOWNLINK AS NORMAL AT FREQ REQUEST 
SYMPTOMS FADING IN AND OUT MODEM LOCKED UP WITH S/ N 
KY ERRS AND DECODER SYNC HITS. 
2010Z SYMPTOMS INTERMITTENT MODEM STILL LOCKED UP 
2013Z ALL SYMPTOMS CLEARED. 
6. THISTA HAS EXPERIENCED LOCAL RFI 3 TIMES IN PAST 3 
MONTHS AND SUSPECTS SAME AND WERE ABLE TO OBSERVE RFI ON 
HP8566B BEFORE, BUT SPECN WAS NOT AVAIL AT TIME OF OUTAGE. 
7. THISTA SUSPECTS LOCL RFI AS PROBLEM. 
XXXX