Initial Award PWS NISSC II OM and S PWS 2 JUL 20.docx

PERFORMANCE WORK STATEMENT (PWS)

For North American Aerospace Defense Command (NORAD) Cheyenne Mountain Complex (NCMC) – Integrated Tactical Warning/Attack Assessment (NCMC-ITW/AA) and Space Support Contract II (NISSC II)

Operations, Maintenance, and Sustainment (OM&S) Task Order

Revision 2, 09 Jun 2020 Air Force Materiel Command Air Force Life Cycle Management Center Digital Directorate Systems Division (AFLCMC/HBQ)

NISSC II OM&S Task Order

FA8723-20-F-9001 (OASIS GS00Q14OADU120)

Distribution authorized to the Department of Defense and U.S. DoD contractors only (Administrative or Operational Use) (09 Jun 2020). Other requests shall be referred to (AFLCMC/HBQN/Z).

FOR OFFICIAL USE ONLY

Page Intentionally Blank

NISSC II OM&S TO, PWS

NISSC II OM&S TO, PWS

PWS for OM&S Task Order

FA8723-20-F-9001 (OASIS GS00Q14OADU120)

REVISION HISTORY

Table of Contents

Figures and Tables

Page Intentionally Blank

PWS for OM&S Task Order

PWS for OM&S Task Order

FA8723-20-F-9001 (OASIS GS00Q14OADU120)

xii Introduction The NISSC II Operations, Maintenance, and Sustainment (OM&S) Task Order (TO) documents requirements for OM&S of the baseline NISSC II covered systems. The NISSC II covered systems provide classified communications and processing for Command and Control (C2) capability in organizational work centers at Cheyenne Mountain Air Force Station (CMAFS), Peterson Air Force Base (PAFB), Colorado; Offutt AFB (OAFB), Nebraska; Vandenberg AFB (VAFB), California; and other sites, world-wide sites. The NISSC II OM&S TO also documents requirements for operations and maintenance support for the CMAFS Information Systems Infrastructure.

The United States Space Force (USSF), PAFB, CO, in coordination with North American Aerospace Defense Command (NORAD), United States Northern Command (USNORTHCOM), United State Space Command (USSPACECOM), and United States Strategic Command (USSTRATCOM), determine and approve requirements for the systems. CDRUSSTRATCOM has delegated day-to-day system integrity management responsibility of the Integrated Tactical Warning/Attack Assessment (ITW/AA) mission to USSTRATCOM/J65, Systems Certification Division.

(Note: USSF was formerly known as Headquarters Air Force Space Command (HQ AFSPC). AFSPC was redesignated to the USSF on December 20, 2019. Some of the NISSC II covered systems baseline and reference documentation has not yet been updated.)

Life cycle management of the NISSC II covered systems is the responsibility of the Digital Directorate, Air Force Life Cycle Management Center (AFLCMC), Hanscom AFB, MA. Government program management of the OM&S TO will be performed by NCMC-ITW/AA and Legacy Space Government Program Offices (GPOs) offices, Strategic Warning and Surveillance Systems Division, PAFB, CO.

NISSC II Covered Systems NISSC II covered systems are identified in drawing DM-00827, Fit-for-Purpose View Level 0 (FFP-0) and further described in DM-03594, Enterprise Technical Volume II. The systems consist of commercial-off-the-shelf (COTS), Government-Off-The-Shelf (GOTS), Free and Open Source Software (FOSS), and specialized hardware and software. Major components to the NISSC II covered systems are application servers, database servers, workstations, communication equipment, and virtual machines. Mission system functionality is provided by specialized software applications.

ITW/AA C2 Systems The ITW/AA weapon system is a worldwide warning and surveillance system for North America. It consists of airborne, land-based and space-based systems which sense and report threat activities in air and space.

ITW/AA C2 Systems include the Combatant Commanders Integrated Command and Control System (CCIC2S), Real-time Algorithm Processing Threats and Origin Release (RAPTOR), and Missile Warning Database.

PWS for OM&S Task Order

FA8723-20-F-9001 (OASIS GS00Q14OADU120)

FOR OFFICIAL USE ONLY

Combatant Commanders Integrated Command and Control System (CCIC2S) CCIC2S is used by NORAD, USNORTHCOM, and USSTRATCOM in support of the ITW/AA mission. Additionally, USSTRATCOM and Fourteenth Air Force (14 AF) use the system to receive and transmit space mission data in support of the space surveillance, defense, and intelligence missions.

