CERS_PWS_Attachment_1_v1.0_022713.pdf

Consolidated Emergency Response System Performance Work Statement Version 1.0; 27 February 2013

For Official Use Only

Source Selection Sensitive See FAR 3.104

MARINE CORPS SYSTEMS COMMAND

PROGRAM MANAGER

INFORMATION SYSTEMS & INFRASTRUCTURE

Consolidated Emergency Response System

Dispatch, Alerting and Records Management

Performance Work Statement

Prepared by:

UNITED STATES MARINE CORPS

Marine Corps Systems Command

Information Systems and Infrastructure

Emergency Response Systems

Consolidated Emergency Response System

VERSION 1.0

27 February 2013 i

For Official Use Only

Source Selection Sensitive See FAR 3.104

Table of Contents

1 Introduction

1.1 Background

1.2 Scope

1.3 Place of Performance

2 Specific Tasks

2.1 Performance Objectives

2.2 Performance Requirements

2.3 Capability Requirements

2.3.1 Computer Aided Dispatch

2.3.2 Fire Station Alerting

2.3.3 Mobile Data Computer

2.3.4 Law Enforcement Records Management System

2.3.5 Uninterrupted Power Supply System – Common Equipment

2.4 Interface Requirements

2.4.1 Enhanced 911 Customer Premise Equipment

2.4.2 Logging and Recording

2.4.3 Dispatch Local Area Network

2.4.4 Time Synchronization

2.4.5 Geographic Information System Data Integration

2.4.6 Fire and Emergency Services Records Management System

2.4.7 Enterprise Land Mobile Radio Dispatch Console

2.4.8 Fire Alarm Systems

2.4.9 Uninterrupted Power Supply System – Workstation

2.4.10 Workstation Area

2.4.11 Administration and Maintenance Workstation

3 Program Management

3.1 Project Planning

3.2 Quality Control

3.3 Systems Engineering Management Plan

3.4 Configuration Management Plan

3.5 Post Award Conference

3.6 Weekly Meetings and Status Reports

4 Engineering Document Package

4.1 System-Level Engineering Document Package

4.2 Location-Specific Engineering Document Package

5 Cyber Security

5.1 General Cyber Security

5.2 System Assurance

5.3 Certification & Accreditation

ii

For Official Use Only

Source Selection Sensitive See FAR 3.104

5.4 Secure System Design

5.5 Secure Maintenance and Administration

5.6 Information Assurance Personnel

6 Coordinating Performance

6.1 Pre-Fielding Coordination Visit

6.1.1 Site Specifications

6.1.2 Site Preparation

6.2 Integration and Cutover

6.2.1 Government Fielding Conference

6.2.2 Removal of Existing Equipment

6.2.3 Clean Up

7 Engineering

7.1 System Engineering Technical Reviews

7.1.1 System Requirements Review

7.1.2 Non-Developmental Item Integration Review

7.1.3 Test Readiness Review

7.1.4 System Verification Review

7.2 Testing

7.2.1 CERS DAR Test Environment

7.2.2 Enhanced 911 Test Article Acceptance

7.2.3 Enterprise Land Mobile Radio Test Article

7.2.4 Functional Verification Test

7.2.5 Functional Configuration Audit

7.2.6 Product Acceptance Test

7.2.7 System Qualification Testing

7.2.8 Physical Configuration Audit

7.2.9 Site Acceptance

7.2.10 Field User Evaluation

8 Maintenance

8.1 Warranty

8.2 Failure Reporting, Analysis, and Corrective Action System

8.3 Sustainment Plan

8.4 Diminishing Manufacturing Sources and Materiel Shortages (DMSMS) Planning

8.5 Item Unique Identification (IUID)

9 Training

9.1 Training Plan

9.2 Training Sessions

9.3 Training Materials

10 Government Furnished Materials

10.1 Government Furnished Information

10.2 Government Furnished Equipment

iii

For Official Use Only

Source Selection Sensitive See FAR 3.104

11 Special Considerations

11.1 Public Trust Access to Information

11.2 Security Inspections

11.3 Physical Security

11.4 Photography Recording Control

11.5 Prohibited Items

11.6 Escorting Policy

11.7 Non-Personal Services

11.8 Business Relations

11.9 Contract Administration and Management

11.9.1 Labor Hours Reporting

11.9.2 Contract Management

11.9.3 Contract Administration

11.9.4 Subcontract Management

11.10 Personnel Administration

11.11 Travel

APPENDIX A. Document Deliverable Schedule

APPENDIX B. References

APPENDIX C. Definitions and Acronyms

APPENDIX D. CERS System Design Specification and Requirements Traceability

Matrix 56

APPENDIX E. CERS Enhanced 911 System Definition

APPENDIX F. Enterprise Land Mobile Radio Interface Description

APPENDIX G. EMC2 Background iv

For Official Use Only

Source Selection Sensitive See FAR 3.104

List of Figures

Figure 1-1 CERS DAR Relationships

Figure 7-1 Systems Engineering Technical Review Alignment

List of Tables

Table 1-1 CERS E911/ Dispatch Subsystems

Table 1-2 Places of Performance

Table 2-1 Quantity of Fire Stations per Installation

Table 9-1 Estimated Student Quantities

Table 11-1 Deliverable Schedule

For Official Use Only

Source Selection Sensitive See FAR 3.104

1 Introduction

This Performance Work Statement (PWS) identifies the design, engineering, program management, preparation, installation, configuration/optimization, system certification support, testing, documentation, training, and sustainment tasks required to implement the Consolidated

