COMPLIANCE WITH THIS PUBLICATION IS MANDATORY

Transcription

1 BY ORDER OF THE COMMANDER 50TH SPACE WING 50TH SPACE WING INSTRUCTION MAY 2013 Incorporating Cange 4, 8 May 2017 Operations AIR FORCE SATELLITE CONTROL NETWORK (AFSCN) USERS OPERATIONS INSTRUCTIONS COMPLIANCE WITH THIS PUBLICATION IS MANDATORY ACCESSIBILITY: Publications and forms are available on te e-publising website at for downloading or ordering RELEASABILITY: Tere are no releasability restrictions on tis publication OPR: 22 SOPS/DOK Supersedes: 50 SWI 10217, 1 Mar 2001; 50 SWI 10218, 1 Oct 2003; 50 SWI 10223, 1 Aug 2000 Certified by: 22 SOPS/CC (Lt. Col W. Scott Angerman) Pages: 96 Tis instruction implements AFPD 10-2, Readiness, by establising requirements, responsibilities, products, and interfaces involved in te management and conduct of te Air Force Satellite Control Network (AFSCN) operations. Tis publication applies to all activities and organizations, including AFRC and ANG units, supporting and using AFSCN controlled resources. Contractor personnel requirements and responsibilities contained witin tis instruction may be modified for a specific purpose troug a validated Performance Work Statement (PWS). Te PWS must indicate specific paragraps tat are being modified. Eac squadron, detacment, organization, section, or operational area may develop supplements to tis instruction. Send one copy to 22 SOPS/DOK, 401 O'Malley Ave, Suite 51, Scriever AFB, CO Ensure tat all records created as a result of processes prescribed in tis publication are maintained in accordance wit (IAW) Air Force Manual (AFMAN) , Management of Records, and disposed of IAW Air Force Records Disposition Scedule (RDS) located in te Air Force Records Information Management System (AFRIMS). Refer recommended canges and questions about tis publication to te Office of Primary Responsibility (OPR) using te AF Form 847, Recommendation for Cange of Publication. Submit requests for waivers to te Publication OPR for non-tiered compliance items.

2 2 50SWI MAY 2013 SUMMARY OF CHANGES Tis interim cange revises 50SWI by (1) Replacing Attacment 2 wit an updated version of te priority matrix. A margin bar ( ) indicates newly revised material. Capter 1 AFSCN OVERVIEW Overview Air Force Satellite Control Network (AFSCN) Operational Control Node (OCN) Remote Tracking Station (RTS) Roles and Responsibilities AFSCN Resource AFSCN User Inter-range Operational Number (IRON) Products Figure 1.1. AFSCN Communications Overview AFSCN Communications Network Electronic Scedule Dissemination (ESD) SOPS Network Operations Center (22 SOPS NOC) SCS Comm Focal Point (CFP) SAFB Secure Voice Operations (SAFB SVO) SOPS Network Operations Center (21 SOPS NOC) EOSOF Patc and Test Facility (PTF) VAFB Secure Voice Operations (VAFB SVO) RTS Comm Area Capter 2 REAL TIME OPERATIONS Real Time Operations Policy: Roles and Responsibilities:... 17

3 50SWI MAY Capter 3 CONFLICT BRIEFING OPERATIONS Daily Conflict Resolution Process Conflict Period Conflict Delete Conditional Delete Program Delete To Be Resolved (TBR) Pre-Deconfliction Listing Frequency Control and Analysis Center (FCAC): Network Sceduling will: AFSCN Users will: SOPS Orbital Analysis will: SOPS Mission Planning will: Procedures: Submit MSCs to Network Sceduling for modifications, adds and deletes witin te seven-day and conflict briefing periods via ESD For deleted satellite contacts Te conflict resolution process ends wen te de-conflicted period is publised as te latest NTO Capter 4 SEVEN-DAY OPERATIONS Policy Seven-day Forecast Frequency Control Message SAT Data PAP Data Network Sceduling will: AFSCN User will: RTS will: SOPS Orbital Analysis will:... 26

4 4 50SWI MAY SOPS Mission Planning will: Capter 5 CERTIFICATE TO OPERATE Purpose Certification to Operate (CTO) Certification Process Proficiency Tasks Decertification Process Capter 6 MISSION IMPACT REPORTING (MIR) Purpose AFSCN users will: SCS/MOC will: NCMDR/NCCH will: SOPS ACCC will RTS will SOPS MAF will: Capter 7 FREE SPACE RADIATION REQUEST Policy Network Sceduling will: RTS will: Capter 8 LAUNCH OPERATIONS Description Launc Readiness and Responsibilities Network Sceduling will: SOPS Orbital Analysis will: SOPS Mission Planning will: MESA and NOPS will: All Launc Agencies will: Capter 9 DOWNTIMES Policy

5 50SWI MAY Downtime NCMDR/NCCH Network Sceduling will: SOPS Mission Planning will: Requesting work center will: Process: Complete te Downtime Request (Nine-Line subject) Routine Request Capter 10 DISA AUTHORIZED SERVICE INTERRUPTIONS Purpose DISA ASI Demand Maintenance SCS TCF and 21 SOPS PTF will: SOPS Comm Control will: SOPS NOC will: Procedures Capter 11 VOICE OPERATIONS Purpose Defense Red Switc Network (DRSN) Integrated Services Telepone (IST) PRI Secure Voice (PSV) Satellite Secure Voice Net Defense Switc Network (DSN) Private Branc Excange (PBX) Tie-line Conference Bridge AFSCN Voice Operations AFSCN user will: SAFB Secure Voice Operations (SVO) will:... 41

6 6 50SWI MAY VAFB Secure Voice Operations (SVO) will: SOPS comm control Secure Voice Operations Prepass Briefing Prepass Cecks Satellite Contact Post-Pass Emergency Satellite Contacts Request for Satellite Contacts Not Sown in te NTO Contingency Operations Voice Communication Failures Negative Voice Communications Procedures Common to All Loss of Communications Situations Capter 12 RTS IRON DATABASE CHANGE PROCESS Purpose Procedures: Figure RTS IRON Database Cange Process Flowcart Roles and Responsibilities: Capter 13 TRANSMIT INHIBIT ZONE (TIZ) AND OBSCURA MANAGEMENT Purpose Procedure... 53

7 50SWI MAY Attacment 1 GLOSSARY OF REFERENCES AND SUPPORTING INFORMATION 54 Attacment 2 AFSCN PRIORITY MATRIX 65 Attacment 3 REMOTE GROUND FACILITIES 68 Attacment 4 SITE DOWNTIME PREFIXES 69 Attacment 5 SECURE VOICE PROCEDURES 70 Attacment 6 AFSCN WORK CENTERS CONTACT INFORMATION 72 Attacment 7 NON-SECURE VOICE PROCEDURES 75 Attacment 8 VOICE OPERATIONS CONTINGENCY PROCEDURES 77 Attacment 9 AFSCN COMMON OPERATIONS TERMINOLOGY LEXICON 87

8 8 50SWI MAY 2013 Capter 1 AFSCN OVERVIEW 1.1. Overview. Tis capter provides an overview of te Air Force Satellite Control Network (AFSCN) organizations, systems, products, and terminology Air Force Satellite Control Network (AFSCN). A global ground and space-based network comprised of two Operational Control Nodes (OCNs), land and space based Defense Information Systems Agency (DISA) communications connectivity, seven Remote Tracking Stations (RTSs) and one test resource facility dedicated to support Department of Defense (DOD) communications, weater, researc and development, and intelligence gatering space programs Operational Control Node (OCN). Provides routing and switces tat connect users to RTSs Scriever Air Force Base OCN (SAFB OCN) - located at Scriever Air Force Base (SAFB) Vandenberg Air Force Base OCN (VAFB OCN) - located at te Ellison Onizuka Satellite Operations Facility (EOSOF) on Vandenberg Air Force Base (VAFB) Remote Tracking Station (RTS) Seven RTSs located around te world provide uplink and downlink connectivity to te space veicle. Eac station maintains at least two antennae, or sides. Eac side can support a single contact at a time RTS Test Resource Facility (RTSTRF), located at SAFB, used for testing and evaluation of Inter Range Operations Number (IRON) databases and transport resources See Attacment 3 for a detailed list of te AFSCN RTSs Roles and Responsibilities. Te following organizations are responsible for operating, maintaining, and managing AFSCN assets: t Network Operations Group (50 NOG) - oversees all AFSCN operations and sustainment st Space Operations Squadron (21 SOPS) - oversees all AFSCN communications assets and tose range assets located at Diego Garcia, Guam, Hawaii, and VAFB. 21 SOPS operates and maintains te AFSCN OCN facility on VAFB nd Space Operations Squadron (22 SOPS) - oversees all network management assets and tose range assets at SAFB. 22 SOPS functions as te primary interface for all AFSCN users. Tey are responsible for developing, maintaining, and enforcing operational directives and policy witin te AFSCN rd Space Operations Squadron (23 SOPS) - oversees tose range assets located in Greenland, England, at Cape Canaveral, and at New Boston Air Force Station (AFS). 23 SOPS operates and maintains te New Boston AFS.

9 50SWI MAY t Space Communications Squadron (50 SCS) - operates and maintains te AFSCN OCN facility on SAFB AFSCN Resource. Any pysical asset witin te AFSCN construct tat provides support to autorized satellite operators Common User Element (CUE) - tose resources available to multiple users Mission Unique Equipment (MUE) - tose resources used only by a specific mission User assets - tose assets outside direct AFSCN control tat utilize AFSCN resources to support various space programs Range assets - tose AFSCN ground assets tat provide a direct interface wit spacebased systems Communications assets - tose AFSCN assets tat provide a conduit between user and range assets Network management assets - tose AFSCN assets tat direct and control te use of AFSCN resources AFSCN User. Any organization utilizing AFSCN resources Internal Users AFSCN users assigned to 50t Space Wing (50 SW) External Users (EXU) - AFSCN user organizations tat are not assigned to te 50 SW Inter-range Operational Number (IRON). A randomly generated unclassified four-digit number assigned to eac space veicle, as supported in fligt or pre-fligt Products. Numerous documents are developed and distributed to support te AFSCN mission. Requirements for various messages not detailed ere are obtained from te applicable Memorandums of Agreement (MOAs) for te supporting agencies. See Capters 2 troug 4 for development and distribution of sceduling products. Te following documents are applicable to AFSCN CUE resources: Network Tasking Order (NTO). Te culmination of all pases of NTO development, it is te official AFSCN tasking scedule publised daily in 24-our blocks. Te NTO identifies wic AFSCN resources (range assets, communications assets, and oter supporting assets) are assigned to eac fligt and non-fligt activity. Tese tasks are indicated in Electronic Scedule Dissemination (ESD) by equipment mnemonics at assigned specific support times for eac site-side. Te NTO is developed troug completion of tree basic pases: Seven-day Forecast Conflict Briefing Operations Realtime period is te publised Network Tasking Order (NTO) Tree-mont Forecast. An official notification to all AFSCN users of te intent to scedule an activity. Te tree-mont forecast includes upcoming major operations and planned downtimes.

