RFP No. 693JJ320R000007.pdf

693JJ320R000007

SOLICITATION, OFFER AND AWARD

4. TYPE OF SOLICITATION2. CONTRACT NUMBER 3. SOLICITATION NUMBER

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

ORDER UNDER DPAS (15 CFR 700)

6. REQUISITION/PURCHASE NUMBER

NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".

NEGOTIATED (RFP)

SEALED BID (IFB)

5. DATE ISSUED

1. THIS CONTRACT IS A RATED RATING PAGE OF PAGES

C. E-MAIL ADDRESS

EXT.NUMBERAREA CODE

B. TELEPHONE (NO COLLECT CALLS)A. NAME

10. FOR

INFORMATION

CALL:

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.

(Date)(Hour) local timeuntildepository located in 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

SOLICITATION

9. Sealed offers in original and

PART IV - REPRESENTATIONS AND INSTRUCTIONS

OTHER STATEMENTS OF OFFERORS

EVALUATION FACTORS FOR AWARD

INSTRS., CONDS., AND NOTICES TO OFFERORS

REPRESENTATIONS, CERTIFICATIONS AND

LIST OF ATTACHMENTS

CONTRACT CLAUSES

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACH.

I

J

K

L

M SPECIAL CONTRACT REQUIREMENTS

CONTRACT ADMINISTRATION DATA

DELIVERIES OR PERFORMANCE

INSPECTION AND ACCEPTANCE

PACKAGING AND MARKING

DESCRIPTION/SPECS./WORK STATEMENT

SUPPLIES OR SERVICES AND PRICES/COSTS

SOLICITATION/CONTRACT FORM

PART II - CONTRACT CLAUSESPART I - THE SCHEDULE

H

G

F

E

D

C

B

A

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

11. TABLE OF CONTENTS

18. OFFER DATE17. SIGNATURE

SUCH ADDRESS IN SCHEDULE.

IS DIFFERENT FROM ABOVE - ENTER

15C. CHECK IF REMITTANCE ADDRESS

EXT.NUMBERAREA CODE

15B. TELEPHONE NUMBER

(Type or print)AND

ADDRESS

OF

OFFEROR

CODE FACILITY

16. NAME AND TITLE OF PERSON AUTHORIZED TO SIGN OFFER15A. NAME

DATEAMENDMENT NO.DATEAMENDMENT NO.

and related documents numbered and dated):

amendments to the SOLICITATION for offerors

