DRAFT SOW - Flightline Access Control System - 21July.pdf

STATEMENT OF WORK (SOW)

JB MDL IP BASED FLIGHTLINE ACCESS CONTROL

INSTALLATION WITH CAMERAS AND

MAINTENANCE SERVICE AGREEMENT

JOINT BASE MDL, NEW JERSEY

21 July 2026

1.0 PROGRAM OBJECTIVES: Install and integrate the contractor supplied server using appropriate Access Control Management with the corresponding VMS and Server Management Software for the combined access control and camera system. All components must be Section 889 of the 2019 NDAA Compliant, provide integrated analytic capabilities as part of the standard system and upon completion the system must be FIPS 140-2 compliant. A second line item will be included in the contractor response to reflect an annual camera and server maintenance agreement price for this server and associated equipment to be included in the purchased in 2026. The government will also follow the guidance of E.O.

14005 (25 Jan 21) when selecting a successful vendor. The “system” of cameras and access control WILL operate on 40-bit encryption utilizing the Common Access Card (CAC) at the readers, based on a “swipe and go” premise with no biometrics or PIN required. Each subordinate unit will have a network connection to enroll their own unit personnel. The system will have separate levels of access that allow the highest level (Admin) to remotely open/close gates and a lower-level user that is able to view the gates with no ability to manipulate the gates. The Administrator Accounts (SFS, FES, Command Post/MOC and Freight Terminal) will have the ability to remotely open/close gates independently for emergency response either through pulse or continual. Multi Head cameras will be capable of monitoring the keypads and the gate status.

2.0 Requirements: Purchase, install and integrate sixteen (16) access control points (see Attch 1), (16) multi-head cameras and one appliance (server) that will be installed within the 87th Communications Squadron Server Facility. The brand specified to reduce training and management processes for this project is Motorola as it is compatible with the camera system that is currently in use on the flightline and base access points. This is also the system used by the units within JBMDL through the 87th SFS. Motorola is also the system known within the 87th CS for the camera configuration and appliance as they require no additional configuration changes for network configuration. Motorola is also the only access control system that can connect and annunciate via the AMC LMR Core ATO. The contractor will not utilize 2019 NDAA prohibited items within their company. Server specifications and capabilities will be verified by the 87th Communications Sq. On-going service maintenance contract outlines are included within section 4.0. Each access control point (gate) will require remote access control hardware and a camera to monitor access activity. The contractor will be required to administer security checks and settings to the appliance (STIGs) to the management appliance, specified as an UA-APP-ENT-7. The contractor will install each location hardware up to the network switch and then STOP, not touching or accessing any network switch or government network component. Cameras MUST be delivered to the 87th Communications Squadron at least (7) business days prior to the start of installation, these cameras will be configured by 87th Communications Squadron prior to initiation of project installation. Video encryption is mandated, as is CAC log-in to system monitoring, FIPS 140- 2 encryption for the video is the current minimum level accepted.

