SSPARS_PWS.pdf

Solid State Phased Array Radar System

(SSPARS)

Performance Work Statement (PWS)

FA2517-06-C-8001

Attachment 1

22 May 2006 (Revision 51, Dated 3 March 2014)

SSPARS, Atch 1 P00401

SSPARS PERFORMANCE WORK STATEMENT (PWS)

TABLE OF CONTENTS

SECTION 1 SSPARS SERVICE REQUIREMENTS

CHAPTER 1 SSPARS OVERVIEW

CHAPTER 2 RADAR OPERATIONS SUPPORT

CHAPTER 3 TECHNICAL ASSISTANCE, EXERCISES, TESTING,

SIMULATION TRAINING AND EMERGENCY MANAGEMENT

CHAPTER 4 MILITARY SATELLITE COMMUNICATIONS

CHAPTER 5 SPACE SYSTEMS MAINTENANCE MANAGEMENT

CHAPTER 6 ELECTRONICS SYSTEMS MAINTENANCE & PMEL

CHAPTER 7 SUPPLY

CHAPTER 8 FUELS

CHAPTER 9 COMMUNICATIONS OPERATIONS AND MAINTENANCE

CHAPTER 10 ENVIRONMENTAL, SAFETY AND OCCUPATIONAL HEALTH

CHAPTER 11 MEDICAL AND PUBLIC HEALTH SERVICES

CHAPTER 12 CIVIL ENGINEERING

CHAPTER 13 VEHICLE MANAGEMENT

CHAPTER 14 TRAFFIC MANAGEMENT

CHAPTER 15 SERVICES

CHAPTER 16 INDUSTRIAL, PHYSICAL AND OPERATIONAL SECURITY

CHAPTER 17 INFORMATION MANAGEMENT

CHAPTER 18 SEVERABLE WORK

CHAPTER 19 PHASE-IN/PHASE-OUT

SECTION 2 SERVICE DELIVERY SUMMARY

SECTION 3 GOVERNMENT-PROVIDED RESOURCES AND SERVICES

SECTION 4 GENERAL REQUIREMENTS

APPENDIX A SSPARS PWS ACRONYMS

APPENDIX B SSPARS PWS DEFINITIONS

SSPARS, Atch 1 P00401

SECTION 1

SOLID STATE PHASED ARRAY RADAR SYSTEM (SSPARS) SERVICE REQUIREMENTS

CHAPTER 1

SSPARS OVERVIEW

1.0. SCOPE. The Solid State Phased Array Radar System (SSPARS) Program is comprised of five

(5) radar Sites at geographically-separated locations in the Northern Hemisphere: Beale Air Force Base (AFB) California (CA), Cape Cod Air Force Station (AFS) Massachusetts (MA), Clear AFS Alaska (AK), Royal Air Force (RAF) Fylingdales United Kingdom (UK) and Thule Air Base (AB) Greenland (GL). Combined, these Sites provide the following capabilities: Sea-Launched Ballistic Missile Warning, Ballistic Missile Early Warning and Space Surveillance. In the future, services will also be provided in support of the Ground-Based Midcourse Defense (GMD) Program. The Upgrade Early Warning Radar (UEWR) Installation is ongoing in support of the GMD Program.

Once the UEWR system is accepted, maintenance will continue to be at the organizational and intermediate level.

1.1. SERVICES AND SUPPORT. The SSPARS has a unique history of Contractor and Government support. Radar operations are performed by Air Force (AF) members assigned to the Sites. SSPARS contracted services vary by Site and are explained below. The Contractor provides all necessary personnel, administrative, financial, and managerial resources necessary on a continuous, 24-hours-a-day, 7-days-a-week (24/7) basis to meet mission requirements as specified in this Performance Work Statement (PWS). In a time of crisis, other services to increase the security and well being of the Site may be required. These services will be determined and requested by the Installation/Site Commander and the Contracting Officer (CO). In addition to stated requirements in performance of this PWS, the Contractor is expected to interface with other Contractors, Subcontractors, and/or Government agencies in support of all programs and efforts dealing with evolution and/or operation of systems and equipment, as well as in providing day-to-day Site support services. Unless otherwise specified, the stated requirements pertain to all Sites;

inclusions or exclusions will be clearly stated in individual PWS paragraphs.

1.2. CONTRACT REQUIREMENTS AND SITES SUPPORTED:

1.2.1. Clear AFS AK; 13th Space Warning Squadron (13 SWS); will be designated the 213th SWS under the Alaska Air National Guard (AKANG). Clear AFS AK was established in the early 1960's as a Ballistic Missile Early Warning System (BMEWS) Site. The primary mission is to provide early warning of intercontinental ballistic missiles and sea-launched ballistic missiles to the Missile Warning Center at North American Aerospace Defense Command (NORAD) at Cheyenne Mountain AFS (CMAFS); United States Strategic Command (USSTRATCOM), Offutt AFB and National Command Authorities. The secondary mission is to track near-earth satellites. This mission allows the Space Control Center to keep manned objects, like the Space Shuttle and International Space Station, out of harm’s way and to closely monitor objects re-entering the earth’s atmosphere close to populated areas.

1.2.1.1. The Clear AFS Site is located approximately 85 miles south of Fairbanks AK and is considered a remote assignment. SSPARS contracted services encompass base support services including management of civil engineering and environmental functions, transportation, supply, medical services, food service, sensitive and non-sensitive communications, radar and mission computer maintenance, and the precision measurement equipment laboratory. The Installation receives limited support from Eielson AFB located near Fairbanks, and Elmendorf AFB located near

SSPARS, Atch 1 Page 1 P00401

Anchorage.

1.2.1.2. In accordance with a Memorandum of Agreement (MOA) between the Air Force Space Command (AFSPC) Commander and the National Guard Bureau, a manpower transfer from AFSPC to the AKANG and a mission transfer from the 13 SWS to the 213 SWS AKANG began in FY04.

The manpower transfer is occurring gradually, with AK Air National Guardsmen occupying most AF billets by the end of FY05. The 13 SWS will be inactivated at the end of the third quarter of FY06 and the 213 SWS will be activated. When the 213 SWS Commander assumes command, one of two remaining regular AF billets will be designated as the Installation Commander. This initiative improves the quality of life for AFSPC regular AF members by removing a remote assignment, and increases longevity and continuity of personnel at this critical Integrated Tactical Warning/Attack Assessment (ITW/AA) location.

