Space Fence PWS_Draft_2 Apr 20.docx

SPACE FENCE

Performance Work Statement (PWS)

Reference # FA2517-19-R-A004

DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense and U.S. DoD Contractors only; administrative/operational use; 29 Mar 20. Refer other requests for this document to 21 SW/PMD, 135 Dover St, Peterson AFB, CO 80914.

WARNING: This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, USC, Sec 2751, et. seq.) or the Export Administration Act of 1979, as amended, Title 50, USC., App. 2401, et. seq. Violations of these export laws are subject to severe criminal penalties. Dissemination of this document is controlled under DoD Directive 5230.25.

DESTRUCTION NOTICE: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

TABLE OF CONTENTS

SECTION/PWS PARAGRAPH(S)

SPACE FENCE SERVICES REQUIREMENTS

PAGE(S)

(Applicable to Det 4 Space Force Operations Center (SOC) and Sensor Site 1 3 - 8

(Applicable to Det 4 SOC and Sensor Site 1) 9 - 37

Paragraphs 2.8 – 2.8.2.

Knowledge Operations

(Applicable to Det 4 SOC Only) 38 - 39

(Applicable to Sensor Site 1 Only) 40 - 47

(Applicable to Det 4 SOC and Sensor SIte1) 49 - 50

APPENDICES

SECTION 1.0. SPACE FENCE GENERAL REQUIREMENTS

(Applicable to Det 4 Space Force Operations Center (SOC) and Sensor Site 1, including all subparagraphs)

1.1. Mission. The 21st Operations Group (21 OG), Peterson Air Force Base (AFB), Colorado, exercises responsibility for Space Fence (SF) Increment One through the 20th Space Control Squadron (SPCS) at Eglin AFB, FL. The SF radar is remotely operated at the SF Operations Center (SOC), designated as 20 SPCS Detachment (Det) 4, and the SOC is co-located at the Reagan Test Site Operations Center in Huntsville, Alabama (ROC-H). The SF radar is located at the U.S. Army Garrison -- Kwajalein Atoll (USAG-KA) in the Republic of the Marshall Islands in the Western Pacific, and is designated as 20 SPCS Det 4 Sensor Site 1. The Det 4 SF SOC is managed by a site director who performs as the SF contracting officer representative (COR). The implementation of the SF Increment One expands and strengthens U.S. space superiority through improved Space Domain Awareness (SDA) mission capabilities.

1.2. Space Fence Scope. Provide non-personal services to manage, operate, maintain, and provide logistical and general support for the SF system. Provide all personnel, tools, materials, transportation, supervision, and other items necessary to perform SF Performance Work Statement (PWS) requirements on 24-hours-a-day, 7-days-a-week (24/7) basis. Contractor’s furnished materials and equipment shall include transportation, fuel, non-specialized tools (specialized tools provided as Government Furnished Property (GFP)), custodial supplies, office administrative supplies and equipment, and any other supplies and materials not furnished by the Government which the Contractor believes necessary to perform these requirements. In addition to providing system operation and maintenance (O&M) requirements, contracted services include exercises and testing, mission systems maintenance management, logistics management, communications, environmental, civil engineering, occupational health, security, knowledge operations, and support of system upgrades and modifications, to include acceptance testing and organizational level maintenance while in acceptance testing and after acceptance, in accordance with (IAW) SF PWS requirements. Interface with Det 4 SOC and Sensor Site 1 Hosts IAW requirements specified in the PWS.

1.3. Site Changes. Support additional sites and relocations, as needed during the performance of this contract. There is potential for SF Sensor Site 2, located in the southern hemisphere, to be added to this PWS during the life of this contract. Det 4 may be potentially relocated to 20 SPCS at Eglin AFB during life of this contract. The anticipated type of work is covered within this PWS and support for additional sites and relocations will be negotiated separately after contract award, when and if, the need arises.

1.4. Active Cyber Defense. The Air Force (AF) is moving towards active United States (US) cyber defense capabilities and implementation. The type of work required has not been determined at this time, but if the work is added to the contract, it will be separately negotiated after contract award.

1.5. PWS Organization. PWS requirements have been organized in a manner to facilitate clarity and location of performance. The grouping of requirements is not intended to imply a preferred organizational structure to meet requirements. Requirements are included in the body of the PWS and all appendices and must be adhered to in total. The contractor is expected to understand the interrelationship between requirements and to organize and perform accordingly.

1.5.1. PWS Standards and References. A Standard (STD) is a PWS requirement, for which compliance is mandatory. Publications listed as reference are included for informational purposes only for background and context. Standards may include an entire directive publication, or may only include titles of chapters or sections, or applicable paragraphs within the directive publication. When not otherwise specified, apply industry standards and commercial best practices and comply with local, state and federal statutes in performance of PWS requirements.

1.5.2. Acceptable Quality Levels (AQLs). Certain standards are identified as AQLs and will be assessed on a scheduled basis by the Government. Report contractor self-assessment of AQLs and other PWS requirements in the Site Quality Status Report (QSR) Deliverable: Appendix A, D1.1.5, Site QSR

1.5.3. Publication Updates. Review product announcements and the Product Index on the e-Publishing web site to ensure publications are current. Comply with the current version of all publications cited as a standard. Review all publications listed in the PWS and notify the Contracting Officer (CO) of any changes in writing within 30 days including any cost impacts, if applicable. Cost impacts will be negotiated in accordance with DFARS REA Clause 252.243-7002 Requests for Equitable Adjustment. If the CO is not notified in writing within 30 days, perform IAW publication changes at no increase to contract price.

1.6. Contractor Performance Assessment Report (CPAR). The contractor will receive an annual CPAR reflecting performance each year of contract performance.

1.7. Site Operations. Contractor personnel may be removed from the site, when the presence of such employee endangers life, property, or security, or where such employee violates reasonable and necessary regulations or lawful orders. Categories of violations or misconduct, which may cause employees to be removed from the installation/site include, but are not limited to:

· Security violations

· Negligence, willful damage to, or destruction of property

· Injuries inflicted upon other personnel

· Alcohol or drug abuse

· Engagement in unauthorized private business transactions

1.8. Withdrawal of Privileges. Contractor employee abuse(s) of installation/site privileges may, upon investigation of facts and circumstances of any incident, be withdrawn by the 20 SPCS Commander (20 SPCS/CC) or the Host Commander on a permanent or temporary basis.

1.9 Individual Job Orders (IJOs). This paragraph outlines the Government’s requirement for work which is not specifically identified in the PWS, but which is still within the general scope of this contract. The Government anticipates using Firm Fixed Price (FFP) or Cost Reimbursable IJOs, to be determined by the CO on a case-by-case basis, depending on the nature of the work. Develop initial technical and cost proposals for Government review and approval at the request of the CO. Perform planning, development, and distribution of plans and specifications, installation instructions, bills of materials, and inspections to complete the job at the work location. Provide all necessary management for IJOs to include technical management, logistics support and services, administrative support and services, engineering, drafting, and similar requirements as they occur. The CO will negotiate IJOs prior to any action occurring. Work shall not commence before a bi-lateral modification is negotiated and signed.

1.10. Contractor Documentation of Contract Performance. Make all information and documentation generated in performance of PWS requirements available to the Government upon request in editable electronic format. Contractor-generated format is acceptable, unless otherwise noted in the PWS.

1.11. Workload Data. Provide a Deliverable (D1.1.1, Workload Data) that captures performance workload data. Examples include numbers of actions and types of actions performed, or level of effort required in performance of contract requirements. Deliverable D1.1.1, will be noted for various paragraphs throughout the PWS that require the Contractor to collect, maintain, and submit performance workload data to the Government.

Deliverable: Appendix A, D1.1.1, Workload Data

1.12. Incident Reporting. Notify the COR, Government 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.13. 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, continue all PWS requirements. 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 continuous basis as identified by the COR and directed by the CO. Make written notification to the COR, the Government PM and CO of any cost impact resulting from declared crises and states of emergencies within 30 days of CO direction to continue work.

1.14. Contract Contingency Planning. Develop a contingency plan for continued operations and return of systems to operational status in the event of a declared crisis, catastrophic and non-catastrophic events, and work stoppages for each site. All site personnel shall be made aware of the Contractor’s contingency plan.

Deliverable: Appendix A, D1.1.2, Contingency Plan

1.15. Third-Party Support. Provide technical information and logistical support for other contractors, subcontractors, or Government agencies in support of upgrades, projects and other efforts impacting PWS requirements and site operations. It is permissible for the contractor to separately contract with third-parties under the following conditions:

(a) the services are performed on a non-interference basis with the contractual services performed under this contract,

(b) no Government property provided under this contract is used in performance of third-party services without written approval of the CO, and

(c) the Government PM and CO are informed of third-party contracts prior to final agreement.

(d) subject to Host support requirements

1.16. Uncleared Personnel Escort. Escort uncleared personnel as requested by the COR. Provide escort support, except in circumstances where the support will cause mission degradation. Notify the COR and CO if requested support is in excess of seven calendar days per project, either consecutive or intermittent.

Deliverable: Appendix A, D1.1.1, Workload Data; project name, purpose and dates capturing the nature and duration that escort support was provided

1.17. SF Operating Instructions (SF OIs). Create new, update and maintain SF OIs where other manuals and directives are not available or do not provide sufficient instructions. Use the Technical Order (TO) change process (AFTO 22) for recommended changes to TOs.

Deliverable: Appendix A, D1.1.3, SF OIs

1.18. Technical Order (TO) Distribution and Control. Appoint a Technical Order Distribution Office (TODO) Point of Contact (POC) and establish and maintain a TO library using the current version of Enhanced Technical Information Management System (ETIMS) to order and distribute publications.

Performance Standard:

a) STD: IAW TO-00-5-1