Emergency Response System (CERS) for the United States Marine Corps (USMC). This effort shall deliver a solution that provides reliable emergency dispatching and alerting capability for

First Responders at USMC installations identified in this PWS. This document summarizes the current operations and supporting technology for the USMC’s CERS as well as future state goals and objectives. This document represents the needs of the Emergency Management Command and Coordination (EMC2) initiative for installation-specific emergency dispatch and alerting.

This PWS is an overview that, combined with EMC2 Concept of Operations (CONOPS), represents the CERS program objectives.

CERS shall comply with applicable Department of Defense (DoD) Information Assurance (IA), interoperability, safety, and spectrum certification requirements for non-tactical systems. The

CERS components installed by the contractor shall not degrade current functionality of the existing dispatch capability where they exist and shall require minimal reconfiguration for future

Next Generation 911 migration.

1.1 Background

Marine Corps Systems Command (MARCORSYSCOM), Product Manager, Emergency

Response Systems (PdM ERS) has been tasked with deploying CERS aboard installations worldwide. CERS is being implemented as part of the EMC2 effort to upgrade current USMC emergency dispatch and communications capabilities. Appendix G provides a detailed background of EMC2. CERS will bring base emergency response systems into compliance with the Secretary of Defense (SecDef) Memorandum in reference to the Fort Hood Task Force recommendations and Secretary of the Navy Policy on Emergency Calls. CERS will provide

Enhanced 911 (E911) capabilities along with the Computer Aided Dispatch (CAD) of emergency personnel and First Responders.

CERS provides Installation emergency response command and coordination using wired and wireless communications paths. CERS is the subset of EMC2 capabilities necessary to coordinate Installation-organic First Responder emergency and day-to-day operations. This encompasses “First Responders: Firefighters, Law Enforcement (LE) and/or security personnel, Emergency Medical Technicians, and Explosive Ordnance Disposal personnel who provide the initial, immediate response to an all-hazards incident.”

CERS supports all dispatcher and First Responder information requirements regarding public safety and preservation of property within the base perimeter; any off-base military controlled and operated housing and training areas and other off-base areas of responsibility.

The USMC supports police, fire and Emergency Medical Service (EMS) public safety operations at fifteen installations in the Continental United States (CONUS) and four Outside CONUS

(OCONUS). Each installation operates independently and is autonomous of the others and provides First Responder fire and EMS and public safety LE services to a combined population

For Official Use Only

Source Selection Sensitive See FAR 3.104 of nearly 300,000 active duty military, civilians and dependents. Detailed base profiles are provided in the separate installation site survey extracts.

1.2 Scope

CERS shall be deployed as a turnkey solution in a two-phased approach. The CERS

E911contract has already been awarded and will deploy components to support E911 functionality (e.g., Local Area Network (LAN), furniture, E911 console). This PWS establishes and defines the requirements for the remaining capabilities of CERS including a turnkey, Commercial Off-The-Shelf (COTS) based, CAD, integrated mapping, FSA, MDCs, LE Records

Management System (RMS), Fire and Emergency Services (F&ES) RMS interface, associated

Customer Premise Equipment (CPE), system installation, integration and implementation, system warranty and support, and system operator training. Table 1-1 outlines those components relevant to CERS E911 and this PWS called CERS Dispatch, Alerting and Records Management

(DAR). CERS E911 is not within scope of this PWS and information is provided for reference purposes only. Successful implementation of CERS DAR is dependent upon its effective integration and interface capabilities with CERS E911, Enterprise Land Mobile Radio (E-LMR), and Base Telecommunications Infrastructure (BTI). Figure 1-1 is a graphic representation of this critical relationship between the independent contracting actions.

The USMC seeks a balance between mature and state-of-the-art technology that enables employment of solutions that will prolong the life of the new system. With this in mind, the

USMC envisions that the CERS DAR will be based upon proven technology derived from current industry standards.

Figure 1-1 CERS DAR Relationships

Table 1-1 depicts the subsystems for both CERS E911 and DAR.

For Official Use Only

Source Selection Sensitive See FAR 3.104

Table 1-1 CERS E911/ Dispatch Subsystems

CERS E911 (Appendix E) CERS DAR (PWS Scope)

E911 CPE CAD

Logging and Recording Emergency Medical Dispatch (EMD)

Master Street Address Guide (MSAG)/Geospatial Data MDCs

Time Sync Subsystem AVL/PLI Interface

Dispatch LAN FSA

Workspace and System Furniture Emergency Reporting (Fire & EMS)

Uninterruptable Power Supply (UPS) RMS

1.3 Place of Performance

The contractor shall be required to work at locations within the Continental United States

(CONUS) as well as locations Outside CONUS (OCONUS). The required places of performance are represented in Table 1-2. Other places of performance may be required for additional DoD sites both CONUS and OCONUS in support of fire, emergency medical, and law enforcement dispatch and alerting operations.

Table 1-2 Places of Performance

Marine Corps Installations

MCB Camp Butler, Okinawa, Japan

MCB Camp Fuji, Japan

MCAS Iwakuni, Japan

MCB Quantico, Virginia USA

MCB Camp Lejeune/ MCAS New River, North Carolina USA

MCAS Cherry Point, North Carolina USA

MCAS Beaufort, South Carolina USA

MCRD Parris Island, South Carolina USA

MCLB Albany, Georgia USA

MCB Camp Pendleton, California USA

MCAS Miramar, California USA

