01._PWS_N39430-19-R-2188.pdf

PERFORMANCE WORK STATEMENT (PWS)

NAVAL FACILITIES ENGINEERING COMMAND (NAVFAC)

ANTI-TERRORISM/FORCE PROTECTION (AT/FP) ASHORE PROGRAM

GLOBAL SUSTAINMENT CONTRACT

1.0 SCOPE

The Naval Facilities Engineering Command (NAVFAC) Anti-Terrorism/Force Protection (AT/FP) Ashore Program’s mission is to design, procure, integrate, install and sustain the Systems/Equipment to include hardware, associated firmware, and software required to provide the ability to protect mission-critical assets and personnel from natural disasters, acts of terrorism and other human-caused disasters. The Naval Facilities Engineering Command (NAVFAC)

AT/FP Ashore Program Management Office (PMO) centrally manages the Program and is located at the Washington

Navy Yard, DC. The AT/FP Ashore Program Management Office (PMO) oversees the AT/FP Ashore Sustainment

Program on behalf of Naval Facilities Engineering Command (NAVFAC).

The primary goal of the NAVFAC AT/FP Ashore Sustainment Program is to provide both preventive and corrective maintenance services to Navy installations as required to sustain NAVFAC AT/FP Ashore Program Systems /

Equipment in accordance with their operational requirements.

The NAVFAC AT/FP Ashore Sustainment Program is executed by the NAVFAC AT/FP Ashore PMO, NAVFAC

EXWC and NAVFAC regional Facilities Engineering Commands (FECs). These organizations provide support to

Commander, Navy Installations Command (CNIC), CNIC N3/N6, Navy Regions, and coordinate with Space and

Naval Warfare (SPAWAR) Systems Centers, and industry to provide sustainment services to Navy Ashore installations, for NAVFAC AT/FP Ashore Program Systems/Equipment worldwide and to facilitate improvements to

NAVFAC AT/FP Ashore Sustainment Program activities.

This is a Performance-Based Service Acquisition (PBSA) which covers the sustainment support for projects of the

NAVFAC AT/FP Ashore Program to include all system related hardware, associated firmware, and software employed as part of a system listed in Appendix C “List of Systems”; gap service calls for sustainment support of

AT/FP Ashore Systems not listed in Appendix C; and post-award Engineering Change Proposals (ECPs), technical refreshments (tech refreshes), upgrades or installation of new NAVFAC AT/FP Ashore Program Systems / Equipment to include hardware, associated firmware and software as required to be accomplished under this Performance Work

Statement (PWS). This PWS details services to be provided by the Contractor to include corrective and preventive maintenance of the systems/equipment, and the response to and resolution of service calls.

The intent of this contract is to effectively procure the equivalent of a full-service maintenance warranty for the

NAVFAC AT/FP Ashore Program Systems/Equipment to include hardware and associated firmware and software, which will include Cybersecurity/Risk Management Framework (RMF) Assessment and Authorization (A&A) requirements of the NAVFAC AT/FP Ashore Program Systems/Equipment. The scope of this AT/FP Ashore Global

Sustainment Contract is to provide centrally-managed sustainment for the NAVFAC AT/FP Ashore Program

Systems/Equipment to include hardware, associated firmware and software located at Naval Installations worldwide as identified in this PWS and supporting documents. A System/Equipment includes all of the hardware, associated firmware, software, and cabling or other signal/data transmission sub-systems necessary for the System/Equipment to function as intended. Sustainment is defined as all work and costs associated with maintaining and repairing the

Systems/Equipment to include hardware, associated firmware, software and material as required enabling the

NAVFAC AT/FP Ashore Program Systems/Equipment to perform as specified in accordance with the applicable performance specifications. This PWS does not include warranty or sustainment services for the Navy information transport networks that provide data connectivity; Navy/Marine Corp Intranet (NMCI), OCONUS Network

Environment (ONE-Net), or Public Safety Network (PS-Net).

The NAVFAC AT/FP Ashore Program Sustainment Team provides oversight of the Sustainment Contractor’s Service

Call Management to include: the Contractor’s Response to and Resolution of Service Calls, Service Call Analysis, and Asset/Configuration Management, as required to maintain specified Operational Availability (Ao) requirements for Systems/Equipment under this PWS. For additional quality assurance purposes, the NAVFAC EXWC AT/FP

Ashore Program Sustainment Team also performs an effective programmatic trend analysis via the AT/FP Ashore

Remedy System to evaluate/analyze systemic NAVFAC AT/FP Ashore Program Systems/Equipment sustainment issues.

1.1 Supported AT/FP Ashore Systems

NAVFAC AT/FP Ashore Program Systems/Equipment provide the capability for access control, ability to receive/transmit orders, receive and process information into situational awareness displays, support command decision processes and communicate electronic data to multi-service or multi-agency nodes across the entire all-hazards/all-threats spectrum of Ashore and Afloat operations. NAVFAC AT/FP Ashore Program Systems /

Equipment also provide hazard warnings to all personnel on board the installation, and others as appropriate. System performance of fielded NAVFAC AT/FP Ashore Program Systems is described via the use of Performance

Specifications, Unified Facility Criteria (UFC) or other available technical data. The specific types of NAVFAC

AT/FP Ashore Program Systems to be supported under this PWS are summarized in the following paragraphs.

1.1.1 Command, Control, Communications, Computers, & Intelligence (C4I)/Emergency Management (EM)

The Anti-Terrorism, Force Protection, and Public Safety missions all require that the Navy maintain a robust capability to respond to emergency situations for protection of U.S. Navy personnel and assets. This is accomplished through a fast and effective First Response to emerging situations as well as a scalable Command and Control capability to effectively assimilate large amounts of breaking information, aid in decision-making, and facilitate effective communications with response forces and the Navy population.

The Command, Control, Communications, Computers, and Intelligence (C4I)/Emergency Management (EM) mission includes the following capabilities:

