DRAFT_GEODSS_PWS.pdf

GROUND-BASED ELECTRO-

OPTICAL DEEP SPACE

SURVEILLANCE

(GEODSS)

Performance Work Statement

(PWS)

DRAFT

Supporting Sensor Detachments (Dets) at:

Socorro, New Mexico (Det 1)

Diego Garcia, British Indian Ocean Territory (Det 2) Maui, Hawaii (Det 3)

GEODSS PWS

TABLE OF CONTENTS

SECTION 1

GROUND-BASED ELECTRO-OPTICAL DEEP SPACE SURVEILLANCE (GEODSS)

SERVICES REQUIREMENTS PAGE

CHAPTER 1 GEODSS OVERVIEW 3-7

CHAPTER 2 OPTICAL SENSOR OPERATIONS AND SUPPORT 8-14

CHAPTER 3 EXERCISES AND TESTING SUPPORT 15

CHAPTER 4 COMMUNICATIONS-ELECTRONICS (C-E) MAINTENANCE MANAGEMENT 16-18

CHAPTER 5 ELECTRONICS SYSTEMS MAINTENANCE (ESM) TEST, MEASUREMENT AND

DIAGNOSTIC EQUIPMENT (TMDE) 19

CHAPTER 6 SUPPLY 20

CHAPTER 7 FUELS MANAGEMENT 21

CHAPTER 8 COMMUNICATIONS OPERATIONS & MAINTENANCE (O&M) 22-25

CHAPTER 9 ENVIRONMENTAL MANAGEMENT 26

CHAPTER 10 CIVIL ENGINEERING (CE) 27-31

CHAPTER 11 TRAFFIC MANAGEMENT 32

CHAPTER 12 OCCUPATIONAL HEALTH 33

CHAPTER 13 INDUSTRIAL, PHYSICAL AND OPERATIONAL SECURITY 34-35

CHAPTER 14 INFORMATION MANAGEMENT 36

CHAPTER 15 INDIVIDUAL JOB ORDERS 37

CHAPTER 16 CONTRACT TRANSITION 38-39

CHAPTER 17 EXTENDED SPACE SYSTEMS ARCHITECTURE (ESSA) SIDECAR PROTOTYPE 40-46

CHAPTER 18 NET-CENTRIC SENSORS AND DATA SOURCES (N-CSDS) SIDECAR

SUSTAINMENT 47-49

SECTION 2 GEODSS SERVICES SUMMARY 50-51

SECTION 3 GOVERNMENT-FURNISHED EQUIPMENT, PROPERTY, INFORMATION AND

SERVICES 52-54

APPENDICES

APPENDIX A GEODSS REPORTING REQUIREMENTS 55-62

APPENDIX B GEODSS PUBLICATIONS 63-69

APPENDIX C HOST INSTALLATION PLANS, POLICIES AND PROCEDURES 70

APPENDIX D GEODSS PWS ACRONYMS 71-76

APPENDIX E GEODSS PWS DEFINITIONS 77-90

GEODSS SERVICES REQUIREMENTS

CHAPTER 1

GEODSS OVERVIEW

1.0. MISSION. The GEODSS Program is comprised of three Detachments (Dets) at geographically-separated locations at Socorro, New Mexico (Det 1); Diego Garcia, British Indian Ocean Territory (Det 2); and Maui, Hawaii (Det 3). Each Det operates with three optical telescopes (referred to as optical sensors throughout the PWS). The 21st Operations Group (21 OG), Peterson Air Force Base (AFB), Colorado, has responsibility for all GEODSS Dets.

The GEODSS system supports the United States Strategic Command (USSTRATCOM) and theater war fighter’s requirements through the detection and surveillance of deep space satellites. The system detects, tracks, identifies, and reports on all deep-space man-made objects in the Earth’s orbit within the telescopes’ field of view. The GEODSS Dets perform the mission using three 1-meter telescopes each with a 1.68 degree field of view; low light level, electro-optical cameras; and high speed computers. These optical sensors detect sun light reflecting off of space objects. Mission operations are conducted between civil sunset and sunrise. Satellite information is provided to the Joint Space Operations Center (JSpOC) at Vandenberg AFB, California.

1.1. SCOPE. The Contractor shall provide non-personal services to manage, operate, maintain, and provide logistical and general support services for the GEODSS system at Det 1, Det 2 and Det 3. In addition to providing GEODSS system operation and maintenance (O&M) requirements, contracted services include exercise and testing, communications-electronics maintenance management, electronic systems maintenance, supply, fuels, communications, environmental, civil engineering, traffic management, occupational health, security and information management requirements. Services will also be provided in support of system upgrades and modifications. The Contractor shall perform organizational level maintenance on system upgrades and modifications once they are accepted by the Government.

1.1.1. GEODSS PWS Requirements. Except as provided in Section 3, Government-Furnished Equipment, Property, Information and Services, the Contractor shall provide all personnel, tools, materials, transportation, supervision and other items necessary to perform GEODSS PWS requirements 16-hours-a-day, 7-days-a-week (16/7) basis. The Contractor’s furnished materials and equipment shall include vehicles, vehicle fuel, tools, custodial supplies, office administrative supplies and equipment, grounds-keeping equipment and any other supplies and materials not furnished by the Government which the contractor believes necessary to perform these requirements. Unless otherwise specified, the stated requirements pertain to all Dets; inclusions or exclusions will be clearly stated in individual PWS paragraphs (paras).

1.1.2. System Certification and Accreditation (C&A). Provide information to support certification activities and maintain the C&A artifacts IAW Air Force Instruction (AFI) 33-200 para

2.27.8 and the Department of Defense Information Assurance Certification and Accreditation Program (DIACAP). The Contractor shall not implement any local hardware or software changes that will impact the C&A package without prior authority.

