Atch_1_-_Performance_Workstatment_(PWS).pdf

DRAFT

13 April 2015

DRAFT

1 PWS: FA8823-15-R-0001

Performance Work Statement (PWS)

GPS Engineering, Analysis & Remote Site Sustainment

1 Introduction

The GPS Engineering, Analysis & Remote Site Sustainment (GEARSS) contract is the vehicle the GPS program sustainment organization (SMC/GPL) will use to satisfy the AFSPC/CC vision that all sustainment contracts for mission system maintenance and support would fall under SMC contract management and administration. This contract implements GPS specific task formerly accomplished under a 50th Space Wing (50 SW) contract known as Network and Space

Operations and Maintenance (NSOM) which expired 29 September 2014. Those GPS specific tasks were added to the GPS Control Segment (GCS) sustainment contract for one three month period from 30 September through 31 December 2014 to ensure continued and uninterrupted support for the GPS mission. Additionally, SMC/GPL will continue that support on the GCS contract via a sole-source justification and authorization to ensure continued support until

GEARSS is awarded. SMC/GPL is chartered to ensure the Operational Control Segment (OCS) viability until the next generation control segment (OCX) effort is developed and fielded.

GEARSS provides organizational maintenance and operational support services to the operational unit that will include remote site technicians, Network Administrative Officers

(NAO) and operations support.

1.1 Mission

Acquire, deliver and sustain reliable GPS and NDS capabilities to America's warfighters, allies and civil users.

1.2 Background

The primary mission of the GPS is to provide precise, continuous, all-weather, three-dimensional position, velocity, and time (PVT) to properly equipped air, land, sea, and space based users.

Civil applications include intercontinental in-route navigation (sea and air), vehicle monitoring, oceanic and coastal navigation, harbor operations, resource exploration, hydrographic and geophysical surveying, position reporting and monitoring, coordinating search operations and cell phone timing. The GPS satellites’ secondary payload, the Nuclear Detonation (NUDET)

Detection System (NDS), is a source of NUDET data for United States (US) military operations and treaty enforcement.

Three primary segments of GPS work together to accomplish the GPS mission: The Space

Segment (SS) of GPS satellites, the Control Segment (CS) of GPS ground-based command, control, and communications (C3) and signal monitoring assets, and the User Segment of GPS devices that receive the satellite PVT data. The Space Segment consists of all GPS space vehicles (SVs) currently in orbit: Block IIA, IIR, IIR-M, and Block IIF. A future block (i.e., the

Block III SVs) is currently under development. The CS commands and controls the SS to ensure it provides the users with the correct PVT information. The CS is operated on a daily basis by

Air Force Space Command (AFSPC) 2nd Space Operations Squadron (2 SOPS) military and civilian personnel. Control Segment sustainment requires expertise in current space vehicle

2 PWS: FA8823-15-C-XXXX

operation as well as the ability to operate and maintain the hardware and software of the CS itself.

The GCS sustainment contract was awarded on 13 December 2012 with contract start on 1

January 2013. The GCS contract was awarded for one base year with five option years and a six-month extension of services clause. The GCS and GEARSS contracts will provide essential operations, maintenance & sustainment support until the Next Generation OCS (OCX) is fielded.

Additionally, the current GPS network consists of 2 each, dedicated, near T-1 speed circuits that run from either the GPS Master Control Station (MCS) or the Alternate Master Control Station

(AMCS) to four remote sites for a total of 8 operational circuits. In addition there are seven external user circuits (High Accuracy Navigation User (HANU), United States Naval

Observatory (USNO), Integrated Mission Operational Support Center (IMOSC), Operational

Support System (OSS), Air Force Technical Applications Center (AFTAC), Integrated

Correlation and Display System (ICADS), and Air Force Satellite Control Network (AFSCN)), five circuits between the MCS and AMCS, four circuits between the MCS and Cape Canaveral

Air Force Station (AFS), FL and five other circuits (National Geospatial Agency (NGA) and test facilities) that are configured in the same manner as the operational circuits. This is a current total of approximately 30 circuits.

Defense Information Systems Agency (DISA) is the long haul communication provider for all these circuits and is responsible for the maintenance of the circuit from DISA’s Point of Presence

(PoP), as designated by them, at the originating site to their PoP at the remote site.

The current OCS is comprised of three major elements: 1) the Master Control Station (MCS) and Alternate Master Control Station (AMCS); 2) four dedicated Ground Antennas (GA); and 3) six Monitor Stations (MS). The MCS is located at Schriever and is the center for all on-orbit

GPS mission control operations. The AMCS is located at Vandenberg. The four GAs are located at Cape Canaveral Air Force Station (CCAFS) Florida, Ascension Island in the South

Atlantic, Diego Garcia in the Indian Ocean, and Kwajalein Atoll in the mid-Pacific. The six

MSs are located at SAFB, Kaena Point in Hawaii, Ascension, Diego Garcia, Kwajalein and Cape

Canaveral Air Force Station (CCAFS), Florida.

The MCS and AMCS are consolidated centers for the control and monitoring of the Space

Segment. They are also the Command, Control and Communications (C3) centers for the OCS.

Only one of the Control Stations can be in control of the constellation at any one time. The OCS has Air Force Satellite Control Network (AFSCN) connectivity to all Automated Remote

Tracking Station (ARTS) sites and provides full support to external users from both the MCS and AMCS. The following paragraphs describe OCS assets which are subject to GCS support

(i.e., GCS supported systems).

