SE4 - Attachment 3 - Statement of Work (SOW) 09MAR2018.pdf

N00039-18-R-0060 i

SPACE AND NAVAL WARFARE SYSTEMS COMMAND (SPAWAR)

SHORE GLOBAL

COMMAND, CONTROL, COMMUNICATIONS, COMPUTER,

INTELLIGENCE, SURVEILLANCE AND RECONNAISSANCE (C4ISR)

INSTALLATIONS CONTRACT

STATEMENT OF WORK

09 MARCH 2018

DISTRIBUTION STATEMENT A: Approved for public release, distribution is unlimited

(09 MARCH 2018)

N00039-18-R-0060 ii

TABLE OF CONTENTS

1.0 SCOPE

1.1 Introduction

1.2 Description

1.3 Web Tools

1.4 Locations

2.0 APPLICABLE DOCUMENTS

2.1 General Application Rules and Principles

2.1.1 Sources of Documents

2.1.2 Potential Conflicts

2.1.3 Order of Precedence

2.1.4 Potential Errors

2.2 Applicable Documents for Shore Installation Services

3.0 REQUIREMENTS

3.1 Program and Project Management

3.1.1 Contract Program Management Reviews (PMRs)

3.1.2 Project Management Plan (PMP)

3.1.3 Project Integrated Master Schedule (IMS)

3.1.4 Daily Status Meetings

3.1.5 Task Order Progress and Status Report

3.1.6 Performance Report

3.1.7 Earned Value Management (EVM)

3.1.8 Monthly Actual Cost Work Breakdown Structure (WBS) Report

3.1.9 Change Order Request Notification (CORN) Process

3.1.10 Meetings

3.1.11 Trip Reports

3.1.12 Technical Reports

3.1.13 Production Schedule/POA&M

3.1.14 Electronic Contractor Manpower Reporting

3.1.15 Project Integrated Master Plan

3.2 Systems Engineering

3.2.1 Configuration Management

3.2.2 Cybersecurity

3.2.3 Design, Integration, Configuration or Installation of Hardware and Software

3.3 Pre-Installation

3.3.1 Site Surveys

3.3.2 Shore Design Documentation

3.3.3 System Operational Verification Test (SOVT) Development

3.3.4 Contractor Furnished Material

3.3.5 Fabrication

3.3.6 Equipment and Material Staging and Transportation

3.4 Installation

3.4.1 Installation Tasks

3.4.2 Removal

3.4.3 Minor Construction

N00039-18-R-0060 iii

3.4.4 Shore Confined Space Work

3.5 Installation Testing and Logistics

3.5.1 Installation Pre-SOVT Inspection and Testing

3.5.2 System Operational Verification Test (SOVT) Support

3.5.3 System Operational Verification Test (SOVT) Performance

3.5.4 Training

3.5.5 Shore Installation Logistic Support Documentation

3.6 Technical Assistance

3.6.1 Fault Isolation and Repair

3.7 Special Fabrication Tasks

3.8 Excess Material and Equipment Disposition

3.9 Quality

3.9.1 Quality Management System

3.9.2 Quality Control

3.9.3 Quality Assurance Records

3.9.4 Contractor Quality Assurance Workbook

3.9.5 Formal Corrective Action Responses and Root Cause Analysis

3.10 Safety

3.10.1 Accident Notification

3.10.2 Shore Facilities Electrical Safety

3.11 Clean-up

3.11.1 Abandoned Cable

3.12 Data Security

3.12.1 Effective Use of Controls

3.12.2 National Information Assurance Partnership (NIAP) Requirement

3.13 Task Order (TO) Completion

3.13.1 Task Order Completion Report (TOCR)

3.13.2 Final Actual Cost WBS Report

3.14 Planning & Design for Large Scale C4ISR Installation Projects

3.14.1 System Requirements

3.14.2 C4ISR/IT Integrated Systems Design

3.14.3 C4ISR/IT Systems Installation Design

4.0 FACILITY REQUIREMENTS

4.1 Permanent Facilities

5.0 DOCUMENTATION AND DELIVERABLES

5.1 CDRLs

5.2 ELECTRONIC FORMAT

6.0 Contractor Information System

6.1 Information Security

6.1.1 Safeguards

6.1.2 Compliance

7.0 SECURITY REQUIREMENTS

7.1 Access Control of Contractor Personnel

7.1.1 Physical Access to Government Facilities and Installations

7.1.2 Submittal of Security Clearance Information for US Locations

7.1.3 Submittal of Security Clearance Information for Tasks Outside of the US . 45

N00039-18-R-0060 iv

7.2 Classified Materials Handling

7.3 Requirements for TS/SCI Clearances

7.4 Control of Contractor Personnel

7.4.1 Site Security

7.4.2 Common Access Card (CAC) Requirements

7.4.3 IT Position Categories

7.4.4 Security Training

7.4.5 Handling of Personally Identifiable Information (PII)

8.0 OPERATIONAL SECURITY (OPSEC) REQUIREMENTS

8.1 Local and Internal OPSEC Requirement

8.2 OPSEC Training

List of Tables

Table 1 ─ Applicable Documents for Shore Platform Installations Table 2 ─ CDRLs

Table 3 ─ Electronic format of deliverables

List of Attachments

Attachment 1 - Cost Work Breakdown Structure

N00039-18-R-0060 5

1.0 SCOPE

1.1 Introduction

The Space and Naval Warfare Systems Command (SPAWAR) mission is to provide the warfighter with knowledge superiority by developing, delivering, and maintaining effective, capable and integrated command, control, communications, computer, intelligence, surveillance and reconnaissance (C4ISR) systems. For the purposes of this

Statement of Work (SOW), the term “C4ISR” encompasses enterprise information systems (EIS), information technology (IT) systems, electronic security systems (ESS), and other electronic systems under SPAWAR cognizance.

1.2 Description

This multiple award contract encompasses the C4ISR installation services for all shore based C4ISR and supporting systems, current and future, under the cognizance of

