GEARSS_II__PWS_20180212.docx
DOCX document 92 KB Posted
- Attached to
- Industry Comments/Review of Draft GPS Engineering, Analysis & Remote Site Sustainment II (GEARSS II)
- Solicitation number
- FA882318R0007
About this file
GEARSS II PWS
View the file
Other files
| File | Type | Posted |
|---|---|---|
| GEARSS_II,_Gov_Responses_to_Draft_RFP_CRM.pdf | ||
| 04_GEARSS_II_DRAFT_RFP_CRM.xlsx | XLSX spreadsheet | |
| 00_FA8823-18-R-0007,_GEARSS_II_Draft_RFP_20180321.pdf | ||
| 01_DD_Form_2345,_Militarily_Critical_Technical_Data_Agreement.pdf | ||
| 03_GEARSS_II,_QASP_(DRAFT).pdf | ||
| 02_SMC_OCI_Mitigation_Plan_Checklist.pdf | ||
| GEARSS_II_Government_Responses_to_CRM_20180226.xlsx | XLSX spreadsheet | |
| GEARSS_II_CRM.xlsx | XLSX spreadsheet | |
| SECTION_M_20180212.docx | DOCX document | |
| SECTION_L_20180212.docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
DRAFT
TBD
Performance Work Statement (PWS) GPS Engineering, Analysis & Remote Site Sustainment II 1 Introduction The GPS Engineering, Analysis & Remote Site Sustainment II (GEARSS II) 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. 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 II 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 United States Nuclear-Detonation (NUDET) Detection System (USNDS) 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 USNDS, 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 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 MCS and AMCS; 2) four dedicated Ground Antennas (GA); and 3) six Monitor Stations (MS). The MCS is located at Schriever Air Force Base (SAFB) and is the center for all on-orbit GPS mission control operations. The AMCS is located at Vandenberg AFB (VAFB). 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.
OCX is anticipated to be delivered October 2022 (Objective)/October 2023 (Threshold). Once delivered, OCS and OCX will perform dual operations until the operational community formal accepts OCX. Additionally, OCX interim contractor support (ICS) is anticipated to begin when OCX is delivered and possible extend beyond operational acceptance (~18-30 months in length). OCX will comprise the same three major elements as the OCS: 1) the MCS and AMCS; 2) four dedicated GAs; and 3) six MSs.
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 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 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. Support for the GIN will be required 24/7.
Red Dragon Cyber Security Suite (RDCSS) The RDCSS provides the 2 SOPS Defensive Cyber Operations team a SIEM (Security Information and Event Management) capability. RDCSS supports threat detection and security incident response through the real-time collection and historical analysis of security events from a wide variety of event and contextual data sources within the OCS system. Located at Schriever AFB, it consists of a pair of user workstations and an ensemble of hardware and software. A relatively ‘new’ capability in support of protecting the 2 SOPS mission and OCS, RDCCS support will be required 24/7.
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. Daily on-site maintenance is provided via a separate contract, 12 hours a day, 5 days a week.
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. Daily on-site maintenance is provided via a separate contract, 12 hours a day, 5 days a week.
GPS Support Facility (GSF) The GSF is a facility in Building 400 at SAFB. 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, 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 SAFB, 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 GPS SVs.
Telecommunications Simulators The telecommunications simulators consist of hardware and software which simulate the 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).
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, 5 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, 5 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 GCS contractor personnel (industrial safety) and mission system safety.
6) Perform Emergency Management requirements for ASCN, KWAJ, DIEGO, COSPM and CAPE for all on-site GCS contractors.
7) Perform COMSEC Responsible Officer (CRO) duties for all mission locations that require handling of COMSEC materials.
8) Provide mission essential Defensive Cyberspace Operations (DCO) support to include, but not limited to: trained DCO personnel; performing DCO crew member duties and responsibilities 24/7 in accordance with Government-provided processes and procedures; performing DCO data analysis and trend correlation; and maintaining required DCO proficiency and certification.
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 Procurement 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 A006. 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 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. |
| 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 II 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 II 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. |
| 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 | 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 PCO) 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. |
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 | The contractor shall prepare for and brief to the Government technical status of program management, schedule, risk management, accomplishments, issues and upcoming events for all GEARSS II tasks. |
Performance Standards
| STD #1: | The contractor shall conduct the status meeting monthly. |
| STD #2: | The contractor shall provide an Isolated Development Lab (IDL)/Windchill link, via e-mail to the Government, of the location of meeting charts at least 2 calendar days before the meeting. |
| STD #3: | The contractor shall provide an IDL/Windchill link, via e-mail to the Government, of the location of meeting minutes within 3 working days after meeting. |
| Deliverables | A001 – Monthly Contractor Performance Status Report (MCPSR) |
| 3.1.2 | The contractor shall author and submit AFTO 22/252s to report and correct deficiencies in published TOs. |
Performance Standards
| STD #1: | The contractor shall ensure that requested changes 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 Urgent findings are documented and submitted within 48 hours of finding. |
| STD #4: | The contractor shall ensure Routine findings are documented and submitted within 7 calendar days of finding. |
| Deliverables | N/A |
| 3.1.3 | The contractor shall maintain accountability of all Government Furnished Property (GFP). |
Performance Standards
| STD #1: | The contractor shall manage all GFP IAW clauses included in Section I of the GEARSS II contract schedule. |
| Deliverables | N/A |
| 3.1.4 | The contractor shall maintain the NAO Position Training Standard (PTS)/Position Training Guide (PTG). |
Performance Standards STD #1: The contractor shall update the NAO PTS/PTG, as required, to include system configuration updates, software maintenance releases, system modifications or upgrades.
NOTE: The Government will provide a baseline NAO PTS/PTG at contract award.
| STD #2: | The contractor shall make the NAO PTS/PTG available to the Government upon request. |
| Deliverables | A008 - NAO Position Training Standard (PTS)/Position Training Guide (PTG) |
| 3.1.5 | The contractor shall maintain the DCO Crew Binder. |
Performance Standards STD #1: The contractor shall update the DCO Crew Binder, as required, to include system configuration updates, GPS Operator checklist updates, DCO responsibilities changes, DCO certification criteria mandates and other operational procedure fiats.
NOTE: The Government will provide a baseline DCO Crew Binder at contract award.
| STD #2: | The contractor shall make the DCO Crew Binder available to the Government upon request. |
| Deliverables | A002 - GPS DCO Crew Binder |
3.2 The contractor shall provide Network Administrative Operator (NAO) support.
NOTE: The NAO is synonymous with the Ground System Specialist (GSS) position as part of the OCX operations crew. The tasks below apply to the OCS NAO and the OCX GSS positions. The Government intends to transition from the NAO to the GSS after OCX is operationally accepted.
3.2.1 The contractor shall provide NAO crew members.
NOTE: Prior to certification, the NAO may be required to participate in a review panel and complete a formal mission ready briefing to the 2 SOPS/CC/DO and the contractor supervisor.
NOTE: Once the Government transitions from the NAO to the GSS position, the contractor shall provide trained, proficient and certified GSS crew members IAW published training standards and guides. The Government will provide all applicable standards and guides when the transition occurs.
Performance Standards
| STD #1: | The contractor shall ensure all NAO crew members are trained, proficient and certified IAW NAO Position Training Standard (PTS)/Position Training Guide (PTG). |
| STD #2: | The contractor shall ensure 24-hours per day, 7-days per week NAO coverage and coordinate scheduling with the 2 SOPS crew scheduler. |
| STD #3: | The contractor shall notify the on-duty Crew Commander when a condition exists, either physical or mental, and affecting themselves or other unit personnel that may prevent mission accomplishment or endanger personnel safety. |
| Deliverables | 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 operational communications 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 notify the on-duty Crew Commander and Crew Chief immediately when an anomalous condition is discovered and recommend fix-actions IAW published technical orders. |
| STD #3: | The contractor shall analyze and isolate all communications-related malfunctions and reconfigure ground systems equipment as required to maintain mission operations IAW published technical orders. |
| Deliverables | N/A |
| 3.2.3 | The contractor shall provide NAO support on-site at the AMCS in support of 2 SOPS MOX activities. |
Performance Standards
| STD #1: | The contractor shall conduct MOX 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 | N/A |
| 3.2.4 | The contractor shall maintain the NAO Position Training Standard (PTS)/Position Training Guide (PTG). |
Performance Standards STD #1: The contractor shall update the NAO PTS/PTG, as required, to include system configuration updates as a result of software maintenance releases, system modifications or upgrades.
NOTE: The Government will provide a baseline NAO PTS/PTG at contract award.
Deliverables A008 - NAO Position Training Standard (PTS)/Position Training Guide (PTG)
3.3 The contractor shall provide on-site Remote Site maintenance support.
NOTE: The Remote Site Technician (RST) will be responsible for the tasks below for the OCS until OCX is operational accepted. The RST will only be responsible for Air Force GA/MS assets.
3.3.1 The contractor shall provide maintenance support per published maintenance TOs for ASCN, KWAJ, DIEGO and CAPE.
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 RST on-call support. |
| STD #3: | The contractor shall provide a minimum of two qualified RSTs at each remote site location at all times when conducting maintenance activities that require two persons for safety and security situations. |
| STD #4: | The RST shall maintain Forward Supply Point and Bench stock assets, with accurate inventories IAW the authorized sparing levels. |
| STD #5: | The contractor shall complete back order requests as shortages are noted in the Forward Supply Point. |
| STD #6: | The contractor shall follow AFMCI 23-101 and MIL-PRF 49506 for Standard Base Supply System (SBSS) actions. |
| Deliverables | A009 – GPS RST Offsite Work Log (GROWL) |
A010 – GPS RST Offsite Work Log Enhanced Report (GROWLER)
3.3.2 The contractor 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 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 contractor shall initiate troubleshooting within 1 hour of notification during off duty hours and within 5 minutes during duty hours. |
| STD #3: | The contractor shall provide an Estimated Time to Restore Operations (ETRO) and modification completion time to the on-duty 2 SOPS Crew Commander within 90 minutes of initial notification for problems affecting OPSCAP. |
| STD #4: | The contractor shall provide an updated repair and modification time at least 30 minutes before the initial estimate expires if initial estimate cannot be met. |
| STD #5: | The contractor shall initiate organizational level corrective maintenance and respond to outages impacting mission IAW applicable maintenance TOs. |
| STD #6: | The contractor shall perform organizational level maintenance IAW the Source, Maintainability and Recoverability (SMR) code as defined in the applicable system technical orders. |
| Deliverables | N/A |
| 3.3.3 | The contractor shall conduct all preventive and periodic maintenance required by published procedures. |
Performance Standards
| STD #1: | The contractor shall perform all PMIs IAW applicable technical publications. |
| STD #2: | The contractor shall make appropriate updates in IMDS upon completion of PMIs. |
| STD #3: | The contractor 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 #4: | The contractor shall provide maintenance support for Jet Propulsion Lab (JPL) assets only upon request 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 #5: | The contractor 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 Uninterrupted Power Supply (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. |
| STD #6: | The contractor shall provide maintenance to support integration of NGA assets only upon coordination through SMC/GPL for NGA receiver equipment. |
NOTE: No regular PMIs are supplied for the NGA equipment and there are no defined routine maintenance requirements.
Deliverables N/A
3.3.4 The contractor shall conduct and manage the Test, Measurement and Diagnostic Equipment (TMDE) program.
Performance Standards
| STD #1: | The contractor shall maintain the Custodian Authorization Custody Receipt Listing (CA/CRL) of the TMDE owning activity. |
| STD #2: | The contractor shall establish and operate controls to ensure all TMDE is repaired, calibrated, and certified. |
| STD #3: | The contractor 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 Precision, Measurement, Equipment Laboratory (PMEL) directives and applicable supplements. |
| STD #4: | The contractor shall transport TMDE between the work-center and the local PMEL facility. |
| STD #5: | The contractor shall follow-up on all TMDE in PMEL over 30 calendar days. |
| Deliverables | N/A |
| 3.3.5 | The contractor shall maintain current and accurate technical documentation. |
Performance Standards
| STD #1: | The contractor shall ensure all publication sets for all assigned equipment are IAW TO 00-5-1. |
| STD #2: | The contractor shall utilize sub-accounts through the 50 SW Technical Order Distribution Office (TODO). |
| Deliverables | N/A |
| 3.3.6 | The contractor shall utilize Integrated Maintenance Data System (IMDS) for documenting all maintenance actions. |
Performance Standards
| STD #1: | The contractor shall enter all maintenance actions into IMDS no later than 60 minutes after the job is identified. |
| STD #2: | The contractor shall complete all actions required to close out the assigned IMDS jobs. |
| STD #3: | The contractor shall verify the IMDS Equipment Inventory List (EIL) annually or upon updates to equipment assigned to verify consistency between IMDS data and physical resources under contractor’s control. |
| STD #4: | The contractor shall enter historical data documentation in IMDS IAW MPTO 00-33A-1001, paragraph 7.6. |
| Deliverables | N/A |
| 3.3.7 | The contractor shall ensure compliance with all remote site mandated guidance. |
Performance Standards
| STD #1: | The contractor shall comply with all Time Compliant Technical Orders (TCTO). |
| STD #2: | The contractor 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 contractor shall ensure all personnel performing maintenance, repair, or construction comply with Facilities Excellence Plan. |
| STD #4: | The contractor shall inform the appropriate contractor or DoD personnel for corrective action when non-compliance is identified within their work areas. |
| STD #5: | The contractor shall comply with all Real Property (RP) and RP Installed Equipment (RPIE) warranties and guarantees. |
| Deliverables | N/A |
| 3.3.8 | The contractor shall monitor all on-site construction activities. |
Performance Standards
| STD #1: | The contractor shall report the status of construction projects affecting the site to Government representatives weekly. |
| STD #2: | The contractor shall review and provide comments to the Government on impact to mission and schedule for all site-related construction projects. |
| STD #3: | The contractor shall track, report, and document utility outages. |
| STD #4: | The contractor 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 contractor shall identify requirements and initiate work requests for all construction project using AF Form 332 or other applicable host base forms. |
| STD #6: | The contractor shall maintain a log of all service calls, work requests, and job orders. |
| Deliverables | N/A |
| 3.3.9 | The contractor shall comply with all site-specific environmental, fire and hazardous material policies. |
Performance Standards
| STD #1: | The contractor shall comply with all environmental programs IAW all applicable directives, executive orders, treaties, agreements, and host base OIs and plans. |
| STD #2: | The contractor shall comply with environmental standards; permit conditions, policies, laws and regulations at all locations. |
| STD #3: | The contractor 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 contractor shall comply with host base environmental programs and participate in meetings at the request of the site commander. |
| STD #5: | The contractor shall comply with and support the host base fire protection standards, department regulations and directives. |
| STD #6: | The contractor shall ensure that each facility is maintained in a fire safe condition and compliant with the applicable Air Force and NFPA codes and standards. |
| Deliverables | N/A |
| 3.3.10 | The contractor shall perform COMSEC Responsible Officer (CRO) duties. |
Performance Standards
| STD #1: | The contractor shall perform duties and tasks as assigned and identified in AFMAN 33-283 and AFKAG 2 to ensure the installation COMSEC account programs comply with all Information Assurance Assessment and Assistance Program requirements defined in AFI 33-230, or IAW host base policies and procedures. |
| STD #2: | The contractor shall appoint a CRO, in writing, to the designated authority. The CRO shall accomplish required training IAW AFMAN 33-283. |
| STD #3: | The contractor shall ensure the CRO is trained and possesses a security clearance commensurate with the highest classification of materials required. |
| STD #4: | The contractor shall ensure all COMSEC aids and equipment is current and up-to-date. |
| STD #5: | The contractor 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 contractor shall perform a monthly account inventory and perform any equipment maintenance at that time. |
| STD #7: | The contractor shall maintain the account in accordance with CRO procedures. |
| STD #8: | The contractor shall perform routine secure telephone equipment rekeys annually or as required as indicated on equipment display. |
| STD #9: | The contractor shall report issues or deviations from established procedures to the CRO and distant end immediately upon discovery. |
| STD #10: | The contractor shall maintain all COMSEC accounts with zero errors found during COMSEC inspections. |
| Deliverables | N/A |
| 3.3.11 | The contractor shall perform site-specific essential duties, remote site safety and emergency management duties to meet mission requirements. |
Performance Standards STD #1: The contractor shall manage their respective remote site to ensure all local safety, environmental, administrative and facility standards are met.
STD #2: The contractor shall meet the requirements of applicable publications listed in paragraph 4.4 of this PWS in the execution of site-specific essential duties.
STD #3: The contractor shall serve as the Records Custodian at their respective remote site.
| STD #4: | The contractor 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. |
| STD #5: | The contractor shall manage the First Aid/CPR, Automatic External Defibrillator (AED) programs. The contractor shall ensure all site personnel maintain current industry safety certifications. |
STD #6: The contractor shall support exercises when required by the government. The support for these exercises shall not require overtime (unless otherwise specified in this PWS) and is limited to the availability of existing site personnel and their capabilities.
STD #7: The contractor shall appoint an Emergency Management (EM) representative and notify the 50 CES/CECR, 50 CES/CEX, the site commander, and local/host base in writing of that appointment within 30 days of contract award and personnel changes.
Deliverables N/A
| 3.4 | The contractor shall provide direct operations support and analysis to 2 SOPS at the MCS and AMCS for a minimum of 12 hours per day, five days per week (0600-1800, Mon-Fri) with 24 hour on-call support. |
| 3.4.1 | The contractor shall provide daily ground system technical support. |
Performance Standards
| STD #1: | The contractor shall support procedure development, data analysis, and other related activities. |
| Deliverables | N/A |
| 3.4.2 | The contractor shall provide system training and training simulation support for the PTE for up to 40 hours per week. |
NOTE: The 40 hours may take place during any shift, night or day.
Performance Standards
| STD #1: | The contractor shall plan, create and execute simulations for operational testing and proficiency training. |
| STD #2: | The contractor shall support simulation operations that require scripting and continuous support during exercises/rehearsals. |
| STD #3: | The contractor shall perform simulations at SAFB and at offsite training facilities within the Colorado Springs area. |
| Deliverables | N/A |
| 3.4.3 | The contractor shall perform technical advisor roles and responsibilities. |
Performance Standards
| STD #1: | The contractor shall provide technical advisors to support systems engineering and integration assessments of new program operational requirements; elimination or change of current operations and procedures; and methods of streamlining operations. |
| STD #2: | The contractor shall review and assess impacts to operations procedures, operations tempo, crew loading, and crew communication and task assignments. |
| STD #3: | The contractor shall recommend changes to operations procedures and training documentation, as necessary. |
| STD #4: | The contractor shall provide technical feasibility and analysis support as required by the Government operational flight commander. |
| Deliverables | N/A |
| 3.4.4 | The contractor shall provide system and operational test support. |
Performance Standards
| STD #1: | The contractor shall provide operational test planning, test execution and test analysis for GPS satellites and the ground system to include the Distributed Communications Controller (DCC) and the HANU interface. |
| STD #2: | The contractor shall support regression testing, satellite re-programmability, upload contact planning and ground verification of on-orbit software as necessary. |
| Deliverables | N/A |
3.5 The contractor shall provide DCO Monitor (DCOM) support.
NOTE: The DCOM is synonymous with the Cyber SME position as part of the OCX operations staff. The tasks below apply to the OCS DCOM and the OCX Cyber SME.
NOTE: The DCO transition period will be 90 calendar days in length and is expected to complete NLT 02 Feb 2021.
3.5.1 The contractor shall provide trained, proficient and certified DCOM personnel IAW the DCO Crew Binder.
NOTE: Prior to performing their first 24/7/365 DCOM shift of this contract, each DCOM may be required to participate in a review panel and complete a formal mission ready briefing to the 2 SOPS Leadership and the Contractor supervisor.
Performance Standards
| STD #1: | The contractor shall notify the on-duty Crew Commander 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 #2: | The contractor shall ensure 24-hours per day/7-days per week/365 days a year DCOM coverage and coordinate scheduling with the 2 SOPS crew scheduler. Coverage is defined as in-person, and on-call (as necessary). |
| STD #3: | The contractor shall complete the 2 SOPS DCO Checkout and Evaluation Assessment before being allowed to perform DCO tasks on the mission system. |
| STD #4: | The contractor shall ensure the DCOM is certified to at least Cybersecurity Service Provider (CSSP) Analyst and CSSP Incident Responder according to Appendix 3 in DOD 8570.01-M. |
| STD #5: | The contractor shall ensure the DCOM is a certified Splunk User. |
| Deliverables | N/A |
| 3.5.2 | The contractor shall conduct DCO monitoring operations (24 hours per day, 7 days per week, 365 days a year) to provide visibility into GPS network assets utilizing situational awareness tools. |
Performance Standards
| STD #1: | The contractor shall maintain awareness of GPS network traffic conditions, performance, bandwidth indicators, anomaly alerts, unauthorized activity, audit logs, and any on-going cyber event or incident. |
| STD #2: | The contractor shall notify on-duty crew commander and crew chief immediately when an anomalous condition is discovered and recommend fix-actions IAW Government approved procedures/documentation. |
| STD #3: | The contractor shall identify and document unauthorized activity and/or cyber events to include: source/destination addresses and ports, vector (e.g. network intrusion, web-based, etc.) and timeframe. |
| STD #4: | The contractor shall ensure consistent shift turnover by maintaining event/incident dashboards to include, but not limited to, updating open and closed events/incidents and tracking event/incident analysis. |
| STD #5: | The contractor shall conduct Malware Protection (MP) activities including, but not limited to, network monitoring and/or host-based security, malware incidents, and malware detection signature currency. |
| STD #6: | The contractor shall collect packet capture data in support of Attack Sensing & Warning Components and provide that data during incident response scenarios to the DCO SME and other stakeholders IAW Government-approved procedures/documentation. |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it.