MCAGCC Twenty-nine Palms, California USA

MCLB Barstow, California USA

MCAS Yuma, Arizona USA

MCMWTC Bridgeport, California USA

MCRD San Diego, California USA

MCSF Blount Island Command, Jacksonville, Florida USA

MCB Hawaii, USA

Guam, Marina Islands USA Territory

Camp Mu Juk, South Korea

Marine Barracks Washington, DC/Joint Base Myer-Henderson Hall USA

For Official Use Only

Source Selection Sensitive See FAR 3.104

2 Specific Tasks

2.1 Performance Objectives

The new system shall require functional integration with CERS E911 components including the

E911 Automatic Number Identification (ANI)/Automatic Location Identification (ALI), Dispatch LAN and the time source for synchronization. CERS DAR shall require integration with a Government provided Public Safety Network (PSNet) for a required Wide Area Network

(WAN) connectivity. The contractor shall provide a system that will advance the overall mission, goals, and objectives of the USMC by making public safety personnel more effective in preventing, combating, and responding to public safety matters. The following describes the performance objectives for CERS DAR:

To implement, in a turnkey fashion, CERS DAR systems at each specified location to meet the threshold requirements identified in Appendix D.

Integrate CERS DAR systems with CERS E911 systems, including:

- Dispatch LAN

- Time synchronization

- E911 CPE for ANI/ALI

- Logging and Recording

Integrate CERS DAR systems with E-LMR audio and data sources for Dispatch Radio consoles, Automatic Vehicle Location (AVL) and Position Location Information (PLI).

Incorporate Government Geospatial data and updates to present integrated mapping.

Provide New Equipment Training (NET), functional training (where dispatch capability has not previously existed), system administration training, and preventative maintenance training for provided systems.

Satisfy applicable DoD and commercial standards for installation, commissioning, physical security, and cyber security of the delivered system.

Provide system warranty, software upgrades, and support services for two (2) years for each delivered system, from the time of Site Acceptance.

Provide CERS support services to include CERS E911 systems.

2.2 Performance Requirements

The contractor shall Engineer, Furnish, Install, Secure and Test (EFIST) and make operational a fully functional, turnkey, CERS DAR system at each installation identified in a Delivery Order.

The implementation shall include configuration, installation, applications, data transfer/migration

(to include existing system records) and entry, hardware, software, ancillary equipment, parts, training, and material for identified services and requirements. The system shall be capable of performing those functions and operating standards identified in the attached System Design

Specification (SDS), Appendix D. The contractor shall EFIST and make operational any ancillary equipment required to support this effort (such as cables, firmware, interfaces, wiring blocks, applications, and racking) to provide a complete solution.

For Official Use Only

Source Selection Sensitive See FAR 3.104

The contractor shall integrate with the existing CERS E911 system at each installation to the maximum extent practical based upon the planned solution for each location. The Government will furnish an E911 CPE test article for integration planning purposes. If integration with the existing CERS E911 systems is not practical, the contractor shall provide their justification to the

Government in the Pre-Fielding Coordination Visit (PCV) Report identified in Section 6.1 of this

PWS.

2.3 Capability Requirements

There are four major capabilities that shall be provided with named commercial components and a strategy to integrate them into a single coherent system:

CAD with Integrated Mapping and EMD

FSA

MDCs

RMS

2.3.1 Computer Aided Dispatch

The contractor shall EFIST a CAD for CERS DAR. The contractor shall provide a CAD that is capable of supporting LE, Fire, and EMS in any capacity including multi-jurisdictional. The contractor shall ensure that calls for service and related information from the E911 system are seamlessly transferred to the CAD. CAD shall provide dispatchers the capability to maintain

Situational Awareness, rapidly assess and assign available emergency response resources. The

CAD shall provide integrated geospatial data/mapping and EMD job aids. Additionally, interfaces to other capabilities, such as AVL, MDCs, Emergency Reporting RMS, and data mining applications must be specified. The contractor shall ensure the CAD meets applicable system requirements set forth in the SDS as defined in Appendix D. Exceptions shall be on a case-by-case basis with prior Government approval.

2.3.2 Fire Station Alerting

The contractor shall EFIST a FSA system at each place of performance. FSA shall be initiated from any emergency dispatch position. The contractor shall ensure the FSA system meets applicable system requirements set forth in the SDS. Exceptions shall be on a case-by-case basis with prior Government approval. The following Table 2-1 identifies the quantity of fire stations at each installation that will require alerting capabilities set forth in the SDS as defined in

Appendix D.

Table 2-1 Quantity of Fire Stations per Installation

Installation Qty Fire

Stations

MCB Japan / Camp Fuji 7

MCB Camp Lejeune / MCAS New River 10

MCB Quantico / Marine Corps Air Facility 3

MCAS Yuma 2

MCAS Cherry Point 3

MCAS Beaufort 2

MCRD Parris Island 1

For Official Use Only

Source Selection Sensitive See FAR 3.104

Installation Qty Fire

Stations

Marine Corps Mountain Warfare Training

Center (MCMWTC) Bridgeport

Camp Pendleton (MCB / MCAS) 8

MCAGCC Twenty Nine Palms 2

MCRD San Diego 0

MCLB Albany 2

MCAS Iwakuni 2

MCAS Miramar 2

MCLB Barstow 2

2.3.3 Mobile Data Computer