CCIC2S Enterprise systems receive and correlate data from terrestrial and space-based sensors to provide ITW/AA authorities with accurate, timely, unambiguous and continuous warning and attack assessment of air, missile, and space threats. CCIC2S Enterprise provides data communications between external sensors and end users; mission processing for air and missile warning missions; and system operations functions. Processed reports are sent to the consolidated NORAD and USNORTHCOM Command Center (N2C2) where the reports are integrated into air, land and space displays for the on-duty command director who determines whether North America is, or is not, under strategic attack. The primary NCMC-ITW/AA Correlation Center at CMAFS, CO and Alternate Missile Warning Center (AMWC) at Offutt AFB, NE provide primary and contingency operations for the Missile Warning mission. Threat assessment reports are provided to the National Military Command Center (NMCC), Alternate National Military Command Center (ANMCC) as well as numerous Situational Awareness (SA) and Forward Users (FU) sites.

RAPTOR System The Real-time Algorithm Processing Threats and Origin Release (RAPTOR) System provides a MW application programming interface (API) and dynamically linked/shared object library, which provides MW algorithms and Government Furnished Information (GFI) data in a single code baseline. The single baseline minimizes the risk of applications implementing MW algorithms from getting different answers given the same inputs. The library also reduces the overall maintenance cost when a modification is made to an algorithm.

Note: NISSC Delivery Order Software Release 18.2 includes scope to implement RAPTOR component within Missile Analysis and Reporting System (MARS) and Processing Display System – Migration (PDS-M). When this is completed, RAPTOR will no longer be identified as a separate ITW/AA system.

Missile Warning Database The ITW/AA Missile Warning Database provides operational database files that define threat characteristics.

Legacy Space C2 Legacy Space C2 consist of systems and applications that maintain the space-related accuracy requirements to perform Space Situational Awareness (SSA) processing and analysis. The mission of Legacy Space C2 is to provide centralized C2, Earth Satellite Vehicle (ESV) surveillance, Space Object Identification (SOI), SSA, and operations support for the space mission in support of the Joint Force Space Component Command (JFSCC) and all Combatant Commands (CCMs). Using situational information obtained from various sources within and outside the Department of Defense (DoD), the Consolidated Space Operations Center (CSpOC) provides both general direction and specific tailored tasking to its assigned space forces. In turn, these forces provide surveillance data on Resident Space Objects (RSO) and any related mission status to the CSpOC. The CSpOC uses this data to generate effects and other information related to the C2 of space-related assets. (Note: CSpOC was formerly known as the Joint Space Operations Center (JSpOC). JSpOC transitioned to the CSpOC on July 18, 2018. Some of the NISSC II covered systems baseline and reference documentation has not yet been updated.)

Legacy Space C2 systems in scope of NISSC II OM&S are Consolidated Space Operations Wide Area Network (CSO WAN), Space Data Server (SDS), CMAFS Message Processor (CMP), Space Defense Operations Center (SPADOC), Single Integrated Space Picture (SISP), and Space Deconfliction (DECON). (Note: The Legacy Space C2 System Requirements Document (SRD) and drawing DM-00827 identify Astrodynamic Support Workstation (ASW), Space Perturbations Tasker (SPTasker), and Non-traditional Data Pre-Processor (NDPP) as Legacy Space C2 systems; however, OM&S for these systems is not in scope of the NISSC II OM&S.)

Engineering and Sustainment Tools The NISSC II OM&S Engineering and Sustainment Tools consist of COTS/GOTS/FOSS hardware and software and specialized applications that provide classified and unclassified database and processing capability, supporting analysis, prototyping, development, test, deployment, and baseline management of CCIC2S and Legacy Space C2. Engineering and Sustainment Tools are identified in DM-00827, Fit-for-Purpose View Level 0 and further described in Test and Development Facility (TDF) Manual.

All software/hardware (SW/HW) changes to the ITW/AA system must be successfully tested in the Test and Development Facility (TDF) prior to implementation with the operational mission system in accordance with Strategic Command Instruction (SI) 534-22, Operations, Planning, and Command and Control Mission Integrity, Change Control Management, And Test Control for the ITW/AA System.