10 10 50SWI MAY Seven-day Forecast. Publised witin te seven-day Forecast pase of NTO development, it is a forecast of all fligt and non-fligt activities for te upcoming seven-day period. Te seven-day forecast is used to establis te initial definitive tasking scedule for AFSCN resources and frequency control messages for te Remote Ground Facility (RGF). Maintenance as well as user Satellite Acquisition Table (SAT) and Program Action Plan (PAP) information is loaded to ESD for te seven-day period Pre-Deconfliction Listing. Publised witin te Conflict Briefing Operations pase of NTO development, it identifies satellite contacts in conflict wit oter activities and provides any suggested modifications to nominal satellite configuration required to alleviate conflict NTO. Publised every 24 ours, it consists of: Conflict Briefing list wic identifies AFSCN wide impacting maintenance downtime, Conflict Deletes, Conditional Deletes, and To Be Resolved (TBR) conflicts A 24-our scedule tat identifies autorized usage of AFSCN resources wic includes all fligt (launc support, satellite contacts) and non-fligt (downtime, training, etc.) activity Realtime Cange Message. Notification of a fligt or non-fligt activity cange made to te current NTO. ESD provides realtime cange notifications and tracks wic AFSCN users and work centers ave acknowledged receipt Manning Scedule Cange (MSC). AFSCN users are required to submit an MSC to affect or acknowledge a cange to teir support requirements witin te seven-day and conflict briefing periods. Tis MSC provides 22 SOPS autorization from te Satellite Control Autority (SCA) to add a new contact or to delete or modify an existing satellite contact previously entered to te scedule. An MSC provides an audit trail for subsequent review and investigation purposes sould te need arise Downtime request. A formal request for maintenance, testing, validation, or system ceckout tat will cause a sceduled loss, limit, or risk of loss of AFSCN resources AFSCN Outage Report. An AFSCN outage report identifies and reports an unsceduled loss or limitation of AFSCN resources. It is used primarily by te user and network sceduler personnel to mitigate risk to space missions, and by maintenance and logistics personnel for trending purposes Mission Impact Report (MIR). Provides AFSCN users a process for reporting less tan successful satellite contacts wen problems encountered are suspected or known to be caused by AFSCN assets, or wen te cause is unknown. A MIR will initiate te process for determining and addressing te reason for te unsuccessful support. MIRs are used to document anomalies, provide audit trails, and determine trending data for recurring problems. See Capter 6 for MIR requirements Ancillary Event. Tis product provides details of abnormal conditions of AFSCN assets wen tey are not captured by a downtime or outage report.

11 50SWI MAY Figure 1.1. AFSCN Communications Overview AFSCN Communications Network. Te AFSCN communications network is designed to provide operators te ability to create dynamic communications connections between user and range assets. See figure 1.1. Te following describes te cief elements of te AFSCN communications network: Inter-nodal communications (INC) - a communications link between te OCNs. INC provides a pat for contingency routing sould direct communications wit eiter node fail. Communications connections across te AFSCN network automatically re-route across INC witout operator intervention Primary communications (PRI) - te primary communications between an OCN and a RGF. PRI carries bot Primary Secure Voice (PSV) and veicle data Additional communications (ADD) - te additional communications between an OCN and a RTS. ADD provides operators wit an additional route for mission data sould PRI fail, or te opportunity to redirect telemetry or commanding in addition to using PRI Operators must explicitly connect to range resources using PRI and/or ADD. Te AFSCN communications network is designed to keep PRI and ADD traffic separate, and places te onus on te operator to route operational traffic around failures or downtimes of eiter communications system Wide Area Network Interface Unit (WANIU) - provides users te interface into te AFSCN communications network. User and range assets are connected to ports of a WANIU, so operators may create dynamic connections between tose assets RTS WANIU - Eac RTS maintains a WANIU for Primary connectivity (PRI) and one for Additional connectivity (ADD).. EVCF maintains a single WANIU for PRI connectivity only. Tese WANIUs provide port connectivity for range assets, suc as commanding, telemetry and IRIG-B signals, and port connectivity for transporting subsystems, suc as secure voice and ESD OCN WANIU - provides port connectivity for user assets at te OCNs, and port connectivity for transporting subsystems, suc as Secure Voice and ESD.

12 12 50SWI MAY EXU (NOPS and RSC) WANIU - provides external users a direct interface into te AFSCN network OCN WANIUs and EXU WANIUs are not restricted to PRI or ADD and route over te communications system as configured by te operator Distributed Communications Controller (DCC) - te application, and te workstation on wic it runs, tat allows an operator to configure, monitor, and release communications resources between WANIU ports Control and Monitor (C&M) - AFSCN communications between DCC and WANIU, wic provides te conduit for controlling and monitoring WANIUs, WANIU ports, and te dynamic connections between. C&M will route around failures of PRI or ADD AFSCN Operational Signals (AOS) - WANIU connections dynamically establised by operators for eac satellite contact Static Connections - WANIU connections permanently maintained by te communications work centers in support of various subsystems and user missions. Static connections wit an RGF traverse eiter PRI or ADD depending on wic RTS WANIU is assigned C&M, AOS, static connections, and test connections all sare te same available bandwidt between locations. Users sould be cognizant of possible limits in available bandwidt wen establising AOS. ADD typically provides less trougput, or bandwidt, for mission data tan PRI Electronic Scedule Dissemination (ESD). ESD is a global computer network used to disseminate AFSCN network management products SOPS Network Operations Center (22 SOPS NOC). Te 22 SOPS NOC produces and maintains te integrity of te NTO and is responsible for all operational aspects of te AFSCN. Te 22 SOPS NOC includes te following functions: Network Crew Commander / Network Crew Cief (NCMDR/NCCH) - provides operational command and control over all AFSCN resources, and oversees AFSCN outage reporting Network Sceduling - develops and publises te NTO, allocates AFSCN resources, and manages Realtime activities Orbital Analysis - produces orbital products suc as pointing data and Radio Frequency Interference (RFI) for NTO production SOPS Mission Planning - coordinates, inputs, and tracks downtime requests and oter non-fligt activities SCS Comm Focal Point (CFP). Te CFP provides a focal point for discrepancy reports and maintenance activity. Te AFSCN functions of te CFP include: Maintain a istorical record of AFSCN discrepancies and outages for trending Maintenance Control - oversees maintenance activities of AFSCN systems and processes requests for depot level maintenance support.

13 50SWI MAY SAFB Tec Control Facility (SAFB TCF). Te SAFB TCF maintains te AFSCN communications circuits terminating at SAFB, operates encryption gear for AFSCN services at SAFB, provides administrative support of AFSCN communications devices, and provides support for te integrated EXU assets located at SAFB. It prioritizes all maintenance activity occurring witin Mod 3/ SAFB Secure Voice Operations (SAFB SVO). SAFB SVO supports voice connectivity troug SAFB for AFSCN operations SOPS Network Operations Center (21 SOPS NOC). 21 SOPS NOC oversees AFSCN operations at VAFB and includes te following sub-functions: Network Operations - manages communications oversigt for te AFSCN enterprise. Tis includes maintaining AFSCN comm situational awareness, reporting, and outage resolution coordination Comm Control - oversees te identification and resolution of communication failures and degradations, and provides support for te integrated EXU assets not located at SAFB EOSOF Patc and Test Facility (PTF). Te EOSOF PTF maintains te AFSCN communications circuits terminating at te EOSOF, operates encryption gear for AFSCN services at EOSOF, and provides administrative support of AFSCN communications devices VAFB Secure Voice Operations (VAFB SVO). VAFB SVO supports voice connectivity troug VAFB for AFSCN operations RTS Comm Area. RTSs maintain a communications area to provide support for operations and maintenance of collocated communications assets.

14 14 50SWI MAY 2013 Capter 2 REAL TIME OPERATIONS 2.1. Real Time Operations. Te period from now until te end of te latest publised NTO. ESD servers and workstations continuously display te end time of te latest publised NTO known as te Real Time Boundary. Network Sceduling responds to all realtime canges necessitated by SCA requirements, outage conditions, or satellite anomalies Policy: All AFSCN users, RGFs, and supporting agencies will adere to te NTO Te 22 SOPS NOC maintains operational command and control over AFSCN resources Any modification to te NTO tat increases network tasking (i.e., early radiation requests, contact adds or extensions, including additional resources) must be coordinated wit and approved by Network Sceduling prior to te action being taken Te conflict resolution process is used for bot planned (Conflict Briefing period) and unplanned (Realtime) conflict situations. If a conflict involves two requirements from witin te same agency, it will be resolved internally by te agency, and te final solution provided to Network Sceduling. Wen a conflict involves separate agencies, sceduling will make every effort to resolve te conflict based on existing priorities witin attacment 2, te approved classified priority matrix and any oter dynamics involved. If unresolved tis conflict becomes a TBR and is presented to te NCMDR/NCCH at least two ours prior to te start of te pre-pass for te earliest requested satellite contact in conflict. Te NCMDR/ NCCH will make te final decision and pass results to Network Sceduling at least 30 minutes prior to te start of te prepass for te earliest requested satellite contact in conflict Te recognized Satellite Control Autority (SCA) for a veicle is te only agency tat may request canges to a fligt activity, unless tey ave previously autorized and coordinated wit 22 SOPS for anoter agency to do so AFSCN users may submit an MSC wen a block cange is required and is precoordinated wit Network Sceduling. Sceduling will deconflict/coordinate as required to incorporate te requested canges AFSCN users are autorized to access AFSCN resources from te first second of start of prepass as sceduled on te NTO, and must release resources prior to te first second of te stop time listed on te NTO Network Sceduling is te approval agency for all RTS free-space radiation requests An RTS need not radiate during te entire block of time autorized on te NTO, but an RTS may not radiate outside of te autorized radiate times.

