Section_J_Atch_03 _SEWS_II_U.S._Support_PWS.pdf

SECTION J, ATTACHMENT 3, U.S. SUPPORT PERFORMANCE WORK STATEMENT

Section J, Attachment 3, U.S. Support Performance Work Statement: FA8723-16-R-0005

SHARED EARLY WARNING SYSTEM (SEWS) PRIME CONTRACT RE-COMPETE

(SEWS II)

UNITED STATES (U.S.) SUPPORT PERFORMANCE WORK STATEMENT (PWS)

TASK ORDER 02

SOLICITATION NO.: FA8723-16-R-0005

ATTACHMENT 03

23 SEPTEMBER 2016

Air Force Materiel Command

Air Force Life Cycle Management Center

Battle Management Directorate

Strategic Warning and Surveillance Systems Division

(AFLCMC/HBQS)

RECORD OF REVISIONS:

VERSION DESCRIPTION Date

001 Initial 19 Dec 2015

002 Draft 05 Feb 2016

003 Draft 31 May 2016

004 Final 23 Sep 2016

1. OVERVIEW

This PWS defines the performance based requirements for Operations, Maintenance, and Support (OM&S) of existing U.S., Theater Combatant Commands (COCOMs), and COCOM-sponsored partners and the integration requirements of all tasks across the various Task Orders (TOs) and Delivery Orders (DOs) of the SEWS II contract.

1.1 PROGRAM OBJECTIVES

The SEWS Program objectives are targeted at reducing total cost of ownership, increasing system interoperability, evolving to integrated Command and Control (C2) architectures that more readily adapt to mission change, and ensuring mission integrity and continuity of operations throughout the evolutionary process. The joint Contractor and SEW System Program Office (SPO) program objectives are to:

1. Maximize flexibility while meeting all operational, functional, and technical requirements on a 24x7x365 basis

2. Employ effective cost, schedule, plans, and real-time adjustments that ensure the SEW System functions at peak performance levels. The efficiencies are expected to keep costs controlled and turn actions quickly

3. Maintain mission performance by sharing cross-trained personnel across theaters

4. Identify and manage risks proactively by identifying issues as they arise and making the SEW SPO aware of concerns

5. Generate, maintain, and use near real time Missile Event Information (MEI) data

1.2 SCOPE

This PWS specifically addresses U.S. appropriated/funded work concentrated in the following areas:

1. Migrate the existing SEW System to a standardized architecture; field a common SEW architecture

2. Integrate SEW capability through systems engineering efforts

3. Install, integrate, relocate, and sustain existing SEW System equipment, training, and system upgrades

4. Implement system design modifications required to maintain Government approved functional architecture

5. Support, design, implement, maintain, and monitor system security requirements as identified in applicable Cybersecurity guidance and directives

6. Achieve interoperability and collaboration among U.S., COCOMs, and COCOM-sponsored partners, where practicable

7. Enable and perform external integration with Air Force (AF), Department of Defense

(DoD), and other interfacing systems with emphasis on interoperability and organizational level sustainment

1.3 COCOMS AND COCOM-SPONSORED PARTNER SPECIFIC INFORMATION

1.3.1 UNITED STATES CENTRAL COMMAND (USCENTCOM) SITUATIONAL

AWARENESS (SA) FEED

Provide technical assistance for systems in the Centralized Distribution Facility (CDF) to the USCENTCOM Headquarters (HQ) at MacDill AFB, Florida, and the Secondary Distribution Facility (SDF). The SDF is located in Tampa, Florida.

1.3.2 UNITED STATES PACIFIC COMMAND (USPACOM) SITUATIONAL

AWARENESS (SA) FEED

Provide technical assistance for systems in the CDF to the following sites in the USPACOM Area of Responsibility (AOR): The SDF at HQ PACOM, Camp Smith, Hawaii;

U.S. Forces Korea (USFK) at Camp Walker, South Korea; USFK at Osan Air Base, South Korea; USFK at U.S. Army Garrison Yongsan, South Korea; U.S. Forces Japan (USFJ) at Yokata Air Base (AB), Japan; USFJ at Camp Zama, Japan.

1.3.3 UNITED STATES EUROPEAN COMMAND (USEUCOM) SITUATIONAL

AWARENESS (SA) FEED

Provide technical assistance for systems in the CDF to the following sites in USEUCOM AOR: The SDF at HQ USEUCOM, Stuttgart Germany; HQ U.S. Air Forces Europe (USAFE), Ramstein Air Base, Germany.

1.3.4 NORTH ATLANTIC TREATY ORGANIZATION (NATO)

Provide technical assistance for systems in the CDF to the following NATO locations:

Supreme Allied Command Transformation (SACT) in Norfolk, Virginia; the Joint Analysis Center (JAC) at Royal Air Force (RAF) Molesworth, United Kingdom (U.K.); and Supreme Headquarters Allied Powers Europe (SHAPE), Mons, Belgium.

2. SEWS II SUPPORT REQUIREMENTS

2.1 PROGRAM MANAGEMENT AND INTEGRATION

The Contractor shall manage all tasks in an integrated manner across all TOs/DOs. The Contractor shall identify a Program Manager (PM) who will be the primary SEWS II contract representative responsible for all planning, organizing, coordinating, integrating, managing, and executing all requirements included in this PWS in accordance with the Program Management Body of Knowledge and DoD Program Management standards.

The Contractor shall maintain efficiency in cost, schedule, and performance, and eliminate duplication of work among multiple TOs/DOs. The Contractor shall identify risks, resolve problems, and verify effectiveness of corrective actions. Results of Contractor actions taken to improve performance shall be tracked and shared with the Government, and lessons learned incorporated into applicable processes.

2.1.1 CONTROL/COST ACCOUNT MANAGEMENT