SPAWAR. The Contractor shall perform C4ISR installation services at shore facilities, on towers, piers, platforms, mobile systems, and special purpose vehicles. C4ISR installation services includes both decommissioning and modernization of existing facilities as well as installation design and installation of integrated C4ISR systems at new shore facilities.

While SPAWAR is acquiring installation services under this contract in order to support its mission to deliver information warfare capabilities, installations at shore facilities frequently require some minor construction work for successful installation and operation of the C4ISR systems. The vast majority of the required construction actions will be small scale and incidental to the installation of the C4ISR equipment/systems. Details on construction work activities are provided in Section 3.

The Contractor shall, in response to task orders issued under this contract, provide services that span the entire spectrum of requirements associated with delivery of fully operational and sustainable C4ISR systems to the warfighter. In response to task orders under this contract, the Contractor shall provide program and project management, engineering design, industrial work, troubleshooting, operational verification, end-user training and other installation services and material necessary to accomplish any

SPAWAR C4ISR maintenance, modernization, and new system installation.

The scope of this contract does not include the Navy Marine Corps Intranet (NMCI), the

Next Generation Enterprise Network (NGEN), or any future such contracts.

1.3 Web Tools

This contract shall maximize the use of web-enabled tools for management. This includes, but is not limited to: status reporting, financial reporting, task orders, and task order modifications. These actions shall be accomplished via posting to the SPAWAR

Fleet Readiness Directorate (FRD) Installation Office (FIO) web-enabled databases, hereafter referred to as “MODTracker.” The Contractor shall provide bid and cost data in a relational database where common Extract, Transform, and Load (ETL) tools can be utilized to load data into Government repositories. Installation projects within

N00039-18-R-0060 6

MODTracker are assigned a unique identification number, called a Job Identification

(JID) number. Task Orders may consist of a single or multiple JIDs. User accounts and detailed posting requirements will be provided by the Government upon award of the basic contract.

1.4 Locations

The Contractor will be required to conduct installations, decommissions, integration, and other technical/ engineering tasks at over 1000 shore facilities worldwide, including potentially hostile regions. The Government’s largest concentration areas for this contract are: Norfolk, VA; San Diego, CA; Puget Sound, WA; Pearl Harbor and Wahiawa, HI;

Yokosuka and Sasebo, Japan; Naples and Sigonella, Italy; Guam; Bahrain; and Djibouti.

2.0 APPLICABLE DOCUMENTS

2.1 General Application Rules and Principles

2.1.1 Sources of Documents

Web-enabled and SPAWAR document sources are provided in Table 1 in the “Source” column. Any additional references invoked under individual task orders will be provided by the Government.

2.1.2 Potential Conflicts

Where two requirements documents (listed in Table 1) are applicable and provide different, but compatible, requirements, unless otherwise stated in the contract or in the task order, the Contractor shall follow the more restrictive requirement so that the requirements of both documents are met. Where two requirements documents (listed in

Table 1) provide different, conflicting guidance, so that it is impossible to meet both requirements, the Contractor shall notify the On-site Lead, the Task Order Contracting

Officer’s Representative (COR), and the Ordering Officer. The Ordering Officer will determine which guidance shall be followed based upon what is in the best interest of the

Government.

2.1.3 Order of Precedence

The requirements of this SOW take precedence over the requirements of the referenced documents. Notwithstanding this order of precedence, nothing in this SOW shall be interpreted to allow any violation of an Occupational Safety and Health Administration

(OSHA) requirement or regulation, the National Electrical Code, or other Safety

Standards referenced in this SOW.

2.1.4 Potential Errors

If the Contractor is or becomes aware of an error in a referenced document that could result in cost increases or presents a risk to safety, the Contractor shall immediately notify the Ordering Officer, the On-site Government Representative (OSGR), Project

Engineer (PE), or another Government representative as identified on the MODTracker so that the situation can be investigated and any necessary action taken.

N00039-18-R-0060 7

2.2 Applicable Documents for Shore Installation Services

The Contractor shall perform all shore installation services in accordance with the requirements contained in the current version of the SPAWAR Shore Installation Process

Handbook (SIPH). All installation documentation, including Base Electronic Systems

Engineering Plans (BESEPs), Installation Design Plans (IDPs), and System Operational

Verification Test (SOVT) documents, delivered under this contract shall meet the technical and formatting requirements for these documents contained in the SIPH.

Installation practices shall conform to the requirements and standards discussed in

Appendix AC of the SIPH. For installations occurring at non-Navy facilities, the SIPH shall be used unless otherwise directed at the task order level. The Contractor shall adhere to the documents listed in Table 1 – Applicable Document for Shore Platform

Installations. The applicability of many of these documents is often covered in detail in

Appendix AC of the SIPH. Whenever one of these standards is applicable to an installation task, and the standard states that something “should” be done, the Contractor shall do what the standard says “should” be done unless specific permission not do so has been granted by the Ordering Officer or stated in the task order.

Table 1 ─ Applicable Documents for Shore Platform Installations

Item Document Number

(Note 1) Title Date

1 SPAWAR M-4720.1 Shore Installation Process Handbook Version 4.0 12-Nov-14

(Standards - 29 CFR), Part

Occupational Safety and Health Standards 26-Jul-16

(Standards -29 CFR), Part

Safety and Health Regulations for Construction 26-Jul-16

4 NFPA 51B

Standard for Fire Prevention During Welding, Cutting, and Other Hot Work

5 NFPA 70

National Fire Protection Association (NFPA), National Electrical Code

6 C2-2017 Institute of Electrical and Electronics Engineers

(IEEE) National Electrical Safety Code

7 NPFA 780

National Fire Protection Association, Standard for the Installation of Lightning Protection

Systems

UFC 3-560-01 (with

Change 5) Electrical Safety, O & M 14-Apr-16

UFC 3-600-01 (with

Change 3)

Unified Facilities Criteria, Fire Protection

Engineering for Facilities 1-Mar-13

FC 1-300-09N (with

Change 2)