The TDF provides a stand-alone, operationally representative environment to conduct test and evaluation activities utilizing simulated and live test data without interfering with or affecting day-to-day real world operations. The TDF systems closely mirror the operational systems increasing the likelihood that problems associated with system modifications are discovered prior to fielding. As operational systems are modified, the TDF is modified to include the operational system modifications. In addition, the TDF provides an environment to accomplish communications, missile warning, air defense, space surveillance and external testing by various communities of interest.

Engineering and Sustainment Tools include NISSC analysis, development, test, training, and configuration management tools as defined in FFP-0. Key sustainment support tools are the unclassified Engineering Life Cycle Management System (ELMS) and the classified NCMC-ITW/AA Integration and Development Environment (NIIDE).

CMAFS Information Systems Infrastructure The 21st Communications Squadron (CS) is responsible for the administration and specialized security, communications, computing, and network systems that make up the CMAFS base information systems infrastructure. These systems are not active components of CCIC2S, Legacy Space C2, or Engineering and Sustainment Tools. The OM&S Contractor will provide operations and maintenance support to the 21st for co-located base information systems infrastructure.

Terms and Definitions The following terms and definitions are applicable to the PWS:

1. Government Program Manager (GPM). The GPM provides primary program oversight and management of the task order. The GPM will also review the Contractor’s performance at periodic points in time.

Government Program Office (GPO). The GPO staff supports the GPM in execution of the task order.

Contracting Officer (CO). The individual designated by the AF to direct and/or redirect the efforts of the Contractor or modify any of the items of the contract. The CO for this HBQ task order is located at Peterson AFB, CO.

Contracting Officer Representative (COR). The COR is the Government representative appointed by the CO responsible for monitoring, evaluating, and reporting Contractor performance on the task order. The COR will interface with the Customer, the Contractor, and the GPO.

Contractor’s On-Site Task Order Lead. The contractor’s task order lead, at each support location, will serve as the focal point to work with the assigned COR. The individual typically has a detailed knowledge of daily activities associated with the PWS and task order and is responsible for day-to-day communication with the COR.

Contractor’s Program Manager. The contractor’s PM serves as the focal point between the GPM and the company’s management regarding all issues and discrepancies. The contractor’s PM ensures full compliance with the terms and conditions of the contract and has the primary responsibility for task order performance.

Functional Baseline – Documented and approved definition of system-level performance requirements. The functional baseline includes all functional and interface characteristics that are at system-level, associated statutory requirements, regulatory requirements and constraints. For NISSC II covered systems the functional baseline includes approved Maintenance Requirements in the Sustainment Portfolio awaiting implementation by the Sustainment Maintenance and Modification Services Allocated Baseline - Documented and approved definition of designated system, subsystem, or component performance, interface, and design consideration requirements. For NISSC II covered systems the allocated baseline includes the functional baseline plus approved Maintenance Actions awaiting implementation by the Sustainment Maintenance and Modification Services.

Product Baseline – Documented and validated Product Engineering Design Data and Associated Lists of the operational systems, subsystems, and components. The product baseline includes physical characteristics, materials, construction processes, deployment processes, and O&M procedures.

On-call support – When on-call support is required in this PWS the requirement is intended to mean personnel “Waiting to be Engaged” as defined in United States Supreme Court ruling in Skidmore v. Swift & Co. (1944).

1067 Form - Air Force Form 1067, per AFI 63-101, is used to document changes to Air Force requirements. Form 1067s apply to CCIC2S and Legacy Space C2 systems and are validated by the Lead/Using Command(s) and approved by the assigned Program Manager. Although not required, typically, a Standard Change Form (SCF) is developed for a Legacy Space 1067 after it has been Part II signed. Proposed changes to ITW/AA systems covered in USSTRATCOM Instruction 534-22 and NORAD Instruction 10-3, require a companion SCF in addition to a form 1067.

Standard Change Form (SCF) - A Standard Change Forms (SCF), reference USSTRATCOM Instruction 534-22 and NORAD Instruction 10-3, are required for any proposed change impacting form, fit, or function (F3I) of an ITW/AA system. An SCF is required for proposed changes to an ITW/AA system in addition to a 1067 form. An SCF may be created for a Legacy Space system change. SCFs are approved by the applicable Configuration Change Manager (CCM) utilizing the Integrated Database System Support (IDSS) (Also known as Integrated IR Database, SCF Database, IWSD Database System (IISIS) system).