Communications o ELMR

Operations Centers o Regional Operation Centers o Emergency Operation Centers

Dispatch Centers o Regional Dispatch Centers o Local Dispatch Centers o Sensor Assessment Cells (SAC)

Mass Notification Systems o Giant Voice/Indoor Voice o Net Centric Mass Notification system

1.1.1.1 Communications

Enterprise Land Mobile Radio (ELMR) System – Digital Trunking Infrastructure

The Scope of this PWS applies to ELMR System infrastructure assets that fall under U.S. Navy administration as part of the Joint National Capital Region Land Mobile Radio (J-NCR LMR) System, serving the Navy District Washington area of responsibility. Land Mobile Radio assets in other Navy Regions are not included in this PWS. Land Mobile

Radio subscriber units (portable, vehicle, and consolette radios) are not covered under this PWS.

The J-NCR Land Mobile Radio (LMR) System is a digitally controlled trunk radio system that provides Navy first responders with critical emergency communications. The J-NCR LMR System is a digital trunked LMR System fielded to coordinate the deployment and actions of the first responder community. It is recognized that effective emergency communications is a key element in reducing the loss of life and property in any crisis or incident. The J-

NCR LMR System network allows a coordinated response between Navy emergency services and other federal, state and local agencies involved in public safety. Additionally, LMR will provide interoperability within and between the service components. The J-NCR LMR System infrastructure includes the following:

Antennas (including Microwave Dishes and cabling)

Lightning arrestors, Pre-selectors, Multi-couplers, Combiners

Repeaters

Zone Cores at Regional Dispatch Center

Channel Banks

Radio Dispatch Work Stations

Encryption Key Management Client Work Stations

Radio System Management Client Work Stations

Microwave Links

Multiplexers

Radio Gateways at Dispatch Centers

1.1.1.2 Operations Centers

The Emergency Operation Center (EOC) serves as the C4I/EM point for the base commander to gather information and gain situational awareness. During incidents affecting tenants within a specific installation or geographic area, the EOC is used to conduct emergency management functions. The installation’s EOC assumes command and control unless the incident escalates beyond the scope of the base-level commander. The EOC interfaces directly with the

Regional Operations Center (ROC). The ROC, in turn, interfaces with the Navy Shore Operations Center (SHOC) where CNIC coordinates with the U.S. Fleet Forces (USFF) Command.

The ROC is the operational and command support center for all Navy installations in a designated Navy region. The

ROC is co-located with the Regional Commander to provide the capability to oversee and respond to any incident and can display and operate in classified, sensitive-but-unclassified, controlled unclassified and unclassified information environment. The four functions handled by the ROC includes gathering of regional information, gain situational awareness, exercise control of forces, and interact with other government agencies.

1.1.1.3 Dispatch Centers

The Regional Dispatch Center (RDC) and the Local Dispatch Center (LDC) provide continuous 24 hour per day, 7 days per week, 365 days per year capability that monitors normal operations on one or more Navy installations and directs an appropriate first response to questionable situations or confirmed incidents that endanger Navy personnel or the Navy mission. Response is enacted using the available Security, Firefighting, and Medical resources assigned to the area of the incident as well as civil authorities when appropriate. The Dispatch Center serves as the Public

Safety Answering Point (PSAP) that fields incoming emergency telephone calls from the public that originate from within a U.S. Navy installation. It also monitors and directs the initial response to numerous Security and Fire Alarms throughout its area of responsibility.

Enterprise Navy Emergency Response Management System (E-NERMS) is at the center of emergency response for the RDC. E-NERMS is a consolidated Computer Aided Dispatch (CAD) system that combines traditional emergency dispatch services with modern Geographic Information Systems (GIS) real-time services, such as Address

Verification, Automatic Vehicle Location, Recommendation and Routing, Map Displays, and Online GIS Updating.

E-NERMS provides an enterprise system that standardizes equipment, operating processes, and capability across all

RDCs in CONUS. Outside CONUS, this emergency response functionality is provided by the OCONUS Navy

Consolidated Emergency Response System (ON-CERS). It provides a standardized VMware virtualized environment that accommodates services such as a CAD Infrastructure that supports centralized administration and two redundant

Service Delivery Point (SDP) datacenters for RDC off-site storage, CAD failover, and failback capability. Hardware for E-NERMS is located at both the RDC and SDP. The integrated technologies enable the Navy to consolidate emergency calls and dispatch functions for police, fire, and emergency medical agencies.

NOTE: Hardware for E-NERMS is located in the Service Delivery Points (SDP) and may require additional access requirements.

Dispatch operations benefit from use of the following technologies to optimize emergency communication and response times:

Alarm Monitoring & Automation o Regional Alarm Monitoring & Automation System (RAMAS) o Local Alarm Monitoring & Automation System (LAMAS) o Alarm front end / field panels / alarm receivers / head end panels feeding to LAMAS or alarm receiver panels o Designated alarm points such as Navy Munitions Command (Class I and II)

Navy Emergency Response Management System (NERMS), Enterprise Navy Emergency Response

Management System (E-NERMS) and OCONUS Navy consolidated Emergency Response System (ON-CERS) in OCONUS.

o Computer Aided Dispatch (CAD), Geographic Information System (GIS), and Management Information

System (MIS) o Records Management System (RMS) which includes Fire RMS (FRMS) and Police RMS (PRMS)

RMS connectivity to National Fire Incident Reporting System (NFIRS) and Consolidated Law

Enforcement Operations Center (CLEOC) o Integrated National Crime Information Center (NCIC) Lookup o Integrated Fire Station Alerting in CAD

Local Mobile Data Computer (MDC) with WiFi Hotspot connectivity

Physical Security Information Management (PSIM)

Voice Recorders for 911 Telephone and Radio Traffic

Enterprise Land Mobile Radio (ELMR)

Sensor Management Display System

Dispatch Console with CAD, GIS, LAMAS, and RAMAS Display Systems

