Purchasing Services 130 Trinity Avenue, S.W.

4th Floor Atlanta, Georgia 30303

Request for Proposals (RFP)

For

Data Dashboard & Analytic Service

May 11, 2026

RFP Number: 26-120525-P-LP

Due Date: June 11, 2026

Time Due: 11:00 a.m., ET

NIGP Commodity Code(s): 20836, 20837, 20811, 20853, 20854, 20846, 20913, 20942, 91812

ATLANTA PUBLIC SCHOOLS

RFP 26-120525-P-LP

ADVERTISEMENT FOR REQUEST FOR PROPOSALS

The Atlanta Independent School System (hereinafter, “Atlanta Public Schools” or “APS”) invites qualified contractors to submit proposals to provide Data Dashboard & Analytic Services.

In using this method for solicitation, we are requesting that you provide the best value for our requirements. To be eligible for consideration, online proposals shall be presented in accordance with the instructions of this solicitation and within the timeframe specified. It shall be the responsibility of the selected offeror to meet all specifications and guidelines set forth herein. Atlanta Public Schools, at its discretion, determines the criteria and process by whereby proposals are evaluated and awarded. No damages shall be recoverable by any challenger as a result of these determinations or decisions by Atlanta Public Schools.

If you are unable to download these documents, you may contact the assigned procurement officer, Lorenzo Presley, at (404) 802-1564 or lorenzo.presley@atlanta.k12.ga.us.

(Pre-Proposal) - Virtual

A Pre-Proposal conference will be held on Monday, May 18th, 2026, at 10:30 a.m. ET via Teams call.

Microsoft Teams Meeting

Join: https://teams.microsoft.com/meet/27055160181001?p=l1XAAGHsKJNmPvsPzv

Meeting ID: 270 551 601 810 01 Passcode: tT3ii9k8

(Please NOTE: Attendance is not mandatory but strongly encouraged)

All questions or requests for clarification must be sent via Bonfire under Message - Opportunity Q&A:

https://aps.bonfirehub.com/opportunities/235957.

All addenda related to this solicitation will be posted on the Bonfire website at https://aps.bonfirehub.com/opportunities/235957. It is the offeror’s responsibility to check the Bonfire website for any addendums, responses to offeror questions, or other communications related to this solicitation.

Proposals shall be submitted online at https://aps.bonfirehub.com/opportunities/235957. The Office of Procurement Services will only accept proposals submitted online. Proposal submissions are due no later than 11:00 a.m. ET, June 11th, 2026.

APS will only accept online submissions for proposals. Proposals can be submitted online at:

https://aps.bonfirehub.com/opportunities/235957. Proposals submitted after the proposal close date will not be accepted. Note: Any proposal submitted in any other format (email, paper, fax, mail, etc.)

will not be accepted for any reason.

mailto:lorenzo.presley@atlanta.k12.ga.us https://teams.microsoft.com/meet/27055160181001?p=l1XAAGHsKJNmPvsPzv https://aps.bonfirehub.com/opportunities/235957 https://aps.bonfirehub.com/opportunities/235957 https://aps.bonfirehub.com/opportunities/235957

TENTATIVE TIMELINE

05/11/2026 Release RFP 05/18/2026 Pre-proposal conference Via Teams, 10:30 a.m. ET 05/22/2026 Deadline for written questions, 12:00 p.m., ET 05/28/2026 Response to questions to be posted to Bonfire 06/11/2026 RFP due online at Bonfire by 11:00 a.m., ET 06/15/2026 Administrative Review 06/29/2026 Initial Shortlist Evaluation 07/13/2026 Phase 2 On-Site Interview/Presentations (if applicable) 08/03/2026 Recommendation to the APS Board of Education

TABLE OF CONTENTS

Section 1 Introduction Section 2 Scope of Work Section 3 Requirements for Data Dashboard & Analytic Service Section 4 Technical Requirements for Data Dashboard & Analytic Plan Section 5 Proposal Submission Requirements Section 6 Company Qualifications and Experience Section 7 Methodology and Operations Section 8 Evaluation Section 9 Additional Requirements Section 10 General Requirements Section 11 General Terms and Conditions Section 12 Award Section 13 Contract

Attachments:

Attachment 1: Solicitation Acknowledgment Form Attachment 2: Offeror Compliance Form Attachment 3: Offeror Inclusion Form Attachment 4: Primary Vendor/Subcontractor Utilization Form Attachment 5: Promise of Non-Discrimination Attachment 6: E-Verify Affidavit of Compliance

1. Contractor Affidavit under O.C.G.A 13-10-91 (b)(I)

2. Subcontractor Affidavit under O.C.G.A. 13-10-91 (b)(3); if applicable

3. Affidavit of Exception (if applicable)

Attachment 7: Joint Venture Affidavit Attachment 8: Contract Exceptions Attachment 9: No Influence and Non-Collusion Affidavit Attachment 10: Local Preference Attachment 11: Offeror Reference Form Attachment A: Price Proposal Form Appendix 1 School Calendar

1.0 INTRODUCTION

1.0.1 To be entitled to consideration, proposals shall be submitted online at https://aps.bonfirehub.com/opportunities/235957. The Office of Procurement Services will only accept proposals submitted online. Proposal submissions are due at 11:00 a.m. ET on the date outlined in the solicitation (as determined by the time stamp clock when submitted online).

1.0.2 Proposals can be submitted online at:

https://aps.bonfirehub.com/opportunities/235957. Proposals submitted after the proposal close date will not be accepted. Note: Any proposal submitted in any other format (email, paper, fax, mail, etc.) will not be accepted for any reason.