Deficiency Reports (DRs) - A Deficiency Report (DR) is created and submitted by User Community\Test Community\Government\SPO personnel to correct a deficiency in the baseline that is inaccurate and needs correction. The Material Improvement Project Review Board (MIPRB) reviews all DRs for approval to proceed with the changes. The system utilized to control DRs is the Joint Deficiency Reporting System (JDRS).

System Change Requests (SCRs) - The Standard Change Request (SCR) is a change documents that describes the reason and need for an engineering baseline change. SCRs are managed by the SCR Coordinator and processed in the IDSS (formerly IISIS) system. SCRs are approved at the MIPRB and forwarded on to the contractor for processing and implementation.

Artifact Defect (AD) - Document and track documentation issues. An AD is typically initiated by the contractor when a document issue is identified during a maintenance or modification action that is not related to the action and can reasonably be deferred to be worked at a later date.

Database Change Request (DBCR) - Description of requirements for Missile Warning Data or other database updates The following terms of reference are applicable to Sustainment Maintenance and Modification Services. [Reference PWS section 3.1.3] Product Line / Product – Product Lines are logical groupings of Enterprise Systems, Systems, and Subsystems for NISSC II covered systems aligned to the FFP-0. Products are individually identified Systems and Subsystems, and components that together provide Product Line capabilities.

Product Line Manager (PLM) / Product Owner (PO) – The Government POC accountable for collaboration with the contractor’s Sustainment Maintenance and Maintenance team lead for defining and prioritizing team activities and performance to plan, perform, and complete Maintenance Requirements. The PO has a significant role in quality control and is the Government POC empowered to accept Maintenance Actions as complete.

Open – formal GPO approval that a Maintenance Requirement (submitted on IR, DR, SCF, 1067, etc.) is valid and funded to be worked. Maintenance Requirement Open processes are the responsibility of the MIPRB as defined in the DRI&R Plan.

Fully integrated - captures the Government intent that Closure of Maintenance Requirements include completion of all integration, verification, deployment, training, logistics impacts, and baseline documentation updates.

Open Maintenance Requirement – Government approved, and tracked issue that requires a fix action to resolve. Maintenance Requirements cover a wide range of complexity and effort required to resolve. SCFs, DRs, and 1067s are Maintenance Requirements. Maintenance Requirements include actions associated with end-of-life/end-of-service hardware and software issues. Maintenance Requirements are the smallest single capability that can be packaged for release to operations.

Maintenance Requirement Closure – formal GPO approval that a Maintenance Requirement is completed and removed from the Sustainment Portfolio. Maintenance Requirement Closure processes are the responsibility of the MIPRB as defined in the DRI&R Plan.

Sustainment Portfolio – The set of GPO approved Maintenance Requirements. The number of Maintenance Requirements in the Sustainment Portfolio and rate of change (up or down) is tracked by the GPO to access effectiveness of the Sustainment activities to meet stakeholder needs and used by the GPO to support strategic planning.

Maintenance Action – Parsing of a Maintenance Requirement into well-defined, standard size elements used to plan, perform, track, and measure Maintenance and Modification Services work. Maintenance Actions are expected to be a standard level of complexity and effort (typically two (2) to four (4) weeks) based on the contractor’s processes. Although rare, it is possible that a single Maintenance Action could complete a Maintenance Requirement. ‘Planned,’, ‘Threshold,’ and ‘Additional’ Maintenance Actions are defined during increment planning meetings.

Maintenance Action Closure Criteria – Clear PO approved criteria that must be met in order to close a Maintenance Action. The closure criteria must define the artifacts (i.e., hardware, software, documentation) that must be completed and the standard to be applied for Government approval of the artifacts.

Maintenance Task – Parsing of a Maintenance Action into the lowest size elements used to plan and perform work of an individual team member. Maintenance Tasks (typically one (1) to four (4) days) are expected to vary in level of complexity, effort, and skills required.

Maintenance Task Definition of Done– Contractor defined criteria that is used to determine completion of a Maintenance Task. The Definition of Done is determined in collaboration with the PO, but does not require PO approval.

APPLICABLE DOCUMENTS

PWS Referenced Documents The following documents are applicable to this PWS. All services provided under the task order shall comply with applicable statues, regulations, policies, and other requirements, required by Department of Defense Instruction (DoDI) 5000.02 and Air Force Instruction (AFI) 63-101/20-101.

