Richmond Metro Procurement, Contracting, and Vendor Opportunities

Public transit authorities operate under procurement frameworks that differ substantially from private-sector purchasing. Richmond Metro's contracting process governs how the authority acquires goods, services, construction, and professional expertise — from bus maintenance parts to capital infrastructure design. This page covers the definition and scope of Richmond Metro's procurement function, the procedural mechanics vendors encounter, common contract scenarios, and the decision boundaries that determine which procurement pathway applies to a given engagement.

Definition and scope

Procurement at a public transit authority is the structured, rules-governed process by which the agency acquires goods, services, and construction while remaining accountable to public funds. Richmond Metro's procurement function is shaped by overlapping federal and state requirements: federally funded projects are subject to the procurement standards codified at 49 CFR Part 18 (Uniform Administrative Requirements for Grants) and further governed by FTA Circular 4220.1F, the Federal Transit Administration's third-party contracting guidance. State-level requirements derive from the Virginia Public Procurement Act (Virginia Code § 2.2-4300 et seq.), which establishes competitive procurement as the default method for all public bodies in the Commonwealth.

The scope of Richmond Metro's procurement authority covers four broad categories:

1. Goods and commodities — fleet components, fuel, uniforms, office supplies, and maintenance materials
2. Professional services — engineering, planning, legal, financial advisory, and information technology consulting
3. Construction and capital works — station construction, track or roadway improvements, facility upgrades tied to the capital projects program
4. Operations-related services — security services, janitorial contracts, and contracted maintenance support

Contracts funded in whole or in part by federal grants must comply with FTA requirements, including Buy America provisions under 49 U.S.C. § 5323(j), which mandate that steel, iron, and manufactured products used in FTA-funded projects be produced in the United States.

How it works

The procurement cycle at Richmond Metro follows a sequential process aligned with both FTA guidance and the Virginia Public Procurement Act:

1. Needs identification — A department identifies a requirement and submits an internal requisition with a specification or scope of work.
2. Procurement method determination — The procurement office classifies the purchase by dollar threshold and complexity to assign the appropriate competitive method.
3. Solicitation issuance — The authority publishes either an Invitation for Bids (IFB), a Request for Proposals (RFP), or a Request for Qualifications (RFQ), depending on the contract type.
4. Vendor response period — Respondents submit bids or proposals within the advertised window, typically a minimum of 14 calendar days for routine procurements, longer for complex capital contracts.
5. Evaluation and award — A selection committee scores proposals against pre-published criteria; IFBs award to the lowest responsive, responsible bidder.
6. Contract execution — Both parties execute a written contract; federally funded contracts include mandatory FTA clauses covering equal employment opportunity, Davis-Bacon wage rates, and audit access.
7. Performance monitoring and closeout — Contract administration staff track deliverables, process invoices, and document final acceptance.

Richmond Metro posts active solicitations through eVA, Virginia's statewide electronic procurement portal (eva.virginia.gov), which is the primary channel for vendor registration and bid submission.

The annual budget and federal and state funding streams directly determine the volume and type of procurement activity in any fiscal year.

Common scenarios

Preventive maintenance and fleet parts contracts are among the highest-frequency procurements. Because Richmond Metro operates a mixed fleet, parts procurement often runs under indefinite-delivery/indefinite-quantity (IDIQ) contracts with a defined ceiling value, allowing the authority to order against a standing contract rather than re-solicit for each purchase.

Design-build vs. design-bid-build for capital projects: These two delivery models represent the most consequential procurement decision in capital infrastructure. Under design-bid-build, the authority contracts separately with a designer, then solicits construction bids against completed drawings — preserving maximum price competition but extending the schedule. Under design-build, a single contractor delivers both design and construction under one contract, compressing the schedule but requiring the authority to evaluate qualifications and price simultaneously. FTA permits both models; the Virginia Public Procurement Act authorizes design-build for public bodies under Virginia Code § 2.2-4381 et seq.

Disadvantaged Business Enterprise (DBE) participation applies to all FTA-assisted contracts. The U.S. Department of Transportation's DBE program, governed by 49 CFR Part 26, requires transit agencies receiving FTA funds to set annual DBE participation goals and document good-faith efforts to engage certified minority- and women-owned firms. Vendors responding to federally funded solicitations must address DBE requirements explicitly in their submissions.

Professional services and sole-source exceptions: When only one qualified provider exists for a specialized service — such as proprietary software maintenance for a specific fare collection system — procurement rules permit a sole-source justification. This requires written documentation, supervisory approval, and, for federally funded contracts, FTA concurrence above certain dollar thresholds.

Decision boundaries

The procurement method applied to any given purchase depends on two primary variables: dollar value and the measurability of the requirement.

The Brooks Act (40 U.S.C. §§ 1101–1104) prohibits price competition for architecture and engineering services on federally funded projects; selection must be based on qualifications alone, with price negotiated after ranking.

Protests — formal challenges to an award decision — are resolved under procedures established in the Virginia Public Procurement Act and, for federally funded contracts, subject to FTA oversight.

For a full picture of Richmond Metro's public-facing operations and authority structure, the Richmond Metro Authority home page provides the foundational organizational context within which procurement activities are conducted.

References

• Federal Transit Administration Circular 4220.1F — Third-Party Contracting Guidance
• 49 CFR Part 26 — Participation by Disadvantaged Business Enterprises in Department of Transportation Financial Assistance Programs
• 49 CFR Part 18 — Uniform Administrative Requirements for Grants and Cooperative Agreements to State and Local Governments
• Virginia Public Procurement Act — Virginia Code § 2.2-4300 et seq.
• Brooks Act — 40 U.S.C. §§ 1101–1104
• 49 U.S.C. § 5323(j) — Buy America Requirements
• eVA — Virginia's Electronic Procurement Portal