1.2.2. Cape Cod AFS MA (6 SWS). The 6 SWS is a Sea-Launched Ballistic Missile Warning System (SLBMWS) Site primarily responsible for detecting sea-launched ballistic missiles fired from submarines in the Atlantic Ocean and also reporting the information to NORAD’s Missile Warning Center, CMAFS, USSTRATCOM, Offutt AFB, and National Command Authorities. Additionally, the 6 SWS tracks earth-orbiting satellites.

1.2.2.1. The unit was activated in October 1978 under the control of NORAD and Aerospace Defense Command (ADCOM) and after numerous reorganizations became the 6 SWS under the 21st Space Wing (21 SW). The 6 SWS occupies over 120 acres of what was once Otis AFB (now the Massachusetts Military Reservation). The squadron receives some Host-Tenant support from Hanscom AFB, Otis ANG and the U.S. Coast Guard Station.

1.2.2.2. SSPARS contracted services at this location include radar and mission computer maintenance, sensitive communications and limited civil engineering, network management, supply, logistics support services, environmental, and occupational health.

1.2.2.3. This Site is the focus of local political activist movements due to perceived environmental concerns. The Site commander attends local community involvement meetings to maintain a “good neighbor” posture.

1.2.3. Beale AFB CA (7 SWS). The 7 SWS is a SLBMWS Site primarily responsible for detecting sea-launched ballistic missiles fired from submarines in the Pacific Ocean and also reporting the information to NORAD’s Missile Warning Center, CMAFS, USSTRATCOM, Offutt AFB, and National Command Authorities. Additionally, the 7 SWS tracks earth-orbiting satellites.

1.2.3.1. The unit was also activated in October 1978 under the control of NORAD and ADCOM, and, after numerous reorganizations, became part of the 21 SW. The 7 SWS is a tenant on Beale AFB, which is located in north-central California, midway between San Francisco and Reno, Nevada. Sacramento is 40 miles to the south. The squadron receives Host-Tenant support from the 9th Reconnaissance Wing, Beale AFB.

1.2.3.2. SSPARS contracted services at this location include radar and mission computer maintenance, sensitive communications, limited civil engineering, network management, supply and logistics support services.

1.2.4. RAF Fylingdales UK. Royal Air Force (RAF) Fylingdales is located in the North York Moors National Park near Pickering, North Yorkshire in the United Kingdom (UK). The Ballistic Missile Early Warning System, Site III, was constructed at the site in the early 1960s consisting of three

SSPARS, Atch 1 Page 2 P00401 radar tracking dishes. These dishes were replaced by a Solid State Phased Array Radar in 1992 and upgraded to an Upgraded Early Warning Site in the mid-2000s.

1.2.4.1. The RAF operates and maintains the radar at RAF Fylingdales to conduct ballistic missile early warning operations, provide support to US missile defense, and conduct space surveillance operations. Radar tasking comes from both the United Kingdom and the United States and all data is shared with both nations.

1.2.4.2. SSPARS contracted services include operation and maintenance of US communications systems including local area network management functions.

1.2.5. Thule AB GL (12 SWS). The 12 SWS is primarily responsible for providing attack warning and assessments of both sea-launched and intercontinental ballistic missiles. Additionally, the squadron tracks nearly 9,500 objects in Earth’s orbit.

1.2.5.1. In 1946, a combined Danish-American radio and weather station was established at Dundas, later called Thule. International tensions prompted Denmark and the US to sign a defense treaty allowing the construction of a complete AB. Thule, much as it exists today, was built during the summers of 1951 and 1952. The unit was activated in 1961 with the establishment of the BMEWS Site. Several commands were responsible for the base before AFSPC took control in 1983 and the unit was redesignated as the 12 SWS in 1992.

1.2.5.2. SSPARS contracted services include radar and mission computer maintenance, PMEL, network management (for the entire installation), land mobile radio, and spectrum management with limited SSPARS Site supply and logistics support services. These activities are limited to US firms due to the classified nature of the work involved. Base support services, such as transportation, fuels, environmental management, civil engineering, health, morale/welfare, and food services are provided under a separate Base Maintenance Contract (BMC) supporting the 821st Air Base Group

(821 ABG).

1.3. GENERAL REQUIREMENTS. In the event of a crisis declared by the President of the United States and/or the Secretary of Defense, contract performance will continue for all the PWS requirements except the tasks in PWS Chapters 15, 17, and 18. Personnel performing the remainder of the PWS tasks are considered “mission essential Contractor personnel”.

1.3.1. Outside Agency Support. Provide technical assistance and advice to other Contractors or Government agencies to support design, development, maintenance, revision, and installation of new facilities, systems, documentation or equipment within existing PWS areas of expertise. This includes, but is not limited to, the Missile Defense Agency (MDA) support and the System Engineering and Sustainment Integrator (SENSOR) contract managed by Air Force Materiel Command (AFMC). The SENSOR contract is responsible for the sustainment and upgrade of mission systems, including those supported by this contract.

1.3.1.1. Outside agency support includes reviewing and providing advice on documents such as the following examples: Concepts of Employment, Concepts of Operation, Engineering Change Request proposals, Host Base Tenant Support Agreements, Interface Control Documents, International Arrangements, Memorandums of Agreements, Memorandums of Understanding, Program Support Agreements, Technical Orders, Technical Proposals, Technical Reports, Technical Solutions, Test Plans, Security Classification Guides, System Description documents, System Manuals, and Requirements documents.

SSPARS, Atch 1 Page 3 P00401

1.3.1.2. Outside agency support includes facilitating meetings, providing introductions, and assisting outside agencies in becoming familiar with local and/or host nation specific requirements that may be unfamiliar to the agency

1.3.2. Meetings, Briefings, Tours, and Escorts.

1.3.2.1. Site Program Management Review (SPMR). Brief the following program elements in a monthly joint USAF/Contractor SPMR meeting: system availability metrics (see Ch 2, PWS para 2.2.8.), supply and other logistical support status, electronic system and civil engineering projects, mission critical system outages, and any other operational/maintenance problem areas. Include recommendations and any corrective actions taken.

1.3.2.2. Familiarization Briefings And Tours. Conduct Site briefings and tours when requested by the Installation/Site Commander and provide technical orientation/familiarization briefings.