1. The latest release versions shall be followed.

Documents rescinded during the execution of the contract shall be applicable until the date rescinded.

The contractor shall notify the CO within 30 calendar days of notification of revisions, changes, supplements, or rescissions if there is a cost impact resulting from such revisions, changes, supplements, or rescissions. If the CO is not notified within the 30 days, the contractor will not be compensated for any cost increase incurred for work performed in accordance with (IAW) such revisions, changes, supplements and rescissions.

Any task set forth in a reference that calls for exercise of discretionary Government authority, shall be subject to the final approval of the Government official having such authority.

If there is a conflict between two or more publications, those issued by a higher authority shall control over those issued by a lower authority.

If there is a conflict between two or more publications issued at the same level of authority, those with a later date of issue shall control over those with earlier dates of issue.

Department of Defense Publications

Department of the Air Force Publications

AFI 10-1701 AFSPCSUP

new Doc for Bidders Library

GPO Publications

Other Publications

NISSC II Covered Systems CCIC2S Baseline Documents Requirements Documents:

Interface Control Documents (ICD):

Architecture Framework:

Other Documents:

Legacy Space C2 Baseline Documents Requirements Documents:

Architecture Framework:

Engineering and Sustainment Tools Baseline Documents Requirements Documents:

Performance Requirements NOTE: Engineering and technical services provided under these requirements are subject to the General Rules regarding Organizational and Consultant Conflicts of Interest as defined in the Federal Acquisition Regulation (FAR) Part 9.505.

OM&S of CCIC2S and Legacy Space C2 Performance requirements for CCIC2S and Legacy Space C2 are documented in the CCIC2S SRD and Legacy Space C2 SRD.

The NISSC II covered systems and supporting infrastructure is a complex system of systems that is distributed over multiple sites. The maintenance and support requires skill sets from multiple disciplines working in concert in a dynamic environment. Obsolescence-driven technology refresh efforts, software and hardware maintenance and modification actions, the coordination of test facilities, and the deployment to one or more sites requires extensive coordination to maintain effective operator capability and to ensure availability of the mission equipment.

NISSC II CCIC2S and Legacy Space C2 OM&S includes all activities to assure mission performance meets requirements defined in the approved CCIC2S SRD and Legacy Space C2 SRD.

On-Site O&M, CCIC2S and Legacy Space C2 (FPIF) The objectives of On-Site Operations and Maintenance (O&M) activities are to maintain effective system user (operator) capability and ensure availability of the NISSC II covered mission equipment.

Mission Assurance Centers (MACs) monitor and administer CCIC2S and Legacy Space C2 systems at CMAFS MAC (CMAC), N2C2 MAC (NMAC), AMWC MAC- Offutt AFB (OMAC), and, CSpOC MAC - Vandenberg AFB (VMAC). MAC personnel provide 24/7 crew mission support, system administration, circuit actions, training, and help desk functions. In addition to the 24/7 MAC locations, on-site O&M activities are required at other CONUS sites on an 8/5 schedule.

OM&S activities are based on a two-level maintenance concept where Line Replaceable Units (LRUs) are removed and replaced at the Organizational-Level (O-Level) and repaired at the Depot-Level (D-Level) at the TDF or contractor’s site. On-site personnel supporting the MACs provide O-Level maintenance.

Contractor personnel working in organizational work centers must meet security clearance requirements up to the Top Secret/Sensitive Compartmented Information (TS/SCI) level. Access to USSTRATCOM facilities also requires a Nuclear Command and Control (NC2) briefing.

General On-Site O&M Tasks General On-Site O&M Tasks listed below apply at sites as specified in PWS sections 3.1.1.3 through 3.1.1.11.

System Administration

1. The contractor shall perform System Administration tasks for routine, emergency, test and exercise events IAW applicable Technical Manuals, Local Procedures, Operating Instructions, and MAC checklists.

The contractor shall create, manage, and delete user and group accounts, profiles, and policies.

The contractor shall conduct training and one-on-one assistance on NISSC II covered systems for organizational users.

The contractor shall actively monitor mission systems operational performance and link status to detect issues that may cause disruption of services.

If an issue is discovered the contractor shall take action IAW Technical Manuals, Local Procedures, Operating Instructions, and MAC checklists to prevent disruption of services.

