Attachment 1 LISC PWS Extension - Market Research.pdf

Attachment 1: Performance Work Statement

Launch and Test Range System (LTRS)

Integrated Support Contract (LISC)

For Operations, Maintenance, and Sustainment (LISC OMS)

Attachment 1: Performance Work Statement (PWS)

8 February 2024

Revision Change Record

Revision Effective

Date Description Initials

2 Aug 2017

Added Table 6-1 work load factors for AFSS launches and increased Range Safety Analysis work load factors.

Incorporated PWS line 3.2.1.4.7.1 for WR Infrastructure and Flight Safety Analysis. Updated List of Acronyms and Abbreviations to include AFSS.

MWF

7 Aug 2017

Added PWS line 2.5.1.7 for exempt employee attrition rate and related personnel reports.

23 Mar 2018

Revised Table 6-1 launch work load factors to show original baseline and FY17 and FY18 updates.

5 Jun 2018

Revised Table 1-1 and added PWS task 3.13.7 to include support for Air Force Technical Applications Center (AFTAC). Removed GPN-30 radar at KSC requirement from PWS paragraph 6.4.1.

22 Mar 2019

Added Telemetry Early Acquisition (TMEA) A&B to 1.5.2.

Updated 6.4.1. by adding TMEA A&B and Removing 8’ Telemetry Antenna System

22 Mar 2019

Removed reference to 30’ Telemetry Antenna System at PWS line 1.5.3. and list of Range Items at 6.4.1.

6 Oct 2020

Removed (except PAFB) from PWS Line 3.2.2.15 and add PAFB Microwave System to the list of Range Items at 6.4.1.

AME

25 FEB 2022

Incorporate Admin changes from Facts of Life review - 2017

KMD

19 May 2022

Replace operation of the ER Range Automated Tracking System (RATS) with the Stargate system.

AJB

24 Aug 22

Incorporate the CLIN XX05 to XX01 Changes from P00378

30 Mar 23

Incorporate Ogden MDM Support

24 May 23

Incorporate Juneteenth, add SLC-8 Equipment List to 6.4.7

12 Jun 23

Incorporate changes from ER FY23 Manifest Increase

17 Jul 23

Incorporate revision to PWS paragraph 2.10.1.8, add new PWS paragraph 3.5.4

AJB

15 23 Aug 23 Incorporate changes from the WR FY23 Manifest Increase AJB

16 27 NOV 23 PWS update adding 6.4.8 and Table 6-3 KMD

17 11 DEC 23 Add Metric Optics to 1.1.2 LTRS Overview, and 1.3.1 ER AJB and WR Functional Overview. Update Scoring Criteria for

SSI 6.

18 14 DEC 23 PWS update for FY24 Increment 1 WLF KMD

19 TBD

TABLE OF CONTENTS

1. EXECUTIVE SUMMARY

1.1. Launch and Test Range System (LTRS) Integrated Support Contract (LISC) Operations, Maintenance, & Sustainment (OM&S) Introduction

1.2. Technical Management Approach

1.3. LTRS Description

1.4. Eastern Range Composition

1.5. Western Range Composition

1.6. General Instructions

2. PROGRAM MANAGEMENT REQUIREMENTS

2.1. Provide Program Management of the Launch and Test Range System (LTRS) Integrated Support Contract (LISC)

2.2. Provide an Enterprise-Level Data Management System, referred to as LISC Information Management Enterprise System (LIMES)

2.3. Provide Adequate Financial Information for Government Insight and Cost Management

2.4. Provide Continuous Monitoring and Improvement of Contractor Performance of LISC Services

2.5. Provide Management of LISC-Employed Personnel

2.6. Manage All Government-Furnished Property (GFP)

2.7. Implement Security Management Processes

2.8. Implement a Comprehensive Safety Program IAW Occupational Safety and Health Administration (OSHA) Federal Regulations and to Support the AFSPC Mission

2.9. Implement a Comprehensive Environmental Management Program

2.10. Conform with LISC General Requirements

3. PERFORMANCE REQUIREMENTS

3.1. Perform Range Operations

3.2. Operate Range Instrumentation (on the baseline identified in PWS Sections 6.4.1 and 6.4.6) and Assess Range Instrumentation Performance

3.3. Perform Range Organizational Maintenance (on the baseline identified in PWS Sections 6.4.1, 6.4.5 and 6.4.6)

3.4. Maintain Range Systems through Depot Maintenance (on the baseline identified in PWS Sections 6.4.1, 6.4.4, and 6.4.5)

3.5. Perform Logistics Management Functions

3.6. Sustain (Modify) LTRS to Ensure that Range Operational Requirements Are Met

3.7. Perform Range Systems Engineering Functions to Support LTRS (in support of the baseline identified in PWS Sections 6.4.1, 6.4.4, 6.4.5 and 6.4.6)

3.8. Improve Range Availability and Reliability through Use of the LTRS Sustainment System163

3.9. Perform Software-Related Activities

3.10. Provide Availability, Integrity, Confidentiality, and Non-Repudiation of DoD Information Systems

3.11. Provide Technical Support to Inform Government Decision-Making for the LTRS Mission 178

3.12. Support Government Item Managers at Organic Depots

3.13. Provide Specialized Support

3.14. Provide Interim Contractor Support

4. APPLICABLE PUBLICATIONS AND DOCUMENTS

5. APPENDICES

5.1. List of Acronyms and Abbreviations

6. PWS SUPPORTING DATA

6.1. Work Load Factors

6.2. Contract Data Requirements List (CDRL)

6.3. Service Summary Items (SSIs)

6.4. Range Items (RIs), Exception List and Others

List of Figures

Figure 1-1: Eastern Range Figure 1-2: Western Range Figure 1-3: West Coast Offshore Operating Area

List of Tables

