RFQ_P15PS02901.docx

REQUEST FOR QUOTE

P15PS02901

DEPARTMENT OF THE INTERIOR (DOI)

NATIONAL PARK SERVICE (NPS)

TRAFFIC COUNT DATABASE

Solicitation Format

(A) Standard Form (SF) 1449

(B) Contract Clauses –

(1) 52.212-4 Contract Terms and Conditions – Commercial Items (by reference, see SF 1449 Block 27a)

(2) Addenda to 52.212-4; and

(3) 52.212-5 Contract Terms and Conditions required to Implement Statutes or Executive Orders;

(C) Solicitation documents, exhibits and attachments

(D) Solicitation provisions –

(1) 52.212-1 Instructions to Offerors – Commercial Items (by reference, see SF 1449 Block 27a);

(2) Addenda to 52.212-1

(3) 52.212-2 Evaluation – Commercial Items

(4) 52.212-3 Offeror Representations and Certifications – Commercial Items

B. CONTRACT CLAUSES

1) As indicated in Block 27a of the Standard Form 1449, FAR Clause 52.212-4 Contract Terms and Conditions – Commercial Items (May 2015) is incorporated into this solicitation by reference.

2) Addenda to 52.212-4 Contract Terms and Conditions – Commercial Items (May 2015)

Addendum 1.0: STATEMENT OF REQUIREMENTS

1.1 Background

The National Park Service (NPS) requires storage of traffic data as part of the Traffic Management Program. Data are collected (auto polled) daily from 109 Automatic Traffic Recorder (ATR) continuous traffic count stations located in 31 national parks in 21 different states. The counts are downloaded to the Field Operations Technical Support Center (FOTSC) of the NPS Transportation Program located in Denver, Colorado. The data are screened for data anomalies and used to generate monthly and annual traffic data reports. The current database is obsolete and does not operate on a NPS supported Information Technology platform.

The NPS requires the ability to permanently store traffic data collected from existing and future continuous count stations and coverage count stations.

Currently traffic data are collected using Peek Traffic Corporation’s traffic counters, either the ADR-Sabre or the ADR-1000. Auto polling is conducted using Peek’s auto polling software.

The NPS currently has approximately 15 years of stored historic traffic data in electronic format, available on a stand-alone hard drive, equivalent to 32,000 files all of which are saved in either a .PNR or .IND format that must be integrated into the new database under this contract.

1.1.1 Purpose

The purpose of this contract is to provide a Commercial Off-the-Shelf (COTS) solution either using NPS or vendor hosted facility capable of meeting the requirements listed within 1.2 Tasks.

The solution must meet Federal Regulations for 508 Compliance (See Attachment 5 GPAT).

All quotes should include base year plus 4 option years pricing and should indicate if the pricing is reflective of vendor hosting or NPS hosting. If the pricing differs between the two hosting options, contractors should provide the information for both options on two separate copies of the Schedule of Supplies and Services found at Addendum 2.0 of this RFQ.

1.2 TASKS

TASK 1 – TRAFFIC DATABASE WITH CAPABILITIES TO MEET THE FOLLOWING REQUIREMENTS:

REQUIREMENT 1.0. General Database Requirements

Database requirements are presented in Appendix A. In addition:

· Database shall import traffic data on a predefined frequency (e.g., daily, weekly, etc.) from the computer which auto polls the traffic data.

· Database shall maintain raw (prior to QA/QC updates) and imputed version of the traffic data.

· Database shall have the ability to allow for the upload of historic data from existing Peek PRN and IND files.

· Database shall have ability to contain a minimum of 300 continuous count stations and 1,000 coverage count stations, and 30 years of traffic data.

· Solution shall allow various levels of data access, including:

· Ability to create and download reports and graphs from imputed and raw data (see Requirement 4).

· Super user with ability to create and run QA/QC scripts, and make changes to data to be saved as imputed data.

· System Administrator – to add users, monitor system performance, log files.

REQUIREMENT 2.0. Continuous Count Station Requirements

· Ability to report continuous count station status as functioning correctly or not functioning correctly (either working or not working correctly).

· Ability for user to record maintenance data information (e.g., call to phone company for repair on line), external information affecting count station such as lane closures or weather events and the ability to preserve historic data on continuous count station maintenance data.

· A minimum list of data fields in provided in Appendix B.

REQUIREMENT 3.0. QA/QC

COTS product shall allow the user to make changes to meet the following QA/QC requirements without further customization of the product by the vendor:

· Ability to create Quality Assurance/Quality Checks (QA/QC) validation procedures based on industry standards such as American Association of State Highway and Transportation Officials (AASHTO) Guidelines for Traffic Monitoring Guide (TMG), Traffic Monitoring Guide (TMG) and Highway Performance Monitoring System (HPMS).

· Ability to add additional QA/QC checks, edit existing QA/QC, and delete QA/QC checks as needed, in accordance with the examples provided in Appendix C.

· Ability to flag data that fail QA/QC checks.

· Ability to impute or accept flagged data.

REQUIREMENT 4.0. Reporting and Data Sharing Requirements

Monthly and Annual reports must have following abilities:

· Reports and graphs will be generated by count stations.

· Reports and graphs will have ability to span multiple years and multiple months for a count station.

· Reports and graphs need to be broken down by lane, by direction, or for all lanes.

· Minimum format for download of data, reports and graphs will be latest versions of MS-Word, MS-Excel and Adobe PDF.

· Ability to export or serve (view) imputed data for use in other NPS Asset Management systems. See Appendix D for example schema of export/view which includes data from other Asset Management systems and Traffic Count data.

· Ability to use imputed data in standard reports as a PDF to be provided via web access for the general public.

Sub- Requirement 4.1. Additional Monthly Report Requirements

· Create monthly reports based on individual lane, direction, or count station. For Word downloads, reports will fit on one page for the parameters selected. For example if report was by count station, the report would be one page; however, if the report was by lane and there were six lanes, the report would contain six pages (one per lane).