1.1.2.1. Installation and Checkout Test Plan. Develop and submit installation and checkout plans for newly installed hardware, firmware, or software through the Det CC to the 21 OG/CC for final approval. See Appendix A, Report Number R1-3.1, Installation and Checkout Test Plan.

Execute approved installation and checkout plans with Government oversight to final approval and acceptance by the Government.

1.1.2.2. Testing Agency Support. Interface and assist in testing activities being accomplished by Government and other Contractor team personnel. Provide data and feedback to the teams on the adequacy of test procedures noting any system deficiencies or anomalies, and assist in developing methods for ensuring all testing is complete prior to system acceptance.

1.1.3. Continuance of Performance/Mission Essential Services. In the event of a crisis declared by the President of the United States and/or the Secretary of Defense, the Contractor shall continue all PWS requirements except the tasks in PWS Chapters (Chs) 3, 9, 11, 12 and 14 through 16. The Contractor shall continue services through all Force Protection and Defense Conditions without interruption. In a time of crisis, other services to increase the security and well-being of the Sites may be required on a 16/7 basis as identified by the Det Commanders (CCs) and directed by the Contracting Officer (CO), and will be funded via cost-reimbursable (CR) contract line item number (CLIN).

1.1.3.1. Contingency Planning. The Contractor shall develop a contingency plan for continued operations and timely return of systems to operational status in the event of a declared crisis, catastrophic and non-catastrophic events and work stoppages for each site.

Include all the PWS requirements identified in PWS para 1.1.4 above. The plan shall contain the following information at a minimum: contingency actions, emergency work requests, natural disasters, labor strike/personnel walk-off, contingency mobilization and mobilization recall commitments. Provide a copy of the contingency plan at contract start and updates as changes occur.

1.1.3.2. Incident Reporting. The Contractor shall notify the Det CC, Government Program Manager (PM), CO and other responsible agencies involved of all incidents, accidents, threats, events, and natural disasters (impending or actual) that may affect or involve the performance of PWS requirements.

1.1.4. Outside Agency Support. The Contractor shall interface with other Contractors and Government agencies in support of programs and efforts dealing with the evolution and operation of systems and equipment, as well as providing day-to-day Det support services. This includes providing technical assistance and advice to other Contractors or Government agencies to support design, development, and installation of new facilities, systems, or equipment within existing PWS areas of expertise.

1.2. GENERAL REQUIREMENTS. The Contractor shall:

1.2.1. GEODSS Operating Instructions (GOIs). Document current operations in GOIs where other manuals and directives are not available or do not provide sufficient instructions. See Appendix A, Report Number R1-1.1.

1.2.2. Quality Program. Develop, implement and maintain a Quality Program ensuring service delivery meets or exceeds performance requirements in the PWS.

1.2.2.1. Quality Program Plan. Implement the Quality Program IAW a Quality Program Plan (QPP) providing insight into the following quality processes: internal audits including procedures and oversight, identification of deficiencies, prevention of nonconforming services, and corrective measures if performance requirements are not attained. Provide a copy of the QPP at contract start and updates as changes occur. Provide copies of BAE’s internal audits to the Government Quality Assurance Specialist.

1.2.2.2. Site Quality Status Report (QSR). The Contractor shall generate and distribute a QSR. See Appendix A, Report Number R1-1.2.

1.2.3. Technical Meetings and Conferences. Participate in sustainment and performance working group meetings, Space Situational Awareness Conferences, Multi-Functional Team (MFT) meetings, and weekly SENSOR O&M Teleconferences. The Contractor shall also participate in the weekly Maintenance Production Status Teleconference and provide briefing slides. See Appendix A, Report Number R1-1.3.

1.2.4. Familiarization Briefings and Tours. Conduct Det briefings, such as technical orientation/familiarization briefings, and tours when requested by the Det CC.

1.2.5. Briefings, Meetings and Tours Workload Data. Maintain workload data on briefings, meetings and tours. See Appendix A, Report Number R3-3.2.

1.2.6. Budget Information. Participate in developing budget information including projected costs for unfunded requirements with justification and impact statements.

1.2.7. Referenced Publications. The contractor shall comply with the requirements cited in PWS publication references preceded by “IAW.” See Appendix B for list of GEODSS publications.

1.2.8.1. Host Installation plans, policies and procedures referenced within individual PWS paragraphs are listed by title in Appendix C. Otherwise, apply industry standards and commercial best practices and comply with local, state and federal statutes in the performance of PWS requirements.

1.2.8.2. Notify the CO of any changes in publications listed in Appendix B and Host Installation plans, policies and procedures in Appendix C within 30 days of receipt of revisions, changes, supplements, and notifications of rescission. Contractor will immediately implement those changes. Before implementing any change that will result in an increase in contract price, the contractor will submit to the CO a price proposal within thirty (30) calendar days following receipt of the change by the contractor. The CO and the contractor will negotiate the change into the contract under the provisions of the contract clause entitled “Changes.” Failure of the contractor to submit a price proposal within thirty (30) calendar days following receipt of the change entitles the Government to performance according to such change at no increase in contract price.

1.2.9. Records, Documentation and Reports. The Contractor shall:

1.2.9.1. Existing Records. Maintain all Government records in the format provided. See Chapter 14, para 14.1 for additional records management requirements.

1.2.9.2. Generated Documentation. Maintain all records generated in performance of PWS requirements in electronic format and make a copy available for Government review upon request.

1.2.9.3. Contractor Reports. Provide electronic reports to the Government as specified in Appendix A. Contractor format is acceptable unless specified otherwise.

1.2.10. Training. The Contractor shall manage training and development activities designed to ensure technical competency of Contractor personnel. The Contractor shall fund for all personnel training unless it is Government unique as specified below.

1.2.10.1. Government Unique Training. Some required training is Government unique and is identified as required training in individual PWS chapters. Additionally, the Contractor shall complete Computer Based Training (CBT) courses deemed necessary by the Air Force (AF).