15 50SWI MAY Non-fligt activities requiring AFSCN CUE must be accomplised during te time specified on te NTO. Te times tat appear on te NTO are to be used for activity specified in te scedule, and are not to be used for oter purposes witout prior coordination and approval Use secure communications wenever possible. Wen secure communications are not available, all parties will use appropriate call-back procedures Network Sceduling will notify all affected AFSCN users and work centers of canges to te NTO via ESD realtime cange notifications or by voice wen ESD is not available AFSCN users and work centers will acknowledge ESD cange notifications upon receipt Network Sceduling will contact, by voice, any affected AFSCN users or work centers wo ave not acknowledged an ESD cange notification wen te start time is witin two ours Network Sceduling will use te AFSCN Satellite Contact Priority List in Attacment 2 wen approving, coordinating and processing adds, deletes, or modifications to te publised NTO, and coordinate wit te NCMDR/NCCH to provide resource allocation direction wen establised priority guidelines fail to resolve conflicts A classified Priority Matrix is available to te NCMDR/NCCH/NSCH to furter clarify mission priority Wen a veicle anomaly occurs, te impacted AFSCN user will immediately contact Network Sceduling and declare te appropriate satellite contact priority, using te AFSCN Satellite Contact Priority List available in Attacment AFSCN users and work centers will notify Network Sceduling of early termination of sceduled activities wen tere is a sceduled sort turnaround to (TAT) te next sceduled activity or te activity is terminated early by five or more minutes Outage Conditions: See 50SWI for outage responsibilities Network Sceduling will contact tose users adversely impacted by an outage condition to determine contact support alternatives Network Sceduling will not alter any fligt activity in te NTO tat cannot be supported due to an outage condition, unless te affected AFSCN user autorizes a deletion, limitation or a move of te impacted activity If a problem occurs during a satellite contact, te affected AFSCN user will immediately alert all personnel on te net supporting te satellite contact All alerted personnel will in return provide te status of equipment at teir location Te AFSCN user will report any mission impact IAW te MIR process (Capter 6) and include in te report te statuses provided by eac location NOC Override:

16 16 50SWI MAY SOPS will develop, distribute, enforce and maintain NOC Override procedures designed to quickly and efficiently enance AFSCN access and enforce te NTO Te NCMDR/NCCH will use te NOC override function to ensure te Network Tasking Order is strictly adered to In te event of a request for a NOC Override, resources will not be released witout confirmation of offending veicle safing from te user. LEO supports tat are more tan 2 minutes beyond visibility fade will be released wit no contact to te user Non-fligt Activities. Network Sceduling will notify AFSCN users via ESD of any canges to downtimes tat impact user required network resources Te AFSCN work center responsible for a downtime will assess te status of te downtime at 30 minutes before te expiration of te sceduled downtime If te assessment indicates operational capability will not be restored by te end of te downtime, contact Network Sceduling and attempt to extend te downtime If te downtime cannot be extended witout approval of Sceduling troug coordination wit an impacted user, te responsible work center will open an appropriate category outage witin 10 minutes of te extension being denied AFSCN Overloading and Optimization: Contingencies may occur tat could cause overloading of available AFSCN resources. Wen conflicts present severe AFSCN mission impact, based on feedback from AFSCN users and work centers, or more tan four Lost supports and/or Conflict Deletes occur in a six-our period, te 22 SOPS NOC will consider taking te following steps to increase AFSCN availability: Delete proficiency training Delete RTS maintenance activities on a case-by-case basis Continue to monitor MIRs and user feedback If training and maintenance ave been reduced and on-orbit satellite contact activities are still impacted, Network Sceduling will conduct te following Level l to 4 reductions (sequentially) until te NCMDR/NCCH determines Lost supports and/or Conflict Deletes are reduced to an acceptable level: Level 1 reduction - Delete exercise and network testing sorties Level 2 reduction - Maximize use of dedicated program resources. Consider reducing maintenance activity on te network Level 3 reduction - Cancel non-mission impacting on-orbit testing and monitoring/ tracking sorties Level 4 reduction - Eliminate lower priority sorties per Priority Matrix located in Attacment In te event tat National Readiness is elevated, directives contained in te applicable 22 SOPS cecklist will be followed.

17 50SWI MAY Roles and Responsibilities: NCMDR/NCCH will: Maintain operational command and control of all AFSCN resources Use all available resources wen rendering te final decision for AFSCN resource use during conflict resolution of a TBR conflict Immediately notify Network Sceduling wit resource allocation decisions Ensure compliance wit te NTO using inerent autority and te NOC override process Assist users wo cannot release resources due to DCC system anomalies Process depot level support requests for any site requiring it Immediately notify Network Sceduling wen outages are reported or veicle emergencies are declared Wen RTS operators report a site problem, or wen MIR submission warrants, investigate te problem and ensure an outage is opened IAW 50 SWI , AFSCN OUTAGE REPORTING SYSTEM Maintain a toroug understanding of all program mission requirements for all users wo conduct operations wit te AFSCN Review and ensure reported outages are accurate prior to distribution to te AFSCN community Notify all AFSCN users of NOC or ESD limitations or evacuation events, to include any contact information Investigate all MIRs and voice reported problems submitted and determine potential for ongoing network impacts. If impacts are determined to be ongoing and negatively impact AFSCN user missions, ensure an outage is opened to reflect te impact If user mission is not negatively impacted, coordinate wit 21 SOPS NOC for troublesooting requirements Notify NSCH of any JSTO, SPIN or SKIWEB taskings tat impact te NTO Assist wit RMI (RFI/EMI) identification and adjudication Network Sceduling will: Scedule AFSCN resources for satellite contacts in accordance wit SCA requirements Resolve realtime conflicts IAW tis instruction Notify te NCMDR/NCCH wen any user attempts to use AFSCN resources witout prior coordination and approval by Network Sceduling.

18 18 50SWI MAY Immediately notify NCMDR/NCCH wen veicle emergencies are declared or wen a sceduled downtime or unsceduled outage creates a cange to SYSCAP/OPSCAP Notify impacted AFSCN users and work centers of veicle emergency conditions in progress Grant or deny free-space radiation requests based on user approval Grant or deny AFSCN user requests to go active prior to sceduled satellite acquisition time AFSCN users will: Ensure te NTO contains required attributes to support satellite contacts Ensure satellite contacts are conducted according to publised NTO requirements Never conduct a support not listed on te NTO NOT radiate or send te active directive or request te RTS operator to manually go active prior to or after, teir sceduled support time witout prior coordination wit Network Sceduling. Tis includes back-to-back supports by te same user Ensure resources in use are available (i.e., terminated) for te next user prior to te first second of te last minute listed on te NTO Immediately contact te NCMDR/NCCH if resources fail to release and request a NOC Override Immediately notify Network Sceduling of any veicle emergency support requirements Notify Network Sceduling wen upcoming minimum support requirements cannot be met due to an outage condition Wen required by te NCMDR/NCCH, provide mission objectives for satellite contacts in conflict and articulate te mission impact if AFSCN resources are not allocated to te satellite contact in question Contact Network Sceduling wen requesting a cange to a sceduled satellite contact Verify te operational impact of eac outage affecting te assigned program Notify 22 SOPS wen evacuation of ops is required or as occurred, to include contact information for relocation area wen possible Wen te cause of a mission impacting non-nominal support is known or suspected to be caused by AFSCN resources, or te cause is unknown, verbally notify 22 SOPS NCMDR via appropriate voice metod witin 15 minutes of support fade or immediately after determining a satellite contact was scored oter tan nominal during telemetry review Provide information tat is known at tat time. Provide detailed information in te content of te MIR per capter 6.

19 50SWI MAY Do not provide a voice report wen an outage is open for te problem tat is encountered Immediately notify te supporting RGF of any detected problems during te support RTS will: Notify Network Sceduling immediately upon identifying conflicting satellite contacts Serve as a backup for NOC Overrides. Operators will accept override direction only from autorized individuals listed on te NOC Override Autorization letter, updated every mont by 22 SOPS Submit antenna radiation requests to Network Sceduling wen free-space radiation is required Verify any non-standard configuration posted on te NTO wit Network Sceduling Notify Network Sceduling wen any user attempts to use AFSCN resources witout prior coordination wit, and approval from, Network Sceduling Review te veicle folder or Operations Directive (OD), and verify te autorized active directive lead-time on te NTO, and verify te autorized start time for eac support Report and update AFSCN Outage Conditions IAW 50SWI , AFSCN OUTAGE REPORTING SYSTEM Submit downtime requests and ancillary messages to 22 SOPS Network Sceduling Track reported anomalies by updating appropriate database systems; e.g. RTS Online Activity Database System (ROADS), wit all pertinent information SCS CFP will: Advise te NCMDR/NCCH on all communications outages and status canges as tey occur, to include potential impact to AFSCN resources and users Assist NCMDR/NCCH in investigating mission impact reports Gater and track anomalous sortie information, outage information, and 50 SW maintenance activities Notify 21 SOPS Comm Control of communications related problems, outage conditions, and trends Report and update AFSCN Outage Conditions IAW 50SWI , AFSCN OUTAGE REPORTING SYSTEM Coordinate wit 22 SOPS to obtain any needed windows or downtime required to perform restoration actions.

20 20 50SWI MAY Notify 22 SOPS wen evacuation of ops is required or as occurred, to include contact information for relocation area wen possible SOPS NOC will: Advise te NCMDR/NCCH on all communications outages and status canges as tey occur, to include potential impact to AFSCN resources and users Monitor AFSCN network communications Report and update AFSCN Outage Conditions IAW 50SWI , AFSCN OUTAGE REPORTING SYSTEM Coordinate wit TCF on te Operational Switc Replacement (OSR) Tec Net for any OSR troublesooting efforts Coordinate wit 22 SOPS to obtain any needed downtime required to perform restoration actions Notify 22 SOPS wen evacuation of ops is required or as occurred, to include contact information for relocation area wen possible Orbital Analysis will: Accomplis investigations and resolution of EMI IAW AFI Provide Network Sceduling wit two-line mean element (TLE) sets, satellite acquisition tables (SATs), RFI data, Lunar and Sun RFI (SRFI) data Provide custom orbit products to AFSCN users as requested Accomplis post-event EMI/RFI investigations as required Perform RTS azimut and elevation angle bias analysis following antenna maintenance or natural disasters.

