PWS.pdf

UNCLASSIFIED//FOR OFFICIAL USE ONLY

PERFORMANCE WORK STATEMENT (PWS)

Gate Entry Access Control System Part 1

General Information

1. GENERAL: This is a supply contract which includes Installation and training of a Gate Entry Access Control System.

1.1 Description of Services/Introduction: The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to provide and install a Gate Entry Access Control System defined herein except for those items specified as government furnished property and services. The contractor shall perform to the standards in this contract.

1.2 Background: ERDC currently has an entry gate access control system called Mobilisa. Moblisa is approaching its end of life. The system uses a centralized web server with a MS SQL backend server to store the date from handheld scanner at each of ERDC’s seven entry gates.

1.3 Objectives: Install and configure a entry gate access control system at the Vicksburg site. This will include installing software on the government provided servers, Watchlist software on the government provided server. Configure Oracle database on government provided Oracle instance. Configure gate scanners at all of the ERDC entry gates to communicate on ERDC’s secure wireless network at each gate.

Configure the gate scanner to communicate to the front-end server. Install and configure badging system.

Train end users on the use of the scanners and how to run reports and use of badging system. The data will reside locally on government owned servers.

- Configure frontend webserver server -Configure backend database -Configure watchlist server -Configure gate scanners to communicate with front end servers -Configure reports -Configure NCIC checks -Train End users

1.4 Scope: Install software and included hardware for gate entry scanner. Verify system is communicating and working properly. The contractor shall install access control software on front end and backend servers to support it. Configure gate scanners to communicate to with front-end server. Install and configure badging system.

1.5 Period of Performance:

Base Year – hardware, software, configuration, training, and software subscription Option Year One - software subscription Option Year Two - software subscription

1.6 General Information

1.6.1 Quality Control The contractor shall perform a 48 hour burn-in on all hardware before it being delivered to the site.

1.6.2 Quality Assurance: The government shall evaluate the contractor’s performance under this contract in accordance with the 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 defect rate(s).

1.6.3 Recognized Holidays:

New Year’s Day Labor Day Martin Luther King Jr.’s Birthday Columbus Day President’s Day Veteran’s Day Memorial Day Thanksgiving Day Independence Day Christmas Day

1.6.4 Hours of Operation: The contractor is responsible for conducting business, between the hours of 07:00 to 17:00 (CST) 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.

1.6.5 Place of Performance: The work to be performed under this contract will be performed at Engineer Research and Development Center, 3909 Halls Ferry Road Vicksburg, MS; Engineer Research & Development Center Construction Engineering Research Laboratory (CERL) 2902 Newmark Dr.

Champaign, IL 61826-9005; and the Engineer Research & Development Center Cold Regions Research & Engineering Laboratory (CRREL) 72 Lyme Road, Hanover, NH 03755-1290.

1.6.6 Type of Contract: The government will award a firm fixed price contract.

1.6.7 Security Requirements: Contractor personnel performing work under this contract must be a US citizen.

Access and General Protection/Security Policy and Procedures: All contractor and all associated sub-contractors employees shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative). The contractor shall also provide all information required for background checks to meet installation/facility access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contractor Personnel) as directed by DOD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any installation or facility change, the Government may require changes in contractor security matters or processes.

For contractors who do not require CAC, but require access to a DoD facility or installation.

Contractor and all associated sub-contractors employees shall comply with adjudication standards and procedures using the National Crime Information Center Interstate Identification Index (NCIC-III) and Terrorist Screening Database (TSDB) (Army Directive 2014-05 / AR 190-13), applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative, as NCIC and TSDB are available), or, at OCONUS locations, in accordance with status of forces agreements and other theater regulations.

1.6.9 Post Award Conference/Periodic Progress Meetings: The Contractor agrees to attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The contracting officer, Contracting Officers Representative (COR), and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. At these meetings the contracting officer will apprise the contractor of how the government views the contractor's performance and the contractor will apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues.

These meetings shall be at no additional cost to the government.

1.6.10 Contracting Officer Representative (COR): The (COR) will be identified by separate letter. The COR monitors all technical aspects of the contract and assists in contract administration The COR is authorized to perform the following functions: assure that the Contractor performs the technical requirements of the contract: perform inspections necessary in connection with contract performance:

maintain written and oral communications with the Contractor concerning technical aspects of the contract:

issue written interpretations of technical requirements, including Government drawings, designs, specifications: monitor Contractor's performance and notifies both the Contracting Officer and Contractor of any deficiencies; coordinate availability of government furnished property, and provide site entry of Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

PART 2