1.2.10.2. Reimbursable Training Costs. The Government will provide government-unique training, and will reimburse the contractor initially for personnel attendance. The Contractor shall reimburse the Government for Government-funded training expenses when personnel turnover causes the need for repetition of Government-provided training within one year of course completion. Knowledge gained by Contractor personnel at Government training courses and conferences shall be disseminated to other contractor personnel requiring the same information. This ensures that such attendance is beneficial to as many personnel as possible, keeping Government training costs to a minimum.

1.2.11. Contractor Manpower Reporting. The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via a secure data collection site. The contractor is required to completely fill in all required data fields using the following web address http://www.ecmra.mil. See Appendix A, Report Number R1-1.5.

1.2.11.1. 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. The contractor shall complete input of FY12 labor data no later than 31 Jan

13. Contractors may direct questions to the ECMRA help desk.

1.3. PROGRAM MANAGEMENT. The Contractor shall report problems affecting functional area mission accomplishment or Contractor performance to the Det CC or designated representative. The Contractor shall:

1.3.1. Key Points of Contact. Provide the names, home, and duty phone numbers of key points of contact at each of the GEODSS locations to the Det CCs, GEODSS PM and CO in writing seven calendar days after contract award and within five calendar days of any subsequent changes thereafter.

1.3.2. Safety and Security. Inform, educate, and provide guidance to Government personnel (military and civilian) at the Dets in the interest of safety, security, and mission accomplishment.

Report any violations to the Det CC.

1.3.2.1. Safety Training and Meetings. The Contractor shall attend Host Installation safety training and provide safety information to all Contractor personnel. At Det 3, the Contractor shall attend Host Installation safety meetings and participate in safety committees.

1.3.2.2. Det CC’s Authority. Det CC may remove any personnel from the Det when retention of such personnel endangers life, property, or security.

http://www.ecmra.mil/

1.3.3. Withdrawal of Privileges. The Det CC may withdraw site privileges from Contractor personnel, upon investigation of facts and circumstances, if those privileges are abused.

Privileges may be withdrawn by the Det CC on a permanent or temporary basis.

1.3.4. Site Personnel Evacuation. The Contractor shall evacuate a site whenever directed by the Det CC, or at Contractor discretion if Det CC is unavailable. At Det 1, the Contractor may be required to evacuate personnel in support of White Sands Missile Range special missile tests and launches.

1.3.5. Detachment Commander (Det CC) Weekly Briefings. Provide a formal weekly briefing to the Det CC. Briefing will include status of operations and maintenance and any inspections, exercises, visits, etc.

CHAPTER 2

OPTICAL SENSOR OPERATIONS AND SUPPORT

2.0. GENERAL. The Contractor shall provide optical sensor operations, technical services, operations support, and maintenance of Det equipment to meet sensor mission requirements.

2.1. SENSOR OPERATIONS. The Contractor shall accomplish the sensor mission IAW STRATCOM Directive (SD) 505-1(S), Volume (Vol) I and II, 14AF Space Tasking Order and Space Standing Order. Operate all available sensors during the operational period to meet taskings. Ensure that all available sensor time in excess of that required to accomplish taskings is used to perform area searches or other tasks. In addition, the Contractor shall:

2.1.1. Mission Scheduling. Accomplish mission scheduling before the start of the operational period by identifying routine and special metric taskings, Space Object Identification (SOI) signature gathering and raw video collection (seldom performed), to be accomplished during the operational period. Incorporate SOI taskings to maximize system accomplishment of daily, weekly, and monthly tasking requirements. Schedule attempts to provide time separation within weather, equipment, and tasking constraints based upon weekly or monthly requirements.

2.1.2. Taskings. Accomplish Higher Headquarters (HHQ) taskings and reporting requirements issued by the JSpOC, the Alternate Space Control Center (ASCC), National Air and Space Intelligence Center (NASIC) and USSTRATCOM. Maintain workload data on number and frequency of taskings and reporting requirements. See Appendix A, Report Number R3-3.2.

2.1.2.1. Metric Taskings. Perform metric taskings as directed by JspOC in the Consolidated Tasking List (CTL) and associated updates.

2.1.2.2. SOI Taskings. Complete 100 percent of SOI-tasked objects each month. Maintain workload data on number and frequency of SOI taskings. See Appendix A, Report Number R3-3.2. Maintain and keep current the SOI software package.

2.1.2.2.1. SOI Reporting. Report to tasking agency, objects below 15 degrees site horizon, lower than 15,000 kilometers, above 50,000 kilometers, or at continuously low sun angles for consideration of tasking removal. If object is not tracked due to the above limitations, notify the Contracting Officer Representative (COR).

2.1.3. Manually Tasked Objects. Enter taskings manually if not received through normal channels. Perform manual scheduling, special sensor settings and other special techniques.

2.1.4. Operations Logs. Document operations, security events, equipment status, authorized software changes, weather, shift changes, changing of the Zulu day and any other significant events in an operations log. Include start and end times for events as well as initials of individuals exchanging information. Maintain operations logs in Contractor-preferred system (e.g., hard copy, Microsoft Access, etc.) which ensures data cannot be altered after entries are made.

2.1.5. Sensor Calibrations. Complete calibrations IAW GEODSS technical order (TO) 31-S1-2FSQ-201-1. Accomplish calibrations on a non-interference basis for Category I mission taskings IAW SD 505-1(S) Vol I and II.

2.1.5.1. Mount Calibrations. Conduct mount calibrations to ensure mission accomplishment.

Document erroneous information in the operations log. Whenever weather or priority tasking does not allow calibrations to be performed, use default calibrations until conditions and tasking requirements allow sensor calibrations to be accomplished.

2.1.5.2. Calibration Satellites (CalSats). When directed by JspOC, accomplish and track CalSats at specified frequencies with each available sensor.

2.1.5.3. SOI Calibrations. Accomplish SOI calibrations for sensors scheduled for SOI data collection or to ensure alignment.