· Reports shall display all the data for various subgroup increment bins, such as vehicle length (e.g. vehicles less than 30’ and greater than 30’), vehicle classification (using FHWA standards) or by speed (e.g. less than 50 mph, 50 -60 mph, 60-70 mph, and greater than 70 mph).

· As a minimum the reports shall contain:

· Month and Year

· File Name

· Park Name and Park Alpha Code

· Count Station Name

· Count Station Number

· GPS Coordinates

· Lane

· Direction

· Hourly Traffic Volumes for Each Day of Month (24 total)

· Daily Total

· Hourly Totals for Month (24 total)

· Day of Week Total

· Number of Days Traffic Data were Collected, by Day

· Average Day of Week Total

· Monthly Total Traffic Volume

· ADT – Average Daily Traffic

· Weekday Total

· Weekday Average

· Weekend Total

· Weekend Average

· Directional Distribution

· Previous Year’s Values and Percent Change

Sub-Requirement 4.2. Additional Annual Report Requirements

· Create annual reports based on individual lane, direction, count station, or of a selected group of count stations. For individual count stations grouping by lane, direction, or count station is required. For a group of count stations, data will only be provided at the count station level. Reports shall contain at a minimum:

Continuous Count Stations (by lane, direction or entire count station)

· Park Name and Park Alpha Code

· Count Station Name(s)

· Count Station Number(s)

· GPS Coordinates

· Lane(s)

· Direction(s)

· MADT – Monthly Average Daily Traffic (12, one per month)

· MAWDT – Monthly Average Weekday Traffic (12, one per month)

· MAWET – Monthly Average Weekend Traffic (12, one per month)

· ADTWDF – Average Daily Traffic Weekday Factor (12, one per month)

· ADTWEF – Average Daily Traffic Weekend Factor (12, one per month)

· ADTF – Average Daily Traffic Week Factor (12, one per month)

· STWDF – Seasonal Traffic Weekday Factor (12, one per month)

· STWEF – Seasonal Traffic Weekend Factor (12, one per month)

· STWF – Seasonal Traffic Week Factor (12, one per month)

· AADT – Annual Average Daily Traffic

· AAWDT – Annual Average Weekday Traffic

· AAWET – Annual Average Weekend Traffic

· SADT – Seasonal Average Daily Traffic Percent AADT by hour (24 hourly percents)

· K Factor (am and pm) - the percentage of the AADT in both directions during the peak hour. For road with an NPS Functional Classification of VII (Urban Parkway).

· D Factor (am and pm) - the percentage of traffic in the peak direction during the peak hour for road with an NPS Functional Classification of VII (Urban Parkway).

· Volume and percent of each type collected (For sites that collect vehicle classification, length or speed) Coverage Count Stations (by direction or entire coverage count station)

· Park Name and Park Alpha Code

· Count Station Name

· Count Station Number

· GPS Coordinates

· Begin Date

· End Date

· Reference Station

· Seasonal Factor Used

· Annual Factor Used

· AADT – Annual Average Daily Traffic

· SADT – Seasonal Average Daily Traffic

· ADT-Average Daily Traffic

· Percent ADT by hour (24 hourly percents)

By park or NPS region

· Region Name

· Park Name and Park Alpha Code

· Route(s)

· Count Station Names

· Count Station Number(s)

· Route Name/Description(s)

· Route Length(s)

· NPS Functional Class(es)

· Four Previous Years and Current AADT

· Percent Growth (for Last xx Years)

· DVMT – Daily Vehicle Miles Traveled

· Percent AADT by Hour (24 Hourly Percents)

REQUIREMENT 5.0. Help Desk Support

· Solution shall provide access to technical support from 9 am EST to 6 pm EST, Monday through Friday

· Allow for five (5) named NPS users to have access to technical support

REQUIREMENT 6.0. System Security

· The System Security Solution Architecture shall include the mechanisms to protect the system from unauthorized access by fully managing the services that a user can access and preventing access to the system by any unauthorized individual or process

· Solution shall use TCP/IP Protocol Suite

· Solution shall be TLS (Transport Layer Security) Compliant

· Solution shall work with the NPS Virus Protection software

These requirements are influenced by the following documents:

· DOI Computer Password Policy

· DOI Department Manual 375 Chapter 19 - Information Technology Security Program

· DOI Privacy Act Regulations on minimum safeguard requirements at 43 CFR 2.51

· DOI Sensitive Information Guideline

· NIST SP 800-53, Recommended Security Controls for Federal Information Systems, Second Public Draft

· NIST SP 800-64 - Security Considerations in the Information System Development Life Cycle

· FIPS Pub 199, Standards for Security Categorization of Federal Information and Information Systems

· OMB A-130, Management of Federal Information Resources

· OMB 06-16, Protection of Sensitive Agency Information

· DOI IT Security Policy Handbook v 3.0

REQUIREMENT 7.0. Implementation

· Kick-off meeting within 10 days of contract award

· Product shall operate on Microsoft SQL 2014 database server and within a Microsoft Windows Server environment.

· Contractor shall provide support to implement new Traffic Count Database including moving of existing data into new database.

· Product shall allow for Additional historic data saved as .PRN and .IND to be integrated into the database.

· All aspects of solution shall be functional under the Federal Desktop Core Configuration (FDCC) and USGCB (United States Government Configuration Baseline).

Contractor shall test all aspects of their product against the Federal Desktop Core Configuration (FDCC) and USGCB (United States Government Configuration Baseline) for full functionality: FDCC/USGCB VHD files are available at: http://nvd.nist.gov/fdcc/download_fdcc.cfm and http://usgcb.nist.gov/usgcb/download_vhd.html

· Web Browser Compatibility – The solution shall allow for web interface via the most current version Windows and Macintosh browsers, including (but not limited to) Internet Explorer, Chrome, Firefox, Safari, and Opera.

· Solution shall be accessible from browsers which are TLS compatible.

Addendum 2.0: SCHEDULE OF SUPPLIES AND SERVICES