If services are disrupted, the contractor shall take immediate action IAW Technical Manuals, Local Procedures, Operating Instructions, and MAC checklists to restore the lost services.

Upon receipt of a customer’s trouble-call, the contractor shall perform the required assessment, troubleshoot, isolate, and resolve the customer’s problem, or refer to the next level of help.

The contractor shall report all mission system and communication outages with an organizational impact to the local site Government representative and the CMAFS Systems Center within 15 minutes.

The contractor shall perform data collection (including application, system, and security logs) of any unexpected service disruption and upon request provide data to the Government to support deficiency resolution and post event forensics.

The contractor shall perform analysis of the application, system, and security logs IAW Technical Manuals, Local Procedures, Operating Instructions, and MAC checklists.

The contractor shall perform error detection and fault correction of the systems.

The contractor shall perform backups and archive of the systems IAW Technical Manuals, Local Procedures, Operating Instructions, and MAC checklists.

The contractor shall perform recovery and restore of the systems IAW Technical Manuals, Local Procedures, Operating Instructions, and MAC checklists.

The contractor shall perform startup, reboots, and shutdown of the systems IAW Technical Manuals, Local Procedures, Operating Instructions, and MAC checklists.

The contractor shall record and track all System Administration and User Support actions via Incident Reports (IRs) using the appropriate unclassified or classified Integrated Database System Support (IDSS) or future Government approved system.

The contractor shall record scheduled and unscheduled maintenance activities using the appropriate unclassified or classified IDSS or future Government approved system The contractor shall coordinate with designated local site Government representative and CMAFS Systems Center for awareness, concurrence, and resolution of system and or network anomalies.

Vulnerability Management

1. The contractor shall perform Information System Security Officer (ISSO) responsibilities defined in DoDI 8500.01.

The contractor shall monitor and assess system security vulnerabilities and threats, and report all security relevant events to the designated local site Government representative and GPO IAW the Cybersecurity Management Plan. [Reference PWS section 3.2.2].

The contractor shall retain all security relevant event artifacts and provide them to the GPO upon request.

The contractor shall provide similar vulnerability management via remote logon (to the extent allowed by the communications infrastructure) for NCMC-ITW/AANCMC-ITW/AA remote sites including the NMCC and ANMCC, as well as multiple sensors, Forward Users, and SA users.

The contractor shall update antivirus definitions without GPO approval.

Organizational Level Maintenance

1. The contractor shall perform preventive maintenance tasks (tracked in the appropriate unclassified or classified IDSS or future Government approved system) to maintain system availability IAW applicable Technical Manuals, Local Procedures, Operating Instructions, and MAC checklists.

The contractor shall obtain approval for scheduled maintenance events from the designated local site Government representative.

The contractor shall perform HW replacement on equipment.

The contractor shall perform O-Level maintenance on the equipment to restore system capability.

The contractor shall comply with all maintenance agreements, warranties, and support agreements when performing O-Level maintenance actions.

The contractor shall request Emergency Depot level Maintenance (EDLM), Unscheduled Depot level Maintenance (UDLM), or Engineering and Technical Assistance Request (ETAR); when O-Level Maintenance actions are exhausted, IAW Air Force Materiel Command (AFMC) Technical Manual TO 00-25-108 Communications-Electronics Depot Support.

Test Support The test support activities may be required to enable success of studies, prototyping, and maintenance or modification activities authorized under this TO or external Task Orders/Delivery Orders (TO/DO) impacting NISSC II covered systems. Some system level or end-to-end tests require concurrent support at more than one location where the NISSC II contractor provides on-site support.

1. When directed by the GPO and deconflicted with designated local site Government representative that activities will not interrupt current mission operations, the on-site personnel shall support NCMC-ITW/AA and Legacy Space C2 systems test activities including installation of this TO or external TO/DO capability using the SW Installation Plan / Site Preparation Requirements and Installation Plan procedures received from the TO/DO.

When directed by the GPO and deconflicted with designated local site Government representative that activities will not interrupt current mission operations, the on-site personnel shall support NCMC-ITW/AA and Legacy Space C2 systems test activities including return of the system to its operational configuration at the end of each test day or trial period using the Test Procedures received from this TO or external TO/DO.