2.1.6. Visual Magnitude Data. Provide visual magnitude data to JspOC. Data is to be sent monthly using the most expeditious means available.

2.1.7. Sensor Contractor Controlled Availability (Acc) and Operational Availability (Ao) by Site.

2.1.7.1. Acc Calculation. Maintain an overall sensor Acc each calendar month of not less than 97% to meet mission operational requirements defined in SD 505-1(S) Vol I and II. See Section 2, GEODSS Service Summary. Acc is expressed as a percentage and represents that portion of time the system is performing its assigned mission based on the Contractor liable downtime (CLD) relative to a specified operating time. The Acc is calculated on a monthly basis as follows:

Acc = Active Minutes – CLD Downtime Active Minutes

2.1.7.2. Acc Sample Calculation. If a site had three sensors available and all three were 500 minutes of available operational time, the total active hours would be 1500 minutes. If two sensors were available for the entire period and one sensor was not available for 75 minutes because of contractor personnel operator error, the calculation for Acc would be calculated as Acc =1425/1500=.95. See Appendix E for Acc formula definitions.

2.1.7.3. Ao Calculation. Provide the monthly calculation for sensor Ao in the QSR. See Appendix A, Report Number R1-1.2. Ao is expressed as a percentage and represents that portion of time the system is performing its assigned mission based on the system downtime relative to a specified operating time. See Appendix E for Ao formula definitions.

Ao = Active Minutes – Downtime Active Minutes

2.1.8. GEODSS Operations Training Plan. Develop and implement a GEODSS Operations Training Plan designed to keep operators proficient in GEODSS mission system requirements.

Standardize training program across the three GEODSS sites. Conduct initial and monthly recurring training, using a task-based approach, addressing mission performance requirements in this chapter. Monthly recurring training shall cover all individual tasks within a one-year timeframe. Provide a copy of the training plan at contract start and updates as changes occur.

Provide a copy of the training plan and training materials to the CORs and the Government Program Manager.

2.1.8.1. Annual Certification. Conduct and document training to ensure proficiency in all required functions. Air Force Space Command Instruction (AFSPCI) 36-2202 may be used as guidance. Maintain a comprehensive list of all monthly sensor operations training tasks.

Personnel training shall be accomplished prior to or on the last duty day of the month for which it is scheduled. Exception: Personnel on leave or on temporary duty (TDY) will receive recurring training prior to their first duty shift upon return. Certify in writing that operations personnel have completed all applicable training for an operational position. No individual shall perform any system operations task for which they have not been trained unless under the direct supervision of fully trained and certified personnel. Documented completion of recurring training as outlined above and within the Contractor’s Operations Training Plan will constitute annual re-certification.

2.1.8.2. Maintain individual training records for all personnel. Training records shall reflect all training received on- and off-site.

2.1.8.3. Provide initial on-site hands-on-equipment operations training for AF personnel. When the Contractor is training a military member, a minimum of one sensor will remain in operational mode. All available sensors will be made available for the trainee to use, provided a certified contractor is overseeing him. The Contractor will not be held accountable for any mission degradation or equipment damage due to the actions of a certified military member.

2.1.9. Daily Status Report (DSR). Develop and maintain a DSR. See Appendix A, Report mber R1-2.2.

2.2. TECHNICAL SERVICES. The Contractor shall provide technical services to meet sensor mission requirements on a continuous basis. The Contractor shall:

2.2.1. System Performance. Monitor root mail, system logs, security logs, security configuration and performance utilities to assure system performance and identify and correct imminent system failures as defined in GEODSS TO 31-S1-2FSQ-201-1.

2.2.2. System Malfunctions or Anomalies. Notify the COR of all system malfunctions or anomalies upon occurrence.

2.2.2.1. Standard Change Forms (SCFs). Generate an SCF10 within 30 days of an anomaly or outage (if required for the anomaly or outage) IAW 21 Space Wing Instruction (SWI) 63-202, para 1.7.5. Maintain supporting data including references to associated Problem Reports (PRs) (if any), computer printouts and data tapes.

2.2.2.2. System or Software Modifications. Generate an SCF for system or software modifications.

2.2.3. Upgrades and Modifications. Maintain workload data on number and frequency of upgrades and modifications supported below. See Appendix A, Report Number R3-3.2.

The Contractor shall:

2.2.3.1. Development, Test and Evaluate (DT&E) and Software and Operational Test and Evaluation (OT&E). Support the installation and evaluation of all software and hardware modifications to include planning, technical and administrative support. Contractor shall perform applicable test plan actions and notify the COR and testing agencies of any system anomalies.

2.2.4. Unit Requirements Validation Board (URVB). The Contractor shall act as coordinator and recorder for the GEODSS URVB, providing technical expertise as requested. A single URVB meets representing the three GEODSS sites and provides information to the 21st Space Wing Requirements Validation Board (WRVB). Technical inputs may include improvements to software, hardware, operations and maintenance procedures, equipment availability, and utilization.

2.2.4.1. System Changes. Advise the Unit Requirements Validation Board (URVB) in identifying and prioritizing new requirements for, and changes to, the operational system IAW 21SWI 63-202, Chapter 2, paragraph 2.4. Submit change requests to the Wing Requirements Validation Board (WRVB).

2.2.4.2. Collaboration. Participate in system life-cycle activities such as program management reviews, design reviews, tests, and physical and functional configurations audits.

2.3. MISSION SYSTEM SOFTWARE AND EQUIPMENT O&M. The Contractor shall operate, maintain, repair and restore the GEODSS mission system to meet Acc and mission requirements. The Contractor shall:

2.3.1. Mission System Software. Assure continued performance of the mission system IAW the GEODSS Software Programmer’s Manual (SPM) GDS-D-SPM-09000 to meet mission requirements.

2.3.1.1. Mission System Administrator (MSA) Training, Certification and Background Investigation Requirements. Contractor MSAs, assigned to perform mission system administration, shall:

2.3.1.1.1. MSA Training. Complete SPM training (training materials provided by the Government) as well as the Contractor-developed GEODSS operations training. See para 2.1.8 for operations training requirements.

2.3.1.1.2. MSA Certification. Perform Information Assurance Technical (IAT) Level II requirements and maintain an IA certification IAW Department of Defense (DoD) 8570.01-M, Tables C3.T1, C3.T4 and AP3.T1, and a current Tru64 UNIX Operating System Certification.

Report changes to certifications to 21 SW/IA on an annual basis or upon changes to MSAs.

2.3.1.1.2.1. IA Certification. The contractor shall fund the annual IA certification fee for the system administrator and assistant system administrator at Det 1, Socorro, NM and Det 3, Maui, HI IAW BAE letter dated 31 Aug 12, entitled, GEODSS CR CLIN Billing Concerns Update 8-31-

12. The contractor is responsible for earning the required Continuing Education (CE) credits during the year to allow the individual to be recertified at the end of his/hers certification cycle.

Should the contractor not complete the required recertification training in a year's time, the government is not responsible for any testing or recertification fees. Any cost for initial IA certification testing is the individual's or contractor's responsibility.

2.3.1.1.3. MSA Background Investigation. Have successfully completed a Single Scope Background Investigation (SSBI) IAW DoDI 8500.2, Table E3.T1. Note: Requirement is for SSBI only, not to fill a Top Secret billet or position.

2.3.1.2. Software Maintenance, Configuration and Support. Maintain data processing software, database, and system files; perform software installation and system reconfiguration and maintain associated documentation (record time and extent of change as a minimum).

Provide communications and networking support.

2.3.1.3. Software Outages, Backups and Restoral Actions. Troubleshoot software-related outages, backup data and restore operations. Detect and correct faulty computer system processes and replace, restore, or delete corrupt or faulty files. Restore data files, operating systems, and application software from backups to recover from catastrophic software failures on an as needed basis.

2.3.1.4. Accounts. Provide, monitor, and control user accounts and user access to assure GEODSS system integrity and operability. Restore mission user accounts.

2.3.1.5. Time Co-Efficient Updates. Synchronize the Data Processing Group (DPG) and Sensor Controller Group (SCG) computers to Universal Time Coordinated (UTC) IAW the SPM for correct operation of the GEODSS astronomic algorithms.

2.3.1.6. Disk Management. Monitor disk space and fragmentation and balance disks.

2.3.1.7. Documentation. Update and maintain documentation on mission system software and site adaptable parameters integrating changes as required to reflect the current mission system operational and support baseline.

2.3.1.8. Preventive Maintenance. Perform preventive maintenance of mission system software as defined in SPM GDS-D-SPM-09000.

2.3.1.9. Software Maintenance Plan. Implement and maintain an annual Mission System Software Maintenance Plan which details the approach and timeline for meeting the software and MSA support requirements. Document MSA support activities in the System Assessment Report (SAR). See Appendix A, Report Number R1-2.1.

2.3.2. Mission System Equipment O&M. Operate and maintain all mission computer equipment and peripherals needed to support sensor operations IAW GEODSS 31-series TOs on a 16/7 basis. Maintenance requirements and GEODSS TOs are found in Chapter 4, Communications –Electronics (C-E) Maintenance Management. Respond to notification of system problems (red or yellow (amber) site condition) within two hours, diagnose and recover system. Initial response can be telephonically or through e-mail, if the MSA is not physically present at a Det.

2.3.2.1. Mission System Failures. Respond to alarms and mission system failures.

Troubleshoot and restore to operational status. Notify the COR of system degradation or equipment failures that could adversely impact the mission.

2.3.2.1.1. Troubleshooting Assistance. Assist sustainment personnel as required in identifying and isolating faulty systems or subsystems in the GEODSS Auxiliary Instrumentation Group (AIG), DPG, SCG, and the GEODSS secure data communications systems.

2.3.2.1.2. Mission System Actions. Coordinate with the COR for power shutdown, maintenance and system reconfiguration and restoration actions that could impact operations.

2.3.2.1.3. Component Replacement. Replace line replaceable unit (LRU) or component. If replacement components are not available, contact the item manager.

2.3.2.2. Mission System Backups. Ensure servers, workstations, and communications devices are backed up for catastrophic recovery IAW SPM GDS-D-SPM-09000, para 7.4, CM Back-up/Restore Process. Accomplish server backups prior to entering a trial period for any software version release or hardware upgrade. Note the date and time of system backups in the SAR and verify the contents and integrity of the backups. See para 2.3.1.9 for SAR requirements. Store the two most recent full sets of backup tapes in a secure and auditable location.

2.3.2.3. Mission System Equipment Inventory. Perform inventory control and account for mission computer equipment on the Custody Authorization/Custody Receipt Listing (CA/CRL).

For Det 3, provide a copy of the CA/CRL to the Host Installation.

2.3.2.4. Mission System Certification and Accreditation (C&A). Provide information to maintain the mission system C&A IAW Air Force Instruction (AFI) 33-200 para 2.27.8 and the Department of Defense Information Assurance Certification and Accreditation Program (DIACAP) to the Electronic Systems Command (ESC/HSIJO). Notify ESC/HSIJO and 21 Space Wing Program Management Division (21 SW/PMD) prior to implementing any local hardware or software changes impacting the mission C&A package.

2.4. OPERATIONAL SUPPORT REQUIREMENTS. The Contractor shall respond to the direction of the COR in support of operational requirements. The Contractor shall:

2.4.1. Emergency Actions. Perform emergency actions as requested by the COR or Crisis Response Element (CRE). Report on site within two hours of notification. Initial response can be electronically or via telephone, if Contractor personnel are not physically present at a site.

2.4.2. Operational Reporting. Conduct operational reporting on a 16/7 basis as follows:

2.4.2.1. Notify the 21 SW Peterson Installation Control Center (PICC) with information on events or incidents that may require Operational Reporting (OPREP), Situation Reporting (SITREP), and Operations Capability (OPSCAP) reporting IAW AFI 10-206 and its required supplements and or guidance memorandums, SD 505-1(S), and 21 OG policy letters. Maintain instructions for Information Condition (INFOCON) IAW SD 527-1, SITREP, OPREP, Force Protection Condition (FPCON), attainment and all other reporting requirements for both exercise and real world status.

2.4.2.2. Notify the COR of any reportable situation. Make required notifications and submit reports. If the COR cannot be contacted, accomplish the necessary voice and hard copy reporting.

2.4.2.3. Prepare the SITREP, notify the COR of any significant changes and up-channel the report to HHQ IAW the established timelines.

2.4.2.4. Establish the necessary chat-type accounts via Secure Internet Protocol Network (SIPRNet) and Non-secure Internet Protocol Network (NIPRNet). Ensure operators are capable of manning and utilizing “chatrooms” or similar collaboration applications (which applications will be at the discretion of Higher Headquarters (HHQ)).

2.4.2.4.1. When directed by HHQ, the contractor will be responsible for maintaining an actively logged in account for the required SIPRNet and NIPRNet collaboration chatrooms as designated by HHQ.

2.4.2.4.1.1. When actively logged into the HHQ designated account and chatroom, the contractor will check for SIPRNet/NIPRNet chatroom updates and make any postings needed in response to questions or direction from HHQ on a frequently recurring basis of approximately every 20 minutes. During periods of exercise and/or contingency, the contractor will continuously monitor or check collaboration chatrooms approximately every 10 minutes via the SIPRNet & NIPRNet (as determined by contingency or exercise requirements) and make any postings needed in response to questions or direction from HHQ.

2.4.3. Status of Resources and Training Systems (SORTS). Prepare SORTS for COR approval, or designated representative, when COR is absent. Submit SORTS reports IAW AFI 10-201, Chs 1 through 5. Contact the Senior COR to schedule SORTS training

CHAPTER 3

EXERCISES AND TESTING SUPPORT

3.0. GENERAL. The Contractor shall participate in exercises and testing. Immediately limit or terminate support if personnel are needed to meet real world operational requirements. The Contractor shall:

3.1. DET AND HHQ DIRECTED EXERCISES AND INSPECTIONS. Participate in Det exercises and support inspection teams as requested by the COR. Maintain workload data on exercises and inspection teams. See Appendix A, Report Number R3-3.2.

3.1.1. Trusted Agent (TA). Designate a TA at the request of the COR, or representative, before the start of an exercise. The TA shall assist the COR in developing and implementing exercises. The three GEODSS sites may or may not participate in exercises during the same timeframe. Contact the Senior COR to schedule TA training.

3.1.2. Exercise Reports. Provide findings to the COR IAW 21 SWI 10-204, para 2.9.9.

Submit exercise inputs for the SITREP to the COR by the time designated. The COR will review inputs, finalize and return it to the Contractor to incorporate changes and submit report.

3.1.3. Crisis Response Element (CRE). Participate in the unit CRE team during real world events, headquarters inspections, or local exercises as determined by the COR. The Contractor Site Manager and designated key personnel shall report on site no later than two hours for Det 1, one hour for Det 2, and two and one-half hours for Det 3, after initial notification.

3.2. TESTING SUPPORT. The Contractor shall:

3.2.1. Installation and Checkout Test Plan. Develop and submit installation and checkout plans for newly installed hardware, firmware, or software through the COR to the 21 OG/CC for final approval. See Appendix A, Report Number R1-3.1. Execute approved installation and checkout plans with Government oversight for final approval and acceptance by the Government.

3.2.2. Testing Agency Support. Interface and assist in testing activities being accomplished by government and other Contractor team personnel. Provide data and feedback to the teams on the adequacy of test procedures, noting any system deficiencies or anomalies, and assist in developing methods for ensuring all testing is complete prior to system acceptance. Note: The sensor operators will only provide testing agency support on a 16/7 basis.

3.2.3 Visiting Team Preparation. Support other Contractor teams visiting the Dets. Process visit requests, provide information on local lodging, and coordinate receipt and storage of project materials and equipment. Maintain workload data on contractor team support. See Appendix A, Report Number R3-3.2.

CHAPTER 4

COMMUNICATIONS-ELECTRONICS (C-E) MAINTENANCE MANAGEMENT

4.0. GENERAL. The Contractor shall ensure C-E systems are serviceable, safely operable, and properly configured to meet mission requirements and system readiness. Plan, schedule, direct, organize, coordinate, control, document, report, and execute all actions necessary to maintain C-E equipment operability and availability. Perform inspections, repairs, modifications, analyses, and other maintenance related tasks. Maintain logs, records, inspection forms and Maintenance Information Systems (MIS) reflecting equipment status, inspections, and maintenance performed. See Chapter 14, para 14.1 for additional records management requirements.

4.1. SCOPE OF MAINTENANCE. The Contractor shall perform all authorized organizational level maintenance IAW GEODSS TOs: 31-10-7, 31S1-2FSQ114-41, 31S1-2FSQ114-81, 31S1-

2FSQ114-91, 31S1-2FSQ114-181, 31S1-2FSQ114-183, 31S1-2FSQ114-191, 31S1-2FSQ114-

201, and 31S1-2FSQ114-271. Site maintenance level authorized for repair is determined by Source, Maintenance and Recoverability (SMR) Codes and Expendability, Recoverability, Repairability Codes (ERRC) assigned to stock listed items. In addition, the Contractor shall:

4.1.1. Depot Level Maintenance. Request depot level maintenance when the maintenance required is beyond the scope, capability, and authorization given. Maintain workload data on number and frequency of requests for depot level maintenance. See Appendix A, Report Number R3-3.2.