Provide a short briefing on radiation hazards and areas that pose a threat to human safety within the Installation/Site.

1.3.2.3. Escort Support. Provide escort support on the Installation/Site as requested by the Site/Installation Commander. Provide escort support, except in circumstances where the escort support will cause mission degradation, or support is required in excess of three (3) consecutive days per visit. Escort requirements for any single project are for a maximum of three (3) days, either consecutive or intermittent.

1.3.3. Referenced Publications. Publications preceded by “in accordance with”, or “IAW,” are mandatory requirements upon the Contractor and are incorporated by reference into the PWS.

Comply with the current version of the referenced publications listed at the end of each chapter.

Notify the CO within 30 days of receipt of revisions, changes, supplements, and notifications of rescission (including referenced publications in the PWS and federal, state and local regulations and statutes), if there is a cost impact resulting from such revisions, changes, supplements, and rescissions. If the CO is not notified, and the Contractor performs IAW such revisions, changes, supplements, and rescissions, it will be at no increase to the contract’s price. Revisions, changes, supplements, and rescissions to publications that increase cost will not become effective until directed by the CO. Comply with all applicable policies and directives identified by Site support agreements. Advise the Installation/Site Commander of any required support not reflected in the Host Base or command policies and directives. Maintain all mission system equipment IAW user manuals or technical orders (TOs).

1.3.4. Contract Data Requirements Listings (CDRLs). Prepare and distribute data in CDRLs (DD Forms 1423) referenced in PWS Sections 1 and 4 and provided in Sec J, Exhibit A.

1.3.5. Documentation, Correspondence and Reporting Requirements. Maintain all program documentation for Government review upon request (electronic format is preferable via the Web or other means). Unless otherwise directed (i.e., in CDRLs), use the Contractor’s own format for reports, data, logs, histories, and other documentation created in performance of PWS requirements.

1.3.6. electronic Contractor Manpower Reporting Application (eCMRA). Report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for AFSPC/21SW via a secure data collection site. (CDRL 0004)

SSPARS, Atch 1 Page 4 P00401

SSPARS PWS REQUIREMENTS

SITE

FUNCTION

C le ar

A

FS

K

SW

S

C ap e C od

FS

M

6S

W S

B ea le

FB

C

7S

W S

Th ul e

B

G L

SW

S

1A B

G

R

F Fy lin g-da le s U

K

Radar Operations Support – Chapter 2

X X X X /

Systems Analysis X X X X Software Config Control & Version Management

X

Media Management X X X X Tech Assistance, Exercises, Testing, Simulation Training, & FSTR – Chapter 3

X X X X /

MILSATCOM –

Chapter 4

X X X X X

C-E Maintenance Mgt – Chapter 5

X X X X X

ESM (PMEL) –

Chapter 6

X /

Supply – Chapter 7 X X X / / Fuels – Chapter 8 X / Communication O&M – Chapter 9

X

LAN/WAN X X / X /

Ops X X / X /

Comm Center Ops X X X X X Crypto Keying X X X /

Telephones X X X

VTC X

Tech Control/Patch-Test X X X

LMR X X /

Frequency Management X X / X

TV X

ESOH – Chapter 10 X Environmental Mgt X X

Occ Health&Ind Hygiene Plan

X X X

Monitoring Program X X X Radiation Safety X X X X

Medical and Public Health – Chapter 11

X

Civil Engineering – Chapter 12

X

Operations & Maint X X X Work Requests X X X

Real Property Mgmt X X X /

HVACR X X X

POL Storage X X / Key Control X X X X

SSPARS, Atch 1 Page 5 P00401

Civil Engineering – Chapter 12 (cont.)

Power X X

SSUPS X X X X

Fire Alarm & Suppression X X X Elevators X X X

Road/Parking/Paved Areas/Grounds

X X

Roads & Grounds X X X Snow Removal X X

Signage X X As-Built Drawings X X X

Refuse Collections X X Engineering Services X X X

Appliances/Fitness Equip X X X Custodial X X X /

Fire Prevention X X X X X Corrosion Control X X X

Roof Management X X Railroad Maintenance X

Unaccompanied Housing X Construction Services X

Vehicle Mgt – Chapter 13

X

Traffic Mgt – Chapter 14

X X X X

Personal Property X Services – Chapter 15

Food Service X

MWR X

Industrial, Physical & Operational Security – Chapter 16

X X X X X

IDS X X X

Information Mgt – Chapter 17

Records Mgt/FOIA X Mail Pickup X X

Publications/Forms X

TODO X X

Severable Work – Chapter 18

X X X X X

Phase-In/Out – Chapter 19

X X X X X

X = This service fully performed / = This service partially performed

*Note: Information in this matrix is not all-inclusive. The individual PWS chapters should be thoroughly reviewed to determine the level of service required at each location.

SSPARS, Atch 1 Page 6 P00401

CHAPTER 2

RADAR OPERATIONS SUPPORT

2.0. GENERAL (Does not apply to RAF Fylingdales, except paragraphs (paras) indicated below). Provide technical services, operations support and maintenance of Site equipment to meet radar mission requirements on a continuous basis.

Service Delivery Summary Items

Chapter 2 – Radar Operations Support Performance Objective PWS Reference Performance Threshold

Radar Operational Availability.

Maintain an overall Radar Operational Availability (Ao).

Para. 2.1. Ao of not less than 99% each calendar month

Calibration and System Data. (Applies to Beale AFB, Cape Cod AFS, and Clear AFS).

Implement and maintain a calibration program showing changes, impacts and corrective actions taken to ensure the sensor stays within required system specifications.

Para 2.3.5. 100% compliance for 2-week average of range, azimuth, and elevation errors staying within specified limits.

Maintain accuracy within 100 feet (30.48m.) radar range, 1 milliradian (.0573 degrees) of Azimuth, and 1 milliradian (.0573 degrees) of elevation for qualifying satellites per ESD/SCT-0001A, para 3.2.1.3.6.1.

Assessment Items Chapter 2 – Radar Operations Support

Assessment Item PWS Reference Assessment Threshold Cannibalization Approvals. Ensure all cannibalization actions are approved.

Para 2.2.7. 100% compliance

Cannibalization Repair.

Repair cannibalized equipment.

Para 2.2.7. 100% compliance within 24 hours of when the parts are received

