Attachment 1 RFP 125353 Concept Feasibility Study Fairfax Circle 10.20.26.pdf

PDF 636 KB Posted

Attached to
Concept Feasibility Study, Fairfax Circle
Solicitation number
RFP-125353
Issued by
Fairfax County, Virginia

About this file

This Request for Proposal (RFP 125353) is issued by the City of Fairfax, Virginia Office of Procurement Services to solicit a qualified planning and engineering Architect/Engineer (A/E) team to conduct a concept feasibility study for the Fairfax Circle intersection. The primary deliverable is a comprehensive alternatives evaluation and recommended concept plan to redesign the Fairfax Circle intersection and associated transportation improvements to create a safer, more multimodal-friendly intersection that supports the vision of the Fairfax Circle Small Area Plan as a vibrant, mixed-use gateway to the city. The scope of work includes reviewing prior studies and plans, analyzing existing and projected traffic volumes, identifying conceptual alternatives beyond a no-build scenario, evaluating alternatives against specified metrics, coordinating robust community engagement, attending City Council work sessions, and developing a recommended alternative with detailed survey work and funding application materials. The optional pre-proposal conference is scheduled for October 22, 2026, at 1:00 P.M. EST with virtual attendance via Microsoft Teams. The questions deadline is October 29, 2026, at 2:00 P.M. EST, and proposals are due November 12, 2026, at 2:00 P.M. EST through the eVA Virginia Procurement website. All submissions must be electronic, and offerors must be registered and in active status on eVA. The contract will begin upon execution and terminate following completion of the concept feasibility study as authorized by the City. Contract amendments require approval by the City's Purchasing Agent. The contract administrator is David Kundid (David.kundid@fairfaxva.gov).

Fees for services shall be negotiated on an hourly basis, with compensation determined by mutual agreement between the City and the selected A/E considering the specificity of scope, estimated manhours for each discipline, and typical labor rates for required skill levels. Price adjustments may be requested a minimum of thirty days prior to the contract anniversary date, with rate increases permitted twelve months after the effective contract date subject to City approval. The A/E must carry professional liability insurance with minimum limits of either five percent of the estimated budget per claim or $500,000 per claim, whichever is greater, with maximum coverage of $5,000,000 per claim and $10,000,000 in the aggregate, and maintain such coverage for not less than five years after work completion. Evaluation of proposals will be based on four technical criteria: Qualifications and Past Involvement with Similar Projects (40 points), Proposed Methodology (40 points), Quality Assurance Plan (10 points), and Schedule (10 points), for a total of 100 points. The City intends to conduct individual discussions with two or more highly qualified offerors and will negotiate with the top-ranked offeror; if satisfactory terms cannot be reached at a fair and reasonable price, negotiations will proceed with subsequent ranked offerors. The A/E must be properly licensed and registered in Virginia, designate an A/E of Record, comply with all applicable codes and standards including AASHTO, VDOT, FHWA, and VMUTCD, and provide all deliverables in CAD and PDF formats. No set-asides are identified in this solicitation. Proposals must remain valid for 180 days, and all vendors must comply with E-Verify requirements if employing more than an average of 50 employees.

View the file

Other files

File Type Posted
Addendum 1, RFP 125353.pdf PDF
Attachment 2, Proposal Submission Form.docx DOCX document
RFP 125353 Pre-Proposal Attendance List Update 10.23.26.docx DOCX document
Attachment 0, Appendix A.pdf PDF

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

City of Fairfax, Virginia

Office of Procurement Services 10455 Armstrong Street

Fairfax, Virginia 22030

REQUEST FOR PROPOSAL

RFP Number: RFP 125353

Title Concept Feasibility Study, Fairfax Circle

Commodity code(s):

92517 – Civil Engineering 92546 – Geotechnical Engineering 92561 – Land Development and Planning/Engineering

Issue Date: October 9, 2026

Optional Pre-proposal Conference:

October 22, 2026, at 1:00 P.M. EST [See Section 6 Optional Pre-Proposal Conference – Registration is required to Attend]

Questions Deadline: October 29, 2026, at 2:00 P.M. EST

Due Date: November 12, 2026, at 2:00 P.M. EST

Contract Administrator: David Kundid David.kundid@fairfaxva.gov

ALL OFFERS MUST BE SUBMITTED ELECTRONICALLY VIA THE VIRGINIA PROCUREMENT

SITE WHICH CAN BE FOUND AT EVA.VIRGINIA.GOV. ANY ASSISTANCE SUBMITTING

PROPOSALS THROUGH THIS SYSTEM MUST BE DIRECTED SOLELY TO EVA

SUPPORT/HELPDESK.

• Your business must be eVA registered and in active status.

• Start by clicking the Register Now link on the eVA website eva.virginia.gov

The City of Fairfax does not discriminate against faith-based organizations in accordance with the Code of Virginia, § 2.2-4343.1 or against a bidder or offeror because of race, religion, color, sex, national origin, age, disability, or any other basis prohibited by state law relating to discrimination in employment in the performance of its procurement activity.

mailto:David.kundid@fairfaxva.gov https://eva.virginia.gov/ https://eva.virginia.gov/

RFP 125353

TABLE OF CONTENTS

1. PURPOSE:

2. CONTRACT TERM:

3. BACKGROUND:

4. SCOPE OF WORK: CONCEPT FEASIBILITY STUDY AND ASSESSMENT:

5. RFP Response:

6. OPTIONAL PREPROPOSAL CONFERENCE:

7. SUBMITTAL INSTRUCTIONS:

8. Proposal Preparation:

9. SPECIFIC PROPOSAL INSTRUCTIONS:

10. EVALUATION AND AWARD CRITERIA:

11. FEES:

12. PURCHASE ORDER REQUIREMENT:

13. ETHICS IN PUBLIC CONTRACTING:

14. DEBARMENT STATUS:

15. ANTITRUST:

16 MANDATORY USE OF CITY FORM AND TERMS AND CONDITIONS:

17. PAYMENT:

18. Unreasonable Charges:

19. PRECEDENCE OF TERMS:

20. QUALIFICATIONS OF OFFERORS:

21. CHANGES TO THE CONTRACT:

22. TAXES:

23. INSURANCE:

24. ANNOUNCEMENT OF AWARD:

25. AUTHORIZATION TO CONDUCT BUSINESS IN THE COMMONWEALTH:

26. ADDENDA:

27. PROPOSAL ACCEPTANCE PERIOD:

28. PRICES AND PRICE ADJUSTMENT:

29. METHOD OF ORDERING:

30. PERIOD FOR PERFORMANCE OF PURCHASE ORDERS:

31. DELAYS AND SUSPENSIONS:

32. COMPLIANCE WITH ALL LAWS:

33. E-VERIFY PROGRAM:

TABLE OF CONTENTS

34. PRIME CONTRACTOR RESPONSIBILITIES:

35. INVOICES AND PAYMENT:

FEASIBILITY ASSESSMENT AND CONCEPT SERVICES TERMS AND CONDITIONS:

1. LICENSE AND REGISTRATION:

2. A/E PF RECORD:

3. PROFESSIONAL SERVICES:

4. RELATIONSHIP OR ARCHITECT/ENGINEER TO CITY:

5. CODE AND REGULATORY COMPLIANCE:

6. A/E PROFESSIONAL LIABILITY INSURANCE:

7. ERRORS AND/OR OMISSIONS:

8. RECORDS RETENTION:

9. OWNERSHIP OF DOCUMENTS AND MATERIALS:

10. PAYMENTS TO THE ARCHITECT/ENGINEER:

11. RELEASE OF INFORMATION PERTAINING TO PROJECT CONCEPT:

12. QUALITY OF WORK:

13. STANDARDS FOR A/E SERVICES:

14. A/E BASIC SERVICES:

GENERAL TERMS AND CONDITIONS

1. PURPOSE:

The City of Fairfax is issuing this Request for Proposal (RFP) to seek a qualified planning and engineering A/E to conduct an alternatives evaluation and develop a recommended concept plan for the Fairfax Circle intersection and any associated transportation improvements.

The City of Fairfax has transformative goals for the Fairfax Circle Activity Center, with a desire for a redesigned Fairfax Circle intersection and multimodal network to complement the area’s transformation into a vibrant, mixed-use gateway to the City. The Fairfax Circle Small Area Plan (SAP) envisions this area as a sustainable mixed-use village to welcome people not just to shop but also to live, work, and thrive in an environmentally sensitive center.

The Fairfax Circle intersection, where Fairfax Boulevard, Routes 29/50 and Blenheim Boulevard meet, is a central feature in the Activity Center. However, as currently designed, it has both operational and safety problems and does not support the future goals envisioned in the SAP.

Fairfax Circle Activity Center’s transformation into a vibrant, mixed-use walkable district and a welcoming gateway to the city hinges on reconfiguring the Fairfax Circle intersection to accommodate all modes more safely and comfortably.

2. CONTRACT TERM:

The contract term will begin upon execution of the agreement, and terminate following the completion of the Concept Feasibility Study of the Fairfax Circle project as authorized by the City.

Contract Amendments shall be approved by the City’s Purchasing Agent.

3. BACKGROUND:

Background and Existing Conditions The Fairfax Circle Activity Center gets its name from the circular geometry of the major central intersection. Historically this intersection was a circular rotary but was converted in the early 1970s into a non-traditional “hamburger” circular intersection to better accommodate increasing traffic. The Fairfax Circle intersection today is sprawling, confusing to navigate, and intimidating for all users, including pedestrians, bicyclists, and automobile drivers.

Fairfax Circle’s location at the junction of three major regional roadways makes it a key intersection both within the City of Fairfax and in the region. Fairfax Boulevard and Route 29 are principal arterials within the I-66 corridor and carry substantial traffic volumes of approximately 30,000-35,000 vehicles per day. These routes provide access to I-66 and the Vienna Metrorail station to the north. Blenheim Boulevard, the intersection’s southern leg and arterial carrying up to 14,000 vehicles per day, provides access to Old Town Fairfax and George Mason University. The primary challenges posed by the intersection are listed below.

A. Automobile Driver Challenges

• Unusual configuration leads to driver confusion, distraction, abrupt lane changes and other conflict points such as frequent commercial driveways.

• Necessary turn restrictions do not align with the expectations of normal intersection configurations

• Concept includes merge areas that have been significantly constrained by later developments

B. Pedestrian & Bicycle Challenges

• Crossing the intersection is challenging and time-consuming due to long crossing distances, limited sight lines to destinations, and multi-stage crossings.

• Right turn slip lanes on each approach create additional crossings increasing pedestrian exposure to vehicular traffic and substantially increases crossing and waiting time.

• A lack of crosswalks on the north and south legs of the intersection forces pedestrians to follow a circuitous route.

• Current east-west crosswalks are located within the center of the circle, not around it

• There are no dedicated bicycle facilities through Fairfax Circle and bicyclists have to share narrow sidewalks with pedestrians or avoid the circle completely.

C. Transit Challenges

• Long distances between bus stops and crosswalks

• Long pedestrian travel times through the intersection complicates transfers

D. Safety Challenges

• Fairfax Circle has one of the highest crash incidences of any intersection in the City, with over 100 accidents since 2021.

• Analysis of crash reports suggests that the primary contributing factors include driver confusion over lane assignment, conflicts with turns into and out of driveways, and red-light running.

• There are 25 commercial driveways located within 300 feet of the intersection increasing potential conflict points