4.1.2. Non-SBSS Inventory Items. Maintain sufficient non-stock listed items (outside the AF inventory) to support daily Det operations.

4.2. C-E MAINTENANCE MANAGEMENT. The Contractor shall:

4.2.1. Programmed Depot Level Maintenance (PDLM) Requests. Submit requests for C-E PDLM requirements and schedule on Air Force Technical Order (AFTO) Form 227 IAW TO 00-25-108, figures 2-2 and 2-3.

4.2.2. Requests for Assistance. Submit Maintenance Assistance Requests for Technical Assistance (TA), Engineering Assistance (EA), Emergency Depot Level Maintenance (EDLM) or Urgent Depot Level Maintenance (UDLM). See Appendix A, Report Number R1-4.1.

4.2.3. Equipment Status Reporting (ESR). Report equipment circuit OPSCAP status changes for all system outages IAW TO 00-33A-1001, para 3.2.1. as they occur. Input data into the Integrated Maintenance Data System (IMDS) ESR subsystem.

4.2.3.1. ESR Changes. Implement changes to ESR provided by 21 OSS/MASW.

4.2.3.2. SRD Reporting. Report all C-E equipment that is assigned Standard Reporting Designators (SRDs) that begin with the alphanumeric characters 1 through 8, B, C, E, F, J, K, Q, and U, as listed in the IMDS Reliability and Maintainability Information System (REMIS) SRD Table.

4.2.4. Maintenance Data Collection (MDC). Collect, input and submit MDC data and utilize all appropriate documentation forms for MDC on systems listed as reportable in the REMIS SRD tables.

4.2.4.1. IMDS Data Entries. Input all MDC data on reportable equipment into the IMDS MDC subsystem IAW TO-00-20-2, paras 1.10, 2.3, and Chs 3 through 7, TO 00-33A-1001, para

3.2.1. applicable –06 TOs, and the following user manuals: AF Computer System Manuals (AFCSMs) 21-556V2, -560V2, -561V2, -562V2, -563V2, -564V2, -569V2, and -571V2.

4.2.5. Scheduled and Unscheduled Maintenance. Maintain, calibrate, and repair C-E equipment, including upgrades and modifications and initiate restoration actions within two hours. Schedule maintenance downtime IAW 21 SWI 10-202 paras 1 through 1.2.3, 1.2.3.2 through 2.1.3, and 2.1.5 through 2.1.5.2.

4.2.5.1. Preventive Maintenance Inspections (PMIs). Load all preventive maintenance routines into the IMDS database for recurring equipment PMIs.

4.2.5.2. Maintenance Events. Maintenance Events. Document scheduled and unscheduled maintenance events for MDC Job Data Documentation (JDD) in the IMDS database for equipment with MDC reportable SRDs IAW TO 00-33A-1001, para 3.2.1.Reference TO-00-20-2 for MDC.

4.2.6. TO System Improvement. Submit AFTO Form 22s to recommend changes. See Appendix A, Report Number R1-4.2.

4.2.6.1. Time Compliance Technical Order (TCTOs). Comply with and respond to TCTOs (Field Change Orders (FCOs) and Equipment Change Orders (ECOs)) within the specified time.

Process and document TCTOs, time change items, and other approved modifications using the instructions in TO 00-5-15. Maintain workload data on number and frequency TCTOs. See Appendix A, Report Number R3-3.2.

4.2.6.2. Proposed Modifications. Route proposed modifications through the URVB process.

See Chapter 2, para 2.2.4 for URVB requirements.

4.2.7. Repairable Assets Status. Determine repairable status of failed assets by the SMR/ERRC and restore serviceability.

4.2.7.1. Non-SMR Coded Items. Repair items with no SMR code (XB3 items) assigned when cost effective or necessitated by mission requirements IAW TO 00-20-2, Table 3-2.

4.2.7.2. SMR Code Changes. Submit request for SMR code changes using Document Routing Entry and Mail Submitter (DREAMS) IAW TO 00-25-195, para 4.2.1 and 4.3.1.

4.2.7.3. Maintenance Turnaround (TRN). Accomplish TRNs for Due in for Maintenance (DIFM) item repairs IAW TO 00-20-3, para 3.4 and 3.5.

4.2.8. RESERVED

4.2.9. Configuration Control. Maintain configuration control IAW GEODSS 31-series TOs and TO 00-33A-1001 para 1.5.3.2. thru 1.5.3.5.

4.2.10. Cannibalization. Cannibalization may only be used as a last resort and before taking such action, all other support avenues must be exhausted.

4.2.10.1. Cannibalization Actions. Ensure all cannibalization actions are approved through COR/Det CC and 21 SW Chief of Maintenance IAW TO 00-33A-1001 para 3.6.1.13, and documented IAW TO 00-20-2, Ch 5.

4.2.10.2. Depot Level Assets. Cannibalization of depot level assets may only be authorized by the Item Manager through the Det CC.

4.2.10.3. Depot Coordination. Coordinate with the Depot and order replacement parts within one day of approval and repair cannibalized equipment as soon as the parts are received, but not later than 24 hours after receipt.

4.2.10.4. Supply Coordination. Coordinate all cannibalization actions regarding supply issues through the Det CC, 21LRS/LGRS, and 21 OSS/MA.

4.2.11. C-E Corrosion Prevention and Control. Maintain all assigned equipment IAW TO 1-1-689, Ch 2 to minimize the effects of corrosion on C-E equipment.

4.2.12. Maintenance Safety Requirements. Practice maintenance safety procedures IAW AFI 91-203, Air Force Consolidated Occupational Safety Instruction, paragraphs 1.12, 30.4.1, and

30.4.2.3. Perform grounding, bonding, and shielding IAW TO 31-10-24.

4.2.13. Engineering Investigation (EI) and Product Quality Deficiency Reports (PQDRs). Identify materiel deficiencies and trends. Depending on deficiency type, develop an EI or PQDR and submit IAW TO 00-35D-54, Ch 3.