The following schedule of supplies and services contains a Contract Line Item (CLIN) structure which corresponds to the supplies and services described in Addendum 1.0 (Statement of Requirements).

This table must be filled out by the contractor and returned as part of the quote.

Pricing must indicate if it is reflective of vendor hosting or NPS hosting. If the pricing differs between the two hosting options, contractors should provide the information for both options on two separate copies of this Schedule of Supplies and Services.

BASE PERIOD (09/30/2015 – 09/29/2016)

FIRM-FIXED-PRICE CLINs

Database License (Enterprise)

Hosting and Support (including helpdesk)

Existing Data Migration

Total

Total BASE YEAR

OPTION PERIOD 1 (09/30/2016 – 09/29/2017)

Hosting and Support (including helpdesk)

Total

Total Option Period 1

OPTION PERIOD 2 (09/30/2017 – 09/29/2018)

Hosting and Support (including helpdesk)

Total

Total Option Period 2

OPTION PERIOD 3 (09/30/2018 – 09/29/2019)

Hosting and Support (including helpdesk)

Total

Total Option Period 3

OPTION PERIOD 4 (09/30/2019 – 09/29/2020)

Hosting and Support (including helpdesk)

Total

Total Option Period 4

TOTAL BASE PERIOD $______________

TOTAL OPTION PERIOD 1 $______________

TOTAL OPTION PERIOD 4 $______________

GRAND TOTAL ALL OPTION PERIODS $______________

Addendum 3.0: PLACE OF INSPECTION

Inspection and acceptance of all work performance, reports and other deliverables under this contact shall be performed by the appointed Contracting Officer’s Representative (COR) and/or any Technical Points of Contact (TPOCs) in Lakewood, CO or electronically from other locations as necessary.

Addendum 4.0 SCOPE OF INSPECTION

In accordance with the Inspection of Services – Fixed-Price clause, (Federal Acquisition Regulation (FAR) 52.246-4, Aug 1996), the Government will evaluate the Contractor's performance under this contract.

All deliverables will be inspected for content, completeness accuracy and confirmation to the contract requirements by the COR. Inspection may include validation of information or software functionality and the scope and nature of the inspection will be sufficiently comprehensive to ensure the completeness, quality and adequacy of all deliverables.

The Contractor shall provide highly qualified and motivated individuals who possess the skills, knowledge and training to perform the services required by this contract. The personnel shall be capable of working independently and with a demonstrated working knowledge of project management best practices as defined by the Project Management Institute’s Project Management Book of Knowledge. Personnel shall be fluent when both speaking and writing in the English language.

Addendum 5.0 BASIS OF ACCEPTANCE

The basis for acceptance shall be in compliance with the requirements set forth in the contract, the contractor’s quote and the commercial item terms and conditions of the contract.

Addendum 6.0 PERIOD OF PERFORMANCE

The contract will consist of 1, 12-month base period and 4, 12-month option periods for a total of 5 years (60 months).

Addendum 7.0 PLACE OF PERFORMANCE

The primary place of performance is expected to be the Contractor’s facility.

If required, work at a Government site shall be performed at the following:

National Park Service – Denver Service Center 12795 West Alameda Parkway Lakewood, CO 80228

Addendum 8.0 CONTRACT SCHEDULE AND MILESTONE DATES

The following schedule of milestones will be used by the COR to monitor timely progress under this contract.

MILESTONE/

DELIVERABLE

Addendum 9.0 CONTRACTING OFFICER’S REPRESENTATIVE (COR)

The Contracting officer will appoint a COR in writing for the contract through a COR Appointment Letter that will be provided upon award (Attachment 7). The COR will receive for the Government, all work called for by the contract and will represent that Contracting Officer in technical phases of the work. The COR will provide no supervisory or instructional assistance to contractor personnel.

The COR is not authorized to change any of the terms and conditions, the scope, schedule or price of the contract. Changes in the terms and conditions, the scope, schedule or price will be made only by the Contracting Officer via properly executed modifications to the contract.

Addendum 10.0 CONTRACT ADMINISTRATION

Contracting Officer:

Jennifer Dansby

NPS, WASO-WCO

7333 W. Jefferson Ave., Suite 100 Lakewood, CO 80235 Telephone: (303) 969-2353 E-mail: jennifer_dansby@nps.gov

Contracting Officer’s Representative:

To be provided at the time of award

Addendum 11.0 GOVERNMENT FURNISHED INFORMATION AND EQUIPMENT

Contractor personnel shall observe all internal and Privacy Act regulations which apply to this requirement, the agency, and the Government.

· Privacy Act of 1974.

· Uniform Security Regulation, dated September 1985.

· It is the intent to have the tasks identified herein fulfilled at the vendor’s office location, however at such time where the vendor is in attendance at any NPS locations, the vendor shall identify key personnel that shall access both sites for this contract. The vendor shall provide a security policy statement for their company and any sub-contractor servicing this maintenance contract. The security statement shall clearly state how employees shall have access to the security equipment identified in the contract are trained and monitored. For certain sensitive systems the contractor shall submit to the COTR/CO a completed request for security information on each proposed employee.

· The Contractor shall safeguard all Government-owned equipment and materials in the Contractor's possession or used in the day-today performance of the Contract. The Government will not be held accountable/responsible for any Contractor items which may have been lost or stolen. Responsibility for the Contractor's compliance with internal security at the site shall be assigned to the Contractor.

· All Contractor personnel shall be briefed on site security operating procedures prior to or upon commencement of contract award and shall be debriefed upon termination. The Government shall be responsible for all continuing security training of the Contractor.

· The Government shall provide all equipment necessary to connect and perform work on the NPS network. Non-government provided equipment is not permitted to connect to the NPS network. The Government will provide access to relevant Government information and documents as required and available.

Addendum 12.0 PHYSICAL SECURITY

The Contractor shall safeguard all Government-owned equipment and materials in the Contractor's possession or used in the day-to-day performance of the Contract. The Government will not be held accountable/responsible for any contractor items that may have been lost or stolen. Responsibility for the contractor's compliance with internal security at the site shall be assigned to the contractor. All contractor personnel shall be briefed on site security operating procedures prior to or upon commencement of contract award and shall be debriefed upon termination. The Government shall be responsible for all continuing security training of the contractor.