1.1.1.4 Mass Notification Systems (MNS)

Mass Notification Systems are employed to comply with Department of Defense (DoD) Instruction 6055.17 “Mass

Warning and Notification”, providing all DoD installations with notifications to warn all personnel immediately, but no longer than ten (10) minutes, following the verification of an incident. All DoD installations must possess, operate, and maintain dedicated access to communication capabilities at the EOC or another designated centralized location to ensure mass warning and notification.

Net Centric Mass Notification system (Automated Telephone Notification System (ATNS) /Computer Desktop

Notification System (CDNS))

The NetCentric Mass Notification system alerts establish groups of individuals via the telephone and/or computer.

The system supports mass alerting via desktop popup, email, SMS texting, and telephone/cell phone.

Giant Voice (GV)

Giant Voice (GV) provides Mass Notification alerts and follow-on directions to personnel located in outdoor areas.

GV is comprised of an Outdoor Voice/Alert function and a System Control function. The System Control function provides an autonomous operation and allows authorized personnel to operate the system manually. The outdoor component consists of the outside speaker(s) positioned on poles and buildings across the installation. The GV system is installed as a base-wide system to provide a siren signal and pre-recorded and live voice messages. In order to create the right level of sound output, multiple poles and speakers will be positioned across the installation.

Indoor Voice (IV)

Indoor Voice (IV) is part of the individual building MNS and is comprised of IV, Interior Notification, and System

Control functions. The IV function is intended to provide real-time alert and follow-on directions. The System Control function allows authorized personnel to operate the system manually or autonomously. The Interior Notification function is intended to be provided by loud speakers, warning lights, and illuminated signs or displays. Speakers are provided at all locations in and around the building at entrances/exits and other outdoor areas (such as courtyards) commonly used by the building occupants.

1.1.2 Physical Security/Access Control (PS/AC) Systems

Physical Security/Access Control systems are important components of the AT/FP Ashore posture at Navy installations worldwide. Descriptions of the NAVFAC AT/FP Ashore PS/AC Systems are provided in the following paragraphs in this section. Complete details and performance requirements for the NAVFAC AT/FP Ashore PS/AC

Systems/equipment are provided in Appendix I “System Performance Specifications” or in Unified Facility Criteria

(UFC) codes or other available technical data.

PS/AC functionality, including Access Control Points (ACPs), Electronic Security Systems (ESSs), Enclave perimeter security, and other capabilities, are typically implemented from a single infrastructure for each Navy Region. A

Regional Physical Access Control System (PACS) and a Regional Physical Security Information Management (PSIM) system infrastructure provides a centralized administration, monitoring, and integrated functionality for NAVFAC

AT/FP Ashore PS/AC systems and components throughout the region.

The Physical Security/Access Control mission includes the following capabilities:

Access Control Points (ACPs) o Vehicle Gates (VGs)

Active Vehicle Barriers (AVB)

Multi-Mode AVBs (M-AVB) o Automated Vehicle Gates (AVGs)

Automated Vehicle Gate – Enclave (AVG-E)

Automated Vehicle Gate – Low Volume (AVG-L)

Automated Vehicle Gate – High Volume (AVG-H)

Automated Vehicle Gate – Bi-Directional (AVG-B) o Pedestrian Gates (PGs)

Automated Pedestrian Turnstiles (APT)

Electronic Security Systems (ESSs) o Airfield Enclave o Perimeter Enclave o Pier Enclave o Building Enclave o NMC Enclave

Waterside Security Systems o Electronic Harbor Security System (EHSS) o Port Security Barriers (PSB)

Inspection Systems o Personnel Inspection System o Vehicle Inspection System

Physical Security Information Management (PSIM) System

1.1.2.1 Access Control Point – Vehicle Gate (ACP-VG)

An active vehicle barrier requires some action, either by personnel, equipment, or both, to permit or deny entry of a vehicle. The system has some form of moving parts controlled by external activation. Active vehicle barrier systems can include active bollards, active drop-arm beams, active nets, actives wedges (plate or fingers) or active gates.

Active Vehicle Barriers (AVB)

The design of an Entry Control Facility (ECF)/Access Control Point (ACP) must ensure that vehicles are contained through an arrangement, which includes Active Vehicle Barriers (AVB). AVBs require some action, either by personnel, equipment, or both, to prevent entry of an unauthorized vehicle. ECFs/ACPs must be provided with Active

Vehicle Barriers (AVBs) to enable the ECF/ACP to be closed (fully contained) and to prevent an unauthorized vehicle from breeching the security. The design of the ECF/ACP must include provisions to protect innocent users of the

ECF/ACP from operation of the AVB whether deployment is accidental, during a test, or during an actual response to a threat.

The technical performance requirements and capabilities for Active Vehicle Barriers (AVBs) are provided in the following documents: List of DoD Anti-Ram Vehicle Barriers, UFC 4-022-01 Entry Control Facilities Access Control

Points dated 27 July 2017, and UFC 4-022-02 Selection and Application of Vehicle Barriers Change 1 dated 9 August

2010.

AVB systems are categorized into three primary areas; 1) baselined multi-mode active vehicle barriers, 2) baselined active vehicle barriers, and 3) legacy active vehicle barriers. Baselined active vehicle barriers are selected from the

NAVFAC AT/FP Ashore Analysis of Alternatives (AoA) authorized list. All other active vehicle barriers are considered legacy.

1.1.2.2 Access Control Point – Automated Vehicle Gate (ACP-AVG)

ACP-AVGs are employed to provide perimeter security to Navy installations or to restricted access to internal enclaves by checking personnel credentials and allowing access only to individuals who are authorized for entry at that location, on that day, and at that time, through automation. Unauthorized personnel will be denied entry and will be instructed how to leave the area. The automation feature provides a capability to perform this process without the interaction of an onsite security guard. ACP-AVG operation can be monitored remotely at a Dispatch center with assistance from patrol units when necessary or may also be supervised by a local security guard while working other duties at the