1.19. Quality Program. Develop, implement, and maintain a Quality Program ensuring performance meets or exceeds all requirements in the PWS.

1.19.1. Quality Program Plan (QPP). Implement the Quality Program IAW a QPP providing insight into the following quality processes: internal audits; procedures and oversight; identification of deficiencies/ nonconformances, actions taken to correct deficiency(ies) and nonconformance(s), root cause analysis, and actions taken to prevent reoccurrence; and a methodology for ensuring all PWS requirements are met, such as a checklist of PWS requirements/paragraphs.

Deliverable: Appendix A, D1.1.4, QPP

1.19.2. Site Quality Status Report (QSR). Generate and distribute a QSR.

Deliverable: Appendix A, D1.1.5, QSR

1.20. Technical Meetings. Participate in sustainment and performance working group meetings, Multi-Functional Team (MFT) meetings, the weekly Maintenance Production Status Teleconference (provide briefing slides identified below) and all invited ad hoc technical meetings and conferences that affect the Contractor’s execution of the operations, maintenance, and repair functions of this contract.

Deliverables:

a) Appendix A, D1.1.1, Workload Data; number of meetings attended and amount of time spent at meetings

b) Appendix A, D1.1.6, Maintenance Production Status Briefing (for weekly teleconference)

1.21. Familiarization Briefings and Tours. Conduct site briefings, such as technical orientation/familiarization briefings and tours when requested by the COR. Include as part of all briefings any areas that pose a threat to human safety within the installation/site.

