N3943020R2245 Draft RFP.pdf

CODE

(Hour)

PAGE(S)

until local time

X

A X B X C

D

EX

X G F 38 - 44

45 - 52 X H 53 - 57 salvador.r.vargas1@navy.mil

RATING PAGE OF PAGES

7. ISSUED BY

(Date)

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

Previous Edition is Unusable 33-134 STANDARD FORM 33 (REV. 9-97)

Prescribed by GSA FAR (48 CFR) 53.214(c)

1 57

(If other than Item 7)

15A. NAME 16. NAME AND TITLE OF PERSON AUTHORIZED TO

AND

ADDRESS

SIGN OFFER (Type or print)

OF

OFFEROR

AMENDMENT NO. DATE

15B. TELEPHONE NO (Include area code) 17. SIGNATURE15C. CHECK IF REMITTANCE ADDRESS

IS DIFFERENT FROM ABOVE - ENTER

SUCH ADDRESS IN SCHEDULE.

18. OFFER DATE

1. THIS CONTRACT IS A RATED ORDER

UNDER DPAS (15 CFR 700)

2. CONTRACT NO.

N39430 8. ADDRESS OFFER TO

See Item 7

9. Sealed offers in original and 4 copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if handcarried, in the depository located in

CAUTION - LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and

Bldg. 1183, Pass and ID Office conditions contained in this solicitation.

10. FOR INFORMATION

CALL:

A. NAME (NO COLLECT CALLS)

SAL VARGAS 805-982-5095

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

3 - 19 J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

X K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 22 X

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror) 23 - 27 X M

L INSTRS., CONDS., AND NOTICES TO OFFERORS

EVALUATION FACTORS FOR AWARD

NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. DISCOUNT FOR PROMPT PAYMENT

(See Section I, Clause No. 52.232-8)

14. ACKNOWLEDGMENT OF AMENDMENTS

(The offeror acknowledges receipt of amendments

AMENDMENT NO. DATE

to the SOLICITATION for offerors and related documents numbered and dated):

FACILITY