Access Control Point.

ACP-AVG designs utilize some or all of the following technologies in various configurations as explained in the paragraphs below:

Automated License Plate Reader (ALPR) System

Active Vehicle Barriers/Drop Arms/Turnstiles

Closed Circuit Television (CCTV) Camera Systems

Network Video Recorder (NVR)

Access Control (Card Readers, Intercoms, Keypads, and Programmable Logic Controllers)

Dynamic Message Signs (DMS)

Gate Automation Systems

Intercom Systems

Physical Access Control Systems (PACS)

Vehicle Presence Sensors

Physical Security Information Management (PSIM) system

Badging/Enrollment

Automated Vehicle Gate – Low Volume (AVG-L)

The AVG-L capability offers the highest level of perimeter security and is intended for public-facing entry points into a Navy installation that either (a) have sufficiently low traffic volumes to be left completely unsupervised for all but the peak traffic hours, or (b) function alongside other supervised traffic lanes of a multi-lane gate, thereby reducing manpower at the site during normal working hours and providing an unsupervised operation during nighttime or weekend hours when traffic volume is sufficiently low. Reduces manpower costs while enhancing the security posture of low vehicular throughput (<60 vehicles/hr).

Automated Vehicle Gate – Enclave (AVG-E)

The AVG-E capability is intended for use at interior access control points where personnel and vehicles have already been screened once for initial access onto the Navy installation and are now seeking entry into a restricted-access

Enclave area. AVG-E is used when a single automated gate (e.g., sliding, tilt, lift) is sufficient to maintain the integrity of the Enclave perimeter while allowing personnel/vehicles to gain access.

Automated Vehicle Gate – High Volume (AVG-H)

The AVG-H design is intended for multi-lane Access Control Points that serve as the main entry point for a Navy

Installation. The AVG-H configuration will typically employ multiple automated ingress and egress lanes under the supervision of one or more local sentries who monitor the automated traffic lanes while manually controlling traffic for at least one inbound lane. Reduces manpower costs while enhancing the security posture of high vehicular throughput (>60 vehicles/hr).

Automated Vehicle Gate – Bi-Directional (AVG-B)

The AVG-B capability is intended for use at interior access control points where personnel and vehicles have already been screened once for initial access onto the Navy installation and are now seeking entry into a restricted-access

Enclave area. AVG-B is used when a single automated gate (e.g., sliding, tilt, lift) is sufficient to maintain the integrity of the Enclave perimeter while allowing personnel/vehicles to gain access. AVG-B utilizes a single lane for both ingress and egress traffic and is intended for gates with very low throughput and with an informed user population.

1.1.2.3 Access Control Point – Pedestrian Gate (ACP-PG)

The Access Control Point capability also includes a pedestrian-only configuration known as an ACP-PG. ACP-PGs are employed both at public-facing entry points for initial access onto a Navy Installation and at interior Enclave perimeters for a restricted-area access. ACP-PGs typically employ automated pedestrian turnstiles (APT) and are often accompanied by a swing gate that complies with Architectural Barriers Act (ABA)/Americans with Disabilities

Act (ADA) Accessibility Guidelines.

Access Control Point – Automated Pedestrian Turnstiles (ACP-APT)

Automated Pedestrian Turnstiles are employed both at public-facing entry points for initial access onto a Navy

Installation and at interior Enclave perimeters for a restricted-area access. Automated Pedestrian Turnstiles may be configured with multiple turnstiles, CCTV camera systems, Network Video Recorder, intercoms and enhanced lighting.

1.1.2.4 Electronic Security System (ESS)

An ESS is intended to provide additional layers of security to a perimeter or area of interest within each Navy

Installation that requires an enhanced security posture. Electronic Security Systems (ESS) are comprised of the following capabilities:

Physical Access Control Systems (PACS)

Access Control (Card Readers, Intercoms, and Keypads)

Closed Circuit Television (CCTV) / Camera Systems etwork Video Recorder (NVR)

Intrusion Detection Systems (IDSs)

Virtual Perimeter o Video Analytics o Sensors, Sensor Management, Sensor Analytics

Badging/Enrollment

1.1.2.5 Waterside Security Systems

Electronic Harbor Security System (EHSS)

An EHSS is intended to protect Navy ships in port from waterside attacks. The operational capability of EHSS includes the following:

Detect and track surface targets

Detect and track subsurface targets

Automatically alert based on security criteria

Aid security forces with assessment, interdiction, response and warning

Output track data for consolidation at higher levels (situational awareness)

Port Security Barriers (PSB)

PSBs provide defense and restriction of unauthorized vessels within restricted waters. They discourage, stop, and delay attacking boats allowing security forces the time to respond, intercept and interdict.

1.1.2.6 Inspection Systems

Both Personnel Inspection Systems and Vehicle Inspection Systems are used to screen either personnel or vehicles entering the installation. This screening is necessary for the protection of high value assets by detecting threats such as weapons, other illegal contraband and narcotics.

1.1.2.7 Physical Security Information Management (PSIM) System

The PSIM does not provide an operational capability in and of itself, rather, it is an overarching management capability that can assimilate information from many diverse sensors and systems. The PSIM presents the sub-system information to Navy Emergency Management personnel in a Common Operating Picture, and interact with diverse systems allowing an operator control of the various technologies while combining relevant visual intelligence, Standard Operating Procedure (SOP) on-screen guidance, and automated tasking.

PSIM functionality includes the following:

Collection: Device management independent software collects data from any number of disparate security devices or systems.

Analysis: The system analyzes and correlates the data, events, and alarms, to identify the real situations and their priority.

Verification: PSIM software presents the relevant situation information in a quick and easily-digestible format for an operator to verify the situation.

Resolution: The system provides Standard Operating Procedures (SOPs), step-by-step instructions based on best practices and an organization’s policies, and tools to resolve the situation.