E. Prior Studies

There are several planning and transportation documents and projects that include this project area in their studies and recommendations.

Fairfax Circle Visioning and Multimodal Intersection Alternatives Study

In 2021, through technical assistance received from the Transportation and Land Use Connections Program, the City completed the Fairfax Circle Visioning and Multimodal Intersection Alternatives Study. The purpose of this study was to explore options for reimagining and reconfiguring the Fairfax Circle intersection. This study was a collaborative process led by City of Fairfax transportation planning staff with support from a consultant team. Engagement with the public and the City Council provided the project team with vital input at key points throughout the study process.

The study identified several overarching needs to improve multimodal safety and connectivity at the intersection.

1. Simplify the intersection to reduce confusion and improve safety.

2. Right-size the roadway infrastructure to provide safe and comfortable conditions for non-drivers.

3. Focus on the most vulnerable users through improvements to reduce crossing distances, install crossing facilities that align with pedestrian desire lines, and separate pedestrians from vehicular traffic.

https://portal2.fairfaxva.gov/Projects/Browse.aspx?id=704044&dbid=0&repo=cityoffairfax https://portal2.fairfaxva.gov/Projects/Browse.aspx?id=704044&dbid=0&repo=cityoffairfax

4. Ensure access to local businesses.

5. Create a sense of arrival through improved gateway treatments that convey the city’s identity and brand.

The study developed nine preliminary alternatives that were assessed against a high-level set of criteria that considered traffic operations, intersection footprint and implement ability.

Ultimately, the team refined the list and recommended three of those nine alternatives for further study: traditional intersection (with skew), roundabout with grade separation, and quadrant roadway intersection.

F. Fairfax Circle Small Area Plan

The Fairfax Circle Small Area Plan, adopted in July 2024, is an extension of the Comprehensive Plan that provides more specific guidance for both private development and public investment in the Fairfax Circle Activity Center. While Fairfax Circle is one of the current defining elements of the Activity Center, the plan recognizes that the intersection may need to be modified to improve safety and operations for all users. One of the four defining goals of the plan is to establish “a reinvented safe and memorable Fairfax Circle”. Through this goal, the Small Area Plan conceptualizes a future reconfiguration of the circle into a more standard four-way intersection with the caveat that a more detailed analysis will be needed to determine the actual future design.

While the Small Area Plan does not specifically recommend alternative traffic patterns as explored in the Fairfax Circle Visioning and Multimodal Intersection Alternatives Study, the Long- Term Transportation Vision in the plan incorporates a street network that could support such options.

The plan also includes specific design elements that should be incorporated with the goal of transforming Blenheim and Fairfax Boulevards into green boulevards.

The Small Area Plan also recognizes that a future intersection reconfiguration may result in a smaller footprint than that of the existing circle and suggests that excess right-of-way be used to incorporate landscaping and placemaking measures that reinforce the circular geometry that can continue to serve as a defining element for the Activity Center.

G. City of Fairfax 2035 Comprehensive Plan

The City of Fairfax 2035 Comprehensive Plan, last updated in October 2024, provides general guidance for the “physical development” of the City as required by the Code of Virginia. Also, in support of the Code of Virginia, the Comprehensive Plan includes a map and cost estimates for proposed transportation facility improvements. One of such “Transportation Policy and Project” recommendations is to “improve safety and connectivity for all users in and around Fairfax Circle”.

Estimated costs for this project are limited to study and analysis as estimates for constructions costs could vary significantly depending on the ultimate design scenario.

H. City of Fairfax Bicycle Plan The city’s bicycle master plan Bike Fairfax City established a vision for a network of low-stress bikeways, enabling residents of all ages and abilities to travel between neighborhoods and destinations. To support bicycling as a convenient and desirable option, the plan identifies a network of recommended bicycle facilities. The plan identifies the roads to and through Fairfax https://www.fairfaxva.gov/Property-Business/Development/City-Plans/Small-Area-Plans/Fairfax-Circle-Small-Area-Plan https://www.fairfaxva.gov/files/assets/city/v/1/development/documents/comprehensive-plan/2024-update-2035-comprehensive-plan_final-with-cover_condense.pdf https://www.fairfaxva.gov/Property-Business/Development/City-Plans/Bicycle-Transportation-Plan

Circle as needing “long term improvements”, which are higher volume and higher speed corridors requiring major investments. A specific facility design is not recommended in Fairfax Circle but based on the general guidance outlined in Bike Fairfax City, bicycle facilities that are physically separated from traffic support the vision of a low-stress network and aligns with the guidance in the FHWA Bikeway Selection Guide.

I. CUE TDP

The City is in the process of completing the CUE Transit Development Plan, which is a planning document for the City’s local bus system, CUE. The TDP evaluates the city’s transit goals, evaluates existing ridership patterns and unmet needs, and identifies ways to improve the CUE system to meet those needs. The draft TDP, which is anticipated to be finalized and adopted this fall, recommends a reconfiguration of the City’s two loop routes into three linear routes with increased frequencies. The proposed new routes will continue to travel through and have stops near Fairfax Circle.

J. Blenheim Boulevard Multimodal Improvements Project

The City has just started construction of the Blenheim Boulevard Multimodal Improvements Project, which is a $30M project to rebuild Blenheim Blvd between Layton Hall and Ridge Ave into a multimodal boulevard containing a two-way cycle track, sidewalks, outdoor public gathering spaces, gateway features, multimodal hubs with bikeshare and upgraded transit amenities, pedestrian-scale signage, lighting and landscaping. The roadway will remain one lane in each direction with the addition of turn pockets at select locations. The northern terminus of the improvements is Ridge Avenue. However, the expectation is that future improvements to Fairfax Circle will extend these improvements from Ridge Avenue through the circle and north to Route 29.

