Statement_of_Work_24_Sept.docx

DOCX document 647 KB Posted

Attached to
IVC Cameras Federal contract opportunity
Solicitation number
FA448418Q0026
Issued by
Department of the Air Force Air Mobility Command

About this file

Statement of Work

View the file

Other files for this federal contract opportunity

Other files attached to IVC Cameras, newest first.
File Type Posted
Statement_of_Work_24_Sept.docx DOCX document
IVC_Site_Visit_Questions_with_Answers.docx DOCX document
List_of_IVC_Cameras_22a_Sept_18.xlsx XLSX spreadsheet
List_of_IVC_Cameras_22a_Sept_18.xlsx XLSX spreadsheet
IVC_Site_Visit_Questions_with_Answers.docx DOCX document
COMBO.docx DOCX document
Statement_of_Work_24_Sept.docx DOCX document
COMBO.docx DOCX document
List_of_IVC_Cameras_22a_Sept_18.xlsx XLSX spreadsheet
List_of_IVC_Cameras_22a_Sept_18.xlsx XLSX spreadsheet
IVC_Site_Visit_Questions_with_Answers.docx DOCX document
Statement_of_Work_24_Sept.docx DOCX document
COMBO.docx DOCX document
SFS_Appendix.rtf RTF text file
Statement_of_Work_6_Sept..docx DOCX document
Show all 15

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

STATEMENT OF WORK (SOW)

MCGUIRE ANNEX IP BASED VIDEO SECURITY AND SURVEILLANCE SYSTEM

MCGUIRE AIR FORCE BASE, NEW JERSEY

5 September 2018

1.0 PROGRAM OBJECTIVES:

1.1. Purpose: Purchase (93) High Definition IP Pan Tilt Zoom Industrial Video & Control (IV&C) cameras, (See Attachment 1 for models and locations). All of the aforementioned locations require Color Camera Coverage that is an approved camera that is able to work with existing IV&C software, IV&C Servers and is an approved system on the AFNET. Additionally, the contractor shall provide all required camera licenses, additional software licenses for IV&C Relay Server Software (RSS) V 4.2.122.0 for the server and View Station Software (VSS), V 4.2.103.0. The Contractor is required to provide (93) camera licenses and install these on Video Relay Servers (ver. 4.2.122.0). The Contractor is required to integrate (93) new cameras into the existing Video Relay Servers (ver. 4.2.122.0). Contractor is required to integrate (93) new cameras into the existing View Station workstations (ver. 4.2.103.0). Contractor will load the VSS Software on 5 existing computers. Finally, the contractor shall ensure the integrity of the JB MDL camera system and will ensure that all current licenses, cameras and software integrates with the with camera expansion.

1.2. Scope: Integrate the purchased contractor installed 93 cameras into the existing IV&C Relay Servers or new Relay Servers. Also, the contractor shall provide an updated Relay Server software that is already approved and tested through the appropriate Air Force agencies.

1.3 This installation will include all related equipment to comprise an integrated VSS utilizing Air Force approved hardware; successful installation testing and Government acceptance of the system.

1.2.1 The contractor shall install cameras in protective housings in the facility locations that will meet the coverage requirements as stated in attachment 1. The contractor shall provide the aforementioned protective housings. The outdoor cameras will be contained in all-weather vandal proof housings. The camera network of transport shall be via standard Ethernet TCP/IP networking and cables (Plenum rated cable). All cameras will transmit via contractor installed Cat 6 cable imagery in a sequence of motion JPEG images (M-JPEG), MPEG 2, MPEG 4 CIF-4 format, or H.264. However, the contractor will use existing wire for replacement cameras. No camera will transmit imagery via wireless components.

1.3.1 The video network infrastructure shall utilize the JB MDL NIPRNET Backbone where ever possible. This is a JB MDL customer mandated requirement.

All system components installed must undergo a Risk Management Framework (RMF) certification and accreditation. RMF has replaced DIACAP Certification and Accreditation. The system shall then be added to the Base System Security Authorization Agreement.

1.3.2 The contactor shall identify any existing government assets that cannot be made compatible with the new video system during the Contractor’s Proposal. If the existing cameras cannot be made compatible, the contractor shall notify 87th Security Forces Squadron and the 87th Contracting representative.

1.3.3 The Contractor’s Proposal shall identify the locations, models, and quantities of all equipment necessary to meet the requirements of this SOW and the minimum requirements of the references in paragraph 8.

1.3.4 The contractor shall include, 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 McGuire after completion of the installation.