Facilities Criteria, Navy and Marine Corps

Design Procedures 21-Aug-15

2015 International Building

Code 2015 International Building Code 30-May-14

12 EM 385-1-1

U.S. Army Corps of Engineers Safety and Health

Requirements Manual 30-Nov-14

OPNAVINST 5100.23G

(with change 1)

Navy Safety and Occupational Health Program

Manual 21-Jul-11

N00039-18-R-0060 8

MIL-STD-188-124B

through Change Notice 4

Military Standard, Grounding, Bonding, and

Shielding for Common Long Haul/Tactical

Communication Systems Including Ground

Based Communications-Electronics Facilities and Equipments

4-Apr-13

15 TIA-568.1-D

Commercial Building Telecommunications

Infrastructure Standard 9-Sep-15

TIA-568-C.0, Through

Addendum 2

Generic Telecommunications Cabling for

Customer Premises 14-Aug-12

SPAWAR IRD Standard, Version 2.0TIA-568.0-D

Revision D

Generic Telecommunications Cabling for

Customer Premises 15-Dec-15

18 ANSI/TIA-569-D Telecommunications Pathways and Spaces Apr-15

19 ANSI/TIA-942-A

Telecommunications Infrastructure Standard for

Data Centers Mar-14

20 ANSI/TIA-942-A-1

Telecommunications Infrastructure Standard for

Data Centers, Addendum 1 – Cabling Guidelines for Data Center Fabrics

Mar-13

21 TIA-758-B

Customer-owned Outside Plant

Telecommunications Infrastructure Standard Apr-12

22 TIA-590-A

Standard for Physical Location and Protection of

Below-Ground Fiber Optic Cable Plant Jan-97

23 TIA-607 Revision C Generic Telecommunications Bonding and

Grounding (Earthing) for Customer Premises 9-Nov-15

24 MIL-STD-1472G Human Engineering 11-Jan-12

ANSI/NECA/BICSI 568-

ANSI/NECA/BICSI 568-2006, Standard for

Installing Commercial Building

Telecommunications Cabling

26 36 C.F.R. Part 1194 Electronic and Information Technology

Accessibility Standards (Section 508) 21-Dec-00

27 SPAWAR M-4720.5A SPAWAR IRD Standard, Version 2.0 27-Mar-14

28 ANSI/ASSE A10.32-2012

Personal Fall Protection Used in Construction and Demolition Operations 12-Sep-12

29 ANSI/ASSE Z359.1-2007

Safety Requirements for Personal Fall Arrest

Systems, Subsystems and Components 25-Nov-07

30 SPAWAR M-3084.1

System Operational Verification Test (SOVT)

Preparation and Execution Guide (SPEG) for

Ship, Shore, and Submarine Installations, Version 1.4

3-Dec-08

NEMA Standards

Publication VE-2-2013 Cable Tray Installation Guidelines 8-Feb-16

NEMA Bulletin No. TCB

2-2012

Guidelines for the Selection and Installation of

Underground Nonmetallic Raceways 1-Sep-13

33 NFPA 70E Standard for Electrical Safety in the Workplace 2015

34 ANSI/TIA-526-14-C-2015

Optical Power Loss Measurement of Installed

Multimode Fiber Cable Plant; Modification of

IEC 61280-4-1 edition 2, Fiber-Optic

Communications Subsystem Test Procedures-

Part 4-1: Installed Cable Plant-Multimode

Attenuation Measurement

1-Apr-15

N00039-18-R-0060 9

35 TIA-526-7 Revision A

Measurement of Optical Power Loss of Installed

Single-Mode Fiber Cable Plant, Adoption of IEC

61280-4-2 edition 2: Fibre-Optic

Communications Subsystem Test Procedures –

Part 4-2: Installed Cable Plant – Single-Mode

Attenuation and Optical Return Loss

Measurement

29-Jul-15

Intelligence Community

Standard Number 705-1

Physical and Technical Standards for Sensitive

Compartmented Information Facilities 17-Sep-10

IC Tech Spec-for ICD/ICS

Technical Specifications for Construction and

Management of Sensitive Compartmented

Information Facilities, Version 1.2

23-Apr-12

38 TDMM 13

th Edition

BICSI Telecommunications Distribution

Methods Manual (TDMM) 13 th Edition

Jan-14

39 MIL-HDBK-419A

Grounding, Bonding, and Shielding for

Electronic Equipments and Facilities 20-Feb-14

40 SPAWAR M-9810.1 Technical Data Package (TDP) Standard V1.0 3-Jan-16

41 Executive Order 13556 Controlled Unclassified Information 4-Nov-10

42 Executive Order 13526 Classified National Security Information 29-Dec-09

43 DoDI 5220.22 DoD Instruction – National Industrial Security

Program 18-Mar-11

DoD 5220.22-M, Incorporating Change 2

DoD Manual – National Industry Security

Program Operating Manual (NISPOM) 18-May-16

DoDI 5200.02, Incorporating Change 1 DoD Personnel Security Program (PSP) 9-Sep-14

DoD 5200.2-R, through

Change 3 DoD Regulation – Personnel Security Program 23-Feb-96

47 DoDI 5200.01

DoD Information Security Program and

Protection of Sensitive Compartmented

Information (SCI)

21-Apr-16

48 DoDD 5205.02E DoD Operations Security (OPSEC) Program 20-Jun-12

49 DoD 5205.02-M DoD Operations Security (OPSEC) Program

Manual 3-Nov-08

50 DoDD 8140.01 Cyberspace Workforce Management 11-Aug-15

51 DoDI 8500.01 Cybersecurity 14-Mar-14

DoDI 8510.01, Incorporating Change 1

Risk Management Framework (RMF) for DoD

Information Technology (IT) 24-May-16

DoD 8570.01-M, through

Change 4

Information Assurance Workforce Improvement

Program 10-Nov-15

54 DoD 5200.01-M, Volume 1 DoD Information Security Program: Overview, Classification, and Declassification 24-Feb-12

55 FIPS PUB 201-2

Personal Identity Verification (PIV) of Federal

Employees and Contractors Aug-13

56 SECNAVINST 5510.30B

Department of the Navy (DON) Personnel

Security Program (PSP) Instruction 6-Oct-06

57 SECNAV M-5510.30

Department of the Navy Personnel Security

Program Jun-06

58 SECNAV M-5239.2

Department of the Navy Cyberspace Information

Technology and Cybersecurity Workforce

Management and Qualification Manual

Jun-16

N00039-18-R-0060 10

59 SECNAVINST 5239.3C Department of the Navy Cybersecurity Policy 2-May-16

60 SECNAVINST 5239.19

Department of the Navy Computer Network

Incident Response and Reporting Requirements 18-Mar-08

61 SECNAVINST 5239.20A

Department of the Navy Cyberspace Information

Technology and Cybersecurity Workforce

Management and Qualification

10-Feb-16

62 DON CIO Memorandum Acceptable Use of Department of the Navy

(DON) Information Technology (IT) 12-Feb-16

COMFLTCYBERCOM

MSG DTG 031442Z OCT

Navy Telecommunications Directive 10-11, OPNAV FORM 5239-14 /(REV 9 2011), System

Authorization Access Request Navy (SAAR-N)

3-Oct-11

IA PUB-5239-22/

September 2008 Protected Distribution System (PDS) Publication Sep-08

65 NIST SP 800-171

Protecting Controlled Unclassified Information in Nonfederal Information Systems and

Organizations

14-Jan-16

66 CNSSAM TEMPEST/1-13 RED/BLACK Installation Guidance 17-Jan-14

67 ISL 2016-02 May 21, 2016 Industrial Security Letter (ISL) Insider Threat

Minimum Standards for Contractors 21-May-16

68 SPAWARINST 3432.1 Operations Security (OPSEC) Policy 2-Feb-05

69 ANSI/EIA Standard 748C Earned Value Management System (EVMS)

70 EIA-649-1

Configuration Management Requirements for

Defense Contracts 20-Nov-14

NAVSEA Standard Item

009-04 Quality Management System; provide 01-Oct-17

72 ASQ/ANSI/ISO 9001:2015 Quality Management Systems - Requirements 15-Sep-15

NAVSEA SE000-00-EIM-

Navy Installation and Maintenance Book

(NIMB) Installation Standards 1-Sep-95

74 MIL-STD-1916

DOD Preferred Methods for Acceptance of

Product 5-Jun-14

75 NAVSUP Publication 409 MILSTRIP/MILSTRAP Desk Guide 9-May-

DoD 4000.25-2-M Change

MILSTRAP Manual 3-Oct-17

77 DoD Manual 4140.27 DoD Shelf-Life Management Program 6-Jul-16

78 FIPS PUB 140-2

Security Requirements for Cryptographic

Modules 3-Dec-02

79 DoDM-1000.13-M-V1 DoD Identification (ID) Cards: ID Card Life-

Cycle 23-Jan-14

80 DoDI 8582.01 Security of Unclassified DoD Information on

Non-DoD Information Systems 6-Jun-12

81 UFGS 01 35 29.13

Health, Safety, and Emergency Response

Procedures for Contaminated Sites 1-Nov-15

82 29 CFR 1915

Occupational Safety and Health Standards for

Shipyard Employment 1-Jul-17

NAVMC DIR 5100.8 Ch

Department of the Navy (DON)

Fall-Protection Guide Jul-2017

Notes:

N00039-18-R-0060 11

1. Document versions listed are the versions current when added to the SOW.

Unless otherwise specified, the Contractor shall comply with the version of the document that is in effect when the individual task order Requests for Proposal

(RFP) is issued.

2. Documents addressing security requirements to include, but not limited to handling and safeguarding of classified material, physical security, Operational

Security (OPSEC), Communications Security (COMSEC), Transmission Security

(TRANSEC), Information Security (INFOSEC), Telecommunications and

Electrical Machinery Protected from Emanations Security (TEMPEST), and

Cybersecurity provide mandatory requirements.

3.0 REQUIREMENTS

3.1 Program and Project Management

The Contractor’s Program Manager shall act as the single point of contact (POC) for the

FIO, senior Government managers, Contracting Officer, Ordering Officer, and COR for all matters involving contract performance. The Program Manager shall have overall responsibility for the successful execution of all work to be performed under the contract and will be considered by the Government to be fully accountable for all aspects of performance under the contract. The Program Manager shall have the requisite authority for full control over the resources necessary for contract performance and have authority to approve task order proposals in emergent situations. Additional duties and responsibilities include, but are not limited to:

a. participating in regular weekly status meetings with the FIO in person or by video teleconference (VTC);

b. participating in and supporting Program Management Reviews (PMRs);

c. providing input to budget estimates and developing installation concepts and plans for large scale or high visibility programs;

d. ensuring deliverables are submitted on time and are error-free;

e. providing bid and cost data in a relational database where common Extract, Transform, and Load (ETL) tools can be utilized to load data into Government repositories; and

f. keeping the Government apprised of any changes to the Contractor’s overall

Organizational structure to include Point-of-Contact information.

3.1.1 Contract Program Management Reviews (PMRs)

The Contractor shall participate in contract-level Program Management Reviews (PMRs) semi-annually, as required, which will be divided into a programmatic and a technical section. The Contractor shall brief manufacturing, engineering, logistics, reliability, quality assurance, subcontractor status, staffing, long range projections and other items as identified by the COR at all PMRs. The Government team will coordinate the PMR agenda, schedule, and location with the Contractor. The Program Manager and other

Contractor personnel shall be present at PMR as required to address the agenda. The

Contractor shall prepare Agendas (CDRL A004B) and Presentation Materials (CDRL

A004C) subject to the Ordering Officer’s approval and prepare and distribute Meeting

Minutes (CDRL A010).

N00039-18-R-0060 12

3.1.2 Project Management Plan (PMP)

The Contractor shall develop, maintain, and implement a Government approved Project