The contractor shall extend the CERS DAR capability to mobile First Responders through the use of MDCs as in-vehicle information sharing tools. MDC is meant to be inclusive of the device, vehicle mounting system and communications network interface. Data is sent from the dispatchers to the MDCs via CAD systems. The contractor shall configure MDCs to enable a secure interface (in accordance with (IAW) IA policy and directive) with the CAD system, allowing secure communications with the MDC. The contractor shall ensure the CAD system interfaces with MDCs by one or more mobile communications networks. The contractor shall configure the MDC units to monitor CAD event and unit activity, view important call details, maintain their own status for assigned calls/events, update existing CAD events from the field, provide call/event disposition comments, send private and secure car-to-dispatch/car-to-car messages and perform comprehensive name, vehicle and property searches in F&ES and LE databases. The contractor shall ensure MDCs shall have access to geographical maps, F&ES database, LE databases, RMS and report generation tools. The contractor shall provide vehicle mounts where necessary for the MDC and associated ancillary devices. The MDC shall not interfere with the normal operations of the vehicle to include driver controls; Heating, Ventilation, & Air Conditioning; airbags; and battery power. Use of the MDC shall not degrade the vehicle battery life. The contractor shall ensure the MDC meets applicable system requirements set forth in the SDS as defined in Appendix D. Exceptions shall be on a case-by-case basis with prior Government approval.

2.3.4 Law Enforcement Records Management System

The contractor shall EFIST an LE RMS for CERS DAR. The contractor shall ensure the LE

RMS meets applicable system requirements set forth in the SDS as defined in Appendix D.

Exceptions shall be on a case-by-case basis with prior Government approval. Note: CAD interface is required to Emergency Reporting RMS (see 2.4.5); however, requirement in this section is for an additional RMS capability focused on LE records management.

2.3.5 Uninterrupted Power Supply System – Common Equipment

The contractor shall provide a solution that supports the power budget for the common equipment. The contractor may utilize existing CERS E911 available uninterrupted power of

1256 Watts, 12.5 Amps and 8 receptacles distributed over three (3) power distribution units.

For Official Use Only

Source Selection Sensitive See FAR 3.104

2.4 Interface Requirements

The contractor shall integrate CERS DAR components without degrading service, performance, or function of previously installed or existing systems. CERS DAR shall integrate with CERS

E911, E-LMR, and BTI without replacing hardware or software components of existing systems.

The contractor shall leverage user access rights and databases from CERS E911. The contractor shall integrate CERS DAR with existing audible and visual alarm notification at the consoles to alert any failure or outage on the system. The contractor shall utilize existing administration interfaces deployed during CERS E911. The contractor shall integrate CERS DAR components with existing dispatch workstation hardware. The contractor shall integrate CERS DAR components with existing Administration and Maintenance (A&M) workstation hardware.

2.4.1 Enhanced 911 Customer Premise Equipment

The contractor shall interface CERS DAR components with the E911 system deployed during

E911 to allow ANI/ALI data to be sent from the E911 system to the CAD. CERS E911 components are identified in Appendix E.

2.4.2 Logging and Recording

The contractor shall interface CERS Dispatch components with the E911 system to allow call data including the voice call to be associated with the incident record for RMS storage. CERS

E911 components are identified in Appendix E.

2.4.3 Dispatch Local Area Network

The contractor shall build CERS DAR on the LAN deployed during CERS E911. CERS E911 components are identified in Appendix E.

2.4.4 Time Synchronization

The contractor shall integrate CERS DAR with existing time synchronization services. The contractor shall synchronize CERS DAR components and subsystems to Global Positioning

System (GPS) time synchronization sources deployed under CERS E911. The contractor shall ensure MDCs are time synchronized with the CERS E911 capability. CERS E911 components are identified in Appendix E.

2.4.5 Geographic Information System Data Integration

The contractor shall integrate CERS DAR components with the Government provided

Geographic Information System (GIS), geospatial mapping data to provide a mapping capability from existing Government Furnished Information (GFI). The contractor shall use native ESRI file formats to the maximum extent possible.

2.4.6 Fire and Emergency Services Records Management System

The contractor shall provide a web services direct interface to the F&ES RMS that is capable of sending CAD data directly to the F&ES RMS system via a secure web link

<https://secure.emergencyreporting.com/dispatch/CallCenter.asmx>.

For Official Use Only

Source Selection Sensitive See FAR 3.104

2.4.7 Enterprise Land Mobile Radio Dispatch Console

The contractor shall integrate CERS DAR with existing E-LMR dispatch consoles. The contractor shall be able to integrate the following console types: Motorola, Harris, Zetron and

Cassidian. The dispatch console integration shall include the ability to accept radio PLI and AVL capabilities where they exist, and that standard interfaces are provided in all cases to allow PLI and AVL information from future E-LMR systems to be ingested. E-LMR components are identified in Appendix F.

2.4.8 Fire Alarm Systems

The contractor shall integrate CERS DAR with existing Fire Alarm monitoring systems that have the required external interface. The contractor shall be able to integrate at a minimum Monaco and King-Fisher fire alarm monitoring systems.

2.4.9 Uninterrupted Power Supply System – Workstation

The contractor shall provide a solution that fits within the power budget for the existing CERS

E911 console workstations; OR if the power budget of the CERS E911 does not have sufficient capacity, the contractor shall provide UPS additions or changes required to support the existing and newly installed systems at cutover. The contractor may utilize existing CERS E911 available uninterrupted power of 590 Watts, 7.2 Amps and 13 receptacles distributed over two

(2) power distribution units.

2.4.10 Workstation Area