1.1 PURPOSE

1.1.1 The Atlanta Independent School System (hereinafter, “Atlanta Public Schools” or “APS”) invites qualified vendors to submit proposals to provide the APS with Data Dashboard & Analytic Services.

1.1.2 APS is seeking experienced and qualified contractors to provide Data Dashboard & Analytic Services to the district in accordance with all Local, State, and Federal regulations.

1.1.3 This solicitation is issued in accordance with applicable state and federal laws.

1.2 BACKGROUND

1.2.1 Atlanta Public Schools (APS) is the seventh-largest school system in Georgia and the eighty-ninth-largest school system in the nation. APS currently serves approximately 50,000 students and operates schools and administrative facilities ranging in size from 31,000 square feet to 485,000 square feet. Some campuses are comprised of a single structure, while others have multiple structures. All schools are within the city limits of Atlanta.

1.3 CONTRACT TERM

The first term of the contract will be when the last signature is obtained through one (1) year. The contract will include an option of up to four (4) additional one-year contract renewals if agreed upon by both Atlanta Public Schools and the Vendor.

1.4 AWARD

1.4.1 APS reserves the right to make multiple awards, based on experience and qualifications, if it is deemed to be in the district’s best interest. APS reserves the right to negotiate with the highest-ranked proposer regarding proposal scope, quality, price, and any other issues it considers relevant to the awarded performance of the services.

1.4.2 If awarded to multiple vendors, the contract will be utilized by distributing service needs based on factors such as vendor capacity, geographic coverage, pricing, and specific expertise. This approach ensures flexibility, maintains competitive service quality, and allows us to allocate work efficiently across offerors to best meet our requirements.

2.0 SCOPE OF WORK

2.1 The vendor must have proven experience in meeting the solicitation requirements as described in sections 3.0 and 4.0. In addition, the vendor’s proposed solution must provide a description of the functionality, the user's process for utilizing the services, and implementation requirements and dependencies. The Vendor must describe functionality for its ability to meet each of the required specifications.

2.2 The vendor must comprehensively describe the methodology and procedures intended to fulfill the requirements outlined in this RFP for APS. The selected Vendor(s) will be accountable for meeting the specifications and guidelines outlined herein. The vendor shall provide a fully integrated, enterprise-level data dashboard platform designed to unify and streamline access to critical district data, enabling stakeholders at all levels to efficiently analyze, interpret, and act on information to support student success and organizational effectiveness. The solution must seamlessly integrate with existing district systems, deliver intuitive and role-based user experiences, and incorporate advanced analytics, including AI-driven capabilities, to move the district from reactive reporting to proactive, data-informed decision-making.

2.3 The platform should enhance data accessibility, promote system-wide adoption, and strengthen data literacy while ensuring the highest standards of security, compliance, and performance.

2.4 At a minimum, the proposed solution shall:

• Aggregate data from multiple district systems (SIS, ERP, LMS, assessments, etc.)

• Provide whole child analysis across academic, attendance, behavior, and SEL domains

• Support role-based dashboards and drill-down capabilities

• Incorporate AI-driven insights, predictions, and recommendations

• Enable secure, compliant access to student-level data

• Support district-wide adoption and data literacy

3.0 DELIVERABLES

The selected vendor shall provide a comprehensive set of deliverables necessary to successfully design, implement, deploy, and sustain a fully integrated data dashboard platform, including all required system configurations, data integrations, documentation, training, support services, and performance monitoring components to ensure effective adoption, long-term usability, and alignment with district goals and requirements.

The selected vendor shall provide:

3.0.1 Fully configured dashboard platform

3.0.2 Role-based dashboards (district, school, classroom/teacher, student, parent)

3.0.3 AI-enabled Analytic and reporting capabilities

3.0.4 Data integration pipelines and refresh schedules

3.0.5 Data governance and security framework documentation

3.0.6 Training materials and onboarding modules

3.0.7 Implementation of project plan and timeline

3.0.8 Ongoing support and maintenance services

3.0.9 SLA documentation and reporting

3.1 Key Performance Indicators:

The effectiveness and overall success of the proposed solution will be evaluated through a defined set of key performance indicators that measure system adoption, operational efficiency, data quality, user experience, and the impact of advanced Analytic capabilities. Vendors must demonstrate how their solution will support measurable improvements across these areas and provide ongoing reporting to track performance against these metrics. The solution will be evaluated based on:

• Increase in dashboard adoption rates

• Reduction in manual data requests

• Improvement in data access turnaround time

• Accuracy and reliability of data integration

• User satisfaction across stakeholder groups

• Effectiveness of AI-driven insights (measured by usage and outcomes)

• System uptime and performance metrics

3.2 Functional Requirements:

3.2.1 Whole Child Analytic

3.2.1.1 Student profile and longitudinal view

• Unified student profile with demographics, programs, enrollment history, and contacts

• Longitudinal trends across academics, attendance, behavior, SEL, and interventions

• Event timeline (assessments, incidents, meetings, interventions, notes)

3.2.2 Academic performance Analytic

• Standard-based assessment views and course performance indicators

• Missing work, failure risk, and growth metrics

• Cohort and subgroup comparisons

3.2.3 Attendance and engagement Analytic

• Chronic absenteeism metrics and trend analysis

• Attendance pattern visualizations (day, period, seasonality)

• Intervention tracking with outcomes

3.2.4 Behavior, Discipline, and Climate

• Incident tracking with categories, actions, and locations

• Disproportionality and trend analysis

• Restorative practice tracking

3.2.5 SEL, wellness, and student support

• SEL screener results and trends

• Counseling/support service tracking (role-restricted)

• Wraparound supports monitoring

3.2.6 MTSS / Intervention management

• Intervention planning with goals, progress monitoring, owners, and schedules

• Fidelity tracking and outcome status

• Meeting workflows and documentation

3.2.7 Early Warning System (EWS)

• Configurable risk rules across domains

• Risk levels with drill-down explanations

• Watchlists and caseload views

3.2.8 Equity and Subgroup Analysis

• Disaggregation by student groups and programs

• Opportunity and outcome gap tracking

• Small-n suppression rules

3.2.9 Dashboards, Views, and Drill Paths (role-based)

• Role-based dashboards (district, school, principal, counselor, teacher, student, parent, etc.)

• Drill-down from district → school → classroom → student

• Saved filters and views

3.2.10 Data Integration and Refresh

• Integration with SIS, LMS, assessment, discipline, MTSS, and survey systems

• Configurable refresh cadence

• Data validation indicators and metric dictionary

3.2.11 Search, Lists, and Case Management

• Global search and custom student lists/watchlists

• Bulk actions and outreach logging

• Notes with timestamps and role-based visibility

3.2.12 Reporting and Exports

• Scheduled reports and role-based exports

• Export audit trails

3.2.13 Alerts and Notifications

• Configurable alerts with thresholds and delivery options

• Alert acknowledgment and task assignment

3.2.14 User Management and Permissions

• Role-based access aligned to rosters/caseloads

• Restricted views for sensitive SEL/health data

• Custom role configuration

3.2.15 Usability, Accessibility, and Training Support

• Mobile-responsive design and ADA/WCAG accessibility

• Embedded help and guided tours

• In-app feedback tools

3.2.16 Data Governance, Transparency, and AI Ethics

• Metric definitions and “last refreshed” indicators

• Data correction workflow and audit logs

3.2.17 Executive Analytic

3.2.17.1 The system shall provide a district-level executive dashboard that consolidates key instructional and operational metrics into a unified, intuitive interface.

3.2.17.2 The platform shall support dual-domain views, including:

Instructional Metrics (e.g., academic performance, assessment outcomes, growth metrics, graduation rates, attendance, behavior, and whole child indicators)

Operational Metrics (e.g., staffing, budget utilization, enrollment trends, transportation, facilities, technology usage, and service delivery performance)

3.2.18 The dashboard shall allow users to toggle between or simultaneously view instructional and operational data, with the ability to identify correlations and dependencies between the two domains.

3.2.19 The system shall provide drill-down capabilities from district to school to subgroup to students (for instructional data) and district to division to department to site (for operational data).

3.2.20 The platform shall support customizable views and filters to allow executives to tailor dashboards to their priorities and focus areas.

3.2.21 The system shall display trend analysis and longitudinal data to monitor performance over time across both domains.

3.2.22 The solution shall include visual indicators of performance status (e.g., on track, at risk, off track) with configurable thresholds.

3.3 Strategic Plan Analytic

3.3.1 The system shall support the creation and visualization of district strategic plans, including goals, objectives, initiatives, and key outcomes.

3.3.2 The platform shall allow alignment of strategic goals to measurable Key Performance Indicators (KPIs), with the ability to track progress over time.

3.3.3 The dashboard shall provide multi-level visibility, enabling users to view progress at the district, school, department, and initiative level.

3.3.4 The system shall support drill-down capabilities from high-level strategic goals to underlying metrics, data sources, and contributing factors.

3.3.5 The platform shall allow for status tracking (e.g., on track, at risk, off track) with configurable thresholds and visual indicators.

3.3.6 The solution shall enable assignment of ownership and accountability for each strategic goal, initiative, and metric.

3.3.7 The dashboard shall support timeline tracking, including milestones, deadlines, and progress updates.

3.4 AI-Enabled Capabilities

• Predictive Analytic (risk scoring, failure prediction, absenteeism)

• Natural language query functionality

• AI-generated summaries and insights

• Pattern detection and anomaly identification

• Intervention recommendations and forecasting

• Explainable AI outputs (transparent logic and drivers)

• AI functions shall operate in a read-only capacity and shall not have the ability to write to, modify, or alter data sources.

• Ensure that district data and user queries are not used to train external AI/LLM models and are protected from unauthorized AI training use.

3.5 User Experience and Role-Based Access

• Role-based dashboards (teacher, counselor, principal, district leader, student, parent, etc.)

• Drill-down capability from district → student level

• Customizable views and saved filters

• Mobile-responsive and accessible design (ADA/WCAG compliant)

4.0 TECHNICAL REQUIREMENTS

4.1 The System Must:

4.1.1 Integrate with:

o Student Information Systems (SIS) o Learning Management Systems (LMS) o Enterprise Resource Planning (ERP) System o Assessment platforms o Special Education platforms o MTSS/intervention tools o Survey and climate systems

4.1.2 Support:

o Single Sign On (SSO) o Real-time or near real-time data refresh o Cloud-based architecture (preferred) o Scalable infrastructure o API-based integrations o Data validation and anomaly detection o Make audit logs available in an easily consumable and integrable format, such as Syslog, scheduled CSV file transfers, or other standard export mechanisms.

4.1.3 Provide

o Data dictionary and metadata management o Configurable data pipelines o System performance monitoring tools

4.2 Vendor Sandbox Environment Requirement