K. Data

The City has a variety of data available for this intersection that will be shared with the selected team including:

• Traffic Counts

• Pedestrian counts

• Bus Ridership

• Scooter Ridership

• Crash Data

L. Stormwater Management The Fairfax Circle Small Area Plan includes goals, the first of which is “A sustainable neighborhood linked to the Accotink Creek.” This section of the Plan provides high level guidance for future development of this area. For Fairfax Circle, the Small Area Plan includes guidance for open space and green fingers, with recommendations to utilize bioswales and rain gardens for stormwater management. Meeting state water quality and quantity standards through reduction of impervious surface and utilization of green infrastructure is preferred over other structural/proprietary Best Management Practices.

https://www.fairfaxva.gov/Property-Business/Development/City-Plans/CUE-Transit-Development-Plan https://www.fairfaxva.gov/Property-Business/Development/Projects/Blenheim-Blvd-Multimodal-Improvements https://www.fairfaxva.gov/Property-Business/Development/Projects/Blenheim-Blvd-Multimodal-Improvements

M. Urban Forest Master Plan – Green Streets The city’s Urban Forest Master Plan identifies trees as essential green infrastructure for creating healthier, more livable, and climate-resilient communities. The Fairfax Circle Activity Center, recognized in other city plans as an environmentally sensitive center, has significant stormwater and flooding challenges, the city’s lowest tree canopy coverage, the highest concentration of impervious surfaces, and the most pronounced urban heat island effect. The plan identifies embedding trees as green infrastructure into all city plans and projects as the community’s highest priority. Green street designs should provide adequate soil volume and planting space to support mature tree growth, prioritize native trees and plants, replace removed trees to achieve no net canopy loss, and use landscaping to manage stormwater while enhancing pedestrian comfort.

4. SCOPE OF WORK: CONCEPT FEASIBILITY STUDY AND ASSESSMENT

The City seeks a forward-thinking and creative multidisciplinary team of planners, engineers and environmental stewards to develop a preferred alternative for the Fairfax Circle intersection.

The primary goal of this project is to identify an innovative and context-sensitive concept that improves the safety for all users and maintains or improves the operation of the intersection. It is possible that improvements to this intersection will require the construction of, or improvements to, nearby roadways and/or intersections. The idea that potential additional roadways could relieve pressure from Fairfax Circle is conceptually outlined in the Fairfax Circle Visioning Study.

Key secondary goals include:

• Creating a human-scale, walkable and pedestrian-friendly environment

• Accommodating bicycle traffic through the continuation of the Blenheim Boulevard cycle track or similar facility

• Creating a sense of place that draws on the Fairfax Circle history

• Minimizing environmental impacts to existing features

• Maximizing the use of landscaping and other natural features in placemaking

• Supporting local business access and future development goals of the Small Area Plan

In general, the following items will need to be performed by the consulting A/E.

1. Review of prior studies and plans, including public input received during the Visioning Study

2. Analyze existing, baseline growth, and projected future (YEAR) traffic volumes to determine appropriate facility needs.

3. Identify non-vehicular needs for the intersection

4. Identify conceptual alternatives for intersection improvement in addition to a no-build scenario

Refer to the Fairfax Circle Visioning Study. Options for the concepts do not need to be limited to those considered in that effort.

5. Evaluate and rank each of the proposed concepts based on a set of metrics that may include vehicular and non-vehicular traffic levels of service, right-of-way impacts, traffic safety, pedestrian and bicyclist safety, construction cost, constructability, maintenance costs, environmental impacts, conformance with the adopted Small Area Plan vision, and other parameters deemed applicable.

6. Coordinate and lead robust community engagement.

https://www.fairfaxva.gov/files/assets/city/v/1/sustainability/documents/urban-forest-master-plan-december-2025.pdf

7. Attend and provide all needed drawings and other materials for City Council work sessions and community engagement meetings.

8. Based on the evaluation and community/City Council input, develop a recommended alternative that meets the primary and secondary project goals.

9. Complete additional detail on the recommended alternative including detailed survey to support development of a funding application(s).

10. Prepare all deliverables including plans, cost estimate and any other required items for funding application(s).

This scope of work concludes if/once a recommended alternative is endorsed by the City Council and the City submits the project for funding. However, the city preserves the option to utilize this contract to advance project design further (from 10% up to 30%).

A separate solicitation will occur to select a consultant for project delivery.

All alternatives shall be designed in accordance with all applicable city and state standards including AASHTO, VDOT & FHWA Highway Design Standards, and VMUTCD.

Design Vehicles should include the entire multi-modal range from pedestrians/scooters to WB 67 tractor-trailer trucks.

5. RFP RESPONSE:

In order to be considered for selection, offerors must submit a complete response to this RFP.

6. OPTIONAL PRE-PROPOSAL CONFERENCE:

An Optional Pre-Proposal Conference will be held virtually on October 22, 2026, at 1:00 P.M. Eastern Standard Time.

A. Attendance at the RFP Pre-Proposal Conference is optional, and registration is required.

B. Offeror shall attend virtually via Microsoft Teams. To participate virtually, contact David Kundid at email address David.kundid@fairfaxv.gov.

The purpose of this conference is to allow potential Offerors an opportunity to present questions and obtain clarification relative to any facet of this solicitation.

7. SUBMITTAL INSTRUCTIONS:

Sealed Proposals shall be received and time stamped online through the eVA website, no later than date and time listed on cover page (Proposal Closing”). Offerors are responsible for ensuring its submission prior to Proposal Closing. The time a Proposal is received shall be determined by the time stamp on the Proposal receipt by the time clock on the eVA Sourcing and Contracting website. The City of Fairfax is not responsible for any technical difficulties which may result in the Offerors response not uploading in time, or any responses that are not properly uploaded. The City will not receive any proposals in person. Any paper submissions received will be not be considered and will be returned, unopened, to the offeror. Proposals received after the Closing date/time shall not be considered.

