02.06_70CDCR18R00000001.pdf
PDF 678 KB Posted
- Attached to
- Access to Commercially Available LPR Database Federal contract opportunity
- Solicitation number
- 70CDCR18Q00000005
- Issued by
- Immigration and Customs Enforcement
About this file
Solicitation
View the file
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
70CDCR18Q00000005
1. REQUEST NO.
5a. ISSUED BY
NAME
a. NAME
c. STREET ADDRESS
d. CITY
10. PLEASE FURNISH QUOTATIONS TO
THE ISSUING OFFICE IN BLOCK 5a ON
OR BEFORE CLOSE OF BUSINESS (Date)
2. DATE ISSUED 3. REQUISITION/PURCHASE REQUEST NO. 4. CERT. FOR NAT. DEF.
UNDER BDSA REG. 2
AND/OR DMS REG.1
RATING
6. DELIVERY BY (Date)
7. DELIVERY
9. DESTINATION
a. NAME OF CONSIGNEE
b. STREET ADDRESS
PAGE OF PAGES
5b. FOR INFORMATION CALL: (No collect calls)
TELEPHONE NUMBER
AREA CODE NUMBER
8. TO:
b. COMPANY
e. STATE f. ZIP CODE
c. CITY
d. STATE e. ZIP CODE
IMPORTANT: This is a request for information, and quotations furnished are not offers. If you are unable to quote, please so indicate on this form and return it to the address in Block 5a. This request does not commit the Government to pay any costs incurred in the preparation of the submission of this quotation or to contract for supplies or services. Supplies are of domestic origin unless otherwise indicated by quoter. Any representations and/or certifications attached to this Request for Quotations must be completed by the quoter.
11. SCHEDULE (Include applicable Federal, State and local taxes)
THIS RFQ
REQUEST FOR QUOTATION
(THIS IS NOT AN ORDER)
IS IS NOT A SMALL BUSINESS SET ASIDEX
12/15/2017
1 51
Immigration and Customs Enforcement Office of Acquisition Management 801 I Street, NW Suite 930
ICE/Detention Compliance & Removals
WASHINGTON DC 20536
Multiple
202 732-2120WILLIAM QUIGLEY
12/18/2017 1800 ES
FOB DESTINATION
OTHER
(See Schedule)X
ITEM NO.
(a)
SUPPLIES/SERVICES
(b)
QUANTITY
(c)
UNIT
(d)
UNIT PRICE
(e)
AMOUNT
(f)
Request for Quote for Access to License Plate Reader (LPR) database Period of Performance: 12/22/2017 to 09/21/2020
0001 Base Period - 12/21/2017 - 01/31/2018 1.4 MO ACCESS TO LICENSE PLATE SYSTEM (All ICE Users) This is a Firm-Fixed Price (FFP) CLIN.
Product/Service Code: D317 Product/Service Description: IT AND TELECOM-
WEB-BASED SUBSCRIPTION
Period of Performance: 12/21/2017 to 01/31/2018
0002 Option Period 1 - 02/01/2018 - 01/31/2019 12 MO ACCESS TO LICENSE PLATE SYSTEM (All ICE Users) This is a Firm-Fixed Price (FFP) CLIN.
Continued ...
12. DISCOUNT FOR PROMPT PAYMENT
a. 10 CALENDAR DAYS (%) b. 20 CALENDAR DAYS (%) c. 30 CALENDAR DAYS (%) d. CALENDAR DAYS
NUMBER PERCENTAGE
NOTE: Additional provisions and representations
13. NAME AND ADDRESS OF QUOTER
b. STREET ADDRESS
c. COUNTY
d. CITY e. STATE f. ZIP CODE
14. SIGNATURE OF PERSON AUTHORIZED TO
SIGN QUOTATION
16. SIGNER
a. NAME (Type or print)
c. TITLE (Type or print)
a. NAME OF QUOTER
AREA CODE
NUMBER
15. DATE OF QUOTATION
b. TELEPHONE are are not attached
AUTHORIZED FOR LOCAL REPRODUCTION
Previous edition not usable
STANDARD FORM 18 (REV. 6-95)
Prescribed by GSA - FAR (48 CFR) 53.215-1(a)
ITEM NO. SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT
NAME OF OFFEROR OR CONTRACTOR
2 51
CONTINUATION SHEET
REFERENCE NO. OF DOCUMENT BEING CONTINUED PAGE OF
(A) (B) (C) (D) (E) (F)
70CDCR18Q00000005
(Option Line Item)
02/20/2018
Product/Service Code: D317
Product/Service Description: IT AND TELECOM-
WEB-BASED SUBSCRIPTION
Period of Performance: 02/01/2018 to 01/31/2019
0003 Option Period 2 - 02/01/2019 - 01/31/2020 12 MO
ACCESS TO LICENSE PLATE SYSTEM (All ICE Users)
This is a Firm-Fixed Price (FFP) CLIN.
(Option Line Item)
05/20/2018
Product/Service Code: D317
Product/Service Description: IT AND TELECOM-
WEB-BASED SUBSCRIPTION
Period of Performance: 02/01/2019 to 01/31/2020
0004 Option Period 3 - 02/01/2020 - 09/30/2020 8 MO
ACCESS TO LICENSE PLATE SYSTEM (All ICE Users)
This is a Firm-Fixed Price (FFP) CLIN.
(Option Line Item)
08/20/2018
Product/Service Code: D317
Product/Service Description: IT AND TELECOM-
WEB-BASED SUBSCRIPTION
Period of Performance: 02/01/2020 to 09/30/2020
NSN 7540-01-152-8067 OPTIONAL FORM 336 (4-86)
Request for Quote for Access to License Plate Database
Contracting Office Address:
Immigration and Customs Enforcement Office of Acquisition Management 801 I. St NW, Washington, DC 20536
Description: NAICS Code: 519190 – All Other Information Services.
This is a combined synopsis/request for quote for commercial items prepared in accordance with the format in Federal Acquisition Regulation (FAR) Subpart 12.6 and under the authority of FAR 13, as supplemented with additional information included in this notice. The North American Industry Classification System (NAICS) Code for this procurement is 519190 and is being conducted as sole source procurement.
The Immigration and Custom’s Enforcement’s (ICE) Enforcement and Removal Operations (ERO) and Homeland Security Investigations (HSI) is requesting that vendors submit a quote for a firm fixed price contract for access to a license plate reader database as set forth in the attached Statement of Work
(SOW).
Period of Performance:
The anticipated period of performance will include a base period of forty-one (41) days, two (2) twelve-month options periods, and one (1) eight-month option period.
Instructions to Offerors/Response Requirement:
Interested contractors must submit information necessary to demonstrate their capabilities to support the ICE requirements including performance requirements, functional requirement, alert list capabilities, mobile device capabilities, audit and reporting capabilities, as specified in the attached Statement of Work. Offerors shall return the complete quotation package, in electronic format. Electronic copies can be sent to Brittany Tobias at Brittany.Tobias@ice.dhs.gov and William Quigley at William.Quigley@ice.dhs.gov. Facsimile and hard copy quotes are not permitted and will be disregarded if received.
All electronic files should be labeled with the Offeror’s name, quotation number, submission date and the words “Source Selection Sensitive” and “Law Enforcement Sensitive”. Proprietary information shall be clearly marked.
a. Format. The submission shall be clearly indexed and logically assembled. Each section shall be appropriately numbered and clearly identified with the date and quotation number in the header and/or footer and shall begin at the top of each page. NOTE: Please submit a signed and dated cover letter with your quote addressed to Mr. William Quigley with your company’s contact information. A Table of Contents should be included.
Each paragraph shall be separated by at least one blank line. A standard, 12-point minimum font size applies to all sections. Times New Roman fonts is suggested.
b. File Packaging. Written quotes shall be submitted in one volume with three (3) sections, as outlined below. Use tab indexing sufficient to identify all sections within a particular quote section. The Offeror is required to provide the quote via email to mailto:Brittany.Tobias@ice.dhs.gov
Brittany.Tobias@ice.dhs.gov and William.Quigley@ice.dhs.gov. The Offeror should submit Attachment 4 in Microsoft Excel, with viewable calculations.
The following shall be included in the Narrative discussion:
SECTION I –TECHNICAL APPROACH: The offeror must submit information to demonstrate that the Offeror’s methods and approach have adequately and completely considered, defined, and satisfied the requirements specified in the Request for Quote and whether the Offeror’s methods and approach to meeting the SOW requirements provide the Government with a high level of confidence of successful completion. No pricing information is to be provided in the Technical Quote.
Technical Database Information Submittal. The vendor shall provide a description of its electronic information retrieval services that addresses:
• Compliance with the SOW
• Number of current records
• Ability to collect new records
• Identification of states or metropolitan areas where significant records are provided
• Ability to add and/or delete subscribers
• Return time on query
Quality Control Plan. The Offeror’s Quality Control Plan (QCP) should describe the methods it will use to review its performance to ensure it conforms to the performance requirements. The Offeror’s QCP should include methods that ensure and demonstrate its compliance with the performance requirements and the QASP discussed in Attachment 2.
SECTION II- PAST PERFORMANCE: The contractor shall provide a list of contracts or orders for the purpose of past performance evaluation. The contractor may also provide other forms of documentation which provide information on the company’s past performance. Valid past performance is evidence of similar work accomplished within the past three years.
SECTION III– PRICE. The offeror shall complete Attachment 4, with pricing for the base and each option period for each Contract Line Item (CLIN).
A Firm Fixed Price Quote and a written technical quote must be submitted by December 18, 2017 by 6:00 PM EST (1800) via email to Brittany.Tobias@ice.dhs.gov and William.Quigley@ice.dhs.gov.
Quotes must include the company’s name, point of contact, address, area code and telephone number and (mandatory) DUNS number. All quotes received without valid DUNS number (those not registered in the System for Award Management (SAM) www.sam.gov), will be considered ineligible.
Issue of the contract will be made to the contractor that offers the best value to the Government, considering price, past performance, and technical in accordance with FAR 13.106. The Government will award a contract resulting from this solicitation to the responsible offeror whose offer confirming to the solicitation will be most advantageous to the Government, price, and other factors considered. The criteria for evaluation are as follows:
1. Technical Capability
2. Past Performance
3. Price.
mailto:Brittany.Tobias@ice.dhs.gov mailto:William.Quigley@ice.dhs.gov mailto:Brittany.Tobias@ice.dhs.gov
The above listed evaluation factors are listed in descending order of importance.. Technical and past performance, when combined, is significantly more important than price.
Instructions: FAR 52.212-1 "Instructions to Offerors - Commercial" applies to this acquisition. Offerors are to include a copy of FAR provision 52.212-3 "Offeror Representations and Certifications - Commercial Items" with their response. The following FAR clauses also apply: 52.212-4 "Contract Terms and Conditions - Commercial Items" and 52.212-5 "Contract Terms and Conditions Required to Implement Statutes or Executive Orders - Commercial Items", with the clauses cited further in this synopsis as being applicable. The aforementioned provisions and clauses can be accessed electronically at http://acquisition.gov/comp/far/index.html. Prospective sources are reminded that award can only be made to a contractor who is registered in the System for Award Management (SAM) (www.sam.gov) database with an active Dun & Bradstreet Number.
Attachments:
Attachment 1: Statement of Work (SOW) Attachment 2: Quality Assurance Surveillance Plan Attachment 3: Terms and Conditions Attachment 4: Price
Statement of Work Access to License Plate Reader Commercial Data Service
C.1. INTRODUCTION AND BACKGROUND.
The intent of this Statement of Work (SOW) is to describe ICE’s operational requirements to obtain query-based access to a commercially available License Plate Reader (LPR) database to support its criminal and immigration law enforcement missions. A commercial LPR database stores recorded vehicle license plate numbers from cameras equipped with license plate reader technology. Records are uploaded into the system from a variety of governmental and private sources including, but not limited to, access control systems such as toll road or parking lot cameras, vehicle repossession companies, and law enforcement agencies. Licenses to access the commercial database are sold to commercial consumers as well as to law enforcement agencies.
ICE is neither seeking to build nor contribute to any public or private LPR database. ICE will use LPR information obtained in response to queries of the commercial database to further its criminal law enforcement and civil immigration enforcement missions. ICE immigration enforcement personnel will query the LPR database using known license plate numbers associated with subjects of their immigration enforcement activities, to determine where and when the vehicle has traveled within a specified period of time. The results of the queries will assist in identifying the location of aliens to further ICE’s immigration enforcement mission.
ICE will also use LPR information obtained from the commercial database to further its criminal law enforcement mission, which includes investigations related to national security, illegal arms exports, financial crimes, commercial fraud, human trafficking, narcotics smuggling, child pornography, and immigration fraud.
For example, use of LPR data in this context could help to identify the location of an investigative target or person of interest, or help track a vehicle that may be involved in illegal activity, such as smuggling.
Use of this data is expected to enhance officer and public safety by allowing arrests to be planned at locations that minimize the potential for injury (e.g., away from a subject’s residence if there are suspected to be children or weapons in the home). Use of this data is also expected to create a cost savings to the government by reducing the work-hours required for physical surveillance.
C2. Objective To provide constant (24 hour, seven days per week) access to a commercially available, query-based LPR database for ICE law enforcement personnel at ICE offices across the United States in the execution of their official law enforcement duties.
C3. Scope
This contract applies only to a query-based LPR database service for ICE.
C4. Performance Requirements
The vendor provides:
Data Service Content/Scope
• The LPR data service shall contain LPR records from a variety of sources across the United States, such as toll road or parking lot cameras, vehicle repossession companies, and law enforcement agencies.
• The LPR data service shall include substantial unique LPR detection records.
• The LPR data service shall compile LPR from at least 25 states and 24 of the top 30 most populous metropolitan statistical areas to the extent authorized by law in those locations.
o A metropolitan statistical area is defined as: a geographical region with a relatively high population density at its core and close economic ties throughout the area as defined by the Office of Management and Budget (OMB) and used by the Census Bureau and other federal government agencies for statistical purposes.
• The LPR data service provider shall demonstrate the number of new unique records that were added to the commercially available LPR database each month for the last consecutive twelve (12) months.
• The LPR data service shall make available at least 30 million new unique LPR data records each month.
• The vendor shall have a history of at least five (5) years of providing similar LPR data services and/or products to law enforcement agencies.
• The vendor shall already be providing similar services to other law enforcement agency customers.
User Management and Support
The vendor shall provide:
• Written instructions and guidance to facilitate use of system.
• The ability to compare new user requests with lists of personnel authorized by ICE to use the vendor system.
• Automatic verification of accounts with the ability to audit by using the user’s Originating Agency Identifier (ORI) to be matched against a current real-time list of active ORI numbers provided directly or indirectly by the National Law Enforcement Telecommunication System (NLETS).
• The ability to add new users or delete existing users within 24 business hours of ICE’s request.
• Initial training to orient personnel to the use of their system, including “Help Desk” support related to the use, access, and maintenance of the system.
• System training and “Escalation Procedures” for agency manager and shall include procedures for resetting passwords.
• Unlimited technical support to each user.
• Periodic or as needed updates to the web interface and mobile application. The vendor will employ appropriate technical, administrative, and physical security controls to protect the integrity, availability, and confidentiality of the data resident in its system.
Functional Requirements
Query Capabilities
• Before a user is able to perform a query from the main system or mobile application, the system must display upon logon a splash screen that describes the agency’s permissible uses of the system and data, and requires the user to affirmatively consent to these rules before proceeding further.
o The splash screen will appear at each logon event.
o The text on the splash screen shall also be available to the users via a hyperlink within the main system interface (including any mobile app interface).
o The agency will provide the language for the splash screen content.
• All queries of the LPR data service shall be based on a license plate number queried by the user only, and the data returned in response must be limited to matches of that license plate number only within the specified period of time.
• The system will not permit user queries of the data service unless a license plate number is entered. A query can only be conducted by entering a license plate number.
• The query interface will include a drop-down field for users to select a reason code for the query from a pre-populated list. The specific reason codes will be provided by ICE. This field is mandatory for conducting a query.
• The query interface will require a user to identify whether the user is entering data for him or herself or for another individual. If the user is entering data for another individual, the query interface will require the user to enter the name of the other individual.
• The query interface must include a free-text field of at least 255 characters for user notes. This will allow for additional information that will assist ICE in referencing the specific case for which the query was performed. Completing this field shall be mandatory for conducting a query.
• The system will have the capability to limit the query by time frame to allow users to comply with agency policy. Depending on the type of investigation being conducted, agency policy will allow the user to query the historical LPR detection records for only a certain period of time (e.g., going back 5 years from the date of query for any immigration investigation).
o The query interface will have a field for the user to select or input the appropriate timeframe for the query.
o The system will display results only for LPR detection records within that timeframe (e.g., only for the last 5 years).
o The system shall not run a query that lacks a time frame entered by the user.
• The vendor shall guarantee the results of queries meet a high degree of accuracy in datasets, with a margin of error not more than 2%.
• To ensure accuracy of information, the response to a query must include at least two photos on all hits.
o Photos must be of sufficient quality to allow the user to visually confirm the license plate and vehicle make/model in the photo are the same as what is represented in the vendor system.
o Query results must seamlessly integrate with web-based interactive maps. The printable report should show two different map views, nearest address, nearest intersection, date and time the license plate was captured, GPS coordinates, and source of the record.
o The vendor shall provide a notification mechanism in the event ICE users identify photographs that do not match the data in their system (license plate numbers or make/model mismatches). The vendor shall address all erroneous data. The vendor shall notify ICE and the ICE user of any inputted erroneous data and keep ICE and ICE users informed of corrections to erroneous data.
• The vendor will not use any information provided by the agency (query data) for its own purposes or provide access or disclose such information to other customers, business partners, or any other individual or entity.
• The vendor will not use ICE’s queries (the license plate numbers input into the system) for its commercial purposes. The vendor will only use the queries submitted by ICE to maintain an audit log.
Alert List Capabilities
• The LPR data service shall provide an “Alert List” feature that will allow ICE users to save license plate numbers so they will be automatically queried against new records loaded into the vendor’s LPR database on an on-going basis. Any matches will result in a near real-time notification to the user.
• The LPR data service Alert List will provide capabilities to share Alert List notifications between ICE users involved in the investigation.
• The Alert List feature will: 1) Automatically match new incoming detection records to user-uploaded or -entered Alert Lists containing the license plate numbers of interest in the investigation; 2) Send an email notification to the user originating such Alert List records and to any ICE user that has been shared the Alert List indicating there is a license plate match to new records in the system; and 3) Provide within the LPR system for download a PDF case file report for the match (with maps, vehicle images, and all pertinent detection & Alert List record information) for each email alert notification. The notification must be able to be limited to the user or a user group of ICE law enforcement officers involved in the specific investigation. The notification will comply with all applicable laws, including the Driver’s Privacy Protection Act of 1994, 18 U.S.C. §§ 2721-2725.
• The LPR data service will allow specifically designated users to batch upload a maximum of 2,500 license plate records into the “Alert List”. The batch upload will be in the form of a single comma separated variable (CSV) file with data fields to include, but not limited to the following: Plate number; State of Registration; Vehicle Year, Make, Model & Color; reason code and an open text field, of at least 255 characters, for a user note to assist in referencing the specific purpose / investigation / operation for which the query was performed.
• The Alert List function will include an automated capability that flags license plates for de-confliction.
• License plate pictures taken with the automated Optical Character Recognition (OCR) plate number translation shall be submitted to the LPR data service system for matching with license plates on any current ICE Alert List. Any positive matches shall return to the iOS application (identified below) alerting authorized users of a positive match. These pictures will be uploaded into the data service query by an authorized ICE user along with any mandatory information needed for a normal query. The pictures will be retained in the vendor’s system for audit purposes only and will not be otherwise accessible or usable for search purposes.
• Each license plate number on an Alert List will be valid for one year unless the user removes it before expiration. The system will prompt users two weeks prior to expiration and require the user to affirmatively indicate that there continues to be an operational requirement to keep the particular license plate entry on the Alert List active, or be given the option to delete the license plate from the Alert List. Prompts should continue periodically until the expiration date is reached. The system will grant the user an additional week after expiration to renew the entry in the Alert List. If the user does not renew, the system shall remove the license plate number from the Alert List.
• All Alert List activity shall be audited to capture user name, date and time, reason code, and user note associated with the query, as well as license plate number entry, deletion, renewal, and expiration from the alert list.
• The vendor shall not retain any data entered onto an Alert List except as part of the audit trail once the entry has expired per the process described above, or once the user has deleted the entry from the Alert List.
Mobile Device Capabilities
• The LPR data service shall feature an iOS-compatible mobile application that allows authorized ICE users to:
o Query the LPR data service by entering the license plate number, state of registration, reason code, and the ability to add returned positive matches into the Alert List.
o Have quick access and recall of any queries and Alert Lists associated with the user or designated user group. The vendor application will delete any saved data on the mobile device after 60 days, if not already deleted manually by the user.
o Provide capabilities to share Alert List notifications between ICE users involved in the investigation.
• The mobile application will conform to all other performance, privacy, and functional requirements identified in the SOW. The vendor shall coordinate with ICE to make sure that the mobile application undergoes the required privacy assessment prior to use.
Audit and Reporting Capabilities
• The vendor shall generate an immutable audit log in electronic form that chronicles the following data:
o Identity of the user initiating the query or the person on whose behalf the query is initiated, if different;
o Exact query entered, to include license plate number, date limitations, geographic limitations (if applicable), reason code, and any other data selected or input by the user;
o Date and time of query; and o Results of the query.
• All Alert List activity shall be audited to capture user name, date and time, reason code, and user note associated with the query, as well as license plate number entry, deletion, renewal, and expiration from the alert list.
• The vendor shall provide to ICE user audit reports on a quarterly basis and upon request. Audit reports shall contain the audit log information of a given user(s) for the specified period of time. The vendor shall provide the audit log in electronic form via secure transmission to ICE promptly upon request. The format of the audit log shall allow for ICE to retrieve user activity by user name (or ID), query entered (e.g., particular license plate) and date/time. The exact technical requirements and format for the audit log will be negotiated after contract award.
• The vendor shall promptly cooperate with an ICE request to retrieve and provide a copy of the actual records retrieved from the LPR data service in response to a particular query, or any other data relevant to user activity on the vendor system, for purposes of the agency’s internal investigations and oversight.
• The vendor shall not use audit trail data for any purpose other than those specified and authorized in this contract.
• The vendor is to provide quarterly, or upon request, statistics based on positive hits against the number of requested searches and hit list.
• The audit logs specified in this statement of work are records under the Federal Records Act. The vendor shall maintain these records on behalf of ICE throughout the life of the contract, but for no more than seven
(7) years. The vendor is not authorized to share these records, or the Alert List data, with any outside entities including other law enforcement agencies. At the end of the contract, the vendor shall extract, transfer, and load these records (including any still-active Alert List data, if requested by ICE) to another storage medium or location specified by ICE. This transfer of records shall occur no later than thirty (30) days after the contract ends. After successful transfer of these records, the vendor shall ensure all copies of the records (including any still-active Alert List data) are securely deleted from all networks and storage media under its control or under the control of any of its agents or subcontractors.
The vendor shall meet the following Key Performance Parameters (KPPs):
Metric Unit of Measure Minimum
LPR Data Service Uptime – Unit of measure 100% > 99.0 Operating Schedule 24/7/365 Scheduled downtime </= 4 hours per month Meantime between failure (MTBF) 4,000 operating hours
Overall Support Service Support availability 24/7/365 Results of a single LPR query Results of a single LPR query </= 5 seconds after submission
C.6. Promotion of the Contract The Vendor may promote this contract to current ICE employees during the life of the contract. The Offeror’s goals shall be to: (a) make customers aware of this procurement vehicle; (b) make customers aware of all available products and services; and (c) assist customers in creating timely and accurate delivery order/purchase orders.
C.7. News Releases News releases pertaining to this contract shall not be made without ICE approval, as appropriate, and then only upon written approval received from the contracting officer and the ICE Office of Public Affairs.
C.8. License Type The Vendor shall provide a license that will permit ICE to add or remove users without purchasing additional licenses so long as ICE’s authorized user population falls within its purchased entitlements. The Vendor shall not provide a named user license.
standards outlined in this QASP shall be used to determine the level of Contractor performance in the elements defined.
The Government performs surveillance to determine the level of Contractor performance to these standards. Standards apply to each month of performance. Should a month of performance fall below acceptable standards, the withholding will apply to the monthly invoice.
The Performance Requirements are listed below. The Government will use these standards to determine Contractor performance and shall compare Contractor performance to the standard and assign a rating. At the end of the performance period, these ratings will be used, in part, to establish the past performance of the Contractor on the contract.
The Government will use these standards to determine Contractor performance and compare Contractor performance to the Acceptable Quality Level (AQL).
Table 1: Performance Requirements Summary (PRS) Metric Unit of Measure Minimum AQL
LPR Data Service Uptime – Unit of measure 100% > 99.0 Operating Schedule 24/7/365 Scheduled downtime </= 4 hours per month Meantime between failure (MTBF) 4,000 operating hours Overall Support Service Support availability 24/7/365 Results of LPR Query Result of LPR query after entered in end-user-computing device </= 5 seconds after submission
Table 2: Performance Standards Matrix
Performance Requirement Paragraph Performance
Standard Performance Indicator Performance Level
Surveillance Method
Withholding Criteria to Monthly Payment
LPR Data Service and Technical Support
4.11.1 4.11.2 4.11.4 4.11.5
Uptime of Data Service and Technical Support shall be fully available 24/7/365
LPR Data Service downtime shall not exceed 4 hours in any 1 month period and Meantime between failure (MTBF) is 4,000 operating hours
> 99.0% Validated User/Customer Complaints 100% Inspection
- 20% withholding for the first hour (or any part thereof) in excess of the 4 hour limitation.
- 0.5% withholding for each hour thereafter until the data service is operable. The withholding shall be determined by prorating the number of days deficient within the particular billing month.
Performance Requirement Paragraph Performance
Standard Performance Indicator Performance Level
Surveillance Method
Withholding Criteria to Monthly Payment
Overall Support Service
4.4 4.10
Support Availability Support Service must be available 24/7/365
>99% Monitored monthly during the Transition In period.
Contractor self-monitoring and Validated User/Customer Complaints 100% Inspection
- 98% / 93% / 88% compliance will result in 2% / 5% / 10% withholding from the invoice(s) of the facilities involved. The withholding shall be determined by prorating the number of days deficient within the
Results of LPR Query
4.5.3 4.6.2
Length of time for Results of LPR query to appear after being entered in the end-user computing device
Less than 5 seconds after submission
95% Monitored monthly during the life of the contract
Contractor Self-monitoring and Validated User/Customer Complaints 100% Inspection
- 93% / 88% / 83% compliance will result in 2% / 5% /10% withholding on the total volume of reports for the facility. The withholding shall be determined by prorating the number of days deficient within the
4. METHODS OF QUALITY ASSURANCE (QA) SURVEILLANCE
Regardless of the surveillance method, the COR shall always contact the Contractor's task manager or on-site representative when a defect is identified and inform the manager of the specifics of the problem.
The COR, with assistance from the CO, shall be responsible for monitoring the Contractor’s performance in meeting a specific performance standard/AQL.
Various methods exist to monitor performance. The COR will use the surveillance methods listed below in the administration of this QASP.
a. PERIODIC INSPECTION
• Scheduled quarterly inspection of audit logs or as required
b. VALIDATED USER/CUSTOMER COMPLAINTS
The Contractor is expected to establish and maintain professional communication between its employees and customers. The primary objective of this communication is customer satisfaction. Customer satisfaction is the most significant external indicator of the success and effectiveness of all services provided and can be measured through customer complaints.
Performance management drives the Contractor to be customer focused through initially and internally addressing customer complaints and investigating the issues and/or problems but the customer always has the option of communicating complaints to the COR, as opposed to the Contractor.
Customer complaints, to be considered valid, must be set forth clearly and in writing the detailed nature of the complaint, must be signed, and must be forwarded to the COR.
Customer feedback may also be obtained either from the results of customer satisfaction surveys or from random customer complaints.
• Review of identified deficiencies and or complaints made by users of the services
• Investigate and validate
• Review of notification of report discrepancies
c. 100% INSPECTION
• Review of LPR Data Service uptime
• Review of Scheduled Downtime
• Review Meantime Between Failure (MTBF)
• Review Overall Support Service Availability
d. Analysis of Contractor’s progress report. The Contractor is required to provide a weekly progress report that will be used to communicate the Contractor’s status in the Transition phase.
e. Performance reporting.
Surveillance results will be used as the basis for actions against the Contractor Past Performance Report.
In such cases, the Inspection of Services clause in the Contract becomes the basis for the CO’s actions.
5. DOCUMENTING PERFORMANCE
Documentation must be accurate and thorough. Completeness, currency, and accuracy support both satisfactory and unsatisfactory performance
a. ACCEPTABLE PERFORMANCE
The Government shall document positive performance. All positive performance should be documented by an email to the COR describing the outstanding performance and why it is of value to the Government. This information shall become a part of the supporting documentation for the Contractor Performance Assessment Reporting System (CPARS) and the QASP
b. UNACCEPTABLE PERFORMANCE
When unacceptable performance occurs, the COR shall inform the Contractor. This will be in writing unless circumstances necessitate verbal communication. In any case the COR shall document the discussion and place it in the COR file.
When the COR determines formal written communication is required, the COR shall prepare a Contract Discrepancy Report (CDR), and present it to the Contractor's representative. A CDR template is attached to this QASP.
The Contractor will acknowledge receipt of the CDR in writing. The CDR will specify if the Contractor is required to prepare a corrective action plan to document how the Contractor shall correct the unacceptable performance and avoid a recurrence. The CDR will also state how long after receipt the Contractor has to present this corrective action plan to the COR. The Government shall review the Contractor's corrective action plan to determine acceptability.
Any CDRs will become a part of the supporting documentation for Past Performance.
6. FREQUENCY OF MEASUREMENT
While the Contractor is fully expected to comply with all requirements in the PWS, the Government’s assessment of Contractor performance will focus mainly on the objectives listed in the AQL column of the Performance Standards Summary Matrix. The COR will monitor the Contractor’s performance to ensure it meets the standards of the contract. Unacceptable performance may result in the Contracting Officer taking any of the following actions: Require the Contractor to take necessary action to ensure that future performance conforms to contract requirements, reduce the contract price to reflect the reduced value of the services, issue a Contract Discrepancy Report, or require the Contractor to re-perform the service. In addition, the Contractor’s performance will be recorded annually in the Contractor Performance Assessment Report (CPAR).
Signature – Contracting Officer’s Representative
Signature – Contracting Officer
ATTACHMENT 3:
TERMS AND CONDITIONS
CUSTOM CO ADDED TERMS AND CONDITIONS
In the case of a conflict between the terms and conditions of the contractor’s agreement and the terms and conditions of this purchase order, all applicable federal statutes and regulations shall govern.
52.204-21 BASIC SAFEGUARDING OF COVERED CONTRACTOR INFORMATION SYSTEM
(JUN 2016)
(a) Definitions. As used in this clause– “Covered contractor information system” means an information system that is owned or operated by a contractor that processes, stores, or transmits Federal contract information.
“Federal contract information” means information, not intended for public release, that is provided by or generated for the Government under a contract to develop or deliver a product or service to the Government, but not including information provided by the Government to the public (such as on public websites) or simple transactional information, such as necessary to process payments.
“Information” means any communication or representation of knowledge such as facts, data, or opinions, in any medium or form, including textual, numerical, graphic, cartographic, narrative, or audiovisual (Committee on National Security Systems Instruction (CNSSI) 4009).
“Information system” means a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information (44 U.S.C. 3502).
“Safeguarding” means measures or controls that are prescribed to protect information systems.
(b) Safeguarding requirements and procedures.
(1) The Contractor shall apply the following basic safeguarding requirements and procedures to protect covered contractor information systems. Requirements and procedures for basic safeguarding of covered contractor information systems shall include, at a minimum, the following security controls:
(i) Limit information system access to authorized users, processes acting on behalf of authorized users, or devices (including other information systems).
(ii) Limit information system access to the types of transactions and functions that authorized users are permitted to execute.
(iii) Verify and control/limit connections to and use of external information systems.
(iv) Control information posted or processed on publicly accessible information systems.
(v) Identify information system users, processes acting on behalf of users, or devices.
(vi) Authenticate (or verify) the identities of those users, processes, or devices, as a prerequisite to allowing access to organizational information systems.
(vii) Sanitize or destroy information system media containing Federal Contract Information before disposal or release for reuse.
(viii) Limit physical access to organizational information systems, equipment, and the respective operating environments to authorized individuals.
(ix) Escort visitors and monitor visitor activity; maintain audit logs of physical access;
and control and manage physical access devices.
(x) Monitor, control, and protect organizational communications (i.e., information transmitted or received by organizational information systems) at the external boundaries and key internal boundaries of the information systems.
(xi) Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks.
(xii) Identify, report, and correct information and information system flaws in a timely manner.
(xiii) Provide protection from malicious code at appropriate locations within organizational information systems.
(xiv) Update malicious code protection mechanisms when new releases are available.
http://uscode.house.gov/
(xv) Perform periodic scans of the information system and real-time scans of files from external sources as files are downloaded, opened, or executed.
(2) Other requirements. This clause does not relieve the Contractor of any other specific safeguarding requirements specified by Federal agencies and departments relating to covered contractor information systems generally or other Federal safeguarding requirements for controlled unclassified information (CUI) as established by Executive Order 13556.
(c) Subcontracts. The Contractor shall include the substance of this clause, including this paragraph (c), in subcontracts under this contract (including subcontracts for the acquisition of commercial items, other than commercially available off-the-shelf items), in which the subcontractor may have Federal contract information residing in or transiting through its information system.
52.209-07 INFORMATION REGARDING RESPONSIBILITY MATTERS (JUL 2013)
(a) Definitions. As used in this provision.
“Administrative proceeding” means a non-judicial process that is adjudicatory in nature in order to make a determination of fault or liability (e.g., Securities and Exchange Commission Administrative Proceedings, Civilian Board of Contract Appeals Proceedings, and Armed Services Board of Contract Appeals Proceedings). This includes administrative proceedings at the Federal and State level but only in connection with performance of a Federal contract or grant. It does not include agency actions such as contract audits, site visits, corrective plans, or inspection of deliverables.
“Federal contracts and grants with total value greater than $10,000,000” means.
(1) The total value of all current, active contracts and grants, including all priced options; and
(2) (2) The total value of all current, active orders including all priced options under indefinite-delivery, indefinite-quantity, 8(a), or requirements contracts (including task and delivery and multiple-award Schedules).
“Principal” means an officer, director, owner, partner, or a person having primary management or supervisory responsibilities within a business entity (e.g., general manager; plant manager; head of a division or business segment; and similar positions).
(b) The offeror [ ] has [ ] does not have current active Federal contracts and grants with total value greater than $10,000,000.
(c) If the offeror checked “has” in paragraph (b) of this provision, the offeror represents, by submission of this offer, that the information it has entered in the Federal Awardee Performance and Integrity Information System (FAPIIS) is current, accurate, and complete as of the date of submission of this offer with regard to the following information:
(1) Whether the offeror, and/or any of its principals, has or has not, within the last five years, in connection with the award to or performance by the offeror of a Federal contract or grant, been the subject of a proceeding, at the Federal or State level that resulted in any of the following dispositions:
(i) In a criminal proceeding, a conviction.
(ii) In a civil proceeding, a finding of fault and liability that results in the payment of a monetary fine, penalty, reimbursement, restitution, or damages of $5,000 or more.
(iii) In an administrative proceeding, a finding of fault and liability that results in.
(A) The payment of a monetary fine or penalty of $5,000 or more; or
(B) The payment of a reimbursement, restitution, or damages in excess of $100,000.
(iv) In a criminal, civil, or administrative proceeding, a disposition of the matter by consent or compromise with an acknowledgment of fault by the Contractor if the proceeding could have led to any of the outcomes specified in paragraphs (c)(1)(i), (c)(1)(ii), or (c)(1)(iii) of this provision.
(2) If the offeror has been involved in the last five years in any of the occurrences listed in (c)(1) of this provision, whether the offeror has provided the requested information with regard to each occurrence.
(d) The offeror shall post the information in paragraphs (c)(1)(i) through (c)(1)(iv) of this provision in FAPIIS as required through maintaining an active registration in the System for Award Management database via https://www.acquisition.gov (see 52.204-7).
52.212-1 INSTRUCTIONS TO OFFERORS. COMMERCIAL ITEMS (JAN 2017)
(a) North American Industry Classification System (NAICS) code and small business size standard. The NAICS code and small business size standard for this acquisition appear in Block 10 of the solicitation cover sheet (SF 1449). However, the small business size standard for a concern which submits an offer in its own name, but which proposes to furnish an item which it did not itself manufacture, is 500 employees.
(b) Submission of offers. Submit signed and dated offers to the office specified in this solicitation at or before the exact time specified in this solicitation. Offers may be submitted on the SF 1449, letterhead stationery, or as otherwise specified in the solicitation. As a minimum, offers must show.
(1) The solicitation number;
(2) The time specified in the solicitation for receipt of offers;
(3) The name, address, and telephone number of the offeror;
(4) A technical description of the items being offered in sufficient detail to evaluate compliance with the requirements in the solicitation. This may include product literature, or other documents, if necessary;
(5) Terms of any express warranty;
(6) Price and any discount terms;
(7) “Remit to” address, if different than mailing address;
(8) A completed copy of the representations and certifications at FAR 52.212-3 (see FAR 52.212-3(b) for those representations and certifications that the offeror shall complete electronically);
(9) Acknowledgment of Solicitation Amendments;
(10) Past performance information, when included as an evaluation factor, to include recent and relevant contracts for the same or similar items and other references (including contract numbers, points of contact with telephone numbers and other relevant information); and
(11) If the offer is not submitted on the SF 1449, include a statement specifying the extent of agreement with all terms, conditions, and provisions included in the solicitation. Offers that fail to furnish required representations or information, or reject the terms and conditions of the solicitation may be excluded from consideration.
(c) Period for acceptance of offers. The offeror agrees to hold the prices in its offer firm for 30 calendar days from the date specified for receipt of offers, unless another time period is specified in an addendum to the solicitation.
(d) Product samples. When required by the solicitation, product samples shall be submitted at or prior to the time specified for receipt of offers. Unless otherwise specified in this solicitation, these samples shall be submitted at no https://www.acquisition.gov/far/html/FormsStandard67.html#wp1189284 https://www.acquisition.gov/far/html/FormsStandard67.html#wp1189284 https://www.acquisition.gov/far/html/FormsStandard67.html#wp1189284 https://www.acquisition.gov/far/html/52_212_213.html#wp1179194 https://www.acquisition.gov/far/html/52_212_213.html#wp1179194 https://www.acquisition.gov/far/html/FormsStandard67.html#wp1189284 expense to the Government, and returned at the sender’s request and expense, unless they are destroyed during preaward testing.
(e) Multiple offers. Offerors are encouraged to submit multiple offers presenting alternative terms and conditions, including alternative line items (provided that the alternative line items are consistent with subpart 4.10 of the Federal Acquisition Regulation), or alternative commercial items for satisfying the requirements of this solicitation.
Each offer submitted will be evaluated separately.
(f) Late submissions, modifications, revisions, and withdrawals of offers.
(1) Offerors are responsible for submitting offers, and any modifications, revisions, or withdrawals, so as to reach the Government office designated in the solicitation by the time specified in the solicitation. If no time is specified in the solicitation, the time for receipt is 4:30 p.m., local time, for the designated Government office on the date that offers or revisions are due.
(2)(i) Any offer, modification, revision, or withdrawal of an offer received at the Government office designated in the solicitation after the exact time specified for receipt of offers is “late” and will not be considered unless it is received before award is made, the Contracting Officer determines that accepting the late offer would not unduly delay the acquisition; and.
(A) If it was transmitted through an electronic commerce method authorized by the solicitation, it was received at the initial point of entry to the Government infrastructure not later than 5:00 p.m. one working day prior to the date specified for receipt of offers; or
(B) There is acceptable evidence to establish that it was received at the Government installation designated for receipt of offers and was under the Government’s control prior to the time set for receipt of offers; or
(C) If this solicitation is a request for proposals, it was the only proposal received.
(ii) However, a late modification of an otherwise successful offer, that makes its terms more favorable to the Government, will be considered at any time it is received and may be accepted.
(3) Acceptable evidence to establish the time of receipt 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.