To support a thorough and informed evaluation process, the district strongly encourages that all proposing vendors provide access to a sandbox environment that allows a designated group of stakeholders to actively engage with the proposed solution in a controlled, trial setting. This environment should enable users to explore key features and user experiences reflective of real-world use within a K–12 educational context

4.2.1 The sandbox or demo environment must be made available for a defined evaluation period and should, at a minimum, include representative data (mock or de-identified) that demonstrates the platform’s capabilities, including dashboards, drill-down functionality, and reporting.

4.2.2 Vendors are encouraged to configure the environment to simulate role-based access (e.g., teacher, principal, district leader, student, etc.) to allow evaluators to assess usability and functionality across user groups.

4.2.3 Vendors should also provide guidance and support during the evaluation period, including:

• A structured demonstration or walkthrough session for stakeholders

• Access instructions and user credentials

• Optional training materials or quick-start guides

• Technical support for troubleshooting during the trial period

4.2.4 Additionally, vendors should outline any limitations of the sandbox environment, including differences between the demo and production environments, data constraints, or restricted features. The district reserves the right to incorporate feedback from sandbox testing into the final evaluation and vendor selection process.

4.3 Application Support

4.3.1 User-friendly ticketing system and produce resolution(s) per Service Level Agreements

(SLAs).

4.3.2 The vendor should enhance (add new fields/updates/functionality as requested) in the application as needed by the users.

4.3.3 Application support should be efficient and respond quickly to user issues/needs.

4.3.3.1 Need daily technical database and FTP (File Transfer Protocol) support. May need to interface with other APS vendors. Vendor must confirm if the data is encrypted in the system that APS will be using. Additionally, the vendor must ensure that the data is secured. The vendor does not have the right to share APS’s data with anyone until you have the approval from the APS business owner.

4.3.3.2 Real-time system outage information.

4.3.3.3 24/7 customer support for ticketing IT backend (as described in Section 4.4 below).

4.3.3.4 24/7 customer support for end-users and other stakeholders.

4.3.3.5 Rapid response time for resolving open tickets.

4.4 Data and Security Requirements

4.4.1 Additionally, the proposed solution must adhere to the highest standards of data security, privacy, and governance, ensuring full compliance with all applicable federal, state, and district regulations, including the Family Educational Rights and Privacy Act (FERPA). The platform must implement robust role-based access controls to ensure that users only have access to data appropriate to their role, along with strong authentication protocols and encryption of data both in transit and at rest. The system must maintain comprehensive audit logs to track user activity, data access, and system changes, including any AI-generated outputs. Additionally, the solution should support data masking for sensitive information, particularly for student-level and protected data domains, and include configurable data governance workflows such as data correction processes and validation checks. Vendors must also demonstrate adherence to responsible AI practices, including transparency in how predictive models generate insights, mechanisms for detecting and mitigating bias, and the ability to apply human-in-the-loop controls to ensure that AI recommendations are reviewed and validated by staff before action is taken. Overall, the platform must provide a secure, transparent, and accountable environment that safeguards student data while enabling meaningful and compliant data use across the district.

4.4.2 The vendor shall promptly notify the district of any data breach involving district data stored, processed, or transmitted by the vendor. The vendor shall maintain appropriate cybersecurity protections, including ransomware prevention and response measures.

4.5 Service Level Agreement (SLA) Requirements

Atlanta Public Schools considers both the quality and availability to be critical factors influencing the selection of a Vendor to provide the services described in the RFP. The primary function of the district is to educate students. It is essential that the software be available at all times to provide Atlanta Public Schools Staff with appropriate tools to create and support the business functions. A service outage will prevent our employees from performing their job functions effectively and disrupt the district from educating students appropriately.

4.5.1 The District requires the selected Vendor to provide and maintain the referenced services on a 24-hour-a-day, seven-day-a-week basis, including weekends and holidays.

4.5.2 Scheduled maintenance is defined as those times that the Vendor needs to make modifications to the services and or equipment to ensure delivery of services prior to any service problems. Vendor will be required to coordinate maintenance windows ahead of time with Atlanta Public Schools so that the District’s operational requirements will not be hindered.

4.5.3 Expected uptime as specified by RFP Service will be 99.99% on a 24x7 basis. Uptime is defined as full usage of the service and at full capacity as stated herein, with the exception of scheduled maintenance.

4.5.4 Vendor response time is defined as the elapsed time between the Vendor’s qualified technician contacting the appropriate site at Atlanta Public Schools after either of the following events occurs:

4.5.4.1 An authorized representative of Atlanta Public Schools contacts the Vendor’s technical services organization to report a problem.

4.5.4.2 The Vendor, through its monitoring functions, becomes aware of a system failure or potential system failure.

4.6 Service Priorities – Service Availability

The solution will be fully available for access and normal operations by the end users 99.99% of the time. If the solution is technically available (i.e., can access the application), but significant problems exist (e.g., performance issues, data inaccuracies), it is functional (and will be considered as) unavailable. Compliance with this availability SLA will be measured on a calendar-month basis. Availability will be calculated by dividing:

• the total number of minutes that the system was available, by

• the total minutes in the respective month, and then multiplying that amount (the quotient) by 100

Note: If the vendor feels that problems are not due to or caused by their product or service, it is incumbent upon the vendor to provide detailed, concrete, and objective data (e.g., product response times within their domain) to substantiate and support their position. In these cases (i.e., vendor and district agree that problems are not due to the vendor), the system will be considered available.

4.6.1 Service Credits