2.1. Site Visit: All site visits will be conducted with members of the 87th SFS Resource Protection Office along with the 87th Contracting Squadron Staff and be conducted only for contractors shown to be capable of meeting the Program Objectives (#1 above) and the Requirements (#2 above).

2.2. Execution: Implementation and execution may be from either of the CLINS options identified in #1 above as the appliance purchase, setup and install or as #2 for the appliance maintenance or either one individually. All submittals will identify CLINS-1 as the appliances, cameras/access control and CLINS-2 as the maintenance agreement with individual pricing shown for each. Any price discounts provided for execution of both line items combined will be shown separately underneath the requested pricing. The purchaser may choose any of the below CLINS.

2.2.1. CLIN-1 (87th): Listed below with the requirements in section 2.0.

• Vehicle gate #6 by 4401 (Marines),

• Vehicle gate #9 by Bldg. 3333 (108).

• Vehicle gate #13 by Bldg.. 3370 (108),

• Vehicle gate #21 by Bldg. 2218,

• Vehicle gate #27 by Bldg. 1757 (APS inbound),

• Vehicle gate #32 by Bldg.. 1757 (APS outbound),

• Vehicle gate #34 by Bldg. 1731 (305 Wing HQ),

• Vehicle gate #37 by Bldg.. 1809

• Vehicle gate #41 by Bldg. 1819, and

• PD gate #25 between Bldgs. 2201 and 2202.

2.2.2. CLIN-2 (305th): Pedestrian Gates listed below with the same requirements in 2.0

• Pedestrian Gate #11 (between Bldgs. 3335 / 3333, 108th side)

• Pedestrian Gate #24 (by Bldg. 2201)

• Pedestrian Gate #26 (adjacent to Bldg. 2253)

• Pedestrian Gate #29 (into APS compound)

• Pedestrian Gate #30 (exit side of APS compound)

• Pedestrian Gate #42 (by Bldg. 1819)

2.2.3. CLIN-3: Multi-year Maintenance of the installed items

3.0. Installation: This appliance installation will include all related equipment to comprise an integrated video and access control suite utilizing US Air Force approved hardware;

successful installation testing and Government acceptance of the system through the STIG process. The appliance will be installed into government furnished enclosures. ALL cameras to be used on this project will be delivered to the 87th CS/Network Ops at least one week prior to commencement of system installation for configuration into the network, this is a government mandated procedure.

3.1.The contractor shall install the appliance in existing a government provided protective housing in the facility as specified by the 87th Communications Squadron.

3.0.1. The infrastructure shall utilize the JB MDL NIPRNET Backbone with fiber/power installed by the government and available at each gate location. This is a JB MDL customer mandated requirement. The RMF Hardening Guide must also be provided to the system FSA upon completion of installation/testing.

3.0.2. The contractor shall utilize existing government hardware and infrastructure currently in working order (except non-NDAA compliant parts) that can be used. The contactor shall identify any existing government assets that cannot be made compatible with the access control/video system during the Contractor’s Site Walk and submitted Proposal. The site walk will be coordinated through the 87 SFS/ESS. Camera mounting poles, gate control boxes and power/fiber are currently in place at each proposed location.

3.2. The Contractor’s Proposal shall identify response times to warranty-related system outages or issues and whether the issue will be addressed remotely (phone or email) or by a technician coming on-site. Government accepted minimums are shown in Table 1-1 of this SOW.

3.2.1 The contractor shall include for the appliance install, as an attachment to the Contractor’s Proposal, a Gantt chart schedule in (at a minimum) Adobe Reader .pdf format, and the original format, that details their entire effort from contract award to leaving JB MDL after completion.

3.3. The contractor will utilize components that can integrate into the existing ACC-7 VMS that is currently in use.

3.4. The contractor shall provide any electrical work needed to complete the installation and integration that involves system power into the system.

3.5. The contractor shall provide any other ancillary utility work and shall coordinate with the 87

SFS, who will then coordinate with any other appropriate JB MDL agency on base.

3.6. The contractor will provide FSA, Administrator/Trainer and primary operator training at no additional cost, either through their company or coordinated through the manufacturer. On-line training is sufficient for primary operator training.

4.0. Service/Maintenance Support:

The contractor will provide routine preventative maintenance work as outlined by the camera and server manufacturers at the prescribed intervals to maintain a functional and secure

VMS.

4.1. Response to outages will be required as outlined in Table 1-1 below:

TABLE 1-1

Response Time Thresholds (Warranty Repairs)

Performance Metric PL Levels Contractor Notified

Contractor on-site

Restore Service:

(Restore or Replace

Scheduled)

Server/Complete System Failure 1 Hour 8 Hours or next duty day

24 Hours

Major Malfunction (MF)

*More than 50% of system not viewable

1 Hour

Mon-Thurs: 24 Hours Except on

Weekends/Federal Holidays: Next Business Day

48 Hours

Minimum restoration to 25% outage

Partial Failure (PF)

*More than 25% of system not viewable

1 Hour Mon-Fri: 24 Hours

Except on:

Weekend/Federal Holidays: Next

Duty Day

48 Hours

4.1.1. Deviations from table 1-1 will be coordinated through the 87th SFS/ESS Program Manager.

4.1.2. Maintenance work will restore camera/system functionality and retain all Information Assurance requirements covered in this SOW.

4.1.3. In the event the contractor is unable to fully return the system to 100% capabilities due to parts-on-hand being unavailable, a copy of the equipment order will be supplied to the government POC.

5.0. INFORMATION ASSURANCE:

Note: Since the customer has mandated the use of the base fiber as the primary backbone infrastructure for this system the following DIACAP requirements are mandated with no exclusions.

5.1. INFORMATION ASSURANCE DOCUMENTS

The new system shall comply with the following DoD policy documents or latest versions (http://iase.disa.mil provides the latest version of the following DoD documents and STIGs):

• DoD Directive 5000.1, The Defense Acquisition System (ref (a), (j), and (k)).

• Department of Defense Directive (DoDD 8500.1, Information Assurance (IA).

• Department of Defense Instruction (DoDI 8500.2, Information Assurance (IA)

Implementation.

• 10 U.S.C. Section 2224, Defense Information Assurance Program.

• Office of Management and Budget Circular A-130, Appendix III, Management of

Federal Information Resources.

• AFI 33-202V1, Network and Computer Security, 03 February 2006.

• Database STIG, Version 7, Release 2, 30 November 2005.

• Network Infrastructure STIG, Version 6, Release 4, 16 December 2005.

• UNIX Security STIG, Version 4, Release 4, 15 September 2003.

• WEB Server STIG, Version 5, Release 1, 29 October 2004.

• WINDOWS NT/2000/XP Addendum, Version 5, Release 1, 29 August 2005.

5.2. INFORMATION ASSURANCE SUPPORT REQUIREMENTS

DoDD 8500.1 states “Information assurance requirements shall be identified and included in the design, acquisition, installation and operation, upgrade, or replacement of all DoD information systems in accordance with 10 U.S.C. Section 2224, Office of Management and Budget Circular A-130, Appendix III, DoD Directive 5000.1 (reference (a), (j) and (k)), DoDD 8500.1 and DoDI 8500.2, and other IA related DOD and Air Force regulations and guidance as issued.

All DoD information systems shall maintain an appropriate level of confidentiality, integrity, authentication, non-repudiation, and availability that reflect a balance among the importance http://iase.disa.mil/ and sensitivity of the information and information assets; documented threats and vulnerabilities, the trustworthiness of users and interconnecting systems; the impact of impairment or destruction to the DoD information system; and cost effectiveness.

Interoperability and integration of IA solutions within supporting the Department of Defense shall be achieved through adherence to an architecture that will enable the evolution to network centric warfare by remaining consistent with the Command, Control, Communications, Computers, Intelligence, Surveillance, Reconnaissance Architecture Framework, and a defense-in-depth approach. This combination produces layers of technical and non-technical solutions that: provide appropriate level of confidentiality, integrity, authentication, non-repudiation, and availability; defend the perimeters of enclaves; provide appropriate degrees of protection to all enclaves and computing environments; and make appropriate use of supporting IA infrastructures, to include robust key management and incident detection and response.”

The contractor shall incorporate all applicable technical, procedural, and system documentation associated with federal, Department of Defense (DoD), and Air Force information assurance (IA) policy and requirements for systems that transmit and manage sensitive but unclassified (SBU) data traffic.

The contractor shall also provide support to the following IA requirements:

• Provide support and documentation for the initial “type accreditation” in process.

• Provide system information up to the component and program level to the Base security engineering team at the Critical Design Review (CDR).

• Provide access to the system and engineering support to the security engineering team so that the team can perform requisite system security assessment(s), and catalog identified risks and mitigating security controls into a plan of action and milestones (POA&M) prior to acceptance test.

• Implement technical security controls, settings, and mitigation measures identified by the security engineering team prior to acceptance test.

• Provide system administration, access, and engineering support to the certification engineering team and installation management personnel during installation certification activities after acceptance test and prior to system burn-in.

• Provide system information and security assistance to the certification authority and certification agents during certification recommendation and accreditation decisions.

• Obtain information assurance vulnerability alert, system patches, and anti-virus updates from applicable original equipment manufacturers (OEM), industry, and government sources when published; evaluate each update against system components for operational impact; and periodically deliver and implement each update onto applicable system components throughout the operations and maintenance phase of the system lifecycle. This contractor support shall occur on a quarterly basis, or as required by the Department of the Air Force at a minimum, however, the contractor shall obtain, evaluate, deliver, and implement applicable updates more frequently should update sources indicate a particular update requirement to be a high priority (e.g., required response to a significant virus or denial of service attack). The contractor shall report all associated update activity to the Base POC on a quarterly basis.

• Ensure that all Prime Sites comply with all applicable physical and environmental security controls for MAC III systems processing sensitive information identified within DoDI 8500.2, Information Assurance Implementation.

• Systems that connect to DoD systems must maintain a level of security equal to the DoD system. Outside agencies have to follow the same policies as DoD and a Memorandum of Agreement has to be established. Outsourcing of management or IA has to be approved by the COI and a formal risk assessment is required.

5.3. INFORMATION ASSURANCE SYSTEM REQUIREMENTS

The new system shall provide the additional features to support the IA requirements:

• Time Reference Subsystem - To synchronize log and event recording and maintain a time reference to facilitate data analysis and evaluation. The proposal shall indicate the criteria for and the stability level (stratum) selected and system implementation.

• Enclave Boundary Defense - To support remote communications, provide equipment that satisfies the sensitive information, and enclave boundary defense requirements of DODI 8500.2. This feature shall be priced as an option.

• Secure Network Infrastructure Communications - All infrastructure management and user information that is passed across the network shall be encrypted using a secure communications method (e.g., SSL, SSH, IP Sec).

• System Update Service - Provide a centralized distribution point for patch management and anti-virus updates for all the components within the system using Citadel Hercules management system. Software license for Hercules will be provided by the Government.

• Centralized Log Server - Consolidate all of the log files from all components and provide a mechanism to back up the log files to media.

• Auditing - Audit the logon and actions for all system components by user and send the audit logs to different media or a centralized server.

• Backup/Restore - Provide a mechanism to backup configuration files and operating systems and a capability to restore the data.

• Include and support all IA activities necessary to meet DoD and Air Force IA requirements and comply with RMF as a part of the Camera implementation.

5.4. IA CERTIFICATION SUPPORT

The contractor shall provide system administration, access, and engineering support to the 87 SFS who will then coordinate with the IA certification team during the IA certification activities after acceptance test and prior to system burn-in. IAW AFMAN 17-1303 Cybersecurity Workforce Improvement Program meet the minimum 8570 Baseline requirement for Certification.

6.0. PROGRAM REQUIREMENTS:

6.1. Security and Privacy. Integration team members will be required to provide their full name, date of birth, and drivers’ license number and state of issue for base access vetting.

All Privacy Act information will be protected accordingly. Information is required for background checks due to the anti-terrorism/force protection initiatives currently in place.

The Government reserves the right to deny access to any personnel with a criminal history based upon the JB MDL Joint Integrated Defense Plan.

The Government will provide the contractor access to facilities from the commencement of the contract until task completion.

Contractor personnel shall comply with all AF rules, regulations and security requirements.

These rules, regulations and security requirements include, but are not limited to, the following: presenting valid identification for base entrance, obtaining and using vehicle passes for all contractor-owned and/or privately owned vehicles, obeying all posted directives, and providing strict adherence to Security Forces direction in instances where Security Forces have dispatched to a particular location.

6.2. Secure Areas: The contractor shall ensure all employees comply with all security requirements imposed by the local installation commander at all times and shall follow all instructions of the organizational commander having jurisdiction over the area being serviced in all matters pertaining to security. The contractor and his personnel shall be required to coordinate and schedule all work in restricted or controlled areas with the 87 SFS/ESS representatives a minimum of three (3) calendar days prior to entering these areas. As the installs in section 2.0. all involve access to controlled areas, SFS will be present at the locations, at all times.

6.3. Testing: The contractor’s Test Plan shall, at a minimum, detail the work to be completed (any applicable testing that can be done) at the 50% and 70% completion points and how the contractor shall test by demonstration the entire system at the 100% completion point.

6.4. The contractor shall provide layout and detailed drawings showing position and configuration of all work and equipment being installed. These drawing(s) shall be provided as attachments to the Contractor’s Proposal and in electronic file format.

6.5. Any signal conductors outside component enclosures must be enclosed in rigid, heavy wall conduit or intermediate metal conduit (IMC); enamel or latex coated for a salt-spray marine environment. Power cables from the Control Units and the Monitor Cabinet to their respective junction boxes may be in outdoor electrical metal tubing (EMT) or industrial plastic tubing with appropriate coating for this environment.

6.6. The successful contractor shall comply with DoD Environmental Baseline Guidance.

The contractor shall be responsible for characterization, transportation, storage and disposal of any waste generated, to include hazardous waste. No materials (hazardous or non-hazardous) or waste (hazardous or non-hazardous) shall be left on the Base without prior approval from the contracting officer.

6.7. The contractor shall be responsible for packaging, shipping, and delivering all required tools, materials, and equipment necessary for project completion to the Base and Work Site.

The contractor shall advise the requiring agency POC when the equipment is scheduled for delivery.

6.8. The contractor will provide their own equipment to extend electrical service to the various work areas where no current electric power is available.

7.0. GOVERNMENT RESPONSIBILITIES:

7.1. The Government will provide communication infrastructure between buildings as Category 5 UTP or one Fiber Optic pair; both will be run to the gate location. In the event that this existing communications infrastructure is inadequate for completing the systems installation then the contractor will provide that additional network connectivity, subject to the approval of the 87th Communications Squadron/SCXP Projects Officer.

7.2. 60 HZ electric power is available on site to support the installations. The contractor shall provide any additional ancillary electric power required to complete the system installation, subject to the approval of the 87 SFS representatives.

7.3. The Government will provide access to all base areas required for project completion.

Entrance to sensitive areas will be coordinated to minimize disruption to unit missions. The Government is responsible for providing an escort for the contractor into priority level resources and controlled areas. If contractors have the required clearance information, these personnel may be issued appropriate Air Force credentials. The SFS/ESS Office will provide escorts to the contractors working on the base, except in the CS Network Ops Center.

7.4. All on-base traffic control required by the contractors will be provided by the SFS/S3O personnel, 24hr advance notification is required. Any work requiring the closure of an Installation Access Control Point will be coordinated by the SFS/ESS office with the appropriate base agencies, this coordination is required a minimum of 24hrs in advance except in case of an emergency.

8.0. SCHEDULED OPERATIONS INTERRUPTIONS:

8.1. When the contractor must schedule an interruption to the existing system while performing work for this effort, the work shall be done at a time that causes the least inconvenience to the system users. The contractor shall notify and obtain approval from the 87 SFS/ESS representatives at least (1) working day in advance of any scheduled interruption. The contractor shall specify the starting time, duration of the interruption, along with what alarmed facilities or other equipment will be affected. The contractor shall provide verbal notification to the ESS office immediately after service has been restored. An acceptance test shall be successfully conducted prior to contractor departure. Additionally, each of the specified gates may experience lane closures for a short length of time. If a gate or lane closure is needed, the contractor shall contact the 87 SFS/ESS representatives at least

(3) days prior so that the appropriate measures can be taken. The 87 SFS will provide all traffic control and traffic safety measures as required. The contractor will provide a schedule of install dates per gate and provide that prior to commencing work on the project.

Page 10 of

9.0. SUPPORT, TRAINING AND DATA:

9.1. The contractor shall provide Appliance Management Training to the designated representative from the 87 CS Sq. immediately after successful installation, successful testing and Government acceptance of the system. The date/time for this training shall be coordinated with Security Forces and the Comm Sq. at least 7 business days prior to the training.

9.2. All information and data to include, but not limited to, drawing, schematics, diagrams, manuals, guides and documentation shall be provided to the Government. The contractor will provide As Built Drawings in Excel or PDF format.

10.0 WARRANTY: Warranty shall extend for a minimum of three years from government acceptance, with preference shown for extended terms without added cost.

11.0 REFERENCES: When any of these publications is superseded the most current version on the day of award will prevail.

• Memorandum From USAF/A7S

• DoD 5200.08-R, “Physical Security Program”

12. HOURS OF OPERATION: The Contractor shall perform the services required under this contract during normal duty hours 0700-1600 of the facility where work is being performed. Any other work schedule outside of normal duty hours requires POC approval. Part or all the facility may be occupied during this effort. Contractor shall accomplish the installation with minimum disruption of daily office activities. If performance of work outside normal duty hours will be required to meet the schedule, include desired working hours in the Contractor’s Proposal.

13. HOLIDAYS/DOWN DAYS: The Contractor shall not perform work under this contract on US Federal holidays or site-unique down-days unless expressly authorized by the POC.

14. FINAL ACCEPTANCE: The Contractor shall schedule a final project walk-through with the PPOC and POC. This should be scheduled at least 5 calendar days prior to acceptance. Final acceptance will be when the Point of Contact signs off on the AF Form 747, thereby indicating Government Acceptance.

15. PERIOD OF PERFORMNACE: The Contractor shall have 1 year from contract award to complete all facets of the project including final walk through with the Government representative. The period of performance for this contract shall consist of one (1) base year.

ATTACHMENT # 1

(5) pages McGuire Airfield Access #1 (CE Numbered)

* Indicates AECS

GATE 6*

PD gate not numbered

GATE 3

GATE 2

GATE 1

GATE 5

McGuire Airfield Access #2

GATE 14

GATE 13*

GATE 12

PD GATE 11

GATE 10

GATE 9*

PD GATE 8

GATE 7

GATE 16

McGuire Airfield Access #3

PD GATE 15

GATE 17

GATE 19

GATE 20

PD GATE 22*

25. Pedestrian Gate

PD GATE 23

PD Gate 24*

PD GATE 18

GATE 21*

PD Gate 26*

McGuire Airfield Access #4

GATE 31 GATE 40

GATE 28

GATE 27*

PD Gate 29*

PD Gate 30*

GATE 32*

39. Vehicle Gate*

PD Gate 33

GATE 34*

GATE 35

GATE 36

GATE 41*

PG 42*

GATE 38

GATE 37*

2 Bay PD Gate

McGuire Airfield Access #5

GATE 43