The Contractor shall ensure all charges are properly allocated in accordance with the Contract Work Breakdown Structure (CWBS).

2.1.1.1 CONTRACT WORK BREAKDOWN STRUCTURE (CWBS) AND CWBS

DICTIONARY

The Contractor shall maintain the integrated CWBS and CWBS dictionary that includes all TOs/DOs. The Contractor shall use the CWBS as the primary framework for contract planning, budgeting, and reporting of the cost, schedule, and technical performance status to the Government for this TO. Prior to implementing any changes to the CWBS and/or associated definitions, at any level included in the Government’s Preliminary WBS, the Contractor shall request and obtain Government approval of the change. CDRL A004

– Contract Work Breakdown Structure (CWBS).

2.1.2 SECURITY

The Contractor shall meet applicable security requirements included in the SEWS II DD Form 254, DoD Contract Security Classification Specification. The PM shall notify the Contracting Officer Representative (COR), Procurement Contracting Officer (PCO), and PM within 24 hours of any security incident involving SEWS II contractor personnel.

2.1.3 ASSOCIATE CONTRACTOR AGREEMENTS (ACA)

Upon award and/or when notified by the PCO, the Contractor shall pursue entering into ACAs in accordance with (IAW) Section J, Attachment 25, for any portion of the contract requiring joint participation in the accomplishment of the Government’s requirement.

2.1.4 DOCUMENT AVAILABILITY

The Contractor shall make all documents and materials created or modified because of this TO available in the Integrated Data Environment (IDE). The Contractor shall submit documents for Foreign Disclosure Office (FDO) approval as required by law. The Contractor shall make the documents and materials available within 30 days of their creation, modification, or completion, as applicable, unless other requirements in this contract specify or allow a longer period. See IDE paragraph 2.1.4.1.

2.1.4.1 INTEGRATED DATA ENVIRONMENT (IDE)

For the life of the SEWS II contract, the Contractor shall host, maintain, and manage an unclassified IDE online that provides cost effective information storage, efficient retrieval, and effective data management capabilities. The SEW SPO shall approve any change, whether it be a major capability, functionality, or user interface change, to the initial design as briefed to the Government at SEWS II Transition Kick-Off Meeting prior to implementation. The Contractor shall ensure the IDE has a disaster recovery capability.

2.1.4.2 IDE DATA REPOSITORY

The Contractor shall use the IDE to provide scalable data repositories of both formal and informal program documentation. The Contractor shall configure the IDE to be continuously accessible by the Government and be used to enable information sharing and collaboration. Final information shall be noticeably segregated from “in-work/draft” documentation. The Contractor shall include, in the repository, documentation and materials from/for all TOs/DOs. The required timelines for posting these materials are dictated by the associated Contract Data Requirements List (CDRL), contract clause, or (failing either of those) a default of five (5) business days. The Contractor shall use this indexed data repository as the primary data storage, retrieval, and management system for SEWS.

The Contractor shall collect, manage, track, modify, and maintain a master set of all SEWS documents (to include those provided/generated by the Government) at the latest approved revision. The Contractor shall maintain all previous versions of documents (both major and minor revisions). The Contractor shall maintain all master documents in Microsoft Office, Adobe Acrobat, or similar human-readable formats that are part of the standard AF desktop suite. The IDE shall be capable of providing a list of the products on the IDE. The list shall include document number, title, security classification, and posting date. The list must be viewable and printable by all account holders.

2.1.4.3 IDE ACCESS

For the life of the SEWS II contract, the Contractor shall provide secure access from the program office facility to the IDE providing information storage, retrieval, and management capabilities. The Contractor shall provide SEWS stakeholders a graphical user interface usable by personnel with a common level of office skills to access all SEWS information, documentation, and materials associated with the contract. In doing this, the Contractor shall adhere to industry best practices for information assurance, data integrity, and recovery within an allowable downtime of one (1) business day (no more than three (3) business days per quarter). The Contractor shall provide secure browser access to the unclassified IDE for a minimum of fifty (50) concurrent users. Account access for Government personnel shall be identified by a single Government Program Office point of contact. The Contractor shall provide a section, within the IDE, that is available for Government use only.

2.1.4.4 IDE TRANSFER

The Contractor shall deliver the complete, operational IDE (all contents and documentation) to the Government at contract end.

2.1.5 INTEGRATED MASTER SCHEDULE (IMS)

The Contractor shall establish, maintain, and deliver an overarching IMS for all SEW SPO activities across all TOs/DOs. CDRL A00A – Integrated Program Management Report

(IMPR).

2.1.5.1 INTEGRATED MASTER SCHEDULE WORKING GROUP (IMSWG)

The Contractor shall plan, host, and conduct a bi-monthly Government chaired Integrated Master Schedule Working Group (IMSWG). CDRL A001 – Briefing Material.

2.1.6 INTEGRATED RISK MANAGEMENT

The Contractor shall implement a continuous, integrated risk management process to identify, track, and resolve technical and programmatic risks across SEWS. For each risk, the Contractor shall:

1. Identify risks;

2. Analyze and characterize, to include risk probability, consequence (technical, schedule, cost), and associated rationale(s);

3. For Contractor risks, identify a sustainment risk handling strategy (assume, transfer, mitigate, avoid, watch) and strategy rationale for each risk is identified. The rationale should include an assessment of overall cost, schedule, or technical impact of the handling strategy versus the risk consequence;

4. For Contractor risks, identify detailed mitigation activities for each “mitigated” risk;

5. Map risks and significant mitigation activities to the CWBS and IMS; and,

6. Attend and provide risk analysis at the monthly Government chaired Risk Review

Boards (RRB). CDRL A001 – Briefing Material.

2.1.7 COST AND SCHEDULE