21 50SWI MAY Capter 3 CONFLICT BRIEFING OPERATIONS 3.1. Daily Conflict Resolution Process. Te daily conflict resolution process allocates AFSCN resources to an activity wit te igest priority for a particular time and site. Resultant products include te NTO and te Daily Conflict Brief Listing wic contains notifications to AFSCN users of specific conflicts wic result in Conflict Deletes, Conditional Deletes, TBR conflicts, and downtimes tat may impact multiple sites During tis period all conflicts are identified and potential resolutions are presented to users in an attempt to minimize conflicts and ensure satellite operator mission success. During te conflict resolution process, all conflicts or imposed limitations are discussed and resolved at te lowest possible level commensurate wit responsibility, autority, and available guidance Tis process is completed daily between te ours of 0000z 1000z. During tis process satellite PAP requirements will be strictly maintained MSCs will be submitted via ESD by users to effect and finalize any cange to an existing contact or to add a new contact. Submit MSCs in te following format: Date/Time (Z) - te date and time of a single support, or te time span encompassing several supports, wic te requested cange affects Site - Enter te site wit X (i.e., BOSS-X) if eiter side may be used for tis support, or te specific site and side if support must be run on a particular antenna. Use ANY for a request tat impacts several supports (e.g., add ARSS) or wen specific site/side is not required IRON - te IRON of te affected satellite contact. Use ANY for a line tat impacts all contacts owned by te user witin a stated period of time and/or on a stated Site/Side Rev - te specific revolution of te satellite contact. Use ANY wen te cange impacts several supports (ensure Date/Time or Site/Side encompasses te desired support contacts) Func - te ESD function of tis request (Blank) eading - A wen adding a satellite contact, M wen modifying an existing satellite contact, or D wen deleting a satellite contact Comments - any clarifying comments to be included witin te comments field of te impacted supports, or oter additional information For any negotiated resolution wit less tan nominal requirements, te AFSCN user sould state wat deviations were accepted (e.g. sort turnaround, substituted equipment, etc.) For deleted satellite contacts, te AFSCN user will include if te deletion is a Conflict or Program Delete. If te type of deletion is not specified, Network Sceduling will categorize it as a Program Delete.

22 22 50SWI MAY Reason for Cange - a description of reason for te cange Conflict Period. Te 24-our time period, 1600Z to 1600Z daily, tat is being prepped for publication as te next NTO Tis is te forecast period for wic Network Scedulers, AFSCN users, and oter AFSCN work centers, resolve any remaining conflicts between program requests, sceduled downtimes, and oter non-fligt activities Users are notified of potential intra-afscn radio frequency interference and downtimes tat may impact te entire AFSCN Conflict Delete. Tose satellite contacts wic cannot be sceduled due to limited resources, and cannot be fulfilled elsewere, resulting in te loss of mission data are identified as Conflict Deletes. Conflict Deletes are documented on te Daily Conflict Briefing Listing Conditional Delete. Used by Network Sceduling in conjunction wit a launc or downtime to indicate te Realtime disposition of eac satellite contact impacted by a potential launc slip or potential completion time of a downtime. Conditional Deletes are listed on te Daily Conflict Briefing Listing Substantiating documentation, by MSC, from te AFSCN user must include all details and will contain all agreed upon conditions including a time tag delineating wen te conditions are to be executed. Te text of te conditional resolution, wen practical, will be identical to te Conflict MSC, te Conflict Briefing Listing, and te NTO Program Delete - label assigned to a contact request from an AFSCN user witdrawn due to internal requirements, program requirements met wit alternative satellite contacts, and so on Program Deletes are similar to Conflict Deletes, but are used wen te satellite contact can be deleted (due to satellite contact requirements being reduced, dropped, or fulfilled elsewere) witout loss of mission data. Program Deletes do not appear on te Conflict Briefing Listing To Be Resolved (TBR). A conflict tat cannot be resolved troug normal processes prior to being placed in te Real Time scedule becomes a TBR issue and forwarded to te NCMDR/NCCH for resolution Pre-Deconfliction Listing. Publised every day by 1100z, tis output lists te satellite contacts requested by te Mission Command Center (MCC)/ Space Operations Center (SOC) and annotates tose satellite contacts wit conflicts (e.g. sun RFI, launces) or contact limitations imposed by resource availability issues Frequency Control and Analysis Center (FCAC): Te FCAC is a Western Range Asset and is not part of te 50SW. Tey provide frequency control and analysis functions for te launc agency witin 30SW. Tey will: Resolve EMI/RFI conflicts to provide EMI/RFI protection to AFSCN satellites from various Western Range activities Coordinate troug te RTS and inform Network Sceduling wen protection from launc pad EMI/RFI cannot be provided to AFSCN satellites.

23 50SWI MAY Inform Network Sceduling wen RF restrictions are placed on Vandenberg Tracking Station to protect payloads on te Western Range Network Sceduling will: Load Data Entry FormaT (DEFT) files Minimize conflicts wile remaining witin users stated requirements as muc as possible Offer workable solutions outside of user s requirements to aid in conflict resolution Publis te Pre-Deconfliction listing Coordinate conflict resolution wit involved users Prepare and publis te Daily Conflict Briefing Listing AFSCN Users will: Review impacts to satellite contact requirements publised in te Pre-Deconfliction Listing and resolve conflicts IAW tis capter Complete conflict resolution negotiation wit, and submit MSCs to, Network Sceduling NLT 1100Z Include specific details of conflict resolution (including Conditional Deletes) on te MSC. Submit an MSC via ESD. If ESD is not available, submit a ard copy via fax, contact Network Sceduling by pone to notify tem of te faxed document Ensure personnel wit proper autority to resolve conflicts are available 24/7, or make arrangements for conflict resolution wit 22 SOPS for any period te user is not available Wen applicable, submit 24 our DEFTs by 0200Z daily Complete deconfliction by 1700z daily and submit MSCs by 1800z daily SOPS Orbital Analysis will: Provide SRFI and RFI data to Network Sceduling SOPS Mission Planning will: Respond to Network Sceduling on identified conflicts involving protected downtimes and Network Freeze impacts Negotiate conflict resolutions tat impact downtimes Procedures: Te daily Conflict Briefing period must include all known requirements. Users are responsible for submitting new or canged requirements via MSC. Network Sceduling personnel will incorporate new and/or modified requirements into te daily Conflict Briefing period Network Sceduling will optimize te conflict period and identify resultant conflicts and limitations. During tis process, satellite Program Action Plan (PAP) requirements will be strictly observed.

24 24 50SWI MAY To aid in optimization, eac satellite contact is assigned a satellite contact priority by te MCC/SOC responsible for te satellite contact based on te nature of te mission being supported (see Att. 2 for AFSCN Satellite Contact Priority List) Network Sceduling may suggest modifications to original support requirements in order to gain conflict resolution Te conflict resolution process begins wen te pre-deconfliction listing is publised at 1100Z. Tis listing contains all requested satellite contacts for te period of te next NTO and identifies supports in conflict, supports wit reduced nominal equipment, supports wit a reduced prepass from its nominal and sceduler suggested modifications intended to avoid stated conflicts Users will coordinate wit Network Sceduling to ensure conflict resolution is acieved NLT 1700Z daily Conflict resolution is acieved wen a decision as been made concerning wo will receive te resource, or acceptance of a limitation is agreed upon, and MSCs ave been received by Network Sceduling confirming all canges to requested satellite contacts If a conflict cannot be resolved, it will be publised on te NTO as a TBR conflict and forwarded to te NCMDR/NCCH for furter evaluation and resolution. Te NCMDR/NCCH may be requested to engage at any time during te conflict resolution period in order to resolve a conflict Submit MSCs to Network Sceduling for modifications, adds and deletes witin te seven-day and conflict briefing periods via ESD. An MSC provides an audit trail for later review and investigation purposes sould te need arise For any negotiated resolution wit less tan nominal requirements, te MCC/SOC sall state wat deviations were accepted (e.g. sort turnaround, substituted equipment, etc.) for eac support For deleted satellite contacts- Network Sceduling will assume a Program delete is appropriate unless oterwise specified on te user MSC Te conflict resolution process ends wen te de-conflicted period is publised as te latest NTO- wit its associated Conflict Brief Listing wen required.

25 50SWI MAY Capter 4 SEVEN-DAY OPERATIONS 4.1. Policy. Te seven day period beginning on te next Monday at 0000Z, tis is te forecast period for wic Network Scedulers load veicle acquisition data, program requests, and nonfligt activities into ESD Te seven-day Forecast provides valuable non-fligt allocation information to te users. Satellite contacts and non-fligt activities are bulk loaded into te ESD database. Inputs for generation of te seven-day Forecast fall into two major categories. Tese categories are Satellite Acquisition Tables (SATs) and Program Action Plans (PAPs) If several canges to a previously submitted PAP are required witin a seven day period, Network Sceduling may request a new PAP and/or SAT in lieu of an MSC Seven-day Forecast. Tis forecast is publised every Tursday at 2200Z and takes effect te following Monday at 0000Z. Te publised seven-day Forecast spans te seven-day period from Mon 0000Z to Mon 0000Z and combines user SAT and PAP data wit te seven-day Maintenance Forecast into a single product. Te product is used by user and sceduler personnel to forecast potential conflicts wit major veicle events and planned maintenance Frequency Control Message. Provided for GTS, HTS and VTS use for launc and aircraft radio frequency deconfliction SAT Data. Normally electronically submitted via ESD, SAT data is used to populate te sceduling database wit veicle visibilities. Submission of acquisition data varies wit te type of orbit PAP Data. Normally electronically submitted via ESD, PAPs are profiles used by various MCCs/SOCs to identify teir satellite contact requirements. Once te PAP as been loaded into te ESD database, any canges to user requirements must be accomplised by submitting an MSC. Agencies submitting paper PAPs sall ensure all entries are clear, in time sequence and do not contain crossed out information Network Sceduling will: Ensure te latest acquisition (SAT) data and its associated PAP are on and and loaded into te ESD database prior to publising te seven-day Forecast Publis te seven-day Forecast every Tursday NLT 2200Z AFSCN User will: Submit acquisition data to Network Sceduling. Updates to acquisition data will be submitted to Network Sceduling wenever acquisition times cange Submit accurate satellite contact requirements via PAP no later tan 2000Z Tuesday, six days prior to te effective seven-day forecast. Submit satellite acquisition data to 22 SOPS/DOUA for new veicle or launc no later tan Tuesday, tirteen days prior to te date of te effective seven-day forecast Submit satellite positional data to 22 SOPS/DOUA in accordance wit ICD-509. Additional SAT inputs are provided as needed for maneuvers and orbital updates.