2.1. EQUIPMENT AVAILABILITY. Maintain an overall Radar Ao each calendar month of not less than 98% to meet mission operational requirements defined in STRATCOM Directive (SD) 505-1 (S) Volumes (Vol) I and II. (Ao rate of not less than 99% each calendar month effective12 months after contract start, 1 Oct 07). Ao is expressed as a percentage (%) and represents that portion of time the system is performing its assigned missions based on Contractor liable downtime (CLD) relative to a specified operating time.

SSPARS, Atch 1 Page 7 P00401

2.1.1. Ao Calculation. The Ao is calculated on a monthly basis as follows:

Ao = Error! Bookmark not defined.(Operating Time- CLD) x 100 Operating Time

Where the terms of the equation are defined as follows:

2.1.1.1. Downtime. Any mission degradation that results in Operations Capability (OPSCAP) RED time as defined in Air Force Space Command Instruction (AFSPCI) 10-1205(S).

2.1.1.2. Contractor Liable Downtime (CLD). The Contractor is liable for downtime except for the following:

2.1.1.2.1. Downtime scheduled in the monthly maintenance schedule and approved by the Installation/Site Commander and higher headquarters as being non-Contractor liable. Scheduled downtime is not counted against the Contractor, nor does it count for the Contractor in cases where the O&M Contractor scheduled the downtime. (See PWS paragraph 2.1.1.3, Operating Time.)

2.1.1.2.2. Downtime caused by a Missile Warning Operations Center (MWOC) military personnel error.

2.1.1.2.3. Downtime due to a higher headquarters priority.

2.1.1.2.4. Downtime caused by events outside the Contractor's control may be determined to be non-Contractor liable by the CO (with inputs from the Installation/Site Commander, MWOC Crew, Quality Assurance Evaluator (QAE), etc.). For example, downtime caused by unobtainable spare parts may be determined to be non-Contractor liable where the Contractor has attempted to keep adequate bench stock while properly planning ahead for parts deficiencies and using the procedures within SBSS, but due to problems beyond the Contractor’s control, those parts have not been delivered.

2.1.1.3. Operating Time. The amount of time the mission system is required to be available - 24 hours per day times the number of days in the month minus Contractor scheduled downtime.

Example: Month: April (30 days) Number of Minutes: 30 X 24 X 60 = 43,200 minutes Total Scheduled Downtime for April: 12 hours 30 minutes (Assume 2 hrs 30 min was used for Cat-A testing by Cheyenne Mt, in this example.)

O&M Contractor Scheduled Downtime in April: 10 hours = 600 minutes * Operating Time for April: 43,200 - 600 = 42,600 minutes

* If the Government or an outside Contractor scheduled the downtime, and the O&M Contractor was able to use it to their advantage, it will not be considered O&M Contractor Scheduled Downtime.

2.1.1.4. Ao Example. Using the data in PWS paragraph 2.1.1.3. for Operating Time, and a CLD of 1 hour and 30 minutes (90 minutes) for April, here is the Ao calculation for April:

Ao = Operating Time - CLD x 100 = 42,600 - 90 x 100 = 99.79% Operating Time 42,600

SSPARS, Atch 1 Page 8 P00401

2.2. MISSILE WARNING OPERATIONS CENTER (MWOC) SUPPORT REQUIREMENTS.

Respond to the direction of the MWOC Crew Commander (CMDR) or MWOC Crew Chief (CCH) in support of MWOC requirements and operating procedures found in AFSPCI 10-1205(S). Perform the following:

2.2.1. Maintenance Monitor Console Operator (MMCO). Establish communications with the MWOC within ten (10) seconds and respond within thirty (30) seconds to calls for Site reporting events.

2.2.2. Configuration Control. Maintain missile warning equipment in optimum configuration.

Notify the CMDR/CCH of all temporary or permanent hardware configuration changes.

2.2.3. Technical Support. Provide technical support for radar operations. Identify and notify the CMDR/CCH of all system malfunctions or anomalies. Provide a written review of operations anomalies and discrepancies as requested by the Operations Officer or Installation/Site Commander within five (5) calendar days of the request. Evaluate and provide written technical analysis on any system modification/upgrade proposal or recommendation to the requesting organization.

2.2.4. Electromagnetic Interference (EMI). Immediately advise MWOC personnel of external or internal system interference and track interference until it changes or ceases. Coordinate termination of internal interference and provide signal characteristics of external interference to the MWOC for EMI reporting.

2.2.5. Emergency Actions (Also applies to RAF Fylingdales). Perform emergency actions as requested by the CMDR, CCH, or Crisis Response Element (CRE).

2.2.6. Mission Computer Equipment Status (Except RAF Fylingdales). Operate and maintain all mission computer equipment and peripherals needed to support radar and space operations mission IAW TOs 31P6-2FPS123 series or 31P6-2FPS132 series (as applicable).

2.2.6.1. Monitor and report to the CMDR or CCH (or in the case of RAF Fylingdales, the Communications Center) any equipment failures, maintenance actions, and all equipment and communications status that could cause system degradation or adversely impact the mission.

2.2.6.2. Mission System Actions. Coordinate with the CMDR or CCH on power shutdown, changeover, system reconfiguration and restoration actions that could impact operations. Respond to MWOC requests for information, and provide direct operating support of the MWOC in areas of system operations and equipment control.

2.2.6.3. Mission Computer Equipment Inventory. Perform inventory control and account for mission computer equipment on the Custody Authorization/Custody Receipt Listing (CA/CRL). At RAF Fylingdales, account for MILSATCOM equipment.

2.2.7. Cannibalization. Cannibalization should only be used as a last resort and before taking such action, all other support avenues must be exhausted. Ensure all cannibalization actions are approved and documented using the instructions in Air Force Space Instruction (AFSPCI) 21-108, paras 5.6.1, 6.1.5, 6.1.5.1, and 6.1.5.2. Cannibalization of depot level assets may only be authorized by the Item Manager and/or the Installation/Site Commander. Coordinate with the Depot and order replacement parts within one day of approval and repair cannibalized equipment as soon as the parts are received, but not later than 24 hours after receipt. Coordinate all correspondence regarding supply issues through the unit Supply QAE.

SSPARS, Atch 1 Page 9 P00401