Reporting: The PSIM software tracks all the information and steps for compliance reporting, training and potentially, in-depth investigative analysis.

Audit trail: The PSIM also monitors how each operator interacts with the system, tracks any manual changes to security systems and calculates reaction times for each event.

PSIM is deployed to interface with numerous sensors and security cameras from diverse systems, thermal imaging cameras, diverse intrusion detection systems, and access control systems. PSIM is used with the ACP-AVG capability to monitor cameras and alarm events associated with unauthorized entries. PSIM can also be used with other capabilities such as the Electronic Harbor Security System, as directed.

1.2 Supported Locations

This PWS is issued in direct support of CNIC for the sustainment of NAVFAC AT/FP Ashore Program Systems /

Equipment at Naval Installations world-wide. Table 1 lists Navy Regions/Areas Responsibility (AORs) where

Systems sustainment support is currently provided to the Navy Regions by the NAVFAC AT/FP Ashore Program.

Navy Regions under CNIC

Navy Region Northwest Navy Region Hawaii

Navy Region Southwest Navy Region Southeast

Navy Region Mid-Atlantic Navy Region Japan

Naval District Washington Navy Region Europe, Africa, Central

Joint Region Marianas Singapore Area Coordinator

U.S. Forces Korea

Table 1

Navy Regions under CNIC

1.3 List of Supported Systems

Appendix C defines the NAVFAC AT/FP Ashore Systems to be supported by the PWS.

Appendix C “List of Systems” establishes the contractual requirements for Systems to be supported under the terms and conditions of this PWS. The Contractor shall sustain listed systems at the locations identified in the Appendix C.

Actual system subcomponents may differ from one location to another; however, the Contractor shall be responsible for sustaining the system and all subcomponents, hardware associated firmware and software thereunder.

1.4 Summary of Sustainment and Maintenance Tasks

The AT/FP Ashore Global Sustainment Contract PWS describes requirements to provide the support needed to carry out the day-to-day sustainment and maintenance of aforementioned NAVFAC AT/FP Ashore Program Systems including hardware, associated firmware, software and related services which are summarized as follows:

Sustainment of existing projects of the NAVFAC AT/FP Ashore Program to include hardware, associated firmware and software management to include:

o Preventive and Corrective Maintenance as required to maintain an Operational Availability (Ao) as defined in the applicable Performance Specifications, technical information and Table 2 “Required

Operational Availability of AT/FP Systems” o Maintaining interoperability of components and systems

Service Call Management to provide end-to-end sustainment support to include:

o Response to and Resolution of Service Calls o Configuration Management as required to maintain the baseline Systems o Providing Remedy database service history o Maintaining Remedy database asset data accuracy o Notification of system End-of-Life (EOL) status o Disposal of assets as applicable

Software Management to include:

o Managing software licenses and renewals o Software installation and updates o Maintaining Cybersecurity compliance

Date Requirements and Contract Support to include:

o Annual verification of system/equipment asset data o Managing and maintaining Service Level Agreements (SLA) as required. Examples listed below:

Security Information Systems (SIS) software

Northrop Grumman Command Point Computer Aided Dispatch (CAD) Software

Northrop Grumman COBOL Computer Aided Dispatch (CAD) Software

Northrup Grumman E-NERMS/NERMS

AtHoc CDNS/ATNS

Kingfisher

PC Logic

Federal Signal

Eaton

Commend

Original Equipment Mfgs eLMR (Harris Corporation)

VPMS System

3ETI

Lenel

Enabler

Bridgepoint

Milestone

Chameleon

Vigilant

Whelen

ATI

American Signal

Monaco

MOOG

RSSI

Honeywell / Vindicator

Alertus

Motorola

Other support to include:

o Implementation of Cybersecurity policy and requirements to include C&A of the NAVFAC AT/FP

Ashore Program Systems across the Enterprise o Sustainment of new NAVFAC AT/FP Ashore Program Systems from post-award installation projects if and when exercised through a modification to this contract.

o Obsolescence management of systems/equipment

1.5 Objective

The intent of this PWS is to have the Contractor perform both preventive and corrective maintenance as required to meet designated time periods as stated in Table 4 “Technical Support Response and Resolution Time Requirements”, as well as maintain an Ao as defined in the applicable Performance Specifications and Table 2 “Required Operational

Availability of AT/FP Systems”. The effort will require advance preparation by the Contractor to include, but not limited to, positioning of technician personnel and housing of spare parts in locally-accessible storage facilities.

SYSTEM Required Ao

Regional Operations Centers (ROC)

Emergency Operations Centers (EOC) 0.90

Regional Dispatch Centers (RDC)

Local Dispatch Centers (LDC) 0.9995

Mass Notification Systems 0.90

J-NCR Land Mobile Radio 0.9995

Access Control Points – (ACP-VG, ACP-AVG, ACP-PG)

0.90

Electronic Security Systems 0.90

Ao requirements exclude down-time for approved planned maintenance events as described in paragraph 4.2.2 Preventative Maintenance Down-time

Table 2

Required Operational Availability of AT/FP Systems

Dispatch Center operation and the Land Mobile Radio System operation shall be available and fully functional 99.95% of the time (excluding planned maintenance as per paragraph 4.2.2 Preventive Maintenance Down-time) as required by the National Fire Protection Association (NFPA) 1221, “Standard for the Installation, Maintenance and Use of

Emergency Services Communications Systems”, Chapter 10 and Section 10.6.5.

1.6 Order of Precedence

In the event of a conflict between the text of this document and the references cited herein, the text of this document takes precedence. Nothing in this document, however, supersedes applicable laws and regulations, including contract clauses, unless a specific exemption has been obtained in writing.

2.0 REFERENCES