Master Control Station (MCS) and Alternate MCS (AN/FSQ-217)

The purpose of the MCS is to provide constellation management. The MCS collects navigation signals from each satellite, recalculates the satellite’s correct position and on-board atomic frequency standards (a.k.a. the atomic clock) corrections, and updates the navigation signal

3 PWS: FA8823-15-C-XXXX

through upload commands. The MCS is responsible for operational maintenance of the GPS constellation. This responsibility requires the MCS to analyze the State of Health (SOH) of each satellite and to interpret associated navigation messages. The MCS is located in Module (MOD)

11 in Building 400 at SAFB.

The AMCS facility is located at Vandenberg Air Force Base (VAFB). The AMCS is functionally identical to the AEP MCS, and serves as the backup to the MCS. As the backup to operations, the AMCS has direct connectivity to operational OCS resources and users. The

AMCS is capable of performing all operations and planning normally conducted in the MCS.

GPS Information Network (GIN) (AN/FYN-1)

The GIN provides the CS a capability for 2 SOPS operators to assist military and civilian users and optimize their use of GPS. Located at Schriever AFB adjacent to the MCS and part of the overall OCS, it consists of an ensemble of hardware and software accessible via the internet to external users. A major aspect of GIN operations is support for US and coalition warfighters conducting missions which require time critical, high precision application of GPS capabilities.

Ground Antennas (GA) (AN/FRC-178)

The GAs are a group of four dedicated GAs at remote sites that transmit commands to satellites and receive vehicle telemetry. The GAs have the capability to receive and store the commands from the MCS for later transmission.

Monitor Stations (MS) (AN/FSN-5)

The MSs are comprised of six GPS receiver stations at Remote Sites that collect L-Band signals and send the signals to the MCS. The MSs track each vehicle that comes into view. MCS personnel can select the satellites that are tracked by individual MSs. Data from the MSs are used by the MCS to update the navigation messages broadcast by each satellite, thus providing the most accurate navigation data to users.

GPS Support Facility (GSF)

The GSF is a facility in Building 400 at Schriever AFB CO. The A/F24U-8 Maintenance

Manual describes the primary function of the GSF as support for the MCS mission. The GSF is not an operational asset, but it provides resources for software testing and integration, and anomaly resolution. The GSF provides a system functionally identical to the MCS and hosts a

GPS System Simulator for testing of software releases and system modifications.

GPS System Simulator (GSS)

The GSS in the GSF provides high fidelity simulations of an entire GPS constellation (up to 30

Block IIA, Block IIR, and Block IIR-M and IIF satellites), as well as 4 GAs and 20 MSs, 11 of which may be National Geospatial-Intelligence Agency (NGA) stations. The GSS provides full command and response capabilities, interactive models, full environment simulation, and selected payload simulation. It provides flexible usage for software development, testing, 4 PWS: FA8823-15-C-XXXX anomaly resolution and analysis. Simulated GA inputs, such as telemetry and command verification, are also provided to the AEP system by the GSS.

Positional Training Emulator (PTE) (AN/FSQ-217-T)

The PTE is a classified trainer located in Building 400 at Schriever AFB, which retains the training capabilities inherent in the AEP/GSS combination and adds capabilities specific to positional training and instructor control. The PTE provides a capability to train the following

GPS operational crew positions: Payload Systems Operator (PSO), Satellite Systems Operator

(SSO), and Satellite Vehicle Operator (SVO).

Launch and Early Orbit, Anomaly Resolution and Disposal Operations (LADO) Off-Line

Trainer (LADO-OLT) (AN/FSQ-215)

The LADO Offline Trainer is a crew and position trainer for the LADO system. The LADO

Offline Trainer simulates use of the Automated Remote Tracking Stations (ARTS) and the Space

Vehicles (SVs) in order to train Air Force personnel in the operations of the LADO system.

Through the use of developed scenarios, the LADO Offline Trainer provides training on Launch and Early Orbit (L/EO) support of Block IIR/IIR-M and IIF SVs, and anomaly resolution and disposal operations for all Global Positioning System (GPS) SVs.

Telecommunications Simulators

The telecommunications simulators consist of hardware and software which simulate the Space

Vehicles (SVs) and are used for the sustainment of OCS software and hardware development, testing, checkout, software verification, cross-link and tri-link testing. Each satellite block has a separate telecommunications simulator provided by the manufacturer comprised of satellite hardware similar to the flight articles and buses from each of the respective satellite families.

Maintenance of the telecommunications simulators is provided via a separate contract; however, test set up, including use of these assets, is within scope of this contract.

Telecommunications Simulator Test Station (TSTS) (AN/FSQ-200)

The TSTS is located adjacent to the GPS GA at CCAFS. The TSTS is comprised of the Monitor

Station Test Station (MSTS) and the Radio Frequency Interface System (RFIS), Radio

Frequency (RF) digitizers and communications equipment that interface with Ground Antenna

Test Simulator (GATS) equipment in the Consolidated Test Environment (CTE). The TSTS also replicates most of the functions of an operational MS and provides the interface between the

CTE/GSF and SV simulators. The TSTS consists of three shelters that also house the three

Telecommunications Simulators: the Telecommunications Simulator Module (TSM Block

II/IIA), Modernized Telecommunications Simulator (MTS - Block IIR), the Satellite

Telecommunications Simulator (STS - Block IIF), and the GPS III Satellite Simulator (GSS –

Block III).

5 PWS: FA8823-15-C-XXXX

1.3 Scope

During the performance of this contract, the contractor shall provide the following services:

1) Perform Remote Site maintenance and operations support per maintenance TOs for ASCN, KWAJ, DIEGO, COSPM and CAPE, to include but not limited to, providing maintenance manning on-site for a minimum of 8 hours per day, five days per week.

2) Provide mission essential Network Administration Officer (NAO) support at the MCS and

AMCS to include, but not limited to, trained NAO personnel and performing NAO crew member duties and responsibilities 24/7 in accordance with the technical orders and maintaining required

NAO proficiency.

3) Provide operations support and engineering and analysis technical expertise at the MCS and

AMCS for daily ground system, on-orbit and launch activities, crew proficiency and system simulation for a minimum of 12 hours per day, five days per week (0600-1800, Monday-Friday) with 24 hour on-call support

4) Perform site-specific essential duties for ASCN, KWAJ, DIEGO, COSPM and CAPE, as required, to meet mission requirements

5) Perform remote site safety for ASCN, KWAJ, DIEGO, COSPM and CAPE for all on-site facilities (ground safety), all on-site GEARSS contractor personnel (industrial safety) and mission system safety

6) Perform Emergency Management requirements for ASCN, KWAJ, DIEGO, COSPM and

CAPE for all on-site GEARSS contractors

7) Perform COMSEC Responsible Officer (CRO) duties for all mission locations that require handling of COMSEC materials

6 PWS: FA8823-15-C-XXXX

2 General Requirements

This section describes the general requirements of this contract.

2.1 Non-Personal Services

The Government shall neither supervise contractor employees nor control the method by which the contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual contractor employees. The contractor shall manage its employees and guard against any actions that are of the nature of personal services, or give the perception of personal services. If the contractor believes that any actions constitute, or are perceived to constitute personal services, the contractor shall notify the Procuring

Contracting Officer (PCO) within 2 business days.

2.2 Business Relations

The contractor shall successfully integrate and coordinate all activities needed to perform the requirements. The contractor shall manage the timeliness, completeness, and quality of problem identification. The contractor shall provide corrective action plans, proposal submittals, timely identification of issues, and effective management of subcontractors. The contractor shall ensure customer satisfaction and professional and ethical behavior of all contractor personnel.

2.3 Contract Administration and Management

The following subsections specify requirements for contract, management, and personnel administration.

2.3.1 Contract Management

The contractor shall establish clear organizational lines of authority and responsibility to ensure effective management of the resources assigned to the requirement. The contractor shall maintain management and operations of this contract in El Paso County, Colorado.

2.3.2 Contract Administration

2.3.2.1 The Contractor shall establish processes and assign appropriate resources to effectively perform the requirements of this contract. The contractor shall respond to Government requests for contractual actions in a timely fashion. The contractor shall generate and maintain the Data

Accession List (DAL) CDRL A001. The contractor shall have a single point of contact between the Government and Contractor personnel assigned to support contracts.

2.3.2.2 The Contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via the secure data collection site (i.e., Contract Manpower Reporting Application). The contractor is required to completely fill in all required data fields using the following web address http://www.ecmra.mil.

Reporting inputs will be for the labor executed during the period of performance during each

Government fiscal year (FY), which runs October 1 through September 30. While inputs may be

7 PWS: FA8823-15-C-XXXX

reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the ECMRA help desk.

2.3.3 Personnel Administration

The contractor shall provide qualified personnel during designated Government non-work days or other periods where Government offices are closed due to weather or security conditions. The contractor shall provide initial and refresher training to its employees as required satisfying the

PWS requirements. The contractor shall make necessary travel arrangements for its employees.

The contractor shall provide necessary infrastructure to support contract tasks for all employees.

The contractor shall provide administrative support to employees in a timely fashion (time keeping, leave processing, pay, emergency needs).

2.4 Subcontract Management

2.4.1 The contractor shall be responsible for any subcontract management necessary to integrate work performed on this requirement and shall be responsible and accountable for subcontractor performance on this requirement. The contractor shall ensure there are no

Organizational Conflict of Interest (OCI) considerations associated with management of the work distribution across prime and subcontractors. Cross teaming is permitted provided the teaming arrangement does not create any OCI.

2.4.2 The contractor shall perform subcontractor management IAW SMC-S-019.

2.5 Contractor Personnel, Disciplines, and Specialties

2.5.1 The contractor shall accomplish the assigned work by employing and utilizing qualified personnel with appropriate combinations of education, training, and experience. The contractor shall match personnel skills to the work or task with a minimum of under/over employment of resources. The contractor shall provide the necessary resources, technical processes and infrastructure to manage, perform, and administer the contract.

2.5.2 The contractor shall ensure open, courteous/professional and clear lines of communication between contractor personnel and Government counterparts. This communication may occur daily via telephone discussions, weekly via face-to-face meetings or any other means and frequency necessary to ensure information flow is optimal.

2.5.3 The contractor shall ensure all personnel comply with all host tenant support agreements

(HTSA), where applicable. The Government retains the right, without penalty, to withdraw privileges at any time for Government convenience or if the contractor violates an HTSA.

2.6 Location and Hours of Work

2.6.1 The Contractor shall perform the services required by this PWS as described in paragraph

1.3 above.

2.6.2 Normal workweeks are five days per week, except US Federal Holidays, unless assigned to operational crew duties.

8 PWS: FA8823-15-C-XXXX

2.6.3 The contractor shall provide necessary facilities to accommodate contract personnel that are not located on Government installations. Facility must meet minimum industry Occupational