mailto:David.kundid@fairfaxv.gov

Proposals should be as thorough and detailed as possible so that the City may evaluate the Offeror’s capabilities to provide the required services. Offerors are required to submit the following items as a complete proposal:

8. Proposal Preparation:

A. Proposals shall be signed by an authorized representative of the offeror. All information requested should be submitted. Failure to submit all information requested may result in the city requiring prompt submission of missing information and/or giving a lowered evaluation of the proposal. Proposals which are substantially incomplete or lack key information may be rejected.

Mandatory requirements are those required by law or regulation or are such that they cannot be waived and are not subject to negotiation.

B. Proposals should be prepared simply and economically, providing a straightforward, concise description of capabilities to satisfy the requirements of the RFP. Emphasis should be placed on completeness and clarity of content.

C. Proposals should be organized in the order in which the requirements are presented in the RFP.

All pages of the proposal should be numbered. Each paragraph in the proposal should reference the paragraph number of the corresponding section of the RFP. If a response covers more than one page, the paragraph number and subletter should be repeated at the top of the next page.

The proposal should contain a table of contents which cross-references the RFP requirements.

Information which the offeror desires to present that does not fall within any of the requirements of the RFP should be inserted at an appropriate place or be attached at the end of the proposal and designated as additional material. Proposals that are not organized in this manner risk elimination from consideration if the evaluators are unable to find where the RFP requirements are specifically addressed.

D. As used in this RFP, the terms "must", "shall", "should" and “may” identify the criticality of requirements. "Must" and "shall" identify requirements whose absence will have a major negative impact on the suitability of the proposed solution. Items labeled as "should" or “may” are highly desirable, although their absence will not have a large impact and would be useful, but are not necessary. Depending on the overall response to the RFP, some individual "must" and "shall" items may not be fully satisfied, but it is the intent to satisfy most, if not all, "must" and "shall" requirements. The inability of an Offeror to satisfy a "must" or "shall" requirement does not automatically remove that Offeror from consideration; however, it may seriously affect the overall rating of the Offerors’ proposal.

E. Ownership of all data, materials, and documentation originated and prepared for the City pursuant to the RFP shall belong exclusively to the City and be subject to public inspection in accordance with the Virginia Freedom of Information Act. Trade secrets or proprietary information submitted by an offeror shall not be subject to public disclosure under the Virginia Freedom of Information Act; however, the offeror must invoke the protections of § 2.2-4342F of the Code of Virginia, in writing, either before or at the time the data or other material is submitted.

The written notice must specifically identify the data or materials to be protected and state the reasons why protection is necessary. The classification of an entire proposal document or prequalification application, line item prices, and/or total proposal prices as proprietary or trade secrets is not acceptable and will result in rejection of the proposal. If, after being given reasonable time the offeror refuses to withdraw an entire classification designation, the proposal will be rejected.

F. Based on the results of the preliminary evaluation, the highest rated offeror(s) may be invited by the Purchasing Agent to make oral presentations to the evaluation committee. This committee will then conduct a final evaluation of the proposals.

G. The City may cancel this RFP at or reject proposals at any time prior to an award, and is not required to furnish a statement of the reasons why a particular proposal was not deemed to be the most advantageous.

H. The City reserves the right to (i) negotiate any and all elements of the RFP, (ii) require supplemental statements of information from any Respondent, (iii) extend the deadline for submission of Proposals, (iv) request additional information or clarification of information provided in any Proposal without changing the terms of the RFP, (v) award this project in whole or in part to a vendor other than the highest scoring vendor based on the determination of the best overall value and/or fit for the City.

9. SPECIFIC PROPOSAL INSTRUCTIONS:

Any information provided in the Proposal is subject to consideration for consideration, evaluation, and scoring. The Offerors’ responses to the listed Exhibits shall be scored in accordance with their Proposal.

Offerors are required to submit the following items as a complete proposal:

Offeror shall return the RFP cover sheet, completed response to the Exhibits, and all addenda acknowledgments, if any, signed and filled out as required.

SECTION 1: Table of Contents

The Table of Contents shall indicate the material included by Section.

SECTION 2: Proposal Form and RFP Attachments Proposal Form must be fully completed and signed and submitted or the proposal may be deemed non-responsive. Include RFP Attachments properly completed; to include State Corporation Commission Form: Required of all offerors pursuant to Title 13.1 or Title 50.

SECTION 3: TECHNICAL PROPOSAL

Exhibit 1 – Qualifications and Past Involvement with Similar Projects (Technical Proposal)

• Identify the proposed team and each person’s qualifications for their assigned role. Preference given to a team with a highly experienced hands-on project manager who has both planning and engineering technical experience as well as the ability to communicate effectively with a variety of stakeholders. Preference also given to teams that demonstrate the ability to develop innovative context-sensitive traffic engineering solutions. Limit of five pages. Include resumes as an appendix.

• Identify example project(s) that demonstrate each primary team member’s prior experience on a similar project(s). Limit of five examples and ten pages.

• Identify example projects where the proposed team as a partial or complete group have worked together on a similar project(s). Preference will be given to teams that have successfully worked together on a similarly complex planning and engineering project. Limit of three examples and six pages.

Each example provided must clearly identify the proposed team member’s role and what elements of the example project are aligned with the city’s project.

Exhibit 2 – Proposed Methodology (Technical Proposal)

• Provide a detailed work plan that describes all tasks and deliverables determined to be necessary to accomplish the project. The work plan shall define resources needed for each task and which staff persons will complete the project element tasks. The methodology should show clarity of thought and process, and attention to the required elements described above. Limit of five (5) pages.

