10-601

BY ORDER OF THE COMMANDER

50TH SPACE WING INSTRUCTION 10-601

15 February 1995

Operations

MANAGEMENT AND CONTROL OF RESOURCE CONFIGURATION FREEZE

This instruction implements policy set forth in AFPD 10-6, Mission Needs and Operational Requirements. It establishes procedures and individual responsibilities for requesting, implementing, and lifting configuration freezes. It applies to all personnel assigned or attached to units conducting 50 SW operations and using resources currently under the control of 50 SW and the Air Force Satellite Control Network (AFSCN).

_________________________________________________________________________________

Certified By: 50 SW/CC (Colonel Simon P. Worden)

OPR: (50 OSS/OSP) TSgt Mark E. Bedell

Pages: 5/Distribution: F

1. General. This instruction sets common guidelines for declaring, requesting and implementing configuration freezes and requesting waivers. Configuration freezes are imposed to minimize the risk to Launch and Early Orbit (LEO) activities and other periods of critical operations. Last minute changes could adversely affect existing capabilities and impact mission readiness. There are three types of freezes: Satellite Operations Center (SOC), Base, and AFSCN-CUE. Note: All references to the unit/CC will include the Commander or a designated representative of the organization with mission success responsibility. Civilian organizations will go through Air Force representatives to initiate freezes. All references to SOC include: module, room, and Mission Control Center (MCC).

2. Definitions. See attachment 1 for a listing of terms used in this instruction.

3. Responsibilities:

3.1. The Unit/CC with mission success responsibility:

3.1.1. Chairs or designates a representative to chair the Modification Control Board (MCB) in accordance with 50 SWI 21-102.

3.1.2. Declares the start and end dates and times (ZULU) for all levels of configuration freezes.

3.1.3. Reviews all freeze waiver requests and recommends approval or disapproval prior to submission to the Group/CC for final approval.

3.1.4. For launch purposes, freezes the SOC. A letter indicating the dates of the SOC freeze and the request dates for a base and AFSCN freeze are sent to the 50 OG/CC for approval and an info copy to 50 OSS/OSPC (see figure 1).

3.2. 50 OG/CC:

3.2.1. Is the freeze authority for all 50 OG assets. When a freeze is requested, directs all requested assets, under the 50 OG, to implement the freeze (see figure 1).

3.2.2. When the request is from a unit in the 50 OG, requests that the 50 SUG/CC, the 750 SG/CC, and the 50 LG/CC freeze those assets that will be needed on the dates and times indicated on the freeze request letter.

3.3. 50 LG/CC. When a freeze is requested, directs the 50 MXS and the 50 LSS to implement their portion of the freeze as appropriate.

3.4. Integration Management Flight (SCT). Is responsible for insuring that any proposed activities presented at the Daily Deconfliction Meeting (DDM) and the Utilities Outage Meeting (UOM) do not affect frozen assets. If so, the activities should be rescheduled or the agency wanting to perform the activity should request a waiver. The SCT ensures that freezes are reflected in the AFSCN Resource Schedule.

3.5. 750 SG/CC. Is the freeze authority for all 750 SG assets. When a freeze is requested, directs the 750 OSS/CC to implement the AFSCN-CUE freeze. The 750 OSS/CC takes all necessary actions to initiate a freeze of the affected 750th agencies (see figure 2)

3.6. 750 OSS/DOP:

3.6.1 Reviews scheduled activities at AFSCN-CUE locations and determines if activities have a possible impact on launch readiness. If so, the activities are rescheduled or the agency performing the activity is directed to request a waiver. Reviews and coordinates all waiver requests, provides assessment and recommendations to 750 SG/CC and the unit/CC requesting the freeze.

3.6.2. Releases freeze of affected 750th agencies on the termination date provided by the unit/CC who initiated the freeze. The release of one freeze does not affect a freeze imposed by other agencies for other reasons.

3.7. 50 SUG/CC. Is the freeze authority for all support assets needed for a freeze. When a freeze is requested, the 50 SUG/CC directs the 50 CES and the 50 MSSQ to freeze any assets necessary to support the freeze.

4. Freeze and Freeze Release Procedures:

4.1. Duration:

4.1.1. SOC Freeze.Should be implemented NLT 24 hours prior to the dress rehearsal, and continue until all LEO operations have been completed. In the event that no dress rehearsal is accomplished, the SOC shall be frozen NLT 7 days prior to launch. After the dress rehearsal, but prior to the base freeze implementation, configuration changes require the approval of the freezing agency.

