Baltimore Tech & Data Procurement Rules
Baltimore, Maryland requires city agencies and vendors to follow established procurement procedures for technology and data contracts. This guide explains how procurement officials evaluate tech and data purchases, common contract structures, compliance expectations for privacy and security, and the main routes for challenge and appeal. It is intended for vendors, contracting officers and in-house counsel working with Baltimore municipal contracts.
Penalties & Enforcement
Enforcement responsibility for procurement compliance rests with the City of Baltimore Bureau of Purchasing and related finance and legal offices; official procedural rules and the ordinance framework are published by the city Baltimore City Bureau of Purchasing[1] and in the consolidated city code Baltimore City Code[2]. Specific monetary fine amounts for procurement violations are not specified on the cited pages.
- Fine amounts: not specified on the cited page; see the City Code for statutory penalties and the Purchasing Bureau for administrative remedies.[2]
- Escalation: first, repeat and continuing-offence processes are governed by administrative review and, where applicable, civil enforcement; specific escalation schedules are not specified on the cited pages.[2]
- Non-monetary sanctions: corrective orders, suspension or debarment from city contracting, contract termination, and referral for civil or criminal action may apply under city rules and the code.[1]
- Enforcer and complaint pathway: file procurement complaints and reports with the Bureau of Purchasing; legal review and enforcement may involve the City Solicitor or Department of Finance.[1]
- Appeals and review: administrative review and protest procedures are set out by the Purchasing Bureau and the Code; explicit time limits for filing protests are not specified on the cited pages and should be confirmed with the bureau.[1]
Applications & Forms
Vendor registration, solicitation documents (RFP/RFQ/RFI), and bidding forms are published and managed by the Bureau of Purchasing; submission instructions and required forms are made available on the purchasing site.[1]
- Vendor registration and W-9 or substitute forms: available via the City purchasing portal; fees are not specified on the cited page.[1]
- Solicitation deadlines: set per individual solicitation documents; always confirm deadlines printed on the solicitation.
- Security/privacy attachments: requirements for data handling may be included in RFP terms or contract exhibits.
Procurement Process for Tech and Data Contracts
Technology procurements typically follow these general stages: solicitation design (scope, deliverables, security), vendor outreach and pre-bid Q&A, submission evaluation against published criteria, contract negotiation and award, and post-award monitoring. City-specific thresholds, sole-source justifications, and minority/local hiring provisions are administered by the Purchasing Bureau and governed by the City Code.[1]
- Solicitation types: RFP, RFQ, IT-specific procurement procedures.
- Technical evaluation: interoperability, cybersecurity, and data governance criteria are commonly evaluated in tech procurements.
- Compliance checks: insurance, background checks for personnel, and security controls may be required in contract terms.
FAQ
- Who enforces procurement rules for technology contracts in Baltimore?
- The City of Baltimore Bureau of Purchasing enforces procurement procedures, supported by the Department of Finance and the City Solicitor as needed.[1]
- Can a vendor challenge an award decision?
- Yes; vendors may file a protest under the Purchasing Bureau procedures. Exact protest time limits should be confirmed with the bureau or the solicitation document, as not specified on the cited pages.[1]
- Are there set fines for procurement violations?
- Specific fine amounts are not specified on the cited city pages; potential remedies include administrative sanctions, contract termination, debarment, and referral for civil or criminal proceedings.[2]
How-To
- Register as a vendor on the City purchasing portal and confirm required forms.
- Review the solicitation documents carefully for technical and security requirements.
- Prepare and submit your proposal before the stated deadline, following format and submission instructions.
- If you disagree with an award, follow the Purchasing Bureau protest procedure promptly and gather documentary evidence.
Key Takeaways
- Register early and follow solicitation instructions exactly.
- Address data security and privacy requirements in proposals.
- Contact the Bureau of Purchasing for procedural questions and protest timelines.[1]
Help and Support / Resources
- Baltimore City Bureau of Purchasing
- Baltimore City Code (Municode)
- Baltimore Office of Information Technology