Exhibit 3 – Quality Assurance Plan (Technical Proposal)

• Provide an explanation of the team’s plan to provide high-quality interim draft and final work products to the city. Explain specifically how this process will work and who will manage it. Limit of two (2) pages.

Exhibit 4 – Schedule (Technical Proposal)

• Provide a timeline depicting the sequence and duration of tasks that account for City Council scheduling (no meetings in August and limited meetings in November and December), public engagement, City review. Include a list of deliverables and a proposed delivery schedule. Limit of two (2) pages.

10. EVALUATION AND AWARD CRITERIA:

Evaluation Committee The City shall use an evaluation committee to conduct a comprehensive, fair, and impartial review and evaluation of the Offeror’s Technical Proposal.

RFP Scoring The evaluation committee will fully evaluate and score all Responsive Proposals submitted by Responsible Offerors in accordance with Section 9. The point values assigned to each section of the evaluation criteria are listed below.

Exhibit Number Category Points

1 Qualifications and Past Involvement with Similar Projects 40

2 Proposed Methodology 40

3 Quality Assurance Plan 10

4 Schedule 10

For professional services, the public body shall engage in individual discussions with two or more offerors deemed fully qualified, responsible and suitable on the basis of initial responses and with emphasis on professional competence, to provide the required services. Repetitive informal interviews shall be permissible. The offerors shall be encouraged to elaborate on their qualifications and performance data or staff expertise pertinent to the proposed project, as well as alternative concepts. In addition, offerors shall be informed of any ranking criteria that will be used by the public body in addition to the review of the professional competence of the offeror. The Request for Proposal shall not, however, request that offerors furnish estimates of man-hours or cost for services. At the discussion stage, the public body may discuss nonbinding estimates of total project costs, including, but not limited to, life-cycle costing, and where appropriate, nonbinding estimates of price for services. In accordance with § 2.2-4342, proprietary information from competing offerors shall not be disclosed to the public or to competitors. For architectural or engineering services, the public body shall not request or require offerors to list any exceptions to proposed contractual terms and conditions, unless such terms and conditions are required by statute, regulation, ordinance, or standards developed pursuant to § 2.2-1132, until after the qualified offerors are ranked for negotiations. At the conclusion of discussion, outlined in this subdivision, on the basis of evaluation factors published in the Request for Proposal and all information developed in the selection process to this point, the public body shall select in the order of preference two or more offerors whose professional qualifications and proposed services are deemed most meritorious.

Negotiations shall then be conducted, beginning with the offeror ranked first. If a contract satisfactory and advantageous to the public body can be negotiated at a price considered fair and reasonable and pursuant to contractual terms and conditions acceptable to the public body, the award shall be made to that offeror. Otherwise, negotiations with the offeror ranked first shall be formally terminated and negotiations conducted with the offeror ranked second, and so on until such a contract can be negotiated at a fair and reasonable price.

Proprietary information from competing Offerors will not be disclosed to the public or to competitors, provided such information is duly marked as "Proprietary Information" by the Offeror and the designation is justified as required by Section 2.2-4342, Code of Virginia, as revised.

11. FEES

The fee for services shall be negotiated on an hourly basis considering the specificity of the Scope of Services required, the estimated manhours required for each level/discipline and the typical labor rates for the various skill levels required for the work. A fee schedule will be negotiated as outlined in paragraph 10.

12. PURCHASE ORDER REQUIREMENT:

City purchases are authorized only if the city issues a Purchase Order in advance of the transaction, indicating that the city has sufficient funds to pay for the purchase. If the Contractor provides goods or services without a city purchase order, it does so at its own risk and expense. The city is not liable for payment for any purchases made by its employees that are not authorized by the City Purchasing Agent.

https://law.lis.virginia.gov/vacode/2.2-4342/ https://law.lis.virginia.gov/vacode/2.2-1132/

13. ETHICS IN PUBLIC CONTRACTING:

By submitting their proposals, offerors certify that their proposals are made without collusion or fraud and that they have not offered or received any kickbacks or inducements from any other offeror, supplier, manufacturer or subcontractor in connection with their proposal, and that they have not conferred on any public employee having official responsibility for this procurement transaction any payment, loan, subscription, advance, deposit of money, services or anything of more than nominal value, present or promised, unless consideration of substantially equal or greater value was exchanged.

14. DEBARMENT STATUS:

By participating in this procurement, the vendor certifies that they are not currently debarred by the City of Fairfax from submitting a response for the type of goods and/or services covered by this solicitation. Vendor further certifies that they are not debarred from filling any order or accepting any resulting order, or that they are an agent of any person or entity that is currently debarred by the City of Fairfax.

If a vendor is created or used for the purpose of circumventing a debarment decision against another vendor, the non-debarred vendor will be debarred for the same time period as the debarred vendor.

15. ANTITRUST:

By entering into a contract, the contractor conveys, sells, assigns, and transfers to the City of Fairfax all rights, title and interest in and to all causes of action it may now have or hereafter acquire under the antitrust laws of the United States and the Commonwealth of Virginia, relating to the particular goods or services purchased or acquired by the City of Fairfax under said contract.

16. MANDATORY USE OF CITY FORM AND TERMS AND CONDITIONS:

Failure to submit a proposal on the official City form provided for that purpose may be a cause for rejection of the proposal. Modification of or additions to the General Terms and Conditions of the solicitation may be cause for rejection of the proposal; however, the City reserves the right to decide, on a case by case basis, in its sole discretion, whether to reject such a proposal.

17. PAYMENT:

A. Invoices for items ordered, delivered and accepted shall be submitted by the contractor directly to the payment address shown on the purchase order/contract. All invoices shall show the City purchase order number.

B. Any payment terms requiring payment in less than 30 days will be regarded as requiring payment 30 days after invoice or delivery, whichever occurs last. This shall not affect offers of discounts for payment in less than 30 days, however.