4.1.2. Base Freeze.In general, the freeze should begin 5 days prior to launch and extend until LEO activities are complete. However, each mission has different requirements and the timeframe for the freeze should be based on the needs of the mission.

4.1.3. AFSCN-CUE Freeze.An AFSCN-CUE freeze in support of LEO activities will begin at L-48 hours or earlier if necessary. The freeze will continue until L+1 days as a minimum, but the actual date/time for the end of the freeze should be based on mission needs as determined by the unit/CC who initiated the freeze. Those AFSCN-CUE assets that are considered to be critical by the program office or "GO/NO-GO" criteria for launch, may be frozen for an additional 48 hours prior to the launch. The freeze does not include activities such as, Preventative Maintenance and Inspection (PMI) and/or Operations and Maintenance (O&M) training, maintenance not requiring a change to the normal physical or operational configuration, and maintenance involving safety of equipment or personnel. Any maintenance or facility activities which, in the judgment of the 750 SG commander, create a reasonable risk of preventing the site from supporting critical operations will be included.

4.2. Freeze implementation:

4.2.1. Freeze Request Letter. The unit/CC requiring the freeze (originator) writes a letter (see attachment 2) requesting their respective group/CC implement the group's portion of the freeze and requests a freeze from the other group/CC's. The letter includes the primary node and the backup node (if required). Units who maintain operational control of assets needed for the freeze decide which assets under their control will be frozen for mission accomplishment. The unit/CC info copies the 50 OSS/CC. The request must be made NLT 14 days prior to the freeze implementation date. The letter should include:

4.2.1.1. Date/time (ZULU) of the start and end for each level of freeze (SOC, Base, AFSCN-CUE).

4.2.1.2. Purpose of the freeze.

4.2.1.3. POC for processing freeze waivers and questions.

4.2.2. SOC Freeze Implementation.For SOC and dual SOC operations, the unit/CC with primary responsibility for the overall mission initiates the freeze. The freeze includes those assets deemed critical for mission success located at both the primary and the backup SOC. Freeze requests are briefed to the MCB for evaluation and approved or disapproved.

4.2.3. Base Freeze Implementation. Since a unit requiring a base freeze may be a tenant unit on a base not under the control of HQ AFSPC, freeze implementation for the base will be different depending on the base where the unit is located.

4.2.3.1. 50th OG.Units assigned to the 50 OG use the following procedures. The unit/CC presents freeze requirements to the 50 OG/CC NLT 14 days prior to the freeze request date. This request can be done on the same letter as the SOC freeze. The 50 OG/CC requests that the 50 LG/CC, the 750 SG/CC, and the 50 SUG/CC implement their portion of the freeze. They then coordinate with their respective units to implement the freeze (see figure 1). Note: 5 and 6 SOPS, while geographically separated from Falcon AFB, follow the freeze process shown in figure 1.

4.2.3.2. 750th Group. Units assigned to the 750 SG use the following procedures. The unit/CC presents freeze requirements to the 750 SG/CC NLT 14 days prior to the freeze request date. This request can be done on the same letter as the unit freeze. The 750 SG/CC implements the freeze through the 750 OSS/CC, who coordinates with the base agencies concerned with the freeze (see figure 2).

4.2.3.3. Tenant units.These are units assigned to 50 SW but are located on a base not under the control of 50 SW. They are also defined as units not under the control of 50 SW that are located on a base that is under the control of 50 SW. A freeze can't be imposed on a base or unit that is not under the control of 50 SW. It is up to the unit or base to use any available agreements to prevent changes to any resources that could impact the mission.

4.2.4. AFSCN-CUE Freeze Implementation.The 750 OSS/CC coordinates all AFSCN-CUE resources needed to support the freeze and with the 750 SG/CC for freeze approval. 750 OSS/CC implements the freeze by issuing an AFSCN-CUE freeze message (see attachment 3) to the AFSCN community NLT 24 hours prior to freeze initiation. A copy of the message is sent to the 50 OG/CC and 50 OSS/CC.