Table 1-1: ER MRTFB Activities Table 1-2: WR MRTFB Activities Table 3-1: Communications Response and Completion Time Requirements Table 3-2: Parameter Uncertainties for Launch Vehicle Track in Beacon Mode Table 3-3: Parameter Uncertainties for Launch Vehicle Track in Skin Mode Table 3-4: Parameter Uncertainties for Satellite Track in Beacon Mode Table 3-5: Parameter Uncertainties for Satellite Track in Skin Mode Table 3-6: Trouble Ticket Response and Restoral Times Table 3-7: 30 LCG Communications List Table 4-1: Applicable Mandatory and Advisory Publications and Documents for PWS Table 6-1: List of Work Load Factors Table 6-2: List of Meetings

Table 6-3: List of Abandon in Place/Discontinuance……………………………………………………….314

Table 6-4: Mission Support Assessment Matrix – Potential Outcome ……………………………………XXX

1. EXECUTIVE SUMMARY

1.1. Launch and Test Range System (LTRS) Integrated Support Contract (LISC) Operations, Maintenance, & Sustainment (OM&S) Introduction

In partnership with the 30th and 45th Space Wings (30 SW and 45 SW), the Space and Missile Systems Center (SMC), Spacelift Range and Network Systems Division (SMC/RN), Los Angeles Air Force Base, California, has designed the LISC effort to meet the Headquarter Air Force Space Command (HQ AFSPC) vision of improving LTRS efficiency and effectiveness while continuing mission success and keeping the Eastern Range (ER) and Western Range (WR) operational today and in the future. Through LISC, the Air Force intends to achieve two primary objectives: 1) maintain mission assurance through responsive Operations, Maintenance, and Sustainment (OM&S) and 2) reduce range costs through efficiencies from consolidating contracts and using common processes throughout the range enterprise. Today, a substantial amount of resources are expended on the Ranges, with yearly increases, in order to maintain current levels of operational performance. The LISC effort provides the opportunity to streamline and normalize operations, maintenance, logistics, engineering, and sustainment activities to achieve cost efficiencies through improved manpower utilization. LISC will consolidate all existing Range OM&S requirements into one contract, preserving unity of effort for all operations, maintenance, and sustainment of the Range mission and mission system. The LISC OM&S contractor will be responsible and accountable for complete and integrated LTRS operations, organizational and depot level maintenance, logistics management, and sustaining engineering.

Simultaneously, LISC will provide a unique opportunity for Small Business to consolidate essential operations support services through a Small Business Set-Aside effort. The Range Operations Support (ROS) contractor will be responsible and accountable for aspects of non-mission administrative support communications for both the ER and WR and essential base service elements of Downrange Base Operating Support (DBOS) for the ER. Through the OM&S and OS efforts, LISC contributes to the AFSPC Commander’s Launch Enterprise Transformation (LET) vision, Office of the Secretary of Defense (OSD) Test Resource Center oversight of the ER and WR as part of the Major Range Test Facility Base (MRTFB), and NASA’s 21st Century Space Launch Complex plans. The LISC OM&S and OS efforts are key enablers of Range Transformation and support the capability for ER and WR to meet operational mission requirements in a cost constrained environment.

1.1.1. LTRS Mission

Air Force, DoD, National Aeronautical Space Administration (NASA), and commercial satellites are launched from ER and WR to provide navigation, communications, weather, scientific, space control, and missile warning capabilities for global military operations, as well as civil and commercial activities.

In addition, the ER and WR provide unique test range capabilities in support of DoD/NASA test requirements. The 45th Space Wing (45SW) operates and maintains the ER, supporting human space launches and unmanned military, civil, and commercial satellite launches into geostationary and geosynchronous orbits and beyond. The ER also supports development of long range rockets and space launch vehicles, Trident IV submarine launch, ballistic missile operational test launches, DoD weapons systems development and testing, and aeronautical testing. The 30th Space Wing (30SW) operates and maintains the WR, supporting unmanned military, civil, and commercial satellite launches into polar orbit. The WR also supports Minuteman III operational test launches, Missile Defense Agency (MDA) Ground-based Midcourse Defense testing, aeronautical testing, air defense exercises, and weapon system development. The WR operates the West Cost Offshore Operating Area (WCOOA) and the Radar Performance Monitoring program for all national ranges. The ER and WR can each operate either as a lead range that draws support from other ranges or as a support range that provides limited to full capability of range assets to support operations at other ranges.

1.1.2. LTRS Overview

The Launch and Test Range System (LTRS) is a complex network of 12 subsystems, including:

Command Destruct, Communications, Data Handling, Safety, Optics, Metric Optics, Planning and Scheduling, Radar, Surveillance, Timing and Sequencing, Telemetry, Weather, and Modeling and Simulation. Each subsystem has human in-the-loop (HITL) operators and procedures that are an integral part of the LTRS. This system of systems, through a combination of instrumentation assets, provides for the safe and effective launch, testing, and tracking of Department of Defense (DoD), civil, and commercial spacelift vehicles, in addition to conducting ballistic missile, guided weapon, and aeronautical tests and evaluations.

LTRS contains, in many cases, critical components that are over 40 years old. As a result of the LTRS evolution over the past five decades, it also consists of more than 49 million Physical Source Lines of Code (SLOC) using more than 200 unique programming languages. Unique technical expertise is needed to operate, maintain, and sustain this equipment and software and to ensure these one-of-a-kind ER and WR aging assets are ready to support our nation’s launches.

The subsystems are documented in the LTRS Department of Defense Architectural Framework (DoDAF) and further defined in the Configuration Item (CI) Tree. There are additional assets identified on an Exception List that support the ER and WR missions that require depot-level maintenance from LISC. Furthermore, there are additional range equipment and assets owned and operated by the 30 SW and 45 SW, as well as some items from the Exception List, that LISC OM&S may be required to incorporate into the CI Tree. With the transition to LISC OM&S, the Government has determined to standardize a CI hierarchy for the LTRS. As described in this PWS, the following terms are defined:

System = LTRS Subsystem = Radars, Optics, Telemetry, etc.

Range Item = Patrick DOAMs, TPQ-18, CT-1, TAA-20, etc.

Configuration Item = Antenna, Pedestal, Receiver, Recorder, etc.

Line Replaceable Unit (LRU) = SEMCO Receiver, hard drives, antenna feed, slip ring, telescope, camera, etc.

Component = power supply, resistor, integrated circuit memory card, interface card, etc.

1.2. Technical Management Approach

1.2.1. Direction to LISC OM&S Contractors

The LISC OM&S effort direction will be provided by the Government and is detailed in the LISC management plan. Operational wings will provide daily tasking while SMC will appoint the program manager and PCO to administer and execute the contract.

1.2.2. Transition Period

Upon direction of the Government, the contractor will initiate a 90-day transition or contract phase-in period. During this period:

a. Incumbent contractors will be fully responsible and accountable for meeting all OM&S requirements for the Eastern Range and Western Range.

b. The LISC OM&S contractor will be responsible for the phase-in requirements defined in task 2.10.4.

At the completion of the transition period, the Government will direct the start of the OM&S CLINs and the LISC OM&S contractor will be fully responsible and accountable for meeting all PWS requirements.

Therefore, the contractor shall perform all tasks during the 90-day transition period that are necessary to ensure it is fully capable of meeting all PWS requirements at the end of transition period.

1.2.3. LTRS Systems Engineering, Configuration Management, and Configuration Control

LTRS Systems Engineering (SE) and Configuration Management (CM) is performed by the government (SMC) with the assistance of the LTRS Systems Engineering and Integration (SE&I) contractor and The Aerospace Corporation. The SMC LTRS PM maintains Configuration Management authority. The government maintains configuration management of the LTRS at the system and subsystem levels.

The government uses LISC OM&S to maintain configuration management of products and data at the Range Item (RI) level and below. The 30 SW and 45 SW Commanders maintain Configuration Control authority and use LISC OM&S to execute configuration control of the LTRS. SMC and the Operational Wings expect LISC OM&S to exercise rigorous discipline for configuration management and configuration control of the LTRS, to include Cybersecurity, with close coordination between SMC and the Space Wings.

1.3. LTRS Description

1.3.1. ER and WR Functional Overview

The ER and WR provide metric tracking, telemetry acquisition, short and long range photo optics, as well as Metric Optics (MO) on the ER, command control, meteorological forecast and real-time observation, area surveillance, communications, real-time data processing, and post-flight data production. Figure 1-1 depicts ER and support range instrumentation tasked to support the ER mission.

Figure 1-2 depicts WR and support range instrumentation tasked to support the WR mission. Range instrumentation consists of telemetry acquisition and processing systems, metric tracking and signature radars, GPS tracking systems, airspace and ocean surveillance systems, short and long range photo optic systems, safety command control systems, meteorological systems, timing systems, communication systems, and control centers. The LISC OM&S contractor is required to operate and maintain a wide variety of mission and mission- support systems; and, in conjunction with the government and other contractors, define requirements, identify operations capability shortfalls/capability to support Range User requirements via the Universal Documentation System (UDS) process, and assess the impact of integrating new systems supported under the LISC effort. The wide variety of mission and mission-support services requires careful workload planning and scheduling of resources to identify and resolve technical systems problems.

Systems supported typically exist in an infrastructure that has undergone various modifications during the past several decades, are located in a highly corrosive environment, and must support missions that are subject to a large number of schedule variables.

Figure 1-1: Eastern Range

Eastern Range Encompasses 15 million square miles!

WALLOPS ISLAND (NASA)

CCAFS/KSC/PATRICK •

RADAR

TELEMETRY

OPTICS

RADAR

• TELEMETRY

• COMMAND

LAUNCH AREA SUPPORT SHIP

COMMAND/CONTROL

RANGE SAFETY

DATA PROCESSING

TELEMETRY

SATRACK

SATCOM

NETWORK HUB

SATCOM

HIGHLY INCLINED

ORBIT

EQUATORIAL ORBIT

JONATHAN DICKINSON MISSIL

TRACKING ANNEX

• TELEMETRY

• SATCOM SLBM CORRIDOR

• RADAR

• TELEMETRY

• COMMAND P3 AIRCRAFT

• OPTICS

• SMILS ASCENSION

• RADAR

• SATCOM

ANTIGUA

Figure 1-2: Western Range

1.3.2. West Coast Offshore Operating Area

The WR controls the WCOOA, Figure 1-3. The WCOOA is a stretch of air space spanning the West Coast of the United States. The test corridor provides a large stable air mass for aeronautical testing with aircraft control and tracking capability along the coast of California. Aeronautical tests requiring minimum turbulence, supersonic speeds and very low altitude, can be run along the test corridor. The 30 SWI 99-103, Aeronautical Operations and Testing in the WCOOA, define the policies, responsibilities, and procedures for supporting operations and tests in the WCOOA.

Figure 1-3: West Coast Offshore Operating Area

1.3.3. ER and WR Support to Other National Ranges

In the support range role, the ER and WR support other National Ranges. The ER serves as lead range in a worldwide network and supports other lead ranges as well as other government agencies. The WR supports orbital insertion and on-orbit requirements for launches from the ER; aeronautical and missile tests conducted by Air Force Flight Test Center, Edwards AFB; aeronautical and missile tests conducted by the Naval Air Warfare Center (NAWC) Weapons Division Point Mugu; Missile Defense Agency (MDA) tests from Kodiak Launch Complex, AK, Barking Sands Test Site, HI, and Reagan Test Site (RTS) U.S. Army Kwajalein Atoll, Marshall Islands; and spacelift launches from the RTS.

1.3.4. When a Range User’s Test Requires Multiple MRTFB Activities

In accordance with DoDD 3200.11, when a Range User’s test requires the support of more than one MRTFB activity:

a. With the ER as the lead activity (Lead Range), it will serve as the principal point of contact with the user for planning, execution, and reimbursements, and will coordinate with other MRTFB activities (Support Ranges) to obtain total support for the test per Table 1-1. An ER user requiring support outside the MRTFB activity (e.g., NASA, MDA) must request, task, and fund the responsible agency for required support.

b. Likewise, with the WR as the lead activity (Lead Range), it will serve as the principal point of contact with the user for planning, execution, and reimbursements, and will coordinate with other MRTFB activities (Support Ranges) to obtain total support for the test per Table 1-2. A WR user requiring support outside the MRTFB activity (e.g., MDA, NASA, etc.) must request, task, and fund the responsible agency for required support.

Table 1-1: ER MRTFB Activities

ER MRTFB Activities

NASA Activities

White Sands Test Center

Wallops Flight Facility

Navy Activities

Naval Ordinance Test Unit

Air Force Activities

Air Force Technical Applications Center (AFTAC)

Table 1-2: WR MRTFB Activities

WR MRTFB Activities

Army Activities

White Sands Test Center

U.S. Army Kwajalein Atoll (Ronald Reagan Ballistic Missile Defense Test Site)

Navy Activities

Naval Air Warfare Center - Weapons Division, Point Mugu

Naval Air Warfare Center - Weapons Division, China Lake

Pacific Missile Range Facility

Air Force Activities

45th Space Wing

30th Space Wing

Nevada Test and Training Range

WR MRTFB Activities

Air Force Flight Test Center

Utah Test and Training Range

1.4. Eastern Range Composition

1.4.1. Overview of the Eastern Range

The ER, operated and maintained by the 45th Space Wing at Patrick Air Force Base (PAFB), extends from the launch head at Cape Canaveral Air Force Station (CCAFS) along the East Coast of the continental United States (US) northward through the Atlantic Ocean to Newfoundland and southeastward to Ascension Island in the South Atlantic Ocean. ER instrumentation is located at CCAFS, PAFB, Malabar Tracking Annex (MTA), Jonathan Dickinson Missile Tracking Annex (JDMTA), Kennedy Space Center (KSC), and Ascension Auxiliary Air Field (AAAF). In addition, the ER may use other DoD sites and/or the NASA facility at Wallops Island, Virginia. Mobile assets are dispatched as necessary. When requested and funded by the user, ER personnel will process, reduce, and analyze data to the user’s specifications. The following is a listing of the principal ER assets by geographical location.

1.4.2. Cape Canaveral AFS

The CCAFS encompasses approximately 15,800 acres located on the Atlantic Coast between Port Canaveral, Florida, and NASA, KSC. It is bordered on the east by the Atlantic Ocean, west by the Banana River, north by KSC, and south by Port Canaveral. Principal assets on CCAFS include:

a. Morrell Operations Center (MOC)

b. Central Command Remoting System (CCRS), Central Command Management System (CCMS)

c. AN/FPS-16 radar 1.16

d. Cape 1A and 1B Command Sites

e. Weather Assets

f. Cinetheodolite optical telescopes (4)

g. Advanced Transportable Optical Tracking System (ATOTS) 2

h. Skid Strip flightline

1.4.3. Patrick AFB

The base maintains an active airfield, encompassing approximately 1,943 acres. The topography of the base is extremely flat, varying from sea level to 15 feet above, with the Atlantic Ocean dune-line providing the only relief. Principal assets on PAFB include:

a. AN/FPQ-14 radar (0.134)

b. Distant Object Altitude Measurement System (DOAMS)

c. Radar, Telemetry, Command and Optics test beds

1.4.4. Florida Annexes

The Florida Annexes are contractor-operated sites providing tracking, weather and communications support to the space flight mission at CCAFS. Specific support requirements for locations on the Florida Annexes are discussed separately within the PWS. Unmanned sites are occupied periodically and during launches based on launch requirements documents and approved Instrumentation Coverage Plan.

a. Jonathan Dickinson Missile Tracking Annex. JDMTA, situated 95 miles south of CCAFS, occupies 12 acres inside the southern boundary of the Jonathan Dickinson State Park, just north of Jupiter, Florida. This state-of-the-art site includes four TAA-50 telemetry units, which provide in-flight monitoring of launch vehicles performance, electronics, and associated subsystems. The site also employs flight test support systems, a microwave relay to the Cape, a Translated GPS Range System (TGRS), and a command destruct system remotely activated from the Cape if and when it becomes necessary to protect life and property should a launch vehicle veer off course.

b. Malabar Tracking Annex. MTA occupies 640 acres and is located 6.2 miles southwest of Melbourne, Florida, on SR 509 in Brevard County. The site hosts a microwave relay.

c. Missile Instrumentation Station - PAFB. A facility that occupies 4.7 acres of oceanfront property within the boundaries of PAFB; however, for range purposes it is considered one of the Florida Annexes. This site consists of the 0.134 radar and the DOAMS.

d. Intermediate Microwave Relay Sites. Sites located between JDMTA and CCAFS near Wabasso, Ft. Pierce, and Stuart, Florida. Each site is approximately one acre in size with a tower and instrumentation building.

e. Weather Sensor Sites. Sites are unmanned and located at a variety of sites across five counties; Brevard, Orange, Osceola, Seminole, and Volusia counties in Florida. The Weather Surveillance Radar is located in Orange County.

1.4.5. REMOVED

1.4.6. Ascension Auxiliary Air Field

The AAAF is a contractor-operated tracking and instrumentation station on a volcanic-rock island in the South Atlantic nearly 5,000 miles downrange from CCAFS. The island has the appearance of a rough circle with an estimated diameter of 6 miles and an area of 34 square miles.

The AAAF mission is to provide radar tracking, space surveillance tracking, telemetry, timing and sequencing, and communications support downrange to the ER. Major range assets include: the AN/FPQ-15 12.15 radar, two TAA 3C telemetry systems, HF Global radio, and other communication systems.