12. In compliance with the above, the undersigned agrees, if this offer is accepted within calendar days (60 calendar days unless a different period

SOLICITATION, OFFER AND AWARD

X

(X) SEC. DESCRIPTION (X) SEC. DESCRIPTION PAGE(S)

PART I - THE SCHEDULE

26. NAME OF CONTRACTING OFFICER (Type or print) 27. UNITED STATES OF AMERICA 28. AWARD DATE

EMAIL:TEL: (Signature of Contracting Officer)

CODE CODE

B. TELEPHONE (Include area code) C. E-MAIL ADDRESS

AWARD (To be completed by Government)

19. ACCEPTED AS TO ITEMS NUMBERED 20. AMOUNT 21. ACCOUNTING AND APPROPRIATION

22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:

10 U.S.C. 2304(c)( ) 41 U.S.C. 253(c)( ) (4 copies unless otherwise specified)

23. SUBMIT INVOICES TO ADDRESS SHOWN IN ITEM

24. ADMINISTERED BY (If other than Item 7) CODE 25. PAYMENT WILL BE MADE BY CODE

PART IV - REPRESENTATIONS AND INSTRUCTIONS

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

28 - 35

PART II - CONTRACT CLAUSES

NAVFAC EXWC

CODE ACQ / NAVAL BASE VENTURA COUNTY

1100 23RD AVE BLDG 1100

PORT HUENEME CA 93043-4301

FAX:

TEL:

FAX:

TEL:

NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".

SOLICITATION

36 - 37

6. REQUISITION/PURCHASE NO.

ACQR3877725

5. DATE ISSUED4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

N3943020R2245

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

Global Sustainment of ATFP Systems

FFP

Provide labor, materials, and equipment to perform life-cycle sustainment services for ATFP Ashore equipment worldwide in accordance with the Operational Availabilities (Ao) specified in the PWS. Work includes preventive and corrective maintenance, repair and replacement, services calls, and systems/software upgrades.

FOB: Destination

PURCHASE REQUEST NUMBER: ACQR3877725

NET AMT

Section C - Descriptions and Specifications

PERFORMANCE WORK STATEMENT

1. GENERAL

This is a non-personnel services contract to provide sustainment of Anti-Terrorism Force Protection Systems and Assets, worldwide. The Government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Contractor who, in turn is responsible to the Government.

1.1 INTRODUCTION

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 contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform sustainment of Anti-Terrorism Force Protection Systems and Assets, worldwide.

1.2 BACKGROUND

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 Navy Systems Commands, 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.

1.3 OBJECTIVE

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.

1.4 SCOPE OF THE CONTRACT

The scope of the contract includes the sustainment of ATFP systems and assets, programatic support of Information Assurance requirements, technological refreshment and upgrades, disposal of old systems, and performance of repairs caused by third-party damage or acts of God. Sustainment includes Corrective Maintenance, Preventative Maintenance, and response to service calls. The systems to be sustained under this contract includes systems that are currently in place, systems that may be constructed or installed in the future and require sustainment after expiration of the warranty period, or new ATFP systems currently under development that may be fielded at a later date. The types of systems to be sustained or services to be provided include, but are not limited to, the following:

1.4.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.

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

1.4.1.1.1 Communications

1.4.1.1.1.1.Emergency Land Mobile Radio (ELMR)

1.4.1.1.2 Operations Centers

1.4.1.1.2.1 Regional Operation Centers (ROC)

1.4.1.1.2.2 Emergency Operation Centers (EOC)

1.4.1.1.3 Dispatch Centers

1.4.1.1.3.1 Regional Dispatch Centers (RDC)

1.4.1.1.3.2 Local Dispatch Centers (LDC)

1.4.1.1.3.3 Continuity Data Centers (CDC)

1.4.1.1.3.4 Sensor Assessment Cells (SAC)

1.4.1.1.4 Mass Notification Systems

1.4.1.1.4.1 Giant Voice/Indoor Voice (GV/IV)

1.4.1.1.4.2 Net Centric Mass Notification system (NMS)

1.4.1.1.4.3 Emergency 911 Telephone

1.4.1.1.4.4 Computer Desktop Notification System (CDNS)

1.4.1.2 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:

1.4.1.2.1 Antennas (including Microwave Dishes and cabling)

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

1.4.1.2.3 Repeaters

1.4.1.2.4 Zone Cores at Regional Dispatch Center

1.4.1.2.5 Channel Banks

1.4.1.2.6 Radio Dispatch Work Stations

1.4.1.2.7 Encryption Key Management Client Work Stations

1.4.1.2.8 Radio System Management Client Work Stations

1.4.1.2.9 Microwave Links

1.4.1.2.10 Multiplexers

1.4.1.2.11 Radio Gateways at Dispatch Centers

1.4.1.3 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.4.1.4 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 continental United States (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.

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

1.4.1.4.1.1 Alarm Monitoring & Automation

1.4.1.4.1.1.1 Regional Alarm Monitoring & Automation System (RAMAS)

1.4.1.4.1.1.2 Local Alarm Monitoring & Automation System (LAMAS)

1.4.1.4.1 1.3 Alarm front end / field panels / alarm receivers / head end panels feeding to LAMAS or alarm receiver panels

1.4.1.4.1.1.4 Designated alarm points such as Navy Munitions Command (Class I and II)

1.4.1.4.1.2 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.

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

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

1.4.1.4.1.2.1 RMS connectivity to National Fire Incident Reporting System (NFIRS) and Consolidated Law Enforcement Operations Center (CLEOC)

1.4.1.4.1.3 Integrated National Crime Information Center (NCIC) Lookup

1.4.1.4.1.3.1 Integrated Fire Station Alerting in CAD

1.4.1.4.1.3.1.1 Local Mobile Data Computer (MDC) with WiFi Hotspot connectivity

1.4.1.4.1.4 Physical Security Information Management (PSIM)

1.4.1.4.1.1.5 Voice Recorders for 911 Telephone and Radio Traffic

1.4.1.4.1.1.6 Enterprise Land Mobile Radio (ELMR)

1.4.1.4.1.1.7 Sensor Management Display System

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

1.4.1.5 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.

1.4.1.5.1 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.

1.4.1.5.2 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.

1.4.1.5.3 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.4.1.5.4 Emergency 911 Telephone

1.4.1.5.5 Computer Desktop Notification System (CDNS)

1.4.1.6 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.

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.

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

1.4.1.6.1.1 Access Control Points (ACPs)

1.4.1.6.1.1.1 Vehicle Gates (VGs)

1.4.1.6.1.1.1.1 Active Vehicle Barriers (AVB)

1.4.1.6.1.1.1.2 Multi-Mode AVBs (M-AVB)

1.4.1.6.1.2 Automated Vehicle Gates (AVGs)

1.4.1.6.1.2.1 Automated Vehicle Gate – Enclave (AVG-E)

1.4.1.6.1.2.2 Automated Vehicle Gate – Low Volume (AVG-L)

1.4.1.6.1.2.3 Automated Vehicle Gate – High Volume (AVG-H)

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

1.4.1.6.1.3 Pedestrian Gates (PGs)

1.4.1.6.1.3.1 Automated Pedestrian Turnstiles (APT)

1.4.1.6.1.4 Electronic Security Systems (ESSs)

1.4.1.6.1.4.1 Airfield Enclave

1.4.1.6.1.4.2 Perimeter Enclave

1.4.1.6.1.4.3 Pier Enclave

1.4.1.6.1.4.4 Building Enclave

1.4.1.6.1.4.5 NMC Enclave

1.4.1.6.1.4.6 Tenant Systems

1.4.1.6.1.5 Waterside Security Systems

1.4.1.6.1.5.1 Electronic Harbor Security System (EHSS)

1.4.1.6.1.5.2 Waterside Defensive System (WDS)

1.4.1.6.1.6 Inspection Systems

1.4.1.6.1.6.1 Personnel Inspection System

1.4.1.6.1.6.2 Vehicle Inspection System

1.4.1.6.1.7 Physical Security Information Management (PSIM) System

1.4.1.6.1.8 Physical Security Access Control- Enterprise Architecture (PSAC-EA)

1.4.1.6.1.9 Counter Unmanned Aerial System (C-UAS)

1.4.1.7 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.

1.41.8 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.

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.4.1.9 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:

1.4.1.9.1 Automated License Plate Reader (ALPR) System

1.4.1.9.2 Active Vehicle Barriers/Drop Arms/Turnstiles

1.4.1.9.3 Closed Circuit Television (CCTV) Camera Systems

1.4.1.9.4 Network Video Recorder (NVR)

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

1.4.1.9.6 Dynamic Message Signs (DMS)

1.4.1.9.7 Gate Automation Systems

1.4.1.9.8 Intercom Systems

1.4.1.9.9 Physical Access Control Systems (PACS)

1.4.1.9.10 Vehicle Presence Sensors

1.4.1.9.11 Physical Security Information Management (PSIM) system

1.4.1.9.12 Badging/Enrollment

1.4.1.9.13 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).

1.4.1.9.14 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.

1.4.1.9.15 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).