4.3. Freeze waivers. If work/maintenance is requested on a frozen asset, a waiver is required by the requesting agency (see attachment 4). Database changes that are provided to the backup node by the primary node should not need to be waivered as it is the responsibility of the primary node to insure the operability of the files. Ideally, the agency performing the work and the unit where the work will be performed coordinate a date and time that meets both of their needs. When a freeze is imposed, it can affect assets not under the operational control of the unit/CC who initiated the freeze. As such, all waiver requests must be reviewed by the unit/CC(s) that requested the freeze to ensure that no action is taken that could directly impact current operations. Once the unit/CC freeze originator approves the waiver request, the waiver is forwarded to the group/CC of the unit that owns the equipment for final approval. For example: AT&T wants to perform work on equipment that is owned by the Communications Squadron. The equipment to be worked on was frozen by request of the 1 SOPS/CC (freeze originator). A waiver is required before this work can be accomplished. AT&T and the Communications Squadron must work out a date and time when they can both support the needed work. 1 SOPS is informed that work on equipment under their freeze is being requested. If 1 SOPS doesn't see any operational impact, then the request is forwarded to the 50 OG/CC (the group/CC for the COMM Squadron) for signature. Otherwise, AT&T and the Communications Squadron should work out a different date and time that will not conflict with 1 SOPS operational needs. The revised freeze waiver process is then restarted as shown in figure 3.

4.3.1. Maintenance is not included in AFSCN-CUE freeze. During the day of the launch, maintenance activities will be curtailed in order to assure all necessary assets will be available to support operations.

4.4. Freeze Release:

4.4.1. The unit/CC should identify the expected termination date of each freeze in the freeze request letter. If there is a change to any release date, the unit/CC must send a letter indicating the change through the proper channels depending on what group they are in as shown in figure 1 or figure 2. This change should be done as soon as possible in order to allow for efficient rescheduling of activities.

4.4.2. The SCT ensures that the freeze release dates as specified by the operations community are reflected in the schedules.

4.4.3. 750 SG/CC ensures all AFSCN-CUE assets are released from a freeze. More than one freeze can apply to a single resource and for that reason the release of one freeze on a single resource does not release that resource from any other freeze restrictions.

SIMON P. WORDEN

Colonel, USAF

Commander

4 Attachments:

1. Definition of Terms

2. Sample Freeze Letter

3. Sample Freeze Message

4. Freeze Waiver Request

Attachment 1

DEFINITION OF TERMS

A1.1. AFSCN Resource Schedule. Daily schedule of approved non-flight AFSCN activities.

A1.2. Air Force Satellite Control Network (AFSCN). A global, inter-command configuration of space vehicle command, control, and communications resources operating in concert to support Department of Defense and other assigned space missions.

A1.2.1. Common User Element (CUE).AFSCN resources shared by everyone who uses the network. The CUE is comprised of communications, Remote Tracking Station antennas and both Resource Control Center scheduling nodes. Systems include:

A1.2.1.1. Automated Remote Tracking Stations (ARTS).

A1.2.1.2. Command and Control System (CCS).

A1.2.1.3. Communication System (CS).

A1.2.1.4. Remote Tracking Stations (RTS).

A1.2.1.5. Resource Control Center (RCC).

A1.2.2. Dedicated System.A dedicated system supports one specific space program.

A1.2.3. Satellite Systems/Programs. The following systems are currently under operational control of the

50 SW:

A1.2.3.1. Defense Meteorological Satellite Program (DMSP).

A1.2.3.2. Defense Satellite Communications System (DSCS).

A1.2.3.3. Defense Support Program (DSP).

A1.2.3.4. Fleet Satellite Communications (FLTSATCOM).

A1.2.3.5. Global Positioning System (GPS).

A1.2.3.6. Milstar Mission Control Segment (Milstar MCS).

A1.2.3.7. Ultra High Frequency Follow-On (UFO).

A1.3. Critical Operations. All operations deemed critical to LEO of a satellite program, operations deemed critical to national security or national defense, operations necessary to stabilize the health of a satellite in order to prevent its loss, or where a change in configuration could have serious consequences to current operations.

A1.4. Daily Deconfliction Meeting. Allows Falcon AFB operations community to review all proposed activities prior to inclusion on the module resource schedule and the AFSCN resource schedule. Coordinates and schedules access to modules for both interference and non-interference actions. This meeting is the primary method for all FAFB users to obtain information concerning activities and freeze schedules.

A1.5. Freeze. A hold put on all configuration changes to the specified system of databases, hardware, software, communications, and ceiling/under-floor activities, and all base utilities required for operations. This includes all work for Engineering Change Proposals (ECP), Temporary Configuration Changes (TCC), Test Case Modifications (TCM), and facility work. Database files necessary for daily on-orbit operations (e.g., schedule records, Contact Support Plans (CSP), Vehicle Ephemeris Identifications (VEID), etc.) are excluded. Corrective maintenance to hardware or communications equipment that is critical to mission success, is considered exempt from the freeze waiver process. Freeze requests are generated by the unit that requires the freeze and approved by the unit's MCB prior to coordination throughout the wing, as shown in figure 3.