Deliverable: Appendix A, D1.1.1, Workload Data; number of briefings and tours provided

1.22. Inspections and Exercise Support. Participate in exercises and debriefings as requested by the COR or 20 SPCS/CC. Support inspection teams, as identified by the COR. Immediately limit or terminate support if personnel are needed to meet real-world operational requirements.

Deliverable: Appendix A, D1.1.1, Workload Data; number of inspections and exercises participated in or supported

1.22.1. Trusted Agent (TA). Designate a TA at the request of the COR or 20 SPCS/CC before the start of an exercise. Complete TA training upon designation. The TA shall assist the COR in developing and implementing exercises.

1.22.2. Exercise Reports. Provide findings to the COR for the completion of the after action report by the time designated.

1.22.3. Crisis Response. Participate in the unit crisis response team during HHQs inspections or local exercises as determined by the COR.

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

Deliverable: Appendix A, D1.1.7, Resource Utilization Report

1.24. Training. Manage training to ensure technical competency to fully execute all PWS requirements. Maintain individual training records for all personnel.Training records shall reflect all training received on- and off-site.

1.24.1. Government-Furnished Training. The Government will furnish and fund the training identified in Appendix F. Submit requests for Government-furnished training in writing to the COR, Government PM and CO for approval, funding, and contractual action. Disseminate knowledge gained by contractor personnel at Government training courses and conferences to other contractor personnel requiring the same information. If turnover of personnel creates the need for another Government-furnished training quota within 1 year of completion of the last training, the contractor is solely responsible for all costs of obtaining training (including course, travel and per diem costs) and any failure in meeting contract requirements.

1.24.2. Knowledge Capture/Management (KCM) Plan. Create, implement, and maintain a KCM Plan for a sustainable workforce qualified in meeting PWS requirements for the contract period of performance. Standardize the KCM Plan across the SF sites.

Deliverable: Appendix A, D1.1.8, KCM Plan

1.24.3. Contractor Personnel Qualifications, Training, Certification, and Licensing. Staff positions with personnel that are qualified, trained, certified, and licensed to perform PWS requirements. Provide initial and refresher training as required to meet PWS requirements.

1.25. Contractor Common Access Cards (CACs). A CAC is required for contractor personnel requiring on-going access to a military installation, or who require Department of Defense (DoD) unclassified network access in performance of PWS requirements. A favorable background investigation is required for Non-Secure Internet Protocol Router Network (NIPRNet) access. Coordinate with the appointed Trusted Agent Security Manager (TASM) to acquire a CAC.

1.26. SIPRNet Tokens. Coordinate with the appointed Trusted Agent Security Manager (TASM) and host to acquire Secure Internet Protocol Router Network (SIPRNet) tokens required for contractor personnel access to the DoD classified network for PWS performance.

1.27. Hand Tools and Equipment. The Government will retain ownership of specialized tools and equipment identified on the contract Government Furnished Property (GFP) listing.

1.28. Program Management. Integrate all activities needed to execute the Space Fence requirements ensuring timeliness, completeness, and quality of deliverables; identification and resolution of issues; corrective action plans; proposal submittals; scheduling and proper allocation of resources to minimize impacts of personnel turnover, issues with shift coverage, gaps in qualified personnel and requirements. Immediately report problems affecting functional area accomplishment or Contractor performance to the COR, Government PM, and CO.

1.28.1. Key Points of Contact. Provide the names, home, cell, and duty phone numbers of key points of contact at each SF location to the COR, Government PM, and CO in writing.

Deliverable: Appendix A, D1.1.9, Key Points of Contact

1.28.2. Organization Chart. Provide an organizational and staffing chart, reflecting all filled positions, to the Government for each site.

Deliverable: Appendix A, D1.1.10, Organizational Chart

1.28.3. Safety Training and Meetings. Attend host safety training and provide safety information to all Contractor personnel. Attend host safety meetings and participate in safety committees IAW support agreements and local regulations, directives and procedures.

1.28.4. Site Personnel Evacuation. Evacuate a site whenever directed by the COR, Host Unit, or at Contractor discretion if COR is unavailable and circumstances warrant. Notify the COR, Govt PM and CO once safely off-site.

1.28.5. COR Briefings. Conduct a weekly briefing to the COR including status of operations and maintenance, any inspections, exercises, visits, training, funding status, and other pertinent information, and as requested by the COR.