The Contractor shall manage the tasks within this PWS to remain within cost and schedule.

2.1.8 INTEGRATED PROGRAM MANAGEMENT PLAN (PMP)

The Contractor shall create, deliver, maintain, and execute a comprehensive PMP integrated across all TOs/DOs. CDRL A00E – Program Management Plan.

2.1.9 PROGRAM OFFICE MEETINGS AND REVIEWS

The Contractor shall prepare and present contract performance, issues, systems performance, and status of all active TOs and DOs during the SEW SPO weekly review meetings. The Contractor shall plan, host, and conduct monthly PM-to-PM meetings for the overall SEWS II contract. Additionally, the Contractor shall conduct a consolidated quarterly review of funding, history, outstanding actions, and status of significant interest items in a Contractor Program Manager Review (CPMR). CDRL A001 – Briefing Material.

2.1.10 FINANCIAL REPORTS

The Contractor shall develop and deliver a TO-specific Contract Funds Status Report (CFSR), a consolidated Financial Actual Report, and a consolidated Program Hours Worked (PHW) Report. The Contractor shall prepare and present to the Government monthly funds status briefings by TO and DO. CDRL A003 – Contract Funds Status Report (CFSR), A007 – Financial Report, and A001 - Briefing Material.

2.1.11 SYSTEM SAFETY PROGRAM

The Contractor shall create, deliver, maintain, and execute a System Safety Program Plan IAW the methodology in MIL-STD-882E, DoD Standard Practice for System Safety.

The Contractor shall ensure compliance with Federal, State, and local regulations pertaining to Environment, Safety and Occupational Health (ESOH) for the SEW System.

CDRL A00N - System Safety Program Plan.

2.1.12 GENERAL SUPPORT REQUIREMENTS

The Contractor shall review Government draft documents and products (e.g., Memorandums Of Agreement (MOAs)/Memorandums of Understanding (MOUs), Authorization & Assessment (A&A) packages, Defense Information Assurance Security Accreditation Working Group (DSAWG) products and packages, equipment lists, U.S., COCOM, and COCOM-sponsored partner requirements) and provide input to the Government within five (5) business days.

2.1.13 SECURITY WORKING GROUP

The Contractor shall attend and provide inputs and recommendations at quarterly Government chaired/conducted SEWS Security Working Group meetings. The Contractor shall annually review the Government Program Protection Plan and provide input to the Government within thirty (30) business days.

2.2 SYSTEM ENGINEERING (SE) AND SUSTAINMENT

The Contractor shall plan, organize, coordinate, integrate, execute, and manage all SE and Sustainment efforts on the SEWS II effort at the appropriate levels to be effective and efficient. The Contractor shall invite the Government to participate in all Contractor technical and management Integrated Product Teams (IPTs), working groups, and review boards. The Contractor shall create, deliver, maintain, and execute an integrated Systems Engineering Management Plan (SEMP) to document the Contractor’s SE processes. The SEMP prepared by the Contractor shall be in close alignment with the Government SEW Systems Engineering Plan (SEP), and evolve with the Government SEP. CDRL A00Q – Systems Engineering Management Plan (SEMP).

2.2.1 SYSTEM ENGINEERING (SE) SUPPORT

The Contractor shall plan, organize, coordinate, integrate, execute, and manage all SE efforts on SEWS II at the appropriate levels to be effective, yet efficient. The Contractor shall maintain efficiency in performance and eliminate duplication of work among multiple TOs/DOs. The Contractor shall participate in the overall system architecture, integration, and sustainment of the SEW System, to include evolving, standardizing, and normalizing the system architecture while providing required capabilities.

2.2.1.1 SYSTEM TECHNICAL BASELINE

The Contractor shall develop, maintain, update, and integrate the Government-controlled System Technical Baseline artifacts and documentation as identified in the SEW System Technical Baseline Matrix. The Contractor shall use Configuration Management (CM) processes to maintain, update, and integrate artifacts and documents. The Contractor shall ensure compatibility with the Government CM processes. The Contractor shall re-integrate artifacts and documentation as a result of any SEWS II TOs/DOs into the baseline to ensure the master set of artifacts and documentation is complete, current, and accurate. The Contractor shall ensure all SEW System artifacts and documentation reside in the IDE (see IDE para 2.1.4.1). CDRL A00C – Interface Design Description (IDD), A00H – Software User Manual (SUM), A00K – System Administrator Manual (SAM), A00M – System Requirements Document (SRD), A00P – System Subsystem Design Description (SSDD), A00R – Technical Data Package (TDP), and A00B – Interface Control Document (ICD), A008 – DoD Architecture Framework Documentation (DoDAF), and A002 – COTS Manuals and Associated Supplemental Data.

2.2.1.2 EVENT RECORDINGS AND ANALYSIS

The Contractor shall conduct daily analysis of event recordings and look for any discrepancies of overall system performance. The Contractor shall monitor all inputs and outputs to ensure system integrity. The Contractor shall perform event analysis to resolve any issues or questions by U.S., COCOMs, and COCOM-sponsored partners. Results of the analysis and recommended corrective actions shall be provided to the Government within five (5) business days. CDRL A00R – Technical Report – Studies/Services.

2.2.1.3 INTEGRATION AND TEST FACILITY (ITF)

The Contractor shall maintain, operate, and sustain the ITF. The Contractor shall ensure the ITF is capable of supporting a full range of integration activities for both the currently fielded system as well as maintenance and modernization releases. The Contractor shall purchase, integrate, and support ITF equipment.

2.2.1.3.1 INTEGRATION

The Contractor shall integrate system modifications and updates into the existing system architecture. The Contractor shall conduct an integration test and trial period prior to shipment of any system or component to any location and implementation on the operational SEW System. The Contractor shall conduct a one (1) week (at a minimum) trial period to verify and validate system requirements of the integrated components. The Contractor shall provide the Government a test plan for approval prior to entering into the trial period. CDRL A00T – Test Plan – Test Procedure.

