DEPARTMENT OF THE AIR FORCE

UNITED STATES SPACE FORCE

SPACE LAUNCH DELTA 30

SLD30GM1

8 January 2024

MEMORANDUM FOR SLD 30

FROM: SLD 30/CV

SUBJECT: Vandenberg Space Force Base Framelight Policy

1. Effective immediately, this guidance memorandum supercedes SLD30I10-1203.

2. “Framelight” is a term used to define a time-period which begins 48 hours prior to launch (L- 48 hours). Framelight ends when released by the Launch Decision Authority (LDA) or equivalent, or by the Interim Safety Board President in the event of an anomaly. Framelight maintains configuration control of launch-associated communications and Range infrastructure to minimize risk of disruption. Framelight is essentially a stop-work order for all work that is non-critical to the launch which might have an impact on the Range mission network or on instrumentation required for the launch. If work must be performed to support the launch, then Framelight does not apply to that work. If work is non-critical to the launch, then a Framelight waiver can be requested.

3. Framelight does not apply to commercial payload missions that fly with an Autonomous Flight Safety System (AFSS) in which minimal range support is required. Minimal range support is defined as no Command Destruct supersystem, no Telemetry supersystem, and no Radar supersystem support from the Range or as otherwise defined by 2 ROPS. This memo does not allow entities to perform work without standard permissions under Framelight conditions. In these cases, work on the Range will follow nominal maintenance coordination processes for risk to launch operations. All mission requirements in Universal Documentation System are still expected to be met.

4. When a waiver (2 ROPS Form 1) is requested it should be submitted two weeks prior to the start of Framelight. This allows subject matter experts time to review the requested work and perform a risk assessment. If the work requested involves excavation near communications lines or power outages, then a 2 ROPS Form 1 should be submitted to 30th Civil Engineer Squadron (CES), specifically the CE Mission Engineering section. If the work requested involves communication infrastructure, then a 2 ROPS Form 1 should be submittted to Space Communications Squadron (SCS). If the work requested doesn’t fall strictly under CES or SCS, then a 2 ROPS Form 1 should be submitted to 2 ROPS/DOR Range Engineer (RE) flight.

Depending on the risk of the requested work the 2 ROPS Form 1 will either be approved by the Squadron Commander or designee, or disapproved.

5. Certain recurring operations and maintenance requests are considered no risk and have been coordinated with 2 ROPS RE without the need to submit a waiver. Work that falls within the criteria below do not require a waiver.

a. No Risk Operations (Contractor supported Range communications): Range system programming changes/modifications, preventive/corrective level 1 or 2 maintenance that will not interfere or conflict with launch configurations of supporting range systems. Additional exemptions will be considered on a case-by-case basis.

b. No Risk Operations (SCS): Operations and maintenance requests for work that is not performed in racks containing Range equipment nor on patch panels through which Range circuits connect.

c. No Risk Operations (CES): Scheduled high-voltage switching which does not result in power outages to facilities required to satisfy Operational Directive (OD) requirements, such as bringing the South Vandenberg Power Plant (SVPP) on-line the day of launch. Excavation near water, natural gas, sewer, and drainage infrastructure is also considered no risk operations.

6. Launch slips affect operations and sometimes extend the Framelight period. It is the requestor’s responsibility to fill out a date range when submitting a waiver (2 ROPS Form 1). If a launch slip causes Framelight to extend, and the original waiver does not cover those dates, then a new waiver must be submitted. This process does not guarantee subsequent approval. The requestor must update the work requested and dates of that work in follow-on waiver submissions.

7. Emergency Waivers: Emergency situations are defined as those situations where failure to take action could result in risk to human life or public safety, system damage, impact to launch readinesss or other serious mission impacts. Agencies are authorized to take immediate action to address emergencies without a Framelight waiver. However, emergency actions shall be documented on 2 ROPS Form 2 at the earliest possible opportunity by the agency taking the emergency action. The 2 ROPS RE section must have situational awareness of all emergency actions to ensure their ability to properly assess mission risk in real time.

8. My point of contact on this matter is 2 ROPS/DOR, 30rms.re@us.af.mil DSN: 276-1299.

BRYAN M. TITUS, Colonel, USSF Vice Commander

TITUS.BRYAN.

M.1239756014

Digitally signed by

TITUS.BRYAN.M.1239756014

Date: 2024.01.16 15:36:20 -08'00'