1.28.6. Travel Orders for Contractor TDY. Coordinate contractor travel through the COR. Submit travel orders/letter of identification (LOI) for non-local travel to the CO for approval. Include sufficient information for the CO to determine whether the TDY is required to fulfill PWS requirements and with all transportation and per diem costs clearly identified. If traveling overseas, indicate whether the US Government rate tariff applies. Compliance with DoD Foreign Clearance Guide for clearance, passport, and immunization requirements are the responsibility of the Contractor. The Government shall reimburse the Contractor for CO-approved TDY/non-local travel as determined necessary for performance of the contract. Cost for delays en route for local, staffing-related, or personal travel shall not be reimbursed by the Government. Note: The Cost Reimbursable (CR) CLIN will be used for official TDY travel only, not local travel, staffing-related, or personal travel.

Performance Standard:

a) IAW Defense Travel Regulation (DTR)

1.28.6. Contractor Manpower Reporting. Report all contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract using the following web address www.sam.gov.

Deliverable: Appendix A, D1.1.11, Contractor Manpower Reporting

SECTION 2.0. MISSION OPERATIONS AND SUPPORT REQUIREMENTS

(Applicable to Det 4 SOC and Sensor Site 1, including all subparagraphs)

2.1. Sensor Operations and Support. Provide radar sensor operations, technical services, and operations support to meet SDA mission requirements.

2.1.1. Sensor Operations. From the SOC at Det 4, the contractor shall accomplish continued operational activity support including radar monitoring, controlling, tasking, and data processing IAW Combined Special Operations Center (CSpOC), 18 SPCS, and National Space Defense Center (NSDC) taskings. Additionally, the SOC operators shall develop and update tactics, techniques, and procedures (TTPs), standard operating procedures (SOPs), and provide updates to TOs within their standard on-duty schedule.

2.1.1.1. Sensor Site 1 Dual-Role Operator/Maintainers. The contractor shall provide operator/maintainers at the radar site capable of performing limited operations as necessary. Sensor Site 1 shall be operated independently providing data to the Command and Control (C2) Centers using Net-Centric Services provided via the DoD Information Network (DoDIN) or controlled by on-site personnel. Sensor Site 1 shall accomplish limited operational mission tasks in the event of contingencies or when the SOC becomes unavailable. Limited mission taskings include, but are not limited to, responding to C2 tasking (voice or message), Positive/Negative reporting for high interest objects, initiation/management of Black Box recording, and operational reporting (Operations Capability (OPSCAP), Operations Reporting (OPREP), and Situational Reporting (SITREP)).

2.1.2. Taskings and Reporting. Accomplish all higher headquarters (HHQ) taskings and reporting requirements.

2.1.2.1. Metric Taskings. Perform routine and special metric taskings as directed by 18 SPCS.

Performance Standards:

a) AQL (Performance Objective# 1 (PO# 1): 100% of all Category (Cat) I taskings

b) STD: IAW SSOPs OI 534-9 (S) Ground-Based Metric Tasking Suffixes table

c) STD: IAW JFSCC and NSDC taskings Deliverable: Appendix A, D1.1.1, Workload Data; number of metric taskings

2.1.2.2. SOI Taskings. Complete 100% of SOI-tasked objects each month within system limitations.

Performance Standards:

a) AQL (PO# 2): 100% of SOI-tasked objects each month

b) STD: IAW SSOPs OI 534-9 (S) Narrowband SOI Tasking Suffixes table Reference: Space Fence System Concept (for system limitations) Deliverable: Appendix A, D1.1.1, Workload Data; number, frequency, and duration of SOI taskings

2.1.2.3. Manually Tasked Objects. Enter taskings manually if not received through normal channels. Perform manual scheduling, special sensor settings, and other special techniques to include uncorrelated target (UCT) processing, hand-offs, break-up processing, maneuver, proximity operations events, and launch events.

Performance Standard:

a) STD: IAW SSOPs OI 534-9 (S) Sensor Tasking Update (SU67)

2.1.3. 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 mission subsystem.

2.1.4. Health and Status Monitoring. Monitor and direct corrective maintenance for system calibrations and system capability. Provide operational reporting, as required.

Performance Standard:

a) STD: IAW SSOPs OI 534-9 (S)

2.1.5. Sensor Contractor-Controlled Availability (Acc ). Ensure availability of radar sensors to meet mission operational requirements. Provide the monthly calculation for Acc in the QSR.

Performance Standards:

a) AQL (PO# 3): Maintain an overall sensor Acc each calendar month of not less than 99.7%

b) STD: IAW SSOPs OI 534-9 (S)

2.1.6. Operations Training Plan. Develop and maintain a Master Task List. Develop and implement an Operations Training Plan that certifies proficient operators and continues to advance operator expertise through advanced training in the Mission System and the contributions to the overall SDA mission. Standardize training program for SOC operators and Sensor Site 1 operator/maintainers, which shall be qualified, trained, and knowledgeable in both maintenance and operations.

Deliverable: Appendix A, D2.1.1, Operations Training Plan