Management and Reporting The objective of On-Site O&M – Management and Reporting activities is to establish clear and effective communication and coordination of On-Site O&M activities between the contractor and Government stakeholders.

Figure 1 illustrates how Mission Assurance Center and O-Level maintenance work is allocated across the ITW/AA and Legacy Space C2 organizational work centers.

Figure 1 Mission Assurance Center and O-Level Maintenance Approach Figure 1: Mission Assurance Center and O-Level Maintenance Approach

1. The contractor shall coordinate with appropriate local site Government representative to get workload prioritization if unable to meet the performance thresholds.

The contractor shall document On-Site O&M issues as Maintenance Requirements (e.g., DR, AD) and support Maintenance Requirement Processing to define prioritized, actionable corrective or preventive actions for resolution of those issues. [Reference PWS section 3.1.2.2 The contractor shall submit recommendation for changes to Technical Manuals (TMs) and Technical Orders (TOs) on AFTO Form 22 IAW TO 00-5-1. [Reference PWS section 3.3.1.7] The contractor shall maintain Local Procedures, Operating Instructions, and MAC checklists to be consistent with updated TMs and TOs.

The contractor shall maintain continuity binders for each on-site role that provides an overview of the role; identification of applicable service assets supported, Local Procedures, Operating Instructions, checklists, TMs and TOs; and description of “day-in-the-life” for the role.

NCMC-ITW/AA Correlation Center O&M The objectives of NCMC-ITW/AA Correlation Center O&M activities are to maintain effective system user (operator) capability and ensure availability of the NCMC-ITW/AA mission equipment at CMAFS, OAFB, and NCMC-ITW/AA remote sites including the NMCC and ANMCC, as well as multiple sensors, Forward Users, and SA users.

Tasks The individual ‘shall’ statements that combine to achieve the task objectives.

1. The contractor shall staff NCMC-ITW/AA Correlation Center with 24x7x365 on-site personnel and additional staff 8x5 weekdays minus US Federal holidays.

1. NCMC-ITW/AA Correlation Center On-site personnel shall have a minimum security clearance of Top Secret/Sensitive Compartmented Information (TS/SCI) after the start of TO option year 2.

1. NCMC-ITW/AA Correlation Center On-site personnel shall have a minimum security clearance of SECRET and a minimum of sixteen (16) personnel with minimum security clearance of TS/SCI at the time of acceptance of O&M responsibility and maintain this minimum level through TO option year 1. [Reference PWS section 3.10, Milestone 8].

1. NCMC-ITW/AA Correlation Center On-site personnel shall have a minimum security clearance of TS/SCI plus NC2 for USSTRATCOM facilities.

1. The contractor shall perform System Administration tasks defined in paragraph 3.1.1.1.1 System Administration.

The contractor shall provide system administration and user support via telephonic, email, and remote logon (to the extent allowed by the communications infrastructure) for NCMC-ITW/AA remote sites including the NMCC and ANMCC, as well as multiple sensors, Forward Users, and SA users.

The contractor shall perform Vulnerability Management tasks defined in paragraph 3.1.1.1.2 Vulnerability Management.

The contractor shall request and track NCMC-ITW/AA Correlation Center Organizational Level Maintenance from the 21 CS through a Remedy based work order management system. [Reference PWS section 3.9.3].

The contractor shall perform Test Support tasks defined in paragraph 3.1.1.1.4 Test Support.

The contractor shall perform Management and Reporting tasks defined in paragraph 3.1.1.1.5 Management and Reporting.

The contractor shall report CCIC2S Enterprise outages IAW Systems Center (SC) Outage Reporting Guide.

The contractor shall conduct daily organizational standup meetings to communicate status, critical events, and issues.

The contractor shall plan, host, and conduct a Monthly Outage/Incident Review to provide overview of outages and incidents, root cause analysis, and actions taken to reduce risk of future occurrence of similar outages or incidents.

The contractor shall develop meeting notes for each Monthly Outage/Incident Review.

The contractor shall collect, analyze, and report metrics of on-site O&M task performance relative to outcomes / standards defined in this PWS.

Deliverables The artifacts prepared by the tasks and provided to the Government. Includes CDRLs and non-CDRLs

1. Incident Reports (IRs) [DAL Item] Maintenance Requirements (e.g., DR, AD) [DAL Item] Security Relevant Event Artifacts [DAL Item] On-site O&M task performance metrics [DAL…