2.2.1.3.2 COMMERCIAL-OFF-THE-SHELF (COTS) SOFTWARE (SW) UPDATES

The Contractor shall assess and integrate all COTS incremental patches or upgrades within the ITF in accordance with industry best practices. The Contractor shall conduct sustaining engineering analysis of COTS SW updates in the ITF to ensure SEW SRD requirements are maintained.

2.2.1.3.3 GOVERNMENT-OFF-THE-SHELF (GOTS) SOFTWARE (SW) UPDATES

The Contractor shall assess and integrate up to twelve (12) GOTS SW incremental patches or upgrades annually within the ITF. The Contractor shall conduct sustaining engineering analysis of current GOTS SW upgrades to demonstrate capabilities included in subsystems satisfy the SEW SRD requirements. The Contractor shall prepare and submit deficiency reports for any identified issues and provide the reports to the Government. CDRL A00S – Technical Report – Studies/Services.

2.2.1.3.4 RESEARCH AND DEVELOPMENT (R&D)

The Contractor shall conduct the following R&D activities in the ITF:

1. Investigate new technologies to identify major system improvements relating to improving the system maintainability, sustainability, and cybersecurity posture

2. Develop integration capabilities from changes in message format or delivery

3. Assess and develop enhanced capabilities for the Cross Domain Solution (CDS) baseline

4. Procure, configure, and maintain test and development equipment

5. Attend weekly Missile Defense Agency (MDA) exercise planning meetings and conduct up to twelve (12) MDA exercise tests annually

The Contractor shall provide analysis results and design recommendations in a briefing to the Government on a quarterly basis. CDRL A001 – Briefing Material.

2.2.1.4 ENGINEERING MEETINGS AND REVIEWS

The Contractor shall prepare and present any system configuration changes, engineering issues, and potential courses of action at bi-weekly Government chaired/conducted SEWS Joint Engineering Review Boards (JERBs). CDRL A001 – Briefing Material.

The Contractor shall prepare and present the JERB-approved course of action for system configuration change(s) at monthly Government chaired/conducted SEWS Configuration Control Boards (CCBs). All CCBs shall be preceded by a JERB (engineering proposals shall include a Government engineering review and a CCB Presentation). CDRL A001 – Briefing Material.

The Contractor shall attend and provide inputs and recommendations at the weekly Government chaired/conducted SEWS System Engineering Integrated Product Team meetings (SE-IPT).

The Contractor shall attend and provide inputs and recommendations at quarterly Government chaired/conducted SEWS Test Working Group meetings.

2.2.2 CYBERSECURITY

The Contractor shall provide the following Cybersecurity functions: vulnerability assessment testing; security control impact assessment on proposed or discovered system changes; risk assessments; mitigation and remediation development and implementation; engineering design proof-of-concept demonstrations; development of security control implementation strategies; development, implementation, and maintenance of automated auditing solutions and continuous monitoring solutions; JERB presentations; and Incident Response/Reporting. The Contractor’s SEWS II efforts shall comply with DoDI 8500.01, DoDI 8510.01, and other Cybersecurity guidance and directives as applicable.

2.2.2.1 CYBERSECURITY TESTING

The Contractor shall test the SEW System for Cybersecurity compliance after installation of any new equipment in the SEW System operational baseline (reflected on network topology drawing) to ensure there is no change in risk posture prior to operational implementation of equipment in sustaining engineering or maintenance efforts. The Contractor shall notify the Government if any system modification results in a change in risk posture. Government approval must be provided prior to operational implementation.

The Contractor shall conduct security assessment scans prior to an independent/external entity’s testing or in conjunction with Authorization and Assessment (A&A) tasks on a six

(6) month basis. The Contractor shall provide security assessment scan results to the Government. CDRL A00S – Technical Report – Study/Services and A00L – System Authorization and Accreditation Artifacts.

2.2.2.2 ASSESSMENT AND AUTHORIZATION (A&A)

The Contractor shall develop, maintain, and provide A&A documents and artifacts IAW DoDI 8500.01. The Contractor shall review Cybersecurity related MOAs, MOUs, or other appropriate agreements, and provide input to the Government to facilitate A&A approval.

CDRL A00L – System Authorization and Accreditation Artifacts.

2.2.2.3 PERSONNEL CERTIFICATION REQUIREMENTS

The Contractor shall ensure all Contractor personnel granted privileged access to system components or assigned to cybersecurity positions shall meet DoDI 8570.01-M certification requirements.

2.2.2.4 INFORMATION SYSTEM SECURITY OFFICER (ISSO)

The Contractor shall assign specific personnel (primary and alternate) to the ISSO role (IAT Level II IAW AFI 33-200 and DoD 8570.01-M) to ensure information systems are functional and secure. The assigned Contractor personnel will be appointed, in writing, by the Information System Security Manager (ISSM) or the SEWS Program Manager.

Contractor personnel performing these functions shall be identified as part of the cybersecurity workforce and shall comply with the roles and responsibilities defined in AFI 33-200, AFI 33-210, and DoD 8570.01-M.

The Contractor shall perform the following activities to maintain situational awareness and/or initiate actions to improve or restore cybersecurity posture:

1. Implement and enforce all AF, DoD, and SEWS cybersecurity policies, procedures, and countermeasures using the guidance within those instructions and applicable cybersecurity publications

2. Account Management, to include identifying and tracking all privileged users

3. Vulnerability Management

4. Reviewing/monitoring audit logs for potential security incidents

5. Track Secure Technical Implementation Guide (STIG) compliance

6. Track Anti-Virus updates and implementation schedules