All reference documents are intended to be used for guidance only, unless compliance is required within the body of this PWS. Guidance documents may be used as an aid in identifying applicable topics to be addressed consistent with meeting the objectives of the NAVFAC AT/FP Ashore Program. The Contractor shall propose alternatives, as required, to the specifications and standards cited herein if they would enhance system performance or cost effectiveness. Unless otherwise specified, the issues of Government documents are those listed in the current version of the DoD Information Technology (IT) Standards Registry (DISR) on the date of this specification. The issues of

Industry standards are those in effect on the date of this specification.

The references identified below apply to this Contract.

2.1 Department of Defense

NUMBER DATE TITLE

C4ISuite SID 09/06/2007 C4ISuite Services Integration Document

CNIINST 3440.17 01/23/2006 navy Installation Emergency Management Program Manual

CNICINST 2300.1 Draft v1.0 Enterprise Land Mobile Radio Account Management

COMSPAWAR 3090.2C-M 07/10/2017 Fleet Readiness Certification Board (FRCB) Handbook

DDCIO (N) 08/04/2017 Risk Management Framework Process Guide v2.0

DFARS 252.211-7003 Rev 05/28/2014 Item Unique Identification and Valuation

DISR 05-1.0 04/25/2005 Department of Defense Information Technology Standards

Registry

DoD 5200.08-R 04/09/2007 DoD Physical Security Program

DoD 5200.28-STD DoD Trusted Computer System Evaluation Criteria

DoD A/E/C CAD STD R5.0 U.S. National CAC Standard (NCS)

DoD DAG 09/15/2012 Department of Defense Guide to Uniquely Identifying Items, Assuring Valuation, Accountability and Control of

Government Property, Version 2.5