1.3.5 The contractor shall provide at completion all product manuals, guides and an IP address table for the installed equipment.

1.4.1 The contractor shall provide any electrical work needed to complete the installation and integration into the existing camera system infrastructure.

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

1.5.1 1.5.2

2.0 INFORMATION ASSURANCE:

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

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

2.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 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 (IAVA), 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.

2.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, IPSec).

· Intrusion Detection - Provide an Intrusion Detection Systems (IDS) to monitor the system for unauthorized activities. Also, provide management and control capabilities for the IDS. This feature shall be priced as an option.

· 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 backup 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.

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

3.0. PROGRAM REQUIREMENTS:

3.1. Security and Privacy. Installation team members will be required to provide their full name, date of birth, and drivers’ license number and state of issue. 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 will provide the contractor access to facilities from the commencement of the contract until task completion.

Contractor personnel shall comply with all AFB 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.

3.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 areas with the 87 SFS representatives a minimum of three (3) calendar days prior to entering these areas.

3.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 VSS at the 100% completion point.

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

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

3.6. 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 contracting officer when the equipment is scheduled for delivery.

3.7. Contractor shall provide their own equipment to extend electrical service to the various work areas where no current electric power is available.

4.0. GOVERNMENT RESPONSIBILITIES:

4.1. The Government will provide communication infrastructure between buildings as Category 5 UTP or one Fiber Optic pair. 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.

4.2. 60 HZ electric power is available on site to support the start of installation, but not in specific proposed camera or allied equipment locations. The contractor shall provide for all additional electric power required to complete the system installation, subject to the approval of the 87 SFS representatives.

4.3. The Government will also be responsible for all software programming for all components of the Video System beyond initial device programming and the warranty expires..

4.4. The contractor shall reuse existing communications and electrical power wiring in facilities when feasible. The contractor shall provide the necessary electrical work if needed to complete the project.

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

5.0. SCHEDULED SERVICE INTERRUPTIONS:

5.1. Base Defense Operations Center (BDOC), Alternate (BDOC), 87 Wing Command Post (WCP), 108 WCP, 87 Crisis Action Team (CAT), Alternate CAT Bldg 2901 may be operational 24-hours-per-day, 7-days-per-week, 365-days-a-year. 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 representatives as specified one (1) working day in advance of any scheduled interruption. The contractor shall specify the starting time and duration of the interruption, along with what alarmed facilities or other alarm equipment will be affected. The contractor shall provide verbal notification to the C4I office immediately after service has been restored. A sensor or equipment 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 representatives (3) days prior so that the appropriate measures can be taken.

6.0. SUPPORT, TRAINING AND DATA:

6.1 The contractor shall provide Type 1 operators training for 20 people immediately after successful installation, successful testing of the system, and Government acceptance of the system. The date/time for this training shall be coordinated with the McGuire customers specified at time of the contractor pre-proposal conference and Security Forces at least 7 business days prior to the training.

6.2 The contractor shall provide administrator training for 10 people. immediately after successful installation, successful testing of the system, and Government acceptance of the system. The date/time for this training shall be coordinated with the McGuire customers specified at time of the contractor pre-proposal conference and Security Forces at least 7 business days prior to the training.

6.3 The contractor shall recommend and supply all spares for immediate bench stock in the Contractor’s Proposal .

6.4 All information and data to include, but not limited to, drawing, schematics, diagrams, manuals, guides and documentation shall be provided to the Government.

7.0. WARRANTY: Warranty shall extend for one year from government acceptance. The warranty shall indicate the minimum response times for repairing system outages.

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

• Memorandum From USAF/A7S, dated 13 Jun 2008, Atch 1 to this SOW

· DoD 4715.5-G Overseas Environmental Baseline Guidance 2007

· DoD 5200.08-R, “Physical Security Program,” April 9

•USAF Force Protection Command and Control Systems Program Office (ESC/FD), "Integrated Base Defense Security Systems (IBDSS) Capability Document."
•USAF ESE-SIT-00001, " Standardized Electronic Security Equipment; Sitting and Design Guidance for Permanent Installations."
•USACE Unified Facilities Criteria (UFC), UFC 4-020-04FA, "Electronic Security Systems: Security Engineering."

· AFI 17-101 Risk Management Framework FOR Air Force Information Technology (IT)

• AFI 31-101, "Air Force Physical Security Program."

· AFI 33-202v1

· AFI 33-21

· DoDI 8510.01p

· DoDD 8500.1

· DoDI 8500.2

· AFPD 33-2

· International Traffic in Arms Regulations

