RFQ-693JJ324Q000013.pdf
PDF 372 KB Posted
- Attached to
- AERMOD Emission Rate PreProcessor
- Solicitation number
- 693JJ324Q000013
About this file
This request for quotation (RFQ) solicits environmental consulting services to develop an AERMOD emission rate pre-processor tool. The RFQ is a total small business set-aside under NAICS code 541620 issued by the Department of Transportation Federal Highway Administration (FHWA). Quotes are due by February 19, 2024 with award anticipated shortly after. The contract is a firm-fixed-price purchase order with a 12-month base period and optional 6-month extension. Services include project management, reviewing existing tools, creating requirements and system documentation, programming the pre-processor, and testing. The pre-processor will combine MOVES and AP-42 emission rates with road and traffic data to generate AERMOD input files.
View the file
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
REQUEST FOR QUOTATION (RFQ) - 693JJ324Q000013
Issuing Office: United States Department of Transportation Federal Highway Administration (FHWA) Office of Acquisition & Grants Management (HCFA) 1200 New Jersey Avenue, SE Washington, DC 20590-0001
Agency Contact: Jason Motala, Contract Specialist Telephone: 720-963-3439 Email: jason.motala@dot.gov
Solicitation Number: 693JJ324Q000013
Title: AERMOD Emission Rate PreProcessor
Solicitation Release Date: January 31, 2024
Technical Questions Due Date:
Quotation Due Date:
:00 M Eastern Time (ET) on February , 2024 4:00 PM ET on February 19, 2024
Submit Questions and To Quotations: Jason Motala at jason.motala@dot.gov
NOTE: This is a total small business set-aside for vendors under NAICS 541620 – Environmental Consulting Services for an open market quote.
PART I
RFQ INFORMATION AND INSTRUCTIONS FOR PREPARATION OF QUOTATION
This is an open-market, Firm-Fixed-Price (FFP) RFQ with Cost Reimbursable Travel. This solicitation is prepared in accordance with Federal Acquisition Regulation (FAR) Part 12, the Acquisition of Commercial Products and Commercial Services in conjunction with the policies and procedures for solicitation, evaluation, award as prescribed in FAR Part 13, Simplified Acquisition Procedures. The solicitation document and incorporated provisions and clauses are those in effect through Federal Acquisition Circular (FAC) 2024-02.
This solicitation is a total small business set-aside business for vendors registered under the North American Industry Classification System (NAICS) code 541620 – Environmental Consulting Services with an industry size standard of $19 million. A responsible quoter is one whose quotation conforms to the solicitation and will be most advantageous to the Government.
It is the contractor’s responsibility to be familiar with applicable clauses and provisions. FAR Provisions and Clauses may be viewed and/or downloaded from http://www.acquisition.gov/far.
The quoter must have a current active registration in the System for Award Management (www.SAM.gov) at the time of quote submission in order to be eligible to receive an award under this RFQ.
Quote Requirements
Evaluation Factors and Basis of Award
The Government will evaluate quotations and make an award decision based on the following non-price factors listed in order of descending importance for the ultimate award decision.
(A) Technical Approach
Detailed technical and management approach and understanding to perform each task outlined in the Statement of Work (SOW).
Describe programming languages the Offeror is capable of working in.
Any relevant experience in performing similar work.
A description of how the knowledge and experience of the team from previous experience will be reflected in the performance of the work.
The Offeror must provide the title and a description of the duties of key included.
Resumes of key personnel, limited to two pages per resume.
Level of Effort table (table displaying names, labor categories and labor hours per task. (Price information must not be provided in the Technical Proposal.)
The Technical Proposal must set forth any information that the Offeror wishes to bring to the attention of the Government.
The Offeror shall provide a schedule of deliverables by Task (See section 6.1 Technical Exhibit 1 - Deliverables Schedule).
(B) Price
(C) Past Performance
The Government will issue a Firm-Fixed-Price (FFP) purchase order with Cost Reimbursable travel resulting from this Request for Quote (RFQ) based on a quote that represents the Best Value to the Government, considering the quotes Technical Approach, Price and Past Performance factors. Technical Approach is approximately equal to Price and Past Performance combined.
In responding to this quotation, your quotation MUST adhere to the below Quote Format.
Quote Format:
• Quotes must be prepared on 8½ x 11-inch paper
• Do not include marketing materials. Do not include letters of support/recommendation
• Quotes must be submitted in a readable format. Adobe (.pdf) documents must not contain any security restrictions (e.g. password protection) that prevent the Government from distributing and printing the document.
• All text must be presented using Times New Roman or Arial font, no less than 11-point.
Text in any images must be legible when printed. Footnotes, legends, or labels associated with tables or diagrams, and other information that is ancillary to the main text, may be presented in a font size smaller than 11-point font---provided that any such smaller font is fully legible, no less than 8-point font.
• Page margins must be a minimum of 1 inch on each side, (top and bottom, left and right)
• All elements of Volume I and Volume II must be included as separate attachments within one e-mail message. The email size must not exceed 10 Megabytes (10MB).
• Quote must be subdivided into two volumes as follows:
o Volume I - Technical Approach o Volume II: Price and Business Quote
• The quote naming conventions must be as follows:
o “Contractor Name - Volume I - Technical Approach” o “Contractor Name - Volume II – Price and Business Quote”
• “Volume I – Technical Approach” must not contain any pricing information.
Note: A quote that does not conform to the above or exceeds the email size will be considered noncompliant and removed from further consideration for award. The timeliness of a quote is determined by the date and time of receipt. It is the quoters responsibility to ensure that the quote submission email is received by the designated cut-off date and time. Early submission is encouraged.
This is an electronic procurement. Hard copies of quotes will not be accepted. Please reference the RFQ number on all correspondence including the subject line of any e-mails related to this procurement.
Information included in Volume I – Technical Approach:
(A) Technical Approach
This volume must provide a detailed narrative that describes the Quoter’s technical approach and the staff’s abilities to complete the requirements of the Statement of Work (SOW) under this RFQ.
This narrative should not restate the SOW requested under this RFQ.
The quoter’s approach to performing the requirements and its capability to successfully perform the contract will be evaluated. All subfactors noted below are considered equal in the overall evaluation of Technical Approach. The quoter’s approach to performing the requirements and its capability to successfully perform the contract will be evaluated. Quotes will be evaluated based on the following:
The quote’s technical approach for performing the requirements, including description of the Statement of Work (SOW) objectives, scope, and specific tasks to demonstrate clear understanding of the requirements.
The quote’s staffing plan including all key personnel, subcontractors, availability of key personnel and subcontractors, level of effort, and a description of their roles and responsibilities.
The quoted staff’s qualifications and their appropriateness for the services. Appropriate qualifications include:
o Experience with performing programming for air quality modeling work.
o Expertise with the Environmental Protection Agency’s (EPA) Motor Vehicle
Emissions Simulator (MOVES) model, an understanding of the format of MOVES outputs, and experience using MOVES for a PM hot-spot analysis.
o Expertise with the American Meteorological Society/Environmental Protection Agency Regulatory Model (AERMOD); an understanding of the format of AERMOD inputs, especially the EMISFACT input; and experience using AERMOD for a PM hot-spot analysis.
o Familiarity with EPA’s Transportation Conformity regulations for PM hot-spot analyses and PM Hot-Spot Guidance, in particular, Sections 4 (using MOVES), 7 (using AERMOD), and Appendix J (AERMOD inputs).
o Familiarity with the California Line Source Dispersion Model (CALINE) approach to input emission rates and traffic information.
o Expertise in air dispersion science and traffic engineering.
The quotation includes a satisfactory approach for developing and maintaining a schedule of deliverables and performing and delivering the work on time.
The evaluation for Factor A- Technical Approach will be done holistically with a rating scale of "High Confidence," "Some Confidence," and "Low Confidence," representing the Government’s confidence that the quoter understands the requirement and will be successful in performing the work as outlined in below.
High Confidence
The Government has high confidence that the Proposer understands the requirement, proposes a sound approach, and will be successful in performing the contract with little or no Government intervention.
Some Confidence
The Government has some confidence that the Proposer understands the requirement, proposes a sound approach, and will be successful in performing the contract with some Government intervention.
Low Confidence
The Government has low confidence that the Proposer understands the requirement, proposes a sound approach, or will be successful in performing the contract even with Government intervention.
End of information included in Volume I – Technical Approach.
Information included in Volume II – Price and Business Quote:
(B) Price
The quote’s prices will be evaluated, but not scored. The quote’s prices must be entirely compatible with the technical quote and the evaluation will be inclusive of all optional items, if applicable. The evaluation will determine whether the quoted prices are realistic, complete, and reasonable in relation to the solicitation requirements. The evaluated price will be considered within the best value award decision, award may be made to a quoter that does not provide the lowest priced quotes.
Submitted pricing in the format of the Schedule of Service, Contract Line Item Number (CLIN) Structure table shown in Part II.
Business Information
• Business Size (Small, Woman-Owned, Disadvantaged, Hub-Zone, Large, Non- Profit, etc.)
• SAM.gov Unique Entity Identifier
• CAGE Code
• Federal Tax Identification Number (9-Digits)
• Correct Mailing Address for the Purchase Order (include name, telephone, email address)
• Verification of registry in System for Award Management (SAM).
End of information included in Volume II – Price and Business Quote.
(C) Past Performance (No submission required)
The quoter’s past performance on previous contracts will be evaluated to assess successful relevant prior experience. The quoter’s past performance as found in Contractor Performance Assessment Reporting System (CPARS) will be evaluated to determine, as appropriate, the performance risk associated with their quote as it relates to the requirement for this solicitation.
Past Performance will be determined to be Satisfactory or Unsatisfactory. If a quoter does not have a history of relevant contract experience, or if past performance information is not available, the quoter will receive a Neutral past performance rating. See table below for definitions.
RATING DEFINITION
Satisfactory Offeror’s performance met contractual requirements. Performance was accomplished with some minor problems for which any required corrective actions taken were satisfactory. Past performance indicates a moderate to low risk of unsuccessful performance to the Government.
Neutral No relevant past performance record is identifiable upon which to base a meaningful performance risk prediction. A search was unable to identify any relevant past performance information for the contractor or their key personnel. This is neither a negative nor positive assessment.
Unsatisfactory Offeror’s performance did not meet one or more critical contract requirements. Performance was not successfully accomplished, or a contract was terminated for default. Past performance indicates a very high or unacceptable risk of unsuccessful performance to the Government.
PART II
SCHEDULE OF SERVICES
The Contractor must furnish all supplies/services to perform the tasks described under this solicitation entitled, AERMOD Emission Rate PreProcessor. The Contractor must furnish all supplies/services in support of the mission of the FHWA.
CLIN DESCRIPTION PRICE
00101
Task 1 – Project Management
Pricing: Firm-Fixed-Price
Period of Performance: 12 months from the effective date of the award
00201
Task 2 – Review of Existing Tools
Pricing: Firm-Fixed-Price
Period of Performance: 12 months from the effective date of the award
00301
Task 3 – Requirements Document
Pricing: Firm-Fixed-Price
Period of Performance: 12 months from the effective date of the award
00401
Task 4 – Pre-Processor Programming and Testing
Pricing: Firm-Fixed-Price
Period of Performance: 12 months from the effective date of the award
00501
Task 5 – Documentation
Pricing: Firm-Fixed-Price
Period of Performance: 12 months from the effective date of the award
00601
Travel
Pricing: Cost Reimbursable
Ceiling (Not-To-Exceed): $5,000.00
Period of Performance: Effective date of the award thought entire period of performance.
$5,000.00
BASE PERIOD: $
10701 Task 6 – Volume Sources (Optional)
Pricing: Firm-Fixed-Price
FAR 52.217-7 Option for Increased Quantity-Separately Priced Line Item (Mar 1989). This CLIN will be exercised bi-laterally as a contract modification (SF-30).
Period of Performance: Effective date of modification through 6 months.
OPTION PERIOD ONE: $
TOTAL PRICE: $
PART III
STATEMENT OF WORK
AERMOD Emission Rate Pre-Processor
1.0 Overview
This is a non-personal services contract to create an AERMOD Emission Rate Pre-Processor.
The Government will not exercise any supervision or control over the contract service providers performing the services herein. Such service providers shall be accountable solely to the Contractor who, in turn is responsible to the Government as defined in this Statement of Work (SOW). The Contractor shall perform to the standards herein.
1.1 Background
The American Meteorological Society/Environmental Protection Agency Regulatory Model (AERMOD) is a dispersion model used by highway project sponsors to predict pollutant concentrations for a variety of applications, such as when a particulate matter (PM) hot-spot analysis is required by the transportation conformity regulations. AERMOD currently requires the input of emission rates in grams per second per meter squared (g/s/m2) for the AREA/LINE and RLINE source types and as gram per second for VOLUME sources. Since MOVES outputs emission rates in grams/link-hour or grams/vehicle-mile, AERMOD users need to convert the emission rate units when using the AREA/LINE and RLINE source types. This conversion is usually done with manual spreadsheet calculations or scripting tools, which often also combine the traffic data and geospatial coordinates of the roadway links with the emissions rates. These spreadsheets and scripts might also include road dust emission rates as inputs when creating overall composite emission rates in units of g/s/m2.
1.2 Objective
The objective of this contract is to create an AERMOD emission rate pre-processor tool that will combine the following inputs:
MOVES vehicle emission rates (in both grams/link-hour and grams/vehicle-mile), AP-42 road dust emission rates (in both grams/link-hour and grams/vehicle-mile), road geometry, and traffic data.
Using these inputs, the pre-processor will output information associated with the LOCATION, SRCPARAM, and EMISFACT Source Pathway keywords in a AERMOD input file (.inp) format as required for AERMOD’s AREA/LINE and RLINE1 source types (as an optional task also provide the LOCATION, SCRCPARAM, and EMISFACT inputs as required for VOLUME sources). The pre-processor shall also include the capability of utilizing multiple options for the Qflag and Qfact parameters used for the EMISFACT keyword in AERMOD. This will create a standard pre-approved processing tool, which will improve the transparency of the calculations for a PM hot-spot analysis and therefore reduce review times for highway projects required to
1 Only the RLINE source type, not the RLINEXT source type.
conduct these analyses. It will also reduce burden on the user by incorporating manual emission rate calculations into a pre-processor.
1.3 Detailed Requirement
The Contractor must provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to create an AERMOD Emission Rate Pre-Processor Tool.
The contractor will be responsible for conducting a review of existing tools; creating a requirements document; completing all programming to create the pre-processor; conducting testing; and providing full documentation. The contract will include an optional task to add a function to the pre-processor to provide gram per second emission rates for VOLUME sources in
AERMOD.
1.3.1 Task 1 – Project Management (CLIN 00101)
The Contractor must provide a Kick-Off Meeting for the project with the Contracting Officer (CO), Contracting Officer’s Representative (COR), and the technical review panel. The technical review panel composition is at the discretion of the COR, but it will likely consist of 4-8 staff from FHWA and EPA that regularly work on dispersion modeling issues for mobile sources.
The technical review panel will also assist in reviewing all deliverables for the project and is therefore critical to the success of the project.
The Contractor must utilize the Kick-Off Meeting to present its Draft Work Plan to the COR and receive guidance from the COR in finalizing the scope and specifics of the Final Work Plan.
The Kick-Off Meeting may, at the discretion of the COR and in consultation with the Contractor, be conducted in person in Washington, D.C., with out-of-town remote participation available, remotely via conference call, or virtually over the Internet.
The Kick-Off Meeting must occur within two (2) weeks from the date of award, unless the COR agrees to a delay. The Kick-Off Meeting Minutes are due one (1) week after the Kick-Off Meeting.
For the Kick-Off Meeting, the Contractor must prepare a Draft Work Plan. The Draft Work Plan must include all pertinent work information including, but not limited to, full descriptions of the tasks to be completed under the contract, deliverables with due dates for each task, methodology/approach expected to be employed, timeline (e.g., Gantt chart), staff labor/cost distribution by task, channels of communication, management and staffing plan, travel plan, and risks and assumptions. The Contractor must make the Draft Work Plan available to the COR for review at least five (5) business days prior to the Kick-Off Meeting unless the COR agrees to a delay. The COR will review the Draft Work Plan and provide comments to the Contractor, which must incorporate the feedback in a revised, Final Work Plan which is due three (3) weeks after the Kick-Off Meeting.
Following the Kick-Off Meeting, the Contractor must coordinate monthly Regular Status Meetings with the COR and the technical review panel to provide updates on progress, schedule, and risks.
The contractor must attend regular progress meetings. The Contracting Officer or Contracting Officer’s Representative (COR), and other Government personnel, as appropriate, may meet periodically with the Contractor to review the Contractor's performance. At these meetings, the CO will apprise the Contractor of how the Government views the Contractor's performance and the Contractor will apprise the Government of problems, if any, being experienced. Appropriate action must be taken to resolve outstanding issues. These meetings must be at no additional cost to the Government.
The Contractor must provide a Monthly Progress Report to the COR throughout the duration of the project at least three (3) business days prior to monthly Regular Status Meetings. Each report must include project progress, findings, next steps, problems, and recommended actions.
Deliverables:
Kick-Off Meeting Kick-Off Meeting Minutes Draft Work Plan Final Work Plan Regular Status Meetings Monthly Progress Reports
1.3.2 Task 2 – Review of Existing Tools (CLIN 00201)
The objective of this task is to conduct a review of existing calculation methods and tools used to prepare emission rate inputs to AERMOD. This review will help to identify:
Existing tools and/or scripts that could be leveraged as a starting point for the pre-processor, and
Functions and features from existing tools that are desired to be included in the pre-processor
These tools could range from spreadsheets or scripts used for a single highway project to robust tools, such as CT-EMFAC2, TRAQS3, or the GIS to AERMOD (GTA) tool.4 EPA has a tool called MOVES2AERMOD5 that automates the process of generating the EMISFACT portion of an AERMOD input file using MOVES output. Similar tools could also be available from
2 CT-EMFAC can be used to estimate project-level emissions from on-road mobile sources based on the EMFAC emissions model. More information is available at: https://dot.ca.gov/programs/environmental-analysis/air-quality/project-level-air-quality-analysis 3 TRAQS is an open-source software tool written in Python for NCHRP Project 25-48 to combine the MOVES and AERMOD models through a centralized GUI. The installer, source code, and documentation are available at https://apps.trb.org/cmsfeed/TRBNetProjectDisplay.asp?ProjectID=3674.
4 The GTA tool was created by the University of New Mexico as Geographical User Interface that allows users to take the MOVES files and place them into AERMOD quickly and accurately. The Python-based tool enables conversion of GIS layers to AERMOD Sources, corresponding emission rates from MOVES output and near-road receptors. More information available at:
https://www.fhwa.dot.gov/environment/air_quality/conformity/methodologies/fhwahep22024.pdf and https://github.com/FHWA/GIS_AERMOD_Project.
5 More information is available at https://www.epa.gov/moves/tools-develop-or-convert-moves-inputs#emisfact. The MOVES2AERMOD tool is also referenced in Section 4.6 of EPA’s PM Hotspot Guidance.
academics or research institutions since they may be used to conduct transportation/air quality studies.
The contractor will conduct research through a literature review, web searches, interviews, etc. to identify existing tools. Then the contractor will evaluate the tools; summarize their features, limitations, and assumptions; and identify strengths and weaknesses of each in a technical memo.
If the contractor desires to use any publicly available tools as a starting point for the pre-processor they will make this recommendation in the technical memo and discuss with FHWA before proceeding. The technical review panel will comment on the draft technical memo and the contractor will address comments in the final technical memo. and discuss with FHWA before proceeding. The technical review panel will comment on the draft technical memo and the contractor will address comments in the final technical memo.
Deliverables:
Draft Technical Memo Final Technical Memo
1.3.3 Task 3 – Requirements Document (CLIN 00301)
The objective of this task is to create a requirements document that will be used to guide the programming in the next task. Based on feedback from the technical review panel on desirable functions and features of existing tools identified in the previous task, the contractor will prepare a draft requirements document. This document will recommend the pre-processor format, the programming language, calculation methodologies, and provide mockups or describe how users will interact with the pre-processor. The technical review panel will comment on the draft requirements document and then the contractor will prepare a final requirements document.
Deliverables:
Draft Requirements Document Final Requirements Document
1.3.4 Task 4 – Pre-Processor Programming and Testing (CLIN 00401) The objective of this task is to perform the programming, testing, and debugging to create the pre-processor that will achieve the objective stated in Section 1.2 above. The pre-processor should undergo multiple rounds of internal testing and debugging by the contractor to ensure it is operating as expected before submitting the draft code for review by the technical review panel.
This testing should include a test to demonstrate consistency of the pre-processor results with manual calculations that currently have to be done to convert gram/vehicle-mile emission rates from MOVES to g/s/m2 emission rates for input into AERMOD. The contractor should submit both the source code and a compiled executable file that will run on a current version of Windows. The contractor should also submit a transmittal memo with a draft user’s guide and technical formulation information about the pre-processor to allow for the technical review panel to test the pre-processor. The memo will serve as a starting point for the full documentation in Task 5.
The technical review panel will review the draft code/compiled executable and transmittal memo and provide comments to the contractor after testing. The contractor will address comments in the Final Code/ Compiled Executable, which shall be 508 compliant.6 Comments on the transmittal memo may be addressed during Task 5.
Deliverables:
Draft Code/ Complied Executable Transmittal Memo Final Code/ Compiled Executable
1.3.5 Task 5 – Documentation (CLIN 00501)
The objective of this task is to provide a document for the pre-processor that includes a User’s Guide and technical formulation information for the pre-processor. The final version of this document shall be provided as both a 508 compliant Word file7 and a 508 compliant PDF file.8
The User’s Guide should provide a sufficient level of detail for most users to operate the processor without assistance. It should also include a description of inputs, outputs, and steps needed to run the processor. Finally, the user guide should also provide several examples to assist users in learning how to use the processor. A set of input and output files that corresponds to each example in the User’s Guide should also be provided.
The technical formulation information should document all calculations performed by the pre-processor in a sufficient level of detail that an experienced air quality modeler could perform the calculations outside of the pre-processor and get the same results. The technical formulation information is important to transparency portion of the objective, and it may be referenced in official transportation conformity documentation for a PM hotspot analysis.
The contractor will provide the Draft Document and Draft Example Files for review. The technical panel will review these deliverables and provide comments to the contractor. The contractor will address comments in the Final Document and Final Example Files. After receiving confirmation that all comments have been addressed, the contractor should convert the Final Document to a fully 508 compliant PDF file with proper tags, etc. Technical Exhibit 2 provides 508 compliance information, which should be followed for the Final Document.
Deliverables:
Draft Document Draft Example Files Final Document Final Example Files
6 See “Section 508 Checks for Websites and Applications”. FHWA-HAD-21-007. Available at:
https://highways.dot.gov/sites/fhwa.dot.gov/files/had21007.pdf 7 See “Creating Accessible Word Files” FHWA-HAD-20-001. Available at:
https://highways.dot.gov/sites/fhwa.dot.gov/files/had20001.pdf and “Creating Accessible Word Files Checklist.” FHWA-HAD-20-002. Available at:
https://highways.dot.gov/sites/fhwa.dot.gov/files/had20002.pdf 8 See “Creating Section 508 Conformant PDFs.” FHWA-HAD-21-001.
https://highways.dot.gov/sites/fhwa.dot.gov/files/had21001.pdf and “Creating Section 508 Conformant PDFs Checklist.” FHWA-HAD-21-002. Available at:
https://highways.dot.gov/sites/fhwa.dot.gov/files/had21002.pdf
508-Compliant Final Document (MS Word and PDF files)
1.3.7 Task 6 – Volume Sources (Optional CLIN 10701)
The objective of this optional task is to repeat Tasks 4-5 and revise the code, testing, and documentation to include VOLUME sources in addition to the RLINE and AREA/LINE sources already included in the pre-processor. The contractor will ensure that the pre-processor provides outputs with the information associated with the LOCATION, SRCPARAM, and EMISFACT Source Pathway keywords in a AERMOD input file (.inp) format as required for AERMOD VOLUME sources. The same deliverables and review process and deliverables as were used for Tasks 4-5 will be used for this optional task.
Deliverables:
Task 6a: Draft Code/ Executable Task 6a: Transmittal Memo Task 6a: Final Code/ Executable Task 6b: Draft Document Task 6b Draft Example Files Task 6b Final Document Task 6b Final Example Files Task 6b 508-Compliant Final Document (MS Word and PDF files)
2.0 Period of Performance
The period of performance for the base contract should be 12 months. The period of performance for the option period should be 6 months.
The Period of Performance reads as follows:
Base Period 12 months (CLINs 00101 – 00501) Option Period 6 months (CLIN 10701)
Note: Travel CLIN 00601 will be for the entire purchase order period of performance.
3.0 General
3.1 Hours of Operation
Not applicable to this contract.
3.2 Place of Performance
The work to be performed under this contract shall be performed at the Contractor’s facility.
3.3 Physical Security
The Contractor shall be responsible for safeguarding all government equipment, information, and property provided for Contractor use.
3.4 Special Qualifications
Not applicable to this contract.
3.5 Periodic Progress Meetings
The contractor agrees to attend progress meetings. The Contracting Officer or Contracting Officer’s Representative (COR), and other Government personnel, as appropriate, may meet periodically with the Contractor to review the Contractor's performance. At these meetings, the CO will apprise the Contractor of how the government views the Contractor's performance and the Contractor will apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the government.
3.6 Identification of Contractor Employees
All contractor personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by Contractors are suitably marked as Contractor products or that Contractor participation is appropriately disclosed.
3.7 Contractor Travel (CLIN 00601)
The Contractor may be required to during the performance of this contract. All travel requires Government approval/authorization and notification to the COR prior to any travel expenditure.
Travel costs shall not exceed $5,000.00. The Contractor shall verify adequate funding is available prior to incurring any travel expense. Travel shall be in accordance with the Federal Travel Regulation.
3.8 Materials
Material costs are not anticipated for this contract.
3.9 Organizational Conflict of Interest
Contractor and subcontract personnel performing work under this award may receive, have access to, or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.), or perform evaluation services which may create a current or subsequent Organizational Conflict of Interests (OCI) as defined in FAR Subpart 9.5. The Contractor shall notify the CO immediately whenever he/she becomes aware that such access or participation may result in any actual or potential OCI, and may merit the submittal of a plan to the CO to avoid or mitigate any such OCI. This mitigation plan would be determined to be acceptable solely at the discretion of the CO, and in the event the CO unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may affect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.
3.10 Phase In /Phase out Period
Not applicable to this contract.
4.0 Government Furnished Equipment and Services
Not applicable to this contract.
5.0 Applicable Publications (Current Editions)
5.1 Applicable Clauses
52.217-7 Option for Increased Quantity-Separately Priced Line Item (Mar 1989)
The Government may require the delivery of the numbered line item, identified in the Schedule as an option item, in the quantity and at the price stated in the Schedule. The Contracting Officer may exercise the option by written notice to the Contractor within 15 days. Delivery of added items shall continue at the same rate that like items are called for under the contract, unless the parties otherwise agree.
(End of clause)
6.0 Attachment/Exhibit List
6.1 Exhibit 1
Deliverables Schedule
6.2 Exhibit 2
Requirements for Implementing Section 508 Standards
6.3 Exhibit 3
Schedule of Services (To be included at award)
TECHNICAL EXHIBIT 1
DELIVERABLES SCHEDULE
This technical exhibit lists any reports or documentation that is required as a deliverable to include the frequency, # of copies, medium/format and who/where it is to be submitted. A deliverable is anything that can be physically delivered but may include non-physical things such as meeting minutes.
Task Deliverable 508 Compliant
Timing (from task order award or as specified)
Medium/ Format
Submit To
Task 1: Project Management
Kick-Off Meeting
No 2 weeks
In-person meeting, remotely via conference call, or virtually over the Internet at the discretion of the COR
COR
Task 1: Project Management
Kick-Off Meeting Minutes
No 1 week following meeting
Microsoft Office (Word)
Task 1: Project Management
Draft Work Plan
No 5 working days prior to Kick-Off Meeting
Microsoft Office (Word)
COR
Task 1: Project Management
Final Work Plan
No 3 weeks after Kick-Off Meeting
Microsoft Office (Word)
COR
Task 1: Project Management
Regular Status Meetings
No Monthly Conference call
COR
Task 1: Project Management
Monthly Progress Report
No Monthly by 3 working days prior to monthly status meeting
Microsoft Office (Word)
COR
Task 2:
Review of Existing Tools
Draft Technical Memo
No To be proposed by contractor
Microsoft Office (Word)
COR
Task 2:
Review of Existing Tools
Final Technical Memo
No To be proposed by contractor
Microsoft Office
Compliant
Timing (from task order award or as specified)
Medium/ Format
Submit To
Task 3:
Requirements Document
Draft Requirements Document
No To be proposed by contractor
Microsoft Office (Word)
COR
Task 3:
Requirements Document
Final Requirements Document
No To be proposed by contractor
Microsoft Office (Word)
COR
Task 4: Pre- Processor Programming and Testing
Draft Code/ Executable
No To be proposed by contractor
Source code and compiled executable file
COR
Task 4: Pre- Processor Programming and Testing
Transmittal Memo
No To be proposed by contractor
Microsoft Office (Word)
COR
Task 4: Pre- Processor Programming and Testing
Final Code/ Executable
Yes To be proposed by contractor
Source code and compiled executable file
COR
Task 5:
Documentation
Draft Document
No To be proposed by contractor
Microsoft Office (Word)
COR
Task 5:
Documentation
Draft Example Files
No To be proposed by contractor
Input/Output Files
COR
Task 5:
Documentation
Final Document
No To be proposed by contractor
Microsoft Office (Word)
COR
Task 5:
Documentation
Final Example Files
Yes To be proposed by contractor
Input/Output Files
COR
Task 5:
Documentation
508 Compliant Final Document
Yes 11 months Microsoft Office (Word) and
PDF.
COR
Task 6a: Pre- Processor Programming and Testing
Draft Code/ Executable
No To be proposed by contractor
Source code and compiled executable file
COR
Task 6a: Pre- Processor Programming and Testing
Transmittal Memo
No To be proposed by contractor
Microsoft Office
Compliant
Timing (from task order award or as specified)
Medium/ Format
Submit To
Task 6a: Pre- Processor Programming and Testing
Final Code/ Executable
Yes To be proposed by contractor
Source code and compiled executable file
COR
Task 6b:
Documentation
Draft Document
No To be proposed by contractor
Microsoft Office (Word)
COR
Task 6b:
Documentation
Draft Example Files
No To be proposed by contractor
Input/Output Files
COR
Task 6b:
Documentation
Final Document
No To be proposed by contractor
Microsoft Office (Word)
COR
Task 6b:
Documentation
Final Example Files
Yes To be proposed by contractor
Input/Output Files
COR
Task 6b:
Documentation
508 Compliant Final Document
Yes 5 months Microsoft Office (Word) and
PDF.
TECHNICAL EXHIBIT 2
REQUIREMENTS FOR IMPLEMENTING SECTION 508 STANDARDS
NOTE: The following applies to all FHWA contracts and assistance agreements containing Information and Communication Technology (ICT) as a deliverable.
In addition to the work requirements specified in this statement of work, the Contractor shall ensure that all ICT deliverables meet the requirements of Section 508 of the Rehabilitation Act and the ICT Final Standards and Guidelines (508 Refresh) at 36 CFR Part 1194.
As defined in the 508 Refresh, at 36 CFR Part 1194, Appendix A, E103.4, ICT is “Information technology and other equipment, systems, technologies, or processes, for which the principal function is the creation, manipulation, storage, display, receipt, or transmission of electronic data and information, as well as any associated content. Examples of ICT include but are not limited to: computers and peripheral equipment; information kiosks and transaction machines;
telecommunications equipment; customer premises equipment; multifunction office machines;
software; applications; Web sites; videos; and, electronic documents.”
Section 508 requires that all electronic products prepared for the Federal Government be accessible to persons with disabilities, including those with vision, hearing, cognitive, and mobility impairments.
Applicable Standards:
Appendix A to Part 1194 – Section 508 of the Rehabilitation Act: Application and Scoping Requirements
Appendix B to Part 1194 – Section 255 of the Communications Act: Application and Scoping Requirements
Appendix C to Part 1194 – Functional Performance Criteria and Technical Requirements
Section 508 Refresh standards are available at: https://www.access-board.gov/ict/ The Contractor shall adhere to the terms and requirements in FHWA Form 4260 Section 508 Information and Communication Technology (ICT) Conformance Criteria for Section 508 conformance. The Conformance Criteria document does not need to be completed when submitting a deliverable.
PART IV
FEDERAL ACQUISITION REGULATION (FAR) AND TRANSPORTATION
ACQUISITION REGULATION (TAR) PROVISIONS AND CLAUSES
PROVISIONS
FAR & TAR PROVISIONS IN FULL TEXT
52.252-1 Solicitation Provisions Incorporated by Reference (Feb 1998)
This solicitation incorporates one or more solicitation provisions 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. The offeror is cautioned that the listed provisions may include blocks that must be completed by the offeror and submitted with its quotation or offer. In lieu of submitting the full text of those provisions, the offeror may identify the provision by paragraph identifier and provide the appropriate information with its quotation or offer. Also, the full text of a solicitation provision may be accessed electronically at https://www.acquisition.gov/far
(End of provision)
52.204-24 Representation Regarding Certain Telecommunications and Video Surveillance Services or Equipment (Nov 2021)
The Offeror shall not complete the representation at paragraph (d)(1) of this provision if the Offeror has represented that it "does not provide covered telecommunications equipment or services as a part of its offered products or services to the Government in the performance of any contract, subcontract, or other contractual instrument" in paragraph (c)(1) in the provision at 52.204-26, Covered Telecommunications Equipment or Services—Representation, or in paragraph (v)(2)(i) of the provision at 52.212-3, Offeror Representations and Certifications- Commercial Products or Commercial Services. The Offeror shall not complete the representation in paragraph (d)(2) of this provision if the Offeror has represented that it "does not use covered telecommunications equipment or services, or any equipment, system, or service that uses covered telecommunications equipment or services" in paragraph (c)(2) of the provision at 52.204-26, or in paragraph (v)(2)(ii) of the provision at 52.212-3.
(a) Definitions. As used in this provision—
Backhaul, covered telecommunications equipment or services, critical technology, interconnection arrangements, reasonable inquiry, roaming, and substantial or essential component have the meanings provided in the clause 52.204-25, Prohibition on Contracting for Certain Telecommunications and Video Surveillance Services or Equipment.
(b) Prohibition. (1) Section 889(a)(1)(A) of the John S. McCain National Defense Authorization Act for Fiscal Year 2019 (Pub. L. 115-232) prohibits the head of an executive agency on or after August 13, 2019, from procuring or obtaining, or extending or renewing a contract to procure or obtain, any equipment, system, or service that uses covered telecommunications equipment or services as a substantial or essential component of any system, or as critical technology as part of any system. Nothing in the prohibition shall be construed to—
(i) Prohibit the head of an executive agency from procuring with an entity to provide a service that connects to the facilities of a third-party, such as backhaul, roaming, or interconnection arrangements; or
(ii) Cover telecommunications equipment that cannot route or redirect user data traffic or cannot permit visibility into any user data or packets that such equipment transmits or otherwise handles.
(2) Section 889(a)(1)(B) of the John S. McCain National Defense Authorization Act for Fiscal Year 2019 (Pub. L. 115-232) prohibits the head of an executive agency on or after August 13, 2020, from entering into a contract or extending or renewing a contract with an entity that uses any equipment, system, or service that uses covered telecommunications equipment or services as a substantial or essential component of any system, or as critical technology as part of any system. This prohibition applies to the use of covered telecommunications equipment or services, regardless of whether that use is in performance of work under a Federal contract. Nothing in the prohibition shall be construed to—
(i) Prohibit the head of an executive agency from procuring with an entity to provide a service that connects to the facilities of a third-party, such as backhaul, roaming, or interconnection arrangements; or
(ii) Cover telecommunications equipment that cannot route or redirect user data traffic or cannot permit visibility into any user data or packets that such equipment transmits or otherwise handles.
(c) Procedures. The Offeror shall review the list of excluded parties in the System for Award Management (SAM) ( https://www.sam.gov) for entities excluded from receiving federal awards for "covered telecommunications equipment or services".
(d) Representation. The Offeror represents that—
Government in the performance of any contract, subcontract or other contractual instrument resulting from this solicitation. The Offeror shall provide the additional disclosure information required at paragraph (e)(1) of this section if the Offeror responds "will" in paragraph (d)(1) of this section; and
(2) After conducting a reasonable inquiry, for purposes of this representation, the Offeror represents that— equipment, system, or service that uses covered telecommunications equipment or services. The Offeror shall provide the additional disclosure information required at paragraph (e)(2) of this section if the Offeror responds "does" in paragraph (d)(2) of this section.
(e) Disclosures. (1) Disclosure for the representation in paragraph (d)(1) of this provision. If the Offeror has responded "will" in the representation in paragraph (d)(1) of this provision, the Offeror shall provide the following information as part of the offer:
(i) For covered equipment—
(A) The entity that produced the covered telecommunications equipment (include entity name, unique entity identifier, CAGE code, and whether the entity was the original equipment manufacturer (OEM) or a distributor, if known);
(B) A description of all covered telecommunications equipment offered (include brand; model number, such as OEM number, manufacturer part number, or wholesaler number; and item description, as applicable); and
(C) Explanation of the proposed use of covered telecommunications equipment and any factors relevant to determining if such use would be permissible under the prohibition in paragraph (b)(1) of this provision.
(ii) For covered services—
(A) If the service is related to item maintenance: A description of all covered telecommunications services offered (include on the item being maintained: Brand; model description, as applicable); or
(B) If not associated with maintenance, the Product Service Code (PSC) of the service being provided; and explanation of the proposed use of covered telecommunications services and any factors relevant to determining if such use would be permissible under the prohibition in paragraph (b)(1) of this provision.
(2) Disclosure for the representation in paragraph (d)(2) of this provision. If the Offeror has responded "does" in the representation in paragraph (d)(2) of this provision, the Offeror shall provide the following information as part of the offer:
(i) For covered equipment—
(A) The entity that produced the covered telecommunications equipment (include entity name, unique entity identifier, CAGE code, and whether the entity was the OEM or a distributor, if known);
(B) A description of all covered telecommunications equipment offered (include brand; model description, as applicable); and
(C) Explanation of the proposed use of covered telecommunications equipment and any factors relevant to determining if such use would be permissible under the prohibition in paragraph (b)(2) of this provision.
(ii) For covered services—
(A) If the service is related to item maintenance: A description of all covered telecommunications services offered (include on the item being maintained: Brand; model description, as applicable); or
(B) If not associated with maintenance, the PSC of the service being provided; and explanation of the proposed use of covered telecommunications services and any factors relevant to determining if such use would be permissible under the prohibition in paragraph (b)(2) of this provision.
1252.237-71 -- Certification of Data (Apr 2005)
NOTICE: The Secretary of Transportation has determined that this certification shall be retained in accordance with Section 4301(b)(1)(B)(i)(II) of the Federal Acquisition Reform Act (Public Law 104-106, 41 U.S.C. 425, note) and DOT Memorandum dated July 17, 1996.
(a) The offeror represents and certifies that to the best of its knowledge and belief, the information and/or data (e.g., company profile; qualifications; background statements;
brochures) submitted with its offer is current, accurate, and complete as of the date of its offer.
(b) The offeror understands that any inaccurate data provided to the Department of Transportation may subject the offeror, its subcontractors, its employees, or its representatives to: (1) prosecution for false statements pursuant to 18 U.S.C. 1001 and/or; (2) enforcement action for false claims or statements pursuant to the Program Fraud Civil Remedies Act of 1986, 31 U.S.C. 3801-3812 and 49 CFR Part 31 and/or; (3) termination for default under any contract resulting from its offer and/or; (4) debarment or suspension.
(c) The offeror agrees to obtain a similar certification from its subcontractors.
Signature: ____________________________________________ Date: ____________________________________________ Typed Name and Title: ___________________________________ Company Name:__________________________________ This certification concerns a matter within the jurisdiction of an agency of the United States and the making of a false, fictitious, or fraudulent certification may render the maker subject to prosecution under 18 U.S.C. 1001.
FAR & TAR PROVISIONS INCORPORATED BY REFERENCE
52.203-11 Certification and Disclosure Regarding Payments to Influence Certain
Federal Transactions (Sept 2007) 52.203-18 Prohibition on Contracting with Entities that Require Certain Internal
Confidentiality Agreements or Statements-Representation (Jan 2017)
52.204-7 System for Award Management (Oct 2018) 52.204-8 Annual Representations and Certifications (Mar 2023) 52.204-16 Commercial and Government Entity Code Reporting (Aug 2020) 52.204-17 Ownership or Control of Offeror (Aug 2020) 52.204-20 Predecessor of Offeror (Aug 2020) 52.204-22 Alternative Line Item Proposal (Jan 2017) 52.204-26 Covered Telecommunications Equipment or Services-Representation (Oct
2020) 52.209-2 Prohibition on Contracting with Inverted Domestic Corporations-
Representation (Nov 2015) 52.209-11 Representation by Corporations Regarding Delinquent Tax Liability or a
Felony Conviction under any Federal Law (Feb 2016) 52.212-1 Instructions to Offerors -- Commercial Items (Sept 2023) 52.212-3 Offeror Representations and Certifications -- Commercial Items (Now 2023) 52.222-22 Previous Contracts and Compliance Reports (Feb 1999) 52.222-25 Affirmative Action Compliance (Apr 1984) 52.225-25 Prohibition on Contracting With Entities Engaging in Certain Activities or
Transactions Relating to Iran—Representation and Certifications (Jun 2020) 1252.239-71 Information Technology Security Plan and Accreditation (Nov 2022)
End of Provisions
CLAUSES
FAR CLAUSES INCORPORATED BY REFERENCE
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…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .