Ecommerce Government Bids & RFPs

Atlanta Public Schools (APS) is seeking proposals for Data Dashboard Analytic Services. The RFP (Request for Proposal) has an open date of May 11th, 2026, a questions due date of May 22nd, 2026, and a close date for submissions on June 11th, 2026. A virtual preproposal conference will be held on May 18th, 2026. Required documents include a proposal, price proposal, business license/Georgia SOS registration, and other administrative forms. Vendors must log in or register for a Bonfire account to download files and prepare a submission.

The Regional Transportation District (RTD) is issuing a Request for Information (RFI) to gather industry insights for a forthcoming Request for Proposals (RFP) for a branded online promotional merchandise store. RTD seeks to understand effective procurement and operational structures for a hosted, full-service e-commerce platform. Key areas of interest include defining the scope of work, identifying best practices in vendor-managed fulfillment, clarifying responsibilities, and gathering market intelligence on technology infrastructure, cybersecurity, accessibility, and system integration. The RFI also aims to collect information on pricing models, long-term cost controls, multiyear price guarantees, escalation management, and transparency in volatile markets. This RFI is intended to help RTD structure a competitive RFP that promotes fiscal responsibility, minimizes risk, and ensures a reliable online retail experience. The timeline includes RFI advertisement on April 29, 2026, a non-mandatory project overview on May 7, 2026, questions due by May 14, 2026, answers to questions by May 21, 2026, and RFI submittals due by May 28, 2026, all via RTD's online procurement portal, OpenGov.

The provided text details various appendices and clauses related to a contract, primarily focusing on cloud software services and payment card industry compliance. For cloud software, vendor obligations include continuous service availability (99. 9%), 24/7/365 telephone and online support, quarterly updates, semiannual reports, and specific response times for priority one issues (within 1 hour). Scheduled and unscheduled maintenance procedures are outlined, with at least 72 hours' notice for unscheduled maintenance unless it's an emergency. The vendor is responsible for vulnerability management and any damage to university data. For payment card transactions, the vendor must comply with PCI DSS, P2DSS, and PCI PTS standards, providing annual attestation of compliance. A Business Associate Agreement (BAA) is also included, outlining the vendor's responsibilities regarding Protected Health Information (PHI) under HIPAA and HITECH, including permitted uses and disclosures, security safeguards, reporting of breaches, and subcontractor requirements. The vendor must maintain a comprehensive information privacy and security program and comply with HHS guidance. The BAA also details the handling of designated record sets, including access and amendment procedures. The vendor indemnifies the university against losses arising from breaches of the agreement or negligence. The BAA survives termination of the agreement indefinitely for retained PHI. The governing law is Arizona, with disputes resolved in Arizona state or federal courts.