•AMC "Flightline Security Standards," April 1996.
•T.O. 31S9-2FSS9-1-5, Balanced Magnetic Switch, SA-1955( )/FSS-9(V)
•JOINT FORWARD OPERATIONS BASE (JFOB) FORCE PROTECTION HANDBOOK, DEC. 2006, J-3, [U-FOUO].
•GTA 90-01-010, JOINT CONTINGENCY OPERATIONS BASE (JCOB) FORCE PROTECTION HANDBOOK, J-3, 1 OCT. 2007, [U-FOUO].
•"U.S. Air Force Entry Control Facilities Design Guide," 18 February 2003.
•MIL-HDBK-1013/10. "Military Handbook Design Guidelines for Security Fencing, Gates, Barriers, and Guard Facilities," 14 May 1993.
•"Security Equipment and Resources Guide," DoD Physical Security Equipment Action Group (PSEAG).
•TM 5-853-2/AFMAN 32-1071 Vol. 2. "Security Engineering Concept Design," 12 May 1994.
•TM 5-853 Vol 4, "Security Engineering, Electronic Security Systems," 12 May 1994
•UFC 4-010-01. "DoD Minimum Antiterrorism Standards for Buildings," 8 October 2003.
•UFC 4-010-02. "DoD Minimum Antiterrorism Standoff Distances for Buildings," 8 October 2003.
•UFC 4-022-01. "Security Engineering: Entry Control Facilities/ Access Control Points," 25 May 2005.
•UG-2031-SHR. "User's Guide on Protection Against Terrorist Vehicle Bombs," May 1998.
•DoD 4715.5-G, Overseas Environmental Baseline Guidance Document, May 2007.
•HSPD-12 Directive, "Policy for a Common Identification Standard for Federal Employees and Contractors," 27 Aug. 2004.
•DHS-M-05-04, "Implementation of HSPD-12," 5 Aug. 2005.
•FIPS-201, "Personal Identify Verification (PIV) of Federal Employees and Contractors," Mar 2006.

· NIST Special Publication 800-53r4 Security and Privacy Controls for Federal Information Systems and Organizations

•NIST Special Publication 800-59, "Guideline for Identifying an Information System as a National Security Systems," Aug. 2003.
•NIST Special Publication 800-73, "Information Security: Interfaces for Personal Identity Verification," March 2006.
•NIST Special Publication 800-76, "Information Security: Codes for the Identification of Federal and Federally Assisted Organizations," March 2007.
•EIA ANSI/TIA/EIA-568-A, "Commercial Building Telecommunications Cabling Standard."
•EIA ANSI/TIA/EIA-569-A, "Commercial Building Standard for Telecommunications Pathways and Spaces."
•EIA ANSI/TIA/EIA-606, "Administration Standard for the Telecommunications Infrastructure of Commercial Buildings."
•EIA ANSI/TIA/EIA-607, "Commercial Building Grounding and Bonding Requirements for Telecommunications."
•EIA TIA/EIA-TSB-67, "Transmission Performance Specifications for Field Testing of Unshielded Twisted-Pair Cabling Systems."
•IBM GA27-3773-0, "Cabling System Technical Interface Specifications."
•ICEA S-83-596, "Fiber Optic Premises Distribution Cable."
•ICEA S-102-700, "Category 6 Individually Unshielded Twisted Pair Indoor Cable for Use in General Purpose and LAN Communications Wiring Systems."
•NFPA 70, "National Electrical Code (NEC)."
•NFPA 72, "National Fire Alarm Code."
•NFPA 101, "Life Safety Code."
•UNDERWRITERS LABORATORIES (UL), UL 50, "Enclosures for Electrical Equipment."
•UL 2050, "National Industrial Security Systems Program."

9.0. SFS ANTITERRORISM STATEMENT

Reference:

•Department of Defense Instruction (DoDI) 2000.16 DoD Antiterrorism (AT) Standards, 02 OCT 2006, Paragraph E3.18 DoD Standard 18
•Defense Federal Acquisition Regulation Supplement (DFARS) (Reference (r)) reflects current DoD AT security requirements for defense contractors
•Joint Publication 3-07.2 Antiterrorism

Terrorism is defined as:

The calculated use of unlawful violence or threat of unlawful violence to inculcate fear; intended to coerce or to intimidate governments or societies in the pursuit of goals that are generally political, religious, or ideological. See also antiterrorism; combating terrorism; counterterrorism; force protection condition; terrorist; terrorist groups.

