Solicitation FBO 4-9-12.pdf

DTRT57-12-R-20001

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

1 89

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

DTRT-RVT-41-117904/09/2012

X

RVP-31

USDOT/RITA/Volpe Center Contracts & Program Support Service 55 Broadway RVP-31 Cambridge MA 02142-1001

SEE BLOCK #7 1500 ET 05/11/2012

Darren F Shaffer 617 darren.shaffer@.dot.gov

494-2332

X

X

X

X

X

X

X

X

X

X

X

X

X

PAGE(S)

Robert P. Robinson

AUTHORIZED FOR LOCAL REPRODUCTION

Previous edition is unusable

STANDARD FORM 33 (Rev. 9-97)

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

SECTION B - SUPPLIES OR SERVICES AND PRICES/COSTS

B.1 CONTRACT TYPE (FEB 2011)

A. This is an indefinite delivery/indefinite quantity (IDIQ) task order contract.

B. Task orders may be issued on a firm fixed price (FFP), cost-plus-fixed-fee (CPFF) completion, or cost-plus-fixed-fee (CPFF) term basis at the Contracting Officer's discretion consistent with the guidelines provided in Part 16 of the Federal Acquisition Regulations.

Performance-based task orders will be used to the maximum extent practicable.

C. Individual CPFF task orders will be issued on a completion-type basis pursuant to FAR

16.306 (d)(1). If a completion-type task order is not appropriate, a term-type task order may be issued pursuant to FAR 16.306(d)(2).

D. The Contract Line Item Number (CLIN) structure provided in Subsection B.4 below establishes a CLIN for the three contract type/pricing methods available for use under this contract. Because using a particular contract type/pricing methodology requires terms and conditions specific to that use, this contract includes terms and conditions covering FFP, CPFF completion, and CPFF term tasks. In general, these terms and conditions are clear on their face with regard to applicability.

B.2 CONTRACT LIMITATIONS (JAN 2011)

A. Maximum Contract Value: The value of all task orders placed under this contract shall not exceed $(TO BE COMPLETED AT TIME OF AWARD). As a task order is issued, its value is subtracted from the total capacity available under this contract.

B. Minimum Guarantee: The guaranteed minimum for this contract is $2,500.

B.3 CONTRACT SCOPE (DEC 2007)

The Contractor, acting as an independent Contractor and not as an agent of the Government, shall furnish all personnel, supplies, facilities, materials, support, and management necessary to provide the services required under this contract. The scope of this effort is defined in the Statement of Work (SOW) (see Section C). General work requirements are outlined in the task areas (See Section C.5). Specific requirements will be in individual task orders.

B.4 CONTRACT LINE ITEMS (FEB 2011)

ITEM NO. SERVICES

0001 The Contractor shall furnish all personnel, supplies, facilities, materials, support, and management necessary to provide the services in accordance with the Statement of Work (SOW) (see Section C), and other terms and conditions of this contract, through task orders issued under one or more of the contract types set forth below:

0001AA FIRM-FIXED-PRICE TYPE TASK ORDERS

0001AB COST-PLUS-FIXED-FEE (COMPLETION TYPE) TASK ORDERS

0001AC COST-PLUS-FIXED-FEE (TERM TYPE) TASK ORDERS

SECTION C - DESCRIPTION/SPECIFICATIONS/STATEMENT OF WORK

Additions and/or Enhancements to Service Oriented Architecture for Geospatial and Other Modeling Tools

C.1 INTRODUCTION

The John A. Volpe National Transportation Systems Center (Volpe Center) is a Federal fee-for-service organization within the Research and Innovative Technology Administration (RITA) of the Department of Transportation (DOT). The Volpe Center’s mission is to improve the nation’s transportation systems. In partnership with sponsoring agencies, the Volpe Center provides technical research and analysis services to the DOT, other Federal agencies, state agencies, and other organizations in connection with the transportation-related components of their missions.

C.2 BACKGROUND

The Volpe Center maintains and develops a number of tools that support its sponsors’ ability to measure and model the impacts of various transportation-related sources, including environmental impacts from aviation, highways, rail, and maritime. Given recent advancements in Geographical Information System (GIS) and Graphical User Interface (GUI) technology, there is a critical need to add or enhance service-oriented architecture (SOA) for geospatial modeling in various sponsors’ tools.

For example, the Federal Aviation Administration’s (FAA) Office of Aviation Environment and Energy (AEE) requires expertise on issues related to environmental concerns regarding noise, local and global air quality, and economic impact. This support may also consider technological and operations measures to reduce impact. To support FAA/AEE, the Volpe Center has developed and continues to improve expertise in the measurement and modeling of airport noise, local and global emissions, and aviation economics. FAA/AEE also has the additional responsibility of continuing to improve and develop new methodologies to assist in the analysis of aviation-related environmental impacts, including consideration of the National Environmental Policy Act (NEPA). To assist in this effort, the Volpe Center is supporting development of a suite of analytical computer models, e.g., the FAA’s Aviation Environmental Design Tool (AEDT), which utilizes GIS capabilities.

Also for example, the Air Tour Management Plan (ATMP) program addresses issues with air tour aircraft noise impacts in the U.S. National Parks. ATMP is a joint effort by the FAA Western Pacific Regional Office (AWP) and National Park Service (NPS) Natural Sounds and Night Skies Division. The FAA’s AEDT, designed, developed and maintained by the Volpe Center, provides a comprehensive computer model for National Park air tour aircraft noise prediction and analysis. The Volpe Center is implementing a unified National Environmental Policy Act (NEPA)-driven environmental analysis application with a graphical front end for FAA and NPS use on ATMP projects, including the integration of a number of service modules into a Microsoft Windows ASP.NET and ArcGIS Server Application. Various upgrades will allow users to implement graphical input, display, and selection of user configuration and source data for scenario construction.

Also for example, the Federal Highway Administration’s (FHWA) Office of Natural and Human Environment (HEPN) requires expertise on issues related to concerns regarding noise and local air quality in the vicinity of highways and communities near highway transportation. The Volpe Center has supported the FHWA’s expertise in the analysis of highway-related environmental impacts through the development and use of a suite of analytical computer models, e.g., the FHWA Traffic Noise Model (TNM) and the Environmental Protection Agency (EPA) Motor Vehicle Emission Simulator (MOVES).

It is expected that this work will expand to include other DOT administrations (e.g., Federal Rail Administration (FRA), Federal Transit Administration (FTA), etc.) as well as non-DOT entities, e.g., NASA, EPA, state DOTs, etc.

The Volpe Center also provides similar measurement assistance to support various transportation initiatives, including the Continuous Lower Energy Emissions and Noise (CLEEN), Aviation Climate Change Research Initiative (ACCRI), and Commercial Alternative Aviation Fuel Initiative (CAAFI) programs. The measurement work may also require related support under this effort.

C.3 SYSTEM OBJECTIVES

Services under this contract will add or enhance SOA primarily for geospatial modeling and at a minimum support the following system objectives:

AEDT

• Service Oriented Architecture (SOA) implementation consistent with FAA’s System Wide Information Management (SWIM) requirements

• SOA extension of data retrieval from FAA Aeronautical Information Exchange Model (AIXM) service providers

• GUI implementation of Web-based services for regulatory, compliance, and inventory level modeling of aviation environmental consequences

• Implementation of GIS to help package data products as GIS map services

• Related support to modeling initiatives supporting FAA’s Next Generation Air

Transportation System (NextGen), e.g., 4-D flight trajectory design, evaluation, manipulation and visualization

ATMP

• Tailored implementation of role-specific user interfaces (client web pages) in the ATMP Web Workflow

• Multi-study administrative management of air-tour park studies.

• Implementation of customized GIS layer access from the web-based clients

• Implementation of a data access service for geospatial data services in the environmental sector, e.g. Ambient Noise database information

Broader Services

• SOA definition of modeling services suitable for aviation, highway, rail, maritime, and other transportation-related projects, including multi-model projects

• Web service access applications for field measurement projects (e.g., dose response, ambient data collection, survey and mapping)

C.4 GEOGRAPHICAL INFORMATION SYSTEM (GIS) DATA OBJECTIVES

As part of the Volpe Center’s maintenance and development of sponsors’ transportation-related environmental computer models, including the FAA AEDT and FHWA TNM, a common GIS import/export processor will be developed to assist in both calculating potential impacts using the same population and geographical data, and also in presenting the results of noise and emissions analyses in a common format. Producing common output will also be facilitated by the development of a common contouring module to generate reports in flexible, user-defined formats to facilitate these types of geographically-based assessments, rather than making users rely on a small number of standard report formats. The use of common GIS input/output will facilitate integrated analyses and support the system objectives described above in paragraph C.3.

The Volpe Center wants to take steps to maintain a customized ArcGIS framework that utilizes the GIS objects library offered by the Environmental Systems Research Institute Inc. (ESRI), including core GIS layers anticipated for use by all model users. Also of interest is the use of Manifold.NET’s GIS in C#. User scenarios would minimally include airport-related analysis, highway traffic analyses, as well as analysis within and around National Parks. Due to the extensive quantity of such information, data and technical support from a contractor will be needed to maintain the GIS database, convert data from different sources (e.g., global positioning system (GPS) and other formats), manipulate geospatial datasets, and write custom tools to automate GIS processes as described in this Statement of Work (SOW), as well as considerable integration support for its use in the transportation models in question, particularly AEDT and

TNM.

C.5 TASK AREAS OF WORK

The task areas are representative of the overarching requirement. The overarching requirement is the development of a database of core GIS layers for tool users

A listing the anticipated firm requirements and of primary and secondary tasks are provided below. Additional tasks within the scope of the task areas below will be specified at the task order level.

The main task to be undertaken, including:

• Fleet

• Facilities (e.g., airports, highways, ports, rail lines, etc.)

• Movements (e.g., radar, operational counts, speeds, etc.)

• Boundaries,

• Base data (e.g., elevation, land cover, buildings etc.),

• Imagery (e.g., orthophotos, landsat, etc.)

• Census data,

• Meteorological data, and

• Analysis specific (acoustic zones, ambient data, etc.).

The following tasks are part of the overall requirements. A listings of primary and secondary tasks are provided below. Additional tasks within the scope of the task areas below will be specified at the task order level.

Task Area (TA) 1: Implement a unified environmental analysis application with a graphical front end for use on projects, e.g., AEDT, ATMP, TNM, etc., dependent on geospatial modeling information:

Work under this task area requires advanced knowledge in software design, software documentation, architecture solutions, and software release management. Work tasks will evaluate, document, update, and integrate into Volpe software various emissions and dispersion models which cover the range of transportation sources. This includes comparisons with real world data or case studies; also, integration into other modeling environments. The primary work in this task area involves extensive software coding, data analysis, and quality assurance as well as extensive use of FAA's AEDT and ATMP and FHWA’s TNM.

Task Area 1A will include the following:

1. Integrate the following series of modules into a Microsoft Windows ASP.NET and ArcGIS Server application:

i. FlightTrackGenerator – Generates ASCII text files of flight track coordinates and ground elevation, including the ability to view receptor to source lines of sight taking into consideration elevation profiles, as well as the ability to smooth elevation profiles based on use-input parameters

ii. AmbientGenerator – Generates ambient maps and AEDT ambient files

iii. InmProcessor and InmReverseLegendProcessor – Generates AEDT contour maps

iv. InmCumulativeProcessor – Generates cumulative equivalent sound level

(Leq) contour maps

The deliverables for Task Area 1A includes software modules, applications, support code, and other related information. The deliverables will be submitted to the Volpe Center Contracting Officer’s Technical Representative (COTR), and Volpe Center program managers.

Task Area 1B includes additional tasks that may involve:

1. Coordinate specific SOA implementation needs with the Volpe Center.

2. Integrate new or existing GIS architecture into a Microsoft Windows ASP.NET and ArcGIS Server Application.

3. Implement graphical input, display, and selection of user configuration and source data for scenario construction. Note that input data for transportation-related Facilities, Fleets, and Movements information shall conform to model-specific definitions (e.g., AEDT, TNM, etc.) for any existing parameters and be coordinated with model developers on inclusion of new parameters. Any computer application that is generated as a deliverable shall be compatible with and graphically render all data sources listed in the Data Objectives section of this SOW. The application shall also address the appropriate requirements in the System Objectives, Section C.3, of this SOW.

4. Participate in regular meetings at the Volpe Center for the demonstration of analysis application deliverables.

5. Participate in one meeting per year in Washington, DC, for the demonstration of analysis application deliverables.

The deliverables for Task Area 1B will be specified at the task order level.

Task Area 2: Integrate output results into application resulting from Task 1:

Work may involve extensive software architecture analysis and design, data analysis and quality assurance as well as extensive use of FAA's AEDT and ATMP and FHWA’s TNM.

Task Area 2A will include the following:

1. Provide a data application for Airport, Fleet, and Movements information, conforming to AEDT definitions for any existing parameters and coordinate with AEDT development on the inclusion of new parameters. The application shall be compatible with and graphically render all data sources listed in the Data Objectives, Section C.4, of this

SOW.

The deliverable(s) for this Task Area 2A includes software modules, applications, support code, and other related information to be specified at the task order level.

Task Area 2B includes additional tasks that may involve:

1. Coordinate specific SOA integration needs with the Volpe Center.

2. Implement ESRI ArcEngine, Manifold or other GIS controls for processing model output results to be rendered as GIS layers.

3. Integrate controls to the application resulting from Task 1.

4. Coordinate with ESRI (or other GIS firm) to form prioritized computational performance improvements.

5. Participate in regular meetings at the Volpe Center for demonstration of integration results (see Task 1).

The deliverables for Task Area 2B will be specified at the task order level.

Task Area 3: Review and extend computer model test procedures under International Standards Organization (ISO) 9000-3 and other guidelines

Work will involve extensive standard review, software compliance review, data analysis, and quality assurance as well as extensive use of FAA's AEDT and ATMP and FHWA’s TNM.

Task Area 3A will include the following:

1. Recommend the optimum technology to leverage as technology for the AEDT2b GUI based on finding from previous tasks and prior related work on the air tour management program. Technology choices are required in the following areas:

a. Primary technology choice, likely Silverlight

b. Selection of supporting 3rd party packages as necessary/useful

c. Data access paradigm for reaching AEDT data in SQL/GIS

d. The deliverable for this task shall be a written summary of technology options and conclusions and explanation of data access model delivered to the CDE, COTR, and Volpe Center program managers.

2. Based on a review of the current GUI and legacy tools, the contractor shall complete an interface design including revised work flow interface should take into account requirements from both AEDT2a and AEDT2b.

The deliverable(s) for this task primary work in this Task Area 3A shall be a written interface design document including user work flow diagrams and mapping between AEDT requirements and GUI functionality.

Task Area 3B includes additional tasks that may involve:

1. Coordinate with the Volpe Center the review or new design of computer model test plans and outcomes.

2. Conduct a review of existing computer model test plans and test outcomes.

3. Provide recommendations for improving coverage, completeness, and computational as well as process efficiencies.

4. Design test battery construction (or refinement) process to facilitate implementation of recommendations.

5. Conduct unit and system testing in accordance with prescribed procedures.

6. Present modified computer model test procedures and testing code/algorithms at the Volpe Center.

The deliverables for Task Area 3B will be specified at the task order level.

Task Area 4: GUI Module Support

Work may involve extensive software tool research, software development, data analysis, and quality assurance as well as extensive use of FAA's AEDT and ATMP and FHWA’s TNM.

Task Area 4A will include the following:

1. Conduct a review of the existing GUI to determine the usability of existing functionality and underlying code. Survey team experience to gain knowledge from team through use of legacy tool use cases, where necessary leverage Volpe Center expertise in legacy tools for follow on questions.

a. The deliverables for this task shall include a Technical Report of useable elements of the AEDT2a GUI along with key use cases from legacy tools.

2. Develop an AEDT2b GUI using test driven development, encompassing AEDT2a GUI review and legacy tool use cases while leveraging the established work flow refactoring and technology sub-architecture components. The results viewer shall include all AEDT2a functionality including all output an data manipulation.

a. The deliverable for this task shall be the AEDT2b GUI software covering AEDT2a functionality.

3. Develop additional add-on functionality to the AEDT2b GUI to include advanced feedback and error logging capability. Develop advanced feedback functionality to capture and package user discrepancy and bug reports for submittal to the AEDT support team. Establish error log filtering and viewing functions for the user.

a. The deliverable for this task shall be the AEDT2b GUI software including feedback and error viewing capability.

4. Extend the functionality of the AEDT2b GUI to include input data viewing. Establish the capability to view input data and progress during import.

a. The deliverable for this task shall be the AEDT2b GUI software including study view and import progress capability.

5. Establish capability to view and directly manipulate the AEDT fleet database form with the GUI.

a. The deliverable for this task shall be the AEDT2b GUI software including capability for user access to the fleet database.

The deliverables for Task Area 4A are specified above.

Task Area 4B includes additional tasks that may involve:

1. For existing tools (e.g., AEDT, TNM, etc.), conduct a review of the GUI modules.

2. Provide recommendations for improving the functionality, completeness, and computational as well as process efficiencies of the GUI modules.

3. For new tools, participate in Volpe-led design discussions.

4. Working with a host of stakeholders, design, develop, and implement updated and/or new versions of the GUI modules using GIS and the latest Microsoft Developer environment tools.

5. Present the modified/new GUI at the Volpe Center.

The deliverables for Task Area 4B will be specified at the task order level.

Task 5: Other Support

Work shall involve extensive software development and review, data analysis, and quality assurance as well as presentations on new technology and development techniques. Additional potential tasking may also include:

Task Area 5A may include the following:

1. Establish connections to AEDT Team Foundation Server (TFS) environment, coordinate with application branching, and establish test driven development.

2. Establish connections to the AEDT development systems and lay out the development framework and approach. The following support will be provided:

a. Coordinate with the Volpe Center to ensure all contractor development accounts are correctly configured and operational

b. Suggest branch and build process for AEDT2b

3. Establish an AEDT2b GUI test-driven and solution/project-based development

a. The deliverables for this task shall include guidance on achieving functional contractor AEDT CDE accounts, account and framework verification, feedback to the AEDT development team on the branch and build process and the framework for a test-driven software solution on the AEDT CDE. This guidance shall be posted on the AEDT CDE and emailed to the COTR and Volpe Center program managers.

4. Provide a Technical Report on the review of the AEDT for compliance with “U.S.

Department of Transportation Federal Aviation Administration SWIM Program Specification NAS Service Software Requirements”, due six months from the date of award.

Task Area 5B includes additional tasks that may involve:

1. Coordinate with the Volpe Center on the review of candidate computer models and modules.

2. Conduct a review of measurable and verifiable criteria for compliance with the SWIM SOA service policies and standards.

3. Conduct a review of existing modules provided by the Volpe Center.

4. Provide recommendations for improving the functionality, completeness, and computational and process efficiencies of the modules.

5. Design, develop, and implement updated/new versions of modules using the latest

Microsoft Developer environment tools.

6. Present the modified AEDT modules at the Volpe Center.

C.6 GENERAL REQUIREMENTS

1. ELECTRONIC AND INFORMATION TECHNOLOGY

All electronic and information technology (EIT) deliverables rendered under this contract must comply with Section 508 of the Rehabilitation Act and the Access Board Standards available for viewing at http://www.section508.gov.

http://www.section508.gov/

2. TRAVEL