Defense Acquisition Guidebook (DAG) (Available on-line at https://dag.dau.mil/Pages/Default.aspx)

DoDD 5000.1 05/12/2003 Operation of the Defense Acquisition System

DoDD 5200.1 12/13/1996 DoD Information Security Program

DoDD 5200.28 03/21/1988 Security Requirements for Automated Information Systems

DoDD 8100.2 04/14/2004 Use of Commercial Wireless Devices, Services, and

Technologies in the Department of Defense (DoD) Global

Information Grid (GIG)

DoDD 8140.01 07/31/2017 Cyberspace Workforce Management, with Change 1

DoDD C-5200.5 04/21/1990 Communications Security (COMSEC)

DoDI 5200.08 12/10/2005 Security of DoD Installations and Resources

DoDI 5215.2 Computer Security Technical Vulnerability

Reporting Program (CSTVRP)

DoDI 7730.47 Defense Incident-Based Reporting

DoDI 8500.01 03/14/2014 Cybersecurity

DoDI 8510.01 07/28/2017 Risk Management Framework (RMF) for DoD Information

Technology

DoDI 8520.02 04/24/2011 Public Key Infrastructure (PKI) and Public Key (PK) Enabling

DoDI 8520.03 05/13/2011 Identity Authentication for Information Systems

DoDM 5200.01 Vol 1-4 02/24/2012 DoD Information Security Program

(DTM) 08-006 11/26/2008 DoD Implementation of Homeland Security Presidential

Directive -12 (HSPD-12)

ELMR CONOPS V2.05 02/24/2014 CNIC Concept of Operations for the U.S. Navy Enterprise

Land Mobile Radio (ELMR)

EM 385-1-1 08/11/2011 Army Corps of Engineers Safety Manual

MIL-HDBK-235/1B 12/22/2000 Electromagnetic (Radiated) Environment Considerations for

Design & Procurement of Electrical & Electronic Equipment, Subsystems & Systems

MIL-HDBK-338B 10/01/1998 Electronic Reliability Design

MIL-HDBK-1013/1A Design Guidance for Physical Security Facilities

MIL-HDBK-2036 11/01/1999 Electronic Equipment Specifications, Preparation of

MIL-STD-130N, with Change 1 11/16/2012 Department of Defense Standard Practice Identification

Marking of U.S. Military Property

MIL-STD-461E 08/20/1999 Requirements for the Control of Electromagnetic Interference

Characteristics of Subsystems and Equipment

MIL-STD-464A 12/19/2002 Electromagnetic Environmental Effects Requirements for

Systems

MIL-STD-810G 08/10/2007 Test Standard for Environmental Engineering

MIL-STD-882D 02/10/2000 System Safety

MIL-STD-961E 08/01/2003 DoD Defense and Program-Unique Specifications Format and

Content

NAVNETWARCOMINST 12271.1 10/17/2006 Policy and Procedures for the Fleet Readiness Certification

Board (FRCB) Process

OPNAV 3440.17 07/22/2005 Navy Installation Emergency Management Program Manual

OPNAVINST 2400.20F 07/19/2007 Electromagnetic Environmental Effects (E3) and Spectrum

Supportability Policy and Procedures

OPNAVINST 3000.12A 09/02/2003 Operational Availability of Equipment and Weapons Systems https://dag.dau.mil/Pages/Default.aspx

Handbook

OPNAVINST 3440.17A 08/01/2014 Navy Installation Emergency Management Program

OPNAVINST 5530.1E 01/28/2009 Navy Physical Security and Law Enforcement Program, with

Change 2

OPNAVINST 5530.13C 09/26/2003 Navy Physical Security Instruction for Conventional Arms, Ammunition and Explosives (AA&E)

OPNAVINST 5530.14C Navy Physical Security

SDDCTEA Military Surface Deployment and Distribution Command

Transportation Engineering Agency Traffic Engineering

Guidance Documents

SECNAV-M 5239.1 11/2005 DoN Information Assurance Program

SECNAV-M 5239.2 06/2016 Cyberspace Information Technology and Cybersecurity

Workforce Management and Qualification Manual

SECNAVINST 5239.C 05/02/2016 DoN Cybersecurity Policy

SECNAVINST 5510.36A 10/06/2006 DoN Information Security Program

SEIWG 0400 01/2012 Joint Anti-Terrorism/Force Protection Technical Standards

Profile (TV-1)

SEIWG ICD-0100 10/27/2006 Security Equipment Information Working Group, Interface

Control Document for XML Information Interchange

SEIWG JGS ICD v2.0 02/2011 Security Equipment Integration Working Group Interface

Control Document (ICD) for XML Information Interchange, Version 2.0

SIPH v4.0 10/12/2014 SPAWAR Shore Installation Process Handbook version 4.0

VPMS CONOPS v1.0 10/29/2008 (DRAFT) CNIC Virtual Perimeter Monitoring System

(VPMS) Concept of Operations (CONOPS)

VPMS PDD v1.1 11/06/2008 CNIC Virtual Perimeter Monitoring System (VPMS)

Preliminary Design Document

VPMS System Spec v1.0 10/29/2008 (DRAFT) CNIC Virtual Perimeter Monitoring System

(VPMS) System Specification

2.2 Unified Facilities Guide Standards – http://www.wbdg.org/ffc/dod/unified-facilities-criteria-ufc

UFGS-26 00 00.00 20 07/2006 Basic Electrical Materials and Methods

UFGS-34 04/2008 Active Vehicle Barriers

2.3 Unified Facilities Criteria – http://www.wbdg.org/ffc/dod/unified-facilities-criteria-ufc

UFC 2-000-05N 01/01/1982 Facility Planning Criteria for Navy/Marine Corps Shore

Installations, Appendix E

UFC 3-501-01 10/06/2015 Electrical Engineering 2

UFC 3-520-01 02/03/2010 Interior Electrical Systems, with Change 2

UFC-3-580-01N 06/22/2007 Telecommunications Building Cabling Systems Planning and

Design

UFC 4-020-01N 09/11/2008 DoD Security Engineering Facilities Planning Manual

UFC 4-022-01 07/27/2017 Security Engineering: Entry Control Facilities/Access Control

Points

UFC 4-022-02 08/09/2010 Selection and Application of Vehicle Barriers, Change 1 http://www.wbdg.org/ffc/dod/unified-facilities-criteria-ufc http://www.wbdg.org/ffc/dod/unified-facilities-criteria-ufc

UFC 3-580-10 04/12/2005 NMCI Standard Construction Practices, with Changes 1-3

FC 1-300-09N 06/14/2018 Design Procedures, with Change 4

2.4 Industry Standards

ASIS GDL FPSM 06/08/2009 Facilities Physical Security Measures Guideline http://www.asisonline.org/guidelines/published.htm

ASTM F2656-15 2015 American Society for Testing and Measurement (ASTM)

Standard Test Method for Crash Testing of Vehicle Security

Barriers

CENELEC EN 70173-2.3,5 2007 European Cabling Standard – Information Technology, Data

Centers, Industrial Premises, Office Premises

ISO/IEC 11801 2010 International Standard for Structured Cabling Systems.

Edition 2, Amendment 2

J-STD-607-B 09/2011 Commercial Building Grounding and Bonding Requirements for Telecommunications

JTCG/ME-85-2 1986 Joint Technical Coordinating Group for Munitions

Effectiveness, Smoke and Natural Aerosol Parameters (SNAP)

Manual

MUTCD 2009 United States Department of Transportation (US DOT), Federal Highway Administration, Manual on Uniform Traffic

Control Devices (MUTCD) http://mutcd.fhwa.dot.gov/pdfs/2009/pdf.index.htm

NEMA 250 2014 Enclosures for Electrical Equipment (1000 Volts Maximum)

NFPA 70 2020 National Electrical Code

NFPA 70E 2018 Standard for Electrical Safety in the Workplace

NFPA 1221 2019 Standard for the Installation, Maintenance, and Use of

Emergency Services Communications Systems

NFPA 730 2018 Guide for Premises Security

NFPA 731 2017 Standard for the Installation of Electronic Premises Security

Systems

RaCM 1.1a 01/05/2010 Recording and Content Management http://www.psialliance.org/index.html

TIA/EIA-568-1D 09/2015 Commercial Building Telecommunications Cabling Standard

TIA/EIA-569-B 09/2012 Commercial Building Standard for Telecommunications

Pathways and Spaces

Note: For locations outside of the United States, the Contractor shall comply with equivalent standards from the Host

Nation as required. Examples standards that apply are European Union Standards (CE), Japanese Architectural

Standard Specifications (JASS), and Japanese Industrial Standards (JIS).

3.0 GENERAL REQUIREMENTS

The Navy’s overarching requirement for this contract is that AT/FP Ashore Systems remain in an operational and committable state to perform the function that the systems were designed, installed, and tested to do in order that they may be utilized to the fullest capacity at those critical moments in which they are needed to support the Navy’s mission.

This overarching requirement involves many aspects of planning, preparation, management and execution which are described in the following paragraphs.

http://www.asisonline.org/guidelines/published.htm http://mutcd.fhwa.dot.gov/pdfs/2009/pdf.index.htm http://www.psialliance.org/index.html

3.1 Management of Operational Availability (Ao)

Based on the statement of requirement expressed above, the most meaningful parameter for discussing the effectiveness of the sustainment effort is called Ao. This parameter relates the percentage of time that the system remains in an “operational and committable state” (i.e. “up-time”) to the amount of time that it is not (i.e. “down-time”). The same figure can also be used to predict the probability that the system is in an “operational and committable state” at any future moment, including those critical moments in which it is needed. Refer to

OPNAVINST 3000.12A, “Operational Availability Handbook, A Practical Guide for Military Systems, Sub-Systems and Equipment”, for a further explanation of Ao for calculation methods used by the NAVFAC AT/FP Ashore

Program.

The Contractor shall meet the Ao of the RDC and the J-NCR LMR System with a minimum threshold requirement of

99.95% (excluding planned maintenance as per paragraph 4.2.2 Preventive Maintenance Down-Time) as required by the National Fire Protection Association (NFPA) 1221 “Standard for the Installation, Maintenance and Use of

Emergency Services Communications Systems”. This figure requires the RDC and the J-NCR LMR System to remain free of Critical Priority outages that would obstruct the Navy mission, and thus render them “inoperable”, for 99.95% of the time (excluding planned maintenance as per paragraph 4.2.2 Preventive Maintenance Down-Time.) That calculates to a maximum amount of 4 hours and 23 minutes of down-time over the course of one calendar year

(excluding planned maintenance as per paragraph 4.2.2 Preventive Maintenance Down-Time.) All other NAVFAC

AT/FP Ashore Systems require an Ao of 90%, which calculates to a maximum allowable amount of 36.5 days of down-time during one calendar year due to a Critical Priority fault condition.

The Contractor shall plan and implement a Supportability Strategy as described in paragraph 4.1 Supportability

Strategy and DED A020 “Supportability Strategy” to achieve this level of Ao. Planning documents shall demonstrate how critical faults shall be prevented and should they occur, shall be detected, responded to, diagnosed, and corrected in a manner that achieves the required Ao.

This level of Ao as described requires the following Contractor action:

Positioning of replacement parts, qualified personnel, test equipment, etc., required to anticipate, quickly diagnose and effect repairs. This is especially important when parts problems are caused by higher than expected system usage resulting in higher parts failure rates and accompanying increases in parts inventory to meet demand, Create and execute a system of periodic inspections, confidence tests, and preventive maintenance that anticipates, identifies and corrects supportability problems before they occur and tracks system / component age, environmental conditions, modifications/upgrades, parts availability/obsolescence, analyze the entire System from end-to-end and make recommendations to prevent a failure or maintenance down-time from creating a critical system outage, Continuous analysis of fault histories and fault trends to proactively predict and mitigate repetitive issues, Develop and execute a configuration management and documentation process to include adherence to the NAVFAC AT/FP Ashore Configuration Management Plan, and participation in the CNIC Move, Add, and Change process, Develop and implement a methodology to track the evolution of technology, identify issues within the

NAVFAC AT/FP Ashore Program Systems associated with technology obsolescence, and develop solutions that avoid down-time and maximize the longevity of the NAVFAC AT/FP Ashore Program

Systems.

3.1.1 Calculation of Ao

System Operational Availability (Ao) is defined by the equation:

Ao = Up-time / (Up-time + Down-time)

It should be noted that “up-time” and “down-time” are, by definition, two mutually exclusive states and that, taken together, they represent the total amount of time. Therefore, the equation may also be expressed as follows:

Ao = Up-time / Total Time

Refer to OPNAVINST 3000.12A, “Operational Availability Handbook, A Practical Guide for Military Systems, Sub-

Systems and Equipment” for a more detailed explanation of the relationship of the values Mean Time Between Failures

(MTBF), Mean Time to Repair (MTTR), Mean Logistics Delay Time (MLDT), Mean Waiver/Extension Time (MWT) when calculating Ao.

Therefore, the calculation of Ao requires a determination of when the system is in an “Up” state, and therefore available for use, and when it is in a “Down” state, existing in a degraded capacity such to render it “unavailable” if needed.

For the purposes of planning and management of Operational Availability (Ao), the failures which would constitute system “down-time” shall be those classified as a Critical Priority as specified by the Priority Level definitions found in paragraph 4.3.1 Priority Level Assignments for System Fault Conditions.

3.1.2 Applicability of Ao in Contractor Execution

While Ao is the most accurate statement of the U.S. Navy requirement, there are often complications which prevent the use of Ao as an accurate metric for measurement of Contractor performance. While a 99.95% Ao threshold requirement permits a maximum of 4 hours and 23 minutes of down-time within one calendar year (excluding planned maintenance as per paragraph 4.2.2 Preventive Maintenance Down-time, there is rarely a definitive record of the exact moments that the systems enters a “down” state and is then restored to an “up” state. There may also be confusion as to the classification of a particular outage event as meeting the criteria of “down-time”.

For these reasons, Ao cannot be the sole determining factor of Contractor performance in the execution of this PWS.

It will be used only as an “order-of-magnitude” guideline to identify gross infractions of contractual requirements.

Instead, the paragraphs that follow in Section 4.0 will outline other measurement criteria such as Response Time and

Restoration Time which are more practical for managing the day-to-day sustainment operations under this PWS.

In spite of these practical limitations, the Contractor shall continue to plan and implement strategies using the achievement of Ao as the overarching strategic objective.

4.0 SPECIFIC REQUIREMENTS

This section details sustainment task requirements for the Contractor in execution of this PWS.

4.1 Supportability Strategy

The Contractor shall develop and implement a comprehensive, cost-effective Supportability Strategy for the covered

NAVFAC AT/FP Ashore Program Systems to ensure that the Systems described herein meet the mandated mission performance thresholds for Ao. The Supportability Strategy shall include the periodic maintenance, repair, replacement, and overhaul of existing NAVFAC AT/FP Ashore Program Systems, hardware, associated firmware, and software listed in Appendix C “List of Systems” and shall be prepared in accordance with DED A020

“Supportability Strategy”.

The Supportability Strategy shall include the Contractor’s approach to total lifecycle sustainment to include:

Locating replacement parts at forward supply points maintaining service shops to support Field

Level/Organizational Level maintenance activities and other logistical preparations.

Training, qualifying and strategically positioning qualified personnel and test equipment to quickly diagnose and effect repairs worldwide.

Clearing and disposal of environmental debris impacting system operation (e.g., dirt, leaves, grease, etc.).

Planning, performing, and documenting system confidence tests, periodic inspections, and preventive maintenance.

Identifying critical system operations and implementing strategies to prevent potential failures and administrative down-time from creating critical system outages.

Analyzing and maintaining Systems/Equipment fault histories and fault trends and translating the results into actionable real time information to enable the AT/FP Ashore Program to proactively predict and mitigate repetitive sustainment risks.

Tra…