26 26 50SWI MAY Participate in te weekly downtime meeting (eiter by attendance or teleconference) conducted every Friday by 22 SOPS Mission Planning Determine if any critical operations (launces, on-orbit maneuvers, etc.) will be impacted by forecast downtimes Participate in conflict resolution wen potential impacts to critical operations are identified Provide orbit track data to RTS or 22 SOPS Orbital Analysis for entry into te NORAD Element Data Set (NEDS) RTS will: Provide forecast downtimes to 22 SOPS Mission Planning NLT Tuesday at 1600 (Mountain Time) six days prior to te effective seven-day forecast Submit requests or canges to non-fligt activities to 22 SOPS/MAO during 22 SOPS normal duty ours, Monday troug Friday or to Network Sceduling after normal duty ours and on weekends or olidays SOPS Orbital Analysis will: Generate and distribute satellite visibility data for AFSCN users and remote tracking stations Submit 14 days of acquisition data via SAT on TUESDAY and FRIDAY by 2200z prior to te date of te effective seven-day forecast. Friday's delivery only consists of 2SWS and all low flyers. Additional SAT inputs are provided as needed for maneuvers and orbital updates Provide Predictive Radio Frequency Interference (PRFI) report to Network Sceduling at least once per week Provide Predictive Sun RFI report to Network Sceduling at least once per week during te seasonal equinoxes for primary and additional AFSCN communication links SOPS Mission Planning will: Process and ensure te accuracy of non-fligt requirements Enter non-fligt seven-day requirements into te ESD database by 2000Z Tursday of eac week Ensure te seven-day non-fligt activities in NTO are reviewed for accuracy and also to ensure tere is no AFSCN SYSCAP impact below an amber rating for tis period.

27 50SWI MAY Capter 5 CERTIFICATE TO OPERATE 5.1. Purpose. Te purpose of tis capter is to establis procedures for AFSCN users to demonstrate to 22 SOPS teir proficiency in te use of DCC workstations to configure and deconfigure AFSCN resources and teir understanding of policy surrounding te NOC Override function. Paragraps 5.2 troug 5.4 do not apply to existing autorized users. Paragrap 5.5 applies to all users of te AFSCN Certification to Operate (CTO). Organizations new to te AFSCN are required to certify troug a train te trainer approac prior to using te AFSCN communications resources Demonstrated proficiency is a prerequisite for users to obtain a CTO Te 22 SOPS/CC or 22 SOPS/DO is te approval autority for CTO All activities and organizations using AFSCN resources are required to meet tis policy CTO must be completed NLT 30 days prior to launc, assumption of program responsibility, or any operations using AFSCN resources In te event a user cannot meet tese requirements due to configuration or oter justifiable limitations, a waiver may be requested Request for a waiver must be submitted to 22 SOPS/CC troug 22 SOPS/DOK. Te request sould explain te reasons te user cannot meet te requirements outlined in tis capter, provide possible workarounds to ensure no negative impact to te network, and provide any possible get well dates for documented deficiencies Certification Process. 22 SOPS/DOK manages and administers te CTO program SOPS/DOK will observe te performance of te organization trainer (SME) wile tey are responding to te proficiency tasks identified below. 22 SOPS/DOK will monitor and assess training and certification supports from te 22 SOPS NOC and ensure tat te user understands NOC Override purpose, process and requirements Te SME is required to successfully complete five monitored proficiency tasks prior to certification Upon successful completion of te CTO process, te organization trainer will in turn certify operators witin is or er organization Proficiency Tasks. Tis section details te tasks for wic a user must demonstrate proficiency. During te training satellite contacts, te SME will: Acquire all required resources witin 30 seconds of being given te direction to acquire, Set Asyncronous Response Mode (SARM) and release all resources after te SARM witin 15 seconds of being given te direction to release Successfully request a NOC override of currently configured resources. Te SME will state wic RGF site-side requires a release of resources, wat time to release resources, and confirm teir veicle is safed.

28 28 50SWI MAY Release resources witin 15 seconds of receiving a call, prior to te sceduled fade time of te support, from 22 SOPS ordering an immediate release of resources Decertification Process. 22 SOPS/DO oversees te decertification process A user organization tat accumulates tree or more Personnel Errors (PEs) witin a 30-day period, wic resulted in a NOC override of user resources, will be issued a warning by te 22 SOPS/DO If a user organization receives two warnings witin a 30 day period from te 22 SOPS/DO, or upon 22 SOPS/DO discretion, te user will be directed to recertify IAW wit section 5.3 of tis capter. Only mission essential operations will be allowed until te user organization completes recertification.

29 50SWI MAY Capter 6 MISSION IMPACT REPORTING (MIR) 6.1. Purpose. Te MIR provides AFSCN users a process for reporting less tan successful satellite contacts wen problems encountered are unknown, suspected or known to be caused by AFSCN assets or user equipment. A MIR will initiate te process for determining and addressing te reason for te unsuccessful support. MIRs are used to document anomalies, provide audit trails, and determine trending data for recurring problems. MIRs elp identify sceduling discrepancies, procedural issues, and possible outage conditions. Users must continue to submit MIRs after an outage as been opened at te RTS AFSCN users will: Gater as muc information as is available and attempt to identify te cause of a problem as soon as it is detected. If te problem occurs during a satellite contact, te user will alert all personnel supporting te satellite contact and gater te status of supporting equipment Notify te RTS operator of any satellite contact scored lost, failed, or marginal, eiter in post-pass or after determining a satellite contact was scored oter tan nominal Notify 22 SOPS NCMDR witin 15 minutes of determining a support was nonnominal. Provide known information suc as mission impact and observed beavior. Investigation details will be included on te subsequent MIR Complete a MIR, using 50 SW Form 79 for any satellite contact scored lost, failed, or marginal witin one our of determination via secure means wenever possible Ensure information provided for te support matces information contained witin te NTO Determine te Satellite Contact Score for all non-nominal satellite contacts according to 50SWI , Table Classify te completed MIR according to te unit s Security Classification Guide and provide appropriate declassification instructions wen required Submit MIR to te 50 SCS MOC and 22 SOPS NCMDR via SIPR , NIPR using te Low-to-Hig website or via NIPR as a last resort Low-to-Hig Website: ttps://dots.dodiis.mil MOC SIPR: usaf.scriever.50sw-nog.mbx.50-scs-maintcontrol@mail.smil.mil MOC NIPR: MOCMPR@us.af.mil AFSCN NCMDR SIPR: usaf.scriever.50sw-nog.mbx.afscn-ncmdrsipr-mirs@mail.smil.mil AFSCN NCMDR NIPR: 22SOPS.NCMDR.MIR@us.af.mil Provide MIR closure meeting feedback to MOC.

30 30 50SWI MAY SCS/MOC will: Assign a unique MPR number, investigate, and arcive MIRs Coordinate wit te NCMDR/NCCH regarding potential system or range outage conditions Coordinate wit 21 SOPS ACCC regarding potential communications outage conditions Provide MIR feedback to te submitting user wen te reported problem is resolved Attend te 22 SOPS MIR Review Board (MRB) NCMDR/NCCH will: Review MIRs for accuracy of IRON, time and location of support and work center assignment. Notify MOC of any required corrections Investigate reported anomalies and perform real time trend analysis to determine if a system outage condition exists Coordinate real time trend analysis investigation wit appropriate agencies as required, i.e. 50 SCS, RTS operator or ACCC Provide notification to 22 SOPS/DO wen users fail to adere to par SOPS ACCC will : Investigate reported anomalies and determine if a communications outage condition exists RTS will : Track reported anomalies and determine if a range outage condition exists SOPS MAF will: Manage te MIR Review Board (MRB) and processes Determine and socialize appropriate frequency and participants for MRB occurrence THE MRB will: Review MIRs wose cause as not been determined. Coordinate wit RTSs, users, 50 SCS MOC, ACCC and oter agencies as required to provide insigt to any unknown issues Coordinate wit 50 SCS MOC to ensure submitting users concur wit closures Determine follow on actions as required, suc as outages, deficiency reports, AF Form 1067 Modification Proposal, etc Submit MIRs suspected to be caused by space weater to: JSpOC Weater Team: usaf.vandenberg.afspc.mbx.jspoc-weater-team@mail.smil.mil. 2d Weater Squadron - Dr. Mills: boniface.j.mills.civ@mail.smil.mil

31 50SWI MAY Capter 7 FREE SPACE RADIATION REQUEST 7.1. Policy. 22 SOPS Network Operations Sceduling is te approval agency for all RTS free space radiation requests and any user request for early radiation. RTS and AFSCN users will not radiate beyond tose times approved on te NTO witout autorization from Network Sceduling Network Sceduling will: Be te granting autority for all AFSCN radiation requests Perform an interference analysis on eac request to determine wic AFSCN satellites may be at risk wit frequencies requested during te radiation period Contact potentially impacted users to determine impact to teir space veicle(s) Deny or modify te request for te following reasons: Wen users deny te radiation request due to risk to teir veicle In te absence of user input, if a satellite using te same frequency(s) is visible, or a LEO witin 5 minutes of rise or fade, at te requesting RTS If te requested radiation times/ cannels can be modified to eliminate risk to impacted users, coordinate canges wit te requesting RTS and any impacted users and enter te granted request. Sceduling may approve a different antenna direction, command type based on user concurrence, or te use of an open cannel to eliminate possible interference Grant te request only wen it is clearly evident tat a need to radiate exists, and only wen te radiation time will not conflict wit any oter AFSCN operation Ensure te approved RTS free space radiation request appears on te NTO RTS will: Verbally submit antenna radiation (free space) request to Network Sceduling Submit a new free space radiation request if any deviation from te original request is necessary.