The contractor shall EFIST and make operational CERS DAR desktop equipment, including cabling, power, display monitors, and ancillary devices, with the existing CERS E911 workstation area to create a dispatch workstation that complies with American National

Standards Institute/Human Factors and Ergonomics Society (ANSI/HFES) 100-2007. The

E911 workstations are designed for up to three (3) additional 17-22” flat panel monitors for use by the planned DAR solution. There is also space identified for an additional two (2) standard computer chassis below the work surface.

The contractor shall furnish a single keyboard and mouse at each workstation, which will give the dispatcher access to any information they can view from the workstation. This keyboard and mouse will interface with contractor computer systems via the E911-provided Keyboard - Video

- Mouse (KVM) interface. Operators shall be able to view information from any of the disparate systems (i.e., E911, CAD, FSA), and dispatch from a single workstation IAW ANSI/HFES 200-

2007. The layout shall be customizable by the user for their specific work preference and responsibilities. Peripheral equipment located on a dispatch workstation shall not be permanently attached to the workstation and instead shall be adjustable across the surface of the workstation.

2.4.11 Administration and Maintenance Workstation

CERS E911 provided a flat screen display for each integrated A&M workstation at each place of performance. The contractor shall integrate CERS DAR to the A&M workstations to support the administration of CERS DAR components and interfaces.

For Official Use Only

Source Selection Sensitive See FAR 3.104

3 Program Management

3.1 Project Planning

The contractor shall establish and maintain a Project Plan that meets the Government’s requirement for insight into the contractor’s methods of procedure used throughout the performance period of the PWS. The contractor shall provide and brief the Project Plan at the

Post Award Conference (PAC). The Project Plan shall be updated when changes to structure, schedule or performance occur and submitted monthly, at a minimum, to the Government for review. Project Plan updates shall be provided during the weekly meetings.

The Project Plan shall:

a) Function as a monthly Plan of Action and Milestones (POA&M) that includes project phases for each installation location. Changes to the POA&M that effect performance will be approved by the Government prior to changes being enacted.

b) Identify the project timeline and associated milestones. Track the progress and critical milestones of the program, including the tasks needed to complete the project.

c) Indicate the order in which the contractor proposes to perform the work and the dates on which the contractor contemplates starting and completing tasks (including acquiring materials, equipment, and utility service connections).

d) Address a management approach and highlight actions that will be taken to mitigate risk to cost, schedule, and performance.

e) Describe the contractor’s approach to Resource Management. The approach to Resource

Management should include program and reporting structure, organizational charts, and delivery team management. Changes in Resource Management that have impact on performance should be highlighted in Project Plan updates.

f) Highlight positive or negative impacts; provide details on the process to deal with unforeseen site conditions; and predict schedule slips

g) Detail work tasks and be reflective of activities and submittals including: technical reviews, planning, Product Acceptance, Site Acceptance, training, asset tagging, closeout documentation, and “as-built” submittals at a minimum.

h) Reflect the updated project progress as percent complete values for each task and project phase.

i) Include information in the form of a progress chart and indicate task dependencies.

j) Be baselined at the time of initial submittal and be re-baselined only upon Government approval.

k) Provide any and all necessary information, data, studies, and reports necessary or useful to demonstrate full compliance with Federal, State, and Local environmental laws, including any known potential compliance issues associated with the system manufacturing, testing, operations, or disposal.

Deliverable A0001, Draft Project Plan

Deliverable A0002, Project Plan Update

For Official Use Only

Source Selection Sensitive See FAR 3.104

3.2 Quality Control

The contractor shall develop and maintain an effective quality control program to ensure services are performed IAW this PWS. All discrepancies shall be reported to the Contracting Officer’s

Representative (COR), the PdM, and the local Technical Support Officer (TSO) within one (1) calendar day to ensure immediate resolution.

The Quality Control Plan (QCP) is intended to establish a benchmark for effective development of quality control procedures and to ensure that the contractor has implemented quality control effectively across all requirements of this PWS. The contactor’s internal quality control program shall establish tracking records for measurable performance requirements listed within this PWS.

In addition, the contractor shall incorporate the following minimum elements into the QCP:

a) Definition of contractor quality control management lines of responsibility.

b) Quality Control Management System Process.

c) Internal Design Review/Change Control Process.

d) Internal Document Control Process.

e) Process for preliminary systems testing and validation prior to Government System

Qualification Test (SQT).

f) Process for the execution of corrective maintenance.

g) Process for maintaining quality assurance records throughout the project lifecycle.

h) Process for performing random internal quality control audits.

The draft QCP shall be provided and briefed as part of the PAC. The Final QCP shall be presented at the System Requirements Review-2 (SRR-2). Any changes to the QCP shall be provided to the Contracting Officer and COR for approval at least 10 working days prior to implementation.

Deliverable A0003, Draft QCP

Deliverable A0004, Final QCP

3.3 Systems Engineering Management Plan

The contractor shall document and provide a Systems Engineering Management Plan (SEMP) detailing processes that aligns with the Government Systems Engineering Plan (SEP) that will be used to implement and commission all planned systems. A draft contractor formatted SEMP shall be delivered to the Government during the SRR-2. The final SEMP will be submitted to the

Government no later than (NLT) 20 working days after completion of SRR-2. Once the finalized

SEMP is developed and approved by the Government, any deviations shall be approved by the

Government.

The contractor shall provide a Hazardous Material Management Program Plan (HMMPP) as an attachment to the SEMP to identify hazardous materials used to build, test or deploy CERS