1.4.1.9.16 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.4.1.10 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.

1.4.1.11 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.4.1.12 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:

1.4.1.12.1 Physical Access Control Systems (PACS)

1.4.1.12.2 Access Control (Card Readers, Intercoms, and Keypads)

1.4.1.12.3 Closed Circuit Television (CCTV) / Camera Systems

1.4.1.12.4 Network Video Recorder (NVR)

1.4.1.12.5 Intrusion Detection Systems (IDSs)

1.4.1.12.6 Virtual Perimeter

1.4.1.12.6.1 Video Analytics

1.4.1.12.6.2 Sensors, Sensor Management, Sensor Analytics

1.4.1.12.7 Physical Security Information Management (PSIM) system

1.4.1.12.8 Badging/Enrollment

1.4.1.13 Waterside Security Systems

1.4.1.13.1 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:

1.4.1.13.1.1 Detect and track surface targets

1.4.1.13.1.2 Detect and track subsurface targets

1.4.1.13.1.3 Automatically alert based on security criteria

1.4.1.13.1.4 Aid security forces with assessment, interdiction, response and warning

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

1.4.1.13.1.6 Physical Security Information Management (PSIM) system

1.4.1.13.2 Waterside Defensive System (WDS)

WDSs provide standoff, detection and interdiction for protection of afloat naval assets in port. They provide an assertive, scalable, and dynamic system-of-systems that provide a measured response.

1.4.1.14 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.4.1.15 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.

1.4.1.15.1 PSIM functionality includes the following:

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

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

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

1.4.1.15.1.4 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.

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