32 32 50SWI MAY 2013 Capter 8 LAUNCH OPERATIONS 8.1. Description. 22 SOPS is responsible for te planning, coordination, resolution, allocation, status, and tasking of AFSCN resources deemed necessary for launc and early-orbit operations, and ensuring te AFSCN is properly dispositioned wen executing a launc Launc operations supported by te Network will be afforded a Priority 4 for a time period of launc +6 ours for Hig Eart Orbit (HEO) and Medium Eart Orbit (MEO) veicles and launc +6 revs for all Low Eart Orbit (LEO) veicles. However, tis priority does not apply to booster or upper-stage support after spacecraft separation Major orbit transfer maneuvers and satellite contacts necessary for te collection of critical attitude data required to accomplis tose transfer maneuvers, as well as critical first acquisition of sun/eart/stars and critical initial deployments (solar wings, antennas, etc) will also be granted a launc priority of Guidance for Operations Requirement Letter (ORL) and Freeze message input and timelines is contained witin 50SWI , Launc Readiness and Responsibilities Slip Windows. Slip windows are a sceduling tool only and represent te window for launc vice an actual launc time. Tis allows potential conflicts to be identified and resolved wile allowing satellite contacts to be sceduled as Conditional Deletes against te launc profile. Users agree to terms of support based on potential launc status during deconfliction. If te launc goes as planned, users in conflict will be deleted based on teir previous acceptance of te Conditional Delete. If te launc does not impact te contact due to slipping 24 ours or, in te case of a contact in conflict wit te slip window only, launcing on time, te contact can be supported as sceduled Network Freeze. A Network freeze ensures ECP (Engineering Cange Proposal), TCM (Test Case Modification), TCC (Temporary Cange Configuration), and routine maintenance activities remain static and CUE/RTS configurations are not modified until after launc or critical fligt activities are completed. Non-interference basis (NIB) maintenance activities are not addressed. Reference 50 SWI , Launc Readiness and Responsibilities for furter guidance Launc Readiness and Responsibilities. In addition to te below requirements, all launc agencies utilizing te AFSCN for support will perform requirements outlined in 50 SWI , Launc Readiness and Responsibilities Network Sceduling will: Input launc requests into ESD wen electronic PAP is received Refuse and return user PAP submissions tat display several errors, contain incorrect information, or contain incorrect functions (e.g., PASS vice RPAS) Enforce te launc freeze request IAW 50SWI

33 50SWI MAY SOPS Orbital Analysis will: Provide SAT DATA to sceduling at L-3 weeks for all agencies except MESA and NOPS Provide Network RFI to Network Sceduling for any sceduled launc at L-1 day Provide updated network RFI files were product delivery is dependent upon receiving updated orbital parameters from te SOC and allowing 2 ours of system processing in te event of a source data anomaly Post TLE to ESD and notify sceduling for payload support activities at L-1 were product delivery is dependent upon receiving updated orbital parameters from te SOC and allowing 2 ours of system processing in te event of a source data anomaly Coordinate wit launc agency Orbit Analyst during pre- and post-launc activities to ensure accurate data is entered into ESD SOPS Mission Planning will: Ensure all required resources identified on ORL are available for launc support Develop and maintain te 50 SW 90-day Launc Forecast Publis and distribute AFSCN Freeze and Freeze release messages 8.6. MESA and NOPS will: Provide SAT DATA directly to Network Sceduling via ESD at L 10 days Post required TLE(s) in ESD at L 1 day. Any instructions for loading tese TLE will be provided to 22 SOPS at te time tey are posted All Launc Agencies will: Provide an electronic PAP or DEFT via ESD to Network Sceduling by L-10 days Do not include any slip window in te body of requested supports. Te slip window will be a separate function added to te end of supports witin te first six ours of a GEO, MEO and HEO launc or te first six revs of a LEO launc in order to accomplis te deconfliction process Do not include any time required for prepass cecks in te body of te support. Te pre-pass is defined by your ESD PAP and is distinctive part of te launc support Identify Priority 4 support requirements for inclusion into ESD comments and any oter specific information tat may need to be communicated to te RTSs or scedulers. (i.e., No Station Cange, Dual Support, etc.) Use Attacment 2 to determine priority requirements for eac PAP d support Submit PAPs prior to launc in reearsal format (Function = RPAR, RPAS). After launc tey will be in te standard format Provide a launc primary POC to 22 SOPS sceduling, wit contact pone numbers were tey can be reaced pre-launc and post-launc. It is igly recommended tat te primary POC perform any deconfliction of tis veicle wit 22 SOPS.

34 34 50SWI MAY Ensure a knowledgeable person is available for eac sift. Tis individual sould be able to answer general questions regarding te launc after ours Use MSCs to add Testing and Data Flow transfers In te event ESD is not available, submit a ard copy PAP to sceduling by any means available.

35 50SWI MAY Capter 9 DOWNTIMES 9.1. Policy. 22 SOPS is te final autority for te placement of requested downtime into te NTO. Tis capter provides direction on requesting resource downtime for maintenance and testing of, or training on, AFSCN resources Downtime. A downtime is a sceduled loss, limit, or risk of loss, of an AFSCN resource or resources An AFSCN resource will not be voluntarily removed from service witout an approved, sceduled downtime witin te NTO, or te requestor as verbal autority from 22 SOPS sceduling NCMDR/NCCH will process real time request for Depot level maintenance Network Sceduling will: Process downtime requests appropriately Notify all impacted parties of any limitations SOPS Mission Planning will: Coordinate downtime requests tat fall witin all but te realtime and conflict briefing periods Track all downtime requests Process routine requests for downtime Load all approved Modification Control Board (MCB) and properly coordinated downtimes into te seven-day forecast period Notify Network Sceduling wen all requested downtimes for a given seven-day period are loaded into tat period Conduct a weekly downtime meeting on Friday at 1600Z to discuss possible operational conflicts wit te seven-day forecast Inform all users of upcoming sceduled downtime maintenances tat impact mission requirements troug publication and distribution of te 3 mont and THURLIST reports Requesting work center will: Request downtime for any effort tat will impact or risk AFSCN resources Process: Downtime requests are submitted via ESD to te 22 SOPS NOC. Te following paragraps detail te content Downtime request information is indexed into a nine line format. A downtime request is commonly referred to as a Nine-Line Downtime requests will identify specific equipment impacted, or potentially impacted, by te intended action and clearly identify possible impacts to AFSCN users.

36 36 50SWI MAY Complete te Downtime Request (Nine-Line subject) A downtime request will be identified as one of te following. Enter te correct description into te Subject line of te Nine-Line request: Routine. A routine downtime request is used for any downtime tat falls witin or later tan te current seven-day period. Tis request is processed and tracked by 22 SOPS Mission Planning Pre-coordinated. A pre-coordinated downtime request is a follow-up to a voice autorized downtime request wereby a ard copy downtime request is still required for documentation and tracking Realtime. A realtime downtime request is used for any downtime required tat falls witin te already publised NTO. A realtime downtime request is processed by Network Sceduling Urgent. An urgent downtime request is submitted for efforts to resolve outage conditions wen te maintenance action required will furter impact AFSCN operations. Tis request is processed and tracked by 22 SOPS Mission Planning sould it fall beyond deconfliction, or by Network Sceduling if it sould fall witin te deconfliction period Line 1 - Job Number (required entry). Te tree-digit serially assigned number preceded by a letter prefix tat identifies te requesting work center. Tis downtime number appears in te NTO for a non-fligt activity in place of an IRON. A record of te tree-digit numbers used sould be maintained by te requesting work center in accordance wit locally publised procedures. Attacment 4 provides a list of downtime number prefixes. Numbers range from 001 to 999, wit 901 to 999 normally reserved for specific purposes and 001 tru 900 used sequentially as new requirements arise Line 2 - Place Work Will Be Performed (required entry). Enter UNDISCLOSED if te location is unavailable or classified Line 3 - Description/ Reason (required entry). Provide a brief description and reason for te work to be accomplised Line 4, part a - Start Time (required entry). Include date and time. Precede wit TS (Time Specific) wen te start time must remain stationary. Include any window for te downtime in te comments section below Line 4, part b - Advanced Notice (required entry). Tis is te advance notice te requesting work center requires prior to te beginning of te downtime. Typically is None Line 5 - Equipment (required entry). Identify impacted AFSCN resources. Tis information sould matc as closely as possible to te resource as it normally appears in te NTO Line 6 - Office/Contact/Extension (required entry). Te contact information for te requesting work center Line 7 - Sift/Limitation (required entry). Enter any sift limitations for wic te activity will be performed. i.e., DAYSHIFT ONLY or WEEKDAY, enter NONE wen tere is no limitation.

37 50SWI MAY Line 8, part a - Requested (required entry). Te total time requested (desired) to accomplis tis downtime activity Line 8, part b - Required (required entry). Tis is te minimum amount of time required to accomplis tis downtime. Te requested and required times normally are te same Line 8, part c Recovery (required entry). Recovery time to place te equipment into full ops capability in te event of a recall after te downtime as begun. If a downtime activity cannot be recovered prematurely after it as begun, ten te recovery time sould matc te minimum time required Line 9 - Comments (optional). Provide any furter information to assist in te sceduling of te downtime activity, suc as an applicable window or if te downtime may occur concurrent wit oter sceduled RTS activity. Any important information not already captured in te previous lines sould be ere Routine Request. Submit routine downtime requests to sceduling at least 10 days prior to downtime start time Network Sceduling will deconflict downtimes wit non-fligt and fligt activities during te deconfliction process. Approved downtimes will be publised in te NTO.