DEFINITIONS & ACRONYMS

2. DEFINITIONS AND ACRONYMS:

2.1. DEFINITIONS:

2.1.1. CONTRACTOR. A supplier or vendor awarded a contract to provide specific supplies or service to the government. The term used in this contract refers to the prime.

2.1.2. CONTRACTING OFFICER. A person with authority to enter into, administer, and or terminate contracts, and make related determinations and findings on behalf of the government. Note: The only individual who can legally bind the government.

2.1.3. CONTRACTING OFFICER'S REPRESENTATIVE (COR). An employee of the U.S. Government appointed by the contracting officer to administer the contract. Such appointment shall be in writing and shall state the scope of authority and limitations. This individual has authority to provide technical direction to the Contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have authority to change the terms and conditions of the contract.

2.1.4. DEFECTIVE SERVICE. A service output that does not meet the standard of performance associated with the Performance Work Statement.

2.1.5. DELIVERABLE. Anything that can be physically delivered, but may include non-manufactured things such as meeting minutes or reports.

2.1.6. KEY PERSONNEL. Contractor personnel that are evaluated in a source selection process and that may be required to be used in the performance of a contract by the Key Personnel listed in the PWS. When key personnel are used as an evaluation factor in best value procurement, an offer can be rejected if it does not have a firm commitment from the persons that are listed in the proposal.

2.1.7. PHYSICAL SECURITY. Actions that prevent the loss or damage of Government property.

2.1.8. QUALITY ASSURANCE. The government procedures to verify that services being performed by the Contractor are performed according to acceptable standards.

2.1.9. QUALITY ASSURANCE Surveillance Plan (QASP). An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance.

2.1.10. QUALITY CONTROL. All necessary measures taken by the Contractor to assure that the quality of an end product or service shall meet contract requirements.

2.1.11. SUBCONTRACTOR. One that enters into a contract with a prime contractor. The Government does not have privity of contract with the subcontractor.

2.1.12. WORK DAY. The number of hours per day the Contractor provides services in accordance with the contract.

2.1.12. WORK WEEK. Monday through Friday, unless specified otherwise.

PART 3

SPECIFIC TASKS

3. Specific Tasks:

3.1. This is a supply contract, however, services are required for installation and training.

3.2. Task Heading.

3.2.1 Contractor shall travel to the Vicksburg site for the server installation and to the Champaign and Hanover sites for the gate scanner installation if necessary.

3.2.2 Contractor shall install and configure software and other supporting compenents for the system to function as an entry gate access system.

3.2.3 Contractor shall troubleshoot and repair any errors or communication issues that may happen during the installation of this system, except for network issues which will fall back on the government to repair.