A1.5.1. AFSCN-CUE Freeze.The Air Force Satellite Control Network Common User Element (AFSCN-CUE), are resources that are used by many organizations. The length of time these resources remain frozen should be kept to a minimum. As with a base freeze, a general or detailed list (if known) should be included with the request and the agencies that maintain operational control over those assets ensures the proper equipment is put into a freeze condition. These assets may be comprised of, but are not limited to:

A1.5.1.1. Resource Control Complex at Falcon (22 SOPS) and Onizuka (21 SOPS).

A1.5.1.2. The 750 SG Dets 1-6, 8, 22 SOPS/DOC, 23 SOPS and the OL-AE.

A1.5.1.3. The communications system required for launch, both at the primary and the alternate node.

A1.5.2. Base Freeze.Many of the assets considered under a base freeze may need to be frozen at different times and for different lengths of times. It will not always be necessary to freeze all the assets at the same time, and certain assets may need to remain frozen while others are released. When a base freeze is requested a general or detailed list of the resources that need to be frozen should be included in the letter. Agencies maintaining operational control of those assets are to determine the exact resources needed for the launch and ensure those assets are frozen. These assets may be comprised of, but are not limited to:

A1.5.2.1. Base communications systems used by the launching program.

A1.5.2.2. Base utilities (Power, HVAC, etc).

A1.5.2.3. Activities that could have an impact on operations.

A1.5.3. SOC Freeze.The SOC including the primary node and any assets deemed critical for mission success located at the backup nodes.

A1.6. Freeze Release. The removal of all restrictions imposed by a freeze. The date and time (ZULU) of the freeze release shall be included with the letter/message that initiated the freeze with the understanding that at any time prior to that date and time the freeze release can be changed. The change of date and time can be done verbally but requires a follow up letter/message. If no change to the original date is received, then the freeze is automatically released on that date.

A1.7. Freeze Waiver. A letter or waiver request form developed by the unit allowing changes to be performed on assets that are frozen. All waiver requests are considered on an individual basis. Waivers must be coordinated with the agency/unit that originally requested the freeze.

A1.8. Module Resource Schedule. Daily schedule of approved non-flight module activity. All activities that have the potential to impact mission hardware availability must be on the module resource schedule.

A1.9. Preventive Maintenance Inspection (PMI). This is work that is normally performed at the unit level, and can include a wide range of activities. The unit performing these PMIs should make the decision as to which activities are performed without the need for a waiver; which require a waiver; and which should be delayed until after the freeze. In the event that it cannot be determined if a PMI has an impact on the operational mission, a waiver is required. A PMI is normally not maintenance that must be done immediately but can be put off to a more convenient time in the future.

A1.10.Corrective Maintenance. Corrective maintenance is performed on equipment that is in need of immediate repair, or posses a safety or health hazard.

A1.11. SOC. Includes all equipment maintained at the squadron level, to include main system computers, consoles, under floor, above roof, SVS (Internet), etc..

A1.12. Utility Outage Meeting. Weekly meeting that allows the operations community to review all proposed utility outages. Attendees agree on impact and how community should cope with the outage prior to activities being put on the Utility Outage Schedule.

A1.13. Utility Outage Schedule. Daily schedule of approved utility outages.

A1.14. Waiver Request. A request to perform a certain activity on equipment that has been frozen. The request states the activities to be performed, equipment involved, risk to the mission, when the work is to start, and how long it will take to be completed. Before a freeze waiver is granted, the request must be approved by the Group Commander of the organization that owns the equipment.

Attachment 2

SAMPLE FREEZE LETTER

MEMORANDUM FOR 50 OG/CC 50 OSS/OSP 50 LSS/SCT DET 5/SMC 50 LSS/SCO 50 CES/CC

FROM: 1 SOPS/XP

400 O'Malley Ave, Ste 35

Falcon AFB CO 80912-4035

SUBJECT: SOC-31 Launch Freeze

1. The launch freeze will commence at 0000Z on 12 Aug 94 for SOC-31 (MODs 10 and 16) to support the DMSP F-12 LEO.

2. The freeze affects all hardware, software, and database configuration changes that must have MCB approval. Any facility work requiring entry under the floor or above the ceiling is also affected by this freeze. Excluded from this freeze are OA interoperability database transfers between SOC-31A and SOC-31B, and NSS tool changes.

3. A letter will be issued terminating this freeze at the appropriate time. Any questions should be directed to the undersigned at extension 7-5543.

CHRISTOPHER R. THORNTON, GM-13

Special Assistant to the Commander