Safety & Health Administration (OSHA) standards and secure access.

2.7 Travel / Temporary Duty (TDY)

Travel to other Government facilities or other contractor facilities may be required to perform the services required by this PWS. All travel requirements (including plans, agenda, itinerary, or dates) shall be pre-approved by the Government (subject to local policy and procedures), and is on a strictly cost reimbursable basis. Costs for travel shall be billed IAW FAR 31.205-46, Travel

Costs. Travel to some GEARSS locations may require travel on military aircraft.

2.8 Associate Contractor Agreement (ACA) The contractor shall enter into any required

ACAs with other contractors as required to fulfill GEARSS requirements.

2.8.1 The Contractor shall enter into Associate Contractor Agreements (ACA) for any portion of the contract requiring joint participation in the accomplishment of the Government's requirement. The agreements shall include the basis for sharing information, data, technical knowledge, expertise, resources, or any combination thereof, which shall ensure the greatest degree of cooperation for the development of the program to meet the terms of the contract.

2.8.2 ACAs shall:

2.8.2.1 Identify the associate contractors and their relationships.

2.8.2.2 Identify the program involved and the relevant Government contracts of the associate contractors.

2.8.2.3 Describe the associate contractor interfaces by general subject matter.

2.8.2.4 Specify the categories of information to be exchanged or support to be provided.

2.8.2.5 Include the expiration date (or event) of the ACA.

2.8.2.6 Identify potential conflicts between relevant Government contracts and the ACA and include agreements on protection of proprietary data and restrictions on employees.

2.8.3 A copy of such agreement shall be provided to the Contracting Officer for review before execution of the document by the cooperating contracts.

2.8.4 The Contractor is not relieved of any contract requirements or entitled to any adjustments to the contract terms because of a failure to resolve a disagreement with an associate contractor.

However, the Government may assist the Contractor in the event of non-responsiveness from an associate contractor.

2.8.5 Liability for the improper disclosure of any proprietary data contained in or referenced by any agreement shall rest with the parties to the agreement, and not the Government.

9 PWS: FA8823-15-C-XXXX

2.8.6 All costs associated with the agreements are included in the negotiated cost of this contract. Agreements may be amended and associate contractors added or deleted as required by the Government during the performance of this contract.

2.9 Base Support

2.9.1 Purpose. The following describes the conditions under which the Government will provide base support to the Contractor during the Contractor's performance of this contract.

2.9.2 Definitions:

2.9.2.1 'Base Support' is defined as Government Property located at Government-controlled facilities. It includes, but is not limited to, working space, equipment, information technology, and related services (excluding use of the Defense Switched Network (DSN) which the

Government determines can be made available at, or through, any Air Force installation where this contract shall be performed.

2.9.2.2 'Information technology (IT)' is defined in FAR 2.101, 'Definitions'.

2.9.3 Requirement. Unless otherwise stated in this contract, such base support shall be provided by the Government on a rent-free basis and the value of that support shall be a part of the consideration passing from the Government to the Contractor under this contract. The

Contractor shall manage such base support in accordance with the Government Property clause of this contract. If the Government fails to provide base support by the dates required, the

Contractor may be entitled to an equitable adjustment in accordance with the Government

Property clause of this contract. Failure by the Contractor to comply with the requirements of this clause shall release the Government, without prejudice, from its obligation to provide base support by the date(s) required. The Contractor agrees that in the performance of this contract or any major subcontract, it will not incur any direct or indirect costs for base support if the

Government determines that property is available at or through any Air Force installation where this contract shall be performed.

2.9.4 The Contractor agrees to immediately report (with a copy to the cognizant ACO) inadequacies, defective Government Property (GP) or non-availability of support stipulated by the contract schedule, together with a recommended plan for obtaining the required support. The

Government agrees to determine (within 10 workdays) the validity and extent of the involved requirement and the method by which it shall be fulfilled (e.g., purchase, rental, lease, GP).

Facilities shall not be purchased under this clause. Additionally, the Contractor (or authorized representative) shall not purchase, or otherwise furnish any base support requirement provided by the clause (or authorize others to do so), without prior written approval of the Contracting

Officer regarding the price, terms, and conditions of the proposed purchase, or approval of other arrangements.

2.9.5 Because of the nature and location(s) of the work performed, the value of such equipment is undeterminable. The Contractor shall not incur any cost resulting from nonsupport prior to

Contracting Officer concurrence.

10 PWS: FA8823-15-C-XXXX

3 Performance Requirements

The following sections specify the Performance Objectives and Performance Elements for the contract. The contractor shall perform all tasks listed in all paragraphs of the PWS.

NOTE: When “contractor format” is referenced throughout all paragraphs of the PWS, the contractor shall provide a contractor generated, consistent, standardized format that is approved by the Government.

NOTE: All products derived from the tasks listed in this PWS shall be delivered in contractor format, unless otherwise specified for a particular task, and coordinated directly with the

Government.

3.1 The contractor shall provide Program Management.

3.1.1 Provide approximately four engineering estimates, in hours, annually for any changes to hardware, software or operations and sustainment procedures requested by the

Government.

Performance Standards

STD #1: The contractor shall deliver estimate via e-mail in contractor format within 15 business days of the Government request.

Deliverables

A000 N/A

3.1.2 Prepare for and brief to the Government one monthly contract and PWS status meeting to include program management, schedule, risk management, accomplishments, issues and upcoming events for all GEARSS tasks. In contractor format, provide an itemized agenda, a meeting presentation and meeting results to assigned Government representative(s).

Performance Standards

STD #1: The contractor shall provide a GSIMS link, via e-mail to the Government, of the location of meeting charts at least 2 calendar days before the meeting.

STD #2: The contractor shall provide a GSIMS link, via e-mail to the Government, of the location of meeting minutes within 3 working days after meeting.

STD #3: The contractor shall conduct the status meeting monthly.

Deliverables

A000 N/A

11 PWS: FA8823-15-C-XXXX

3.1.3 Provide annual contract performance assessment inputs to the Government.

Performance Standards

STD #1: The contractor shall, in contractor format, provide a self-assessment of contract performance within 30 calendar days of Government request.

STD #2: The contractor shall provide this assessment directly to the Government Program

Manager and Contracting Officer’s Representative (COR).

Deliverables

A000 N/A

3.1.4 Maintain all required local procedures. This includes creating new, modifying existing, and deleting obsolete procedures.

Performance Standards

STD #1: The contractor shall maintain procedures IAW 2 SOPS OIs and day-to-day operational support needs.

STD #2: The contractor shall maintain up-to-date documentation on GSIMS for all local procedures and operating instructions.

Deliverables

A000 N/A

3.1.5 Author and submit AFTO 22/252s to report and correct deficiencies in published

TOs.

Performance Standards

STD #1: The contractor shall ensure AFTO 22/252s are IAW TO 005 series and MIL-STD

38784.

STD #2: The contractor shall ensure Emergency findings are documented and submitted within 24 hours of finding.

STD #3: The contractor shall ensure Routine findings are documented and submitted within

7 calendar days of finding.

STD #4: The contractor shall ensure Urgent findings are documented and submitted within

48 hours of finding.

12 PWS: FA8823-15-C-XXXX

3.2 The contractor shall provide Network Administration Officer (NAO) support.

3.2.1 The contractor shall provide trained and certified NAOs.

Performance Standards

STD #1: The contractor shall provide trained, proficient and certified NAO crew members.

Prior to certification, the NAO will be required (at Government discretion) to participate in a review panel and complete a formal mission ready briefing to the 2 SOPS/CC or DO and the contractor supervisor.

STD #2: The contractor shall notify the on-duty Crew Commander and organizational level management personnel when a condition exists, either physical or mental, and affecting themselves or other unit personnel that may prevent mission accomplishment or endanger personnel safety.

STD #3: The contractor shall ensure 24-hours per day, 7-days per week NAO coverage and coordinate scheduling with the 2 SOPS crew scheduler.

Deliverables

A000 N/A

3.2.2 The contractor shall monitor and coordinate the status of all GPS ground systems and communication lines, into and out of the MCS and AMCS

Performance Standards

STD #1: The contractor shall monitor all communications circuits continuously including, but not limited to, operational circuits, the NGA Network Control Center, the Air Force

Technical Applications Center (AFTAC), High Accuracy Navigation Users (HANU), and satellite vehicle contractor interfaces.

STD #2: The contractor shall analyze and isolate all communications-related malfunctions and reconfigure ground systems equipment as required to maintain mission operations per published technical orders.

13 PWS: FA8823-15-C-XXXX

3.2.3 Provide NAO support on-site at the AMCS in support of 2 SOPS MOX activities.

STD #1: The contractor shall conduct mission operations transfer procedures between the

MCS and AMCS and relocate to the back-up location, as required, to conduct NAO operations with military crews as part of real-world/exercise and contingency operations.

STD #2: The contractor shall provide support approximately four times per year, 5-7 days per event, when 2 SOPS transfers operations to the AMCS.

Deliverables

A000 N/A

3.2.4 The NAO shall support all troubleshooting activities until anomalous conditions are correctly resolved and operations are restored to normal status.

Performance Standards

STD #1: The contractor shall assist MS and GA site technicians in the troubleshooting of hardware and software anomalies.

STD #2: The contractor shall notify the on-duty Crew Commander and/or Crew Chief immediately when an anomalous condition exists and recommend fix-actions IAW published technical orders.

14 PWS: FA8823-15-C-XXXX

3.3 The contractor shall provide on-site Remote Site maintenance support.

3.3.1 The Remote Site Technician (RST) shall provide maintenance support per published maintenance TOs for ASCN, KWAJ, DIEGO, CAPE and COSPM.

Performance Standards

STD #1: The contractor shall provide a minimum of one RST 8-hours per day, 5-days per week.

STD #2: The contractor shall provide 24-hour/7-days per week on-call support.

STD #3: The contractor shall provide a minimum of two qualified RSTs at each remote site location at all times in support of 3.3.1, STD #4.

STD #4: The contractor shall provide adequate coverage when conducting maintenance activities that require two persons for safety and/or security situations.

Deliverables

A000 N/A

3.3.2 The RST shall support all troubleshooting activities until anomalous conditions are correctly resolved and operations are restored to normal status.

Performance Standards

STD #1: The RST shall provide personal or telephonic response to the on-duty 2 SOPS

Crew Commander within 30 minutes of initial notification of GPS remote sites problems affecting OPSCAP or a single GA string failure.

STD #2: The RST shall initiate troubleshooting within 1 hour of notification during off duty hours and within 5 minutes during duty hours.

STD #3: The RST shall provide an Estimated Time to Restore Operations (ETRO) and/or modification completion time to the on-duty 2 SOPS Crew Commander within 90 minutes of initial notification for problems affecting OPSCAP.

STD #4: The RST shall provide an updated repair and/or modification time at least 30 minutes before the initial estimate expires if initial estimate cannot be met.

STD #5: The RST shall initiate organizational level corrective maintenance and respond to outages impacting mission IAW applicable maintenance TOs.

STD #6: The RST shall perform organizational level maintenance IAW the Source, Maintainability and Recoverability (SMR) code as defined in the applicable system technical orders.

15 PWS: FA8823-15-C-XXXX

3.3.3 The RST shall conduct all preventive and periodic maintenance required by published procedures.

Performance Standards

STD #1: The RST shall perform all PMIs IAW applicable technical publications. The contractor shall make appropriate updates in IMDS upon completion of PMIs.

STD #2: The RST shall perform organizational level corrosion control on GPS equipment to minimize the effects of corrosion IAW TO 1-1-689-1, TO 1-1-689-3, TO 31Z-10-37, TO 1-

1-700 and Methods and Procedures Technical Order (MPTO) 00-33A-1001 (paragraph

6.2.3).

STD #3: The RST shall provide maintenance support for Jet Propulsion Lab (JPL) assets only upon direction from JPL for the DIEGO JPL GPS equipment.

Note: No PMIs are supplied for the JPL GPS suite of equipment and there are no defined routine maintenance requirements. Availability of spares for the JPL GPS suite of equipment will be at the discretion of JPL; spares will be provided by JPL as needed.

STD #4: The RST shall, unless otherwise identified by host base instructions, operate and provide organizational level maintenance (routine inspection, servicing, minor repairs, adjustments, maintain proper environmental controls and ensure general UPS/battery room housekeeping.) of all GPS-specific UPS equipment, module bypass control cabinets, and battery systems IAW AFSPC Memorandum for UPS Procurement and Maintenance (HQ

AFSPC/A7CO Policy), AFI 32-1062, applicable supplements and appropriate manufacturer manuals to ensure normal operations.