Management Plan (CDRL A004A) of the efforts required to complete execution of the installation project as required by the task order. The Project Management Plan (PMP) shall describe in detail all aspects of the project that will be monitored and controlled.

3.1.3 Project Integrated Master Schedule (IMS)

The Contractor shall develop, maintain, and deliver a logically networked Project

Integrated Master Schedule (IMS) (CDRL A030) where required by the Task Order. The

IMS shall contain the planned events and milestones, including all activities from task order award to task order completion, activity entrance and exit criteria. The IMS shall also reflect the tasks, dates (baseline, forecast, and actual), critical path, external and internal dependences and relationships necessary to support independent accurate forecasts of task order milestone delivery dates by both the Contractor and the

Government. Information provided in the Project Integrated Master Schedule (IMS)

(CDRL A030) shall be consistent with the information provided in the Earned Value

Management System, where applicable. While the Cost WBS in Attachment 1 is intended to provide standard reporting categories for cost reporting purposes, it is not intended to provide a template for scheduling purposes. However, the Project Integrated Master

Schedule (IMS) (CDRL A030) WBS shall have an additional column added to reference the appropriate Cost WBS element. Each Project Integrated Master Schedule (IMS)

(CDRL A030) item shall be at a low enough level to allow assignment of a single

Attachment 1 Cost WBS element so hours and costs as reflected in the Project Integrated

Master Schedule (IMS) (A030) can be easily exported/translated and used in the Cost