18. UNREASONABLE CHARGES:

Under certain emergency procurements and for most time and material purchases, final job costs cannot be accurately determined at the time orders are placed. In such cases, contractors should be put on notice that final payment in full is contingent on a determination of reasonableness with respect to all invoiced charges. Charges which appear to be unreasonable will be resolved in accordance with Code of Virginia, § 2.2-4363 and -4364. Upon determining that invoiced charges are not reasonable, the City shall notify the contractor of defects or improprieties in invoices within fifteen

(15) days as required in Code of Virginia, § 2.2-4351.

19. PRECEDENCE OF TERMS:

The following General Terms and Conditions VENUE, ANTI-DISCRIMINATION, OFFICIALS NOT TO BENEFIT, IMMIGRATION REFORM AND CONTROL ACT OF 1986, DEBARMENT STATUS, ANTITRUST, MANDATORY TERMS AND CONDITIONS, CLARIFICATION OF TERMS, PAYMENT shall apply in all instances. In the event there is a conflict between any of the other General Terms and Conditions (Appendix A) and any Special Terms and Conditions in this solicitation, the Special Terms and Conditions shall apply.

20. QUALIFICATIONS OF OFFERORS:

The City may make such reasonable investigations as deemed proper and necessary to determine the ability of the offeror to perform the services/furnish the goods and the offeror shall furnish to the City all such information and data for this purpose as may be requested. The City reserves the right to inspect offeror’s physical facilities prior to award to satisfy questions regarding the offeror’s capabilities. The City further reserves the right to reject any proposal if the evidence submitted by, or investigations of, such offeror fails to satisfy the City that such offeror is properly qualified to carry out the obligations of the contract and to provide the services and/or furnish the goods contemplated therein.

21. CHANGES TO THE CONTRACT:

Changes can be made to the contract in any of the following ways:

A. The parties may agree in writing to modify the terms, conditions, or scope of the contract. Any additional goods or services to be provided shall be of a sort that is ancillary to the contract goods or services, or within the same broad product or service categories as were included in the contract award. Any increase or decrease in the price of the contract resulting from such modification shall be agreed to by the parties as a part of their written agreement to modify the scope of the contract.

B. The Purchasing Agent may order changes within the general scope of the contract at any time by written notice to the contractor. The contractor shall comply with the notice upon receipt, unless the contractor intends to claim an adjustment to compensation, schedule, or other contractual impact that would be caused by complying with such notice, in which case the contractor shall, in writing, promptly notify the Purchasing Agent of the adjustment to be sought, and before proceeding to comply with the notice, shall await the Purchasing Agent's written decision afA/Eing, modifying, or revoking the prior written notice. If the Purchasing Agent decides to issue a notice that requires an adjustment to compensation, the contractor shall be compensated for any additional costs incurred as the result of such order and shall give the Purchasing Agent a credit for any savings. Said compensation shall be determined by mutual agreement between the parties in writing.

22. TAXES:

https://www.fairfaxva.gov/home/showpublisheddocument/22645/638452373501830000

Sales to the City of Fairfax are normally exempt from State sales tax. State sales and use tax certificates of exemption, Form ST-12, will be issued upon request. Deliveries against this contract shall usually be free of Federal excise and transportation taxes.

23. INSURANCE:

By signing and submitting a bid or proposal under this solicitation, the offeror certifies that if awarded the contract, it will have the following insurance coverage at the time the contract is awarded. For construction contracts, if any subcontractors are involved, the subcontractor will have workers’ compensation insurance in accordance with §§ 2.2-4332 and 65.2-800 et seq. of the Code of Virginia.

The offeror further certifies that the contractor and any subcontractors will maintain these insurance coverages during the entire term of the contract and that all insurance coverage will be provided by insurance companies authorized to sell insurance in Virginia by the Virginia State Corporation Commission.

MINIMUM INSURANCE COVERAGES AND LIMITS:

A. Workers’ Compensation - Statutory requirements and benefits. Coverage is compulsory for employers of three or more employees, to include the employer. Contractors who fail to notify the City of increases in the number of employees that change their workers’ compensation requirements under the Code of Virginia during the course of the contract shall be in noncompliance with the contract.

B. Employer’s Liability - $1, 000,000.

C. Commercial General Liability - $1,000,000 per occurrence and $2,000,000 in the aggregate.

Commercial General Liability is to include bodily injury and property damage, personal injury and advertising injury, products and completed operations coverage. The City of Fairfax shall be added as an additional insured to the policy by an endorsement.

24. ANNOUNCEMENT OF AWARD:

Upon the award or the announcement of the decision to award a contract as a result of this solicitation, the purchasing agency will publicly post such notice on the eVA VBO (www.eva.virginia.gov) for a minimum of 10 days.

25. AUTHORIZATION TO CONDUCT BUSINESS IN THE COMMONWEALTH:

A contractor organized as a stock or nonstock corporation, limited liability company, business trust, or limited partnership or registered as a registered limited liability partnership shall be authorized to transact business in the Commonwealth as a domestic or foreign business entity if so required by Title

13.1 or Title 50 of the Code of Virginia or as otherwise required by law. Any business entity described above that enters into a contract with a public body pursuant to the Virginia Public Procurement Act shall not allow its existence to lapse or its certificate of authority or registration to transact business in the Commonwealth, if so required under Title 13.1 or Title 50, to be revoked or cancelled at any time during the term of the contract. A public body may void any contract with a business entity if the business entity fails to remain in compliance with the provisions of this section.

http://www.eva.state.va.us/

26. ADDENDA:

Offerors are reminded that changes to the solicitation, in the form of addenda, are often issued between the issue date and within five (5) days before the due date. All addenda shall be signed and submitted and must accompany the proposal.