Deliverables

A000 N/A

3.3.4 The RST shall conduct and manage the Test, Measurement, and Diagnostic

Equipment (TMDE) program.

Performance Standards

STD #1: The RST shall perform organizational level maintenance on TMDE and maintain the Master Inventory Listing of owning activity TMDE provided by the supporting Precision, Measurement, Equipment Laboratory (PMEL).

STD #2: The RST shall establish and operate controls to ensure all TMDE is repaired, calibrated, and certified.

16 PWS: FA8823-15-C-XXXX

STD #3: The RST shall comply with the Air Force Metrology and Calibration Program IAW

AFI 21-113, TO 00-20-2, TO 00-20-14, TO 33K-1-100 series, TO 33-1-27, host base PMEL directives and applicable supplements.

STD #4: The RST shall maintain the Master Inventory Listing of owning activity TMDE provided by the supporting PMEL.

STD #5: The RST shall transport TMDE between the work-center and the PMEL facility.

STD #6: The RST shall follow-up on all TMDE in PMEL over 30 days.

Deliverables

A000 N/A

3.3.5 The RST shall maintain current and accurate technical documentation.

Performance Standards

STD #1: The RST shall maintain current and accurate technical order accounts and technical publication sets for all assigned equipment IAW TO 00-5-1 by utilizing sub-accounts through the 50 SW Technical Order Distribution Office (TODO).

STD #2: The RST shall develop and maintain site-specific OIs for all non-mission systems.

The OIs shall include all actions required to safely operate all equipment and systems.

Deliverables

A000 N/A

3.3.6 The RST shall utilize Integrated Maintenance Data System (IMDS) for documenting all maintenance actions.

Performance Standards

STD #1: The RST shall enter all maintenance actions into IMDS no later than 60 minutes after the job is identified and complete all actions required to close out the assigned IMDS jobs.

STD #2: The RST shall verify the IMDS Equipment Inventory List (EIL) annually or upon updates to equipment assigned to verify that the IMDS data is consistent with physical resources under the contractor’s control. IMDS data is identified as Equipment Designator, Equipment ID, System Reference Designator (SRD), and Work Unit Codes associated with the equipment.

STD #3: The RST shall accomplish historical data documentation in IMDS IAW MPTO 00-

33A-1001, paragraph 7.6.

17 PWS: FA8823-15-C-XXXX

3.3.7 The RST shall ensure compliance with all remote site mandated guidance, to include, but not limited to:

Performance Standards

STD #1: The RST shall comply with all Time Compliant Technical Orders (TCTO).

STD #2: The RST shall comply with the Government-furnished Facilities Excellence Plan and ensure all maintenance, repair, and construction work is accomplished within Facility

Excellence guidelines and standards.

STD #3: The RST shall ensure all contractors performing maintenance, repair, or construction comply with Facilities Excellence Plan.

STD #4: The RST shall inform the appropriate contractor or DoD personnel for corrective action when non-compliance is identified within their work areas.

STD #5: The RST shall comply with all RP and RPIE warranties and guarantees.

Deliverables

A000 N/A

3.3.8 The RST shall monitor all on-site construction activities.

Performance Standards

STD #1: The RST shall report the status of construction projects affecting the site to

Government representatives weekly.

STD #2: The RST shall review and provide comments to the Government on impact to mission and schedule for all site-related construction projects.

STD #3: The RST shall track, report, and document utility outages.

STD #4: The RST shall initiate work requests/service calls, and monitor status of work requests and service calls for any RP or RPIE not functioning as designed and requiring maintenance or repair in compliance with host base procedures.

STD #5: The RST shall identify requirements and initiate work requests for all construction project using AF Form 332 or other applicable host base forms.