38 38 50SWI MAY 2013 Capter 10 DISA AUTHORIZED SERVICE INTERRUPTIONS Purpose. Tis capter outlines responsibilities for managing DISA Autorized Service Interruptions (ASI) and it provides a process to minimize disruption to AFSCN operations due to a DISA ASI or Demand Maintenance DISA ASI. DISA provides te majority of te communications services for te AFSCN communications network. Wenever a DISA facility as to interrupt service for maintenance or any oter activity, tey use te process of notification described in DISAC , DII Tecnical Control. Te process includes notifying te circuit actions functions of 50 SCS CFP and 21 SOPS PTF wen an ASI will impact AFSCN services Demand Maintenance. A priority maintenance activity in wic DISA may seize AFSCN communications services wit no notification to, or concurrence from, AFSCN personnel SCS TCF and 21 SOPS PTF will: Ensure DISA ASI requests tat impact AFSCN services are forwarded to 21 SOPS comm control Ensure AFSCN concur/non-concur for an ASI reaces appropriate requesting DISA facility Ensure 21 SOPS comm control receives notification of any conflict wit a nonconcur response Develop local procedures in coordination wit 21 SOPS comm control and 22 SOPS NOC to ensure efficient and timely execution of tese requirements Investigate and resolve any failure to be notified of an ASI tat impacts AFSCN services SOPS Comm Control will: Determine ASI impact to AFSCN resources and submit an appropriate downtime request to 22 SOPS NOC Ensure 50 SCS and 21 SOPS Circuit Actions receive te concur/non-concur from 22 SOPS NOC Notify 22 SOPS sould DISA still plan on disrupting AFSCN services even after tey receive AFSCN non-concurrence for te ASI Submit outage reports wen communications links are seized or oterwise removed from service un-expectedly, resulting in disruption to AFSCN operations Develop local procedures in coordination wit 50 SCS Circuit Actions, 21 SOPS Circuit Actions, and 22 SOPS NOC to ensure efficient and timely execution of tese requirements.

39 50SWI MAY SOPS NOC will: Determine concur/non-concur IAW wit downtime procedures in Capter 9 of tis instruction Provide concur/non-concur to 21 SOPS comm control Manage IAW capters above a eads-up notification tat DISA still plans on disrupting AFSCN services even after receiving an AFSCN non-concurrence Develop local procedures in coordination wit 21 SOPS comm control to ensure efficient and timely execution of tese requirements Procedures. 50 SCS CFP, 21 SOPS PTF, 21 SOPS comm control, and 22 SOPS NOC will develop local procedures to meet te responsibilities as directed above. In addition to responsibilities stated above, local procedures will include: Appointed individuals acting as primary POC for andling an ASI Contact numbers for eac primary POC and supporting work center A process to investigate, and correct wen possible, any failure to coordinate an ASI, wile mitigating future risk.

40 40 50SWI MAY 2013 Capter 11 VOICE OPERATIONS Purpose. Tis capter establises a single primary source of standard voice procedures for conducting satellite operations witin te AFSCN community. Te AFSCN utilizes multiple voice switcing systems to support operational voice requirements and to provide redundancy Defense Red Switc Network (DRSN). DRSN is a DoD asset providing secure voice services to various DoD and federal agencies. Te AFSCN utilizes te DRSN switces at SAFB and VAFB to support satellite operations Integrated Services Telepone (IST). An IST is te primary end instrument for access to DRSN. Te IST may be used to provide access to bot secure DRSN services and non-secure local base telepone services if te supporting infrastructure is in place and properly configured. ISTs located at te RTSs are configured to provide DRSN services to te SAFB DRSN switc and to te VAFB DRSN switc PRI Secure Voice (PSV). PSV is te secure voice capability of an RTS. Te conveyance for te secure voice wit a RTS is provided by static connections terminating at te RTS PRI WANIU. RTS secure voice capability wit SAFB and wit VAFB are treated as two separate resources in te NTO Satellite Secure Voice Net. Te secure voice services provided in support of AFSCN operations includes dedicated conferences for eac RGF site and side. Attacment 5 provides details for accessing tese nets SAFB SVO and VAFB SVO can connect secure calls to any of te RTS nets or to an RTS IST extension troug SAFB PSV or VAFB PSV SAFB SVO merges IST net buttons for AFSCN users at SAFB wit specific site and side based on te NTO. Tis prevents users from accessing te same site and side operational nets simultaneously witout prior coordination Some AFSCN work centers, suc as 21 SOPS comm control, ave continuous access to all RTS nets. Continuous access to RTS nets is restricted to tose work centers wit proper approval Defense Switc Network (DSN). DSN is a DoD asset providing inter-base non-secure voice telepone services Private Branc Excange (PBX). AFSCN facilities are located on federal or military installations and ave access to te local base PBX for non-secure voice services. Te local base PBX provides AFSCN operational areas and work centers wit access to bot DSN and commercial telepone networks Tie-line. A tie-line is a dial-up trunk between two PBXs. A caller dialing a tie-line s access number will get te dial tone of te remote PBX and be able to dial a number as if te caller was on a local telepone at tat remote location. Access restrictions can be assigned to a tie-line to prevent abuse.

41 50SWI MAY Bot SAFB and VAFB ave tie-lines establised between teir local base PBX and most of te RGFs. Te conveyance for tese tie-lines is provided by static connections terminating at one of te RTS WANIUs. Tese tie-lines are not sceduled resources and outage conditions for tese tie-lines are not reported Conference Bridge. A conference bridge provides a way for various parties to all dial into an establised telepone conference, given a dial-in number for te bridge and a code for accessing te conference Bot SAFB and VAFB ave base conference bridges on wic ave been preestablised and dedicated conferences, also referred to as meet-me-nets (MMN), for eac RGF site and side. Bot te SAFB and VAFB bridges ave te additional capability of blast dialing, calling a pre-establised number wen a command code is entered by a participant wo as moderator privileges for te conference call. Te RGF MMN blast dials te appropriate RGF operational area. Attacment 7 provides details. Note: Generally, te MMNs blast dial a DSN number. If tere is loss of DSN capability at eiter location, te blast dial will fail Te Tec Net and backup Tec Net are also dedicated conferences establised on te VAFB and SAFB conference bridges and are configured to blast dial 21 SOPS comm control AFSCN Voice Operations. Te primary metod for supporting operations wit a RGF is by using PSV. If an AFSCN user does not ave access to PSV, or PSV is unavailable due to a downtime or outage condition, te user may instead use a MMN. If a MMN is not viable or oterwise unavailable, a user may dial te site directly using oter non-secure voice (NSV) means, suc as DSN, commercial networks, or a tie-line. Attacments 7 and 8 provide furter details A user requiring secure voice communications, were PSV is not available, may dial direct using Secure Telepone Equipment (STE) to secure te call. Attacment 7 provides furter details. Note: All operational and support areas are responsible for meeting OPSEC and COMSEC requirements AFSCN user will: Establis voice communications wit all required parties Determine and use te existing AFSCN voice metod tat best meets teir operational and security requirements Use te proper terminology IAW Attacment 9, AFSCN Common Operations Terminology Lexicon Immediately notify 50 NOG CFP of any detected faults SAFB Secure Voice Operations (SVO) will: Provide assistance connecting callers securely wit AFSCN operational areas and work centers Maintain an up-to-date directory of AFSCN operational areas and work centers connected to te SAFB DRSN switc.

42 42 50SWI MAY Assist 21 SOPS comm control wit fault detection, fault isolation, and fault resolution Operate and maintain secure voice recordings of operational nets Perform playbacks of secure voice recordings for cleared individuals VAFB Secure Voice Operations (SVO) will: Provide assistance connecting callers securely wit AFSCN operational areas and work centers Maintain an up-to-date directory of AFSCN operational areas and work centers connected to te VAFB DRSN switc Assist in 21 SOPS comm control wit fault detection, fault isolation, and fault resolution Operate and maintain secure voice recordings of operational nets Perform playbacks of secure voice recordings for cleared individuals SOPS comm control will report and resolve any PSV outage conditions IAW 50SWI Secure Voice Operations. Wen personnel are going to discuss classified information, all parties must prepare for secure communications. Do not discuss classified information until ALL individuals on te net ave acknowledged teir area as secured for classified discussion Individuals about to initiate a classified conversation will inform everyone on te net All parties on te net will acknowledge and advise if teir area is secure or not Wen a classified discussion is at an end, all parties will acknowledge te end of classified discussion Prepass Briefing. Use of proper terminology is important to ensure all parties understand briefings, directions, and status. Reference attacment 9 for common terminology use. Satellite operators will clearly brief all information required to support a satellite contact and any subsequent playback activities prior to te beginning of te pass. Te tempo must be slow enoug so te briefing can be fully understood and acknowledged by all parties and properly transcribed by te RTS operator. Te SOC operator will confirm all information read back from te RTS operator is correct. Te following information will be briefed and requested in te following cronological order as applicable to te satellite operator: Te satellite operator will: Ask te RTS for a brief of any new problems tat occurred during te previous satellite contacts not already sown in ESD Brief te classification and sceduled satellite contact times Request station status, system time, and RTS operator s name. A satellite operator sould be aware of any outages conditions tat may affect te support and cange te prepass brief.

43 50SWI MAY Brief Command/Control/Status (C/C/S) and telemetry routing. Te satellite operator will include te WANIU telemetry cannel designation and data rate for eac expected telemetry stream, and te PRI and ADD routing of C/C/S and telemetry. WANIU telemetry cannels are designated as TLM-1 troug TLM-5 or Telemetry-1 troug Telemetry Brief exact IRON configuration ID wic consists of a 4-digit IRON number followed by alpanumerical identifiers Brief required non-standard equipment configurations. Non-standard includes any configuration canges tat ave to be made to te equipment after loading te IRON configuration ID into ARTS or RTS Block Cange (RBC) and all patcing requirements Brief space veicle acquisition time, acquisition azimut antenna angle, and acquisition elevation antenna angle Brief expected downlink signal strengt, especially if tere is a difference between normal and expected values due to a known or suspected anomaly Brief mid-pass time, mid-azimut antenna angle, maximum elevation antenna angle, and two-axis antenna keyole instructions, if keyole is expected Brief fade time, fade-azimut antenna angle, and fade-elevation antenna angle Brief te RBC Operator to manually offset te tird axis or enter Acquisition of Signal (AOS) and Loss of Signal (LOS) parameters if a TLE is not available. Brief all acquisition, mid-pass, and fade azimut and elevation angles to use AOS/LOS parameters to offset te tird axis Brief ARTS Automatic Main Beam Acquisition (AMBA) parameters, if required, to include acquisition azimut and elevation rates Brief transmitter active and uplink modulation enable instructions to include uplink power and cannel Brief downlink carrier programmed turn-on and turn-off times Brief approximate expected range number in nautical miles Brief loss of communications procedures, as appears in Attacment Brief ARTS/ RBC telemetry recording disposition not covered by or wen deviating from te OD Request prepass read back and any questions or comments, to include confirmation of soft or ard antenna obscura RTS operator will, time permitting or upon satellite operator request: Provide station status to include problems and outages, system time, and operator s name Read back te briefing.