Addendum 13.0 – TRAVEL

Any travel other than local travel (defined as being travel within 50 miles of the contractor’s location and which is not reimbursable under this contract) must be clearly defined prior to performance and have been established by the contract. In addition, all travel when authorized must be coordinated with the Project Contact and the COTR/CO four (4) work days prior to the start of proposed travel period. All travel shall be reimbursed as per the current Federal Travel Regulations in effect at the time of travel.

Addendum 14.0 – SECTION 508 COMPLIANCE REQUIREMENTS Unless the Government invokes an exemption, all Electronic and Information Technology (EIT) products and services quotes shall fully comply with Section 508 of the rehabilitation Act of 1973, per the 1998 Amendments, 29 United States Code (U.S.C.) 749d, and the Architectural and Transportation barriers Compliance Board’s Electronic and Information Technology Accessibility Standards at 36 Code of Federal Regulations (CFR) 1194. The contractor shall identify all EIT products and services provided and state the degree of compliance with the applicable standards.

Addendum 15.0 - ADDITIONAL CLAUSES INCORPORATED BY REFERENCE

Fill In: 30 days Nov 1999

Fill In: 30 days Fill In: 60 days Mar 2000

15.1 DEPARTMENT OF THE INTERIOR LOCAL CLAUSES

Electronic Invoicing and Payment Requirements - Invoice Processing Platform (IPP) (April 2013)

Payment requests must be submitted electronically through the U. S. Department of the Treasury's Invoice Processing Platform System (IPP).

"Payment request" means any request for contract financing payment or invoice payment by the Contractor. To constitute a proper invoice, the payment request must comply with the requirements identified in the applicable Prompt Payment clause included in the contract, or the clause 52.212-4 Contract Terms and Conditions - Commercial Items included in commercial item contracts. The IPP website address is: https://www.ipp.gov.

Under this contract, the following documents are required to be submitted as an attachment to the IPP invoice: [NONE]

The Contractor must use the IPP website to register, access and use IPP for submitting requests for payment. The Contractor Government Business Point of Contact (as listed in SAM will receive enrollment instructions via email from the Federal Reserve Bank of Boston (FRBB) within 3 - 5 business days of the contract award date. Contractor assistance with enrollment can be obtained by contacting the IPP Production Helpdesk via email ippgroup@bos.frb.org or phone (866) 973-3131.

If the Contractor is unable to comply with the requirement to use IPP for submitting invoices for payment, the Contractor must submit a waiver request in writing to the Contracting Officer with its proposal or quotation.

(End of Template)

1452.201-70 AUTHORITIES AND DELEGATIONS (SEPT 2011)

(a) The Contracting Officer is the only individual authorized to enter into or terminate this contract, modify any term or condition of this contract, waive any requirement of this contract, or accept nonconforming work.

(b) The Contracting Officer will designate a Contracting Officer's Representative (COR) at time of award. The COR will be responsible for technical monitoring of the contractor's performance and deliveries. The COR will be appointed in writing, and a copy of the appointment will be furnished to the Contractor. Changes to this delegation will be made by written changes to the existing appointment or by issuance of a new appointment.

(c) The COR is not authorized to perform, formally or informally, any of the following actions:

(1) Promise, award, agree to award, or execute any contract, contract modification, or notice of intent that changes or may change this contract;

(2) Waive or agree to modification of the delivery schedule;

(3) Make any final decision on any contract matter subject to the Disputes Clause;

(4) Terminate, for any reason, the Contractor's right to proceed;

(5) Obligate in any way, the payment of money by the Government.

(d) The Contractor shall comply with the written or oral direction of the Contracting Officer or authorized representative(s) acting within the scope and authority of the appointment memorandum.

The Contractor need not proceed with direction that it considers to have been issued without proper authority. The Contractor shall notify the Contracting Officer in writing, with as much detail as possible, when the COR has taken an action or has issued direction (written or oral) that the Contractor considers to exceed the COR's appointment, within 3 days of the occurrence. Unless otherwise provided in this contract, the Contractor assumes all costs, risks, liabilities, and consequences of performing any work it is directed to perform that falls within any of the categories defined in paragraph (c) prior to receipt of the Contracting Officer's response issued under paragraph (e) of this clause.

(e) The Contracting Officer shall respond in writing within 30 days to any notice made under paragraph (d) of this clause. A failure of the parties to agree upon the nature of a direction, or upon the contract action to be taken with respect thereto, shall be subject to the provisions of the Disputes clause of this contract.

(f) The Contractor shall provide copies of all correspondence to the Contracting Officer and the COR.

(g) Any action(s) taken by the Contractor, in response to any direction given by any person acting on behalf of the Government or any Government official other than the Contracting Officer or the COR acting within his or her appointment, shall be at the Contractor's risk.

(End of clause)

3) FAR CLAUSE 52.212-5 Contract Terms and Conditions Required to Implement Statutes or Executive Orders - Commercial Items. (May 2015)

(a) The Contractor shall comply with the following Federal Acquisition Regulation (FAR) clauses, which are incorporated in this contract by reference, to implement provisions of law or Executive orders applicable to acquisitions of commercial items:

(1) 52.209-10, Prohibition on Contracting with Inverted Domestic Corporations (Dec 2014)

(2) 52.233-3, Protest After Award (AUG 1996) (31 U.S.C. 3553).

(3) 52.233-4, Applicable Law for Breach of Contract Claim (OCT 2004)(Public Laws 108-77 and 108-78 (19 U.S.C. 3805 note)).

(b) The Contractor shall comply with the FAR clauses in this paragraph (b) that the Contracting Officer has indicated as being incorporated in this contract by reference to implement provisions of law or Executive orders applicable to acquisitions of commercial items:

[Contracting Officer check as appropriate.]

