Albuquerque City Open Data: Vendor Requirements

Albuquerque, New Mexico requires vendors that provide data or data-driven services to the city to meet open data and procurement expectations described by municipal programs and purchasing rules. This guide summarizes the roles, likely contractual requirements, how to register as a vendor, data-format expectations, compliance pathways, and where to report concerns on city open data systems ^[1].

Scope & Who this Applies To

This guidance applies to third-party vendors, consultants, contractors, and platform providers that deliver datasets, APIs, or hosted services to any City of Albuquerque department when the contract anticipates public data publication, integration with the city Open Data portal, or transfer of records that the city intends to publish.

Vendor Technical & Data Requirements

• Deliver data in machine-readable formats (CSV, JSON, GeoJSON) and include metadata and field descriptions.
• Provide documentation for APIs, data schemas, and update schedules.
• Adhere to any contractually agreed SLAs for data refresh, uptime, and error correction.
• Follow data security and privacy standards specified in the contract and in applicable city policies; redact or exclude protected personal data as required by law.
• Include clear maintenance and archival plans for datasets and record retention timelines.

Data Licensing & Metadata

Vendors should attach open license statements or rights grants that permit the city to publish and redistribute datasets. Metadata must identify source, update frequency, contact person, and any legal restrictions.

Penalties & Enforcement

Specific monetary fines and statutory penalty amounts for failures related to vendor-provided open data are not specified on the cited city pages; enforcement typically flows through contractual remedies and procurement actions. The City of Albuquerque Purchasing Division and the department holding the contract are the primary enforcers and can require cure, withhold payments, or pursue contract termination ^[2].

• Monetary fines: not specified on the cited page.
• Escalation: first breach remediation, repeat breaches may lead to contract termination or suspension of work; ranges not specified on the cited page.
• Non-monetary sanctions: cure notices, corrective action plans, contract suspension or termination, withholding of payments, and referral to legal action or debarment processes.
• Inspection and complaint pathways: vendors and residents may report issues via the department contract manager or the Purchasing Division contact points linked below.
• Appeal/review: procurement protest procedures and contract dispute resolution processes; specific time limits for appeals are not specified on the cited page.
• Defences/discretion: reasonable excuse, force majeure, or approved variances in the contract language may apply; specific statutory defenses not listed on the cited page.

Applications & Forms

The City requires vendor registration through its Purchasing Division and standard procurement documents for bidding and contracting; there is no city-published, separate "Open Data vendor form" identified on the official Open Data or Purchasing pages. For procurement, vendors should complete vendor registration, W-9 and any purchasing-system onboarding steps as required by Purchasing ^[2].

Common Violations

• Failing to deliver datasets in agreed formats or frequencies.
• Omitting required metadata or contact information.
• Publishing restricted or personal data without authorization.
• Failing to fix critical data quality or API outages within contractual SLA windows.

Action Steps for Vendors

• Register as a vendor with City Purchasing and complete procurement onboarding.
• Ask for data format, metadata, and licensing expectations before signing the contract.
• Include contractual SLAs for updates, error correction, and security obligations.
• Keep a named city contract manager and use official reporting channels for disputes or compliance notices.

FAQ

Do vendors need special permission to publish city data?

Vendors must follow contract terms; the city typically controls publishing rights and will specify licensing and publication steps in the contract or data transfer agreement.

Is there a specific open data form for vendors?

No separate open-data-specific vendor form is published on the official Open Data or Purchasing pages; vendors use standard procurement onboarding forms instead.

Who enforces compliance?

The Purchasing Division and the contracting city department enforce compliance through contractual remedies and procurement processes.

How do I report incorrect or sensitive data?

Report issues to the dataset contact listed in the metadata or to the department contract manager; unresolved issues can be raised with Purchasing.

How-To

1. Confirm contract terms about data publication, licensing, and SLAs with the city contract manager.
2. Prepare datasets in machine-readable formats with complete metadata and a designated contact.
3. Submit datasets and documentation according to the city’s technical instructions or via the Open Data intake process.
4. If a dispute arises, follow the contract’s cure and dispute procedures and contact Purchasing for procurement remedies.

Key Takeaways

• City contracts and Purchasing rules govern vendor open data obligations.
• Deliver machine-readable data with metadata and agreed SLAs to avoid remedial actions.
• Use official department contacts and Purchasing for reporting and appeals.

Help and Support / Resources

• City of Albuquerque Open Data
• City of Albuquerque Purchasing Division
• Albuquerque Code of Ordinances (municipal code)
• City Clerk & Public Records

1. [1] City of Albuquerque Open Data
2. [2] City of Albuquerque Purchasing Division