2.2.8. Monthly Metrics Briefing. Provide a Monthly Metrics Briefing to the Installation/Site Commander that includes trend analysis, status of equipment, areas of concern for redundant equipment, and calibration issues (CDRL 0201). Six months after contract start and every 6 months thereafter, brief whether antenna primary transmit and receive side lobes are in or out of limits.

2.2.9. (Applies to Beale AFB and Thule AB only) Missile Defense Scheduling, Tracking, and Reporting. Provide scheduling for Missile Defense Agency (MDA) operational events; maintain records tracking the MDA monthly operational rate and report MDA data as are performed for the radar system Aₒ. (See PWS paragraph 2.1.1, and 2.1.1.4, Aₒ Calculation and Example).

2.3. SPACE SURVEILLANCE SUPPORT. Provide space surveillance support. For an understanding of the reporting requirements, see SD 505-1(S) Vol I and II and local procedures.

Perform the following:

2.3.1. RESERVED. (P00114)

2.3.2. Real-Time Operational Support. Respond to real-time requests for operational support by the CMDR/CCH.

2.3.3. Job Requests. Process job requests upon request of the CMDR/CCH.

2.3.4. Computer Products. Prepare the following computer printouts and provide to the

CMDR/CCH:

2.3.4.1. Pass Schedules. The twenty-four (24) hour pass schedules of satellites identified by the MWOC Crew at least one hour prior to change of Zulu day, dependent upon the availability of the off-line system and priority of tasks assigned by the CMDR/CCH.

2.3.4.2. Daily Sensor Taskings. Daily sensor tasking response reporting that shows a compilation of satellites by category, passes scheduled, passes not attempted, passes not accountable, passes accountable, and passes acquired.

2.3.4.3. Weekly Usage Metrics. Weekly usage metrics for missile warning events and space surveillance tracks categorized by the number of missile events and number of Category 1 and Category 2 passes and an overall percentage, spacetrack hack rate, and radar availability rates (for example, Ao).

2.3.5. Calibration and System Data. Implement and maintain a calibration program showing changes, impacts and corrective actions taken to ensure the sensor stays within required system specifications. System specifications are available in the following:

2.3.5.1. (Applies to Beale AFB, Cape Cod AFS, and Clear AFS). ESD/SCT-0001A, para 3.2.1, and the B-5 and C-5 Specifications, Computer Program Configuration Item (CPCI)-2, G264302-2 Parts I and II.

2.3.5.2. (Applies to Thule AB). ESD/BMEWS-0005C-A, para 3.2.1 and the B-5 and C-5 Specifications, CPCI-2, G165893-1, Parts I and II.

2.3.5.3. Reserved

SSPARS, Atch 1 Page 10 P00401

2.3.6. ON-SITE OPERATIONAL SYSTEM ANALYSIS. Monitor, analyze and document findings in performing systems analysis as indicated below.

2.3.6.1. Monitor:

2.3.6.1.1. Tactical files including the mission plan file, satellite catalog, and satellite task list for abnormal data or overflow.

2.3.6.1.2. Computer/radar O&M logs for system or operator errors.

2.3.6.1.3. Daily uncorrelated target (UCT) rates to the Site running UCT average to identify abnormal performance.

2.3.6.1.4. The fifteen (15) day library of Day, File, Error Log and Account File (DAETERM) listings, ensuring the Day File, Error Log, and Account File are properly updated and maintained.

2.3.6.1.5. System calibration, operability assessment test results, and other indicators which give an indication of system performance (such as the 1st Space Control Squadron (1 SPCS) website system calibration metrics).

2.3.6.2. Analyze occurrences of system outages or operational degradation (as defined in the Tactical Requirements Document or Operability Assessment Tests), to include the following:

2.3.6.2.1. False Launch and Impact Message or False Impacting Object Reports.

2.3.6.2.2. Abnormal daily UCT rates.

2.3.6.2.3. Indications of radar system degradation.

2.3.6.2.4. Uncommon computer halts or hangs.

2.3.6.2.5. CAT 1 satellite misses.

2.3.6.2.6. Electromagnetic interference (EMI).

2.3.6.2.7. Failure to track a real missile launch or significant portions of a real missile launch in coverage.

2.3.6.2.8. Other abnormal data, performance, and occurrences that may lead to a system failure.

2.3.6.2.9. Requests for information to support Site operations investigations by the DO, Operations Support, CMDR/CCH, or Installation/Site Commander.

2.3.6.3. Document:

2.3.6.3.1. Unusual and/or unique problems in a PR within 30 days of the anomaly or outage.

Maintain PR supporting data such as computer printouts and data tapes and make available for Government review upon request.

SSPARS, Atch 1 Page 11 P00401

2.3.6.3.2. Generate an SCF within thirty (30) days of the anomaly or outage (if needed for the anomaly or outage) using the instructions in 21 SWI 21-10401, paras 3.2.1 through 3.2.1.3 and maintaining references to any associated PR and all supporting data, such as computer printouts and data tapes. Also generate an SCF for system or software modifications as follows:

2.3.6.3.2.1. System/Software Modifications. Document proposed system/software modifications for corrective or preventive action as a result of analyses from paras 2.3.6.1. and 2.3.6.2., above, or any other proposed system/software modifications.

2.3.6.3.2.2. Installation of New Subarray Test and Element Test Constants. Document the rationale for the proposed change, results of tests that ensure system meets all internal system specifications for system calibration, operability, alignment and equipment checks in an Standard Change Form (SCF) prior to installing new software constants for the subarray test and the element test.

2.3.6.3.3. Provide a written review of operations anomalies and discrepancies as requested by the Operations Officer or Installation/Site Commander within five (5) calendar days of the request.

Evaluate and provide written technical analysis on any system modification/upgrade proposal or recommendation to the requesting organization.

2.3.6.4. Operations Approval Review Board (OARB). Advise the Site OARB identifying and prioritizing new requirements for, and changes to, the operational system. Participate in system life-cycle activities such as program management reviews, design reviews, tests, and physical and functional configuration audits. Participate in unit Operational Review Panels (ORPs), Initial Assessments, Unit Review Boards (URBs), and Operational Review Boards (ORBs).

2.3.6.5. Emergency Computer Problems. Respond to emergency requests for assistance by the CMDR in cases of system or computer problems.

2.3.6.6. Modifications. Support the installation and evaluation of all software and hardware modifications.

