Section_J_Atch_10 _P3_PWS.pdf

SECTION J, ATTACHMENT 10, P3 PERFORMANCE WORK STATEMENT (PWS)

Section J, Attachment 10, P3 Performance Work Statement: FA8723-16-R-0005

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

(SEWS II)

FOREIGN MILITARY SALES (FMS) CASE TW-D-DAB (P3) PERFORMANCE WORK

STATEMENT (PWS)

TASK ORDER 09

SOLICITATION NO.: FA8723-16-R-0005

ATTACHMENT 10

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 05 Feb 2016

002 Draft 31 May 2016

003 Final 23 Sep 2016

1. OVERVIEW

The Contractor provides support for Shared Early Warning System (SEWS) in the United States (U.S.) Pacific Command (USPACOM) Area of Responsibility (AOR). This Performance Work Statement (PWS) specifically addresses a SEWS Foreign Military Sales (FMS) customer which will be referred to as P3. Support to this case is provided jointly by Contractor and Government representatives.

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 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 work concentrated in the following areas:

1. Operations, Maintenance, and Support (OM&S) of the PACOM sponsored partner for the P3 FMS Case

2. Migrate existing SEW systems to a standardized architecture; field a common SEW architecture

3. Integrate new SEW capability through systems engineering efforts

4. Install, integrate, relocate, and sustain existing SEWS equipment, training, and system upgrades

5. System design modifications required to maintain Government approved functional architecture

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

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

8. 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.2.1 PARTNER SPECIFIC INFORMATION

The Contractor shall use the existing SEWS architecture for P3 which consists of eight

(8) sites on six (6) military installations. Additionally, there are two (2) commercial leased, dedicated and diverse data circuits (one Secret and one Sensitive But Unclassified data) from Peterson Air Force Base (PAFB), Colorado, to two (2) separate locations in P3 (sites #1 and #2) to carry MEI data. The MEI data is disseminated between sites through a P3 provided internal Wide Area Network (WAN). The architecture includes a previously installed, but not activated, Broadband Global Area Network (BGAN) capability to be activated during this period of performance. Additionally, a third commercial leased circuit (Secret data) extends to another site from HQ USPACOM (acting as a Secondary Distribution Facility). The Contractor shall also support the Automated Data Transfer (ADT) laptop and software which feeds the P3 Early Warning Message Distribution System (EWMDS). No full-time on-site engineer is required in P3 for the FMS Case.

However, in-country contractor support has been provided and is managed via the U.S.

Government under a separate contract mechanism.

2. SEWS II SUPPORT REQUIREMENTS

2.1 PROGRAM MANAGEMENT AND INTEGRATION

The Contractor shall manage all tasks in an integrated manner across all Task Orders/Delivery Orders (TOs/DOs). The Contractor shall plan, organize, coordinate, integrate, execute, and manage all requirements included in this PWS. The Contractor shall maintain efficiency in cost, schedule, and performance, and eliminate duplication of work among multiple TOs/DOs, particularly for activities that require “hand-offs” between TOs/DOs (e.g., changes driven by a project that is incorporated into the baseline documentation). 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 include P3-specific tasks in the integrated CWBS and CWBS dictionary. 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.

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

(RESERVED).

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 thirty (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)

The Contractor shall maintain P3-specific products in the SEWS program Integrated Data Environment (IDE) as the authoritative data repository for System, Technical Baseline, Contract, and Program documentation. The information shall be made available to SEW SPO personnel upon request and be remotely accessible.

2.1.5 INTEGRATED MASTER SCHEDULE (IMS)

The Contractor shall include P3-specific activities in the overarching Integrated Master Schedule (IMS) for all SEW SPO activities as described.

2.1.5.1 INTEGRATED MASTER SCHEDULE WORKING GROUP (IMSWG)

The Contractor shall address P3-specific activities during the bi-monthly Government chaired Integrated Master Schedule Working Group (IMSWG).

2.1.6 INTEGRATED RISK MANAGEMENT

The Contractor shall integrate P3-specific risks into the consolidated SEWS risk management process. The Contractor shall pro-actively communicate all P3-specific risks to the Government. 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. Provide P3-specific risk analysis at the monthly Government chaired Risk Review

Boards (RRB).

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 include the management of P3 FMS activities in the integrated program-level PMP. This program-level PMP shall describe the processes the Contractor uses to track output-oriented metrics and tie them to cost data and program milestones.

2.1.9 PROGRAM OFFICE MEETINGS AND REVIEWS

The Contractor shall include P3-specific contract performance, issues, systems performance, and status during the SEW SPO weekly review meetings. Additionally, the Contractor shall include P3-specific information into the consolidated quarterly review of funding, history, outstanding actions, and status of significant interest items to be presented at the Contractor Program Manager Review (CPMR).

2.1.10 FINANCIAL REPORTS

The Contractor shall provide financial reports to include a P3-specific Contract Funds Status Report (CFSR) and contribute P3-specific information into the consolidated Financial Actual Report and the consolidated Program Hours Worked (PHW) Report.

CDRL A003 – Contract Funds Status Report.

2.1.11 SYSTEM SAFETY PROGRAM

The Contractor shall include P3-specific information into the System Safety Program Plan IAW the methodology in MIL-STD-882E, DoD Standard Practice for System Safety.

2.1.12 GENERAL SUPPORT REQUIREMENTS

The Contractor shall review Government draft documents and products (e.g., Memorandums Of Agreement (MOA)/Memorandums of Understanding (MOU), 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 within five (5) business days. The Contractor shall assist the SEW SPO in developing International Agreements (e.g., FMS Cases) and coordinating equipment releasability and disclosure.

2.1.13 SECURITY WORKING GROUP

The Contractor shall include P3-specific information/inputs and recommendations at quarterly Government chaired SEWS Security Working Group meetings.

2.2 SYSTEMS ENGINEERING (SE) AND SUSTAINMENT

The Contractor shall plan, organize, coordinate, integrate, execute, and manage all SE and Sustainment efforts on this TO at the appropriate levels to be effective and efficient.

The Contractor shall invite the Government to participate in all P3 specific Contractor technical and management Integrated Product Teams (IPTs), working groups, and review boards. The Contractor shall contribute P3-specific information into the integrated Systems Engineering Management Plan (SEMP) to document the Contractor’s Systems Engineering (SE) processes.

2.2.1 SYSTEMS ENGINEERING (SE) SUPPORT

The Contractor shall plan, organize, coordinate, integrate, execute, and manage all P3-specific 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 P3-specific 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 P3-specific 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 P3-specific TOs/DOs into the baseline to ensure the master set of artifacts and documentation is complete, current, and accurate. The Contractor shall ensure all P3-specific artifacts and documentation reside in the IDE. CDRL A00C – Interface Design Description (IDD), A00H – Software User Manual (SUM), A00K – System Administrator Manual (SAM), A00P – System Subsystem Design Description (SSDD), A00R – Technical Data Package (TDP), A00B – Interface Control Document (ICD), A002 – COTS Manuals and Associated Supplemental Data, and A008 – DoD Architecture Framework (DoDAF) Documentation.

2.2.1.2 EVENT RECORDINGS AND ANALYSIS

The Contractor shall conduct daily recordings of events and look for any discrepancies of overall system performance. The Contractor shall monitor inputs and outputs to ensure system integrity. The Contractor shall perform event analysis to evaluate system performance and respond to any issues or questions from the P3 partner. Results of the analysis and recommended corrective actions shall be provided to the Government within five (5) business days. CDRL A00S – Technical Report – Studies/Services.

2.2.1.3 INTEGRATION AND TEST FACILITY (ITF)

The Contractor shall support P3-specific integration and test activities. The Contractor shall be capable of supporting a full range of integration activities for both the currently fielded system as well as maintenance and modernization releases.

2.2.1.3.1 INTEGRATION

The Contractor shall integrate system modifications and updates into the existing P3-specific 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 Procedures.

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)

(RESERVED).

2.2.1.4 ENGINEERING MEETINGS AND REVIEWS

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

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 and A00W – Briefing Minutes.

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

The Contractor shall provide P3-specific 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 P3-specific upgrades for Cybersecurity compliance after installation of any new equipment in the P3-specific system operational baseline within the US Accreditation Boundary (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 A00L – System Authorization and Accreditation Artifacts.

2.2.2.2 ASSESSMENT AND AUTHORIZATION (A&A)

(RESERVED).

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 certification requirements.

2.2.2.4 INFORMATION SYSTEM SECURITY OFFICER (ISSO)

(RESERVED).

2.2.2.5 CROSS DOMAIN SOLUTION (CDS) APPROVAL PACKAGES

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

The Contractor shall operate, maintain, and support the P3-specific 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 P3-specific deployed systems to meet the requirements detailed in the SEW SRD.

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 any P3-specific 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 integrate P3-specific information into the daily system status, weekly summary, monthly availability, and monthly outage reports.

2.3.1.3 COMMUNICATION SECURITY (COMSEC)

The Contractor shall install and sustain secure devices acquired through a National Security Agency (NSA) FMS Case in direct support of P3. The Contractor shall coordinate with the installation COMSEC office to provision and maintain necessary crypto key material. The Contractor shall perform COMSEC account custodial duties IAW DoD 5220.22-M and perform sustainment activities such as periodic crypto key updates.

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 P3-specific system and shall communicate with customers’ systems’ maintainers and sponsoring COCOMs to ensure the 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 ensure entire system performance by notifying, coordinating, and facilitating resolution by working with any Contractors, including coordination with commercial vendors for support, suppliers, and/or other agencies (e.g., foreign partner WAN provider) to keep the SEWS fully functional to meet the technical requirements.

2.3.2.4 CDF EXERCISE SUPPORT

(RESERVED)

2.3.2.5 INTEGRATED LOGISTICS SUPPORT

The Contractor shall plan, organize, coordinate, integrate, execute, and manage all logistics tasks included in this PWS.

2.3.2.5.1 INTEGRATED LOGISTICS SUPPORT PLAN (ILSP)

The Contractor shall include P3-specific information into the 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 P3 systems.

2.3.2.5.2 INTEGRATED LOGISTICS SUPPORT WORKING GROUP (ILSWG)

The Contractor shall include P3-specific information into the monthly Government chaired

ILSWG.

2.3.2.5.3 INVENTORY

The Contractor shall maintain a complete up-to-date inventory of all P3-specific SEWS 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. The Contractor shall maintain and deliver the inventory list to the Government two

(2) weeks prior to any scheduled on-site OM&S activity. CDRL A00D – Inventory Listing.

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 P3 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 action if any, during 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 to support P3. The Contractor shall comply with all warranty terms for all COTS products installed in the systems. The Contractor shall maintain the capability to procure out-of-cycle equipment (FMS-funded surge CLIN). The Contractor shall maintain the capability to purchase equipment in country with Government approval. 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 the P3 systems, 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 utilize their proposed depot storage facility for P3-specific items. The Contractor shall utilize the designated Freight Forwarder to complete shipments to the COCOM-sponsored partner as identified in the TO. 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 1149, Export Documentation, receipt verification). The COCOM-sponsored partner is responsible to distribute assets to appropriate storage/installation location(s).

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

(RESERVED).

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

The Contractor shall travel to P3 partner sites to conduct on-site system familiarization training and OM&S activities. 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 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. For each installed location, the Contractor shall keep current and provide to each site a System Administration Manual (SAM). The Contractor shall ensure any documentation provided to a non-U.S. customer be approved for release by the FDO prior to transfer of the material. CDRL A00V – Trip Report, A00G – Site Survey, and A00K – System Administration Manual.

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 SUSTAINMENT (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

(RESERVED).

2.3.3.4 FAMILIARIZATION TRAINING

The Contractor shall conduct annual on-site system familiarization training at P3-specific partner sites in conjunction with a semi-annual OM&S activities. The Government will specify the scheduling, locations, specific training requirements, and frequency of training (See Table 3). The Contractor shall submit a Training Plan to the Government for review.

The familiarization training shall include both P3 SEWS-specific communications systems training and TDP (e.g., GCCS-J) training. The training program covers the entire P3-specific SEWS with a focus on operations, configuration, and maintenance. The

Contractor shall develop, maintain, and/or update student and instructor training materials. The Contractor shall ensure any documentation provided to a non-U.S.

customer is approved for release by the FDO prior to transfer of the material. CDRL A00U

– Training Material.

2.3.4 ON-SITE TECHNICIAN/ENGINEER

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 and at P3-specific in-country sites. The Contractor shall perform portions of the required work at the Contractor’s own facilities or off-site locations.

3.3 BASE SUPPORT

(RESERVED).

3.4 DUTY HOURS

When working on U.S. Government sites, normal duty hours are 0730-1630, Monday through Friday. When working at P3-specific sites, duty hours will be dictated while in-country based upon assigned tasks and customers preferences. 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 Contractor is responsible for acquiring required clearances. The highest personal security clearance required by this TO is Top Secret/SCI. 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 and potentially travel to P3-specific in-country sites. 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 contributes Task Order-specific activities to the overarching IMS.

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

The Contractor identifies Task Order-specific risks to the SEWS risk management process, 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

Objective Performance Objective PWS Section

Threshold (Acceptable Quality Levels)

Method of Surveillance

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

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; the Financial Actuals Report is due monthly fourteen (14) calendar days after the accounting month cut-off; the PHW is due within ten (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 complexities. The SE program should bring value to the Program Office. The Contractor provides systems engineering support as required to ensure that PWS, SRD, and mission requirements are met, including:

Maintain the SEWS-unique architectures

SEW architectures updated 15 business days after return from OM&S trips and maintained in the

IDE

Periodic inspection;

random sampling

Cybersecurity security assessment Must be within 5% of independent verification

Upon delivery

Objective Performance Objective PWS Section

Threshold (Acceptable Quality Levels)

Method of Surveillance

Mission System Sustainment

The operational users receive MEI data at the TDP per the performance requirements of the SRD, ORD, or FMS Case. The Contractor must also meet the requirements of the PWS by:

Sustain the SEW system to meet the performance standards specified by the SEWS SRD or FMS Case.

As specified in the SEWS SRD or FMS Case.

Periodic inspection;

Contractor metrics;

Customer complaint

Monitor and provide 24x7x365 support to ensure that data is passing to the remote locations and the TDPs display the data properly.

24x7x365 support is provided 100% of the time.

Periodic inspection;

Contractor metrics;

Customer complaint

During degraded system performance, the Contractor shall:

Coordinate, and facilitate resolution by working with any Contractors, vendors, suppliers, and other agencies to keep the SEWS fully functional to meet the SRD and FMS Case requirements.

Resolved 90% of issues without Government intervention.

Periodic inspection;

Contractor metrics;

Customer complaint

On critical outages (no SEW data to customer) – the Contractor shall:

Present a restoral plan within two

(2) hours

On non-critical issues/outages (SEW data still being delivered to customer) – the Contractor shall:

Present a restoral plan within two

(2) business days

Percentage of Government Accepted Restoral Results (RR):

At a minimum, the RR% was 75% as expressed as the percentage of RRs required (RRR) the Government accepted (RRA):

RR% = RRA / RRR

Periodic inspection;

Contractor metrics;

Customer complaint

5. INDEX OF CONTRACT DATA REQUIREMENTS LISTING (CDRL)

Table 2 is the index of CDRLs for the P3 Task Order.

Table 2. Deliverables

DM # Title

A001 Briefing Material

A002 Commercial-Off-The-Shelf (COTS) Manuals and Associated Supplemental Data

A003 Contract Funds Status Report (CFSR)

A005 Data Accession List (DAL)

A008 DoD Architecture Framework (DoDAF) Documents

A00B Interface Control Description (ICD)

A00C Interface Design Description (IDD)

A00D Inventory Listing

A00G Site Survey

A00H System User Manual (SUM)

A00K System Administrator Manual (SAM)

A00L System Authorization and Accreditation (A&A) Artifacts

A00P System Subsystem Design Description (SSDD)

Table 2. Deliverables

DM # Title

A00R Technical Data Package (TDP)

A00S Technical Report – Study/Services

A00T Test Plan – Test Procedures

A00U Training Material

A00W Briefing Minutes

6. TRAVEL TABLES

Table 3. P3 Basic PoP (1 October 2017 – 14 May 2018)

(CLIN 0046 Labor, CLIN 0047 Travel)

Purpose Location GFY Trips No

Trvlrs

Labor Category

(e.g. GCCS / Tech, Engr)

Trvl Days

Rest / Week End

Days

Work Days

Work Duty

Hours

Total Trip

Days

Danger Area (Y or N)

Travel hrs/tvlr

/trp

Total Trvl Hrs

Work Hrs/Tvlr

Total Work Hrs

Total Hrs

OM&S P3 FY18 1 2

1 Tech, 1

GCCS

3 4 15 10 22 N 48 96 150 300 396

EOSS P3 FY18 1 1 1 Tech 3 0 5 8 8 N 48 48 40 40 88

Table 4. P3 Basic PoP (15 May 2018 – 30 September 2022) (CLIN 1046 Labor, CLIN 1047 Travel)

Purpose Location GFY Trips No

Trvlrs

Labor Category

(e.g. GCCS / Tech, Engr)

Trvl Days

Rest / Week End

Days

Work Days

Work Duty

Hours

Total Trip

Days

Danger Area (Y or N)

Travel hrs/tvlr

/trp

Total Trvl Hrs

Work Hrs/Tvlr

Total Work Hrs

Total Hrs

OM&S P3 FY18 1 1 1 Tech 3 4 15 10 22 N 48 48 150 150 198

OM&S P3 FY19 1 2

1 Tech, 1

GCCS

3 4 15 10 22 N 48 96 150 300 396

OM&S P3 FY19 1 1 1 Tech 3 4 15 10 22 N 48 48 150 150 198

EOSS P3 FY19 1 1 1 Tech 3 0 5 8 8 N 48 48 40 40 88

OM&S P3 FY20 1 2

1 Tech, 1

GCCS

3 4 15 10 22 N 48 96 150 300 396

OM&S P3 FY20 1 1 1 Tech 3 4 15 10 22 N 48 48 150 150 198

EOSS P3 FY20 1 1 1 Tech 3 0 5 8 8 N 48 48 40 40 88

OM&S P3 FY21 1 2

1 Tech, 1

GCCS

3 4 15 10 22 N 48 96 150 300 396

OM&S P3 FY21 1 1 1 Tech 3 4 15 10 22 N 48 48 150 150 198

EOSS P3 FY21 1 1 1 Tech 3 0 5 8 8 N 48 48 40 40 88

OM&S P3 FY22 1 2

1 Tech, 1

GCCS

3 4 15 10 22 N 48 96 150 300 396

OM&S P3 FY22 1 1 1 Tech 3 4 15 10 22 N 48 48 150 150 196

EOSS P3 FY22 1 1 1 Tech 3 0 5 8 8 N 48 48 40 40 88

7. MANDATORY AND ADVISORY PUBLICATION AND DOCUMENTS

7.1.1 The Government has identified publications and documents that are mandatory (applicable) and advisory (reference) for this PWS. Mandatory coded publications and documents require contractor compliance. Advisory coded publications and documents provide guidance to the contractor to the extend necessary to accomplish the tasks and requirements in this PWS.

7.1.2 Publications preceded by “in accordance with”, or “IAW”, or indicated as “applicable” are mandatory requirements upon the contractor and are incorporated by reference into this PWS. In those cases, the remainder of the document is advisory. The contractor shall comply with the current version of the referenced publications reference.

The contractor shall notify the Government PCO within thirty (30) days of receipt of revisions, changes, supplements, and notifications of rescission (including referenced publications in this PWS and federal, state, and local regulations and statutes), if there is a cost impact resulting from such revisions, changes, supplements, and rescissions. If the Government PCO is not notified, and the contractor performs IAW such revisions, changes, supplements, and rescissions, it will be at no increase to the contract’s price.

Revisions, changes, supplements, and rescissions to publications that increase cost will not become effective until directed by the Government PCO.

7.1.3 PRECEDENCE OF DOCUMENTS

7.1.3.1 If there is a conflict between or among two or more publications, those coded mandatory shall control advisory/guidance. Between or among those similarly coded, those issued by a higher authority shall control over those issued by a lower authority. Between or among those issued at the same level of authority, those with a later date of issue shall control over those with earlier dates of issue. Any task set forth in any such reference that shall call for the exercise of discretionary Government authority that cannot be delegated, shall be subject to the final approval of the Government official having such authority.

7.1.3.2 Values in this PWS identifying specific section/paragraph indicate application to the whole section, i.e., 3 indicates applies to whole section, 3.3 indicates applies only to paragraph 3.3 in Section 3. When a paragraph is cited, subparagraphs are implied, i.e., citing 3.3 implies 3.3.1, 3.3.2… 3.3.X are also cited.

7.1.3.3 Requirements may change due to publication revisions, additions, or deletions; therefore, the contractor shall search for current documentation (including advisory) prior to creation of a contractor process or documentation.

7.1.4 APPLICABLE DOCUMENTS:

1. Joint Travel Regulations, 1 October 2014

2. Directorate of Defense Trade Controls (DDTC)

3. The International Traffic in Arms Regulations (ITAR) 22 CFR, Parts 120-130

4. MIL-STD-882E, Department of Defense Standard Practice System Safety, 11 February 2000

5. DoD 5220.22-M, National Industrial Security Program, 28 February 2006

6. DoDI 8500.01, Cybersecurity, 14 March 2014

7. DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT), 12 March 2014

8. DoDD 8570.01-M, Information Assurance Training, Certification, and Workforce Management, 15 August 2004

9. Shared Early Warning (SEW) System Requirements Document (SRD), Version 1.0, 15 April 2016

10. Shared Early Warning (SEW) Systems Engineering Plan (SEP), Version 1.0, 31 October 2008

11. Shared Early Warning System (SEW) Technical Baseline Matrix

7.1.5 REFERENCE DOCUMENTS:

1. Presidential Decision Directive (PDD)/NSC-17 for U.S. Policy on Ballistic Missile Defense (BMD), 11 December 1993

2. SEWS Program Budget Decision (PBD) 756, Major Command, Control, Communications, and Intelligence (C3I) Initiatives, 23 December 1998

3. SEWS Program Management Directive (PMD) 2438, 14 April 2000

4. DoD Product Support Manager (PSM) Guidebook, November 2015

5. AFMAN 33-283, Communications Security (COMSEC) Operations, 3 September 2014 (and change 1, 4 June 2015)

6. AFI 63-101/20-101, Integrated Life Cycle Management, 23 February 2015

7. AFI 33-200, Air Force Cybersecurity Program Management, 31 August 2015

8. AFI 33-210, Air Force Certification and Accreditation (C&A) Program (AFCAP), 23 December 2008 (incorporating Change 1, 2 October 2014)