Antiterrorism - As a prelude and during performance of any contract, it is critical that the Contractor be supportive of all DoD requirements to protect personnel and; their families, installations, facilities, information, and other resources from terrorist acts. All Contractors and Sub-Contractors are responsible for providing their personnel information on the (JB MDL) Antiterrorism Program. During performance of work, personnel security and protection of resources is critical for the installation to maintain a safe work environment. Contractors and contracted personnel shall be alert for any suspicious activities while on the installation. If any situation appears to be suspicious, immediate actions must be taken to properly notify base 87 Air Base Wing (ABW) Security Forces Squadron (SFS) Law Enforcement Desk (Dix and McGuire) (609) 562-6001, Lakehurst (732) 323-4000. Contractors must ensure that contracted personnel and vehicles are strictly controlled during performance of duty. For instance, Contractors shall use reasonable efforts to prevent any personnel or equipment from being placed in harm’s way or in a position that could aid or abet terrorists. It is recommended that all contracted personnel take the computer based training (CBT) for the DoD approved Antiterrorism Level I Training at https://atlevel1.dtic.mil/at/. Contractors are encouraged to contact the JB MDL Antiterrorism Office at (609)754-1397 for information regarding the installation Antiterrorism Program.

10.0. ATTACHMENTS: The attached files are provided for the contractor to better understand the basic requirement. Please see realted spreadsheet on FBO for Camera location details.

Any additional information necessary shall be requested by US Mail correspondence or via the NETCENTS Portal.

Attachment 1: 87th SECURITY FORCES SQUADRON (SFS); MCGUIRE ANNEX CONTRACTOR SECURITY REQUIREMENTS.

Facility photographs, and copies of government reference publications. Trademarked and copyrighted publications are the responsibility of the contractors.

**This document/attachment may contain information which must be protected IAW AFI 33-332 and DoD Reg 5400.11; Privacy Act of 1974 as amended 5 U.S.C. 552a applies and is For Official Use Only (FOUO). RECIPIENT IS RESPONSIBLE FOR SAFEGUARDING AND MAINTAINING THIS PRODUCT IAW THE PRIVACY ACT OF 1974, PL 93-579** image1.emf

Contractor Security Appendix

FOR OFFICIAL USE ONLY

HQ 87 ABW (AMC)

JB MDL, NJ 08641-5002

10 Jun 15

APPENDIX 4 TO ANNEX C TO JB MDL JIDP

CONTRACTOR SECURITY APPENDIX

1. SITUATION. This annex provides the 87th Security Forces Squadron (SFS) appendix to all statements of work for JB MDL.

1.1. Enemy. Refer to Basic Plan.

1.2. Friendly. Refer to Basic Plan.

1.3. Assumptions. Refer to Annex C of this plan.

1.4. Limiting Factors. Not all members listed below will be monitoring the radio.

2. MISSION. To provide Installation entry control procedures for all contractors. The following appendix provides information from Air Force Instruction 31-101, AFMAN 31-113 and local supplements on requirements for entering and conducting business while on Joint Base McGuire-Dix- Lakehurst (JB MDL), New Jersey.

3. EXECUTION

3.1. Contract Award. JB MDL requires all visitors/contractors/vendors to conduct a criminal history background check and Wants/Warrants check prior to being issued an Installation Access Pass/Card.

This check is done at no expense to the contractor and will be accomplished at the Visitor Control

Center or Commercial Vehicle Inspection Area. This will be completed prior to any access credential for JB MDL being issued to the contractor personnel.

3.1.1 All personnel requesting an installation visitor pass must complete the JB MDL request for criminal history form at the Visitor Control Center or Commercial Vehicle Inspection facility. Failure to provide all required information may result in access to the installation being denied.

3.1.2 If the contractor requires access to the installation for more than 60 days and up to three years, Visitor Control Center personnel will conduct a QWA Person Inquiry and criminal record check prior to issuing a card. Prior to issuing another Pass/Card another QWA Person Inquiry and criminal record check will be conducted.

3.1.3 If the contractor requires access for less than a 60 day period, a QWA Person Inquiry and criminal history check will be conducted prior to the contractor/vendor being issued an Installation

Access Pass. Any subsequent request for entry will require another QWA Person Inquiry and criminal history background check to be accomplished.

3.1.4. The Visitor Control Center will conduct the required background checks, review the results and determine whether personnel will be authorized to enter JB MDL. The Visitor Control Center will forward any derogatory/disqualifying information to 87 SFS/S5R for debarment initiation. If no derogatory/disqualifying information is identified, any printed QWA Person Inquiries or criminal background checks will be destroyed immediately.