1.4.1.15.1.6 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.

1.4.1.15..2 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.4.1.16 Physical Security Access Control- Enterprise Architecture (PSAC-EA) PSAC-EA provides a unified, hardened platform hardware infrastructure in support of the suite of ATFP IT systems.

The enterprise architecture will allow for centralized command and control, monitoring, management, update, maintenance and response.

1.4.1.17 Counter Unmanned Aerial System (C-UAS)

C-UAS systems provide interdiction capabilities for protection of personnel and naval assets on installations and in port. C-UAS are designed to disrupt and neutralize Unmanned Aerial Vehicles (UAVs), or drones, engaged in hostile airborne surveillance and potentially malicious activity. C-UASs include both fixed and mobile systems.

1.4.1.18 Enterprise System Administration and Cybersecurity Administration Support The major elements include:

1.4.1.18.1 Version Control

1.4.1.18.2 Patch Management

1.4.1.18.3 Vulnerability Scanning

1.4.1.18.4 Signature File Updates

1.4.1.18.5 Support for CNIC Security Monitoring

1.4.1.18.6 Region/Local System Administration which includes:

1.4.1.18.6.1 Standard user account troubleshooting

1.4.1.18.6.1 Regional database input

1.4.1.18.6.3 RDC/LDC Patch installation

1.4.1.18.6.4 RDC/LDC to user workstation communications troubleshooting and maintenance

1.4.1.18.2 The following enterprise positions may be required:

1.4.1.18.2.1 Enterprise System/Network/Active Directory Administration Includes:

1.4.1.18.2.1.1 Domain maintenance and administration

1.4.1.18.2.1.2 Active directory policy

1.4.118.2.1.3 Virtual host maintenance

1.4.1.18.2.1.4 Virtual host resource allocation

1.4.1.18.2.1.5 Enterprise database maintenance and support

1.4.1.18.2.1.6 Windows Server Update Service (WSUS) patch repository maintenance

1.4.1.18.2.1.7 Network device maintenance at SDPs and RDCs for enterprise communications maintenance

1.4.1.18.2.1.8 Ongoing STIG Compliance

1.4.1.19 RMF Information Security System Professionals (ISSPs)

ISSPs perform Risk Management Framework (RMF) support for Accreditation Steps 1 through Step 4 and Step 6 (beyond accreditation) throughout the systems cyber security lifecycle. The contractor will provide Information Assurance/Cybersecurity (IA/CS) support including testing, mitigation, annual IA/CS compliance, sustainment, vulnerability and risk management, system engineering support, and preparation, processing, and submission of Assessment and Authorization (A&A) packages in accordance with the references in DED A042 “Cybersecurity and System Administration”. AT/FP Ashore requires a sufficient number of ISSPs to support all Commander, Naval Installations Command (CNIC) and Naval Facilities Engineering Command (NAVFAC) Anti-Terrorism/Force Protection (AT/FP) Command, Control, Communications, Computers, and Intelligence (C4I), Physical Security Access Control (PSAC), and Energy systems.

1.4.1.19.1 The ISSP's should work with the A&A package owners and AT/FP Ashore Cyber Security Managers/Officers and provide all levels of documentation and oversight of cyber-security requirement support throughout the Risk Management Framework (RMF) Step 1 through Step 4 and Step 6 (beyond accreditation) throughout the systems cyber security lifecycle for the packages listed. Actions related to RMF Step 1 through Step 4 and Step 6 include, but are not limited to:

1.4.1.19.1.1 RMF Step 1:

1.4.1.19.1.1.1 Establishment of RMF Security Plan in eMASS.

1.4.1.19.1.1.2 Support detailing mission requirements as part of NAVFAC CyberSafe grading determination process.

1.4.1.19.1.2 RMF Step 2

1.4.1.19.1.2.1 Drafting of Architecture, Boundary, and Dataflow diagrams.

1.4.1.19.1.2.2 Inventory and documentation of hardware/software/firmware within assessment boundary.

1.4.1.19.1.2.3 Development of Continuous Monitoring Strategy.

1.4.1.19.1.2.4 Security Control Tailoring including establishment of inheritance models with key security service providers (PSNet-T, C2SOC, PSAC EA).

1.4.1.19.1.2.5 Completion of eMASS Implementation Plan based on Continuous Monitoring Strategy.