2.1.6.1. Operations Training Classes and Curriculum. Develop training curriculum and provide training to all operator personnel (to include all Sensor Site 1 operator/maintainers). Provide limited Combat Mission Ready training to all Sensor Site 1 operator/maintainer personnel for performance of limited operational mission tasks during contingencies and when the SOC is not available. Provide training material to operators and make training available to other Air Force personnel, such as test personnel, upon request and COR approval. Support additional training developed as part of Det 4 standup and operations (e.g., emergency procedures, ancillary training, etc.) provided by the Government, within operations personnel standard on-duty schedule. Support 20 SPCS advanced training activities, as requested.

Reference: AFSPCGM 2018-13-01 Deliverable: Appendix A, D2.1.2, Operations Training curriculum

2.1.6.2. Initial and Annual Certification. Conduct and document training to ensure proficiency in all required functions before operating the Mission System. Maintain a comprehensive list of all monthly sensor operations training tasks. 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. Each Sensor Site 1 operator/maintainer shall perform at least one real-world proficiency shift per month. Documented completion of recurring training as outlined above and within the Contractor’s Operations Training Plan shall constitute annual re-certification.

Performance Standard:

a) STD: IAW AFSPCGM 2018-13-01

2.1.6.3. Continuation Training. Conduct monthly continuation training using task and scenario based approaches, addressing mission performance requirements. Monthly continuation training shall cover all individual tasks within a one-year timeframe. SOC operations personnel and Sensor Site 1 operator/maintainer personnel designated to support operations for tasks required (i.e., Operations Supervisor position during Contingency Operations), will receive mission operations training similar to Mission Ready (MR) Mission Qualification Training (MQT) required for Space Operations Command (SPOC) military and DoD civilian space operators, upon arrival at the unit. This initial mission operations training is a prerequisite to being certified Mission Capable (MC) for SOC and Contingency Operations.

2.1.6.4. Individual Training Records. Maintain individual training records for all operators. Training records shall reflect all training received on- and off-site.

2.1.7. Equipment Familiarization Training. Provide on-site equipment familiarization training for AF personnel upon request and with COR approval.

2.1.8. Collaboration. Support system life-cycle activities such as program management reviews, design reviews, data collection, tests, physical and functional configurations audits.

2.1.9. System Performance. Monitor system logs, security logs, security configuration, and performance utilities to assure system performance to identify and correct imminent system failures.

2.1.9.1. System Malfunctions or Anomalies. Notify the COR of all system malfunctions or anomalies.

Performance Standard:

a) STD: SF OPSCAP Determination Matrix

2.1.9.2. Deficiency Reporting (DR). For qualifying events, generate a DR within 30 days of an anomaly or outage. Maintain supporting data including references to associated Problem Reports (PRs), computer printouts, and system data logs.

Performance Standard:

a) STD: IAW TO 00-35D-54, Chapter 3 – Deficiency Identification and Reporting

2.1.9.3. System Modifications or Enhancements. Generate a DR, AF Form 1067, or 21st Space Wing (SW) Form 1 for system modifications or enhancements.

Performance Standards:

a) STD: IAW TO 00-35D-54, Chapter 3 – Deficiency Identification and Reporting

b) STD: IAW AFI 63-101/20-101, Attachment 2 – Modication Management and Modification Proposal Process and AF Form 1067 Descriptions

2.1.9.4. System Requirements Validation Board (SRVB). Perform as coordinator and recorder for the SF SRVB, providing technical expertise, as required.

Performance Standards:

a) STD: IAW TO 00-35D-54

b) STD: IAW 21 SWI 21-131 - SRVB responsibilities

2.1.9.5. Materiel Improvement Project Review Board (MIPRB). Participate in MIPRB meetings and discussions and provide feedback as requested.

Performance Standards:

a) STD: IAW TO 00-35D-54

2.1.9.6. System Changes. Advise the SRVB in identifying and prioritizing new requirements for, and changes to, the operational system. Submit change requests to the Wing Requirements Validation Board (WRVB) after the COR approval.

Performance Standard:

a) STD: IAW 21st Space Wing Instruction (21 SWI) 21-131, Chapter 2, Paragraph 2.6 – The SRVB provides the first level of review in the change approval process section and attachment

2.1.10. Mission System Risk Management Framework (RMF) for DoD Information Technology (IT). Maintain situational awareness and initiate actions to implement or restore cybersecurity posture as directed by the Mission System Information System Security Manager (ISSM) at Space and Missile Center (SMC). Provide information to support RMF authorization, information system continuous monitoring activities, and maintain system artifacts. Coordinate any changes impacting the Mission System RMF package through the COR and send to SMC for approval. Conduct annual security reviews of all cybersecurity controls and test selected cybersecurity controls as directed by SMC. Provide artifacts identified in Appendix G to the requesting Mission System ISSM for information assurance (IA) control validation and inclusion into the AF Assessment and Authorization (A&A) package, using Mission System ISSM provided guidance.

Performance Standards:

a) STD: IAW STD: IAW AFI 17-101 - Information System Security Officer (ISSO)

b) STD: IAW Department of Defense Instruction (DoDI) 8500.01

c) STD: IAW National Institute of Standards and Technology (NIST) Special Publication (SP) 800-53

d) STD: IAW 21 SWI 21-131 - Cybersecurity Reference: DoDI 8510.01- RMF for DoD IT Deliverable: Appendix A, D2.1.3, RMF Artifacts