3.1.5. The Visitor Control Center will also notify the appropriate Administrative Contracting Office or unit POC of those personnel who are being denied access to the installation due to derogatory information identified in the individual’s criminal background investigation. The disposition date (date the charges were finalized in court) is the date used to determine time frames. The below criminal history findings will automatically disqualify the person in question from being granted access to the installation:

3.1.5.1. There is a reasonable basis to believe based on an individual's criminal or dishonest history, that issuance of an access credential poses an unacceptable risk to the installation/mission.

3.1.5.2. Wanted by Federal or civil law enforcement authorities, regardless of offense or violation.

3.1.5.3. Immigration status is in question or cannot be verified.

3.1.5.4. US Citizenship or Social Security Account Number cannot be verified.

3.1.5.5. There is a reasonable basis to believe the individual has submitted fraudulent information concerning his or her identity.

3.1.5.6. There is a reasonable basis to believe the individual will attempt to gain unauthorized access to classified documents, information protected by the Privacy Act, information that is proprietary in nature, or other sensitive or protected information.

3.1.5.7. There is a reasonable basis to believe the individual will unlawfully or inappropriately use an access credential outside the workplace.

3.1.5.8. Barred from entry/access to any Federal installation or facility.

3.1.5.9. Wanted by federal or civil law enforcement authorities, regardless offense/violation.

3.1.5.10. Any conviction of firearms or explosives violation within the last 10 years.

3.1.5.11. Incarcerated for 12 months or longer within the past three years, regardless of the offense/violation. This can be a single incarceration or several combined which total 12 months.

3.1.5.12. Any conviction of espionage, sabotage, treason, terrorism or murder.

3.1.5.13. The individual is known to be or reasonably suspected of being a terrorist or belongs to an organization with known terrorism links/support.

3.1.5.14. The individual’s name appears on any Federal or State agency’s “watch list” or “hit list" for criminal behavior or terrorist activity.

3.1.5.15. The individual has been convicted of DUI manslaughter or involuntary manslaughter in the past 10 years.

3.1.5.16. The individual has been convicted of sexual assault, armed robbery, rape, child molestation, child pornography, trafficking in humans, drug possession with intent to sell or drug distribution.

3.1.5.17. Any Felony conviction within the last 10 years

3.1.5.18. Any conviction of drug possession, or drug manufacture within the past 5 years, reviewable on a case-by-case basis.

3.1.5.19. There is a reasonable basis to believe, based on the individual's material, intentional false statement, deception, or fraud in connection with Federal or contract employment, that issuance of an access credential poses an unacceptable risk to the installation/mission.

3.1.5.20. There is a reasonable basis to believe, based on the nature or duration of the individual's alcohol abuse without evidence of substantial rehabilitation, that issuance of an access credential poses an unacceptable risk to the installation/mission.

3.1.5.21. There is a reasonable basis to believe, based on the nature or duration of the individual's illegal use of narcotics, drugs, or other controlled substances without evidence of substantial rehabilitation, that issuance of an access credential poses an unacceptable risk to the installation/mission.

3.1.5.22. A statutory or regulatory bar prevents the individual's contract employment; or would prevent

Federal employment under circumstances that furnish a reasonable basis to believe that issuance of a access credential poses an unacceptable risk to the installation/mission.

3.1.5.23. The individual has knowingly and willfully engaged in acts or activities designed to overthrow the U.S. Government by force.

3.1.5.24. Any person with a pending court resolution will be denied access for any offense listed above.

The disposition date (defined as the date the charges were finalized in court) is used to determine the d e barment period.

3.1.5.25. Any person with a pending court resolution for an offense not listed above will be issued a pass for two weeks at a time until the case is finalized in court. If the charges are dismissed the person will be considered to have a favorable criminal history.

3.1.6. The contractor will provide an Entry Authority List (EAL) (see attachment 5 for EAL requirements) to the administrative contracting office or installation Point of Contact (POC) (i.e. 87

CONS, US Army Corps of Engineers (USACE), 87 CES, etc.). The contracting office will provide a copy of the initial EAL to the 87 SFS/Visitor Control Center. The contracting office will maintain any required documentation until the contract has been completed or terminated for any reason.

3.1.6.1. The administrative contracting office or installation POC will authenticate and forward the

EAL to the 87 SFS Visitor Control Center, NLT 72 hours prior to contract start date.

3.1.6.2. If EALs are not accurate or contain fraudulent information, contractor identification badges will not be issued.

3.1.6.3. Pen and ink changes for deletion purposes may be made to an EAL.