1.4.1.19.1.2.6 Assist assigned Validator in drafting the RMF Security Assessment Plan.

1.4.1.19.1.2.7 Support all key stakeholders during RMF Step 2 Concurrence process.

1.4.1.19.1.3 RMF Step 3

1.4.1.19.1.3.1 100% execution of the approved Security Assessment Plan provided from RMF Step 2 Concurrence Checkpoint which includes-

1.4.1.19.1.3.1.1 Perform ACAS automated vulnerability scans on all assets with-in assessment boundary and establish hardened baseline configuration with consistent, repeatable successful results.

1.4.1.19.1.3.1.2 Documentation of DISA STIG compliance utilizing SCAP scripts to provide detailed analysis of security vulnerabilities present on AT/FP IT solutions.

1.4.1.19.1.3.1.3 Analysis and results of NIST SP 800-52 rev. 4 Assessment Procedures and support documentation as evidence of compliance.

1.4.1.19.1.4 RMF Step 4

1.4.1.19.1.4.1 Serve as an IT Security subject matter expert supporting the Validator during on-site Independent Validation and Verification (IV&V) of AT/FP IT solutions.

1.4.1.19.1.4.2 Provide process improvement of the overall control implementation of AT/FP IT solutions.

1.4.1.19.1.5 RMF Step 6

1.4.1.19.1.5.1 Execute and review weekly ACAS scans and upload results into VRAM/CMRS.

1.4.1.19.1.5.2 Maintain the RMF POA&M to accurately portray the risk posture of AT/FP IT Solutions.

1.4.1.19.1.5.3 Detail all relevant changes to IT assets for AT/FP IT solutions through the NAVFAC AT/FP Change Management Process.

1.4.1.19.1.5.4 Detail all relevant mitigation and remediation activities to vulnerabilities noted on the RMF POA&M through the NAVFAC AT/FP Change Management Process.

Monitor HW/SW lifecycles and provide recommendation for upgrade/sustainment to NAVFAC AT/FP leadership.

1.4.1.19.1.5.5 Execute STIG/SCAP updates quarterly for relevant changes to risk posture.

1.4.1.19.1.5.6 Update all RMF documentation based on change and vulnerability management efforts.

1.4.1.19.1.5.7 Provide incident response capability for AT/FP IT solutions.

1.4.1.19.1.5.8 Perform continuous security reviews of RMF Security Controls (1 security control family each month).

1.4.1.19.1.5.9 Respond to risk based on the results of ongoing monitoring activities, risk assessments, and outstanding items in the plan of action and milestones. This may include installing patches in accordance with the established ATFP Ashore configuration change control process.

1.4.1.20 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.

Table 1 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

Navy Region Korea

1.5 GENERAL INFORMATION

1.5.1. Quality Control

The contractor shall develop and maintain an effective quality control program (QCP) to ensure services are performed in accordance with the task order PWS. The contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The contractor’s quality control program is the means by which the contractor assures that work complies with the requirement of the contract. Individual Task Orders will designate the submission requirements for the QCP.

1.5.2 Quality Assurance

The government shall evaluate the contractor’s performance under the task orders in accordance with the task order’s Quality Assurance Surveillance Plan. This plan is primarily focused on what the Government must do to ensure that the contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable quality levels.

1.5.3 Recognized Holidays

All or a portion of the effort under this contract will be performed on a Government installation. Listed below are the holidays observed by the Federal Government. The Contractor, generally, will not be allowed to work on the government installation on these days.

NAME OF HOLIDAY TIME OF OBSERVANCE

New Year’s Day 1 January Martin Luther King, Jr. Day Third Monday in January President’s Day Third Monday in February Memorial Day Last Monday in May Independence Day 4 July Labor Day First Monday in September Columbus Day Second Monday in October Veteran’s Day 11 November Thanksgiving Day Fourth Thursday in November Christmas Day 25 December

1.5.4 Hours of Operation

The contractor is responsible for conducting business, between the normal operating hours of the individual installations. Normal operating hours are typically hours 7:30am to 4:00pm, Monday thru Friday except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. The Contractor must at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed for the above reasons. When hiring personnel, the Contractor shall keep in mind that the stability and continuity of the workforce are essential.

1.5.5 Place of Performance