If the vendor fails to meet the Service Availability criteria during any calendar month, the Customer (i.e., “Atlanta Public Schools”) will receive a service credit equal to any applicable service fees for the Services, prorated for the amount of time Service Availability fell below the Service Availability criteria. If System Availability falls below fifty percent for two consecutive months, then the District will discontinue payments until all problems have been rectified.

4.6.2 Staff/Service Performance

The vendor shall describe their classification scheme for prioritizing problem incidents and Service Requests, along with their corresponding resolution times.

For example:

Table 1. Target resolution times by Priorities.

Priority is determined by the Urgency and the Impact of the Incident or Service Request, as follows:

Priority Description Target Resolution Time 1 Critical 1 hour 2 High 8 hours

3 Medium 24 hours

4 Low 48 hours

5 Planning Planned

Table 2. Determination of Priorities.

Impact

High Medium Low

Urgency High 1 2 3 Medium 2 3 4 Low 3 4 5

The vendor shall also provide a detailed list of types of Incidents and Service to Requests, along with their Urgency and Impact, and the calculated Priority.

4.6.3 Service Support Capacity

The vendor shall describe the support infrastructure that they have in place to ensure that all problem incidents and requests are addressed in a timely fashion and in accordance with the criteria specified in their response to this RFP. This includes specifying the organization of their support team and their hours of operation.

4.6.4 Service Support Escalation Procedures

The vendor shall provide escalation procedures for incidents or requests that have exceeded the agreed-upon SLA.

4.6.5 Service Objectives Ratings

Timely and consistent Problem Resolution Times (PRT) are critical to providing excellent customer service. The vendor shall specify their Service Objectives for their support team and their means of verifying that their services are meeting all the specified Service Objectives.

4.6.6 Other SLA Requirements

4.6.6.1 Vendor will identify a technical contact assigned to the District that will be accessible during normal business hours and a secondary contact for emergencies and after-hours events.

4.6.6.2 Vendor will conduct scheduled repairs and upgrades during hour periods or at a mutually agreed upon time so as not to affect the District’s operation or use of the solution. All scheduled repairs will be subject to notification of the District’s representative in advance. Vendor will coordinate all repairs involving access to district faculties in advance with the District’s contact and facilities manager.

4.6.6.3 In the event the Vendor is unable to respond and/or make corrections to the operation of the contracted services to the substantial satisfaction of the District, the Vendor will immediately make available a supervisor with the authority to obtain the resources required to make such repairs as may be necessary.

5.0 PROPOSAL SUBMISSION REQUIREMENTS

5.1 MANDATORY REQUIREMENTS (See list in section 5.2 below)

5.1.1 Vendors are instructed to read all terms, conditions, and specifications set forth in the RFP carefully. Responses must be either typed or written in ink. Any correction made within the RFP submission (whiteout or strike-through) must be initialed by an authorized representative of the company submitting the proposal, or the proposal may be rejected by APS.

5.1.2 The offeror shall submit an online proposal with a response that fully responds to Sections 5, 6, and 7 in the Bonfire Portal. Failure to respond to Sections 5, 6, and 7 may result in the proposal being deemed non-responsive. The offeror must reference each section as listed below.

Proposals must be submitted online via the following link by the given due date: https://aps.bonfirehub.com/opportunities/235957

5.2 List of Mandatory Attachment Documents

Responses must be on the forms furnished within this RFP and completed in their entirety.

Attachment 1: Solicitation Acknowledgment Form Attachment 2: Offeror Compliance Form Attachment 3: Offeror Inclusion Form Attachment 4: Primary Vendor/Subcontractor Utilization Form Attachment 5: Promise of Non-Discrimination Attachment 6: E-Verify Affidavit of Compliance

1. Contractor Affidavit under O.C.G.A 13-10-91 (b)(I)

2. Subcontractor Affidavit under O.C.G.A. 13-10-91 (b)(3); if applicable

3. Affidavit of Exception (if applicable)

Attachment 7: Joint Venture Affidavit Attachment 8: Contract Exceptions Attachment 9: No Influence and Non-Collusion Affidavit Attachment 10: Local Preference Attachment 11: Offeror Reference Form Attachment A: Price Proposal Form

6.0 COMPANY QUALIFICATIONS AND EXPERIENCE

6.1 Provide a brief history of the company, including the number of years in business, a minimum of three (3) years providing Data Dashboard & Analytic Services to large and/or other large school districts.

6.2 Specifically, provide the following:

6.2.1 Information as to experience that will demonstrate competence to perform the work involved in this project.

6.2.2 Describe your experience transitioning districts with extensive existing dashboards and Analytic services to a standardized, scalable solution within your platform.

6.2.3 Organization and size of the company, and whether it is local, regional, national, or international in operations and capabilities.

6.2.4 The number of and/or professional staff available to be employed on this engagement.

6.2.5 Provide evidence of financial stability, such as audited financial statements or comparable financial documentation.

6.3 Provide three (3) references that your company has or is currently providing services similar to the specifications of this solicitation, Data Dashboard & Analytic Services.

Provide the following for each reference:

6.3.1 Name and address of school district or company.

6.3.2 Name and title of primary contact with telephone number, and e-mail address.

6.3.3 Description of the services provided, including dates and number of sites serviced.

6.4 Provide resumes, which include qualifications, certifications, education, and responsibilities of staff expected to be assigned to this project.

6.5 Indicate and describe the scope and volume of business with other school systems, including Georgia. Please specifically provide the average number of contracts and/or professional staff provided to each school system.