2.1.11. System Analysis and Performance. Monitor and analyze system performance. Analyze critical system files, computer and radar logs ensuring the logs are maintained and archived. Analyze daily UCT rates to identify abnormal performance. Review and analyze system calibration, operability assessment test results, and other indicators of system performance utilizing the system calibration metrics on the Space C2 Agency website, https://www.space-track.org. Analyze occurrences of system outages or operational degradation such as the following: indications of radar system degradation; uncommon computer halts or hangs; CAT 1 satellite misses; electro-magnetic interference (EMI); and other abnormal data, performance, and occurrences that may lead to a system failure. Provide analyses to support site operations investigations to the COR.

Performance Standard:

a) STD: Completion of investigation of occurrences of system outages or operational degradation within five calendar days of the problem or by request of the COR References: SI 538-01(S), SSOps OI 534-9(S), and SI 534-16(S) Deliverables:

a) Appendix A, D2.1.4, System Analysis Results

2.1.11.1. Document and Report Analysis and Findings. Provide Problem Reports (PRs) to support site operations investigations by the COR. Submit a DR for unusual and unique anomalies, or outages. Generate an AF Form 1067 or Standard Change Form (SCF) prior to installing new software constants for the subarray test and element test installations. Generate an SCF for system or software modifications for corrective or preventive action as a result of analyses or any other proposed system/software modifications. Evaluate and provide written technical analysis on any system modification/upgrade proposal or recommendation. Maintain references to any associated PR, DR and SCF and supporting data.

Performance Standards:

a) STD: IAW TO 00-35D-54

b) STD: IAW 21 SW Instruction (21 SWI) 21-131 - System Modification and Deficiency Processing

c) STD: Submit DR within 30 days of the anomaly or outage

d) STD: Submit SCF within 30 days of the anomaly or outage; prior to installing new software constants; and for system or software modifications Deliverables:

a) Appendix A, D2.1.5, Problem Report (PR)

b) Appendix A, D2.1.6, Deficiency Report (DR)

c) Appendix A, D2.1.7, AF Forms 1067 or Standard Change Form (SCF)

d) Appendix A, D2.1.8, Evaluation and Technical Analysis

2.1.12. Emergency Actions. Perform emergency actions as requested by the 20 SPCS Commander or their designated representative.

Performance Standard:

a) STD: Respond immediately and report on site as determined by COR

2.1.13. Events or Incidents Reporting. Perform OPSCAP reporting to CSpOC and notify the 20 SPCS Mission Operations Center (MOC) of OPSCAP changes. Notify the 20 SPCS MOC and COR with information on events or incidents that may require OPREP or Commander’s Critical Information Request (CCIR) Reporting. Provide a daily report of operational activities as specified by HHQ. Maintain checklists and implement Information Condition (INFOCON) and Force Protection (FP) Condition (FPCON) measures for both exercise and real-world scenarios.

Performance Standards:

a) STD: IAW AFI 10-206

b) STD: IAW AFI 10-206 AFSPC Supplement (Sup) 1 and its required guidance memorandums

c) STD: IAW SSOPs OI 534-9 (S)

d) STD: IAW HHQ policy letters

e) STD: IAW Strategic Instruction (SI) 527-1

2.1.14. Chatroom Communications. Establish the necessary chat-type accounts via SIPRNet and NIPRNet. Ensure operators are actively logged into the HHQ-designated account and utilizing “chatrooms” or similar collaboration applications. During periods of exercise and/or contingency, continuously monitor or check collaboration chatrooms via the SIPRNet/NIPRNet and make any postings needed in response to questions or direction from HHQ.

2.1.15. Depot/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.

2.1.15.1. Installation, Development, Test and Evaluate (DT&E) and Software and Operational Test and Evaluation (OT&E) Support. Provide organizational level support for installation and evaluation of all software and hardware modifications to include planning, technical, and administrative support. Provide organizational level maintenance in support of installation activities, perform applicable test plan actions, and notify the COR and testing/depot agencies of any system anomalies.

2.1.15.2. Installation and Checkout Evaluation (ICE) Plan. Develop and submit ICE plans for newly installed hardware, firmware, or software through the COR and 20 SPCS/MA. Execute approved installation and checkout plans with Government oversight for final approval and acceptance by the Government.

Performance Standards:

a) STD: IAW 21 SWI 10-202

b) STD: IAW 21 SWI 21-131 - Unit (organizational) maintenance personnel, Installation Checkout and Evaluation (ICE), 21 OG units and Restricted Operational Use (ITW/AA and Surveillance) Deliverable: Appendix A, D2.1.9, Installation and Checkout Evaluation (ICE) Plan

2.1.15.3. Visiting Team Preparation. Support all teams visiting SF. Provide logistics support for visiting teams and coordinate receipt and storage of project materials and equipment.

Deliverable: Appendix A, D1.1.1, Workload Data; number of visiting contractor teams supported

2.2. Mission System Maintenance Management. Ensure Mission 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 Mission System 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.

2.2.1. Scope of Maintenance. Perform all authorized organizational level maintenance. Site maintenance level authorized for repair is determined by Source, Maintenance, and Recoverability (SMR) Codes and Expendability, Recoverability, Reparability Codes (ERRC) assigned to stock listed items.

Performance Standards:

a) STD: IAW TO 31-10-7

b) STD: IAW TO 00-33A-1001

c) STD: IAW SF TOs (TBD); utilize draft until approved

2.2.1.1. Depot-Level Maintenance. Request depot-level maintenance when the maintenance required exceeds organizational-level maintenance through the COR or 20 SPCS/CC.

Deliverable: Appendix A, D1.1.1, Workload Data; number, type, and frequency of depot-level maintenance requests

2.2.1.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).

Performance Standards:

a) STD: 21 SWI 21-131 – Depot Level Maintenance (DLM)

b) STD: IAW TO 00-25-107 - Procedures for Requesting Assistance, Response Time and Required Actions

c) STD: IAW TO 00-25-108 Deliverable: Appendix A, D2.2.1, Maintenance Assistance Requests

2.2.1.3. Non-Integrated Logistics System-Supply (ILS-S) Inventory Items. Maintain sufficient non-stock listed items (outside the AF inventory) to support the Mission System.

2.2.1.4. Shop Stock. Maintain shop stock for day-to-day operations. Monitor shop stock to prevent materiel from becoming excessive or outdated. Shop stock should not normally exceed 90-days usage, or the unit of issue or unit pack, whichever is greater. Store shop stock near/adjacent to bench stock items, if practical, but do not mix them together. Clearly identify materiel as "Shop Stock" and label them with noun, national stock number or part number, unit of issue, and shelf-life, if applicable. Shop stock includes gas cylinders, random length bar stock, sheet metal, plastic, fabric, electrical wire, and similar items not normally included in bench stocks.

Performance Standards:

a) STD: IAW AFI 23-101

b) STD: 100% accountability of tools IAW TO 00-33A-1001, Unit/Work Center Tool Management

c) STD: No systems misaligned or erroneously declared serviceable/unserviceable or damaged equipment components or hardware due to unserviceable tools

2.2.1.5. Operating Stock. Store operating stock near/adjacent to bench stock items, if practical, but do not mix them together. Monitor operating stock to prevent it from becoming excessive or outdated. Retain partially used bench stock items in bench stock and not in operating stock. Identify, tag, and turn in items with no forecasted use. Clearly identify items as "Operating Stock" and label them with noun, national stock number or part number, unit of issue, and shelf-life as applicable. Operating stock includes connector dust covers, hydraulic line caps/plugs, and similar items that are normally recovered after use and re-used.

Performance Standard:

a) STD: IAW AFI 23-101

2.2.2. Equipment Status Reporting (ESR). Fulfill requirements listed in performance standards below. Report equipment status changes, as they occur. Input data into the Integrated Maintenance Data System (IMDS) ESR subsystem.

Performance Standards:

a) AQL (PO# 4): Submit IMDS entry within two hours of the equipment status change

b) STD: IAW AFI 21-103, AFSPC Sup 1, Chapter 6 and Section 6.10 - What is Reportable, Equipment Status Reporting Procedures, Downtime Codes for Communications Equipment, IMDS to Reliability and Maintainability Information System (REMIS) Status Code Conversion Cross Reference, and IMDS to REMIS Downtime to Reason Code

c) STD: IAW TO 00-33A-1001

d) STD: IAW Air Force Computer System Manuals (AFCSM) 21-560, Volume 2 (V2) (Distribution Statement: D) - Communications Equipment Status and Inventory Reporting

e) STD: IAW AFSPCI 21-108 - Equipment Status Reporting (ESR) and Maintenance Data Documentation (MDD)

2.2.2.1. ESR Changes. Implement changes to ESR provided by 21st Operations Support Squadron (OSS)/MAD within one duty-day.

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

2.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.

Performance Standards:

a) STD: IAW TO-00-20-2

b) STD: IAW Applicable –06 TOs

c) STD: Input SRD reportable data in IMDS within three days of completion References: AFSPCI 21-108 and AFCSMs 21-556 V2, 21-560 V2, 21-561 V2, 21-562 V2, 21-563 V2, 21-564 V2, 21-569 V2, and 21-571 V2 (Distribution Statement: D)

2.2.4.1. Integrated Maintenance Data System (IMDS) Data Entries. Complete IMDS training prior to use of the system. Input all MDC data on reportable equipment into the IMDS MDC subsystem. Input MDC data into IMDS for all maintenance performed on the mission system, to include maintenance performed by on-site Depot teams.

Performance Standards:

a) AQL (PO# 5): MDC data shall be entered into IMDS with 95% initial accuracy, 98% accuracy within 72 hours, and 100% accuracy within 5 days

b) STD: IAW TO-00-20-2

c) STD: IAW TO 00-33A-1001

d) STD: IAW TO 31P7-2FSY1-6WC1

e) STD: IAW AFCSM 21-556V2 (Distribution Statement: D)

f) STD: IAW AFCSM 21-560V2 (Distribution Statement: D)

g) STD: IAW AFCSM 21-561V2 (Distribution Statement: D)

h) STD: IAW AFCSM 21-562V2 (Distribution Statement: D)

i) STD: IAW AFCSM 21-563V2 (Distribution Statement: D)

j) STD: IAW AFCSM 21-564V2 (Distribution Statement: D)

k) STD: IAW AFCSM 21-569V2 (Distribution Statement: D)