The work to be performed under this contract will be performed world-wide.

1.5.6 Type of Contract

Task orders issued under this contract will be firm fixed price.

1.6 CONTRACTOR PERSONNEL REQUIREMENTS

All personnel performing on this contract will be U.S. citizens. CNIC requires all Contractor personnel working on the Federally-controlled facility to have, at a minimum, an initiated National Agency Check with Written Inquiries (NACI=T1) or NACI equivalent and favorable completion of a Federal Bureau of Investigation (FBI) fingerprint check.

1.6.1In accordance with Department of Defense (DoD) Regulation 5200.2-R, Personnel Security Programs, all DoD Contractor personnel who have access to Federally-controlled information systems must be assigned to positions which are designated at one of three information technology (IT) levels, each requiring a certain level of investigation and clearance, as follows:

1.6.1.1 Critical Sensitive=IT-I for an IT position requiring a single scope background investigation (SSBI=T5) or SSBI equivalent. This designation encompasses privileged user accounts for networks and systems encompassed under this PWS, often referred to as “administrator” or “sys admin” accounts;

1.6.1.2. Non-Critical Sensitive =IT-II for an IT position requiring a National Agency check with Law and Credit (NACLC=T3) or NACLC equivalent; and

1.6.1.3 Non Sensitive=IT-III for an IT position requiring a T1 or equivalent.

Note: ALNAV 005/16 implemented the tiered investigation system renaming NACI to T1, NACLC to T3, and SSBI to T5.

1.6.2 Previously completed security investigations may be accepted by the Government in lieu of new investigations if determined by the CNIC Personnel Security Office to be essentially equivalent in scope to the contract requirements. The length of time elapsed since the previous investigation will also be considered in determining whether a new investigation is warranted, as outlined in SECNAV M-5510.30, Exhibit 5A. To assist the

Government in making this determination, the Contractor must provide the following information to the respective Personnel Security Office immediately upon receipt of the contract. This information must be provided for each Contractor employee who will perform work on a Federally-controlled facility and/or will require access to Federally-controlled information systems:

1.6.2.1 Full name, with middle name, as applicable, with social security number;

1.6.2.2 Citizenship status with date and place of birth;

1.6.2.3 Proof of the individual’s favorably adjudicated background investigation or T1, consisting of identification of the type of investigation performed, date of the favorable adjudication, name of the agency that made the favorable adjudication, and name of the agency that performed the investigation;

1.6.2.4 Company name, address, phone and fax numbers with email address;

1.6.2.5 Location of on-site workstation or phone number if off-site (if known by the time of award); and

1.6.2.6 Delivery order or contract number and expiration date; and name of the Contracting Officer.

1.6.3 The Contracting Officer will ensure that the Contractor is notified as soon as a determination is made by the assigned or cognizant CNIC Personnel Security Office regarding acceptance of the previous investigation and clearance level.

1.6.3.1. If a new investigation is deemed necessary, the Contractor and Contracting Officer will be notified by the respective CNIC Personnel Security Office after appropriate checks in DoD databases have been made.

1.6.3.2 If the Contractor employee requires access to classified information and currently does not have the appropriate clearance level and/or an active security clearance, the Personnel Security Office will relay this information to the Contractor and Contracting Officer for further action. Investigations for Contractor employees requiring access to classified information must be initiated by the Contractor Facility Security Officer (FSO).

1.6.3.3 It is the Contractor’s responsibility to ensure that adequate information is provided and that each Contractor employee completes the appropriate paperwork, as required either by the Contracting Officer or the Personnel Security Office, in order to begin the investigation process for the required clearance level.

1.6.4 The Contractor is responsible for ensuring that each Contractor employee assigned to the position has the appropriate security clearance level.

1.6.5 The Contractor shall submit each request for IT access and investigation through the Contracting Officer to the assigned or cognizant Personnel Security Office. Requests shall include the following information and/or documentation:

1.6.5.1 Standard Form (SF) 85, Questionnaire for Non-Sensitive Positions, or the SF 86, Questionnaire for National Security Positions (see note below);

1.6.5.2 Proof of citizenship (i.e., an original or a certified copy of a birth certificate, passport, or naturalization certificate); and

1.6.5.3 Form FD-258, Fingerprint Card