2.3.6.7. Maintain System Documentation (Applies to Clear AFS and Thule AB Only). Maintain a copy of baseline and support documentation. Integrate changes to the baseline as required to assure software documentation reflects the operational and support baseline. Maintain the master copy of all software-related documentation and make available for Government review upon request.

2.3.6.8. Software Configuration Control and Operational Test and Evaluation (OT&E).

Participate in planning, development, test and evaluation (DT&E), perform OT&E to determine operational effectiveness and suitability of a system under realistic operational conditions, and determine if specified operational performance and supporting requirements have been satisfied.

Schedule tests using the information provided in 21st Space Wing Instruction (SWI) 10-202.

2.3.6.9. Software Configuration Control and Software Version Management Functions (Applies to Clear AFS Only). At Clear AFS, perform software configuration control and OT&E procedures for ITW/AA Missile Warning and Space Surveillance Assets IAW 21 SWI 21-10401.

Perform functions of the OARB Secretariat and participate in the software version design, development and testing process. Perform systems analysis and data reduction functions. Review Site generated reports, identify problem areas and submit Problem Reports (PRs), SCFs and System Advisories, as necessary. Analyze data in the event of an anomalous situation, determine

SSPARS, Atch 1 Page 12 P00401 possible cause and recommend corrective action. Maintain existing baseline software and assist in DT&E of new software version releases. Evaluate system performance IAW the Tactical Requirements Doctrine (TRD).

2.3.6.10. Information Assurance (IA) Controls. Maintain situational awareness and initiate actions to improve or restore IA posture as well as conduct annual security reviews of all IA controls and a test of selected IA controls IAW DoDI 8500.2, Enclosure 4.

2.4. Mission Computer Media Management. The contractor shall:

2.4.1. Establish a local procedure to ensure all media is created, handled, stored, and protected IAW industry standards for the types of media in use (magnetic, optical, flash, etc.).

2.4.2. Label and protect media as prescribed in AFI 31-401, chapter 4 and 5.

2.4.3. Maintain dispatch records. Accomplish sanitization or destruction of classified media when no longer required IAW AFSSI 8580 (FOUO).

2.4.3.1 (Applies to Beale AFB, Thule AB, and Clear AFS) Mark and ship classified media according to AFI 31-401, Ch 6.

2.4.3.2 (Applies to Cape Cod AFS) Mark and ship classified media IAW local operating instruction

CCAFSOI 31-401.

2.4.4. Develop, maintain and execute a written site backup plan, approved by the O&M System Analyst and Information System Security Officer, to include maintaining a minimum of 30 days of archived virtual mission history tape files and procedures for placing and rotating critical archive data to a secure storage area physically separated from the primary media storage area. This plan will be reviewed annually and prior to operational acceptance of any modifications and upgrades which change the way system data is stored.

2.4.5. Maintain records that provide listings of the media on hand in the library, those temporarily out for cleaning or rehabilitation, media shipped for use elsewhere, those on hand belonging to another center or organization, and any media awaiting disposition.

2.4.6. Electronic Tape Transfer System (ETTS). Operate the ETTS using the ETTS User Manual.

2.5. Mission Computer System Facility Management. The contractor shall:

2.5.1. Set up local procedures for physical security and information protection.

2.5.2. Set up safety and fire practices.

2.5.3. Maintain and monitor environmental conditions according to equipment specifications and set up emergency procedures for environmental equipment failures. Facilities that have an energy management control system do not require recording devices.

2.5.4. Accomplish the preventive maintenance schedule specified in Technical Orders for all mission computer equipment.

SSPARS, Atch 1 Page 13 P00401

2.5.5. Janitorial Briefing and Escort. Protect equipment and media by providing safety and security briefings. Work center personnel must escort janitorial staff.

2.5.6. Toxic Hazard Notification. Ensure the Installation/Base fire chief is notified in writing of the location of all magnetic media and of toxic fume hazards.

2.6. (Applies to Beale AFB and Thule AB). Perform UEWR System Administrator functions with overall technical responsibility for managing and maintaining the UEWR Prime Mission Equipment (PME), UEWR Simulator Tester (ST) computer, and associated network equipment.

2.6.1. Maintaining system configuration with respect to UEWR applications, Mission Application Software (MAS), Signal Processing Software (SPS), Receiver-Exciter Software (RES), and Data Reduction.

2.6.1.2. Develop and implement backup strategies and system restoration procedures.

2.6.1.3. Assist Information System Security Officer (ISSO) in reviewing system security information and maintain relevant security accountability logs and records.

SSPARS, Atch 1 Page 14 P00401

PUBLICATIONS CROSS REFERENCE

Chapter 2 – Radar Operations

Publications Publication Title Publication Para

References

PWS Para References

Location

SD 505-1, Vol I (S)

Space Surveillance Operations - Basic Operations

All 2.1. and 2.3. To view contact PM office after 29 Apr 05

SD 505-1, Vol II (S)

Space Surveillance Operations - Event Processing

All

2.1. and 2.3.

To view contact PM office after 29 Apr 05

AFSPCI 10-

1205(S)

Ground Based Missile Warning Sensor Operations

All

All

2.1.1.1.

2.2.

To view contact PM office after 29 Apr 05

21 SWI 21-10401 Configuration Control of Integrated Tactical Warning/Attack Assessment Missile Warning and Space Surveillance Assets

All

Paras 3.2.1.

through 3.2.1.3.

2.3.6.9.

2.3.6.3.2.

https://halfway.peters on.af.mil/publish/21S eries/21-10401.pdf

TO 31P6-

2FPS123 series

System Operator Manual, Phased Array Warning System, AN/FPS-

123(V1) (PAVE

PAWS 1), AN/FPS-

123(V2) (PAVE

PAWS 2), AN/FPS-

123(V7) (BMEWS

II)

All 2.2.6. To view contact PM office after 29 Apr 05

TO 31P6-

2FPS132 series

All 2.2.6. To view contact PM office after 29 Apr 05

AFSPCI 21-108 Air Force Space Systems Maintenance Management paras 5.6.1, 6.1.5, 6.1.5.1, and 6.1.5.2

2.2.7. http://www.e-publishing.af.mil/

ESD/SCT-0001A System Performance Specification

Para 3.2.1. 2.3.5.1. http://www.FedTeds.

gov

B-5 Specification

CPCI-2,

G264302-2, Pt 1

Computer Program Development Specification for the Tactical Application Software

All 2.3.5.1. http://www.FedTeds.