X (1) 52.203-6, Restrictions on Subcontractor Sales to the Government (Sept 2006), with Alternate I (Oct 1995) (41 U.S.C. 4704 and 10 U.S.C. 2402).

__ (2) 52.203-13, Contractor Code of Business Ethics and Conduct (Apr 2010) (41 U.S.C. 3509)).

__ (3) 52.203-15, Whistleblower Protections under the American Recovery and Reinvestment Act of 2009 (June 2010) (Section 1553 of Pub. L. 111-5). (Applies to contracts funded by the American Recovery and Reinvestment Act of 2009.)

X (4) 52.204-10, Reporting Executive Compensation and First-Tier Subcontract Awards (Jul 2013) (Pub. L. 109-282) (31 U.S.C. 6101 note).

__ (5) [Reserved].

__ (6) 52.204-14, Service Contract Reporting Requirements (Jan 2014) (Pub. L. 111-117, section 743 of Div. C).

__ (7) 52.204-15, Service Contract Reporting Requirements for Indefinite-Delivery Contracts (Jan 2014) (Pub. L. 111-117, section 743 of Div. C).

X (8) 52.209-6, Protecting the Government’s Interest When Subcontracting with Contractors Debarred, Suspended, or Proposed for Debarment. (Aug 2013) (31 U.S.C. 6101 note).

X (9) 52.209-9, Updates of Publicly Available Information Regarding Responsibility Matters (Jul 2013) (41 U.S.C. 2313).

__ (10) [Reserved].

__ (11)(i) 52.219-3, Notice of HUBZone Set-Aside or Sole-Source Award (Nov 2011) (15 U.S.C. 657a).

__ (ii) Alternate I (Nov 2011) of 52.219-3.

__ (12)(i) 52.219-4, Notice of Price Evaluation Preference for HUBZone Small Business Concerns (OCT 2014) (if the offeror elects to waive the preference, it shall so indicate in its offer) (15 U.S.C. 657a).

__ (ii) Alternate I (JAN 2011) of 52.219-4.

__ (13) [Reserved] X (14)(i) 52.219-6, Notice of Total Small Business Set-Aside (Nov 2011) (15 U.S.C. 644).

__ (ii) Alternate I (Nov 2011).

__ (iii) Alternate II (Nov 2011).

__ (15)(i) 52.219-7, Notice of Partial Small Business Set-Aside (June 2003) (15 U.S.C. 644).

__ (ii) Alternate I (Oct 1995) of 52.219-7.

__ (iii) Alternate II (Mar 2004) of 52.219-7.

X (16) 52.219-8, Utilization of Small Business Concerns (Oct 2014) (15 U.S.C. 637(d)(2) and (3)).

__ (17)(i) 52.219-9, Small Business Subcontracting Plan (Oct 2014) (15 U.S.C. 637(d)(4)).

__ (ii) Alternate I (Oct 2001) of 52.219-9.

__ (iii) Alternate II (Oct 2001) of 52.219-9.

__ (iv) Alternate III (Oct 2014) of 52.219-9.

__ (18) 52.219-13, Notice of Set-Aside of Orders (Nov 2011)(15 U.S.C. 644(r)).

X (19) 52.219-14, Limitations on Subcontracting (Nov 2011) (15 U.S.C. 637(a)(14)).

__ (20) 52.219-16, Liquidated Damages-Subcon-tracting Plan (Jan 1999) (15 U.S.C. 637(d)(4)(F)(i)).

__ (21) 52.219-27, Notice of Service-Disabled Veteran-Owned Small Business Set-Aside (Nov 2011) (15 U.S.C. 657 f).

X (22) 52.219-28, Post Award Small Business Program Rerepresentation (Jul 2013) (15 U.S.C. 632(a)(2)).

__ (23) 52.219-29, Notice of Set-Aside for Economically Disadvantaged Women-Owned Small Business (EDWOSB) Concerns (Jul 2013) (15 U.S.C. 637(m)).

__ (24) 52.219-30, Notice of Set-Aside for Women-Owned Small Business (WOSB) Concerns Eligible Under the WOSB Program (Jul 2013) (15 U.S.C. 637(m)).

X (25) 52.222-3, Convict Labor (June 2003) (E.O. 11755).

X (26) 52.222-19, Child Labor-Cooperation with Authorities and Remedies (Jan 2014) (E.O. 13126).

X (27) 52.222-21, Prohibition of Segregated Facilities (Apr 2015).

X (28) 52.222-26, Equal Opportunity (Apr 2015) (E.O. 11246).

X (29) 52.222-35, Equal Opportunity for Veterans (Jul 2014)(38 U.S.C. 4212).

X (30) 52.222-36, Equal Opportunity for Workers with Disabilities (Jul 2014) (29 U.S.C. 793).

X (31) 52.222-37, Employment Reports on Veterans (JUL 2014) (38 U.S.C. 4212).

X (32) 52.222-40, Notification of Employee Rights Under the National Labor Relations Act (Dec 2010) (E.O. 13496).

X (33)(i) 52.222-50, Combating Trafficking in Persons (Mar 2015) (22 U.S.C. chapter 78 and E.O. 13627).

__ (ii) Alternate I (Mar 2015) of 52.222-50 (22 U.S.C. chapter 78 and E.O. 13627).

__ (34) 52.222-54, Employment EligibilitY Verification (AUG 2013). (Executive Order 12989). (Not applicable to the acquisition of commercially available off-the-shelf items or certain other types of commercial items as prescribed in 22.1803.)

__ (35)(i) 52.223-9, Estimate of Percentage of Recovered Material Content for EPA–Designated Items (May 2008) (42 U.S.C. 6962(c)(3)(A)(ii)). (Not applicable to the acquisition of commercially available off-the-shelf items.)

__ (ii) Alternate I (May 2008) of 52.223-9 (42 U.S.C. 6962(i)(2)(C)). (Not applicable to the acquisition of commercially available off-the-shelf items.)

__ (36)(i) 52.223-13, Acquisition of EPEAT®-Registered Imaging Equipment (JUN 2014) (E.O.s 13423 and 13514).

