Arizona Department of Education Executive update Presented to: - - PowerPoint PPT Presentation

arizona department of education executive update
SMART_READER_LITE
LIVE PREVIEW

Arizona Department of Education Executive update Presented to: - - PowerPoint PPT Presentation

Arizona Department of Education Executive update Presented to: Information Technology Authorization Committee May 24, 2017 Mark T. Masterson Chief Information Officer First and foremost AzEDS data quality has provided the State of Arizona


slide-1
SLIDE 1

Presented to: Information Technology Authorization Committee May 24, 2017 Mark T. Masterson Chief Information Officer

Arizona Department of Education Executive update

slide-2
SLIDE 2

First and foremost

AzEDS data quality has provided the State of Arizona an annual cost savings of $40M compared to SAIS

slide-3
SLIDE 3

AzEDS in Azure performance

100 200 300 400 500 600 700 Response in Milliseconds Millions of Transactions

  • ADE processes an average of 6.5

million transactions a day through the AzEDS system. Leveraging Azure elasticity, ADE was able to scale to meet that demand and maintain response times despite increases in transaction counts.

  • Average transaction

response time is

  • 257milliseconds. Response

time is the sum of actual processing time and the time the session spends waiting on availability of resources.

slide-4
SLIDE 4

AzEDS proactive management

ADE monitors 24/7 using Azure Application Insights and Microsoft System Center Operations Manager (SCOM) identify when system

  • perations are abnormal or slow. Alerts

are generated to the Dev/Ops team when Key Performance Indicators (KPI) are exceeded, and are visualized on the big screens in the operations room. Synthetic transactions simulate a user’s perspective.

slide-5
SLIDE 5

Manage Student Data (Memberships, SPED, ELL, etc)

Operational Data Store

“One Stop Data Shop”

Manage Organization Entities (Districts, Charters, etc)

OEMS

Enterprise CT E ESS MCESA Accountability Assessments

AzEDS

SAIS - 915 Process (FY16, FY15, FY14) SAIS – Student Details

20+ Additional Agency Applications

Multiple Copies of Student Data *Data integrity and quality at risk

A picture of today

1 2 3 4 5 6

Payments (APOR/CHAR) Budgets

School Finance Systems Note – Not depicted but also part of current state are:

  • Staff / HQT – applications currently pulling data

directly and will streamline in future state

  • STC in AzEDS
  • Calendar (Enterprise)

6 7

AZDash

External Assessment Data Sources (AZMerit, ACT, Stanford, Gold, …)

Health & Nutrition

Azella & AIMS only

slide-6
SLIDE 6

Manage Student Data & Student-Teacher-Course (STC) (Memberships, SPED, ELL, etc;)

Operational Data Store

“One Stop Data Shop”

Manage Organization Entities (Districts, Charters, etc)

OEMS

CT E ESS MCESA Accountability Assessments

AzEDS

Streamline Agency Applications (TO BE)

Future State

NEW School Finance Systems (TO BE)

AZDash

External Assessment Data Sources (AZMerit, ACT, Stanford, Gold, …)

Health & Nutrition EdFacts

Payments Budgets

Manage Staff Data

Staff (tbd)

Reporting Visualizations (TO BE) ER Studio & Data Dictionary

slide-7
SLIDE 7

2017 AzEDS high-level architecture

slide-8
SLIDE 8

AzEDS FY18 development $1,500,000

  • 4 main deliverables for FY 2018 in AzEDS

– Single-source Agency data, and decommission legacy apps via Operational Data Store ($700,000) – LEA vendor Calendars submissions via the AzEDS API ($300,000) – ESSA requirement for Financial Transparency data collection ($200,000)

  • New LEA Finance/Teacher API
  • Requirements, design and prototype only

– Self-servicing LEA user interface and Agency approval workflow for Organizational Entity Management System (OEMS) ($300,000)

slide-9
SLIDE 9

APOR/CHAR requirements $500,000

  • Develop high-level requirements for new payment

system – Includes breaking down the existing APOR and CHAR (20+ processes and steps for monthly payment alone) – Annual payment separate process – Create statute-based modeling for proposed replacement – Automate existing manual processes

  • Decouple APOR/CHAR from legacy Enterprise
slide-10
SLIDE 10

FY18 AELAS Maintenance $5,3000,000

  • AzEDS Support

– User bugs and ticket analysis and fixes to resolution – 2 API releases and enhancements to rules, portal, reports, tools, etc

  • AZDash
  • ADEConnect
  • Data migration and State/Federal reporting

– Design support for applications migrating to ODS – Analysis support for Program area reporting to Feds

slide-11
SLIDE 11

FY18 AELAS spending plan

AP APOR/CHA HAR r requir irements $ $ 500, 500,000 00 AzEDS DS $ $ 1,500,000 AE AELAS AS Maint ntenanc nance a and O Operat atio ions ns $ $ 5, 5,300 300,00 000

– AzEDS Support $1,200,000 – Program Support Office $ 500,000 – AZDash $ 600,000 – AELAS Network Operations $ 700,000 – ADEConnect $ 450,000 – AELAS Strategic Oversight $ 320,000 – School Finance Support $ 250,000 – Data Migration & State/Fed Reporting $ 630,000 – Hardware and Software $ 650,000

TOTA TAL $ $ 7,300,000

slide-12
SLIDE 12

What was tabled in FY17

  • Integrating existing systems that use SAIS for data
  • New dashboards for AZDash
  • Adequate software/hardware needs for AELAS

development

  • APOR/CHAR rewrite
slide-13
SLIDE 13

On-going challenge for AELAS success

  • Insufficient and Unpredictable Funding