7. Documentation input, accuracy, and artifact maintenance

8. Training, Exercises, and Drills

9. Change Management (JERB, CCB)

10. Independent Validation Testing support

11. Ensure visitor access records are maintained

12. Emission Security (EMSEC) and Computer Security (COMPUSEC) inspections/ compliance/package preparation

13. Security Management compliance with SEWS plans, policy, and procedures

14. Participate in annual review security control effectiveness analysis

15. Monitor system security and provide incident response and reporting

2.2.2.5 CROSS DOMAIN SOLUTION (CDS) APPROVAL PACKAGES

The Contractor shall interact with internal and external stakeholders to facilitate obtaining the required CDS approval package artifacts. The Contractor shall coordinate with the appropriate DoD-service Cross Domain Solution Element (CDSE) to obtain CDS package approval. The Contractor shall coordinate with the Defense Information Assurance Security Accreditation Working Group (DSAWG) for CDS change implementation approval.

2.3 OPERATIONS, MAINTENANCE, AND SUPPORT (OM&S)

The Contractor shall operate, maintain, and support the SEWS operational system 24x7x365 to provide timely and accurate missile event information.

2.3.1 CENTRALIZED DISTRIBUTION FACILITY (CDF) OPERATIONS

The Contractor shall operate, maintain, and support the SEW System to meet the requirements detailed in the SEW SRD. The Contractor shall open and close the CDF each business day (excluding Government holidays) and conduct security checklist actions according to local policy. The Contractor shall perform on-site CDF management, physical configuration audits and inventory, system monitoring, maintenance of system components and communications lines, and report issues to the maintenance team for resolution and restoration. A technician shall be present in the CDF for not less than the hours of 0730-1630 Mountain Standard Time (MST), excluding weekends and Government holidays. Outside of these hours, the Contractor shall respond as the single point of contact for all SEWS U.S., COCOM, and COCOM-sponsored partners within thirty (30) minutes.

2.3.1.1 SYSTEM MONITORING & TROUBLE TICKETS

The Contractor shall monitor and provide technical assistance and support 24x7x365 for incoming queries and issues. Upon receipt of an incoming query or issue, the Contractor shall document and log the issue, actions taken, and the Point of Contact (POC) to whom they spoke into a trouble ticket. The Contractor shall log all trouble tickets into the IDE database and monitor trouble tickets through resolution and close out.

2.3.1.2 SYSTEM OUTAGE REPORTING

The Contractor shall notify the Government of all system outages, including planned outages. On critical outages (no SEW data to customer), the Contractor shall report via direct contact (in person/over phone) to the SEW SPO POC and via email to the applicable COCOM POC within one (1) hour of being notified of the outage. On non-critical issues/outages (SEW data still being delivered to customer), the Contractor shall report via email to the SEW SPO and the applicable COCOM POC within one (1) business day. Reports shall include at a minimum: description explaining nature of the outage;

time and date of outage; when and how technician was notified; time of technician response; name of technician(s); date and time of restoration; a comprehensive narrative description of internal and external troubleshooting efforts and fix actions; external POC names and ticket numbers. The Contractor shall provide the following SEWS integrated reports to the SEW SPO Personnel:

1. Daily System Status: Each business day (excluding Government holidays) the Contractor shall provide a summary of system status and all communication outages, identifying the location of the outage and the fix actions attempted, from the time of the previous report. The daily report shall be in encrypted e-mail format titled “Daily Status E-Mail”.

2. Weekly Summary: The Contractor shall provide a weekly summary of outages and any events which degrade availability or reliability of the system. The weekly summary shall include an analysis and recommended course(s) of action to the SEWS Program Manager and/or designee. The Contractor shall propose an executive summary format suitable for a five (5) minute presentation to be given during the SEW SPO weekly review meetings.

3. Monthly Availability Report: The Contractor shall provide a monthly report containing an executive summary of system availability which lists metrics for each location, as well as a running six (6) month chart of availability per location. CDRL A00S – Technical Report – Study/Services.

4. Monthly Outage Report: The Contractor shall provide a monthly report containing narrative descriptions of all system outages. At a minimum, include analysis of troubleshooting activities and fix actions, outage trends as well as any recommended improvements or efficiencies. CDRL A00S – Technical Report – Study/Services.

2.3.1.3 COMMUNICATION SECURITY (COMSEC)

The Contractor shall acquire and maintain COMSEC account and administer the account IAW DoD 5220.22-M. The Contractor shall coordinate with the installation COMSEC office to provision and maintain necessary crypto key material. The Contractor shall perform COMSEC duties and perform sustainment activities such as periodic crypto key updates and daily inventory. The Contractor shall obtain, procure, support, document, and account for secure/non-secure equipment and communications enhancements, as well as assist COMSEC custodians at U.S. customer SEWS sites.

2.3.2 SEWS MAINTENANCE AND SUPPORT SERVICES

2.3.2.1 PREVENTATIVE MAINTENANCE

The Contractor shall conduct daily checks (during normal CDF hours of operation) of the SEW System and shall communicate with customers’ systems’ maintainers and sponsoring COCOMs to ensure U.S. systems are fully operational at all times. The Contractor shall communicate to the SEW SPO any potential non-compliance with the SEW SRD present course(s) of action within five (5) business days. CDRL A00S – Technical Reports – Study/Services.

2.3.2.2 SYSTEM OUTAGE RESTORAL

The Contractor shall exhaust all capabilities and resources to restore system capability to the state prior to the system outage. The Contractor shall notify, coordinate, and facilitate resolution by working with any Contractors, vendors, suppliers, and other agencies. Once all resources are exhausted, and if necessary, the Contractor recommends to the Government if/when an emergency on-site support (EOSS) and/or Government intervention/assistance is necessary.