__ (ii) Alternate I (Jun 2014) of 52.223-13.

__ (37)(i) 52.223-14, Acquisition of EPEAT®-Registered Televisions (JUN 2014) (E.O.s 13423 and 13514).

__ (ii) Alternate I (Jun 2014) of 52.223-14.

(38) 52.223-15, Energy Efficiency in Energy-Consuming Products (DEC 2007) (42 U.S.C. 8259b).

__ (39)(i) 52.223-16, Acquisition of EPEAT®-Registered Personal Computer Products (JUN 2014) (E.O.s 13423 and 13514).

__ (ii) Alternate I (Jun 2014) of 52.223-16.

X (40) 52.223-18, Encouraging Contractor Policies to Ban Text Messaging While Driving (AUG 2011) (E.O. 13513).

__ (41) 52.225-1, Buy American-Supplies (May 2014) (41 U.S.C. chapter 83).

(42)(i) 52.225-3, Buy American-Free Trade Agreements-Israeli Trade Act (May 2014) (41 U.S.C. chapter 83, 19 U.S.C. 3301 note, 19 U.S.C. 2112 note, 19 U.S.C. 3805 note, 19 U.S.C. 4001 note, Pub. L. 103-182, 108-77, 108-78, 108-286, 108-302, 109-53, 109-169, 109-283, 110-138, 112-41, 112-42, and 112-43.

__ (ii) Alternate I (May 2014) of 52.225-3.

__ (iii) Alternate II (May 2014) of 52.225-3.

__ (iv) Alternate III (May 2014) of 52.225-3.

__ (43) 52.225-5, Trade Agreements (NOV 2013) (19 U.S.C. 2501, et seq., 19 U.S.C. 3301 note).

X (44) 52.225-13, Restrictions on Certain Foreign Purchases (June 2008) (E.O.’s, proclamations, and statutes administered by the Office of Foreign Assets Control of the Department of the Treasury).

__ (45) 52.225-26, Contractors Performing Private Security Functions Outside the United States (Jul 2013) (Section 862, as amended, of the National Defense Authorization Act for Fiscal Year 2008; 10 U.S.C. 2302 Note).

__ (46) 52.226-4, Notice of Disaster or Emergency Area Set-Aside (Nov 2007) (42 U.S.C. 5150).

__ (47) 52.226-5, Restrictions on Subcontracting Outside Disaster or Emergency Area (Nov 2007) (42 U.S.C. 5150).

__ (48) 52.232-29, Terms for Financing of Purchases of Commercial Items (Feb 2002) (41 U.S.C. 4505, 10 U.S.C. 2307(f)).

__ (49) 52.232-30, Installment Payments for Commercial Items (Oct 1995) (41 U.S.C. 4505, 10 U.S.C. 2307(f)).

X (50) 52.232-33, Payment by Electronic Funds Transfer-System for Award Management (Jul 2013) (31 U.S.C. 3332).

__ (51) 52.232-34, Payment by Electronic Funds Transfer-Other than System for Award Management (Jul 2013) (31 U.S.C. 3332).

__ (52) 52.232-36, Payment by Third Party (May 2014) (31 U.S.C. 3332).

X (53) 52.239-1, Privacy or Security Safeguards (Aug 1996) (5 U.S.C. 552a).

__ (54)(i) 52.247-64, Preference for Privately Owned U.S.-Flag Commercial Vessels (Feb 2006) (46 U.S.C. Appx. 1241(b) and 10 U.S.C. 2631).

__ (ii) Alternate I (Apr 2003) of 52.247-64.

(c) The Contractor shall comply with the FAR clauses in this paragraph (c), applicable to commercial services, that the Contracting Officer has indicated as being incorporated in this contract by reference to implement provisions of law or Executive orders applicable to acquisitions of commercial items:

[Contracting Officer check as appropriate.] __ (1) 52.222-17, Nondisplacement of Qualified Workers (May 2014)(E.O. 13495).

__ (2) 52.222-41, Service Contract Labor Standards (May 2014) (41 U.S.C. chapter 67).

__ (3) 52.222-42, Statement of Equivalent Rates for Federal Hires (May 2014) (29 U.S.C. 206 and 41 U.S.C. chapter 67).

__ (4) 52.222-43, Fair Labor Standards Act and Service Contract Labor Standards-Price Adjustment (Multiple Year and Option Contracts) (May 2014) (29 U.S.C. 206 and 41 U.S.C. chapter 67).

__ (5) 52.222-44, Fair Labor Standards Act and Service Contract Labor Standards-Price Adjustment (May 2014) (29 U.S.C. 206 and 41 U.S.C. chapter 67).

__ (6) 52.222-51, Exemption from Application of the Service Contract Labor Standards to Contracts for Maintenance, Calibration, or Repair of Certain Equipment-Requirements (May 2014) (41 U.S.C. chapter 67).

__ (7) 52.222-53, Exemption from Application of the Service Contract Labor Standards to Contracts for Certain Services-Requirements (May 2014) (41 U.S.C. chapter 67).

__ (8) 52.222-55, Minimum Wages Under Executive Order 13658 (Dec 2014)(E.O. 13658).

__ (9) 52.226-6, Promoting Excess Food Donation to Nonprofit Organizations (May 2014) (42 U.S.C. 1792).

__ (10) 52.237-11, Accepting and Dispensing of $1 Coin (Sept 2008) (31 U.S.C. 5112(p)(1)).

(d) Comptroller General Examination of Record. The Contractor shall comply with the provisions of this paragraph (d) if this contract was awarded using other than sealed bid, is in excess of the simplified acquisition threshold, and does not contain the clause at 52.215-2, Audit and Records-Negotiation.

(1) The Comptroller General of the United States, or an authorized representative of the Comptroller General, shall have access to and right to examine any of the Contractor’s directly pertinent records involving transactions related to this contract.

(2) The Contractor shall make available at its offices at all reasonable times the records, materials, and other evidence for examination, audit, or reproduction, until 3 years after final payment under this contract or for any shorter period specified in FAR Subpart 4.7, Contractor Records Retention, of the other clauses of this contract. If this contract is completely or partially terminated, the records relating to the work terminated shall be made available for 3 years after any resulting final termination settlement. Records relating to appeals under the disputes clause or to litigation or the settlement of claims arising under or relating to this contract shall be made available until such appeals, litigation, or claims are finally resolved.

(3) As used in this clause, records include books, documents, accounting procedures and practices, and other data, regardless of type and regardless of form. This does not require the Contractor to create or maintain any record that the Contractor does not maintain in the ordinary course of business or pursuant to a provision of law.

(e)(1) Notwithstanding the requirements of the clauses in paragraphs (a), (b), (c), and (d) of this clause, the Contractor is not required to flow down any FAR clause, other than those in this paragraph (e)(1) in a subcontract for commercial items. Unless otherwise indicated below, the extent of the flow down shall be as required by the clause-

(i) 52.203-13, Contractor Code of Business Ethics and Conduct (Apr 2010) (41 U.S.C. 3509).

(ii) 52.219-8, Utilization of Small Business Concerns (Oct 2014) (15 U.S.C. 637(d)(2) and (3)), in all subcontracts that offer further subcontracting opportunities. If the subcontract (except subcontracts to small business concerns) exceeds $650,000 ($1.5 million for construction of any public facility), the subcontractor must include 52.219-8 in lower tier subcontracts that offer subcontracting opportunities.

(iii) 52.222-17, Nondisplacement of Qualified Workers (May 2014) (E.O. 13495). Flow down required in accordance with paragraph (l) of FAR clause 52.222-17.

(iv) 52.222-21, Prohibition of Segregated Facilities (Apr 2015)

(v) 52.222-26, Equal Opportunity (Apr 2015) (E.O. 11246).

(vi) 52.222-35, Equal Opportunity for Veterans (Jul 2014) (38 U.S.C. 4212).

(vii) 52.222-36, Equal Opportunity for Workers with Disabilities (Jul 2014) (29 U.S.C. 793).

(viii) 52.222-37, Employment Reports on Veterans (Jul 2014) (38 U.S.C. 4212)

(ix) 52.222-40, Notification of Employee Rights Under the National Labor Relations Act (Dec 2010) (E.O. 13496). Flow down required in accordance with paragraph (f) of FAR clause 52.222-40.

(x) 52.222-41, Service Contract Labor Standards (May 2014) (41 U.S.C. chapter 67).

(xi) __(A) 52.222-50, Combating Trafficking in Persons (Mar 2015) (22 U.S.C. chapter 78 and E.O 13627).

__(B) Alternate I (Mar 2015) of 52.222-50 (22 U.S.C. chapter 78 and E.O 13627).

(xii) 52.222-51, Exemption from Application of the Service Contract Labor Standards to Contracts for Maintenance, Calibration, or Repair of Certain Equipment-Requirements (May 2014) (41 U.S.C. chapter 67).

(xiii) 52.222-53, Exemption from Application of the Service Contract Labor Standards to Contracts for Certain Services-Requirements (May 2014) (41 U.S.C. chapter 67).

(xiv) 52.222-54, Employment Eligibility Verification (AUG 2013).

(xv) 52.222-55, Minimum Wages Under Executive Order 13658 (Dec 2014) (Executive Order 13658).

(xvi) 52.225-26, Contractors Performing Private Security Functions Outside the United States (Jul 2013) (Section 862, as amended, of the National Defense Authorization Act for Fiscal Year 2008; 10 U.S.C. 2302 Note).

(xvii) 52.226-6, Promoting Excess Food Donation to Nonprofit Organizations (May 2014) (42 U.S.C. 1792). Flow down required in accordance with paragraph (e) of FAR clause 52.226-6.

(xviii) 52.247-64, Preference for Privately Owned U.S.-Flag Commercial Vessels (Feb 2006) (46 U.S.C. Appx. 1241(b) and 10 U.S.C. 2631). Flow down required in accordance with paragraph (d) of FAR clause 52.247-64.

(2) While not required, the contractor may include in its subcontracts for commercial items a minimal number of additional clauses necessary to satisfy its contractual obligations.

(End of clause)

C. SOLICITATION DOCUMENTS, EXHIBITS AND ATTACHMENTS

1. Appendix A - Minimum Database Requirements

2. Appendix B - Minimum List of Data Fields

3. Appendix C - NPS QA/QC

4. Appendix D – Examples of Traffic Count Database View to integrate with Other Data Management Systems*

5. GPAT Documentation of 508 Compliance Requirements

6. Past Performance Reference Sheet – to be removed at the time of award

7. COR Appointment Letter – to be provided at the time of award

*The views are provided in a format that allows the contractor to double click on the picture to see an enlargement

D. SOLICITATION PROVISIONS

1) As indicated in Block 27a of the Standard Form 1449, FAR Clause 52.212-1 Instructions to Offerors- Commercial Items is incorporated into this solicitation by reference.