3.1.6.4. Pen and ink additions to an EAL will not be accepted. All additions must be made by initiating a new EAL.

3.1.6.5. The Master EAL will be resubmitted with the additions included. Individual letters for long term employees will not be accepted if the contract exceeds 60 days.

3.1.6.6. The Visitor Control Center will maintain a copy of the documents for 90 days after expiration for future reference.

3.1.6.7. Contractor/vendor Criminal History Record and Background Checks will be valid for a period not to exceed 3 years.

3.1.6.8. At the 3 year mark, the contractor/vendor is required to complete a new check for each individual still employed and working at JB MDL.

3.1.6.9. Background checks older than 3 years will be updated by accomplishing a new JB MDL

Criminal History Request Form. Records older than three years on file will be destroyed.

3.1.6.10. Holders of other federal credentials must have a validated need for installation access and will not be granted unlimited or unrestrained access to JB MDL. Therefore, identification credentials/tokens issued by other Federal departments, such as the Transportation Workers Identification Credential

(TWIC) [produced in accordance with the Maritime Transportation Security Act of 2002 and Security and Accountability for Every (SAFE) Port Act of 2006] or other Federal credentials, may be used as identity proofing only and the person must be vetted and issued an Installation Access Pass/Card. .

3.1.7. Contractor Visitor Passes for Entry to JB MDL. Contractors and vendors will be issued a computer generated or hand written Visitor Pass, or Defense Biometrics Identification System (DBIDS) card identifying them as a contractor authorized access to JB MDL.

3.1.7.1. A criminal history check will be conducted prior to issuing any pass or card, if a criminal history check has not been completed within the last 3 years.

3.1.7.2. Contractor and vendor visitor passes will be issued at a Visitor Control Center or the

Commercial Vehicle Inspection facility for all contractors or vendors who require access to the installation for less than 60 days in a year.

3.1.7.3. Visitor passes will be issued to contractors or vendors who do not access the installation at least three days per week.

3.1.7.4. Contractors and vendors who access the installation less than three days per week, but will access the installation for longer than one month will be included on an EAL with the date the contract expires. These personnel must stop at the Visitor Control Center each time they are needed to perform work. They will be issued a Visitor Pass each time they need to enter the installation. These personnel will be identified on the EAL as requiring periodic access.

3.1.7.5. DBIDS Installation Access Cards will be only be issued to contractors or vendors requiring access at least 3 days a week for more than 30 days in a year. Personnel will only be issued an

Installation Access Card after all required Criminal History Checks are completed. Installation Access

Passes will only be issued at any of the Visitor Control Centers or Commercial Vehicle Inspection facilities for the entire JB MDL. These personnel will be identified on the EAL as requiring daily access.

3.1.7.5.1. Contractor passes will be updated annually at the Visitor Control Center or Checkpoint 9 for contracts lasting over 1 year.

3.1.7.5.2. Contractor passes will be issued for the duration of the contract, or the length of the option period not to exceed 3 years, whichever is less.

3.1.7.5.3. NON U.S. CITIZENS: All non-U.S. citizens must provide a Work Permit Visa or Alien

Registration Card with immigration number when requesting entry onto JB MDL. Upon completion of an approved Alien Immigration background check, the foreign national will be permitted to be sponsored onto the installation.

3.1.7.5.4. Foreign nationals requesting access onto Lakehurst must be initially authorize access and then be escorted to and from the required location.

3.1.7.5.5. Sponsors must meet their Foreign National visitor at the Lakehurst Visitor Control Center.

3.1.7.5.6. Non US citizens will not be issued an Installation Access Card for longer than their Work

Permit Visa is valid.

3.1.7.5.7. Those contractors working under the AF Industrial Security program will provide an EAL to the Visitor Control Center.

3.1.7.5.8. Those contractors under the AF Industrial Security program requiring access to the AF computer network may be issued a Common Access Card (CAC) in lieu of the normal contractor visitor pass.

3.1.7.5.9. Those contractors under the AF Industrial Security program who have not been issued a

CAC will be issued a contractor visitor pass if they will be on the installation less than 60 days. These

Contractors will be issued an Installation Access Card if they will be on the installation longer than 60 days.

3.1.7.5.10. Those contractors under the AF Industrial Security Program who maintain an active DoD security clearance shall provide a Joint Personnel Adjudication System (JPAS) printout in lieu of the required background checks.

3.1.7.6. Installation Access Cards or temporary visitor / vehicle passes are issued for a specific purpose.