l) STD: IAW AFCSM 21-571V2 (Distribution Statement: D)

2.2.4.2. IMDS Reconciliations. Set up contingency procedures to track equipment status while IMDS is unavailable. Process IMDS status changes when IMDS is restored. Maintain and update the Equipment Inventory List (EIL). Process NFS5B0 reconciliation program and review the quarterly NFS5B0 error output file for action. Reconcile all Red/Amber jobs using the Open Incident List (OIL). Implement changes provided by 21st Operations Support Squadron (OSS) to ensure accurate data submissions.

Performance Standards:

a) STD: IAW AFI 21-103, AFSPC Sup 1 - Inventory Records

b) STD: Weekly reconciliation of all Red/Amber jobs

2.2.5. Scheduled and Unscheduled Maintenance. Maintain, calibrate, and repair Mission System equipment, including upgrades and modifications. Schedule maintenance downtime and complete scheduled system downtime for maintenance between 75% and 100% of the estimate. Immediately initiate restoration actions for unscheduled maintenance.

Performance Standards:

a) STD: IAW 21 SWI 10-202

b) STD: Immediately initiate restoration actions for unscheduled maintenance

c) STD: Complete scheduled system downtime for maintenance between 75% and 100% of the estimate Reference: TO 00-33A-1001

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

Deliverable: Appendix A, D2.2.2, IMDS PMI inputs and updates

2.2.5.1.1. Locally Developed Maintenance Procedures. Submit all contractor-developed Local Work Cards (LWCs) to the COR and Government PM for submission to the 21 SW Chief of Maintenance (COM) for approval prior to use. LWCs cannot modify existing PMIs. Ensure compliance with all parent TO procedures and ensure new requirements for tools or test equipment are not introduced. Do not use locally prepared technical instructions to circumvent centrally-managed responsibilities. Do not inter-file LWCs in TO binders.

Performance Standard:

a) STD: LWCs will be updated/deleted within 60 calendar days of equipment modification/removal

b) STD: IAW TO 00-5-1 - Locally Prepared Workcards, Checklists, Job Guides, and Page Supplements;

c) STD: IAW TO 00-33A-1001 - Local Workcards

d) STD: IAW AFSPCI 21-108 Deliverable: Appendix A, D2.2.3, Local Work Cards

2.2.5.2. Maintenance Events. Document scheduled and unscheduled maintenance (both software and hardware) events for MDC Job Data Documentation (JDD) in the IMDS database for equipment with MDC reportable SRDs.

Performance Standards:

a) AQL (PO# 5): MDC data shall be entered into IMDS with 95% initial accuracy, 98% accuracy within 72 hours, and 100% accuracy within 5 days

b) STD: IAW TO-00-20-2

c) STD: IAW TO 00-33A-1001

2.2.5.3. Operational Downtimes. Operational downtime requests will be the responsibility of the Contractor. The Contractor will submit all Combat Capability Assessment Schedule (CCAS) inputs for A - Retrofit or Modification, B - Depot Maintenance Scheduled and C - Test coded line numbers. Contractor will coordinate with COR or designated representative for approval prior to submitting downtime requests in CCAS. Notify COR or designated representative via email as a minimum once the schedule request has been successfully inputted into the CCAS website.

Performance Standard:

a) STD: IAW 21 SWI 10-202

2.2.6. TO System Improvement. Submit Air Force Technical Order (AFTO) Form 22 to recommend changes. Coordinate through the COR prior to submission.

Performance Standard:

a) STD: IAW TO 00-5-1, Paragraphs 9.1.14, 9.1.15, 9.2, 9.6, and 9.7 - Mishap Investigation Directed Changes, Submitting Changes to Joint-Use TMs, Submitting Recommended Changes, Recommendation Priorities and AFTO Form 22 Procedures Deliverable: Appendix A, D2.2.4, Technical Order (TO) System Improvement

2.2.7. 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.

Performance Standard:

a) STD: IAW TO 00-5-15 – Air Force Time Compliance Technical Order Process

2.2.8. Historical Records. Maintain and document AFTO Form 95, Historical Record, or Historical Screen in IMDS, to reflect current operational configuration. Notify equipment custodians when TCTO actions result in equipment stock number changes and initiate AFTO Form 22, as applicable. Identify preplanned items, time change items, and TCTOs. Complete required actions when scheduled.

Performance Standards:

a) STD: IAW TO 00-20-1 - Maintenance Historical Documentation

b) STD: IAW IMDS Manual AFCSM 21-568 V2 (Distribution Statement: D)

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

Performance Standards:

a) STD: Repair SMR items IAW the specific SMR code in TO 00-25-195

b) STD: IAW TO 00-20-3 - Repair Cycle Processing of XB Coded Items

c) STD: IAW TO 00-20-2 - Rules for Documentation and Convenience of Making Repair Table

d) STD: IAW TO 00-25-234 - Economical Repair, and Replacement and Repair of Parts Deliverable: Appendix A, D2.2.6, SMR Code Change Requests

2.2.9.1. Non-SMR Coded Items. Repair items with no SMR code (XB3 items) assigned when cost effective or necessitated by mission requirements.

Performance Standard:

a) STD: IAW TO 00-20-2 and Table 3-3 – Convenience…