2) Addenda to 52.212-1 Instructions to Offerors – Commercial Items (April 2014)

Addendum 1.0: TAILORED INSTRUCTIONS FOR THE SUBMISSION OF QUOTES

This Addendum to FAR Provision 52.212-1 tailors the instructions for the submission of Quotes found at FAR 52.212-1(b)

1.1 General Instructions

a. Offerors shall furnish the information required by this RFQ.

A Standard Form (SF) 1449, “Solicitation/Contract/Order for Commercial Items” completed and signed by the Offeror, Block 30(a), constitutes the Offeror’s acceptance of the terms and conditions of the proposed contract. Therefore, the SF 1449 must be executed by a representative of the Offeror authorized to commit the Offeror to contractual obligations.

b. Offerors are expected to examine the entire RFQ document. Failure to do so will be at the offeror’s own risk.

c. The Government may make award based upon initial offers received, without discussion of such offer. Quotes shall set forth full, accurate and complete information as required by this RFQ (including relevant attachments).

1.2 Submission of Questions

Questions must be received before the date specified for the receipt of questions provided in the notice of combined synopsis and solicitation. Questions or requests for extension submitted after the cut-off date will not be considered.

Any information provided to one prospective offeror concerning this RFQ shall be provided to all prospective offerors as an amendment to this RFQ.