It is not intended to allow unrestricted installation access and is to be used only when access is required for the stated purpose. Access Cards are the property of the government and must be returned to the issuing office when no longer authorized (termination, retirement, end of contract, expired, etc) or required. The misuse of an Access Card or a temporary pass may be cause for confiscation and barment from the installation. All visitors and contractors will be advised that the acceptance of an Access Card and or temporary pass will be considered implied consent to inspect passenger(s) and vehicle at any time while on the installation. When an Access Card, visitor or vehicle pass has expired, renewal is not automatic. The sponsor or requesting individual must resubmit required information.

3.2. Contractor Vehicle Passes for Entry to JB MDL. Contractor vehicle passes will be issued at any

Visitor Control Center or Commercial Vehicle Inspection Area .

3.2.1. All vehicles and drivers must have the following documentation prior to being issued a Visitor

Pass/Card and being granted access to JB MDL:

3.2.1.1. Valid state driver's license with photo.

3.2.1.2. Valid state driver’s license without photo with another government/state issued form of identification with photo.

3.2.1.3. Valid vehicle insurance.

3.2.1.4. Valid vehicle registration.

3.2.1.5. Bill of Lading (if available).

3.2.1.6. A JB MDL point of contact with a phone number.

3.2.1.7. Contractors will be issued Visitor Pass/Card for entry to JB MDL provided the required documentation listed in 3.2 is valid.

3.2.1.8. Commercial vehicles identified in Appendix 4 and issued a Visitor Pass/Card must enter the installation through a Commercial Vehicle Inspection Area

3.3. Contractor, Commercial and Oversized Vehicles. All contractors, commercial and oversized vehicles must enter JB MDL Main Base through Checkpoint-9 located on Saylor’s Pond Road.

3.3.1. All contractors, commercial and oversized vehicles must enter JB MDL Lakehurst through the

Commercial Vehicle Inspection (CVI) gate located on CR 547.

3.3.2. The following are considered “commercial and oversized” vehicles at JB MDL and these vehicles can only enter the installation IAW paragraph 3.3.1. & 3.3.2..

3.3.3. All vehicles registered and licensed for commercial purposes with “commercial” license plates, regardless of state of issue.

3.3.4. All vehicles, regardless of type, license plate, or size, having more than two (2) axles.

3.3.5. All vehicles used to carry tools, machinery, equipment, or other commercial related equipment onto the installation.

3.3.6. All vehicles displaying a commercial plaque, logo or emblem carrying tools, machinery, equipment, or other commercial related equipment onto the installation.

3.3.7. Pick-up trucks which have not been equipped with storage containers and are not loaded with material in the bed of truck may enter JB MDL through any gate.

3.4. Contractor vehicle and personnel processing requirements. Checkpoint - 9 is open for personnel and vehicle processing from 0600-1600 hours Monday through Friday and 0600-1400 hours Saturday, Closed on Sunday and some Holidays.

3.4.1. Contractor/Commercial vehicles requesting JB MDL Main Base entry from 1600-

0600 will not be allowed entry. Unusual circumstances will be handled on a case by case basis. Contact the Emergency Communication Center (ECC) at (609) 754-6001.

3.5. Lakehurst CVI is open for personnel and vehicle processing from 0700-1600 hours Monday through Friday.

3.5.1. Contractor/Commercial vehicles requesting JB MDL Lakehurst entry from 1600- 0700 or on weekends must be coordinated with the Operations Emergency Communication Center (ECC and

BDOC) at (609) 754-6001/2001 /2002.

3.6. Sub-Contractors. All subcontractors are required to follow the same instructions listed above for their subcontractor personnel.

3.6.1. Contractors with an immediate access requirement for a short-term subcontractor must coordinate with their Contracting Officer prior to authorization of access without following the normal procedures.

3.6.2. Short term Subcontractors will be issued a pass not to exceed 1 week.

3.7. Contractors. Contractors working in USAF Restricted Areas will comply with the following:

3.7.1. All contractors meeting the standard of visitor groups IAW AFI 31-501 will be issued line badges for working on the flight line and restricted areas. Those contractors must be working 90 or more consecutive days. All other contractors will require escort.

3.7.2. Each individual contractor (person) will be required to complete a Standard Form

85P - Questionnaire for Public Trust Position before accessing the Restricted Area. This is an investigation to determine the trustworthiness of the individual requiring access to the Restricted Area.

This is not the same type of investigation as the NJ or other state background checks required to be conducted to access JB MDL.

3.7.3. Each individual will work with the unit security manager the contractor is supporting to complete the SF 85P.

3.7.4. Upon completion, the contractor will submit to the unit security manager for review.