DAR, including procedural controls and precautions to be followed and risks of hazardous materials. Contractor format is acceptable as long as the contents in this data item description

(DID), DI-MGMT-81398B.

For Official Use Only

Source Selection Sensitive See FAR 3.104

The contractor shall provide a discussion as part of the SEMP of Human Factors and Human

Systems Integration (HSI) methods, processes, and standards that were used in the development of this system, including the system's projected compliance with the HSI standards listed in the

SDS (e.g., ANSI/HFES 100, ANSI/HFES 200, American Society for Testing and Materials

F1166-07).

The contractor shall develop content for Categorical Exclusions, Environmental Assessments, Environmental Impact Statements, and associated documentation, including the Programmatic

Environment, Safety and Occupational Health Evaluation (PESHE), National Environmental

Policy Act (NEPA) Compliance Assessments, and Overseas Environmental Assessments IAW

Executive Order (EO) 12114, Environmental Memorandums for the Record (MFRs), and other required environmental documentation and assessments to include any necessary NEPA/EO

12114 MFRs and Decision Memorandums. Contractor format is acceptable as long as the contents in this DID, DI-MISC-80508B.

The contractor shall document a Safety Assessment Report (SAR) to identify safety features of the hardware, software, and system design and to identify procedural, hardware, and software related hazards that may be present, including specific procedural controls and precautions that shall be followed, and any residual safety risks. Contractor format is acceptable as long as the contents in this DID, DI-SAFT-80102B, SAR. The contractor shall present the draft SAR as part of SRR-2. The contractor shall provide a final SAR with each system installation.

Deliverable A0005, Draft SEMP

Deliverable A0006, Final SEMP

Deliverable A0007, Draft SAR

Deliverable B0008, Final SAR

3.4 Configuration Management Plan

The contractor shall establish and maintain a Configuration Management (CM) Program throughout the project lifecycle. This program CM shall be documented in a Configuration

Management Plan (CMP) that aligns with the Government CMP, provided as GFI. The Draft

CMP shall be submitted to the Government for review at the PAC. The Final CMP shall be approved at the SRR-2.

Deliverable A0009, Draft CMP

Deliverable A0010, Final CMP

3.5 Post Award Conference

The contractor shall conduct a PAC, in the National Capital Region at a Government approved location, within 30 calendar days after contract award. NLT two (2) calendar days prior to the

PAC, the contractor shall electronically send to all participants the meeting information to include the agenda and presentation slides (in Microsoft Office format), and the Project Plan (in

Microsoft Project and Adobe Portable Document Format (PDF) file). The contractor shall provide a hardcopy binder of all required deliverables for each Government participant.

For Official Use Only

Source Selection Sensitive See FAR 3.104

The Government will conduct a paragraph-by-paragraph review of the PWS in conjunction with the contractor’s technical solution as it relates to system requirements and provide comments and recommendations. The Government will provide GFI, identify the contractor staging/storage area, establish Point of Contact (POC) lists, and provide protocols and rules of conduct.

Following the PAC, the contractor shall make the recommended changes to the documents presented during the meeting. The contractor shall not commence work until final approval by the COR of the Project Plan. The PAC shall be documented by electronic meeting minutes, which shall be submitted to the Government for approval NLT five (5) working days after the meeting. The PAC meeting minutes shall include at a minimum, attendees, activities conducted against the agenda, decisions/major clarifications made, action items, responsible party and due dates.

Deliverable A0011, PAC Agenda

Deliverable A0012, PAC Presentation

Deliverable A0013, PAC Meeting Minutes

3.6 Weekly Meetings and Status Reports

The contractor shall participate in weekly meetings with Government personnel either by teleconference or video teleconference to ensure the adherence to the Project Plan. At a minimum, the contractor shall participate in the weekly meeting in-person on a quarterly basis at a predefined Government location. During the weekly meetings the contractor shall provide status updates, findings, milestones, significant actions, issues and concerns, and discrepancies.

The contractor shall submit a Weekly Meeting Agenda NLT two (2) working days prior to the first weekly meeting. The Government will approve the agenda and the contractor shall use the

Government approved agenda for all weekly meetings. The contractor shall establish a Weekly

Meeting Action Log that tracks individual assigned actions including persons assigned, dates, course of actions (COA), and reference to the meeting at which the action was assigned. The contractor shall make the action log available NLT one (1) working day prior to the weekly meeting. The contractor shall establish a library showing drawings or photographs of critical items and work progress. The contractor shall maintain this library throughout the project. The contractor shall make the library available NLT one (1) working day prior to the initial weekly meeting. The contractor shall provide weekly meeting minutes. The contractor shall make the weekly meeting minutes available within five (5) working days after each meeting. The contractor shall transfer weekly meeting minutes, action logs, and the photo library to the

Government upon final acceptance of the project. The contractor shall provide a secure method, such as a secure File Transfer Protocol (FTP) site, for the purpose of delivering related project documents and weekly project photos electronically to the Government. This is separate from the

Compact Disk (CD) deliveries required of other contract deliverables.

Deliverable A0014, Weekly Meeting Agenda

Deliverable A0015, Weekly Meeting Action Log and Library

Deliverable A0016, Weekly Meeting Minutes

For Official Use Only

Source Selection Sensitive See FAR 3.104

4 Engineering Document Package

4.1 System-Level Engineering Document Package

The review and approval process for all system-level engineering documents includes preliminary (minimum 50 percent for each product) and final system-level engineering document package.

