DTFH6111R00026upload.pdf

SOLICITATION, OFFER AND AWARD 1. THIS CONTRACT IS A RATED ORDER

UNDER DPAS (15 CFR 700)

RATING

PAGE OF PAGES

1 | 54

2. CONTRACT NUMBER

3. SOLICITATION NUMBER

DTFH61-11-R-00026

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

5. DATE ISSUED

6. REQUISITION/PURCHASE NO.

41-30-11013

7. ISSUED BY CODE 8. ADDRESS OFFER TO (If other than Item 7)

Federal Highway Administration Office of Acquisition Management 1200 New Jersey Avenue, SE E65-101 Washington, DC 20590

NOTE: In sealed bid solicitations “offer” and “offeror” mean “bid” and “bidder”

SOLICITATION

9. Sealed offers in original and 3 copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if hand carried, in the depository located in 1200 New Jersey Avenue, SE, 6th Floor, Room E65-101 until 3:00 p.m. local time by November 11,2011. THIS REQUIREMENT IS A FULL AND OPEN COMPETITION REQUIREMENT.

CAUTION LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and conditions contained in this solicitation. FULL AND OPEN COMPETITION REQUIREMENT

10. FOR A. NAME B. TELEPHONE (NO COLLECT CALLS) C. E-MAIL ADDRESS

INFORMATION

CALL:

Gina Jackson Robin K. Hobbs

AREA CODE

NUMBER

366-4087 366-4004

EXT.

Gina.Jackson@dot.gov Robin.Hobbs@dot.gov

11. TABLE OF CONTENTS

() SEC. DESCRIPTION PAGE(S) () SEC. DESCRIPTION PAGE(S)

PART I - THE SCHEDULE PART II - CONTRACT CLAUSES

√ A SOLICITATION/CONTRACT FORM 1 √ I CONTRACT CLAUSES 25

√ B SUPPLIES OR SERVICES AND PRICE/COST 2 PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACH.

√ C DESCRIPTION/SPECS./WORK STATEMENT 2 √ J LIST OF ATTACHMENTS 34

√ D PACKAGING AND MARKING 12 PART IV - REPRESENTATIONS AND INSTRUCTIONS

√ E INSPECTION AND ACCEPTANCE 12 √ K REPRESENTATIONS, CERTIFICATIONS 35

√ F DELIVERIES OR PERFORMANCE 13 AND OTHER STATEMENTS OF OFFERORS

√ G CONTRACT ADMINISTRATION DATA 16 √ L INSTRS., CONDS., AND NOTICES TO OFFERORS 40

√ H SPECIAL CONTRACT REQUIREMENTS 21 √ M EVALUATION FACTORS FOR AWARD 51

OFFER (Must be fully completed by offeror) NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

12. In compliance with the above, the undersigned agrees, if this offer is accepted within _____ calendar days (60 calendar days unless a different period is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s),

13. DISCOUNT FOR PROMPT PAYMENT

(See Section I, Clause No. 52.232-8)

10 CALENDAR DAYS

20 CALENDAR DAYS

30 CALENDAR DAYS

CALENDAR DAYS

14. ACKNOWLEDGMENT OF AMENDMENTS AMENDMENT NO. DATE AMENDMENT NO. DATE

(The offeror acknowledges receipt of amendments to the SOLICITATION for offerors and related documents numbered and dated):

15A. NAME CODE FACILITY 16. NAME AND TITLE OF PERSON AUTHORIZED TO SIGN

AND OFFER (Type or print)

ADDRESS

OF

OFFEROR

15B. TELEPHONE NUMBER 15C. CHECK IF REMITTANCE 17. SIGNATURE 18. OFFER DATE

AREA CODE

NUMBER

EXT.

ADDRESS IS DIFFERENT FROM ABOVE

- ENTER SUCH ADDRESS IN

SCHEDULE.

AWARD (To be completed by Government)

19. ACCEPTED AS TO ITEMS NUMBERED

20. AMOUNT

21. ACCOUNTING AND APPROPRIATION

22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:

10 U.S.C. 2304(c) ( ) 41 U.S.C. 253(c)(

23. SUBMIT INVOICES TO ADDRESS

SHOWN IN (4 copies unless otherwise specified)

ITEM

24. ADMINISTERED BY (If other than Item 7)CODE 25. PAYMENT WILL BE MADE BY CODE

26. NAME OF CONTRACTING OFFICER (Type or print)

27. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

28. AWARD DATE

IMPORTANT -- Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

AUTHORIZED FOR LOCAL REPRODUCTION STANDARD FORM 33 (Rev. 9-97) Previous edition is unusable Prescribed by GSA – FAR (48 CFR) 53.214(c) mailto:Gina.Jackson@dot.gov mailto:Robin.Hobbs@dot.gov

PART 1

SECTION B - SUPPLIES OR SERVICES AND PRICES/COSTS

B.1 DESCRIPTION OF SERVICES

The Contractor shall develop and maintain an effective web interface program for the Long Term Pavement Performance (LTPP) Information Management System (IMS) through the project entitled, “LTPP Web Interface Program”.

The Government contemplates a hybrid cost plus fixed fee (CPFF)/indefinite-delivery-indefinite-quantity (IDIQ) contract utilizing cost reimbursable and/or fixed-price task orders. The Contractor shall provide and furnish the necessary and qualified personnel, facilities, equipment, materials, and supplies not otherwise provided by the Government, as needed to perform the requirements set forth herein.

The total estimated cost for CLIN 0001 is $(to be filled in at award); which consist of an estimated cost of $(to be filled in at award) and a fixed fee of $(to be filled in at award). The total potential cost for CLIN 0102, 0202 and 0302 is $(to be filled in at award); which consists of a total potential cost of $(to be filled in at award) and a total potential fixed fee of $ to be filled in at award. The minimum guarantee is $(to be filled in at award) for CLINs 0102-0302.

CLIN 0001 Base Year– (24 months) (Task A) – CPFF CLIN 0102 Option Year 1 (12 months) Task B - IDIQ CLIN 0202 Option Year 2 (12 months) (Task C) - IDIQ CLIN 0302 Option Year 3 (12 months) (Task D) - IDIQ

(End of Section B)

SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

C.1 BACKGROUND

The Long-Term Pavement Performance (LTPP) study began in 1987 under the Strategic Highway Research Program (SHRP). LTPP field data collection began in 1989. Since 1992, FHWA has maintained and expanded upon the original SHRP goals through a staff effort in the Office of Infrastructure R&D, LTPP Team, with active input from the State departments of transportation and with the cooperation of the Canadian provincial transportation agencies. The mission of the LTPP program was to promote increased pavement life through:

• Collecting and storing performance data from a large number of in-service highways in the United States and Canada, over an extended period, to support analysis and product development.

• Analyzing these data to describe how pavements perform and to explain why they perform as they do.

• Translating these insights into knowledge and usable engineering products related to pavement design, construction, rehabilitation, maintenance, preservation, and management.

LTPP consists of 2500+ pavement test sections and the information management system that stores the information gathered through the test sections, and supporting technical documentation that seek to determine how and why pavements perform as they do. From this knowledge, new pavement design, management, and maintenance systems can be developed that will extend pavement life and serve a new generation of highway administrators and users. The breadth and length of the program—what is being studied, over what period of time, and why—are probably best understood in terms of the expectations of the highway community for LTPP. These expectations have guided LTPP, and over time, evolution of these expectations has led to some updates of LTPP’s mission.

LTPP IMS

Over the past 20 some years, the LTPP program has accumulated a huge amount of data, as well as a mass of documentation and related tools. These data, documentation, and related tools comprise the comprehensive LTPP Information Management System (IMS). Definition of the term LTPP IMS has changed over the years. While the LTPP program is best known for development of its premiere pavement performance database, it has also created an information warehouse that extends well beyond the collected data. In addition to the data contained in the formal relational databases, the LTPP IMS knowledge base includes findings from early analysis of LTPP data; raw data sources used to populate the electronic databases; extensive documentation for all aspects of experiment design, data acquisition, quality control and data dissemination format; and LTPP related products.

The LTPP IMS is the premier product of the LTPP program. It is the world’s largest long-term pavement performance database. Researchers and engineers in the federal government, state highway departments, industry associations, consulting firms, international community and universities are and will use the LTPP database in research, development, and design projects for decades to come. The LTPP data will continue to be analyzed for as long as it is available to discover cause-and-effect relationships and to explain why some pavements decline rapidly in serviceability, smoothness, and structural integrity while others do not. These relationships and explanations will enable pavement engineers to design pavements rationally, by using local or site-specific data for calibration of design parameters in accordance with the guidelines in the new mechanistic-empirical design guide.

Although it is not yet complete, it already contains more research-quality data than have ever been collected anywhere. This data contains data that have been collected systematically and rigorously concerning the type, extent, and rate of deterioration of a sample of the nation’s highway pavements as a result of time, traffic, weather, and other influences.

In this solicitation, the LTPP IMS is defined as the mechanisms used to store, preserve, and disseminate the electronic data, resources, information, research findings, and electronic tools and products from the LTPP program. The LTPP IMS is comprised of two major components:

the Pavement Performance Database (PPDB) and the Ancillary Information Management System

(AIMS).

LTPP PPDB – LTPP PPDB is the premier pavement performance database produced by the LTPP program. It contains comprehensive data aiming at finding out how and why pavements perform the way they do. The LTPP PPDB was developed and operated as an Oracle® based relational database, and the latest production database is implemented in Oracle 10i system housed on a Microsoft Windows server. In addition to a production database, the system development environment is stored on the server. Two clones of the production database, along with data loader programs, data quality checks programs, and data entry forms comprise the development environment.

The LTPP program issues annual standard data releases (SDRs) of the LTPP PPDB using Microsoft® Access Database formats for easy and convenient dissemination and use. The PPDB SDR enables the users to harness the power of relational databases to manipulate large amounts of data at a reasonable cost and with ease-of-use.

The LTPP PPDB is the largest and most comprehensive pavement performance research database ever created. The current version of the PPDB includes over 300 million records of data comprising 12,000+ individual data elements, stored in more than 500 tables. By virtue of its size and the evolutionary nature of its development, the database can be characterized as a complex data warehouse. Plans to simplify the database structure, add more commonly used computed parameters, improve transparency, and create a ready-for-analysis data structure have been canceled due to budget constraints. Therefore, the LTPP PPDB is somewhat cumbersome to navigate. Providing technical support to warehouse users (i.e., data analysts) has been, and will continue to be, an important activity.

LTPP AIMS – LTPP AIMS is a central electronic archive of the data (not contained in the LTPP PPDB), information, documents, research reports or briefs, and tools that were either collected or developed by the LTPP program, as well as those derived using LTPP data. LTPP AIMS houses ancillary data and information in the form of pictures, video, raw data in its native collection format, images of paper data collection forms, reports, documents, past investigations of LTPP data, etc.

The ancillary data and information contained in LTPP AIMS are even more voluminous than the pavement performance database: the traffic monitoring raw data contains more than 1.5 billion raw traffic classification and weight measurement records; the central electronic ancillary information consisting of data and images not in the pavement performance or traffic databases currently numbers 10,000 files; and over 12,000 35-mm black and white, high-quality photographs of LTPP test sections are stored in the Materials Reference Library.

In addition, Federal Highway Administration (FHWA) has created a central LTPP library at the Turner-Fairbank Highway Research Center (TFHRC) to store the more than 600 physical documents associated with the program, many of which have yet to be converted into a searchable electronic format. Plans to create an indexed electronic library containing all of this information were canceled due to program budget cuts.

The LTPP IMS is housed at the FHWA Turner-Fairbank Highway Research Center, in McLean, VA. An LTPP Data Processing Work Station containing the LTPP PPDB and its data entry forms, as well as portions of the LTPP AIMS, is housed and operated by the LTPP Technical Support Services Contractor in Oakridge Tennessee.

There is a great need to improve public access and understanding of LTPP data, as well as to keep up with the current IT technology. The LTPP program management made a decision to provide access to the LTPP IMS on-demand through a web centric interface and provide education and tools to maximize user understanding of the information.

A subset of the LTPP products is available at www.ltpp-products.com. The most important and comprehensive product related to the LTPP IMS is the “DataPave Online” (http://www.ltpp-products.com). DataPave Online enables the users to explore and download LTPP data from the web. The DataPave Online is a good example as to how to make the LTPP IMS available to the users. It allows the users to view, explore, and extract LTPP data and some information. It also contains a GIS based viewing interface, and summary data, graphs, and query wizards to help users find data and information they are interested in.

Selected List of Key References of the LTPP IMS and IMS Operations

LTPP Standard Data Release (SDR) DVDs

The LTPP Program traditionally provides its data and key information through SDRs. The latest version, SDR25, consists of three DVDs: two data DVDs and one information DVD. The data DVDs contain the data tables from the LTPP PPDB, in MS Access format. To facilitate access and use of the LTPP SDR, a Reference Library DVD accompanies the SDR providing electronic versions of many LTPP publications and utility software useful to the LTPP data users.

The SDR25 is available through the LTPP Customer Support Center: ltppinfo@dot.gov. The following two documents on the SDR25 DVD provide a starting point for understanding the LTPP data:

• "LTPP_Data_User_Guide.pdf" - This document provides a release specific update to the previous pavement performance database user guide that strives to provide a comprehensive overview of the LTPP program, experiments, database structure, information on how to obtain LTPP data, and tutorials on the use of structured query language (SQL) to extract data.

• "LTPP_Traffic_Data_User_Guide.pdf" is included in the "Data_User_Documents" folder in Volume 5 of the SDR25 to facilitate access and use of the LTPP Traffic Analysis Software (LTAS) tables.

http://www.ltpp-products.com/ http://www.ltpp-products.com/ http://www.ltpp-products.com/ mailto:ltppinfo@dot.gov

LTPP IMS Operations Manual

Another key reference regarding the LTPP IMS is the LTPP IMS Operations Manual. It was developed for internal LTPP program usage and provides specific information about maintaining and upgrading the LTPP database servers, operating systems and software, performing database administration (DBA) functions, tracking change requests, producing software releases, and producing the annual Standard Data Release. It also describes the IMS entry application, including running quality control programs, data loaders and entering data into the PPDB with data entry forms. The latest version of the LTPP IMS Operations Manual is provided as an attachment to this solicitation (SECTION J).

Note: Due to historical reasons, the definitions of the LTPP IMS and its components may not be consistent with the definitions in this RFP. Most notably is the LTPP Traffic Analysis software and its input/output database. The LTPP program is modifying the PPDB as well as this manual so that the PPDB contains all the relevant tables including the traffic tables produced by the LTAS software. The LTPP Traffic Analysis software will eventually reside in the LTPP AIMS, as a data processing tool.

C.2 OBJECTIVE

The primary objective of this effort is to develop, enhance, maintain, and support an Effective Web Interface Program of the LTPP IMS [LTPP WIP]. This program will provide access to the LTPP IMS on-demand through a web interface and provide tools to maximize user understanding and utilization of the information.

C.3 DELINEATION OF CONTRACTOR TASKS

BASE PERIOD OF PERFORMANCE (CLIN 001)

TASK A – LTPP WEB INTERFACE PROGRAM DEVELOPMENT AND

ENHANCEMENTS

Task A.1 Framework of LTPP Web Interface Program

The main goal of Task A.1 is to develop a framework of the LTPP Web Interface Program Version 1.0. As a minimum, the following activities shall be conducted:

• Background review—LTPP IMS related literature and products (e.g. LTPP Product online) as listed in this solicitation. Software techniques and tools, in particular web development software, suitable for the LTPP Web Interface Program shall be evaluated and summarized.

• Survey of the representative LTPP data users—this can be done in person, by phone, and/or via questionnaires. At a minimum, this survey shall include users from academia, State DOTs, and other users in the pavement community.

NOTE: The Paperwork Reduction Act of 1995 (PRA): Any activities involving information collection (i.e., paper or web-based surveys, questionnaires, etc) from 10 or more non-Federal entities, including States, are subject to PRA requirements and may require the USDOT to coordinate an OMB Information Collection Clearance, a process that generally takes eight months. The Contractor shall coordinate with the COTR on this process.

• Interaction with the TRB LTPP committees, LTPP Technical Support Service Contractor, and other LTPP contractors with regard to the current LTPP IMS status, contents, and operation details. At least one face-to-face meeting and, multiple teleconference calls shall be conducted.

• Task A.1 Report. Draft Task A.1 report shall be submitted to the FHWA within six months from contract effective date. At a minimum, this report shall include:

o Approach and findings from: background review, survey of the LTPP users, and communication with the LTPP Technical Support Service Contractor team.

o Detailed LTPP Web Interface Version 1.0 Design o Task A.2 work plan to develop LTPP Web Interface Program 1.0.

The following is a preliminary list of the anticipated contents for the LTPP Web Interface Program 1.0 Design:

• Selection and justification of the software tools and techniques for development of the LTPP Web Interface Program. This shall include proposed website hosting mechanism for the LTPP Web Interface Program.

• Software develop approaches to connecting, synchronizing, accessing, and downloading LTPP PPDB and AIMS data and documents in an effective manner. The LTPP PPDB resides on an Oracle 10.g platform, which requires the LTPP IMS Web Interface Program to interact with the Oracle database. Whereas LTPP AIMS contains various raw data files, images, videos, documents, and software tools in different formats, cutting-edge data mining techniques are essential to obtain useful information and data quickly for the users.

• Engineering functionalities to enable users to view, explore and learn about the LTPP IMS, as well as to extract the analysis data sets specific to their needs. Mock Graphical User Interface (GUI) screens along with descriptions are expected to illustrate the intended capabilities. Example WIP functionalities anticipated:

o Interface for the users to view (e.g. through GIS type map) and explore the LTPP section information and database contents.

o Data views/visualization tools assisting users to create specialized data sets they need.

o Mechanism to produce LTPP Standard Data Releases (SDRs) through the web interface, in a robust and effective way.

o Data manipulation tools (widgets) to perform often used extractions, data views, or data manipulation o Web-based contextual search and data extraction methodologies for LTPP AIMS.

o Mechanism to track LTPP Web Interface Program usage, e.g. by user registration and log-in time tracking.

o Interface for customer survey on the LTPP Web Interface Program, and the LTPP customer support. For example, similar to what is provided on this webpage:

http://www.fhwa.dot.gov/research/tfhrc/programs/infrastructure/pavements/ltpp/surve y2.cfm.

o Effective interface for user feedback, bugs reporting, discussion forum, and support.

o Training tutorials or tools on LTPP Web Interface Program o Training tutorials or tools on LTPP PPDB and AIMS contents o Topical “ready to use” data set extractions (queries) o Computed (interpreted) engineering parameters

The Task A.2 Work Plan to develop LTPP Web Interface Program 1.0 shall be submitted for FHWA review and approval. It should include the following elements, as a minimum:

• Work plan to develop the LTPP Web Interface Program 1.0, in accordance with the design document

• Contractor’s QC/QA and testing plan of the LTPP Web Interface Program 1.0

• Proposed deliverables and reporting, including detailed milestones and schedule for execution

Note: The LTPP Web Interface Program 1.0 shall at least encompass the functionalities available at the LTPP DataPave Online (http://www.ltpp-products.com/). In addition, other LTPP software products such as Diva, ESALCalc, Performance Forecaster, LTPP E*, and others as identified by the COTR, shall be incorporated into the LTPP Web Interface Program 1.0.

Aside from the regular teleconference calls, two or more meetings shall be scheduled with the FHWA COTR: the initial kick-off meeting and Task A.1 reporting meeting within five months from contract start date. At least one of the meetings will be face-to-face in McLean Virginia or another location specified by the COTR.

Task A.2 Developing LTPP Web Interface Program Version 1.0

Note: Task A.2 shall not start until notice to proceed (NTP) is received from the COTR.

The offeror shall execute the approved Task A.2 Work Plan developed under Task A.1. The following outlines the key stages, milestones, and delivery packages FHWA anticipates.

Task A.2.1 Alpha versions of the LTPP Web Interface Program 1.0

Alpha versions of the LTPP Web Interface Program 1.0 shall be developed in accordance with the Design Document contained in the revised and approved Task A.1 report. Two Alpha versions shall be submitted to the FHWA for external testing.

http://www.fhwa.dot.gov/research/tfhrc/programs/infrastructure/pavements/ltpp/survey2.cfm http://www.fhwa.dot.gov/research/tfhrc/programs/infrastructure/pavements/ltpp/survey2.cfm http://www.ltpp-products.com/

Alpha Version #1 shall be fully functional and made available to the FHWA and its designated alpha testers within 6 months from Task A.2 NTP date. A comprehensive user’s guide, plus Alpha #1 testing guide and check list, shall accompany the Alpha version #1.

FHWA will provide comments from Alpha #1 testing within 1.5 months from receipt.

Alpha Version #2 shall be produced within 3 months from receiving the FHWA comments on the Alpha Version #1, and made available to the FHWA. Again, a revised comprehensive user’s guide, plus Alpha #2 testing guide and check list, shall accompany the Alpha version #2.

The Alpha Version #2 shall serve as the pre-Beta version, ready to be released to the public on the approved website as determined under Task A.1. FHWA will provide comments from Alpha #2 testing within 1.5 months from receipt.

Task A.2.2 Beta version of the LTPP Web Interface Program 1.0

Beta version of the LTPP Web Interface Program 1.0 shall be produced within 1 month from receiving the FHWA comments on the Alpha version #2.

Upon receiving FHWA approval, the Beta version shall be released to the public, live on the web, along with the User’s Guide and Beta Testing Guide and Checklist, as well as a means for the users to provide feedback.

The live Beta version shall be properly maintained and supported. The contractor shall submit to the FHWA User Comments and Feedback Summary Reports monthly to document the user feedbacks, plus resolutions, as appropriate.

Task A.2.3 LTPP Web Interface Program Version 1.0

Task A.2.3 LTPP Web Interface Program Version 1.0 shall be formally released to the public before the end of Task A.2. The actual date and venue of the public release shall be determined with consultation and approval from the FHWA. The contractor shall maintain and support the LTPP Web Interface Program and submit to the FHWA User Feedback Summary Reports monthly to document the user feedbacks and resolutions, as appropriate.

TASK B – Coordination and Outreach

The Contractor shall provide assistance to the FHWA in planning, coordination and, outreach related to the LTPP Web Interface Program. Activities shall include:

B.1 Coordination and Outreach

The Contractor’s Project Manager (PM) shall communicate regularly with the COTR. From time to time, the PM and Contractor’s other key personnel (e.g. PI, Co-PI) will be required to participate in teleconference calls, face-to-face meetings with the FHWA LTPP Team, LTPP

TRB committees, and/or speak at technical conferences, on as needed basis. The purpose of these meetings or presentations is to report the project status, explain work approach, or demonstrate the LTPP Web Interface Program being developed.

For proposal planning purposes, plan to attend two face-to-face meetings in addition to those planned under Tasks A.1 and A.2.

B.2 Technical Reporting

In addition to the deliverables identified under Task A.1 and Task A.2, the following are required:

a. Final Report to:

Summarize the work completed under this Task A.1 and A.2.

• Recommend future enhancements to the LTPP Web Interface Program V1.0

• Develop a work plan for developing LTPP Web Interface Program V2.0, including a preliminary design document of the V2.0 and an execution plan.

b. Presentation and training slides, discussion materials or minutes for meetings with other LTPP contractors, TRB ETG committees, or any workshops and training sessions, as directed by the COTR.

c. Technical memoranda or letter-reports on status or resolution of action items from meetings with FHWA and/or its designated contractors, as directed by the COTR.

d. Tech Brief or brochures for distribution to the public regarding the LTPP Web Interface Program.

Note: COTR will provide guidance on the preparation of Tech Briefs or brochures.

e. Preparation of display and/or promotional materials (for example, brochures, PowerPoint slides, video clips, and tech briefs) for use at conferences and workshops.

OPTION PERIODS (YEARS 3, 4, and 5)

If Option periods are exercised, the Contractor may be required to conduct the following work on a task order basis.

OPTION TASK AREAS (TASKS C, D, & E)

The general task areas from which the Government will issue task orders under this contract are:

TASK C – LTPP Web Interface Program Further Development and Enhancements

The Contractor shall further develop and enhance various versions of the LTPP Web Interface Program. This IMS web-interface program, when fully developed, shall provide the following functions to the LTPP data and information users:

• Provide timely web access to the LTPP PPDB. This shall allow the users to extract LTPP data in various common forms, such as the Microsoft ACCESS databases, Excel spreadsheets, ASCII flat files.

• Provide timely web access to the LTPP AIMS that includes raw data files, images, data collection and other resource documents, videos, research reports, software tools, and other products.

• Provide effective web interface that allows the user to query and download needed data and information they need.

• Provide effective web graphical interface that allows the users to explore and view the data and information contained in the LTPP IMS.

• Provide web-enabled LTPP software products.

• Implement effective web based user training, at various levels.

Activities may include:

1. Designing, developing, and testing of various versions of the LTPP Web Interface Program.

2. Preparation of clear and well-written documentation of LTPP Web Interface Program.

3. Planning and implementing future program enhancements based on the state of the technology, user needs, and directions of the FHWA.

TASK D – Operate, Maintain, and Support the LTPP Web Interface Program

The Contractor shall operate, maintain, and support the LTPP Web Interface Program. Activities may include:

1. Operating and maintaining the live web interface by keeping the LTPP Web Interface Program operational land free of bugs to the extent possible and in accordance with Government Information Technology Security requirements.

2. Reporting on the LTPP Web Interface Program access status, usage statistics, and other issues periodically.

3. Providing user support and feedback.

TASK E – Planning, Coordination, Outreach, and Reporting

The Contractor shall provide assistance to the FHWA in planning, coordination, and outreach related to the LTPP Web Interface Program. Activities may include:

1. Participating in planning future LTPP Web Interface Program versions.

2. Participating in meetings conducted for the purposes of coordination, planning, and outreach of the LTPP program as related to the LTTP Web Interface Program.

3. Preparation and delivery of presentations to highway agency and industry audiences at meetings, conferences and/or workshops pertinent to the LTPP Web Interface Program as directed by the COTR.

4. Preparation of display and/or promotional materials (for example, brochures, PowerPoint slides, video clips, and tech briefs) for use at conferences and workshops.

5. Develop technical reports and Tech Briefs as directed by the COTR.

(End of Section C)

SECTION D - PACKAGING AND MARKING

D.1 PACKAGING

Preservation, packing, and packaging of items for shipment shall be in accordance with commercial practice and adequate for acceptance by common carrier for safe transportation at the most economical rates.

D.2 SHIPMENT AND MARKING

Shipment of deliverable items shall be delivered F.O.B. Destination, under transmittal letter, as follows:

Ship to: Federal Highway Administration Turner-Fairbank Highway Research Center 6300 Georgetown Pike McLean, Virginia 22101 (Attention: to be filled in at award)

The Contractor shall mark each shipment with the company name, this contract number, the item identification, quantity of items, and notice of partial or final delivery.

(End of Section D)

SECTION E - INSPECTION AND ACCEPTANCE

E.1 INSPECTION AND ACCEPTANCE

All work hereunder shall be subject to review by the Government. Acceptance of the final report shall be made in writing by the Contracting Officer (CO).

52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)

This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer (CO) will make their full text available. Also, the full text of a clause may be accessed electronically at this address:

https://www.acquisition.gov/far/

(End of Clause)

52.246-4 INSPECTION OF SERVICES – FIXED PRICE (AUG 1996)

52.246-5 INSPECTION OF SERVICES- COST REIMBURSEMENT

(AUG 1996)

(End of Section E)

SECTION F - DELIVERIES OR PERFORMANCE

F.1 PERIOD OF PERFORMANCE

The period of performance for work conducted under the base period shall not exceed 24 months. The period of performance for issuance of task orders under this IDIQ contract shall be 12 months if the first option is exercised. If all options are exercised, the total period of performance including the base periods shall not exceed 60 months.

Any Task Order issued prior to the expiration date of this IDIQ, and not completed within that time, shall be completed by the contractor within the time specified under the task order. The contractor is required to abide by the terms and conditions of this IDIQ contract until the conclusion of the task order performance period.

The period of performance of the individual Task Orders will be specified within the Task Order document.

F.2 PLACE OF PERFORMANCE

Generally, work performed under this contract will either be accomplished at the Turner- Fairbank Highway Research Center in McLean, Virginia or at the Contractor’s site. However, during the performance of the contract, there may be Task Orders issued by the COTR that specify other designated locations.

F.3 PLACE OF DELIVERY

All deliverables shall be delivered F.O.B. Destination, under transmittal letter, to the COTR at https://www.acquisition.gov/far/ the following address:

Turner-Fairbank Highway Research Center 6300 Georgetown Pike McLean, VA 22101 Attention: to be filled in at award

Email address: to be filled in at award

Quarterly reports (See Section G) and other items as specified shall be delivered by email to the Contract Administrator at the following address:

Federal Highway Administration Office of Acquisition Management HAAM 20- Room E65-103 1200 New Jersey Avenue, S.E.

Washington, DC 20590 Attention: to be filled in at award

Email address: to be filled in at award

52.247-34 F.O.B. DESTINATION (NOV 1991)

52.242-15 STOP-WORK ORDER (AUG 1989) -- ALTERNATE I (APR 1984)

F.4 DELIVERABLES & MILESTONES

All deliverables shall utilize a Microsoft Office Suite format unless otherwise approved by the COTR. Technical Reports shall be submitted in accordance with technical report specifications provided herein.

BASE PERIOD Task A and B Key Deliverables and Milestones

Key Deliverables Due Dates Notes Task A Task A.1 Task A.1 Draft Report Within six months from contract effective date.

Reserve one month for FHWA review and comments.

Revised Task A.1 Report Within one month from receiving FHWA comments.

Reserve one month for FHWA review and approval.

Task A.2 LTPP WIP 1.0 Alpha #1, and Within six months from Reserve 1.5 months for its package Task A.2 NTP date FHWA testing and comments.

LTPP WIP 1.0 Alpha #2, and its package

Within three months from receiving FHWA comments on Alpha #1

Reserve 1.5 months for FHWA testing and comments.

LTPP WIP 1.0 Beta Live, and its package

Within one month from receiving FHWA comments on Alpha #2

Reserve one month for FHWA and public testing and comments.

LTPP WIP 1.0 official release, Live, and its package

After Beta release, to be determined w/ FHWA

LTPP WIP User Support Summary Report

After Beta release, monthly

Task B Presentation slides, training and/or discussion materials for various meetings

TBD, during the course of Task B

As directed by the COTR

Technical memoranda or letter-reports

TBD, during the course of Task B

As needed and directive by the COTR

Draft Task B Final Report After the Beta version is released, and within 12 months from A.2 NTP date

Reserve 1.5 months for FHWA testing and comments.

Draft Tech Brief and a brochure of the LTPP WIP 1.0 Revised Task B Final Report;

Revised Tech Brief and Brochure

Within one month from receiving FHWA comments

Reserve 1.5 months for FHWA testing and comments.

Quarterly Progress Report Quarterly, as specified in Section G

Note: *A memorandum addressing FHWA comments shall accompany all revised documents or software.

Unless specified otherwise, technical reports under this contract shall be prepared in accordance with the latest version of the Turner-Fairbank Highway Research Communications Reference Guide (FHWA-RD-03-074), available at http://www.tfhrc.gov/qkref/qrgmain.htm.

All tasks set forth in the Statement of Work shall be performed in accordance with the work schedule and deliverable schedule as delineated in each task order. Performance shall begin on the effective date of each task order.

Specific requirements for technical documentation and deliverables will be established for each individual task order.

(End of Section F) http://www.tfhrc.gov/qkref/qrgmain.htm

SECTION G - CONTRACT ADMINISTRATION DATA

G.1 FUNDS AVAILABILE

a. Currently, funding in the amount of ______ is available for payment under this contract.

b. The balance of funding under this contract (_______) will be obligated by formal modification to the contract.

c. FAR Part 52.232-22, entitled, "LIMITATION OF FUNDS" applies to this contract. Any notification required on the part of the contract shall be made in writing to the Contracting Officer. In the event that the contract is not funded beyond the estimated cost set forth in the schedule, the Contractor shall deliver to the Contracting Officer the data collected and the material produced or in process or acquired in connection with the performance of the project provided herein together with a summary report in five copies of its progress and accomplishments to date.

PAYMENTS

G.2.1 PAYMENT/COST REIMBURSEMENT

The Contractor may request monthly interim payments for costs incurred during the performance of the contract. A statement of costs incurred by the Contractor in the performance of tasks under this contract and claimed to constitute allowable costs shall support each interim payment request. Each interim payment request shall be submitted in accordance with the attached, “FHWA Billing Instructions for Cost Reimbursement Contracts” to be considered proper for payment. Prior approval of the Contracting Officer (CO) is required if the Contractor wishes to use a different payment request format.

In accordance with clause 52.232-25, “Prompt Payment”, interim payments will be made by the 30th day following receipt of proper request for payment by the designated billing office, unless audit or other review is considered necessary to ensure compliance with the terms and conditions of the contract. All interim payments hereunder will be made upon further determination by the CO that the Contractor is making adequate progress toward successful contract completion.

Final invoice payment shall be made upon the CO’s determination that all contract requirements have been completed. The payment due date for final invoice shall be established in accordance with the clause 52.232-25.

G.2.2 PAYMENT OF FIXED PRICE TASK ORDERS (CLIN 0102-0302)

For firm-fixed-price task orders, unless otherwise specified in the individual task order, the Contractor may request payment for the firm-fixed-price specified in the task order upon the

Government’s acceptance of work under that task order. Partial payment may be made for partial delivery. Satisfactory completion and acceptance of the task order will be made by the

COTR.

(a) Upon the Government’s acceptance of deliverables in accordance with Section E, the

Contractor may submit a request for payment in accordance with fixed-unit prices specified in Section B. The Government will make payment to the Contractor in accordance with the Prompt Payment Clause.

(b) To constitute a proper invoice, the invoice must include the following information:

(1) Name of the business concern, invoice number, and invoice date.

(2) Contract and Task Order numbers.

(3) CLIN Item number(s), description, quantity, unit price and extended totals of services actually delivered or rendered.

(4) Payment terms.

(5) Taxpayer Identification Number & DUNS Number

G.3 TRAVEL AND PER DIEM RATES

Travel and Per Diem authorized under this contract shall be reimbursed in accordance with the Federal Travel Regulations currently in effect.

Travel requirements under this contract shall be met using the most economical form of transportation available. If economy class transportation is not available, the request for payment voucher must be submitted with justification for use of higher class travel indicating dates, times, and flight numbers. All travel shall be scheduled sufficiently in advance to take advantage of offered discount rates, unless authorized by the COTR.

G.4 SUBCONTRACTS - ADVANCE NOTIFICATION AND CONSENT

Under this contract, the requirements of FAR 44.2, CONSENT TO SUBCONTRACTS, have been fulfilled for the following subcontracts:

[as negotiated]

Any future change or revision to the Statement of Work or other applicable aspects of this contract shall include the subcontract(s) only to the extent that performance of the subcontract(s) is directly affected by the change or revision.

G.5 CONTRACTING OFFICER'S TECHNICAL REPRESENTATIVE (COTR)

The Contracting Officer has designated ___________ as COTR to assist in monitoring the work under this contract. The COTR is responsible for the technical administration of the contract and serves as technical liaison with the Contractor. The COTR is not authorized to change the scope of work or specifications as stated in the contract, to make any commitments or otherwise obligate the Government or authorize any changes which affect the contract price, delivery schedule, period of performance, or other terms or conditions.

The CO is the only individual who can legally commit or obligate the Government for the expenditure of public funds. The technical administration of this contract shall not be construed to authorize the revision of the terms and conditions of this contract. The CO shall authorize any such revision in writing.

G.6 TASK ORDER PROCEDURE

The following ordering procedure shall apply to all Task Orders (TOs) issued under this contract.

TOs shall be issued in accordance with FAR 52.216-18. 52.216-19, and 52.216-22 (See SECTION I). In addition:

a. The Task Order Proposal Request (TOPR) will be issued electronically. The exact nature and extent of the Contractor’s work under the contract will be based on written Task Order Proposal Request (TOPR) delivered by the CO.

b. In response, the contractor shall submit to the Contracting Officer a Task Order Proposal

(TOP) with the time specified for submission.

c. Within 14 calendar days after receipt of an e-mailed TOPR from the Government, or within an earlier or later deadline specified in the TOPR, the Contractor shall submit to the COTR and to the CO a Task Order Proposal.

d. Each task order proposal must clearly state the contract number and TOPR number on the cover page of the submission.

e. The proposal shall outline the Contractor’s overall approach for completing the task order and shall, at a minimum, include:

(1) Signed cover letter stating that this is the proposal responding to the TOPR;

(2) Discussion of technical approach for performing the work, including detailed list of work activities, methods, timelines, milestone, and proposed deliverables for each task, in response to the TOPR;

(3) Proposed staff for performing the work items, their labor categories, estimated level of effort (hours) and roles. Resumes shall be included for staff members new to the contract.

(4) Estimated date of commencement of work, and any changes proposed to the schedule of performance;

(5) Budget summary for the entire period of performance, including:

• Labor categories, staff names, direct labor hours, hourly rates, for each task

• Indirect Rates and their applications

• Subcontractors/Consultants and your cost analysis in accordance with

FAR 15.404-3.

• Other Direct Costs with a breakout by category

• Travel and materials cost estimates

• Total estimated cost for completion of the task order

e. The Contracting Officer will modify task orders in the same manner as they are issued.

f. If the Contractor either at the time of receipt of a task order or at any time during work assignment performance has reason to believe that the cost or number of labor hours will exceed the estimates set forth in the task order, the Contractor shall immediately notify the COTR and Contracting Officer in writing and suggest a revised estimate for completion of the work required. After discussion with the COTR, the Contracting Officer may issue a modification revising the terms and conditions of the task order.

g. The Contractor is not authorized to expend funds beyond those obligated to the task order.

Additionally, the effort under each task order shall not exceed the total ceiling price specified. The Limitation of Funds or Limitation of Cost clauses apply to each cost reimbursable task order individually. Therefore, the Contractor is required to notify the CO by each individual task order in accordance with clauses 52.232-22, Limitation of Funds, and 52.232-20 Limitation of Cost, as applicable.

G.7 INDIRECT COSTS

The Contractor shall be reimbursed for allowable indirect costs hereunder at the predetermined or provisional rates as granted in the contractor’s rate agreement in effect. The predetermined or provisional rates effective at award are:

Category Rate

This INDIRECT COST provision does not operate to waive the LIMITATION OF FUNDS Clause. The Contractor’s audited final indirect costs are allowable only insofar as they do not cause the Contractor to exceed the total estimated costs for performance of the contract listed on page 2 (SECTION B) and under the PAYMENT (SECTION G).

G.8 INVOICES

Submit all invoices to one of the following invoice addresses, as appropriate:

All invoices and required supporting documents shall be sent via e-mail to the following e-mail address: 9-AMC-AMZ-FHWA-Invoices@faa.gov.

(i) Include the invoice as an attached PDF document

(ii) Include in the e-mail subject line the following:

(iii) Invoice Number

(iv) Contract/Agreement Number

(v) Name of your Company/Organization

(vi) Attention: _to be filled in at award

If the invoice and supporting documents exceed 8 MB as an e-mail attachment, the Contractor must select one of the other submission options presented below:

Invoices submitted via an overnight service must use the following physical address:

MMAC

FHWA/AMZ-150

6500 S. MacArthur Blvd Oklahoma City, OK 73169 Attention: to be filled in at award

Express Delivery Point of Contact: to be filled in at award

Invoices may be submitted via regular U.S. Postal Service to the following address:

Federal Highway Administration Markview Processing

P.O. Box 268865 Oklahoma City OK 73126-8865

Attention: (to be filled in at award)

G.9 QUARTERLY PROGRESS REPORTS

The Contractor shall furnish an electronic copy of a quarterly letter-type progress report to the Contracting Officer’s Technical Representative and one copy to the Contract Administrator, on or before the 15th of the month following the calendar month being reported. Each report shall contain concise statements covering the activities relevant to the study, including:

1. A clear and complete account of the work performed on each task

2. An outline of the work to be accomplished during the next report period.

3. A bar chart showing the work completed by task versus the Schedule of Work of the contract.

4. A description of any problems encountered or anticipated that will affect the completion mailto:9-AMC-AMZ-FHWA-Invoices@faa.gov of the contract within the time and fiscal constraints as set forth in the contract, together with recommended solutions to such problems; or a statement that no problems were encountered.

5. A tabulation of the planned, actual and cumulative person-hours expended by the personnel identified in the performance of work during the base period and for individual task orders.

6. A chart showing current and cumulative expenditures by tasks versus planned expenditures.

(End of Section G)

SECTION H - SPECIAL CONTRACT REQUIREMENTS

H.1 POST-AWARD EVALUATION OF CONTRACTOR PERFORMANCE

Contractor Performance Evaluations

a. Interim and final evaluations of contractor performance will be prepared on this contract in accordance with FAR 42.1502 and TAM 1242.1502. The final performance evaluations will be prepared at the time of completion of work.

b. The Contractor can elect to review the evaluation and submit additional information or a rebuttal statement. The contractor will be permitted 30 calendar days to respond.

Contractor response is voluntary. If the contractor does not respond within 30 days, the Government will presume that the contractor has no comment. Any disagreement between the parties regarding an evaluation will be referred to an individual at a level above the Contracting Officer, whose decision is final.

c. Copies of the evaluations, contractor responses, and review comments, if any, will be retained as part of the contract file, and may be used to support future award decisions.

Federal Highway Administration utilizes the Contractor Performance Assessment Reporting System (CPARS) to record and maintain past performance information.

CPARS hosts a suite of web-enabled applications that are used to document contractor performance information that is required by Federal Regulations.

The CPARS module assesses performance on contracts for Systems, Services, Information Technology, and Operations Support. The Architect-Engineer Contract Administration Support System (ACASS) module assesses performance on Architect- Engineer contracts. The Construction Contractor Appraisal Support System (CCASS) module assesses performance on Construction contracts. CPARS reference material can be accessed at http://www.cpars.csd.disa.mil/cparsfiles/cpars/refmatl.htm.

The registration process requires the contractor to identify an individual that will serve as a primary contact. This individual will be authorized access to the evaluation for review and comment. In addition, the contractor is encouraged to identify a secondary contact in the event the primary contact is unavailable to process the evaluation within the required 30-day time period. After the FHWA Contract Specialist registers the contract in CPARS, the contractor will receive a system generated e-mail notifying him/her that the contract is registered. A system generated e-mail will also provide the contractor with User ID if the person does not already have a CPARS User ID.

Onc…