WBS Reports (i.e., the Monthly Actual Cost WBS Report (CDRL A028), and the Final

Actual Cost WBS Report (CDRL A029). In no instance will a single schedule item be tagged with more than one Attachment 1 Cost WBS element. In some circumstances schedule roll up work elements may not be assigned a Cost WBS element.

3.1.4 Daily Status Meetings

The Contractor shall attend daily status meetings in accordance with the SIPH and as specified in the individual Task Order, and present updates in a Daily Status Report

(CDRL A021).

3.1.5 Task Order Progress and Status Report

The Contractor shall submit a Task Order Progress and Status Report (CDRL A002) for tasks or subtasks as required by individual task orders. Topics will include but are not limited to: cost, resource loading, schedule, quality, and challenges.

3.1.6 Performance Report

The Contractor shall provide Performance Reports (CDRL A015) by Government JID as required by individual task orders. Where Performance Reports (CDRL A015) are required by the Task Order, the Contractor shall use the same applicable Work

Breakdown Structure (WBS) elements as those associated with the Project Integrated

Master Schedule (CDRL A030) and the Shore Production Schedule (CDRL A018) for preparing the Performance Reports, unless otherwise required by the Task Order. If the

N00039-18-R-0060 13

Task Order is re-baselined through the approval of change orders, then the Performance

Report (CDRL A015) shall use the new approved WBS amounts.

3.1.7 Earned Value Management (EVM)

The Contractor shall implement an Earned Value Management (EVM) Integrated

Program Management Report (IPMR) (CDRL A024) where individual task orders invoke

EVM. When EVM is required by a task order, DFARS 252.234-7001will be incorporated into the Task Order RFP and, per DFARS 252.234-7001, a comprehensive

Earned Value Management System (EVMS) compliant with American National

Standards Institute /Electronic Industries Association Standard 748-C, EVMS (ANSI/EIA

– 748C) is required. The Contractor shall follow the requirements set forth in the following subsections below. Where EVM is required, the EVMS shall:

a. Relate resource planning to schedules and technical performance requirements

b. Integrate technical performance, cost, schedule, and risk management

c. Provide the integrated management information to plan the timely performance of work, budget resources, account for costs, and measure actual performance against plans and by Work Breakdown Structure (WBS) element

d. Have the capability to predict, isolate, and identify variances and the factors causing the variances

3.1.7.1 Use of EVMS Information

The Contractor shall use the EVMS information to develop alternative solutions and implement corrective action. The Contractor shall use the EVMS information to generate progress and financial reports to analyze and track scheduled versus actual events, including, but not limited to cost analysis and status by task order. The EVMS reports shall identify any issues and risk elements, and shall include recommended methods to mitigate those risks. The Contractor shall produce a Performance Measurement Baseline

(PMB) that integrates contract work scope and schedule and budget to achieve a realistic, executable contract plan.

3.1.7.2 Contractor Integrated Performance Management

The Contractor shall use its existing, internal Integrated Program Management System

(IPMS) to plan, schedule, budget, monitor, manage, and report cost, schedule, and technical status applicable to the contract. The Contractor's system shall be compliant with the Industry Guidelines delineated in the ANSI/EIA-748C, the general provisions of the contract, and this SOW.

3.1.7.2.1 Integrated Subcontract Management and Reporting

The EVMS requirement shall be flowed down to subcontractors in accordance with

DFARS 252.234-7001. The prime Contractor and the Government shall agree on the subcontractors or the subcontracted effort selected for application of the EVMS requirement. Any subcontractor with a contractual flow down requirement for EVM shall be included in the Integrated Baseline Review (IBR) process. A separate IBR may be conducted at the subcontractor’s facility, in which case the prime Contractor shall take the lead in conducting the IBR, with active Government participation. On subcontracts where EVM and IMS requirements are not flowed down, subcontracted scope and

N00039-18-R-0060 14 performance information shall be incorporated/integrated into and reported via the prime’s Contractor's integrated performance management system and EVMS Integrated

Program Management Report (IPMR) (CDRL A024).

3.1.7.2.2 Integrated Baseline Review (IBR)

The Contractor shall participate and assist the Government program manager and technical staff in conducting IBRs to assess the realism and inherent risks in the

Contractor's integrated PMB plan. The Contractor shall present the contents and underlying/ supporting assumptions of its initial PMB to Government representatives via an IBR to be held at the Contractor’s facilities. The initial IBR shall be conducted as soon as practicable after the Task Order is awarded but not later than 90 days after Task Order award.

Subsequent IBRs shall be conducted, as required, throughout the life of the contract following initiation of the Task Order, including undefinitized contract actions, contract modifications, major milestone events, major changes to the baseline, or re-planning. The scope of the IBRs shall be tailored to the nature of the work content and/or dollar value issued with the Task Order, and the IBR shall be conducted within a reasonable time.

Each IBR will verify that the Contractor has established and is maintaining a reliable

PMB that includes the entire contract scope of work; is consistent with contract cost targets and schedule requirements; has adequate resources assigned; and uses effective

Earned Value (EV) techniques/methods to accurately reflect technical achievement/progress. Each IBR will also record any indications that effective EVM is not being used. IBR planning, preparation and conduct details will be discussed and finalized on a case-by-case basis with the issuance of the Task Order.

The prime Contractor shall seek Government concurrence on:

The IBR scope and approach, i.e., Contract Line Item Number

(CLIN)/Performance Work Schedule (PWS) scope coverage, dates, duration, depth of the event, and preliminary IBR agenda.

IBR entrance and exit criteria. The government program office Lead will take lead roles in assessing Contractor IBR readiness.

If the scope of the Task Order and dollar value warrant, pre-IBR support requirements include:

- Advance IBR artifacts (EVMS output) submittal requirements and IBR schedule Integrated Baseline Review (CDRL A025).

- Contractor participation in Government pre-IBR Workshop activities (e.g., vendor may be asked to send 1-3 representatives (i.e., Program Manager

(PM), System Engineering (SE) Lead, Scheduler) to a Government pre-

IBR workshop to provide 2-4 hours of PMB, IMS, IBR artifact overview and data traces.

During contract performance, the Contractor shall provide ongoing access to its records and data that underlie and support the PMB and cost and schedule data reported.

3.1.7.2.3 Over Target Baseline (OTB)/Over Target Schedule (OTS)/ Restructure

N00039-18-R-0060 15

During performance, the Contractor may conclude the baseline no longer represents a realistic plan in terms of budget/schedule execution. In the event the Contractor determines an Over Target Baseline (OTB)/Over Target Schedule (OTS)/Restructuring action is necessary, the Contractor shall obtain customer approval prior to implementing an OTB/OTS/Restructuring action. The request shall also include detailed implementation procedures as well as an implementation timeframe. The Contractor shall not implement the OTB/OTS/Restructuring prior to receiving written approval of their

Recovery Plan from the Ordering Officer.

3.1.7.2.4 Integrated Master Schedule (IMS) (IPMR Format 6)

The Contractor shall develop, maintain, and deliver a logically networked IMS in accordance with the DoD Integrated Master Plan and Integrated Master Schedule

Preparation and User Guide, DI-MGMT-81861, Format 6, and tailoring instructions provided in CDRL A024, Integrated Program Management Report (IPMR). The IMS shall contain the planned events and milestones, all activities from task order award to task order completion, activity entrance and exit criteria, and risks/risk mitigation activities identified and documented in the Contractor’s Risk Management Plan (RMP).

The IMS shall also reflect the tasks, dates (baseline, forecast, and actual), external and internal dependences and relationships necessary to support independent accurate forecasts of task order milestone delivery dates by both the Contractor and the

Government. The IMS shall be developed, maintained and reported consistently and in conjunction with the Contract Work Breakdown Structure (CWBS) and the IPMR. The

Contractor shall support teleconferences, as needed, to discuss IMS progress and issues and shall be available for review at all Government meetings. (CDRL A024)

3.1.7.2.5 Schedule Analysis/Schedule Risk Assessment (SRA)

A Schedule Analysis section shall be included with the monthly IPMR deliverable as part of Format 5 of the IPMR. This section shall be in accordance with DI-MGMT-81861 and tailoring instructions provided in CDRL A024, Integrated Program Management

Report (IPMR). Schedule Risk Assessment shall be conducted quarterly as outlined in

CDRL A024.

3.1.7.2.6 Contract Work Breakdown Structure (CWBS)

Where EVMS is required by a Task Order, the Contractor shall develop an extended

CWBS and CWBS dictionary in accordance with the guidelines in DI-MGMT-81334D.

The Contractor’s organizational entity responsible for systems engineering shall analyze the requirements specified in the Task Order and translate them into a Contract Work

Breakdown Structure (CWBS) (CDRL A026) representing the products and services that comprise the entire work effort commensurate with the contract requirements to a level providing adequate internal management, surveillance, and performance measurement.

Information provided in the CWBS shall be consistent with the information provided in the Earned Value Management System, where applicable. While the Cost WBS in

Attachment 1 is intended to provide standard reporting categories for cost reporting purposes, it is not intended to provide a template for CWBS generation purposes.

However, the CWBS shall have an additional column added to reference the appropriate

Cost WBS element. Each CWBS item shall be at a low enough level to allow assignment of a single Attachment 1 Cost WBS element. In no instance will a single CWBS item be

N00039-18-R-0060 16 tagged with more than one Attachment 1 Cost WBS element. In some circumstances

CWBS roll up work elements may not be assigned a Cost WBS element.

The Contractor shall use the CWBS as the primary framework for task order planning, budgeting and reporting of cost, schedule and technical performance status to the

Government. The Contractor shall maintain, update and deliver the CWBS and the

CWBS Dictionary during the execution of the contract in accordance with DI-MGMT-

81334D and the tailoring instructions provided in Contract Work Breakdown Structure

(CWBS) (CDRL A026). Changes to the CWBS and/or associated CWBS Dictionary definitions at any reporting level require approval of the Government.

3.1.7.2.7 Contract Fund Status Report (CFSR)

The Contractor shall submit a quarterly Contract Fund Status Report (CFSR) (CDRL

A027) as required by Task Order. The CFSR will be used by the Contractor and the

Government to update and forecast task order funds requirements; to plan and communicate funding changes; to develop funding requirements for approved efforts; to determine funds in excess of task order needs and available for de-obligation; and to obtain rough estimates of termination liability and open commitment costs on all cost reimbursable contract line items. The CFSR shall be prepared by JID, with a rollup to the task order level. All data shall be time phased and displayed in conjunction with

Government fiscal years.

3.1.8 Monthly Actual Cost Work Breakdown Structure (WBS) Report

The Contractor shall provide a Monthly Actual Cost WBS Report (CDRL A028) as required by individual task orders. Beginning at the end of the first month after task order award, the Contractor shall initiate monthly reporting of accumulative labor hours expended and actual cost expenditures (inclusive of changes and modifications) attributed to each applicable WBS element shown in Table 1, “Cost WBS Hierarchy” of

Attachment 1, “Cost Work Breakdown Structure,” for labor, material, travel, and ODCs for each JID. The Contractor shall use all applicable elements specified by the individual task order. The Contractor shall also provide cost basis details of actual costs/labor hours attributed to each applicable WBS element for labor, material, ODCs and travel.

3.1.9 Change Order Request Notification (CORN) Process

The purpose of the Change Order Request Notification (CORN) (CDRL A003A) process is to provide prompt notification to the Government of any problems or conditions that are expected to cause a change to the cost or requirements of the work covered by the

Task Order. The Contractor shall initiate the CORN process by completing an “Info

CORN” in accordance with CDRL A003A. This shall be accomplished on the

MODTracker within two (2) business days of becoming aware of the problem or condition. The Contractor shall enter a description of the problem or condition found on the CORN form and a proposed solution, including a Rough Order of Magnitude (ROM) estimate for any additional work to be performed. The Contractor shall notify the OSGR, PE, or another Government representative as identified on the MODTracker of the “Info

CORN” prior to submission. The “Info CORN” will be reviewed by the appropriate

Government Representatives for comments and concurrence.

N00039-18-R-0060 17

3.1.9.1 Following coordination and concurrence by the appropriate Government

Representatives, the Contractor shall update the CORN form as necessary and shall upload a detailed description of the problem, a proposed detailed solution and detailed cost proposal (including specific labor categories) attributed to each applicable WBS element shown in Table 1, of Attachment 1, for labor, material, travel, and ODCs for each JID, and scheduling change estimates to the MODTracker. This “Cost CORN” with the detailed information specified above shall be uploaded to the MODTracker within five (5) business days of Government approval of the “Info CORN.” For each CORN that exceeds the simplified acquisition threshold, the Contractor shall certify, through the use of a “certificate of cost or pricing data” that the request for approval is made in good faith, and that the supporting data are accurate and complete to the best of the

Contractor’s knowledge and belief, as required by DFARS 252.243-7002, Requests for

Equitable Adjustment. This certificate shall be uploaded to the MODTracker. The

Contractor shall notify the cognizant Ordering Officer (from the cognizant task order contracting office) or the Contracting Officer who issued (or is assigned to) the original task order via email. The Contractor shall use the MODTracker to provide this email notification whenever this capability is available from the website. The Government will review the submitted documents, and if the Government review indicates that the CORN form contains insufficient technical information or supporting documentation, the

Government will notify the Contractor POCs identified on the CORN form via email.

The Contractor shall update the CORN form to provide any additional information requested within two (2) business days of receipt of the notice.

3.1.9.2 If the CORN is approved, the Ordering Officer will authorize the Contractor to proceed with the work by issuing an Authorization to Proceed by email. Details on this process will be provided on the MODTracker. If the CORN is rejected, the Government will notify the Contractor.

3.1.9.3 The Contractor shall submit a request for a CORN modification no later than thirty (30) days after receiving the Ordering Officer authorization to proceed. Extensions of this deadline or exceptions to this requirement shall be coordinated in advance of the deadline with the Ordering Officer.

3.1.10 Meetings

The Contractor shall attend installation project related meetings and provide Meeting

Minutes (CDRL A010) as required by Task Order, or as conditions/circumstances require.

3.1.11 Trip Reports

The Contractor shall prepare a Trip Report (CDRL A004D) as required by the Task

Order. Where required by the Task Order, the trip report shall provide a detailed record of events that occurred, to include but not limited to, meetings attended, meeting results, project related information obtained, and actions assigned.

N00039-18-R-0060 18

3.1.12 Technical Reports

The Contractor shall provide technical reports, studies, white papers, technical presentations, comments to technical documents, recommendations as required by Task

Order. (CDRL A003B)

3.1.13 Production Schedule/POA&M

The Contractor shall provide a Shore Production Schedule (CDRL A018) for each JID that lists all tasks identified in Appendix H of the SIPH that apply to the task order. In addition, the following activities shall be included as separate sub-tasks for the purpose of production scheduling only under the “On-Site Installation” task, whenever they apply:

a. Cabinet Mounting and Grounding

b. Antenna Mounting and Grounding

c. Electrical Wiring Pathway Installation

d. Inside Plant Cable Pathway Installation

e. Outside Plant Cable Pathway Installation

f. Electrical Wiring Installation

g. Signal Cabling Installation

h. Equipment Installation

Information provided in the Production Schedule/POA&M shall be consistent with the information provided in the Earned Value Management System, where applicable. While the Cost WBS in Attachment 1 is intended to provide standard reporting categories for cost reporting purposes, it is not intended to provide a template for scheduling purposes.

However, the Production Schedule/POA&M WBS shall have an additional column added to reference the appropriate Cost WBS element. Each Production Schedule/POA&M item shall be at a low enough level to allow assignment of a single Attachment 1 Cost WBS element so hours and costs as reflected in the POA&M can be easily exported/translated and used in the Cost WBS Reports (i.e., the Monthly Actual Cost WBS Report (CDRL

A028), and the Final Actual Cost WBS Report (CDRL A029). In no instance will a single schedule item be tagged with more than one Attachment 1 Cost WBS element. In some circumstances schedule roll up work elements may not be assigned a Cost WBS element.

3.1.14 Electronic Contractor Manpower Reporting

The Contractor shall report ALL Contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the Navy via a secure data collection site. The Contractor shall be required to completely fill in all required data fields using the following web address https://doncmra.dmdc.osd.mil/.

Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than

October 31 of each calendar year. Contractors may direct questions to the help desk, linked at https://doncmra.dmdc.osd.mil/.

https://doncmra.dmdc.osd.mil/ https://doncmra.dmdc.osd.mil/

N00039-18-R-0060 19

3.1.15 Project Integrated Master Plan

The Contractor shall develop, maintain, and deliver a logically networked Project

Integrated Master Plan (IMP) (CDRL A022) where required by the Task Order. The IMP shall provide an overarching framework against which all work is accomplished.

3.2 Systems Engineering

3.2.1 Configuration Management

The Contractor shall apply engineering analytical disciplines to identify, document, and verify that functional, performance, and physical characteristics of systems, to control changes and non-conformance, and to track actual configurations of systems and platforms. The Contractor shall provide a Configuration Management Plan (CDRL A031) as outlined in EIA-649-1.

3.2.2 Cybersecurity

Cybersecurity is defined as prevention of damage to, protection of, and restoration of computers, electronic communications systems, electronic communications services, wire communication, and electronic communication, including information contained therein, to ensure its availability, integrity, authentication, confidentiality, and nonrepudiation.

Contractor personnel shall perform tasks to ensure Navy applications, systems, and networks satisfy Federal/DoD/DON/Navy cybersecurity requirements.

3.2.2.1 Cyber IT and Cybersecurity Personnel

(a) The Cyberspace workforce elements addressed include contractors performing functions in designated Cyber IT positions and Cybersecurity positions. In accordance with DFARS Subpart 5239.71, DoDD 8140.01, SECNAVINST 5239.20A, and SECNAV

M-5239.2, Contractor personnel performing cybersecurity functions shall meet all cybersecurity training, certification, and tracking requirements as cited in DoD 8570.01-

M prior to accessing DoD information systems. Proposed Contractor Cyber IT and cybersecurity personnel shall be appropriately qualified prior to the start of the contract performance period or before assignment to the contract during the course of the performance period.

(b) The Contractor shall be responsible for identifying, tracking and reporting cybersecurity personnel, also known as Cybersecurity Workforce (CSWF) and Cyber IT workforce personnel. Although the minimum frequency of reporting is monthly, the

Task Order can require additional updates at any time.

(c) Contractors that access Navy IT shall also follow guidelines and provisions documented in Navy Telecommunications Directive (NTD 10-11) and are required to complete a System Authorization Access Request (SAAR) – Navy form as documented in Section 7.4.2b.

(d) Contractor personnel with privileged access will be required to acknowledge special responsibilities with a Privileged Access Agreement (PAA) in accordance with

SECNAVINST 5239.20A

N00039-18-R-0060 20

3.2.2.2 Cybersecurity Workforce (CSWF) Report

DoD 8570.01-M and DFARS PGI 239.7102-3 have promulgated that Contractor personnel shall have documented current cybersecurity certification status within their contract. In accordance with clause 252.239-7001, Contractor personnel accessing information systems shall meet all Information Assurance (IA) training, certification, and tracking requirements prior to accessing DoD information systems. Personnel tracking information, which includes subcontractor personnel, shall be included in the Monthly

Contract Status Report (CDRL A023B) and the Quality Assurance Workbook (CDRL

A011C).

3.2.3 Design, Integration, Configuration or Installation of Hardware and Software

The Contractor shall ensure any equipment/system installed or integrated into Navy platform will meet the cybersecurity requirements as specified under DoDI 8500.01. The

Contractor shall ensure that any design change, integration change, configuration change, or installation of hardware and software is in accordance with established

DoD/DON/Navy cyber directives and does not violate the terms and conditions of the accreditation/authorization issued by the appropriate Accreditation/Authorization official.

Contractors that access Navy IT are also required to follow the provisions contained in

DON CIO Memorandum: Acceptable Use of Department of the Navy Information

Technology (IT) dtd 12 Feb 16. Use of blacklisted software is specifically prohibited and only software that is registered in DON Application and Database Management System

(DADMS) and is Functional Area Manager (FAM) approved can be used as documented in Section 3.12.2.1. Procurement and installation of software governed by DON

Enterprise License Agreements (ELAs) – Microsoft, Oracle, Cisco, Axway, Symantec, ActivIdentity, VMware, Red Hat, NetApp, and EMC shall be in accordance with DON

CIO Policy and DON ELAs awarded.

3.3 Pre-Installation

3.3.1 Site Surveys

The Contractor shall conduct inspections of shore platforms identified by Task Order to validate the location and configuration for an equipment/system installation and any site or platform preparation requirements. The Contractor shall be capable of gathering all pertinent environmental, security access, pre-boarding training, engineering, configuration, and design information relevant to site conditions, analyzing the collected data, performing necessary calculations to make technical recommendations, and preparing technical reports and documentation (CDRL A003C) (such as Site Survey In-

Briefs and Out-Briefs, and Site Survey Reports) for a specific installation or a group of installations. The Contractor shall assess potential impacts to cost, schedule and performance and communicate recommendations to mitigate discoveries. The

Contractor shall conduct Site Surveys of shore installation sites in accordance with the requirements in the SIPH.

3.3.2 Shore Design Documentation

The Contractor shall provide shore Installation Design Documentation that meets the applicable requirements of the current version of the SIPH or the SPAWAR Installation

N00039-18-R-0060 21

Requirements Drawings (IRD) Standard, whichever is applicable. Installation Design

Documentation includes, but is not limited to:

a. Base Electronic System Engineering Plans (BESEPs) (CDRL A009A)

b. Training System Installation Plans (TSIPs) (CDRL A009B)

c. Installation Requirements Drawings (IRDs) (CDRL A005A)

d. Site Preparation Specifications (CDRL A020)

e. Installation Design Plans (IDPs) (CDRL A005B)

f. IDP Quality Assurance Checklists (CDRL A011E)

g. On-The-Job Training (OJT) Materials (CDRL A003B)

3.3.3 System Operational Verification Test (SOVT)…