STD #6: The RST shall maintain a log of all service calls, work requests, and job orders.

This log shall contain the most recent status and/or completion dates and shall be made available to the government upon request.

18 PWS: FA8823-15-C-XXXX

3.3.9 The RST shall comply with all site-specific environmental, fire and hazardous material policies.

Performance Standards

STD #1: The RST shall comply with all environmental programs IAW all applicable directives, executive orders, treaties, agreements, and host base OIs and plans.

STD #2: The RST shall comply with environmental standards; permit conditions, policies, laws and regulations at all locations.

STD #3: The RST shall ensure contractor generated hazardous wastes are managed and turned into the servicing host base per procedures of the host base or servicing agency.

STD #4: The RST shall comply with host base environmental programs and participate in meetings at the direction of the site commander to include, but not limited to: environmental protection committee meetings (approximately once per month per site); host base pollution prevention programs to include HAZMAT, HAZWASTE, affirmative procurement, energy conservation, solid waste management, recycling, and environmental compliance programs;

and Host Base or supporting Main Operating Base HAZMAT Pharmacy Program.

STD #5: The RST shall comply with and support the host base fire protection standards, department regulations and directives.

STD #6: The RST shall ensure that each facility is maintained in a fire safe condition and compliant with the applicable NFPA codes and standards.

Deliverables

A000 N/A

3.3.10 The RST shall perform COMSEC Responsible Officer (CRO) duties.

Performance Standards

STD #1: The RST shall perform duties and tasks as assigned and identified in AFI 33-201, Volume 2 and AFKAG 1 and AFKAG 2 to ensure the installation COMSEC account programs comply with all Information Assurance Assessment and Assistance Program requirements as defined in AFI 33-230, or IAW host base policies and procedures.

STD #2: The RST shall appoint a CRO, in writing, to the designated authority. The CRO shall accomplish required training IAW AFKAG 1.

STD #3: The RST shall ensure the CRO is trained and possesses a security clearance commensurate with the highest classification of materials required.

19 PWS: FA8823-15-C-XXXX

STD #4The CRO shall ensure all COMSEC aids and/or equipment is current and up-to-date.

STD #5: The RST shall perform COMSEC rekeys on Type 1 cryptographic equipment annually or as required. All COMSEC loads will be coordinated with distant end prior to accomplishment. Short-notice, (4 hour response time) rekeys/loads may be required and will be directed by the distant end.

STD #6: The RST shall perform a monthly account inventory and perform any equipment maintenance at that time.

STD #7: The RST shall maintain the account in accordance with CRO procedures.

STD #8: The RST shall perform routine secure telephone equipment rekeys annually or as required as indicated on equipment display.

STD #9: The RST shall report issues or deviations from established procedures to the CRO and/or distant end immediately upon discovery.

STD #10: The RST shall maintain all COMSEC accounts with zero errors found during

COMSEC inspections.

Deliverables

A000 N/A

3.3.11 The RST shall perform site-specific essential duties, as required, to meet mission requirements. These duties include, but are not limited to the following standards.

STD #1: The RST shall serve as the copier monitor.

STD #2: The RST shall serve as the bulletin board monitor

STD #3: The RST shall coordinate and support site visits and familiarization tours at DGO, KWAJ, ASCN, and CAPE only.

STD #4: The RST shall provide courier service between the site, host base and/or designated postal offices no more than once a day, 3 times a week. The RST shall distribute the mail received within the site. This requirement is applicable to KWAJ, ASCN, and CAPE only.

STD #5: The RST shall appoint an IT Equipment Custodian (ITEC) that shall maintain IT assets and AFEMS-AIM accounts IAW AFI 33-112.

STD #6: The RST shall follow the government established EMSEC program IAW AFSSI

7700, AFSSI 7702 and applicable supplements.

20 PWS: FA8823-15-C-XXXX

STD #7: The RST shall receive a baseline tool inventory that shall be updated and maintained through the life of the contract. The RST shall inventory, at least quarterly, all tools and document any discrepancies between the baseline inventory and actual inventory.

The RST shall replace any missing tools at their own cost. The RST shall replace any broken tools utilizing existing warranties, where applicable. If no warranty exists, the RST is authorized to use ODCs to acquire repair parts and/or supplies.

STD #8: The RST shall receive, store, issue, inspect, distribute and dispose of hazardous material. The RST shall maintain a file of all Material Safety Data Sheets (MSDS) for hazardous materials. AFI 32-7086, Paragraph 2.5.5 identifies exceptions for hazardous tracking.

STD #9: The RST shall serve as the Records Custodian at DGO, KWAJ, ASCN, and CAPE.

STD #10: The RST shall administer the telephone control program IAW AFI 33-111, as applicable at KWAJ, ASCN, and CAPE only.

STD #11: The RST shall ensure the site has representation at host base or higher headquarters meetings when the site commander and/or QAE are not available at KWAJ, ASCN, and CAPE only. The site manager or designee shall participate in host base and or higher headquarters meetings and coordinate issues concerning the site with respective SMC and 50 SW units.

STD #12: The RST shall establish and maintain a publications set containing all publications not available in electronic format, as designated by the site commander at DGO, KWAJ, ASCN, and CAPE. These publications sets shall contain the latest basic publications, revisions, changes and supplements and shall be available in one central location.

STD #13: The RST shall appoint, in writing, a Telecommunications Monitoring and