(The offeror acknowledges receipt of

14. ACKNOWLEDGEMENT OF AMENDMENTS

CALENDAR DAYS (%)30 CALENDAR DAYS (%)20 CALENDAR DAYS (%)10 CALENDAR DAYS (%)

(See Section I, Clause No. 52.232.8)

13. DISCOUNT FOR PROMPT PAYMENT

designated point(s), within the time specified in the schedule.

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

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

NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

OFFER (Must be fully completed by offeror)

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

28. AWARD DATE

(Signature of Contracting Officer)

27. UNITED STATES OF AMERICA

25. PAYMENT WILL BE MADE BY

26. NAME OF CONTRACTING OFFICER (Type or print)

CODE 24. ADMINISTERED BY (If other than Item 7)

ITEM

(4 copies unless otherwise specified)

23. SUBMIT INVOICES TO ADDRESS SHOWN IN

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

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

21. ACCOUNTING AND APPROPRIATION20. AMOUNT19. ACCEPTED AS TO ITEMS NUMBERED

AWARD (To be completed by government)

CODE

X

1300 ET

NAHEED NASRIN

naheed.nasrin@dot.gov

X

X

X

X

X

X

X

X

X

X

X

X

X

PAGE(S)

Aimee S. Drewry

AUTHORIZED FOR LOCAL REPRODUCTION

Previous edition is unusable

STANDARD FORM 33 (Rev. 9-97)

Prescribed by GSA - FAR (48 CFR) 53.214(c)

3-11 15-23 24-35

36-45

47-51

52-59 59-62

11/22/2019 HRDI30200001PR

FEDERAL HIGHWAY ADMINISTRATION

OFFICE OF THE CHIEF FINANCIAL OFFICER

OFFICE OF ACQUISITION & GRANTS MANAGEMENT

1200 NEW JERSEY AVENUE, SE

WASHINGTON DC 20590

NAHEED.NASRIN@DOT.GOV

zero

See Section L 12/23/2019

SECTION B - Supplies or Services/Prices

B.1 INDEFINITE-DELIVERY INDEFINITE-QUANTITY (ID/IQ) MINIMUM AND

MAXIMUM CONTRACT AMOUNTS

CLIN Supplies/Services Not to Exceed

Amount

0001 Technical Support Services for

Highway Infrastructure Engineering and Research Data Services

60-Month Ordering Period

$15,000,000

Total $15,000,000

This is a single award ID/IQ type contract with a 60-month ordering period.

During the term of the contract, the Government shall place orders totaling a minimum of

$50,000. The maximum amount of all task orders issued against the awarded contract as a result of this acquisition shall not exceed a total estimated cost of $15,000,000.

The task orders placed under the contract will be Firm-Fixed-Price (FFP), Time-and-Materials/Labor

Hour (T&M/LH), or a hybrid of both types based on a determination by the Contracting Officer (CO) at the task order level.

B.2 SCHEDULE OF RATES

Labor skill sets and rate ceilings governing this contract shall conform to the descriptions found in

Exhibit No. J.1 and shall be listed in the Microsoft Excel format found at Exhibit No. J.1 and apply for each of the described categories for each of the contract years. The unit of issue (rates) is the fully burdened fixed price hourly rate. Please see Federal Acquisition Regulation (FAR) 52.216-29(c)(2).

The maximum amount of the contract listed in Section B.1 includes travel and materials. Travel and materials shall be reimbursed at cost. Inclusion of indirect burden amounts or fee on material costs, including travel expenses, is not allowable.

(End of Section B)

SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

C.1 INTRODUCTION

Engineering services, data validation and management, and data visualization and analytics are needed to ensure data quality and public access of the infrastructure related data. The success of this effort requires a team that possesses expertise in not only data management and web application development, but also pavement, bridge, and other highway infrastructure engineering. FHWA seeks support to provide capability statements in the areas listed for consideration in developing future FHWA requirements.

The research area and data include the following:

• Long-Term Pavement Performance (LTPP) program and related data

• Long-Term Bridge Performance (LTBP) program and related data

• Other highway infrastructure research and project data

Overview of LTPP Program and Related Data

Started in 1987 as part of the Strategic Highway Research Program (SHRP) and managed by the Federal

Highway Administration (FHWA) since 1992, the Long-Term Pavement Performance (LTPP) program studies the performance of in-service pavements. The primary goal of the LTPP program is to understand how and why pavements perform as they do. The mission of the Long-Term Pavement

Performance (LTPP) Program is 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 the 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.

As highway agencies transition to a performance-based approach to managing highway investments, the

LTPP program is more important than ever.

Since 1989, the LTPP database has grown exponentially and has included a collection of electronic information from over 2,500 pavement test sections throughout the United States and Canada. The LTPP program has two sets of experiments, the General Pavement Studies (GPS) and the Specific Pavement

Studies (SPS). The GPS test sections were established on existing pavements. An experimental matrix was used to guide the selection of GPS test sections that would cover, to the greatest extent possible, the range of factors required to explain pavement performance. Test sections for SPS experiments were built to specific designs and thicknesses, as defined in the experimental plans.

Huge amount of pavement performance related data have been collected using standard data collection procedures and protocols on a variety of pavement types. This information is stored in an Information

Management System (IMS) and has been available to researchers since the early nineties with new data and data elements added every year. It is the world’s largest 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.

Since 2014 LTPP data and relevant knowledge has been disseminated and visualized through the LTPP

InfoPave web portal (https://infopave.fhwa.dot.gov/ ). LTPP InfoPave is the gateway to the LTPP data and knowledge, and have been used by thousands of pavement engineers and researchers worldwide to advance the science of pavement engineering. For more information about LTPP program, please visit https://www.fhwa.dot.gov/research/tfhrc/programs/infrastructure/pavements/ltpp/ .

Overview of LTBP Program and Related Data

The Long-Term Bridge Performance (LTBP) program was congressionally mandated under the Safe, Accountable, Flexible, and Efficient Transportation Equity Act: A Legacy for Users (SAFETEA-LU).

In 2008 FHWA initiated the LTBP Program, which is anticipated to be a multi-decade research effort.

The overall objective of the LTBP Program is to periodically monitor representative samples of bridges nationwide to collect, document, maintain, and manage research-quality performance data over an extended time horizon. This is accomplished by taking advantage of advanced nondestructive evaluation

(NDE) and structural health monitoring (SHM) technologies in addition to traditional visual bridge inspection approaches. The LTBP Program is designed in part to collect critical performance data that are not available elsewhere and merge it with data gathered from other sources. The LTBP program has a comparable goal as the LTPP program in that the data is gathered to improve understanding of bridge performance to enable data-driven decisions. Similarly, the LTBP Information Management System

(IMS) stores and manages data collected by the LTBP program, as well as data collected from other sources. An example is National Bridge Inventory (NBI) data.

Launched in January 2019, the LTBP InfoBridge web portal, https://infobridge.fhwa.dot.gov/, is a centralized, national repository of bridge performance data and related analysis tools. It provides storage, retrieval, dissemination, analysis, and visualization of data collected through LTBP program efforts, as well as data sets collected through other research studies, and provides users with the ability to holistically assess bridge performance on an individual project or network basis. For more information, please visit the LTBP web-site at http://www.fhwa.dot.gov/research/tfhrc/programs/infrastructure/structures/ltbp/.

LTPP and LTBP Data Management and Web Portals

The FHWA Long-Term Infrastructure Performance (LTIP) team manages both LTPP and LTBP programs and is combining similar areas to make both programs run more efficiently and effectively.

Data resulting from both programs are now co-located in Amazon AWS cloud. Many data elements, such as climatic factors are common to both programs. The process of collecting field data, Quality

Control/Quality Assurance, and storing data into a structured database is essentially the same for both programs. There are also many similarities and synergies to be gained by implementing similar platforms for both IMS structures and how the data and knowledge should be made available to the public through InfoPave and InfoBridge.

https://infopave.fhwa.dot.gov/ https://www.fhwa.dot.gov/research/tfhrc/programs/infrastructure/pavements/ltpp/ https://infobridge.fhwa.dot.gov/ http://www.fhwa.dot.gov/research/tfhrc/programs/infrastructure/structures/ltbp/

InfoPave and InfoBridge Configuration and Development Platform Introduction

Both InfoPave and InfoBridge are hosted on Amazon Web Services (AWS) cloud technologies, consisting of development and production environments. These environments include a number of servers such as web server, Oracle RDS server, MS SQL database server, and application server.

Example software technology used includes Oracle 12c, Microsoft SQL Server, Microsoft ASP.NET

MVC (C#), Microsoft Windows IIS web server. In addition, several other cloud technologies such as

Amazon S3 and Amazon SES, etc. were used to support the required application features.

In terms of client-side technologies, InfoPave uses several client-side technologies that include basic jQuery library as well as MVVM frameworks such as Knockout. Additionally, it also uses Bootstrap for the user interface development. The client-side of the LTBP InfoBridge application has been developed using the latest UI/UX technologies such as HTML, CSS, HTML 5, and Bootstrap 4. The client-side development was done using the latest MVVM frameworks such as AngularJS and Knockout that allow two-way binding of the data elements being exchanged between the web server and the client browser. Additionally, advanced WebGL techniques were also used on the client side to enhance and optimize the application performance for rendering huge amounts of data points on Google Maps.

C.2 OBJECTIVE

The objective of this contract is to provide highly specialized structural and highway pavement engineering services to:

• Data Quality Control: Perform quality control and quality assurance on infrastructure research data collected in the field and produced in engineering laboratories. Correct and process the data into research-quality information to be used in nationwide research studies that improve the design, construction, rehabilitation, and management of highway infrastructure assets.

• Data Management: Upgrade and enhance existing information management systems consisting of highly technical databases, data warehouses, metadata, etc.

• Data Visualization: Develop visualization techniques that enable engineers and research scientists to readily understand and make use of the vast amount of infrastructure research data that is generated by FHWA and other transportation research entities.

• Data Augmentation: Periodically, update validated research data sets on LTPP InfoPave, LTBP

InfoBridge, and other web portals as appropriate.

C.3 SCOPE OF WORK

Under this contract, the Contractor shall perform research, field data quality management, and development of innovative visualization techniques as necessary to support the activities of the FHWA related to highway infrastructure engineering and research data services. Work under the contract shall include the conduct of research; the development and demonstration of visualization techniques and methods; and the verification of field collected and laboratory produced data against national research quality standards. All work under this contract shall be performed through the issuance of specific task orders.

C.4 DELINEATION OF CONTRACTOR TASKS

To meet the objectives of this contract and as directed by the Government through the issuance of specific task orders, the Contractor shall perform the following tasks/Activities:

Tasks/Activities

• Verify that field collected and laboratory produced data meet national research quality standards.

Typical data sets include:

o In-situ performance monitoring data collected by non-destructive testing equipment (e.g., the robotic bridge deck assessment tool: RABIT™, pavement roughness measuring vehicles, highway weigh-in-motion systems, falling-weight deflectometers, automated longitudinal and transverse profile measurements), o Manually collected infrastructure performance field data (e.g. pavement surface distresses, bridge condition rating), o Laboratory produced test results, and o Data submitted by the state DOTs or made available through other relevant research programs.

• Modify non-conforming data to meet quality standards so that it is readily usable in nationwide research studies.

• Develop and implement enhancements to existing information management systems consisting of highly technical databases, data warehouses, metadata, etc.

• Periodically, update validated research data sets on LTPP InfoPave, LTBP InfoBridge, Pavement

Research Database System, and other web portals as appropriate.

• Develop visualization techniques that enable engineers and research scientists to readily understand and make use of the vast amount of infrastructure research data that is generated by

FHWA and other transportation research entities.

• Enhance, maintain, and provide technical support to LTPP InfoPave, LTBP InfoBridge, and other infrastructure research data related web portals as appropriate, including packaging of engineering research data in useful formats to civil and structural engineers, engineering professors, and researchers.

C.5 STAFFING

The Contractor’s project team must possess the necessary combination of qualifications and experience to provide superior-level research and work products to the satisfaction of FHWA.

Project Manager

Duties

The Project Manager (PM) shall be responsible for administration and management of the Contract, including coordinating time and travel for the contract personnel. Responsible for submission of all task order proposals, progress and required reports, and all other contract and task order deliverables. The PM shall assume the initiative and be the point of technical and administrative contact between the Government and the Contractor and shall be responsible for the successful completion of all work required under this contract.

Qualifications

The PM shall have good experience in most task areas and knowledge of all the task areas described in this

RFP, and have a minimum of a B.S. degree in Engineering (or equivalent) and 15 years of related experience, 5 of which should be in a management role on large research contracts. Excellent organizational and communication skills are required.

Senior Engineer

The Senior Engineer shall be the primary engineering lead for at least one of the main Task Areas as described in this RFP, namely validating and analyzing the LTPP Data and InfoPave, LTBP Data and InfoBridge, and

Other Highway Infrastructure Research Data.

The Senior Engineer shall have a Master’s Degree in Civil Engineering or equivalent with relevant experience in his/her assigned area(s). Senior Engineer shall have a minimum of 10 years of relevant experience with a

Master's in Engineering, or 5 years of relevant experience and a Ph.D.

Project Engineer

The Project Engineer shall work on at least one of the main Task Areas as described in this RFP, namely

LTPP Data and InfoPave, LTBP Data and InfoBridge, and Other Highway Infrastructure Research Data..

The Project Engineer shall have a Bachelor’s Degree in Civil Engineering or equivalent technical experience.

The Project Engineer shall have a minimum of 8 years of relevant experience with a Bachelor’s Degree or a minimum of 5 years of relevant experience and a Master's degree in Engineering or higher, or a Ph.D in Civil

Engineering.

Staff Engineer

Shall work on at least one of the main Task Areas as described in this RFP, namely LTPP Data and InfoPave, LTBP Data and InfoBridge, and Other Highway Infrastructure Research Data.

Qualifications

The Staff Engineer shall have a Bachelor’s Degree in Civil Engineering or equivalent technical experience.

Staff Engineer shall have a minimum of a Bachelor’s Degree in Engineering and 1 year of experience or an entry level with a Master's degree in Engineering.

Data Scientist—Infrastructure Engineering

Shall provide both engineering database support to QC/QA, process, and develop infrastructure research related data sets, such as the LTPP, LTBP, asphalt and concrete testing laboratory data. Infrastructure

Engineering Data Scientists shall have a multi-faceted background in a combination of engineering and computational/database fields. Their engineering background is in civil engineering, transportation engineering, or related field. Their computational background is in statistics, relational database, computational science, or other related field

The Data Scientist shall have a minimum of 10 years of relevant experience with a Bachelor's Degree in

Engineering, or equivalent.

Subject Matter Expert (SME)

The SMEs shall provide subject matter expertise to guide or support the technical work under this contract, in either bridge engineering, pavement performance and research

The SMEs shall be nationally recognized experts in the task areas as specified in this SOW.

Senior Database Engineer

The Senior Database Engineer shall lead technical and database administrative support of the LTPP, LTBP, and other relevant infrastructure research databases. May work either on-site the FHWA TFHRC site, or offsite on the LTPP database operations and support as specified in the task order.

The Senior Database Engineer shall have at least 8 years of experience with database designing, warehousing and modeling, related programming, database administration, and data validation and processing concepts.

Shall have in-depth knowledge of the Task Areas described in this RFP, be proficient with commonly used database programming and administration tools such as Oracle RDBMS, Microsoft SQL server. Senior

Database Engineers shall have a minimum of a Bachelor’s Degree in Computer Science, Mathematics or

Engineering or equivalent technical experience and 8 years of relevant experience.

Database Engineer

The Database Engineer shall provide technical and database administrative support of the LTPP IMS. The

Database Engineer shall work either on-site the FHWA TFHRC site, or offsite

The Database Engineer shall be familiar with the database programming, database administration, and data processing concepts using Oracle and Microsoft SQL Server databases and supporting software tools. Must have experience in implementing highly performing scalable databases with large data storage needs.

Database Engineer shall have a minimum of a Bachelor’s Degree in Computer Science, Mathematics or

Engineering or equivalent technical experience and 3 years of related experience.

Senior Software Developer

The Senior Software Developer shall be responsible for leading the design and development of computer software, including web based systems such as InfoPave and InfoBridge.

The Senior Software Developer shall have demonstrated experience in designing and developing scalable software application architectures. Should be able to lead and manage team of software developers, quality engineers and testers, and network engineers to deliver an end-to-end software solution. Must have experience in both web application development and desktop application development using .NET technologies for implementing large scale data driven applications. Possess expertise in latest web technologies including response web design (RWD) and MVVM frameworks. Proficient in relational database programming and knowledge of both Microsoft SQL Server and Oracle® relational database systems and supporting software.

Should be able to perform basic DevOps tasks such as server setup and configuration, software installation, and application deployment using cloud hosting platforms such as Amazon Web Services (AWS) and

Microsoft Azure. Shall have a minimum of a Bachelor’s Degree in Computer Science, or equivalent, and 8 years of experience or higher.

Software Developer

The Software Developer shall assist with designing, development, testing and implementation of computer software including web based systems.

The Software Developer shall have demonstrated experience in both web application development and desktop application development using .NET technologies for implementing large scale data driven applications. Possess expertise in latest web technologies including response web design (RWD) and MVVM frameworks. Proficient in relational database programming and knowledge of both Microsoft SQL Server and

Oracle® relational database systems and supporting software. Should be able to perform basic DevOps tasks such as server setup and configuration, software installation, and application deployment using cloud hosting platforms such as Amazon Web Services (AWS) and Microsoft Azure. The Software Developer shall have a minimum of a Bachelor’s Degree in Computer Science, or equivalent and at least 5 years of experience.

Junior Software Developer

The Junior Software Developer shall assist with the development, testing, and implementation of computer software including web based systems.

The Junior Software Developer shall be familiar with basic programing concepts using .NET technologies and should be able to perform required programming tasks under supervision of their seniors. Must possess hands-on experience on latest web technologies and MVVM frameworks. Shall have hands-on experience in both developing web based interface programs and/or managing or developing software applications with the

Oracle® databases. Shall have a minimum of a Bachelor’s Degree in Computer Science, or equivalent.

Minimum of 1 year of experience or higher.

Media Specialist/Editor

The Media Specialist/Editor shall assist in the outreach and communications activities, including graphic design, layout, and production of brochures, flyers, pamphlets, briefings, posters, displays, video and website layouts. Shall create presentations, including graphics, charts, photos, and clip-art using different graphic software. The Media Specialist/Editor may also apply writing and editing skills to the development of specifications, training, operating, or maintenance manuals.

The Media Specialist/Editor shall have experience with Section 508 compliance. Shall have a Bachelor's

Degree in English, Media, or equivalent degree with at least 2 years of experience.

Project Support Staff

The Project Support Staff shall provide support to technical and management-level personnel. This includes, but is not limited to, documentation planning and support, project administration, event planning and administration, Section 508 compliance, data input, etc.

The Project Support Staff shall have 3 years of administrative/technical support experience.

C.6 PROGRESS REPORTS

The Contractor shall submit quarterly progress reports by the 10th of the first month of the quarter following the reporting period. The report shall provide at a minimum:

(a) Clear and complete account of the work performed under each task order during the reporting period.

(b) The cumulative amount expended under the ID/IQ by task order and summary.

(c) An outline of the work to be accomplished during the next reporting period.

(d) A description of any problem encountered or anticipated that will affect the completion of any individual task order within the time and fiscal constraints as set forth in the task orders, together with recommended solutions to such problems; or, a statement that no problems were encountered.

(e) Deliverables submitted, date due, and date submitted.

(f) Project Schedule – (task order specific) The Contractor shall submit, to the Government, an initial project schedule in Microsoft Project format within sixty (60) days after the effective date of a task order and updates showing the percent complete of major deliverables every thirty (30) days thereafter. The schedule shall include at a minimum, the major deliverables and milestones and adhere to the Microsoft

Project template structure provided by the COR. Any changes to due dates after the initial project schedule baseline must be approved by the Government. The Contractor shall support the identification of schedule dependencies related to the project and in accordance with the Government defined process.

The Contractor shall furnish an electronic copy of the quarterly progress report to the CS and COR.

C.7 KICK OFF MEETING

Within 45 days following contract award, the Contractor shall facilitate a kickoff meeting to be held via conference call. The meeting shall include its representatives, ensuring all parties have a common understanding of the contract tasks and requirements. The Contractor shall have its key personnel participate, at a minimum, in this meeting.

(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 best commercial practices and adequate for acceptance by common carrier for safe transportation at the most economical rates.

The Contractor shall clearly mark each shipment with the company name, the contract number, Task Order number (if applicable), and as appropriate the item identification, quantity of items, and notice of partial or final delivery.

D.2 MARKINGS

All deliverables submitted to the Contract Specialist (CS) and the designated Contracting

Officer’s Representative/Task Order Contracting Officer’s Representative (COR/TOCOR) shall be accompanied by a packing list or other suitable shipping document that shall clearly indicate the following:

(a) Contract number;

(b) Task Order number;

(c) Name and address of the consignor;

(d) Name and address of the consignee;

(e) Government bill of lading number covering the shipment (if any); and

(f) Description of the item/material shipped, including Deliverable Item Number (If applicable), Report Requirement, or Project Title under which the item is being delivered.

Specific marking objectives may be addressed in individual task orders.

The offeror shall take all necessary precautions to ensure that all sensitive data developed under this contract are delivered to the Government in a secure manner.

(End of Section D)

SECTION E - Inspection and Acceptance

E.1 52.246-2 INSPECTION OF SUPPLIES – FIXED PRICE (AUG 1996)

E.2 52.246-4 INSPECTION OF SERVICES - FIXED-PRICE (AUG 1996)

E.3 52.246-6 INSPECTION – TIME-AND-MATERIAL AND LABOR HOUR (MAY 2001)

E.4 ACCEPTANCE

All work hereunder shall be subject to review by the Government. The COR or TOCOR as specified in each appointment letter at the contract and task order level, is responsible for inspection and acceptance of all incoming shipments, documents, and services. The COR/

TOCOR will provide written acceptance of deliverables.

E.5 GOVERNMENT ACCEPTANCE PERIOD

Unless stated elsewhere in each Task Order, the COR will have 14 calendar days to review draft deliverables and make comments. The Contractor shall have 10 calendar days to make corrections and return the corrected deliverable to the Government. Upon receipt of the final deliverables, the COR will have 14 calendar days for final review prior to acceptance or providing documented reasons for non-acceptance.

The COR shall have the right to reject or require correction of any deficiencies found in the deliverables that are contrary to the information contained in the Contractor’s accepted proposal. In the event of rejection of any deliverable, the Contractor shall be notified in writing by the COR of the specific reasons why the deliverable is being rejected. Unless otherwise directed by USDOT, the Contractor shall have 14 calendar days to correct the rejected deliverable and return it per delivery instructions.

(End of Section E)

SECTION F - Deliveries or Performance

F.1 52.242-15 STOP-WORK ORDER. (AUG 1989)

F.2 52.242-17 GOVERNMENT DELAY OF WORK. (APR 1984)

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

F.4 PERIOD OF PERFORMANCE (ID/IQ)

The period of performance of this Indefinite Delivery/Indefinite Quantity Contract (for the purpose of placing orders) is 60 months from the effective date of award.

F.5 PLACE OF DELIVERY

All deliverables, except the annual and quarterly progress report shall be delivered to the COR at the following address:

To be completed at time of award

The quarterly progress reports shall be delivered to the COR and Contract Specialist (CS) at the following address:

Fill-in Name and Title at Award

Fill-in E-mail Address at Award

F.6 PLACE OF PERFORMANCE

The work under this contract shall be performed primarily at the Contractor’s facilities and at the

Turner-Fairbank Highway Research Center in McLean, Virginia. Place of performance will be specified at the task order level.

F.7 DELIVERABLE/DELIVERY SUMMARY

Deliverable

Delivery Date Format Recipient

Quarterly Progress

Reports

Quarterly, by the 10th of the month following the quarter being reported

Email/ MS

Word /

Adobe PDF

COR, CS

For task orders issued under this contract, specific deliverables and due dates will be specified in the task order documents.

(End of Section F)

SECTION G - Contract Administration Data

G.1 PAYMENT- (ID/IQ)

FFP:

For each FFP Task Order, the Government shall pay the Contractor for the prices delineated in each task order. Payment shall be made upon review and written acceptance of the FFP deliverable(s) by the

Government.

T&M/LH:

For each T&M/LH Task Order, the Contractor may request payment no more than monthly, for work performed during the preceding reporting period. The Contractor shall provide sufficient detail, including fully burdened labor rates and hours worked, to support the invoice.

The Contractor shall not accrue costs in excess of the amount funded under a T&M/LH Task Order. Any work performed in excess of the amount funded is at the Contractor’s own risk.

NOTE: For each T&M/LH Task Order, allowable materials costs, including travel expenses shall be reimbursed at cost. Inclusion of indirect burden amounts or fee on material costs, including travel expenses, is not allowable.

G.2 TRAVEL AND PER DIEM

Travel (other than local) may be expected to occur throughout the duration of the contract to attend meetings, conferences, and training. The Contractor shall submit a written request for travel, if required

(excluding local travel) and must be approved by the COR.

The Contractor shall invoice in accordance with FAR 31.205-46, Travel Costs, and Federal Travel

Regulations, and must submit documentation of all travel costs.

Travel requirements under this contract shall be met using the most economical form of transportation available. All travel shall be scheduled sufficiently in advance to take advantage of offered discount rates, unless authorized by the CO.

The following web site provides information on current Per Diem rates:

http://www.gsa.gov/portal/category/100120

G.3 SUBCONTRACTS – ADVANCE NOTIFICATION AND CONSENT

Under this contract, the requirement of FAR 44.2, Consent to Subcontracts, has been fulfilled for the following subcontracts:

(Filled in at Award)

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.

http://www.gsa.gov/portal/category/100120

G.4 INVOICES

Submit all invoices (per individual task order) to one of the following invoice addresses:

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.

(a) Include the invoice as an attached PDF document

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

(1) Invoice No.

(2) Contract Number/Task Order Number

(3) Name of your Company/Organization

(4) Attention: Contract Specialist

Example: Invoice No. 35 – 693JJ320Dxxxxxx – Contractor Name – Attention: Contract Specialist

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: Contract Specialist

Express Delivery Point of Contact: Lead Accounting Technician, 405-954-8252

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: Lead Accounting Technician, 405-954-8252

An invoice submitted to an address other than those identified will be returned to the vendor as non-conforming.

G.5 FINAL INVOICES

NOTE: The final invoice is not subject to interest payment under the Prompt Payment Act. The CO will process the final invoice as a routine part of the closeout process. When submitted, the Contractor shall mark the invoice as ‘FINAL’ in accordance with Section G.4 Invoice of this contract.

G.6 TECHNICAL DIRECTION

Performance of the work under this contract is subject to the Technical Direction of the COR. The term

“Technical Direction” is defined to include, without limitation, the following:

mailto:9-AMC-AMZ-FHWA-Invoices@faa.gov

(a) Direction to the Contractor which redirects the efforts, shifts work emphasis between work areas, requires pursuit of certain lines of inquiry, fills in details or otherwise serves to accomplish the statement of work;

(b) Provision of information to the Contractor that assists in the interpretation of drawings, specifications or technical portions of the work description; and,

(c) Review and approval/rejection of technical reports, drawings, specifications and technical information to be delivered by the Contractor.

All Technical Direction must be within the general scope of work stated in the contract. The COR does not have the authority to and may not issue any Technical Direction that:

(i) constitutes an assignment of additional work outside the general scope of the base contract;

(ii) constitutes a change as defines in the base contract clause entitled “Changes”;

(iii) in any manner causes an increase or decrease in prices set forth in Section B; or

(iv) changes any of the expressed terms, conditions or specifications of the contract.

All Technical Direction must be issued in writing, or shall be confirmed in writing by the COR within 3 working days after issuance. The Contractor shall proceed promptly with the performance of duly issued

Technical Directions. However, if in the opinion of the Contractor, the direction issued by the COR is within one of the prescribed categories in (i) through (iv) above, the Contractor shall not proceed, but shall notify the CO in writing, within 3 working days after receipt of any such direction. The CO will determine if the Technical Direction is proper, or if a contract modification would be required to properly implement the direction. Failure of the parties to agree upon the nature of the direction or upon the contract action to be taken with respect thereto shall be subject to the clause included in Section I entitled

“Disputes”.

G.7 CONTRACTING OFFICER’S REPRESENTATIVE AND TASK ORDER COR

(a) The CO 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 delivered under this contract.

(b) The CO shall designate a COR by written notice to the Contractor. The COR’s responsibilities shall include technical monitoring of the Contractor’s performance on the overall contract award and inspecting and accepting deliveries under the contract. The COR shall be appointed in writing, at which time ALL of the responsibilities of the COR shall be detailed, and a copy of the appointment memorandum shall be furnished to the Contractor. Any changes to the COR delegation shall be made in writing, either by changes to the existing memorandum, or by issuance of a new appointment memorandum. Copies of any changes shall be provided to the Contractor.

As needed, the CO may appoint a TOCOR. The TOCOR’s responsibilities shall include technical monitoring of the Contractor’s performance as well as inspecting and accepting deliveries under specified task order(s). Any changes to the TOCOR delegation will be made in writing, either by changes to the existing memorandum or by issuance of a new appointment memorandum. Notification of any changes will be provided to the Contractor and COR.

(a) The COR and, if designated, the TOCOR are not authorized to perform, formally or informally, any of the following actions:

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

• Waive or agree to any modification of the delivery schedule;

• Make any final decision on any contract matter subject to the Disputes Clause;

• Terminate, for any reason, the Contractor’s right to proceed, or issue any order causing the

Contractor to stop work; or

• Obligate in any way, the payment of money by the Government.

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

Contractor need not proceed with direction that it considers having been issued without proper authority. The Contractor shall notify the CO in writing, with as much detail as possible, when the COR or TOCOR, if applicable, has taken an action or has issued direction (written or oral) that the Contractor considers exceeding the COR or TOCOR’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 CO’s response issued under paragraph (e) of this clause.

(c) The CO 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.

(d) The Contractor shall provide copies of all correspondence to the CO and the COR and TOCOR, if applicable.

(e) 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 CO or the

COR acting within his or her appointment, shall be at the Contractor’s risk.

G.8 CONTRACTOR SUPERVISION

The Contractor shall provide total supervision of its staff. Government personnel are not authorized or permitted to supervise any Contractor personnel. The Contractor's Project Manager (PM) for this contract is [Fill-in at Award], who shall communicate with the COR to determine the Government's work requirements as set forth in the Statement of Work and shall assure that these requirements are fulfilled.

In the event the designated PM is incapacitated due to illness or injury or otherwise is to be removed by the Contractor during the contract performance, replacement of the incumbent PM shall be subject to the approval of the CO.

G.9 AGENCY TASK ORDER OMBUDSMAN

The CO’s selection decision on each task order request shall be final and is not subject to protest, except for a protest that the task order increases the scope, period, or maximum value of the contract.

Accordingly, in accordance with FAR 16.505(b)(5), an ombudsman has been appointed to hear and facilitate the resolution of the Contractor’s concerns resulting from task order award. The existence of the ombudsman does not diminish the authority of the CO. Further, the ombudsman does not participate in the evaluation of the proposals or the adjudication of formal contract disputes. Therefore, before consulting with the ombudsman, interested parties must first address their concerns, issues, disagreements and/or recommendations to the CO for resolution.

If the CO cannot make resolution, interested parties may contact the FHWA ombudsman at the following address:

United States Department of Transportation

Federal Highway Administration

1200 New Jersey Avenue, SE

Washington, DC 20590 Location:

E66-327

Attention: Ombudsman

G.10 TASK ORDER SELECTION CRITERIA

FHWA anticipates that the following elements will be the standard criteria for awarding individual task orders: Technical/Management Approach, Past Performance, and Price in relation to task order requirements. Each task order will indicate any changes or additions to standard criteria. The order of importance for the factors will be identified in each individual Task Order Proposal Request (TOPR).

Evaluation of past performance will be based on the past performance data in each awardee’s proposal as supplemented by the Government and Contractor during the period of performance. As work proceeds under this contract, it is probable that the past performance information evaluated at original contract award will be given less weight than current performance reports received on task orders performed under this contract.

G.11 TASK ORDER PROCEDURES

All funds expended under this contract shall be incurred and accounted for under individual task orders.

All task orders are subject to the terms and conditions of this contract.

The following ordering procedures apply to all task orders issued under this contract. All task orders under this contract will be competed unless a special exception to competition applies.

Any supplies/services to be furnished under this contract will be ordered by issuance of written task orders. Task orders shall be issued in accordance with FAR 52.216-18, 52.216-19, and 52.216-22 (See

Section I). In addition:

(a) Only an authorized FHWA CO can issue a task order for this contract.

(b) All task orders are subject to the terms and conditions of the contract. In the event of conflict between a task order and the contract, the contract will take precedence.

(c) All costs associated with preparation, presentation, and/or discussion of the Contractor’s task order proposal shall not be billable as direct contract expenses.

(d) The CO or CS will issue TOPRs electronically to the ID/IQ Contractor awarded a contract in response to solicitation 693JJ320R000007, in accordance with FAR 16.505 Ordering. Each TOPR will indicate the objective or results required by the Government. This objective will be within the scope, period, and maximum value of the IDIQ contract. Each TOPR will indicate the task order type, the due date for proposal submission, the estimated level of effort (if applicable), any

Government estimates for equipment and/or travel, any special requirements, and any additional selection criteria not specifically identified in the task order Selection Criteria clause below.

(e) Upon receipt of a TOPR, the Contractor shall prepare and submit a written task order proposal within the timeframe specified for submission. The Contractor shall submit one electronic copy of the task order proposal to the CO. The task order proposal shall include, as a minimum, the following information:

1. A discussion of the Task Order objective demonstrating the Contractor’s understanding of the required outcome.

2. A concise work plan for achieving the task order objectives that clearly demonstrates the

Contractors’ understanding of and planned approach to the problem.

3. A performance schedule that provides the following information:

i. Planned accomplishments/milestones

ii. Anticipated problems or challenges

iii. Planned solutions to anticipated problems or challenges

4. Qualifications of the proposed staff, including any proposed subject matter expert consultants.

5. A detailed price proposal, including:

i. Proposed level of effort and labor categories

ii. The corresponding labor rates

iii. Other Direct Costs as applicable (materials, travel, shipping, copying, etc.)

1) Task Order Conflicts of Interest: The Offerors shall provide a brief statement in each task order proposal that describes in a concise manner all past, present or planned organizational, contractual or other interest(s), which may affect the Offeror’s ability to perform the proposed task order in an impartial and objective manner. The CO will review the statement and may require additional relevant information from the Offerors. In accordance with FAR Subpart 9.5, all such information, and any other relevant information known to DOT, will be used to determine whether an award to the Offeror(s) may create an actual or potential conflict of interest. If any such conflict of interest is found to exist, the CO may (a) disqualify the Offeror(s), or (b) determine that it is otherwise in the best interest of the United States to contract with the Offeror(s) and include appropriate provisions to mitigate or avoid such conflict in the contract awarded.

2) Proposals shall be delivered, on or before the due date, to the CS listed in the TOPR.

3) Upon selection/acceptance of a task order proposal, the CO shall execute a task order. This task order will contain, as a minimum, the following information:

i. Name and signature of CO

ii. Task Order Number and Contract Number

iii. Effective Date of Task Order

iv. Task Order Subject and Description of Work (including deliverables/schedule)

v. Period of Performance

vi. Total Amount of Task Order

vii. Accounting Data

viii. Reporting Requirements

ix. Work Plan

x. Key Personnel

4) No work will be performed and no payment will be made except as authorized by a properly executed Task Order.

NOTE: The type of task orders issued will vary based on the nature of the work requested and the

CO’s determination.

In lieu of submitting a Task Order Proposal, if the Contractor is not able or does not wish to compete for a specific task order, the Contractor must so state in writing to the CO.

G.12 LIABILITY

The Government cannot indemnify the Contractor or its subcontractors from liability as a result of the performance of work under this contract. Therefore, the Contractor is required to obtain adequate property, vehicle and liability insurance during the entire period of performance, as appropriate, in accordance with the clause at FAR 52.228-7, which is incorporated into this contract in Section I.

Evidence of such insurance must be submitted to the CO as a condition of award.

G.13 ON-SITE DUTY HOURS

Work under this contract shall be performed at Contractor facilities. When onsite work is required, duty hours will be specified in individual TOs.

G.14 FEDERAL…