gov

SSPARS, Atch 1 Page 15 P00401 https://halfway.peterson.af.mil/publish/21Series/21-10401.pdf https://halfway.peterson.af.mil/publish/21Series/21-10401.pdf https://halfway.peterson.af.mil/publish/21Series/21-10401.pdf http://www.fedteds.gov/ http://www.fedteds.gov/ http://www.fedteds.gov/

Publications Publication Title Publication Para

References

PWS Para References

Location

C-5 Specification

CPCI-2,

G264302-2, Pt 2

Computer Program Product Specification for the Tactical Application Software

All 2.3.5.1. http://www.FedTeds.

gov

PRF H293101C

(S)

Performance Specification System Specification for the Ground-Based Midcourse Defense Upgrade Early Warning Radar (U)

All 2.3.5.3. Currently unavailable

– available after UEWR system turnover

ESD/BMEWS-

0005C-A

Computer Program Development Specification for BMEWS Mission Software

Para 3.2.1 2.3.5.2. http://www.FedTeds.

gov

B-5 Specification

CPCI-2,

G165893-1, Pt 1

Computer Program Development Specification for BMEWS Mission Software

All 2.3.5.2. http://www.FedTeds.

gov

C-5 Specification

CPCI-2,

G165893-1, Pt 2

Computer Program Product Specification for BMEWS Mission Software

All 2.3.5.2. http://www.FedTeds.

gov

Tactical Requirements Doctrine

All

All

2.3.6.2.1.

2.3.6.9.

To view contact PM office after 29 Apr 05

DoDI 8500.2 Information Assurance (IA) Implementation

Enclosure 4 2.3.6.10 http://www.dtic.mil/wh s/directives/corres/pd f/850002.pdf

AFI 31-401 Information Security Program Management

Chs 4 and 5

Ch 6

2.4.2.

2.4.3.1.

http://www.e-publishing.af.mil/pubfile s/af/33/afi33-113/afi33- 113.pdf

AFSSI 8580 Remanence Security All 2.4.3. https://private.afca.af.mi l/ip/Documents/AFSSI_ 8580_17_Nov_08.pdf

CCAFSOI 31-401 Information Security Program Management

All 2.4.3.2

CCAFSOI 31-401

ETTS User Manual

ETTS User Manual All 2.4.4. http://www.FedTeds.

gov

SSPARS, Atch 1 Page 16 P00401 http://www.fedteds.gov/ http://www.fedteds.gov/ http://www.fedteds.gov/ http://www.fedteds.gov/ http://www.fedteds.gov/ http://www.fedteds.gov/ http://www.fedteds.gov/ http://www.fedteds.gov/ http://www.dtic.mil/whs/directives/corres/pdf/850002.pdf http://www.dtic.mil/whs/directives/corres/pdf/850002.pdf http://www.dtic.mil/whs/directives/corres/pdf/850002.pdf http://www.e-publishing.af.mil/pubfiles/af/33/afi33-113/afi33-113.pdf http://www.e-publishing.af.mil/pubfiles/af/33/afi33-113/afi33-113.pdf http://www.e-publishing.af.mil/pubfiles/af/33/afi33-113/afi33-113.pdf http://www.e-publishing.af.mil/pubfiles/af/33/afi33-113/afi33-113.pdf

CHAPTER 3

TECHNICAL ASSISTANCE, EXERCISES, TESTING, SIMULATION TRAINING, AND

EMERGENCY MANAGEMENT

3.0. GENERAL (Does not apply to RAF Fylingdales, except paragraphs indicated below).

Provide MWOC technical assistance and support exercises, testing and training IAW AFSPCI 10- 1205(S). Immediately limit or terminate this support if participating personnel are needed for corrective maintenance or operational events. Schedule all scenarios around preventive maintenance.

3.1. TECHNICAL ASSISTANCE. Review operations training and evaluation performance exercises and provide comments and recommendations to the operations staff within five (5) working days of the request.

3.2. INSTALLATION AND HIGHER HEADQUARTERS DIRECTED EXERCISES (Also applies to RAF Fylingdales). Support evaluation and inspection teams as requested by the Installation/Site Commander/Liaison Officer. Participate in exercises. Exercises with Contractor participation may occur on a no-notice basis to meet exercise objectives. Perform the following:

3.2.1. Trusted Agents (Also applies to RAF Fylingdales). Designate trusted agents at the request of the inspection or exercise team chief.

3.2.2. Exercise Reports (Also applies to RAF Fylingdales). Provide inputs for the final inspection/exercise report, as requested.

3.2.3. Crisis Response Element (CRE) (Also applies to RAF Fylingdales). Participate on the unit CRE during activations for real world events, headquarters inspections, or local exercises as determined by the Installation/Site Commander based on the situation or exercise objectives.

3.2.4. Exercise Evaluation Team (EET) (Applies to Clear AFS Only). Participate on the EET and attend training provided by Eielson AFB, Civil Engineer Readiness Flight.

3.2.5. Recall of Contractor Personnel (Also applies to RAF Fylingdales). The Installation/Site Commander/USAFLO will determine the level of Contractor participation for any given exercise or inspection including recall of Contractor personnel. Overtime requests must be recommended by the Installation/Site Commander and approved by the CO.

3.3. TESTING SUPPORT (Also applies to RAF Fylingdales). Participate in the preparation, review, running, and analyses of system test plans and procedures. Support test plans, procedures, and activities for evaluating system capabilities; modifying and improving existing hardware, firmware or software; or, testing newly installed hardware, firmware, or software. Interface with military personnel and other Contractor personnel to support testing activities, provide feedback on the adequacy of test procedures and results, and data and documentation in support of tests, noting system deficiencies or anomalies. (P00016)

3.4. SSPARS TRAINING SYSTEM (SSPARTS) (Applies to Beale AFB, Clear AFS, Cape Cod AFS and Thule AB). Install and maintain simulation media programs to support scenario evaluations, tests, exercises and scenarios for training simulators. Maintain and repair all SSPARTS hardware and software to include the Meridian Switch. Perform routine

SSPARS, Atch 1 Page 17 P00401 maintenance, configuration, and fault isolation. In the event of a failure or outage during non-duty hours, perform maintenance as soon as possible the next duty day. Submit and coordinate PRs associated with SSPARTS to 21 OSS/OSOT, 81 TRSS/TSL and 533 TRS/DOC.