Some travel by Contractor personnel may be required, to the Volpe Center in Cambridge, Massachusetts and Washington, DC. It is anticipated that travel to the Volpe Center will be necessary for bi-weekly meetings and to Washington D.C. annually. The schedule for travel will be specified at the Task Order Level.

3. PROJECT MANAGEMENT

Use of advanced project management techniques is required to be used for all task areas, including the preparation of a detailed project plan in the Microsoft Project software.

SECTION D - PACKAGING AND MARKING

D.1 PACKAGING (MAY 1999)

The Contractor shall ensure that all items are preserved, packaged, packed, and marked in accordance with best commercial practices to meet the packing requirements of the carrier and ensure safe delivery at destination.

D.2 MARKING (MAY 1999)

All items submitted to the Government shall be clearly marked as follows:

a. Name of contractor;

b. Contract number;

c. Task order number; (if applicable)

d. Description of items contained therein;

e. Consignee's name and address; and

f. If applicable, packages containing software or other magnetic media shall be marked on external containers with a notice reading substantially as follows: "CAUTION:

SOFTWARE/MAGNETIC MEDIA ENCLOSED. DO NOT EXPOSE TO HEAT OR

MAGNETIC FIELDS."

SECTION E - INSPECTION AND ACCEPTANCE

E.1 FAR 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 will make their full text available. Also, the full text of a clause may be accessed electronically at this /these address(es):

https://www.acquisition.gov/far/ (FAR) http://www.dot.gov/ost/m60/tamtar/tar.htm (TAR) http://www.dot.gov/ost/m60/tam2010/tam.htm (TAM)

FEDERAL ACQUISITION REGULATION (48 CFR CHAPTER 1) CLAUSES

NUMBER TITLE DATE

52.246-4 INSPECTION OF SERVICES - FIXED-PRICE AUG 1996

52.246-5 INSPECTION OF SERVICES - COST-REIMBURSEMENT APR 1984

E.2 GOVERNMENT REVIEW AND ACCEPTANCE (OCT 2011)

A. Technical inspection and acceptance of all work, performance, reports, and other deliverables under this contract shall be performed at the location specified in the individual task order. The task order shall also designate the individual responsible for inspection and acceptance as well as the basis for acceptance. Task order deliverable items rejected shall be corrected in accordance with the applicable clauses.

B. Unless otherwise stated in the individual task order, the Government requires a period not to exceed thirty (30) calendar days after receipt of the final deliverable item(s) for inspection and acceptance or rejection. Final acceptance rests with the Contracting Officer or designee.

C. The Government has the right to inspect all supplies and services required by the individual task orders, to the extent practicable, at any and all places and times and in all circumstances or event before acceptance.

https://www.acquisition.gov/far/ http://www.dot.gov/ost/m60/tamtar/tar.htm http://www.dot.gov/ost/m60/tam2010/tam.htm

SECTION F - DELIVERIES OR PERFORMANCE

F.1 FAR 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 will make their full text available. Also, the full text of a clause may be accessed electronically at this/these address(es):

https://www.acquisition.gov/far/ (FAR) http://www.dot.gov/ost/m60/tamtar/tar.htm (TAR) http://www.dot.gov/ost/m60/tam2010/tam.htm (TAM)

NUMBER TITLE DATE

52.242-15 STOP WORK ORDER (applies to FFP task orders) AUG 1989 52.242-15 STOP WORK ORDER ALTERNATE I (applies to CPFF, APR 1984 task orders)

52-247-34 F.O.B. DESTINATION NOV 1991

F.2 CONTRACT PERIOD OF PERFORMANCE (APR 2012)

This contract shall become effective on the date the Contracting Officer (CO) signs the contract.

The ordering period and performance period will begin on the date of contract award. The ordering period will continue for five (5) years thereafter (i.e., term of the contract). Also see Section I.1 entitled Ordering (FAR 52.216-18).

The performance period will continue until the time specified in the clause in Section I.1 entitled Indefinite Quantity (FAR 52.216-22).

F.3 DELIVERIES (NOV 2007)

Delivery of supplies, services, and written documents [e.g. reports, briefings, presentations, etc.

(including required formats and delivery locations)] will be in accordance with the task order requirements. All correspondence and reports related to each task order shall be delivered to the Contracting Officer (CO), designated Administrative Contracting Officer (ACO) and/or Contract Specialist, and/or designated CO’s Technical Representative (COTR) as specified in the task order.

F.4 CONTRACT PROGRESS UPDATES (DEC 2011)

The contractor shall provide monthly overall progress reports. Updates shall be provided to the CO or designee not later than the 15th of each month. The Government requires submission of reports electronically in a Microsoft Office table or spreadsheet format.

https://www.acquisition.gov/far/ http://www.dot.gov/ost/m60/tamtar/tar.htm http://www.dot.gov/ost/m60/tam2010/tam.htm

The monthly progress updates shall address all activity under the contract through the last day of the previous month. The monthly progress report shall contain the following information in table format with column headings as follows:

1. Task Order/Modification No.