1.4.7. Kennedy Space Center

Principal instrumentation and systems at KSC include:

a. Multiple Object Tracking Radar (MOTR) AN/MPR-39 Radar 19.39

b. TEL IV

c. AN/FPQ-14 Radar 19.14

d. Weather Assets

e. Distant Object Altitude Measurement System (DOAMS)

1.5. Western Range Composition

1.5.1. Overview of the Western Range

The WR, operated and maintained by the 30th Space Wing at Vandenberg AFB (VAFB), extends from the launch head at VAFB along the West Coast of the continental United States (US) westward through the Pacific and Indian Oceans. WR instrumentation is located at VAFB, CA; Pillar Point Air Force Station (PPAFS), CA; Santa Ynez Peak (SYP), CA; and at the Naval Air Warfare Center (NAWC) Point Mugu, CA.

The following is a listing of the principal WR instrumentation and systems by geographical location.

1.5.2. North Vandenberg AFB (NVAFB)

a. Building 7000 Complex

i. Western Range Operations Control Center (WROCC), building 7025

ii. Instrumentation control facility, building 7011

iii. Data Center 80 (DC-80), building 7050

iv. Telemetry Analog Equipment Room (TAER)

v. Telemetry Integrated Processing System (TIPS)

vi. Quick Look Display Area (QLDA)

b. Frequency Control and Analysis Center (FCAC)

c. Radio Frequency Measurements Center (RFMC)

d. Western Range Network Segment Center (WRNSC)

e. High Accuracy Instrumentation Radar (HAIR)

f. Ocean Surveillance System (OSS) radar (2)

g. High Frequency Radio Receivers (HFRX)

h. Command Transmitter #1 (CT-1)

i. Mobile Telemetry Receiving Station (MTRS) 2

j. Automated Meteorological Profiling System (AMPS)

k. Base Weather Station (BWS)

l. Telemetry Early Acquisition (TMEA) A&B

Real-time telemetry data, translated GPS data, radar data, video and audio are relayed to the 7000 complex for recording, retransmission, processing, and display. CT-1 is located to maximize line-of-sight coverage for the ICBM Launch Facilities (LF) on NVAFB. The HAIR provides line-of-sight coverage for the Space Launch Complexes (SLCs) on South Vandenberg AFB (SVAFB).

1.5.3. South Vandenberg AFB (SVAFB)

a. Vandenberg Telemetry Receiving Site (VTRS) with 44’a, 44’b, 35’ antennas

b. TGRS (2)

c. AN/FPS-16 Radar

d. AN/TPQ-18 Radar (undergoing ROSA modification)

e. Air Route Surveillance Radar (ARSR-4)

f. Ocean Surveillance System (OSS) radar

g. Command Transmitter #3 (CT-3)

h. Command Transmitter #5 (CT-5)

i. Frequency Monitoring Station (FMS)

j. UHF/VHF Radio Systems

k. High Frequency Radio Transmitters (HFTX)

l. DOAMS

Other launch area support instrumentation including weather, network connections, and radio frequency (RF) monitoring systems are located throughout the base. VTRS is located on Sudden Peak at 2100 feet above sea level to maximize coverage in all directions. The AN/FPS-16 is located on Tranquillon Peak at 2126 feet above sea level, providing a commanding view of most launch facilities.

CT-3 is located to provide command control for launch facilities south of Honda Ridge.

1.5.4. Pillar Point AFS

The principal instrumentation and systems on PPAFS located 23 miles south of San Francisco near Half Moon Bay, CA include:

a. 44’ and 40’ telemetry antennas

b. TGRS (2)

c. Command Transmitter #4 (CT-4)

d. UHF/VHF radio systems

e. FPQ-6

The geographical location of PPAFS provides an aspect angle for westerly ballistic launches that diminishes problems associated with plume attenuation, phase front disturbances, and other anomalous behaviors common to the VAFB sensors that result from looking into the plume of an outbound solid propellant rocket. This site also provides extended coverage for aeronautical tests conducted in the WCOOA.

1.5.5. Santa Ynez Peak

Santa Ynez Peak is located 30 miles east of VAFB and is the site of the Recording Optical Tracking Instrument (ROTI) telescope. At an elevation of 4133 feet, SYP is approximately 1000 feet above the marine convection layer putting it above a high percentage of atmospheric turbulence. Its location provides an excellent broadside aspect angle for polar spacelift launches and coverage for aeronautical tests conducted in the WCOOA.

1.5.6. NAWC Point Mugu, CA

The WR’s Command Transmitter #6 (CT-6) is located at NAWC Point Mugu, CA. The geographical location of NAWC provides an aspect angle for polar spacelift or ballistic launches that diminishes problems associated with plume attenuation, phase front disturbances, and other anomalous behavior common to the VAFB sensors that result from looking into the plume of an outbound solid propellant rocket. The NAWC is also designated an MRTFB and provides extensive support to the WR as a support range.

1.5.7. Other WR Remote Locations

The WR utilizes communications connections that flow through several remote sites to include:

Rainbow Ridge, Mill Valley, Los Angeles Center, and San Clemente Island. These sites house communication link UHF radios and modems. The WR also utilizes the OSS radars located at San Luis Light Station (16 miles north of VAFB) and Point Conception (located 10 miles south of VAFB).

1.6. General Instructions

1.6.1. Applicability of Requirements to Eastern and Western Ranges

All tasks apply to both Eastern (ER) and Western Ranges (WR) unless otherwise indicated. In the event of a perceived conflict or inconsistency between ER and WR requirements, the requirement will be clarified through a PCO letter.

1.6.2. Workload Factors

The Workload Factors are identified in Attachment 6 for the purpose of scoping the extent of the tasks in the PWS.

1.6.3. Service Summary Items

The Service Summary Items (SSIs) located in Section 6.3 define the Performance Based Objectives that will be used to evaluate overall contractor performance beyond basic cost control for this contract.