6.6 Indicate the names, addresses, and degree of utilization of any and all subcontractors that would be used in the performance of this contract.

6.7 Company Staffing

6.7.1 Identify the principal supervisory and management staff, including engagement partners, managers, other supervisors, and specialists, who would be assigned to the engagement;

6.7.2 Provide as much information as possible regarding the number, qualifications, experience, and training, including relevant continuing professional education, of the specific staff to be assigned to this engagement; and

6.7.3 Indicate how the quality of staff, with appropriate experience, over the term of the agreement will be maintained.

7.0 METHODOLOGY AND OPERATIONS

7.1 Project Management and Implementation

7.1.1 Provide a complete project plan that outlines your pre-implementation, implementation, and post-implementation methodology and operational plan.

7.1.2 Provide detailed information regarding your firm’s training and implementation processes.

7.1.3 Describe your initiation/project planning approach, stakeholder engagement, and the process for gathering dashboard and reporting requirements from district teams to identify data visualization and data utilization needs.

7.1.3 Describe the support available to APS during the implementation of the project.

7.1.4 Describe your post-implementation support plan, which should include your approach to analyzing APS’s existing systems and making recommendations for enhancements.

7.1.5 Submit a proposed timeline that assumes services will begin on September 1, 2026. A detailed installation plan will be required before contract award.

7.2 Assumptions, Dependencies, and Key Performance Indicators

7.2.1 Explain in detail the seamlessness of the solution to integrate with Infinite

Campus, Oracle/Peoplesoft, various Assessment Platforms (i.e., Georgia Milestones state assessment, NWEA Map, Write Score, Illuminate, AMIRA, ACT, SAT), and other systems.

7.2.2 Describe in detail the hosting data center component of the proposed solution.

7.3 Functional Requirements

7.3.1 Whole Child Analytic

7.3.2 Provide robust academic analytics, including standards-based performance indicators, growth metrics, identification of missing work and failure risk, and cohort/subgroup comparisons

7.3.3 Support attendance and engagement analysis, including chronic absenteeism tracking, attendance pattern visualization, and monitoring of intervention effectiveness

7.3.4 Deliver comprehensive behavior, discipline, and school climate insights, including incident tracking, trend analysis, disproportionality monitoring, and restorative practice tracking

7.3.5 Enable SEL, wellness, and student support tracking, including SEL screener data, counseling services (with role-based access), and wraparound supports

7.3.6 Include a fully integrated MTSS/intervention management system supporting planning, progress monitoring, and fidelity tracking.

7.3.7 Provide an embedded Early Warning System (EWS) with configurable risk rules, clear risk level explanations, and support for watchlists and caseload management

7.3.8 Support equity and subgroup analysis, including disaggregation by student groups, monitoring of opportunity and outcome gaps, and enforcement of small-n suppression rules

7.3.9 Deliver role-based dashboards and drill-down capabilities, enabling navigation from district-level views to individual students, with customizable filters and saved views

7.3.10 Support data integration and refresh across multiple systems (SIS, LMS, ERP, assessments, discipline, MTSS, surveys), including configurable refresh schedules, data validation indicators, and a defined metric dictionary

7.3.11 Provide search, list management, and case management tools, including global search, custom student lists/watchlists, bulk actions, outreach tracking, and role-based notes

7.3.12 Enable reporting and exports, including printable student summaries, scheduled reports, and audit trails

7.3.13 Include alerts and notifications, with configurable thresholds, delivery options, acknowledgment tracking, and task assignment capabilities

7.3.14 Ensure robust user management and permissions, including role-based access aligned to rosters/caseloads, restricted views for sensitive data, and customizable roles

7.3.15 Prioritize usability, accessibility, and training support, including mobile responsiveness, ADA/WCAG compliance, embedded help features, guided tours, and in-app feedback tools

7.3.16 Maintain strong data governance, transparency, and ethical standards, including clear metric definitions, data refresh indicators, data correction workflows, and comprehensive audit logging

7.4 Executive Analytic

7.4.1 Provide a district-level executive dashboard that consolidates key instructional and operational metrics into a single, intuitive interface

7.4.2 Support dual-domain views, including:

• Instructional metrics (academic performance, assessments, growth, graduation rates, attendance, behavior, whole child indicators)

• Operational metrics (staffing, budget utilization, enrollment, transportation, facilities, technology usage, service delivery)

7.4.3 Enable users to toggle between or simultaneously view instructional and operational data, with the ability to identify correlations and dependencies across domains

7.4.4 Include drill-down capabilities:

• Instructional: district → school → subgroup → student

• Operational: district → division → department → site

7.4.5 Provide customizable dashboards and filters to align with executive priorities and focus areas

7.4.6 Deliver trend analysis and longitudinal data views to monitor performance over time across both instructional and operational domains

7.4.7 Display performance status indicators (e.g., on track, at risk, off track) with configurable thresholds

7.5 Strategic Plan Analytic

7.5.1 Support the creation and visualization of district strategic plans, including goals, objectives, initiatives, and key outcomes

7.5.2 Enable alignment of strategic goals to measurable KPIs, with the ability to track progress over time

7.5.3 Provide multi-level visibility across district, school, department, and initiative levels

7.5.4 Include drill-down capabilities from high-level strategic goals to underlying metrics, data sources, and contributing factors

7.5.5 Support status tracking (e.g., on track, at risk, off track) with configurable thresholds and visual indicators

7.5.6 Allow assignment of ownership and accountability for goals, initiatives, and metrics

7.5.7 Enable timeline tracking, including milestones, deadlines, and progress updates