On critical outages (no SEWS data to customer), the Contractor shall prepare and present to the Government a restoral plan within two (2) hours. On non-critical issues/outages (SEW data still being delivered to customer), the Contractor shall prepare and present to the Government a restoral plan within two (2) business days.

2.3.2.3 EXTERNAL COORDINATION

The Contractor shall interact with external stakeholders. These relationships are reflected in the SEWS Organizational Relationships document (Operational View–4).

2.3.2.4 CDF EXERCISE SUPPORT

The Contractor shall support up to twelve (12) exercises/test injects annually (e.g., operational readiness, system integration, system interoperability). The support requires exercise planning efforts (e.g., meetings, working groups, conferences), recording of data, analyzing the results of the exercise, and reconfiguring system components to support exercises. The Contractor shall provide exercise support during both normal duty and non-duty hours.

2.3.2.5 INTEGRATED LOGISTICS SUPPORT

The Contractor shall plan, organize, coordinate, integrate, execute, and manage all logistics tasks included in this PWS. The Contractor shall eliminate duplication of work among multiple TOs/DOs.

2.3.2.5.1 INTEGRATED LOGISTICS SUPPORT PLAN (ILSP)

The Contractor shall create, deliver, maintain, and execute an ILSP. The ILSP must describe the planning and management functions to be performed by the Contractor, as well as the Performance Based Logistics framework that will be used for OM&S of the SEWS. In addition, the Contractor shall ensure the ILSP addresses the 12 Life Cycle Sustainment Product Support Elements (PSEs) listed below, as applicable: CDRL A009

- Integrated Logistics Support Plan (ILSP).

1. Sustaining/Systems Engineering

2. Design Interface

3. Supply Support

4. Maintenance Planning and Management

5. Support Equipment/Automatic Test Systems (SE/ATS)

6. Facilities

7. Packaging, Handling, Storage, and Transportation (PHS&T)

8. Technical Data Management/Technical Orders

9. Manpower and Personnel

10. Training

11. Computer Resources

12. Protection of Critical Program Information and Anti-Tamper Provisions

2.3.2.5.2 INTEGRATED LOGISTICS SUPPORT WORKING GROUP (ILSWG)

The Contractor shall plan, host, and conduct monthly Government chaired ILSWG. CDRL A001 - Briefing Material.

2.3.2.5.3 INVENTORY

The Contractor shall maintain and deliver complete up-to-date listings of all SEW System secure and non-secure equipment (including equipment model and specifics, specific location of equipment, status of functionality, and disposition status) by site and installation date. CDRL A00J Status of Government Furnished Equipment (GFE) Report and CDRL A00D – Inventory Listing.

The Contractor shall maintain and manage the capability to support inventory control and logistics assessments (e.g., obsolescence management activities by accurately tracking all current equipment to include software, HW warranties/maintenance agreements, SW licenses, spares, and obsolescence management data to the equipment LRU level). The Contractor shall track which software applications reside on each hardware item. The Contractor shall provide the Government access to the data and analysis, when requested, and provide information/updates at the ILSWG.

2.3.2.5.3.1 SPARING ANALYSIS

The Contractor shall perform and update sparing analyses to determine and maintain the most appropriate levels, locations and distribution methods of spares for each unit/subassembly installed to meet the performance requirements for the SEW Systems.

The analyses shall identify any assumptions, formulas, or models used. The Contractor shall provide sparing analysis/updates to the Government at the ILSWG.

2.3.2.5.4 OBSOLESCENCE MANAGEMENT (OM)

The Contractor shall continuously track and analyze hardware, software, and firmware for Original Equipment Manufacturer vendor support to identify when vendor support ends. The Contractor shall identify and present the results of the supportability analysis during the ILSWG. The Contractor shall also coordinate with the GOTS Programs of Record (PoRs) for obsolescence of any GOTS items.

The Contractor shall resolve form/fit/function/interface Line Replaceable Unit (LRU)-level obsolescence issues through standard depot maintenance practices. If not form/fit/function/interface equipment LRU-level obsolescence issues, the Contractor shall provide OM mitigation options and recommended actions, if any, at the ILSWG.

2.3.2.5.5 PROCUREMENT

The Contractor shall procure, acquire, and manage all equipment, spares, maintenance agreements, warranties, support agreements, and licenses in the Government’s name specific to the SEW Systems. The Contractor shall comply with all warranty terms for all COTS products installed. The Contractor shall deliver all maintenance agreements, warranties, licenses, and support agreements to the Government at contract end. CDRL A002 – COTS Manuals and Associated Supplemental Data.

2.3.2.5.5.1 HW/SW LICENCES

The Contractor shall, when purchasing COTS hardware and software licenses for use on SEWS U.S. and COCOM requirements, use mandatory Air Force and Department of Defense contracts before purchasing the hardware and software in the open market.

Examples of such contracts are AFWAY, NETCENTS II, and the DoD’s Enterprise Software Initiative (ESI) Blanket Purchase Agreement (BPAs).

2.3.2.5.6 PACKAGING, HANDLING, STORAGE, & TRANSPORTATION (PHS&T)

The Contractor shall be responsible for PHS&T activities for all system equipment and consumables. The Contractor shall properly store spares. Shipments shall be completed via commercial means, U.S. Postal Service, and/or designated Freight Forwarder, as specified by the DD Form 1155. The Contractor shall ensure all shipments are received at the destination within the required timelines through coordination and verification activities. Associated transportation documentation shall be developed and maintained in the approved IDE (e.g., DD Form 1149, Export Documentation, receipt verification).

2.3.2.5.6.1 EXPORT OF TECHNICAL SERVICES