3.7.4.1. If the 85P package contains errors, the individual will work with the security manager to correct.

3.7.4.2. If unable to correct, the individual will not be allowed access to the restricted area and may be asked to leave the installation.

3.7.5. If the SF 85P package contains no errors, the unit security manager will complete an AF Form

2586 - Unescorted Entry Authorization Certificate for accessing the restricted area.

3.7.6. The unit security manager will make an appointment with 87 ABW/IPP Personnel Security office for contractor processing and turn-in AF Form 2586.

3.7.7. The contractor will meet 87 ABW/IPP personnel and submit the completed SF 85P. 87

ABW/IPP will review SF 85P for accuracy and completion. If the 85P package contains errors, the individual will work with the personnel security office to correct.

3.7.7.1. If unable to correct, the individual will not be allowed access to the restricted area and may be asked to leave the installation.

3.7.7.2. If no issues with 85P, the 87 SFS Reports and Analysis will conduct a local files check on the individual.

3.7.8. Upon local files check completion (no issues), contractor will be directed to the Pass &

Registration (Bldg 1738) where a restricted area badge can be issued on an interim basis based on submission of the 2586 to S-5B.

3.7.8.1. S-5B will review AF Form 2586 for accuracy and completion.

3.7.8.2. If there are no errors, then an AF Form 1199 - Restricted Area Badge will be produced for the contractor.

3.7.8.3. If there are errors on the AF Form 2586, the contractor will be directed to return to the unit security manager for re-accomplishment of the form.

3.7.9. If potential disqualifying information is discovered the file is forwarded to the 87th ABW IPP office. The IPP office will coordinate with the unit and appropriate wing to determine an appropriate status for the contractor. If the determination is unfavorable the IPP office will notify the 87th SFS and unescorted entry privileges to restricted areas and the flightline will be withdrawn automatically.

3.8. Any work on or near the flightline will be coordinated through the 87 SFS/S5 office. The S5

Resource Protection section (Bldg. 6049 / Room 8) and Plans Manager (Bldg. 6049 / Room 7) must review prior to start of any work in or around a Controlled/Restricted Area.

3.8.1. The S5 Resource Protection section will verify the need to access the restricted area and determine if a Free Zone must be established.

3.8.2. The S5 Plans Manager needs to review all Statements of Work, Blueprints, and Contracts to ensure all JB MDL Force Protection needs are met and any police support is identified.

3.9. Flightline Driving. Only authorized contracted or privately owned vehicles with colored cones/placards are authorized on the flightline and/or flightline road unless driving a government vehicle or under authorized escort.

3.9.1. Contractor personnel who are authorized to drive on the flightline will be issued a colored cone/placard from Airfield Management.

3.9.2. Cones/placards must be visible during operations of the vehicle when driving on the flightline and when parked on the flightline.

3.9.3. The cone/placard must be secured (put away) upon departure from the flightline.

3.10. Restricted Areas: Defined as an area delineated by ropes, red lines or barriers that contain

Protection Level resources (i.e. aircraft or equipment).

3.10.1. These areas require a certain level of protection, and entry is only allowed by authorized personnel wearing a restricted area badge or personnel under authorized escort.

3.10.2. Aircraft hangars are restricted areas when aircraft are present.

3.10.3. Signs are posted every 100 feet on the exterior of restricted area boundaries stating; "Deadly

Force is Authorized."

3.10.4. Contractors will never enter restricted areas unless properly escorted or authorized by the installation commander or designee through the issuance of a restricted area badge.

3.10.5. If the Security Forces or a military member detains a contractor or contract employee at any time or for any reason, the contractor will comply with their request and will not become combative or argumentative.

3.11. Miscellaneous Requirements. All requests for additional contractor personnel must meet the same requirements listed in para A1 above before Installation Access Passes will be issued.

3.11.1. The administrative contracting office will be notified when personnel leave the contractor company for any reason and provide that information to the Visitor Control Center.

3.11.2. The contractor company is responsible for the return of all contractor identification badges at the end of the contract or when personnel depart for any reason. All badges and passes will be returned to the Visitor Control Center.

3.11.3. During increased Force Protection Conditions (FPCONs) there may be limited entry to the installation.

3.11.4. Retired military or government personnel may be allowed to enter the installation through any gate providing the vehicle operator has a current and valid base entry ID card.

3.11.5. Retired military or government personnel must be listed on the company EAL.

3.11.6. All retired military or government personnel will complete all Criminal History Record

Information/Background Check regardless of their military/government retired status.

3.11.7. All contractor vehicles entering must be registered at the…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it.