Notice of addenda will be posted on eVA and the City’s current solicitation webpage. It is the offeror’s responsibility to monitor these sites for any changes.

27. PROPOSAL ACCEPTANCE PERIOD:

Any proposal submitted in response to this solicitation shall be valid for 180 days. At the end of the acceptance period, the proposal may be withdrawn at the written request of the offeror. If the proposal is not withdrawn at that time, it remains in effect until an award is made or the solicitation is cancelled.

28. PRICES AND PRICE ADJUSTMENT:

Cost proposals shall be in the form of a firm hourly rate for each item during the contract period.

Contractor shall request approval for a price increase a minimum of thirty (30) days prior to the Contract anniversary date by notifying the purchasing office. A rate increase may be considered twelve (12) months after the effective date of the contract. The City reserves the right to approve or deny a rate increase. Any approved price changes shall be effective on the agreed upon effective date of the pricing change. In order to receive approval, the contractor shall document the amount and proposed effective date of any general change in the price of there services. Documentation shall be supplied with the contractor’s request for increase which will: (1) verify that the requested price increase is general in scope and not applicable just to the City; and (2) verify the amount or percentage of increase which is being passed on to the contractor by the contractor’s suppliers.

The contractor shall fill all purchase orders received prior to the effective date of the price adjustment at the old contract prices. The contractor is further advised that decreases which affect their services are required to be communicated immediately to the purchasing office.

29. METHOD OF ORDERING:

The City will place orders with a Purchase Order. The purchase order indicates that sufficient funds have been obligated as required by Title 15.2-1238 of the Code of Virginia. Performance under this contract is not to begin until receipt of the purchase order or other notification to proceed by the Purchasing Agent and/or City department. Purchasing charge cards offer the City the opportunity to streamline their procedures for procuring and paying for small dollar goods and/or services. Bidders responding to this solicitation should note that acceptance of payment by purchase card is an optional method of ordering.

30. PERIOD FOR PERFORMANCE OF PURCHASE ORDERS:

To be valid, a purchase order issued under this Contract must be issued during the term of the Contract. The period specified for performance of the purchase order may extend past the term of the Contract. If a notice terminating this Contract is issued, the notice shall be construed as applying only to the Contract and not to any existing purchase order, unless the notice expressly states the intent to terminate the purchase order.

31. DELAYS AND SUSPENSIONS:

The City may direct the Contractor, in writing, to suspend, delay, or interrupt all or any part of the work of this contract for the period of time deemed appropriate for the convenience of the City. The City will extend the Contractor’s time of completion by a period of time that in the discretion of the Purchasing Agent is reasonably suited for completion of work. The City may further amend the contract by mutual agreement for any increase in the cost of performance of the contract (excluding profit) resulting from the delay or suspension of the contract. No adjustment shall be made under this clause for any delay or interruption resulting from any other cause, including the fault or negligence of the Contractor.

32. COMPLIANCE WITH ALL LAWS:

Contractor shall comply with all federal, state, and local statutes, ordinances, and regulations now in effect or hereafter adopted, in the performance of scope of work set forth herein. Contractor represents that it possesses all necessary licenses and permits required to conduct its business and will acquire any additional licenses and permits necessary for performance of this contract prior to the initiation of work. The Contractor further expressly represents that it is a corporation, partnership, or limited liability company that it is in good standing in the City of Fairfax and will remain in good standing throughout the term of this contract.

33. E-VERIFY PROGRAM:

Pursuant to Code of Virginia, §2.2-4308.2., any employer with more than an average of 50 employees for the previous 12 months entering into a contract in excess of $50,000 with the City of Fairfax to perform work or provide services pursuant to such contract shall register and participate in the E- Verify program to verify information and work authorization of its newly hired employees performing work pursuant to such public contract. Any such employer who fails to comply with these provisions shall be debarred from contracting with the City of Fairfax for a period up to one year. Such debarment shall cease upon the employer’s registration and participation in the E-Verify program. If requested, the employer shall present a copy of their Maintain Company page from E-Verify to prove that they are enrolled in E-Verify.

34. PRIME CONTRACTOR RESPONSIBILITIES:

The contractor shall be responsible for completely supervising and directing the work under this contract and all subcontractors that he may utilize, using his best skill and attention. Subcontractors who perform work under this contract shall be responsible to the prime contractor. The contractor agrees that he is as fully responsible for the acts and omissions of his subcontractors and of persons employed by them as he is for the acts and omissions of his own employees.

35. INVOICES AND PAYMENT:

INVOICES: All invoices shall be rendered promptly to the City of Finance, Accounts Payable, 10455 Armstrong Street, Fairfax VA or accountspayable@fairfaxva.gov after all goods and/or services covered by the invoice have been provided. No invoice may include any cost other than those identified in the Order referencing the Contract.

PAYMENT: Payment will be made within thirty (30) days after receipt of a valid invoice for all goods and/or services received and accepted.

mailto:accountspayable@fairfaxva.gov

FEASIBILITY ASSESSMENT AND CONCEPT SERVICES TERMS AND CONDITIONS

1. LICENSE AND REGISTRATION

Persons providing architectural and/or engineering services shall be properly registered and licensed in Virginia as required by DPOR through the APELSCIDLA Board, and, if incorporated, the State Corporation Commission. Professional corporations shall obtain a Certificate of Authority as required by Code of Virginia, § 13.1-549. Other business entities shall register with DPOR as required by Code of Virginia,§ 54.1-411, as amended.

The individual Architect or Engineer responsible for the control and supervision of each discipline shall be at all times licensed in the Commonwealth of Virginia and shall affix his or her seal to those documents for which he or she is responsible.

2. A/E OF RECORD

The A/E shall designate an A/E of Record.

3. PROFESSIONAL SERVICES

The…

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 .