The Contractor shall comply with the requirements of the International Traffic in Arms Regulations (ITAR), including guidance from the Secretary of the Air Force – International Affairs (SAF/IA), and applicable authorized delegated FDOs, to export defense services and defense articles for FMS Cases/activities. The Contractor shall register with Directorate of Defense Trade Controls (DDTC) to maintain direct contact with the SEWS customers.

2.3.2.5.7 DISPOSITION/DEMILITARIZATION

The Contractor shall perform demilitarization/disposal activities for permanently removed software, hardware, and other equipment in accordance with Government instructions.

2.3.3 SEWS ON-SITE OPERATIONS, MAINTENANCE, & SUPPORT (OM&S)

The Contractor shall conduct on-site OM&S at U.S., COCOM, and COCOM-sponsored partner sites. The Contractor shall be able to respond to simultaneous incidents in three

(3) geographically separated Sensitive Compartmented Information Facilities (SCIFs) with no interruption to mission. The Government specifies the scheduling, location, and specific OM&S travel requirements (See Table 3). The Contractor shall include all on-site OM&S travel schedules in the IMS. The Contractor shall travel IAW the “Authorization to Support” letter for technical and travel support, signed by the PCO, effective for the TO duration.

2.3.3.1 ON-SITE OM&S

The Contractor shall conduct pre-trip planning, post-trip reports, routine site equipment maintenance, crypto re-key, cybersecurity upgrades, site surveys, site preparation and installation plans, site relocations, system testing support, redline technical baseline artifacts, physical configuration audit of the operational system (inventory), anti-virus updates, client and server back-ups, and provide exercise support. The Contractor shall implement and perform semi-annual GOTS and COTS software updates. The Contractor shall perform one (1) Tactical Display Processor (TDP) and one (1) Tactical Receiver Suite (TRS) software upgrade annually. CDRL A00V – Trip Report, A00F – Site Preparation Requirement and Installation Plan, and A00G – Site Survey.

2.3.3.1.1 OPERATIONAL INTEGRATION TEST

After shipment and installation of any system or component to a customer location, the Contractor shall perform testing to verify system performance within the operational SEWS. The Contractor shall develop and deliver an operational integration test plan which captures how the Contractor will demonstrate system completeness and mission performance. Testing may be conducted after hours due to time differences from the CDF to the COCOM-sponsored customer. CDRL A00T – Test Plan – Test Procedures.

2.3.3.2 EMERGENCY ON-SITE SUPPORT (EOSS)

The Contractor shall only respond to Emergency and Urgent on-site support requests after the SEW SPO or delegate authorizes such actions. The Contractor shall conduct emergency on-site support when directed by the Government and as identified in Table

3. Unplanned trips (not identified in Table 3) will utilize Time and Material (T&M) CLINs.

The contractor shall provide the government daily status updates until the EOSS activities are completed. The Contractor, upon completion of EOSS activities, shall notify the Program Office the EOSS activities are complete and shall provide the total time required to return to operations.

2.3.3.3 COCOM HEALTH CHECKS AND EXERCISE SUPPORT

The Contractor shall conduct COCOM Health Check, support exercises, and attend world-wide conferences that requires travel to another location to set up equipment, monitor the exercise, troubleshoot problems, and/or document results, as specified in Table 3.

2.3.3.4 FAMILIARIZATION TRAINING

The Contractor shall conduct on-site system familiarization training at U.S., COCOM, and COCOM-sponsored partner sites. The Government specifies the scheduling, locations, specific training requirements, and frequency of training in Table 3. The Contractor shall submit a Training Plan to the Government for review. The familiarization training shall include both communications systems training and TDP (e.g., GCCS-J) training. The Contractor shall develop, maintain, and/or update student and instructor training materials. The Contractor shall submit any documentation provided to a non-U.S.

customer to the FDO as required by law. CDRL A00U - Training Material.

2.3.3.4.1 USCENTCOM FAMILIARIZATION TRAINING

The Contractor shall keep current and provide two (2) System User’s Manuals (SUM) per site. The Contractor shall keep current and provide TDP (e.g., GCCS-J) familiarization training material during each semi-annual OM&S trip (5 copies per site). CDRL A00H – System User’s Manual and A00U – Training Material.

2.3.3.4.2 USPACOM FAMILIARIZATION TRAINING

The Contractor shall keep current and provide one (1) SUM per site. The Contractor shall keep current and provide TDP (e.g., GCCS-J) familiarization training material during one

(1) semi-annual OM&S trip (10 copies per trip). CDRL A00H – System User’s Manual and A00U – Training Material.

2.3.3.4.3 USEUCOM FAMILIARIZATION TRAINING

The Contractor shall keep current and provide one (1) SUM per site. The Contractor shall keep current and provide TDP (e.g., GCCS-J) familiarization training material during one

(1) semi-annual OM&S trip (10 copies per trip). CDRL A00H – System User’s Manual and A00U – Training Material.

2.3.4 ON-SITE TECHNICIAN/ENGINEER

(RESERVED).

3. GENERAL INFORMATION

3.1 GOVERNMENTAL SUPERVISION OF CONTRACTOR EMPLOYEES

The Government will not supervise or otherwise direct Contractor employees. The Government will inspect Contractor performance in accordance with (IAW) the Quality Assurance Surveillance Plan (QASP) and any other clauses included in the contract.

3.2 PLACE OF PERFORMANCE

CDF and ITF tasks shall be performed at the Government-owned facility located on Peterson AFB, Colorado. The Contractor shall perform the required work at the locations identified in their proposal. The Contractor shall perform portions of the required work at the Contractor’s own facilities or off-site locations.

3.3 BASE SUPPORT