cc: 1 SOPS/CC

/DO

/DOG

/DOV

/DOA

/SC

Attachment 3

SAMPLE FREEZE MESSAGE

UNCLASSIFIED

01 02 261432Z AUG 94 RR UUUU ZYUW DOP 260732L

NO

750SGP ONIZUKA AFB CA//CC//

AIG 10553

UNCLAS FOUO OPS MSG

QQQQ

SUBJ: NETWORK CONFIGURATION FREEZE

1. EFFECTIVE 27/0002Z AUG 94, A NETWORK FREEZE ON COMMON USER ELEMENTS OF THE AFSCN AS INDICATED IN PARAGRAPH 4 IS IMPOSED.

2. FREEZE IS IMPOSED ON ANY CONFIGURATION CHANGES OR MODIFICATIONS INCLUDING ECP'S, TCM'S, AND TCC'S.

3. THIS FREEZE MESSAGE SUPERSEDES ALL PREVIOUS FREEZE MESSAGES.

4. AFSCN RESOURCES AFFECTED:

VTS-A: YES VTS-B: YES

NHS-A: YES NHS-B: YES

TTS-A: NO TTS-B: YES TTS-C: YES

IOS-A: YES

GTS-A: YES GTS-B: YES

HTS-A: YES HTS-B: YES

CTS-A: YES

TCS-A: YES TCS-B: YES

DGS-A: YES

MELISSA BUTLER, A1C

750 OSS/DOP, X4111

PHILLIP O. BAER, GS-12, DOP, 4087

CRC: 17764

UNCLASSIFIED

UNCLASSIFIED

02 02 261432Z AUG 94 RR UUUU ZYUW DOP 260732L

NO

EVCF: YES

OAFB: YES SEE PARA 6A & 6B

FAFB: YES

5. EXEMPTIONS: NONE.

6. REMARKS: A. NO OAS POWER PLANT MAINTENANCE WITHIN PLUS OR MINUS 12 HRS OF OPERATION. B. WAIVER APPROVED FOR ECP 1353 NSSCNS, AND ASTRO 1.49 SW INSTALL.

7. NO INDICATES NOT FROZEN. YES INDICATES ASSETS ARE FROZEN.

8. PLEASE REFER QUESTIONS TO 750 OSS/DOP AT DSN 561-4087.

MELISSA BUTLER, A1C

750 OSS/DOP, X4111

PHILLIP O. BAER, GS-12, DOP, 4087

CRC: 17764

UNCLASSIFIEDAttachment 4

FREEZE WAIVER REQUEST

OPR/POC:_____DATE:_____

Description of Activity:_____

_____

_____

_____

_____

Downtime Required:___Recovery Time:____Contractor Involvement:_____

Risk Involved: Benefits If Completed:_____

_____

_____

Assessment: (Comm Segment)

50th SCS Maintenance

MGR/Shift Supervisor

50th SCS OPS

MGR/Shift Supervisor

COORDINATION

Affected Modules: Name: Comments:

1.

2.

3.

Approval/Disapproval: Comments, if any:

50th SCS CC:

Comments: (Prior to beginning work, check with Mod Manager/Crew Commander/Etc...)

Approval/Disapproval Date:

GROUP CC:

FREEZE WAIVER REQUEST

OPR/POC: 1 DATE: 2

Description of Activity: 3

Downtime Required: 4 Recovery Time: 5 Contractor Involvement: 6

Risk Involved: 7 Benefits If Completed: 8

How to properly fill out your

FAFB Launch Freeze Waiver Request

Completion of this waiver is required prior to performing activities on a module which is frozen due to a launch freeze. A waiver is not required for Maintenance activities, PMI's of "Look Only" activities (opening racks and pulling floor tiles is not considered "Look Only").

1. Enter your name, organization and phone number.

2. Enter date.

3. Give a complete description of the activity, to include start and stop dates.

4. Enter the amount of downtime required, if any. If none, enter N/A

5. If downtime was entered in the "Downtime Required" block, enter the amount of time it will take to recover in case of an emergency. If N/A was entered in the "Downtime Required" block, enter N/A.

6. If the activity is being performed under contract, what company is performing it? If contractors are not involved, enter N/A.

7. Is there a risk of the activity impacting any other circuits or resources? If so, to what degree? If not, enter NONE.

8. What is the benefit of performing this activity during the freeze?

After you have completed answering these questions, bring the form to 50 SCS Plans and Scheduling located in Module 2A Northwest corner.

NOTE: It takes approximately 7 to 10 working days to process this form, so please plan carefully.