1.3 Availability of Software

All commercial software quoted in response to this RFQ shall have been formally announced for general release on or before the closing date of this RFQ.

1.4 Format for Quote Submission

Each Quote consists of two parts.

Part I is the Price Quote, and shall contain the following:

a. A signed SF 1449

b. A completed Addendum 2.0: SCHEDULE OF SUPPLIES AND SERVICES

· The information requested is required to enable the Government to perform a price analysis and to confirm that the quoted pricing is based upon the offerors commercially available pricing schedule/structure at competitive rates. The offeror is required to submit supporting evidence for the pricing which may include: a commercial price list, or other established software license pricing documentation which adequately demonstrates that the quoted pricing is generally made available to the offerors commercial clients.

c. Any cost or pricing assumptions

Part II is the Technical Quote, and shall contain the following Rated Technical Factors:

a. Technical Approach, including a narrative of COTS software compliance.

· The offeror shall provide a brief narrative, not to exceed 12 pages, of the quoted COTS software product’s compliance with all of the requirements of this RFQ with regard to: QA/QC procedures, Reports, Data Views and Exports, Data Storage capacity and Factor Creation as stated in Addendum 1.0. The offeror may include graphics at its option, not exceeding he overall page limit.

The narrative shall identify the nature and extent of configuration required to meet the RFQ requirements. Configuration is acceptable, custom programming is not acceptable. The offerors technical narrative should describe the suggested configuration, installation, integration and report generation of the COTS product and identify the features and functionality that are relevant to meeting the RFQ requirements.

· The narrative shall also identify the version and release of the product, the date of first commercial availability, the licensor of the product any unique hardware or software environmental requirements. This demonstration is not counted against the page limit and may be provided in a spreadsheet format.

· The offeror may provide supporting evidence of the compliance described in the technical narrative and may include a product brochure, use manual, training manual or other substantiating evidence that the COTS product meets the requirement. This supplemental evidence will not be counted against the page limitation.

b. Identification of one individual Point of Contact (POC)/Key Personnel who will serve as the Project Manager. Desirable qualifications for this individual include:

· Demonstrated experience in the installation and configuration of the quoted COTS product

· Experience in quality assurance

· Demonstrated ability to communicate orally and in writing with a management audience.

c. Completed GPAT:

· The offeror must provide a completed Government Product Accessibility Template (GPAT, provided as Attachment 5) demonstrating that the product complies with the requirements of Section 508 of the Rehabilitation Act of 1973, in accordance with Addendum 14.0.

Information regarding what to do with the GPAT provided with this RFQ can be found here: https://section508.gov/blog/what-do-vendors-do-with-gpat

d. Submission of 3 Past Performance References:

· The offeror shall provide Past Performance References for three projects performed within the last three years using the Past Performance Reference Sheet provided as Attachment 6. The examples should be similar in size, scope and complexity as the requirements identified in Addendum 1.0 of this RFQ.

3) FAR Provision 52.212-2 Evaluation – Commercial Items (Oct 2014)

The Government will award a contract resulting from this RFQ to the offeror whose quote is most advantageous to the Government, price and other factors considered. The Government intends to make award without discussions, using the following factors for evaluation:

TECHNICAL EVALUATION FACTORS

· Technical Approach

· POC/Key Personnel

· GPAT

· Past Performance

The Technical factors are listed in descending order of importance. All technical factors combined are more important than price; however the overall quoted price will contribute to the selection decision. The Government will evaluate each of the technical factors to arrive at an overall rating for the written technical quote as a whole. The receipt of an evaluation of Not Acceptable in any single factor may result in the overall quote being found Not Acceptable and therefore ineligible for award.

Factor 1: TECHNICAL APPROACH The Government will evaluate the Technical Approach Factor based on an overall consideration of the following:

a. QA/QC Procedures – the quoted product will be evaluated for its ability to provide the following QA/QC capabilities.

· Ability to create Quality Assurance/Quality Checks (QA/QC) validation procedures based on industry standards such as American Association of State Highway and Transportation Officials (AASHTO) Guidelines for Traffic Monitoring Guide (TMG), Traffic Monitoring Guide (TMG) and Highway Performance Monitoring System (HPMS).

· Ability to add additional QA/QC checks, edit existing QA/QC, and delete QA/QC checks as needed. (See Appendix C from Traffic Count Database Requirements document for examples.)

· Ability to flag data that fail QA/QC checks.

· Ability to impute or accept flagged data.

b. Reports– the quoted product will be evaluated for its ability to provide the following report generation capabilities.

· Reports and graphs will be generated by count stations.

· Reports and graphs will have ability to span multiple years and multiple months for a count station.

· Reports and graphs need to be broken down by lane, by direction, or for all lanes.

· Ability to use imputed data in standard reports as a PDF to be provided via web access for the general public.

c. Data Views and Exports - the quoted product will be evaluated for its ability to provide the following data view and export capabilities.

· Ability to export or serve (view) imputed data for use in other NPS Asset Management systems. See Traffic Count Database Requirements document Appendix D for example schema of export/view which includes data from other Asset Management systems and Traffic Count data.

· Flexibility in providing data via web services to meet various requirements.

· Minimum format for download of data, reports and graphs will be latest versions of MS-Word, MS-Excel and Adobe PDF.

d. Data Storage - the quoted product will be evaluated for its ability to provide the following data storage capabilities.

· Database shall have ability to contain a minimum of 300 continuous count stations and 1,000 coverage count stations and 30 years of traffic data.

e. Factor Creation - the quoted product will be evaluated for its ability to provide the following factor creation capabilities.

· Ability to create factors (growth, seasonal and annual factors - monthly, weekly, day of week, etc.) for the traffic data.

Factor 2: POC/KEY PERSONNEL The Government will…