2. Task Order Type (FFP, CPFF term or completion)

3. Task Order Title

a. Brief one sentence description of work

4. Submission date of most recent Task Order Progress Report.

5. Name of individual submitting the Task Order Progress Report

6. Task Order/Modification Award Date

7. Period of Performance End Date

8. Obligated Amount

9. Total Amount invoiced to date

10. Notifications (Answer yes, no or n/a). If the answer is yes, submit any additional information as necessary, and provide page reference to location in this report)

a. Has 75% of obligated amount been reached?

b. Have there been changes to Key Personnel changes or changes are requested?

c. Have there been changes to Subcontractors or changes are requested?

d. Have there been any delays, events or trends that will impact performance?

e. Have there been key milestones, including submission of deliverables, met during the reporting period?

11. Other pertinent information.

Any data submitted in the contract progress reports, along with other relevant information, may be included in a past performance database developed and maintained by the Government.

F.5 MONTHLY TASK ORDER PROGRESS REPORTS (APR 2008)

A monthly progress report shall be submitted for each task order. The monthly task order progress reports shall be provided not later than the 15th of each month. The Volpe Center requires that the task order progress report be submitted electronically in a Microsoft Office compatible format. If a contractor has been awarded more than one task order monthly progress reports will be submitted separately. Unless otherwise prescribed in the task order, the report will cover the following items:

1. The work performed during the previous month;

2. Significant findings, problems, delays, events, trends, etc. during the reporting period which result from or affect the performance of the task order;

3. Detailed technical description of the work planned for the next reporting period;

4. Specific action requested of the Government to assist in the resolution of a problem or to effect the timely progression of the task order;

5. An up-to-date schedule of the work performed and work to be performed under the task order. A chart shall be presented reflecting planned project accomplishments versus actual accomplishments in terms of time;

6. Report on accomplishments against any identified performance metrics, if applicable.

F.6 TECHNICAL REPORTS – TASK ORDER CONTRACTS (OCT 2010)

Task orders that identify technical reports as a deliverable will culminate in one of the two types described below:

Letter Report Technical Report Used for smaller tasks such as data validation, field support, task planning documents, literature searches, analysis plans, conference planning documents, and schedules.

Used for major tasks and may include earlier letter-type reports as subsections.

The task order statement of work will specify the type, formatting and the number or reports required. The reports submitted are subject to review and approval by the Volpe Center COTR or Task Order COTR. The COTR or Task Order COTR may request modifications prior to acceptance of interim reports. The contractor shall incorporate the COTR and/or Task Order COTR comments, if resubmission of the report is required. A draft final report shall be submitted for review by the COTR and/or Task Order COTR. The final report will incorporate the COTR and/or Task Order COTR comments the comments. The number and delivery schedule will be specified in each task order. Most final reports shall be submitted on disks and in hard copy in a format specified in the task order.

F.7 REPORTS OF WORK - REPORT DISTRIBUTION (DEC 2003)

Nothing set forth herein regarding number of copies shall be construed as authority to disregard the provisions of the clause of this contract (see Section H.2. – “GPO Printing Requirement”).

A. Contract Progress Report:

1 copy CO or designee 1 copy COTR

B. Monthly Task Order Progress Reports:

1 copy CO or designee 1 copy COTR 1 copy Task Order COTR (TOCOTR)

C. Technical Reports

The number of copies and recipients will be determined in each task order. The contractor shall provide a copy of the cover letter transmitting final submission of technical deliverables to the CO or designee.

F.8 DOCUMENTATION OF COMPUTER PROGRAMS (MAY 1999)

The contractor shall fully document all computer programs first produced in performance of this contract. Unless otherwise specifically agreed to by the CO in writing, the contractor shall deliver the final codes in executable form accompanied by the source and object codes and appropriate support documentation.

F.9 RIGHTS IN DATA (DEC 2007)

All data first produced in the performance of this contract, including software, shall be delivered with unlimited Government rights, unless otherwise agreed to in writing by the CO when granting permission claim to copyright as required by FAR 52.227-14(c).

F.10 WARRANTIES (MAY 1999)

With respect to equipment or supplies acquired under this contract, title of which will pass to the Government, the contractor shall ensure that any warranties, together with rights to replacement, service, or technical assistance, shall run to or automatically be assigned to the Government.

F.11 LICENSES (MAY 1999)

With respect to any computer software, databases, or other licensed product acquired for use by the Government, the contractor shall ensure that the license, together with any associated rights, shall run to or automatically be assigned to the Government.

F.12 PLACE OF CONTRACT PERFORMANCE (OCT 2011)

The Government anticipates that the preponderance of work will be performed at the Contractor’s facility. Work to be performed at another facility will be specified at the Task Order level.

SECTION G - CONTRACT ADMINISTRATION DATA

G.1 TAR 1252.242-73 CONTRACTING OFFICER’S TECHNICAL

REPRESENTATIVE (OCT 1994)