The evaluation and scoring of these metrics will establish the Quality Performance Index (QPI) used to adjust the contractor’s incentive as described in the LISC Incentive Plan. These SSIs represent those most critical attributes required from the contractor to “keep the Range green.” Achievement of the SSIs will also form the foundation of the Contractor’s Performance Assessment Report (CPAR) required at the completion of each performance period. The contractor should carefully consider the achievement of the SSIs when determining appropriate courses of action throughout the execution of the contract.

2. PROGRAM MANAGEMENT REQUIREMENTS

OBJECTIVE

2.1. Provide Program Management of the Launch and Test Range System (LTRS) Integrated Support Contract (LISC)

TASK

2.1.1. The contractor shall establish a management structure to ensure the requirements of the PWS are met.

The contractor is responsible for performing all tasks necessary to fulfill this requirement. At a minimum, this work includes:

2.1.1.1. The contractor shall appoint a single Program Manager with the authority to make all decisions regarding the performance of the contract.

2.1.1.2. The contractor shall maintain single points of contact on site at the Eastern Range (ER) and at the Western Range (WR) with authority over their respective LISC resources.

2.1.1.3. The contractor shall designate site managers for each downrange location as a primary point of contact to manage LISC OM&S day-to-day activities, participate in long-range planning, and assist the respective Station Commander in representing the United States and the Air Force with the host nation and local communities.

Note: A site manager is a role to be performed by the contractor not necessarily a full time duty.

2.1.1.4. The contractor shall ensure that the contract is adequately staffed (including subcontracts) and, where required, ensure that employees meet all certification, licensing, experience, and training requirements.

2.1.1.5. The contractor shall interface with and cooperate with other Range contractors, government and commercial agencies, other Major Range and Test Facility Bases (MRTFBs), and government support contractors.

2.1.1.6. The contractor shall ensure that a senior contract management representative is present during Range operations and is available during emergencies with the authority to direct contract personnel.

2.1.1.7. The contractor shall provide all Non-CDRL data IAW PWS Section 2.2.1.17.

DELIVERABLES

None

2.1.2. The contactor shall provide program management, functional, and logistical support for government program-level meetings.

This task is in support of the meetings identified in Table 6-2 of the PWS. The contractor is responsible for performing all tasks necessary to fulfill this requirement. At a minimum, this work includes:

2.1.2.1. The contractor shall ensure information is provided to support meeting and decision-making objectives.

2.1.2.2. The contractor shall accomplish all logistical elements of contractor-supported meetings and reviews.

2.1.2.3. The contractor shall provide all Non-CDRL data IAW PWS Section 2.2.1.17.

A001 Management Reviews

A002 Technical Meetings and Reviews

2.1.3. The contractor shall develop, implement, operate, and maintain information support systems.

There are a number of government business management tools that the LISC contractor will provide support for that are not part of the LISC Information Management Enterprise System (LIMES) as defined in PWS section 2.2. This task defines the LISC contractor requirements for these tools.

The contractor is responsible for performing all tasks necessary to fulfill this requirement. At a minimum, this work includes:

2.1.3.1. The Contractor shall provide the government with program management information support services to share information relevant to the space launch, with the range community and commercial organizations.

2.1.3.1.1. The Contractor shall provide relevant data generated or maintained by the Contractor, such as databases, documents, email, and drawings via automated and web based interfaces.

2.1.3.1.2. The Contractor shall support AutoSTK, AutoPlan, ERIS Planning Support System (EPSS), TurboDOCS, and ERIH Wiki and other software or database application recommended by the contractor to meet this requirement.

2.1.3.2. The Contractor shall provide the following types of baseline maintenance support for software and databases required to meet this requirement.

2.1.3.2.1. The Contractor shall modify software and database applications and systems in order to correct discovered problems (corrective maintenance).

2.1.3.2.2. The Contractor shall modify software and database applications and systems in order to keep them usable in a changed or changing environment (adaptive maintenance)

2.1.3.2.3. The Contractor shall modify software and database applications and systems in order to improve performance or maintainability (perfective maintenance). The Contractor shall modify software and database applications and systems in order to detect and correct latent faults before they become effective faults (preventive maintenance).

2.1.3.3. The contractor shall ensure that the automated task management and control system tracks all CO tasks and COR requests, including tracking of the following task-related documents and data at a minimum:

a. Tasking directive document

b. Name(s) of the requester and the requester’s organization

c. Date and time of the request

d. Date and time for when the support is required

e. The support requirement (PWS reference paragraph)

f. Any coordination that was required

g. Any action taken.

2.1.3.4. The contractor shall provide all Non-CDRL data IAW PWS Section 2.2.1.17.

A003 Source Code and Executables Non-CI

A004 Software User Manual Non-CI

A005 Database Design Document Non-CI

A006 Software Design Document Non-CI

2.1.4. The contractor shall prepare and maintain a Contract Work Breakdown Structure (CWBS) to define, organize, and graphically display contractor activities under

LISC.

The contractor is responsible for performing all tasks necessary to fulfill this requirement. At a minimum, this work includes:

2.1.4.1. The contractor shall employ the CWBS as the basis for contract planning, budgeting, and cost and schedule reporting.

2.1.4.1.1. The contractor shall use a single numbering system based on the CWBS that depicts the time-phased requirements.

2.1.4.2. The contractor shall update the LISC CWBS and CWBS dictionary, as required, subject to Contracting Officer (CO) approval.

2.1.4.3. The contractor shall provide all Non-CDRL data IAW PWS Section 2.2.1.17.

2.1.5. The contractor shall manage and execute an Integrated LISC Plan (ILP) and an Integrated LISC Schedule (ILS).

The contractor is responsible for performing all tasks necessary to fulfill this requirement. At a minimum, this work includes:

2.1.5.1. The contractor shall electronically link individual job schedules and be able to display and filter specific schedule events and activities.

2.1.5.2. The contractor shall ensure that the Integrated LISC Schedule (ILS) integrates with non- LISC schedules which could impact LISC.

2.1.5.3. The contractor shall identify dependencies between activities necessary to achieve key events or milestones. NOTE: Of special interest are activities which are not otherwise grouped with the key event or milestone (e.g. a project to upgrade telemetry on the ER appears to not have any dependency to other activities on the ER, however, a specific phase of the project needs to be complete by a specific NASA launch to support customer requirements.) Additionally, of special interest are key events or milestones which will stress (i.e. over demand limited resources) the contractor’s ability to meet the key events or milestones.

2.1.5.4. The contractor shall perform analysis of the ILS tasks and report potential or existing problem areas, recommend corrective actions, and implement mitigation actions to eliminate or reduce schedule impacts.

2.1.5.5. The contractor shall structure the ILS to permit revisions and updates.

2.1.5.6. The contractor shall provide all Non-CDRL data IAW PWS Section 2.2.1.17.

A007 Integrated LISC Schedule

A008 Integrated LISC Plan

2.2. Provide an Enterprise-Level Data Management System, referred to as LISC Information Management Enterprise System (LIMES)

2.2.1. The contractor shall execute data management processes in accordance with (IAW) the LISC data management plan.

The following are applicable to the sub-tasks below: AFI 10-701 and AFI 33-129.

Currently, the government uses three separate data management systems (Electronic Information Interchange System (EIIS) for sustainment, Program Information Management System (PIMS) for WR operations and maintenance (O&M), and VPORT/Vision for ER O&M). Under LISC, the government requires a single web-based interface for government access to LISC-managed data (including all data currently residing in the aforementioned systems). The common data management framework is referred to as the LISC Information Management Enterprise System (LIMES) throughout this PWS.

The contractor is responsible for performing all tasks necessary to fulfill this requirement. At a minimum, this work includes:

2.2.1.1. The contractor shall develop a system (LIMES) that provides a web-based interface for a single point of access to all contractor-generated LISC data including data access tools to integrate data elements. The contractor shall ensure all data from the government-provided EIIS, PIMS, and VPORT/Vision legacy data management systems is accessible through or in LIMES.

Note: The contractor does not need to maintain the legacy data management systems so long as legacy data is fully integrated into LIMES.

2.2.1.2. The contractor shall ensure that LIMES conforms with Department of Defense (DoD) 8500 Series Cybersecurity instructions and Air Force Instruction (AFI) 10-701.

2.2.1.3. The contractor shall make the data accessible on LIMES 24 hours a day, 7 days a week (24/7) via a single web-based interface government data management system or other contractor-recommended and government-approved method.

NOTE: Excludes LIMES planned maintenance/downtime.

2.2.1.4. The contractor shall ensure that LIMES implements roles-based security profiles allowing full control, restricted access, and limited access for personnel authorized access at the appropriate level. The contractor shall ensure that LIMES provides data in native file formats to enable manipulation for future government use.

2.2.1.5. The contractor shall host LIMES on government-owned hardware (Contractor Acquired Property (CAP)).

Note: The hardware may be located either on or off the government network.

2.2.1.6. The contractor shall provide LIMES Help Desk support during core working hours as defined in this PWS.

2.2.1.7. The contractor shall provide LIMES training to users.

2.2.1.8. The contractor shall publish interface information on LIMES to enable cross-platform automated data sharing.

2.2.1.9. The contractor shall use a data management process to:

a. Prevent duplication of previously developed data

b. Ensure that the developed data meets contract requirements

c. Ensure that contract data is delivered in a timely manner

d. Ensure data integrity

e. Ensure that the delivered data is the latest revision of the data

f. Document, manage, and control personnel access

g. Elicit government input during requirements definition, system design, and implementation of any proposed changes to LIMES

h. Provide the current status of all contract data requirements.

2.2.1.10. The contractor shall incorporate interoperability between platforms and best industry standards (open systems architecture) into LIMES.

2.2.1.11. The contractor shall ensure that all non-LISC contractor user access requires government sponsorship.

2.2.1.12. The contractor shall perform the following functions with LIMES:

a. Generate complete and accurate Dynamic Information (DI) and Automated Data Products (ADPs)

b. Provide DI and ADPs to the government

c. Revise DI and ADPs when errors in them are discovered

d. Retain DI and ADPs IAW LISC requirements

e. Provide operational availability 24 hours a day, 7 days a week (24/7)

f. Provide user tools (e.g., search and query functions).

2.2.1.13. The contractor shall allow external contractors to access LIMES as approved by the government.

2.2.1.14. The contractor shall provide controlled access, as the controls exist today, on current government-provided systems, to LIMES.

2.2.1.15. The contractor shall use LIMES to store information on the following areas, at a minimum:

a. CWBS

b. Staffing data and organizational structure

c. O&M data and procedures

d. Metrics and performance reporting

e. Authorized work

f. Quality management

g. Financial management

h. Property and supply management

i. Configuration management and data management

j. Training management

k. Safety management

l. Risk management

m. Contract Data Requirements List (CDRL) and associated reporting

n. Environmental database and reporting

o. Project status reports

p. Status of anomalies, failures, and other such problems

q. Status of systems that are supporting launches

r. Maintenance schedules

s. Reliability and integrity trends in terms of system performance

t. System manuals and maintenance procedures

u. Property and supplies

v. Interface to the Geographic Information Management System (GIMS) (ER)

w. Interface to the Geographic Information System (GIS) (WR).

2.2.1.16. The contractor shall maintain all CDRL data within LIMES.

2.2.1.17. The contractor shall post all non-deliverable data required to satisfy requirements of this PWS to LIMES to include datasets contained natively within software tools. The contractor shall provide government personnel access to software tools that generate non-deliverable data that is not published in a common readable format.

2.2.1.18. The contractor shall import WR data management system flat files into LIMES.