At the SRR-2, the contractor shall present the preliminary system-level document package and conduct a preliminary document review to allow the Government to validate the drawing formats, details captured, quality, and accuracy of the information. The contractor shall deliver the preliminary system-level engineering document package to the Government NLT thirty (30) working days prior to the SRR. The Government will review and comment on each of the engineering document packages and provide feedback on the document package at the SRR.

Contractor format is acceptable as long as the contents in the identified DIDs are addressed. At a minimum, the contractor’s system-level engineering document package shall include:

a) Table of Contents/Drawing Index.

b) System Architecture Diagram (logical diagram).

(1) Network services required for the operation of that device. Indicate the service name, protocol (e.g., Transmission Control Protocol and User Datagram Protocol) and port range.

c) System Time Synchronization Diagram (notional).

d) Design Descriptions

(1) System-Subsystem Design Description: DI-IPSC-81432A.

(2) Database Design Description: DI-IPSC-81437A.

(3) Data Flow Description.

(4) Theory of Operation.

e) Signal and Power Rack Plans.

f) Rack Elevations (notional).

g) Electrical Circuit Route Plan (notional).

h) Details of Interfaces to Other Systems/Subsystems.

(1) Interface Control Document: DI-CMAN-81248A, DI-IPSC-81436A, DI-IPSC-81434A

i) Details of Surge Protection Devices.

j) Details of Connector Terminations.

k) Detail Device Wiring.

l) Operating systems, applications, open-source software, Mobile Code, utilities, drivers, system services, scripts, configuration files, databases (including full database schemas), and other software required and the appropriate configurations, including revisions and/or patch levels for each of the computer systems.

m) List of hardware to include make, model, purpose/function, and supplier.

After completion of the preliminary document review and Government acceptance, the contractor shall construct the final system-level engineering document package incorporating any comments or changes delineated by the Government. The contractor shall deliver the final (90

For Official Use Only

Source Selection Sensitive See FAR 3.104 percent) system-level engineering document package to the Government for review NLT fifteen

(15) working days after completion of the SRR. When the final system-level engineering document package has been completed, the contractor shall prepare and conduct a final documentation review during a regular scheduled weekly meeting to allow the Government to provide final comments prior to final acceptance and implementation. The final system-level engineering document package will be accepted when Government comments are adjudicated and the Government approves all drawings and technical documents.

The contractor shall not begin work at any site until the Government has reviewed and approved the final system-level engineering document package.

Deliverable A0017, Preliminary System-level Engineering Document Package

Deliverable A0018, Final System-level Engineering Document Package

4.2 Location-Specific Engineering Document Package

The review and approval process for all location-specific engineering documents includes preliminary (minimum 50 percent for each product), final, and “as-built” document package.

At each PCV, the contractor shall provide the preliminary location-specific engineering document package and conduct a preliminary document review to allow the Government to validate the drawing formats, details captured, quality, and accuracy of the information. The contractor shall deliver the preliminary location-specific engineering document package to the

Government NLT five (5) working days prior to each PCV. The Government will have a period of ten (10) working days to review and comment on each of the engineering document packages.

The contractor shall deliver the final location-specific engineering document package to the

Government NLT twenty (20) working days prior to each Site Acceptance. The contractor shall deliver the ”as-built” location-specific engineering document package to the Government NLT five (5) working days after each Site Acceptance. The contractor shall redline the location-specific engineering document package and then incorporate the changes into a final, “as-built” drawing package. The final, “as-built” diagrams shall be delivered on Compact Disk – Read

Only Memory and one (1) printed hardcopy during the installation Site Acceptance. The contractor shall review the engineering document package for differences between the planned install and the actual. All differences will be formally noted on the final document package.

At a minimum, the contractor’s location-specific engineering document package shall include:

a) Table of Contents/Drawing Index.

b) System Architecture Diagram (logical diagram).

(1) Source Device Name and Media Access Control and/or Internet Protocol (IP) Address.

(2) Destination Device Name and Media Access Control and/or IP Address.

c) System Time Synchronization Diagram.

d) Floor Plan.

e) Electrical Plan Notes.

f) Panel Schedules.

g) Signal and Power Rack Plans.

h) Rack Elevations.

For Official Use Only

Source Selection Sensitive See FAR 3.104

i) Horizontal and Vertical Layouts.

j) Cable Racking Details.

k) Electrical Circuit Route Plan.

l) Details of Connections to Power Sources, Including Grounding.

m) Operating systems, applications, open-source software, Mobile Code, utilities, drivers, system services, scripts, configuration files, databases (including full database schemas), and other software required and the appropriate configurations, including revisions and/or patch levels for each of the computer systems.

n) Detailed listing of external interfaces and information sources and data flows associated with all interfaces. The listing shall include, for each networked device or class of device

(e.g., server, workstation, and switch).

o) Encryption and key exchange algorithms and services that shall be employed between any users or systems.

p) List of hardware to include make, model, serial number, purpose/function, and supplier.

Deliverable B0019, Preliminary Location-Specific Engineering Document Package

Deliverable B0020, Final Location-Specific Engineering Document Package

Deliverable B0021, “As–Built” Location-Specific Engineering Document Package

5 Cyber Security

The contract shall provide system hardware, software, and ancillary equipment that satisfies IA

Certification and Accreditation (C&A) requirements IAW the Department of Defense Instruction

(DoDI) 8510.01, Department of Defense (DoD) Information Assurance Certification and