3.4.1. Simulation Media Storage. Store and maintain all simulation media (scenario tapes, disks, or other forms of scenario software) necessary to perform system checkout/verification, raid simulation, training, or other special interest simulations. Maintain an inventory of all simulation media including ITW&AA scenario information.

3.4.2. (Applies to Thule AB Only) For Thule’s second SSPARTS located on main base, support will be identical to the support of the first SSPARTS located on the radar site as described in paragraph 3.4. with one exception. In the event of a failure or outage during non-duty hours, perform maintenance as soon as possible to the main base simulator NLT 5 duty days.

3.5. EMERGENCY MANAGEMENT (EM) (Applies to Clear AFS Only, excluding PWS para 3.5.6.). Manage the EM Program IAW AFI 10-2501, Atch 2 through 6. Maintain the existing Clear Air Force Station (AFS) Emergency Management Operations Plan 10-2, update as required, and make available for Government review upon request.

3.5.1. Point of Contact (POC) and Training. Appoint a primary and alternate POC to manage the EM Program. Provide training for all personnel as outlined in AFI 10-2501, Chapter 6 and document attendance. Initial EM training will be provided to the EM Program Manager by the disaster preparedness organization at Eielson AFB AK.

3.5.2. Publications and Checklists. Review and maintain all Site disaster/emergency response and shelter Operation Plans (OPlans) and associated checklists.

3.5.3. Installation Warning Systems. Maintain and test Installation-warning systems. For information regarding Installation-warning systems, see AFI 10-2501, Chapter 9.

3.5.4. Shelter Management. Provide 24-hour operations for each shelter listed in the Clear AFS EM Operations Plan 10-2. Provide a shelter management team trained in the following: basic concepts of shelter management and operations, including contamination control area (CCA) management and processing, selected shelter equipment use, nuclear, biological, chemical and conventional (NBCC)-related subjects, post-attack damage assessment procedures to include reporting requirements and exposure control procedures when applicable.

3.5.4.1. Duties. Perform duties described in Air Force Manual (AFMAN) 32-4004, Sec 1A, para

1.2.5.4. Ensure mobile command post equipment includes the items listed in Sec 1B, para 1.9 (Government provided equipment).

3.5.4.2. Food and Supplies. Stock shelters with food and supplies on a crisis-implemented basis during emergencies. Information regarding war reserve materials can be found in AFMAN 32-4005, para 1.12.

3.5.4.3. Shelter Maintenance. Perform preventive maintenance on all Installation shelter facilities.

3.5.4.4. Training. Attend required training provided by the Readiness Flight at Eielson AFB AK.

Schedule and maintain documentation of all training accomplished to include Disaster Control Group (DCG), Exercise Controller (EC), and Shelter Management Training (SMT). Make training records available for Government review upon request.

SSPARS, Atch 1 Page 18 P00401

3.5.5. On-Scene Disaster Control Group (OSDCG). Participate on the OSDCG as specified in Clear AFS EM Operations Plan 10-2.

3.5.6. EM Participation (Applies to Beale AFB, Cape Cod AFS, RAF Fylingdales, and Thule AB). Appoint a primary and alternate member for participation in the Installation EM Program.

Implement and maintain plans of action and checklists and provide support in local, civil, federal and other medical and health agencies during EM matters.

SSPARS, Atch 1 Page 19 P00401

Chapter 3 – Technical Assistance, Exercises, Testing, Simulation Training, And Full

Spectrum Threat Response Support

Publications Publication Title Publication Para

References

PWS Para References

Location

AFSPCI 10-

1205(S)

Ground Based Missile Warning

SENSOR

Operations

All 3.0. To view contact PM office after 29 Apr 05

AFI 10-2501 AIR FORCE

EMERGENCY

MANAGEMENT

(EM) PROGRAM

PLANNING AND

OPERATIONS

Atch 2 through 6

Chapter 6 .

Chapter 9

3.5.

3.5.1.

3.5.3.

http://www.e-publishing.af.mil/pubfi les/af/10/afi10- 2501/afi10-2501.pdf

Clear AFS EM

OPLAN 10-2

Clear Air Force Station (AFS) Emergency Management (EM) Operations Plan 10-2

3.5. and 3.5.4.

http://www.FedTeds.

gov

AFMAN 32-4005 Personnel Protection and Attack Actions

Para 1.12.

3.5.4.2. http://www.e-publishing.af.mil/pubfi les/af/32/afman32- 4005/afman32- 4005.pdf

AFMAN 32-4004 Emergency Response Operations

Sec 1A, Para

1.2.5.4 and Sec 1B, Para 1.9

3.5.4.1. http://www.e-publishing.af.mil/pubfi les/af/32/afman32- 4004/afman32- 4004.pdf

AMDOTS MOA Air and Missile Defense Operational Test Suite (AMDOTS)

All 3.3 To view contact PM

SSPARS, Atch 1 Page 20 P00401 http://www.e-publishing.af.mil/pubfiles/af/10/afi10-2501/afi10-2501.pdf http://www.e-publishing.af.mil/pubfiles/af/10/afi10-2501/afi10-2501.pdf http://www.e-publishing.af.mil/pubfiles/af/10/afi10-2501/afi10-2501.pdf http://www.e-publishing.af.mil/pubfiles/af/10/afi10-2501/afi10-2501.pdf http://www.fedteds.gov/ http://www.fedteds.gov/ http://www.e-publishing.af.mil/pubfiles/af/32/afman32-4005/afman32-4005.pdf http://www.e-publishing.af.mil/pubfiles/af/32/afman32-4005/afman32-4005.pdf http://www.e-publishing.af.mil/pubfiles/af/32/afman32-4005/afman32-4005.pdf http://www.e-publishing.af.mil/pubfiles/af/32/afman32-4005/afman32-4005.pdf http://www.e-publishing.af.mil/pubfiles/af/32/afman32-4005/afman32-4005.pdf http://www.e-publishing.af.mil/pubfiles/af/32/afman32-4004/afman32-4004.pdf http://www.e-publishing.af.mil/pubfiles/af/32/afman32-4004/afman32-4004.pdf http://www.e-publishing.af.mil/pubfiles/af/32/afman32-4004/afman32-4004.pdf http://www.e-publishing.af.mil/pubfiles/af/32/afman32-4004/afman32-4004.pdf…