Note: to 1.6.5.1 above: An investigation request is facilitated through use of the SF 85 or the SF 86. These forms with instructions as well as the Optional Form (OF) 306, Declaration for Federal Employment, which is required with submission of the SF85 or SF 86, are available at the Office of Personnel Management’s (OPM) system called Electronic –Questionnaires for Investigations Processing (e-QIP). Hard copies of the SF85 and SF86 are available at OPM’s web-site, http://www.opm.gov, but hard copies of the forms are not accepted.)

1.6.6 Required documentation, listed above in paragraphs 1.6.7.5.1 through 1.6.7.5.3, must be provided by the Contractor as directed by the Contracting Officer to the cognizant Personnel Security Office at the time of fingerprinting or prior to the Personnel Security Office releasing the investigation to OPM.

1.6.7 Upon completion of the T1, T3, T5, or other sufficient, appropriate investigation, the results of the investigation will be forwarded by OPM to the appropriate adjudication facility for eligibility determination or the CNIC Personnel Security Office for review and determination regarding the applicant’s suitability to occupy an unescorted entry position in performance of the contract. Contractor personnel shall not commence work on this effort until the investigation has been favorably adjudicated or the Contractor employee has been waived into the position pending completion of adjudication. The Personnel Security Office will ensure that results of investigations will be sent by OPM to the Department of Defense, Consolidated Adjudications Facility (DoD CAF) or Personnel Security Office.

1.6.8 A waiver for IT level positions to allow assignment of an individual Contractor employee to commence work prior to completion of the investigation may be granted in emergency situations when it is determined that a delay would be harmful to national security. A request for waiver will be considered only after the Government is in receipt of the individual Contractor employee’s completed forms, the background investigation has been initiated and favorable FBI fingerprint check has been conducted. The request for a waiver must be approved at the Flag/SES level. The cognizant Personnel Security Office reserves the right to determine whether a waiver request will be forwarded for processing. The individual Contractor employee for which the waiver is being requested may not be assigned to a position or physically work at the Federally-controlled facility and/or be granted access to Federally-controlled information systems, until the waiver has been approved.

1.6.9 The requirements of this clause apply to the prime Contractor and any subcontractors the prime Contractor may employ during the course of this contract, as well as any temporary employees that may be hired by the Contractor. The Government retains the right to request removal of Contractor personnel, regardless of prior clearance or adjudication status whose actions, while assigned to this contract, who are determined by the Contracting Officer to conflict with the interests of the Government. If such removal occurs, the Contractor shall assign qualified personnel, with the required investigation, to any vacancy.

1.6.10 All Contractor personnel who are granted access to Government and/or Federally-controlled information systems shall observe all local automated information system (AIS) security policies and procedures. Violations of local AIS security policy, such as password sharing, performing personal work, file access violations, or browsing files outside the scope of the contract, will result in removal of the Contractor employee from Government property and referral to the Contractor for appropriate disciplinary action. Actions taken by the Contractor in response to a violation will be evaluated and will be reflected in the Contractor’s performance assessment for use in making future source selection decisions. In addition, based on the nature and extent of any violations of AIS security policy, the Government will consider whether it needs to pursue any other actions under the contract such as a possible termination.

1.6.10.1 The Contractor may also be required to obtain a Common Access Card (CAC) or Installation Access Badge for each Contractor employee in accordance with procedures established by CNIC. When a CAC is required, the Contracting Officer will ensure that the Contractor follows the requirements of Homeland Security Presidential Directive 12 and any other CAC-related requirements in the contract. The Contractor shall provide, on a monthly basis, a listing of all personnel working under the contract that have CACs.

1.6.11 Contractor personnel must additionally receive operations security (OPSEC) and information security (INFOSEC) awareness training. The CNIC annual OPSEC refresher training and CNIC annual INFOSEC training will satisfy these requirements and are available through the CNIC Security Office.

1.6.12 When a Contractor employee who has been granted a clearance is removed from the contract, the Contractor shall provide an appropriately trained substitute who has met or will meet the investigative requirements of this clause. The substitute may not begin work on the contract without written documentation, signed by the Contracting Officer, stating that the new Contractor employee has met one of the criteria set forth in paragraphs 1.6.2, 1.6.3, or

1.6.8 of this clause, (i.e., acceptance of a previously completed security investigation, satisfactory completion of a new…