The Government will provide utilities/base support for limited office space and storage, secure storage containers (safes) for up to twenty (20) co-located personnel. At the Government facility, the Government will provide utilities at no cost, limited to electricity, natural gas, water, and sewage. Additional base support, provided at no cost to the Contractor, includes facility maintenance and alarm maintenance. The Government will provide to Contractor-designated work areas, as validated by the Government, Local Area Network (LAN) access, telephone services (e.g., Defense Switched Network (DSN), and telephones. Use must be in accordance with (IAW) applicable publications. The Contractor will be required to participate in all energy conservation programs.

3.4 DUTY HOURS

When working on Government sites, normal duty hours are 0730-1630, Monday through Friday; however, duty hours may vary by specific U.S., COCOM, and COCOM-sponsored site. Portions of the required work support continuous operations (24 hours per day, 7 days per week, 365 days per year).

3.5 LEGAL HOLIDAYS

The Federal Government observes the following holidays:

New Year's Day Martin Luther King's Birthday President's Day Memorial Day Independence Day Labor Day Columbus Day Veteran's Day

Thanksgiving Day Christmas Day

3.6 SECURITY REQUIREMENTS

3.6.1 PERSONNEL SECURITY

The Contractor shall comply with the SEWS DD Form 254. The highest personal security clearance required by this TO is Top Secret/SCI. The Contractor is responsible for acquiring required clearances. The Contractor may be given access to applicable documentation to include requirements, plans, specifications, studies, and analyses up to and including Top Secret/SCI classification.

3.6.2 CONTRACTOR IDENTIFICATION

The Contractor shall comply with their company identification procedures. The Contractor shall comply with all Government identification requirements for Contractors for the Government facilities and locations where the Contractor performs work. The Contractor shall identify its Contractor status when interacting with Government personnel at meetings, in emails, and during telephonic exchanges.

3.6.3 PERFORMANCE OF SERVICES DURING CRISES

In the case of crises declared by the President of the United States, the Secretary of Defense, or an overseas Combatant Commander, some of the services required by this contract are considered mission essential. Contractor must have access to the CDF during crisis. Refer to the Mission Essential Plan, Section J, Attachment 27.

3.6.4 TRAVEL REQUIREMENTS

Contractor employees may be required to travel to various locations within the continental U.S., COCOM, or COCOM-sponsored sites. All travel shall be in accordance with JTR, SAF/IA guidance, Department of State Standardized Regulations, FDO guidance, and in compliance with the DoD Foreign Clearance Guide, individual protection, and individual deployment policies required by the specific COCOMs, and foreign country entry and exit requirements.

3.6.5 EXPORT OF TECHNICAL SERVICES

The Contractor shall comply with ITAR, SAF/IA guidance, and applicable authorized delegated FDO guidance. The Contractor will have direct contact with the SEWS customers and shall register with DDTC, coordinate ITAR exemptions, and obtain approved Technical Assistance Agreements (TAAs) as required.

4. SERVICE DELIVERY SUMMARY (SDS)

Table 1 defines the Contractor service requirements to be used for the performance and evaluation of this TO. The Performance Objective is a reference point for Government personnel and does not relieve the Contractor from any contractual requirements.

Table 1. Service Delivery Summary Performance

Objective Performance Objective PWS Section

Threshold (Acceptable Quality Levels)

Method of Surveillance

Program Management

The Contractor shall utilize industry best practices and enterprise level systems to provide insight into contract cost, schedule and performance factors. The Contractor shall, subject to Government approval, implement common processes, procedures, and maintenance practices where feasible. The Contractor shall demonstrate resource stewardship and transparency by employing industry standards for maintenance management, systems engineering, project management, customer centered mission support, safety, security, environmental, quality management, and other logistical functions.

The Contractor meets applicable security requirements included in the DD Form 254, DoD Contract Security Classification Specification. All incidents involving Contractor personnel at all locations will be reported to the PCO/COR and PM.

Zero (0) security incidents. Ensure security directives are complied with 100% of the time.

Periodic Inspection; Trend Analysis; Contractor Metrics

The Contractor maintains an overarching IMS IAW with CDRL A00A – Integrated Program Management Report

(IPMR).

IMS deliverables are current, accurate, and do not contain omissions.

The IMS contains no more than three (3) program/schedule errors per Delivery.

Upon CDRL review; Weekly Meetings

Table 1. Service Delivery Summary Performance

Objective Performance Objective PWS Section

Threshold (Acceptable Quality Levels)

Method of Surveillance

The Contractor shall implement and perform a disciplined risk management process across all aspects of the SEWS, focusing on system performance, technical requirements, cost, and schedule. The Contractor shall proactively identify issues and risks to the Government as they are aware of concerns, and manages/mitigates them to meet PWS, SRD, and mission requirements.

Provide status of program and technical risks to include Government and Contractor program risks.

Weekly Meeting;

Monthly Program Review

Measurement of the Contractor’s synergy of operations as to how well they are cross-utilizing/sharing human capital.

Provide status of efficiency report maintained to facilitate cross-utilized resource sharing.

Monthly Program Review

Table 1. Service Delivery Summary Performance

Objective Performance Objective PWS Section

Threshold (Acceptable Quality Levels)

Method of Surveillance

The Contractor provides timely and accurate financial reports and informs Government of issues pertaining to costs that impact project overruns and under-runs. Timeliness for the CFSR is defined in the CDRL A003 – Contractor Funds Status Report (CFSR); the Financial Actuals Report is due monthly 14 calendar days after the accounting month cut-off; the PHW is due within 10 workdays of each quarter’s end.

Zero (0) late financial report deliveries over the life of the contract; Issues pertaining to all cost overruns and under-runs addressed in financial reports.

100% Surveillance; Periodic Inspection; Trend Analysis;

Contractor Metrics

Systems Engineering

Apply repeatable and tailored SE principles and practices to all aspects of SEWS II. Establish and implement a structured SE program appropriately tailored to the cost, schedule, performance, risk, and technical…