A. The CO may designate Government personnel to act as the CO's Technical Representative (COTR) to perform functions under the contract such as review and/or inspection and acceptance of supplies and services, including construction and other functions of a technical nature. The CO will provide a written notice of such designation to the contractor within five working days after contract award or for construction, not less than five working days prior to giving the contractor the notice to proceed. The designation letter will set forth the authorities and limitations of the COTR under the contract.

B. The CO cannot authorize the COTR or any other representative to sign documents (i.e., contracts, contract modifications, etc.) that require the signature of the CO.

G.2 RESPONSIBILITY FOR CONTRACT ADMINISTRATION (MAR 2012)

Contracting Officer: The Contracting Officer (CO) has the overall responsibility for this contract. The CO alone, without delegation, is authorized to take actions on behalf of the Government to amend, modify, or deviate from the contract terms, conditions, requirements, specifications, details and/or delivery schedules. However, the CO may delegate certain other responsibilities to his/her authorized representatives.

Administrative Contracting Officer: An Administrative CO (ACO) may be designated by the CO. The duties of an ACO include but are not limited to issuing task order RFP’s, analyzing and making recommendations on the contractor's proposals, offers, or quotations upon request of the CO, and approving contractor's invoices in accordance with the terms of the contract.

Task Order Contracting Officer:

The Task Order Contracting Officer (TOCO) has the overall responsibility for the task order to which he/she has been designated. The TOCO, with delegation, is authorized to take actions on behalf of the Government to sign task order award documents, amend, modify, or deviate from the Task Order terms, conditions, requirements, specifications, details and/or delivery schedules. The TOCO only has responsibility over his/her assigned Task Order, and may not authorize changes to the master contract. Any change made to the Task Order may not conflict with the master contract.

Contracting Officer's Technical Representative: A Contracting Officer's Technical Representative (COTR) will be designated by the CO. The responsibilities of the COTR include but are not limited to inspecting and monitoring the contractor's work, determining the adequacy of performance by the contractor in accordance with the terms and conditions of this contract, acting as the Government's representative in charge of work at the site to ensure compliance with contract requirements in so far as the work is concerned, and advising the CO of any factors which may cause delay in performance of the work. The COTR does not have the authority to make new assignments of work or to issue directions that cause an increase or decrease in the price of this contract or otherwise affect any other contract terms.

Task Order Contracting Officer's Technical Representative: The CO may designate a Task Order Contracting Officer's Technical Representative (TOCOTR). The TOCOTR will perform the duties of the COTR in connection with the technical oversight of an individual task order.

The TOCOTR does not have the authority to make new assignments of work or to issue directions that cause an increase or decrease in the price of this contract or on a task order or otherwise affect any other contract or task order terms.

G.3 ORDERING (MAR 2012)

A. During the period of performance of the contract, the CO or TOCO may issue task orders in accordance with Section I.1. (FAR 52.216-18 and 52.216-22).

B. The Government will order any supplies and services to be furnished under this contract by issuing task orders on Optional Form 347 or an agency-prescribed form by mail, facsimile, or electronically. In addition to the CO, the following individuals are authorized ordering officers: Designated ACOs.

C. The performance period of the contract is not synonymous with the performance period of any task order issued under the contract. The period of performance for a given task order shall be specified in that task order.

D. A Standard Form 30 will be used to modify task orders.

E. A representative authorized by the contractor shall acknowledge receipt of each task order within three (3) calendar days of receipt.

F. Each task order issued may incorporate the contractor’s technical and/or price proposals and will include an estimated cost and fixed fee set forth as a ceiling price or a total fixed price in the case of a fixed price task order.

Under no circumstances will the contractor start work prior to the issue date of the task order unless specifically authorized to do so, in writing, by the CO or ACO.

G.4 ISSUANCE OF TASK ORDERS (MAY 2011)

A. Under this contract, as firm work requirements materialize, within the period of performance of the master contract, and within the funds allotted, the Contracting Officer will direct the Contractor to perform work as generally described in Section C. The Contracting Officer will issue direction to the Contractor in the form of Task Orders. Prior to issuance of any Task Order, the Contracting Officer will discuss with the Contractor the work to be performed, the timing, and will negotiate the price. In the event that agreement cannot be reached on the price of any Task Order, the Contracting

Officer may unilaterally determine the price of that Task Order. In such event, the Contractor may seek relief or remedies as set forth in the Disputes Clause. Except as specifically provided, the Government makes no representation as to the number of Task Orders or the actual amount of work that will be assigned. The Contractor shall not perform any work, until it receives a specific Task Order signed by the Contracting Officer. Each Task Order will contain as a minimum, the following:

1. Sequential number;

2. Type of Task Order – Firm-Fixed-Price or Cost Plus Fixed Fee

3. Statement of the problem;

4. Scope of work effort;

5. Reporting requirements;

6. Time schedule of performance;

7. Estimated level of effort to be expended, if applicable;

8. Price or fixed fee, as applicable;

9. Delivery, inspection and final acceptance points.

B. If a Task Order will culminate in a report, the Task Order will specify the type of report and format required.