Accreditation Process (DIACAP). The contractor shall provide and develop any necessary system documentation, settings, self-assessments and specifications required to support the successful accreditation of the Government DIACAP package. This shall include information in support of Government input into the Marine Corps Certification and Accreditation Support Tool

(MCCAST).

5.1 General Cyber Security

CERS is categorized as Mission Assurance Category (MAC) III Sensitive. The information processed by CERS DAR systems will be sensitive but unclassified. The contractor shall describe their implementation of applicable Cyber Security controls for the MAC and confidentiality level and provide security controls as described in Sections E4.A3 and E4.A5 of

DoDI 8500.2.

5.2 System Assurance

System assurance is the extent to which the underlying software, firmware, and hardware (which in totality constitute the service) have been controlled, evaluated, and tested to ensure that the service delivers precisely what it is designed to deliver. The Government desires to understand, on a continuing basis, the extent to which the contractor validates software, firmware, and hardware for completeness and compliance to ensure these items will not carry out any operation inconsistent with the requirement, design, or purpose of the overall service.

For Official Use Only

Source Selection Sensitive See FAR 3.104

The contractor shall ensure that the system, network and any component complies with applicable Government-wide laws, rules, and regulations for Cyber Security to include applicable DoD, Navy and USMC regulations, directives, and instructions associated with Cyber

Security. The Government will be responsible for submitting paperwork to the appropriate

Government Cyber Security organizations. The contractor shall work with the Government representative to provide required documentation, testing results, and compliance reports and follow through until Government certification is received for each installation. The contractor shall be responsible for correcting any deficiencies which prevent CERS DAR from being certified.

Additionally, the contractor shall remove, or otherwise disable, any unnecessary or unused software, ports, protocols and services, firmware or hardware from CERS DAR systems. The contractor shall also remove all default system, database, or application passwords and accounts, sample scripts, data, and files and programs not necessary for the operation of the system from

CERS DAR systems. The contractor shall ensure that the system shall not contain any components designed to permit access by non-authorized personnel into the system or to damage/erase system information.

5.3 Certification & Accreditation

The contractor shall conduct security vulnerability scanning IAW USMC/DoD approved tools, such as Gold Disk, Security Readiness Review Scripts (SRRS), or Retina. The contractor shall provide both raw and summarized reports of the scans for each system installation location. The scans shall be no more than 15 calendar days old on date of Site Acceptance for each location.

The contractor shall prepare a POA&M IAW USMC POA&M format. The contractor shall fix, patch, or mitigate all High risk, Severity Code 1, or Category 1 findings prior to delivery. The

Government will make available USMC specific scanning tools and POA&M format. The contractor shall provide a Host Information Configuration File to allow input of system data into

MCCAST. This file is a native tool output file and shall be no older than 15 calendar days prior to Site Acceptance. The contractor shall have the DoD Security Technical Implementation

Guides (STIGs) and SRRS applied to the system prior to connecting to the network. Once the

STIGs have been applied and the SRRS completed, all Category 1 vulnerabilities shall be mitigated prior to connection to the network. Verification of STIG and SRRS compliance by the

Government will be part of the certification process prior to Government acceptance. All

Category 2 vulnerabilities shall be mitigated prior to full accreditation. An accumulation of

Category 3 vulnerabilities can lead to a denial of the Authority to Operate (ATO). The contractor shall provide a POA&M using the USMC format for other unmitigated vulnerabilities prior to full accreditation.

Deliverable B0022, Raw Retina Security Vulnerability Scan Report

Deliverable B0023, Host Information Configuration File

Deliverable B0024, Summarized Retina Security Vulnerability Scan Report

Deliverable B0025, Cyber Security POA&M

At the accreditation boundary (the connection between the E911 system/service and the external network infrastructure) the contractor shall ensure:

For Official Use Only

Source Selection Sensitive See FAR 3.104

a) All hardware, software, and firmware that perform Cyber Security functions (e.g., firewalls, Intrusion Detection System (IDS)/Intrusion Protection System, cryptographic accelerators, and others) or is considered IA-enabled shall identify its Evaluated Assurance

Level IAW the National Security Telecommunications and Information Systems Security

Policy No. 11 as a result of the National Information Assurance Partnership (NIAP)

Assessment.

b) As approved in Section 5131 of the Information Technology Management Reform Act of

1996, Public Law 104-106, hardware, software, and firmware contractors using cryptographic modules shall ensure software meets Federal Information Processing

Standards (FIPS) Publication 140-2 (most current version) cryptographic protection Level

3 or higher and is validated via the Cryptographic Module Validation Program (CMVP).

The contractor shall support the collection of evidence in completing security accreditation and connection decisions and assist the process of requesting this decision. The contractor shall provide information necessary and assist the Government in developing (or updating) the System

Security Plan and DIACAP Implementation Plan and create other required documentation in pursuit of an ATO from the Marine Corps Designated Approving Authority (DAA) and an

Authority to Connect from the appropriate Connection Approval Office.

The contractor shall provide to the Government the data necessary to support the DIACAP C&A process. The contractor shall follow USMC C&A processes. This will include a description of the system, services and artifacts necessary to demonstrate compliance with management, technical, and operational security controls.

The contractor shall provide the following documentation and information for evaluation leading to C&A of capabilities:

a) Appropriate Defense Information Systems Agency (DISA) STIG report/procedures to support the accreditation.

b) Hashing to certify the operating system, driver, firmware, and other software versions installed on the device.

c) Software configuration parameters required for proper system operation.

d) Procedures used for performing a backup and trusted recovery of the servers, workstations, operating system, application…