Assessment Program (TMAP) point of contact (POC) to ensure compliance with AFI 10-712 para 1.4.21 at KWAJ, ASCN, and CAPE. The RST shall follow their host base for biennial reporting.

STD #14: The RST shall administer and coordinate all of the security activities on-site under the supervision and direction of the site commander at KWAJ, ASCN, and CAPE. The RST shall coordinate all security activities with the host base.

STD #15: The RST shall administer the classified information program at KWAJ, ASCN, and CAPE and ensure that all personnel authorized to view classified material receive the appropriate training and comply with AFI 31-401. The RST shall ensure site personnel complete the Standard Form (SF) 312. The RST shall serve as the site Authority to

Reproduce/Destroy Classified Monitor.

21 PWS: FA8823-15-C-XXXX

STD #16: The RST shall provide safe maintenance at DGO, KWAJ, ASCN, and CAPE, which involves administering the classified safes, inspecting their contents periodically, conducting combination changes as required and conducting annual inspections.

STD #17: The RST shall serve as the site Point of Contact (POC) at DGO, KWAJ, ASCN, and CAPE for Office of Special Investigation (OSI) personnel conducting investigations, unit security meetings, security assessment teams, and liaison with host base security forces.

STD #18: The RST shall perform controlled and restricted area program duties at DGO, KWAJ, ASCN, and CAPE to include validating security clearances and visit requests.

STD #19: The RST shall serve as the Anti-Terrorism/Force Protection (AT/FP) POC at

KWAJ, ASCN, and CAPE, attend meetings and brief site personnel as required.

STD #20: The RST shall ensure all on-site employees at KWAJ, ASCN, and CAPE undergo initial and annual refresher security training in accordance with AFI 31-601, Paragraph 3.1.

Initial security education for contractor employees will meet requirements of AFI 31-401.

The Home Office Facility (HOF) security officer will appoint a site security administrator to administer and record the initial and refresher security training required by AFI 31-601, Paragraph 3.1 and site specific security instructions as provided by the OPR Security manager. Site specific security training will include; information security, physical security and resource protection as specified in AFI 31-401 and AFI 31-101 to include all applicable supplements. Site specific training should be conducted annually or on a more frequent basis as needed. Training methods may include group briefings, interactive videos, dissemination of instructional materials, Computer Based Training (CBT), or other media and methods.

Work center specific training for areas not under the control of the contractor are the responsibility of the host unit or work center security manager.

STD #21: The RST shall provide transportation to and from the flight line for personnel/teams visiting the site at DGO, ASCN and KWAJ.

STD #22: The RST shall coordinate room assignments for permanent party and TDY personnel at KWAJ and ASCN only.

STD #23: The RST shall positively control and account for all keys issued to the contractor by the Government at DGO, KWAJ, ASCN and CAPE. The RST shall not duplicate keys issued by the Government unless otherwise directed. The RST shall immediately report lost or duplicated keys to the Government.

STD #24: The RST shall control access to all areas of contractor responsibility at DGO, KWAJ, ASCN and CAPE.

STD #25: The RST shall change and control combinations IAW DoD 5200.1-R, Paragraph

C6.4.6.2.

22 PWS: FA8823-15-C-XXXX

STD #26: The RST shall conduct self-inspections, as applicable, support formal inspections, as required and use the Management Internal Control Toolset (MICT) or any other

Government designated inspection checklists.

Deliverables

N/A

3.3.12 The RST shall perform remote site safety for all on-site facilities (ground safety), all on-site GEARSS contractor personnel (industrial safety) and mission system safety.

STD #1: The RST shall administer/establish the safety program for all personnel on-site and attend meetings as required IAW AFI 91-202 and all applicable supplements.

STD #2: The RST shall provide regular safety education (safety grams, 50SW/SE safety notices, etc.) to site personnel and complete and process mishap notifications IAW host base instructions.

STD #3: The RST shall manage the First Aid/CPR, Automatic External Defibrillator (AED) programs. The RST shall ensure all site personnel maintain current industry safety certifications.

STD #4: The RST shall support the 50 SW System Safety Office for 50 SW facility systems

IAW AFI 91-202 and 50 SWI 91-205 for 50 SW GSUs. The RST shall ensure the 50 SW facility systems comply with 50 SWI 33-105, MIL-STD 882E, OSHA, and AFOSH standards.

STD #5: The RST shall monitor 50 SW/SE identified mission-critical facility systems construction and operations and maintenance activities throughout their operational life. The

RST shall coordinate and provide systems safety status to 50 SW/SE.

STD #6: The RST shall identify, investigate and analyze systems safety status and hazards, and make recommendations to 50 SW/SE for corrective actions.

STD #7: The RST shall conduct an annual facility inspection on 50 SW/SE identified mission-critical facilities and as requested for unique instances, i.e. major modifications to facilities. The RST shall inspect facilities and recommend acceptance after modification, renovation, or new construction to 50 SW/SE.

STD #8: The RST shall provide a System Safety Assessment Report (SSAR), in RST format, for each inspection, to include an analysis of the electrical, power, heating, ventilation, air conditioning (HVAC), fire suppression, lightning protection, and miscellaneous systems.

STD #9: The RST shall review and use existing checklists for safety requirements, codes, and specifications that are applicable to the facility, facility systems, subsystems, and operations.

23 PWS: FA8823-15-C-XXXX

STD #10: The RST shall provide recommendations to 50 SW/SE if checklists need to be changed, added, or deleted.

STD #11: Provide technical support to 50 SW/SE personnel during reviews and system safety related meetings at the GSUs.