44 44 50SWI MAY Read back te five to seven caracter IRON configuration exactly as it appears in te ARTS PASS ID field or as it appears on te RBC Contact Scedule Execution (CSE) GUI Make any required modifications or canges to te equipment configuration during te appropriate periods and ten read back tose canges as tey appear on te appropriate ARTS or RBC displays Read back te actual TLE number in use and time offset entered, if TLE is available Read back te actual satellite contact start time as displayed Prepass Cecks. Command, telemetry, and antenna pointing tests will be performed wen sufficient time is available to test signal routing and mission equipment Command Test. Te RTS operator will report wen command tones are active and any anomalous conditions suc as eco ceck errors or Control and Status (C&S) alarms Telemetry Test. Te RTS operator will report wen a telemetry test directive is received and confirm bit syncronizer lock on te appropriate telemetry streams. Te satellite operator will confirm WANIU cannel lock on te appropriate telemetry streams Antenna Pointing (Slave Bus) Test. Te RTS operator will report wen a C/C/S slave bus is received and te antenna is at te briefed point of acquisition. Te RTS operator will advise te satellite operator of any differences between te briefed and actual point of acquisition Te satellite operator will report all prepass test results to te RTS operator Satellite Contact. Te following details te responsibilities and procedures during a satellite contact Te RTS operator will: Report te time te transmitter active directive was received and visually confirms te transmitter is active, i.e. transmitting to te antenna instead of dummy load Enable te uplink modulation, as briefed by te satellite operator, confirm on system summary screen uplink modulation is enabled, and report te time uplink modulation was enabled Confirm good auto-track status and report acquisition signal strengt Report range acquisition time and confirm range value Monitor all equipment for proper status and report any anomalies Report telemetry events, as briefed by te satellite operator During ig elevation space veicle contacts utilizing a two-axis antenna, take te appropriate steps to minimize data loss by following te briefed keyole procedure or briefed loss of voice contingency procedures (keyole not briefed). Report loss and reacquisition of downlink signal Report wen te transmitter goes passive.

45 50SWI MAY Report loss of downlink signal at fade, as appropriate Brief any new problems discovered during te satellite contact immediately. It is critical tat all parties accurately and clearly report symptoms, provide recommendations for problem resolution, and coordinate teir actions. Problem resolution for satellite contacts will be directed by te satellite operator Wen a problem is encountered during te support te satellite operator will: Ask all parties to standby and take no action because any problem resolution activity could cause adverse mission impact or; Take full control of te problem resolution process or; Ask tat eac party attempt to locally resolve and report actions taken Post-Pass. Te following details te responsibilities and procedures after fading from a satellite contact Satellite operator will direct space veicle termination or ensure contact is automatically terminated at te sceduled stop time Te satellite operator will inform all parties wen te satellite contact is over, wat resources are no longer required, and tat reconfiguration for te next satellite contact can take place NLT 30 seconds after end of te sceduled satellite contact period te satellite operator will brief any playback requirement and inform all parties of any problems and scoring (successful, marginal, failed, or lost) All sceduled resources will be de-configured unless te same SOC is immediately sceduled as te next RTS support. Te Satellite operator will send a disconnect directive to allow te RTS operator to accurately report a good connection on te following support after receiving a SARM Te RTS operator will verbally remind te satellite operator to disconnect te ARTS or RBC resource, if tey fail to drop Emergency Satellite Contacts. Any satellite operator declaring a veicle emergency must contact 22 SOPS Network Sceduling and inform tem of te situation and requirements. 22 SOPS must resolve te declared emergency based on priority, and ten verbally contact all parties involved. If resources are currently in support, 22 SOPS will be added to te voice nets used to support te satellite contact Request for Satellite Contacts Not Sown in te NTO. If a satellite operator calls for a satellite contact not sown in te NTO, te RTS operator will: Inform te satellite operator te satellite contact is not listed in te NTO Query te oter parties on te voice net to determine if te satellite contact is sown on a different scedule Ask te satellite operator to immediately contact 22 SOPS Network Sceduling or add Network Sceduling to te voice net. Adding Network Sceduling to te voice net ensures all parties are properly informed of te outcome.

46 46 50SWI MAY Inform te satellite operator ow muc time is available before te anticipated roll call for te next sceduled satellite contact If tere is no impact to sceduled operations, initialize te satellite contact for te requested satellite wile waiting for Network Sceduling response. Do not go active witout Network Sceduling approval Contingency Operations. If at any time an operational area must evacuate teir operations area, tey must contact 22 SOPS Network Sceduling and provide teir new pone numbers as soon as possible If 22 SOPS Network Sceduling must evacuate teir operations area, tey will contact all operational areas and provide alternate contact information Voice Communication Failures. A failure to establis voice connectivity, or te loss of voice communications during a satellite contact, may impact a satellite operator s ability to successfully support a mission. Severity depends upon te cause and available contingency procedures. Attacment 8 details voice operations contingencies Alternate voice communications must be establised regardless of operational contingencies for te following: Incorrect IRON configuration listed in te NTO Mission impact of an outage condition is unclear and RTS clarification is required RTS is not provided wit adequate voice communication failure procedures. It is te responsibility of eac satellite operator to ensure te RTS operator understands wat coordinated actions to take during a voice communication failure Set Asyncronous Response Mode (SARM) coordination required. Te satellite operator must verbally coordinate a SARM wit te RTS operator before sending unless te voice communication failure procedure allows for an autonomous SARM at ETA minus 5 minutes SARM failure Improper RTS status received. After sending a SARM and establising a link, te satellite operator sould monitor critical RTS status to ensure te antenna is at te proper point-of-acquisition, Radiation Warning System (RWS) as timed out and transmitter is active, good auto-track as occurred, and valid range is acquired Equipment failure detected Prepass testing required Communication failure procedures state transmitter active is done by satellite operator direction only Communication failure procedures state enabling uplink modulation is done by satellite operator direction only Critical RTS event verification required Support terminated early or support period extended.

47 50SWI MAY Negative Voice Communications. If te satellite operator as not contacted te RTS by te normal start of prepass tests or by ETA minus 5 minutes (wicever occurs first), te RTS operator will follow te negative voice communications procedure provided by te applicable program OD. Te RTS operator will ceck if primary voice is operational and contact 22 SOPS Network Operations sceduling to determine if te satellite contact was deleted. See attacment 8 for furter details Procedures Common to All Loss of Communications Situations. Te satellite operator as te responsibility to ensure voice contact is establised or adequate procedures are available for continued support for any voice communication problems. See Attacment 8 for furter details.

48 48 50SWI MAY 2013 Capter 12 RTS IRON DATABASE CHANGE PROCESS Purpose. Tis process describes ow a user submits RTS configuration requirements into te IRON Database Office (IDO) for incorporation into bot te ARTS and RBC ground systems. It also describes te validation process in order to ensure accurate and timely implementation of IRON databases to meet users requirements Procedures: Process Flow. Te overall IRON database cange process can be seen in Figure 12.2 wic illustrates te responsibilities of te five different organizations (User, IDO, 22 SOPS MAF, 22 SOPS/MI and te RTS Operations Teams at BOSS and/or COOK) IRON Database Cange Request (IDCR) Input. Users and 22 SOPS/Mission Integration (MI) generate IDCR forms utilizing current version of te QUICK or RAPID Tools, downloadable from Web Based Data Analysis Repository (WeB DARt). (ttps://webdart.scriever.af.mil/webdart/common/main.jsp) RTS All Parameter IRON Data (RAPID) and Question User s IRON Configuration Knowledge (QUICK) Tools. RAPID and QUICK are desktop computer tools tat allow users to create accurate IRON Database Cange Requests (IDCRs), verify canges made witin eac IRON database delivery and manage RTS Telemetry, Tracking and Commanding (TT&C) parameters. Users and support agencies are encouraged to download tese tools from te access controlled WeB DARt site: ttps://webdart.scriever.af.mil/webdart/common/main.jsp User generates and sends IDCR to MI (22sopsmsnint@scriever.af.mil) via attacment for tecnical review. MI will validate information prior to submitting to te IDO (DLCO22IRONDB@Honeywell.com) via as an autorized IDCR OPSEC. All content in te IDCR will be kept at te unclassified level. Te only reference to te satellite or booster being supported will be te four digit IRON(s) pre-assigned to te user(s) by 22 SOPS/MAF. No details about upcoming launces or critical mission events are to be included on te form. Te Need Date is te only Need to Know information required on te form Need Date. Te IDCR form includes a space for a user-defined need date. Te user specifies te date te new or modified configuration is required at te RTS(s) in order to support an activity. If no specific need date is required ten te word Routine will be entered in tis space, wit te understanding te requested configuration(s) will be available at te RTS witin six monts of submittal. Typically all IDCRs sould be implemented and available at te RTSs witin 60 days of submission. On rare occasions, tis process time may be compressed to meet unforeseen mission requirements wit a Quick Turn submission. Quick Turn submissions sould be kept to a minimum due to te large amount of time and resources needed to fulfill tese requests. Users must plan for configuration contingencies, utilize te temporary build and save capability at te ARTS sites and make real-time parameter canges wit RBC sites werever possible in order to keep Quick Turn requests to a minimum.

49 50SWI MAY MI Initial Review. MI conducts an initial tecnical review of te IDCR prior to submittal to te IDO. Tis will include a Need Date validation wit te User if te IDCR is considered a Quick Turn. MI will evaluate and modify te IDCR wen required, wit te user s concurrence prior to IDO submittal. Tis may include signal quality, operational improvements, and/or adding oter IRONs owned by users requiring te same canges IDO Receives te IDCR, builds, tests, and delivers te release package for review. Figure RTS IRON Database Cange Process Flowcart