4.3. GEODSS Maintenance Training Plan. The Contractor shall develop and implement a maintenance training plan designed to keep C-E technicians proficient in GEODSS mission system maintenance requirements. Provide a copy of the training plan at contract start and updates as changes occur. Provide a copy of the training plan and training materials to the CORs and the Government Program Manager. See Chapter 2, para 2.1.8.2 for additional training records requirements.

CHAPTER 5

ELECTRONICS SYSTEMS MAINTENANCE (ESM)

TEST, MEASUREMENT AND DIAGNOSTIC EQUIPMENT (TMDE)

5.0. GENERAL. The contractor shall manage, schedule, and transport TMDE IAW TO 33K -1- 100-1, TO 33K-1-100-2, and TO 00-20-14, paras 3.6 through 3.8. Perform organizational level maintenance IAW TOs 33-1-27 and 33-1-32. In addition, the Contractor shall:

5.1. TMDE Coordinator. Appoint a primary and alternate TMDE coordinator and maintain and complete host-provided coordinator training. Consult the host Precision Measurement Equipment Laboratory (PMEL) for newly acquired items to determine if the items are considered TMDE and need to be scheduled into the PMEL for service. See Host Tenant Support Agreements (HTSA) listed in Section 3, para 3.3.1, for Det TMDE support locations. Maintain workload data on TMDE sent to host for calibration. See Appendix A, Report Number R3-3.2.

The government will reimburse the contractor under the CR CLIN for TMDE transportation and shipment costs.

CHAPTER 6

SUPPLY

6.0. GENERAL. The Contractor shall direct, manage, control, acquire, issue, and safeguard Government-owned and Government-furnished supplies and equipment to assure continuous system operation. The Contractor shall:

6.1. SUPPLY SUPPORT. Provide supply support for mission items using the customer procedures in AFMAN 23-110 Vol 2, Part 13. Prepare SBSS Transaction Identification Codes (TRICs) and submit to Peterson Air Force Base (PAFB) Satelite A4 account via World Wide Web, telephone or fax. Provide a list of items that the contractor purchased outside of the Standard Base Supply System (SBSS), and were not provided through Depot level support or another Government contract, and where the acquisition value is greater than $5,000. See Appendix A, Report Number R1-1.6.

6.1.1. After-Hours Support. Provide after-hours support for Non-Mission Capable Supply/Partial Mission Capable Supply (NMCS/PMCS) conditions. Maintain workload data on after-hours support for NMCS/PMCS. See Appendix A, Report Number R3-3.2.

6.1.2. Supply Assistance. Notify the Det CC, and 21 LRS of any supply and equipment support problems that cannot be resolved at the unit level, within 24 hours of receipt of unacceptable delivery date on required item.

6.2. LOCAL PURCHASE. The Contractor shall obtain appropriate AF Item Manager approval for local purchase of centrally managed weapon system parts (XD, XF, NF or XB expendables repair codes).

6.2.1. Parts and Supply Purchases. Procure all parts and supplies necessary to support the Det, which are not obtainable through SBSS, under the CR CLIN with Det CC approval.

6.2.2. Purchase Approval. Obtain CO approval for any item over $5,000.

6.3. HAZARDOUS MATERIAL (HAZMAT). Manage the receipt, storage, inspection and distribution of HAZMAT. Maintain Material Safety Data Sheets (MSDSs) and a list of all HAZMAT used on the Det, including annual use rates and final disposition (if not entirely consumed in process). For Det 3, provide MSDSs to Host Installation for items due in.

CHAPTER 7

FUELS MANAGEMENT

7.0. VEHICLE FUEL. The Contractor shall:

7.1. Det 1 and Det 3. Obtain vehicle fuels from a commercial source on a non-reimbursable basis.

7.2. Det 2. Identify fuel requirements and obtain vehicle fuel from the Host Installation. Obtain a “T-DoDAAC” from the Defense Energy Support Center (DESC) at www.desc.dla.mil/ that allows contractor-provided vehicles to refuel on site at the contractor’s expense.

7.3. Diesel Generators. See Section 3, Government-Furnished Equipment, Property, Information and Services reimbursable supplies and materials.

http://www.desc.dla.mil/

CHAPTER 8

COMMUNICATIONS OPERATIONS & MAINTENANCE (O&M)

8.0. GENERAL. The Contractor shall comply with administrative communication policies and procedures, provide desktop support, enforce information assurance (IA) policies, and assist Unclassified but Sensitive Internet Protocol Router Network (formerly called the Non-Classified Internet Protocol Router Network), or NIPRNET, and Secret Internet Protocol Router Network (SIPRNET) Det Service Providers and Defense Information Systems Agency (DISA) with circuit troubleshooting functions as needed.

8.1. Desktop Support. Contractor Client Support Administrators (CSAs) shall perform IAT Level I requirements for NIPRNET and SIPRNET and maintain certifications IAW DoD 8570.01-M, Tables C3.T1, C3.T2 and AP3.T1. Contractor CSAs shall have a successfully completed National Agency Check with Local Agency Credit Check (NACLC) investigation IAW DoDI 8500.2, Table E3.T1. The Contractor shall:

8.1.1. Service Disruptions. Coordinate with service provider to resolve network problems.

Report problems, outages and/or deficiencies to Det CC and the 21 SW Communications and Maintenance Control Center (CMCC) within one hour on a 16/7 basis. Maintain workload data on number and frequency of network outages. See Appendix A, Report Number R3-3.2.

8.1.2. Installations and Troubleshooting. Install client equipment and software and connect peripherals, ensuring the physical security of network backbone components. Perform client workstation diagnostics and troubleshooting.

8.1.3. Desktop Configuration. Configure client level software and provide software application assistance for commonly used office automation applications. Promote user awareness concerning unauthorized or illegal use of computer hardware and software.

8.1.4. User Access. Request NIPRNET and SIPRNET user access through…