– Approved funding each year has not approached each annual ask – Maintenance funding each year has not been appropriated

slide-14
SLIDE 14

FY 2017 AELAS closed projects

Project Name Accomplishments

ADE Online Certification (OACIS) PIJ ED12003

  • OACIS Public Portal; value – The Certification public portal allows

educators, parents, and the general public to access information regarding an Arizona educator’s certification

  • Initial code (only) for OACIS Public Portal and Educator Portal
  • Project closed in Red status with end of contract period June 30,
  • 2017. Due to vendor:
  • Missing required scope deliveries
  • Consistent missing of Delivery milestones
  • Code delivered as compiled, not source as per contract

AELAS SIS Opt-In PIJ ED14005

  • 44 current LEAs are on the State supported Student Information

System

  • LEA count peaked during FY17 due to JLBC condition to Cap total

implementations to those active and in pipeline at the start of FY17

  • 74,000 students being managed and reported through State SIS
slide-15
SLIDE 15

Mark T Masterson Chief Information Officer (602) 542-3542 Mark.Masterson@AZED.gov

Thank You

slide-16
SLIDE 16

AELAS Development Reference Slides

slide-17
SLIDE 17

Single-source Agency data/decommission legacy $700,000

  • Decommissioning of legacy platforms, Enterprise and SAIS

– Reduce redundancy, quality risks and cost of maintaining 2 systems in parallel – Build additional 3-5 Data Marts for specific Agency divisions (5 complete), supporting Program Area application migration – Migrate 30 legacy applications to utilize Entity and Student Data via ODS – Enhance ODS ED-ORG domain to enable the shutdown of Enterprise entity management

  • Build out Ed-Facts reporting using new ODS as single source for all

Federal and State Reporting (180 reports)

  • Extend AzEDS ODSto increase ability to be single source of data for all

Agency data needs that cross multiple Program Areas

– Build new School Finance domain – Build new Average Daily Membership (ADM) domain – Enhance Staff domain (teacher performance data)

  • Build 5 dimensional data cubes for analytics reporting
slide-18
SLIDE 18

AzEDS LEA vendor (16) Calendar via AzEDS API $300,000

As Is: LEAs have to setup a Calendar in their Student Information System (SIS) and in Enterprise (double entry). To Be: Streamlined process that reduces LEA burden by enabling the calendar setup in a SIS to be sent to the state via AzEDS API. Initial API development is complete, remaining effort for Integrity rules, reports and workflow for School Finance approvals.

Student Information System (SIS)

LEA Staff / Account Analyst

Manually Enter Calendar 2 Systems

DUPLICATE ENTRIES

 Additional Time due to duplication  Higher risk of Error

State Legacy System - Enterprise

11 Steps in Setup Process, Est 25 plus Data Entry Fields

Student Information System (SIS)

LEA Staff / Account Analyst

Manually Enter Calendar 1 System  Remove duplication steps  Reduce risk of Error

AzEDS Platform

Automation via API

BEFORE AFTER

slide-19
SLIDE 19

AzEDS LEA Finance/Teacher API $200,000

  • Develop and obtain high-level scope and business

needs to support financial transparency data gathering and reporting

– ESSA requirement

  • Estimate development and on-going maintenance

timeline and costs to support requirements

  • Complete initial prototype of solution
slide-20
SLIDE 20

OEMS user interface and approval workflow $300,000

  • Develop new user interface for LEAs to self service

their entity organization and contact information

  • Develop workflows to enable ADE staff to approve,

and lock down, the changes submitted by LEAs

slide-21
SLIDE 21

Challenges from disconnected silos

  • Vendors built upon old non-supported technology platform
  • Poor code practices

– No code reuse across application, – no data services – No code libraries

  • Cross domain applications required linked servers or

database replication

  • Limited interoperability between core systems
  • Data Integrity and Aggregation for school finance

payments a multi-day operation

  • No common definition of data elements
  • Yearly database snapshots to capture historical data
slide-22
SLIDE 22

Components of AELAS AzEDS

  • 4-10M transactions

daily

  • Returned $40M back

to the State due to accuracy of systems and rules

  • Returns $40M each

and every year going forward

AzEDS Data Interchange & User Interface AzEDS Integrity Rules Aggregation Calculation Engine Student, STC, Staff

LEAData Exceptions / report data Bulk Data Interface

Verification Reports

Ed-Fi REST API 2.1

Integrity Reports AzEDS Portal

Identity Search/Split/Merge UI Exception REST API Membership STC Accountability

SPED

ELL Support Prorgram

ADM Reports

Admin UI

Aggregation/ Limiting

Admin UI AzEDS

R

664 LEAs Student Information Systems (SIS)

slide-23
SLIDE 23

Components of AELAS Operational Data Store

slide-24
SLIDE 24

Components of AELAS Operational Data Store

Data Marts

Agency ODS Legacy School Finance Payments System Student Counts, ADM AzEDS Student, STC, Staff, ADM EdOrg/Calendar ETL OEMS HQT Enterprise Education Organization Staff School Calendar NAU Gear Up CTE AZ Dash MCESA Assessments S t u d e n t A s s e s s m n e t s

Our design and implementation to-date and with continued investment will remove these silos.

slide-25
SLIDE 25

Components of AELAS AZDash

Longitudinal student data available next business day after data submission from School/LEA

slide-26
SLIDE 26

AZDash Application

slide-27
SLIDE 27

Components of AELAS School Finance payment system

Payments

School Finance Payments

CSF Payments IIF Payments APOR Payments CHAR Payments Budgets

Student Counts, ADM AzEDS

Payment Reports Payment UI