2.2.1.19. The contractor shall maintain Range mission-required software applications hosted on the base enterprise network and on the base infrastructure.

2.2.1.19.1. The contractor shall use government standards in the maintenance and operation of web-based information and applications IAW AFI 33-129.

2.2.1.19.2. The contractor shall gain COR approval for use of non-standard software.

A003 Source Code and Executables Non-CI

A004 Software User Manual Non-CI

A005 Database Design Document Non-CI

A006 Software Design Document Non-CI

A009 Data Accession List (DAL)

A010 LISC Data Management Plan

A011 LISC Information Management Enterprise System Plan (LIMES)

2.3. Provide Adequate Financial Information for Government Insight and Cost Management

2.3.1. The contractor shall utilize a financial accounting system for LISC cost management.

The contractor is responsible for performing all tasks necessary to fulfill this requirement. At a minimum, this work includes:

2.3.1.1. The contractor shall ensure that corrections and adjustments to cost and financial data are completed within 30 days following a government request.

2.3.1.2. The contractor shall have adequate internal controls so that all data in the transaction database will be supported by documentation and cross-referenced.

2.3.1.2.1. The contractor shall ensure a comprehensive audit can be accomplished.

2.3.1.3. The contractor shall ensure that cost adjustments from prior fiscal-year tasking reflect fiscal integrity and are reported with current-month transactions.

2.3.1.3.1. The contractor shall trace cost adjustments to the adjusted fiscal-year recorded balances.

2.3.1.3.2. The contractor shall prevent negative balances from appearing in the year-to-date fields for the current fiscal year.

2.3.1.4. The contractor shall ensure financial and labor hour information are provided to the ER and WR JOCAS IAW CDRL A012.

2.3.1.5. The contractor shall provide all Non-CDRL data IAW PWS Section 2.2.1.17.

A012 Job Order Cost Accounting System Report (JOCAS II)

A013 Funds And Man-Hour Expenditure Report

2.3.2. The contractor shall develop incremental and unambiguous cost estimates.

The contractor is responsible for performing all tasks necessary to fulfill this requirement. At a minimum, this work includes:

2.3.2.1. The contractor shall prepare necessary cost estimates on an annual and per mission basis.

2.3.2.2. The contractor shall prepare cost estimates as directed by the Contracting Officer Representative (COR) (e.g., changes in task or schedule requirements, and future-year planning).

2.3.2.3. The contractor shall support the COR as directed in responding to short-notice suspenses regarding budget drills, estimates, analysis, and historical data.

Note: Responses include, for example, work scope reduction or increase, impact on target cost, ceiling price, and Service Summary Item (SSI).

2.3.2.4. The contractor shall provide all Non-CDRL data IAW PWS Section 2.2.1.17.

A015 Launch and Non-Launch Related Estimates

A016 Year End Cost Estimate Report

A017 Annual Recurring Support Cost Estimates

2.3.3. The contractor shall deliver financial reports for detailed, periodic, accurate, and actual cost data.

The contractor is responsible for performing all tasks necessary to fulfill this requirement. At a minimum, this work includes:

2.3.3.1. The contractor shall provide requested information to the COR within one working day of receiving an ad hoc cost data request.

2.3.3.1.1. The contractor shall provide a course of action and/or justification to the COR if the request cannot be fulfilled within one working day.

2.3.3.2. The contractor shall provide all Non-CDRL data IAW PWS Section 2.2.1.17.

A019 Contract Funds Status Report (CFSR)

A020 Sustaining Engineering Cost Report

A021 Supplies and Equipment Summary Report

A022 Monthly Instrumentation Cost Report

A023 Launch Operations and Scrub Costs

A024 Launch Operations Cost Report

A025 50/50 Requirements Report

2.4. Provide Continuous Monitoring and Improvement of Contractor Performance of LISC Services

2.4.1. The contractor shall establish, document, implement, and maintain a Quality Management System (QMS) and continually improve the system’s effectiveness.

The following are applicable to the sub-tasks below: International Organization for Standardization

(ISO) AS9100.

The contractor is responsible for performing all tasks necessary to fulfill this requirement. At a minimum, this work includes:

2.4.1.1. The contractor shall ensure that the QMS is in place and operational no later than (NLT) 90 calendar days after Contract Start of the performance for Phase-in.

2.4.1.2. The contractor shall ensure that the QMS meets the intent of ISO AS9100 or an equivalent standard.

2.4.1.3. The contractor shall make QMS documentation and data available to the CO or COR for review.

2.4.1.3.1. The contractor shall ensure records are intact and available to the COR for the life of the contract.

2.4.1.3.2. The contractor shall ensure that QMS documentation includes, at a minimum, information on all QMS procedures, training and certification records, completed work orders, results of inspections and audits, nonconformance data, and corrective and preventive action records.

2.4.1.4. The contractor shall use the QMS proactively to ensure that LISC activities meet contract requirements.

2.4.1.5. The contractor shall provide an acceptable cause and corrective action response to every government-issued non-conformance notice and Corrective Action Request (CAR).

2.4.1.6. The contractor shall team with the COR to develop a self-assessment methodology that communicates the contractor’s achievement of the Service Summary Item (SSI) Performance Objectives and associated thresholds.

2.4.1.6.1. The contractor shall identify deviations from SSI Performance Objectives, the reasons for the deviations, and recommendations for correcting or resolving the deviations.

2.4.1.6.2. The contractor shall make QMS data accessible to the Contracting Officer (CO), PM, and Contracting Officer Representative (COR).

2.4.1.6.3. The contractor shall brief the self-assessments at monthly business reviews and quarterly program reviews.

2.4.1.7. The contractor shall provide all Non-CDRL data IAW PWS Section 2.2.1.17.

A026 Technical Issues/Concerns and Accomplishments Report

A027 Quality Management Plan

2.5. Provide Management of LISC-Employed Personnel

2.5.1. The contractor shall provide positive management of employees executing LISC tasks.

The following are applicable to the…