G.5 TASK ORDER OMBUDSMAN (FEB 2011)

Contractors with any complaint regarding award of individual task orders shall submit such complaint(s) to the Volpe Center Competition Advocate, U.S. Department of Transportation, Research and Innovative Technology Administration, Volpe National Transportation Systems Center, 55 Broadway, Cambridge, MA 02142, Attention: David S. Ishihara; fax: (617) 494-3062;

e-mail: David.Ishihara@dot.gov. It should be noted that in accordance with FAR 16.505(a)(9), no protest is authorized in connection with the issuance of a task order except for a protest on the grounds that the task order increases the scope, period of performance, or maximum value of the contract.

G.6 PAYMENT AND CONSIDERATION (JAN 2011)

Contract clauses regarding payment processes and consideration will differ depending on the contract type/pricing methodology used in the task order. Specific clauses to be used in each case are provided below:

A. The following clause is applicable to fixed-price task orders:

CONSIDERATION - FIXED PRICE

Upon delivery and acceptance of the required services, the contractor shall be paid at the fixed price specified on the face of the task order.

B. The following clauses are applicable to Cost-Plus-Fixed-Fee task orders:

CONSIDERATION - COST-PLUS-FIXED-FEE

(1) Subject to the clauses Limitation of Cost (FAR 52.232-20), Allowable Cost and Payment

(FAR 52.216-7), and Fixed Fee (52.216-8), the total allowable cost of this task shall not exceed $(TO BE COMPLETED AT TIME OF AWARD OF TASK), which is the total estimated cost of the contractor's performance hereunder exclusive of fixed fee. In addition, the Government shall pay the contractor a fixed fee of $(TO BE COMPLETED AT TIME OF AWARD OF TASK) for the performance of this task.

(2) The contractor shall be provisionally reimbursed indirect expenses on the basis of billing rates approved by the Cognizant Federal Agency (CFA) pending establishment of final indirect rates.

(3) The final indirect expense rate pertaining to the contract shall be those determined for the appropriate fiscal year in accordance with FAR 42.705 and FAR 52.216-7.

G.7 PAYMENTS UNDER COST REIMBURSEMENT CONTRACTS (FEB 2011)

NOTE: Under no circumstances can funds obligated under one task order be used to pay costs incurred or fee earned under another task order.

The invoicing and payment office for all contract actions issued by the DOT/RITA/Volpe National Transportation Systems Center is located at the Enterprise Services Center (ESC), Office of Financial Operations, Federal Aviation Administration (FAA), Oklahoma City, Oklahoma.

The contractor must submit separate cost and fee invoices. All invoices, including supporting documentation, shall be submitted electronically (e.g., PDF format) to the ESC at FAA in Oklahoma City by e-mail at the following address: volpeinvoices@faa.gov (all lower case). A cover e-mail must accompany each invoice and provide the applicable information in the fields listed below.

Invoice Date:

Supplier Name:

Invoice Amount:

Invoice Number:

Contract No.

Task Order No.:

Modification No.:

Terms/Discount:

Performance Period:

Notes:

mailto:volpeinvoices@faa.gov

Under indefinite delivery/indefinite quantity contracts, separate invoice or contract financing requests must be submitted for each task order. However, all interim payment requests for task orders under the contract must be submitted concurrently each month and only one contract level completion invoice shall be submitted. The Contractor shall submit a final invoice for each task order. This shall include a complete list of invoices previously tendered under the task order.

The final invoice shall be submitted within six (6) months of the task order’s physical completion. If changes to this invoice become necessary as a result of Government review, the Contractor shall submit a corrected final invoice.

In addition to the information required by FAR 52.216-7 and FAR 52.232-25 incorporated by reference in Section I, an invoice or contract financing payment request must meet the following requirements:

1) Consecutively number each interim payment request beginning with No. 1 for each task order;

2) The voucher shall include current and cumulative charges by major cost elements such as direct labor, overhead, subcontracts, and other direct costs. Cite direct labor hours incurred by the Prime contractor and each subcontractor. Other direct costs must be identified, e.g., travel, per diem, material, and equipment;

3) Requests for contract financing or invoices must clearly indicate the period of performance for which payment is requested and the Volpe Center accounting information necessary to process payments. When contracts or task orders contain multiple lines of accounting data, charges that cannot be assigned to a single line of accounting information should be allocated based on the percentage of total dollars unless otherwise specified;

4) When the Contractor submits vouchers on a monthly basis, the period covered by invoices or requests for contract financing payments must be the same as the period for monthly progress reports reported under the contract or tasks orders. If, in accordance with FAR 52.216-7, the Contractor submits requests for invoices or contract financing payments more frequently than monthly, one payment request per month must have the same ending date as the monthly progress report;

5) Pending settlement of the final indirect rates for any period, the Contractor shall be reimbursed at billing rates approved by the Cognizant Federal Agency (CFA). The Contractor shall ensure that any change in the identity of the CFA responsible for establishment of its indirect rate factors is made known to the Volpe Center ACO.