7.6 Technical Requirements

7.6.1 The system must integrate with:

o Student Information Systems (SIS) o Learning Management Systems (LMS) o Enterprise Resource Planning (ERP) o Assessment platforms o Special Education platforms o MTSS/intervention tools o Survey and climate systems

7.6.2 The system must support:

o Single Sign On (SSO) o Real-time or near real-time data refresh o Cloud-based architecture (preferred) o Scalable infrastructure o API-based integrations o Data validation and anomaly detection o Make audit logs available in an easily consumable and integrable format, such as Syslog, scheduled CSV file transfers, or other standard export mechanisms.

7.6.3 The system must provide:

o Data dictionary and metadata management o Configurable data pipelines o System performance monitoring tools

7.7 PRICING

7.7.1 Provide pricing on the APS price proposal form, which is included in the solicitation. The Price Proposal Form must be completed 100%. Attachment A

8.0 EVALUATION

8.1 To be eligible for consideration, proposals shall be presented in accordance with the instructions of this solicitation and within the timeframe specified. It shall be the responsibility of the awarded contractor to meet all specifications and guidelines set forth herein.

8.2 An APS evaluation committee will evaluate each proposal that is deemed responsive.

APS, at its sole discretion, determines the criteria and process whereby proposals are evaluated and awarded. No damages shall be recoverable by any challenger as a result of the determinations or decisions by APS.

8.3 APS reserves the right during the evaluation process to contact offerors who submit proposals and request additional information or clarification necessary to complete the evaluation.

8.4 After the closing date and time, Procurement Services will conduct an administrative review of all proposals received to determine responsiveness. Proposals that are deemed to be responsive will be submitted to the evaluation committee for review.

Proposals that are deemed to be non-responsive will not be evaluated or considered for the award.

8.5 APS will evaluate all proposals and reserves the right to develop a competitive range for consideration. The competitive range is defined as a group for competitive negotiation, as determined during the evaluation process, composed of only those proposals that are considered to have a reasonable chance of being selected for an award and who are, therefore, chosen for additional discussions and negotiations. Proposals not in the competitive range are given no further consideration.

8.6 Proposals will be evaluated on the following criteria:

8.7 The formula to evaluate prices is as follows:

(Lowest price/price of the proposal being evaluated) x points possible for price = score (If applicable)

8.8 It is anticipated that the top evaluated proposals submitted in Phase 1 will be shortlisted and may be asked to participate in presentations/interviews as a part of Phase 2 of the

# Criteria for Phase I Points Possible

1 Company Qualifications and Experience 300

2 Methodology and Operations 500

3 Cost – Attachment A – Price Proposal Form 200

Total 1000 evaluation process. APS, at its sole discretion, will determine which/if any, proposals will move forward into Phase 2.

8.9 APS reserves the right to NOT hold a Phase 2 presentation/interview.

8.10 PHASE 2: Criteria for Phase 2 Presentation/Interview: (Solely at APS discretion)

8.10.1 Offerors who have been shortlisted may be invited to participate in the presentation/interview Phase of the RFP process.

8.10.2 The shortlisted offerors will be sent an email outlining the date/time/agenda of their scheduled invitations.

8.10.3 Offerors who choose not to participate in the presentation/interview process will be removed from consideration for an award.

8.10.4 Phase 1 scores will not be considered as part of Phase 2 scoring. Phase 2 will be the final score of the evaluation process.

8.10.5 Phase 2 Presentation/interview evaluation criteria will be provided to the shortlisted offerors.

Phase 1 scores will not be considered as part of Phase 2 scoring. Phase 2 scores will be the final score of the evaluation process unless BAFOs are requested.

8.10.6 APS reserves the right to request the best and final offer (BAFO) from offerors during either Phase 1 or Phase 2 of the evaluation process.

8.10.7 APS reserves the right to negotiate terms and conditions, scope of work, price, and/or non-price terms and conditions with selected vendor(s) to meet the needs of the district.

8.10.8 Negotiations may be:

• Concurrent, which may be conducted concurrently with multiple offerors.

• Exclusive, which may be conducted with the offeror whose proposal is the highest rated overall.

9.0 ADDITIONAL REQUIREMENTS

9.1 All responses submitted become the property of APS and are subject to applicable open records policies and laws.

9.2 Proposals cannot be withdrawn after they are submitted to APS unless the offeror makes a request in writing to the Executive Director of Purchasing Services prior to the time set for receiving proposals or unless the Executive Director of Purchasing Services fails to accept or reject the proposals within one hundred and twenty (120) days after the due date of the proposal.

9.3 Proposals that contain irregularities of any kind and/or do not comply fully with the requirements stated in the solicitation documents may be rejected at the discretion of the Executive Director of Purchasing Services.

# Criteria for Phase II Points Possible

Interview/Presentations 1000

Total 1000

9.4 APS reserves the right to waive any minor informality or error in the solicitation or offeror’s proposal that will not adversely affect competition.

9.5 By submitting a response, the offeror certifies that this proposal is made without prior understanding, agreement, or connection with any corporation, company, or person submitting a proposal for the same service and is in all respects fair and without collusion or fraud; that collusive pricing is understood to be a violation of state and federal law and can result in fines, prison sentences, and civil damage awards. It is further agreed that the offeror agrees to abide by all conditions of the solicitation, notice of award, and/or purchase order(s) of APS and that the person signing this proposal is duly authorized to propose on behalf of the offeror.