3.3. CONTRACTOR MANAGEMENT REPORTING (CMR: The Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site where the Contractor shall report ALL Contractor manpower (including subcontractor manpower) required for performance of this contract. The Contractor shall completely fill in all the information in the format using the following web address https://Contractormanpower.army.pentagon.mil. The required information includes: (1) Contracting Office, Contracting Officer, Contracting Officer’s Technical Representative (COTR) or also know as the Contracting Officer’s Representative (COR); (2) Contract number, including task and delivery order number; (3) Beginning and ending dates covered by reporting period; (4) Contractor's name, address, phone number, e-mail address, identity of Contractor employee entering data;

(5) Estimated direct labor hours (including sub-Contractors); (6) Estimated direct labor dollars paid this reporting period (including sub-Contractors); (7) Total payments (including sub-Contractors); (8) Predominant Federal Service Code (FSC) reflecting services provided by Contractor (and separate predominant FSC for each sub-Contractor if different); (9) Estimated data collection cost; (10) Organizational title associated with the Unit Identification Code (UIC) for the Army Requiring Activity (the Army Requiring Activity is responsible for providing the Contractor with its UIC for the purposes of reporting this information); (11) Locations where Contractor and sub-Contractors perform the work (specified by zip code in the United States and nearest city, country, when in an overseas location, using standardized nomenclature provided on website); (12) Presence of deployment or contingency contract language; and (13) Number of Contractor and sub-Contractor employees deployed in theater this reporting period (by country). As part of its submission, the Contractor shall provide the estimated total cost (if any) incurred to comply with this reporting requirement. Reporting period shall be the period of performance not to exceed 12 months ending September 30 of each government fiscal year and must be reported by 31 October of each calendar year. Contractors may use a direct XML data transfer to the database server or fill in the fields on the website. The XML direct transfer is a format for transferring files from a Contractor’s system to the secure website without the need for separate data entries for each required data element at the website. The specific formats for the XML direct transfer may be downloaded from the website.

PART 4

System Requirements

All the following requirements must be met or exceeded. Must be a complete system to include all hardware, and software and support of the system as a whole, with the exception of the head end servers which will be furnished by the government. This system is for ID verification at gates only, this is not for building access control. See specs below:

The scanner must be a one click, instant read scan of CAC, PIV, and driver’s licenses.

The scanner needs to be small and made for ONE hand use. Must be light weight and small in size, no more than 16oz. Include a wrist lanyard. User must have a hand free at all times to draw a weapon if needed. Must include a ruggedized case, and weather resistant. Each guard station will require a charging station for the scanners.

The scanner needs to be wireless and encrypt traffic.

The scanner cannot store any Personally Identifiable Information (PII).

The scanner must sync with a local server. There can be no cloud storage.

Scanner software must be user friendly, once a user has logged in no other typing, or clicking or changing of menus will be allowed, simply point and pull the trigger of the scanner to read the identification card and an instant return of the information to the user as whether the person is allowed to enter with a stop or go return.

The system must be able to produce customized reports of the scanned information.

The system will need to be an enterprise operation between all 3 of the ERDC sites. The two other sites will communicate with the head end server via the government network.

The system does not require preregistration of visitors coming into the facility.

The hardware will need to be provided by the vendor. This will include the scanners and server side software. (Server hardware, Operating System and licensing will be provided by the government, for head-end servers). The system must be able to connect to NCIC, the terror watch list, most wanted list and other relevant databases.

NCIC III and state criminal information checks must be made to screen for known or suspected terrorists, violent offenders, wanted persons, registered sex offenders, and possible serious threats to law enforcement officers. This requirement includes both NCIC background checks (NCIC) and criminal history (III). This may be done in NCIC by using EITHER QWI inquires alone or via two queries, QWA and QWH. State system checks will depend upon the means to access state criminal history and identification records.

Results showing a felony conviction within the last 10 years will be used to bar entry. Other results such as locating a record or possible record in the NCIC Terrorist file may require further coordination with the Terrorist Screening center. Other criminal history report results and wanted persons reports may be grounds for a commander to deny entry based upon the record. NCIC rules will generally require vendor to report only positive hits and not include details of criminal histories beyond a go/no-go status.

Personally identifiable information (PII) collected and utilized in the execution of this DTM must be maintained under secure access to prevent any unauthorized use, disclosure, or loss. The collection, use, maintenance, and dissemination of PII must comply with the requirements of

DoDD 5400.11, DoD 5400.11-R, DoDI 5505.17, DoDI 5400.16, and DoDI 1000.29 (References (de), (ef), (fg), (gh), and (hi)).

Vendor must provide access to NCIC and state how it will be provided.

All web communications must be encrypted using SSL, all wireless traffic must be encrypted, all must meet Army standards.

Backend database will store all data and must be encrypted.

No remote access will be allowed into the system from the vendor

Scanner software must be able to clear an individual coming in the gate in no more than eight seconds.

Software must be Army approved using Army Certificate of Networthiness or have an Army Approval to Operate (ATO) using Risk Management Framework (RMF).

Vendor must provide 24/7 service and support. Must have a 24 hour helpdesk line, no foreign owned or operated helpdesk support.

Faulty scanners will be mailed back to vendor and vendor will immediately send a working scanner back. 48 hour turn around.

Vendor must be ready to deploy within 30 days, due to replacing a failing system.

Attachment/Technical Exhibit List:

Attachment 1 – Performance Requirements Summary . See attachement

Attachment 2 – Deliverables Schedule. See attachement

TECHNICAL EXHIBIT 1

Performance Requirements Summary

The contractor service requirements are summarized into performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success.

Performance Objective (The Service required—usually a shall statement)

Standard Performance Threshold (This is the maximum error rate. It could possibly be “Zero deviation from standard”)

Method of Surveillance

Install and configure Gate Entry Access Control System on government owned server at the Vicksburg site

The contractor provided software and installation services

System is operational 100% Completition

Install and configure watchlist server software on government owned server at the Vicksburg site

Work with government provided Oracle database administrator to properly configure Oracle database to work access system software

The contractor provided installation services

Install and configure gate scanners

Install and configure badging system The contractor provided software and

Train end users at Vicksburg site End users are trained System is operational 100%

TECHNICAL EXHIBIT 2

DELIVERABLES SCHEDULE

Deliverable Frequency # of Copies Medium/Format Submit To

Software When the onsite work begins

One copy of each

CD

POC: Scott Hill Engineer Research and Development Center Vicksburg, MS 39180

Hardware