9.6 Failure to provide an online submission with correct information may result in the rejection of the proposal. If further information is required to demonstrate responsibility, such as providing copies of licenses or permits (other than those mentioned in 6.4), certificates, etc., the offeror will be notified, in writing, and given five (5) days from notification to supply such information.

9.7 After the closing date and time, Procurement Services will conduct an administrative review of all proposals received to determine responsiveness. Proposals that are deemed to be responsive will be evaluated. Proposals that are deemed to be non-responsive will not be evaluated or considered for award

10.0 GENERAL REQUIREMENTS

10.1 All work conducted must be in accordance with all local, state, and federal guidelines.

10.2 CONTRACT EXCEPTIONS:

The terms and conditions contained in this solicitation comprise the contract terms and conditions proposed by APS. APS does not intend to make changes to those terms and conditions, unless necessary to clarify the scope of work and/or technical requirements.

In order for any exceptions to be considered by APS, you must submit your exception request on the contract exception form through the Bonfire System by the due date as noted in the Submission Requirements.

10.3 WMBE OUTREACH EFFORTS:

The Atlanta Public Schools’ Equity and Social Justice Supplier Diversity efforts aim to eliminate discrimination against businesses on the basis of race, color, national origin, and gender. You may access the Atlanta Public Schools’ Equity Policy by clicking the link.

Below:

Atlanta Public Schools' Equity Policy

If your firm plans to use subcontractors for this project, the following organizations may help with identifying qualified Minority and Female-Owned firms:

GMSDC

NAMC

The National Association of Women in Construction National Association of Black Women in Construction Georgia Hispanic Chamber of Commerce City of Atlanta Supplier Diversity https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsimbli.eboardsolutions.com%2FPolicy%2FViewPolicy.aspx%3FS%3D36031014%26revid%3Dzx4bAX2FzpkDqx2XNgwicQ%3D%3D%26PG%3D6%26st%3Dequity%2520policy%26mt%3DExact&data=05%7C02%7CLorenzo.Presley%40atlanta.k12.ga.us%7Ccbdd7e0e56774fb7613e08dcb183f0a4%7C0d95ef40a0dd431890985e10f876f635%7C0%7C0%7C638580427456949953%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=F2fxBhVBYkXr5adqaduAm%2FcqtkUOlQnyrZlbxO%2FgHM8%3D&reserved=0 https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgmsdc.org%2F&data=05%7C02%7CLorenzo.Presley%40atlanta.k12.ga.us%7Ccbdd7e0e56774fb7613e08dcb183f0a4%7C0d95ef40a0dd431890985e10f876f635%7C0%7C0%7C638580427456960556%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=B42Z0uYf98hOgKnpYrOj%2FbKUzikBmF5N8YQRJ%2F1aI6s%3D&reserved=0 https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnamcatlanta.org%2F&data=05%7C02%7CLorenzo.Presley%40atlanta.k12.ga.us%7Ccbdd7e0e56774fb7613e08dcb183f0a4%7C0d95ef40a0dd431890985e10f876f635%7C0%7C0%7C638580427456970538%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=ZvGUrySy7O%2FEEcEZVtdesZwCWKVFrIJVNUUlV7PV3HY%3D&reserved=0 https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnawic.org%2F&data=05%7C02%7CLorenzo.Presley%40atlanta.k12.ga.us%7Ccbdd7e0e56774fb7613e08dcb183f0a4%7C0d95ef40a0dd431890985e10f876f635%7C0%7C0%7C638580427456980948%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=aEU%2BsmoPD%2FXdRJMlZc8urRPusmILsGq5%2Fsf2ZOWns1I%3D&reserved=0 https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnabwic.org%2F&data=05%7C02%7CLorenzo.Presley%40atlanta.k12.ga.us%7Ccbdd7e0e56774fb7613e08dcb183f0a4%7C0d95ef40a0dd431890985e10f876f635%7C0%7C0%7C638580427456992018%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=Y1y5MyRTi2LrV3IKKFJBqzfUjkuXXFOXGPqUA2VWt7A%3D&reserved=0 https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fghcc.org%2Fen%2F&data=05%7C02%7CLorenzo.Presley%40atlanta.k12.ga.us%7Ccbdd7e0e56774fb7613e08dcb183f0a4%7C0d95ef40a0dd431890985e10f876f635%7C0%7C0%7C638580427457002409%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=yaP5CHe6V8XONE33WEOrElqBSzGsWnj2jk0UMv2FlbU%3D&reserved=0 https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fatlantaga.gob2g.com%2F&data=05%7C02%7CLorenzo.Presley%40atlanta.k12.ga.us%7Ccbdd7e0e56774fb7613e08dcb183f0a4%7C0d95ef40a0dd431890985e10f876f635%7C0%7C0%7C638580427457012458%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=UE705iWfIqXfsUOEvNzTr0MAGeQf1mb7iVOtChWsB1s%3D&reserved=0

You may also seek assistance from the Atlanta Public Schools’ Supplier Diversity. You may access information regarding APS Supplier Diversity by clicking the link below:

Supplier Diversity

10.4 Vendor Conduct

10.4.1 Vendor’s employees are expected to exhibit professional, courteous conduct and an appropriate appearance at all times. Any conduct or appearance deemed inappropriate by an APS representative will be grounds for removal from APS property.

10.4.2 A vendor’s employees are to be respectful to faculty, students, and visitors;

these employees are prohibited from fraternizing with these groups. Flirtatious behavior, soliciting monies, names, addresses, and other such inquiries will cause for the employee to be removed from the premises.

10.4.3 Also, radios or audible music are not allowed at worksites.