Enterprise & Vertical
Reporting
The Challenge:
How do you design a real time data collection system that is scalable for states and districts that is easy to use
■ Data is in motion: Students are constantly
enrolled and dropped, change courses and enter and exit programs.
■ Districts/states need the ability to see
information within minutes of entering, modifying, or deleting the data.
■ The entire process should be invisible to users.
■ Errors need to be corrected at the source for
increased data accuracy.
■ Project must have an executive sponsor or at least a data champion.
■ Need to have staff dedicated to supporting the
deployment – should not just depend on the vendor to do it all.
■ Project Manager-District/State and Vendor
■ Create a project team to promote buy-in
■ Conduct regular status meetings
■ Create a project scope and stick to it.
■ Scope changes can impact your production dates.
■ Determine what documentation is needed up front.
■ How do districts give permission to vendors to pass and receive data is not the ODS?
■ How does a district notify if they want to drop out
of a data collection activity?
■ Example
■ Determine version of the specification
■ Don’t keep switching – vendors have their own development processes
■ Other standards required?
■ EdFi
■ CEDS
■ Create a SIF Profile Document
■ Determine if you need extended elements
■ Notify your SIS vendor!
■ Communicate early and often
■ Project Manager-District/State and Vendor
■ Create a project team to promote buy-in
■ Conduct regular status meetings
Basic Data Collection
Components
■ Student Information System
■ SIF Agent
■ REST API
■ ODBC/CSV
■ Student Identifiers [writeback]
■ Assessments
■ Multiple sources
■ No SIF agents to dump data
■ Other sources:
■ Photos
■ IEPs, AYPs, OMG
■ A SIF 2.x agent isn’t always the best way to gather data to move data to an ODS
■ Paradigm Shift Example:
■ Food Service is a subscribing application
■ What data do you need to collect?
■ How do you get that data into an ODS?
■ Gathering data via SIF can help normalize data
■ Feed data to an ODS that is SIF aware
■ Real Time data – is always in motion
■ Need a place/method for snapshots or
historical data
■ State reporting is date driven
■ Importance of SIS vendor collaboration
■ Real time data is not enough in the education ecosystem. To make this data truly effective validation of the data is added to the mix.
■ Gathering the relevant data from all of the
various sources can be challenging.
■ Entry/Exit Dates
■ Photos
■ Attendance
■ Create a SIF profile to document the Objects and elements you want to collect. Example
■ Compare with data you currently collect [state level]
■ Throw out the stuff you really don’t need
■ Determine mandatory and optional requirements
■ Make sure the data you collect is “clean”
■ Entry exit dates
■ Grade codes
■ LEA codes
■ State codes
■ Districts can mirror state data collection business rules
■ There are different ways of handling errors:
■ Staff can review a report and update their SIS
■ Vendors can be asked to assist
■ Key to data clean up is to correct the error in the
SIS so data changes can flow to the ODS
■ Create a best practices document for your users.
■ What errors are common problems?
■ Can be free form fields or data entry in field
that are not validated by the vendor
■ User Reports
■ Can be created with existing tools using data
from ODS
■ Create a template or requirements document
for the creation of new and existing reports Meet with your stakeholders to determine their expectations
■ Know the data source
■ Portal Access to Instructional applications
■ Single-Signon
■ Identity management
Example 2: Illinois Shared
Learning Environment [ISLE]
End-User Facing Interfaces Tenants (School Districts) Backend Interfaces & Services
Tenants (School Districts)
Data Collection and Validation)
■ Acting as a K12 federation operator and service provider, the IlliniCloud established three foundational services for the K12 community:
• Data Services
• Identity Services
• Presentation / “Portal” Services
■ Lowering the Bar for Adoption: services require little to no modification of
existing data and identity processes in the districts
3rd Party Service Providers & Other Federations Districts (1 .. N) using Active Directory Districts (1 .. N) using eDirectory Districts (1 .. N) using LDAP/Kerberos Tru st Proxy IDP/SP School District Metadata Non-School District Metadata
inCommon Google 4 Edu Other Service Providers Read-Only Query Functionality Workforce Development Users/Orgs Federated Central Service School District Users/Orgs SAML 2.0 OAuth OpenID Native Directory Interface Tru st
SP SP Google for Ed InCommon Federation Metadata IDP IlliniCloud K12 Federation Metadata Publish Subscribe SP SP K12 Service Providers K12 District X Directory Authoritative Directory Source K12 District Y K12 District Z
AD | LDAP | Kerberos | eDirectory
Single Sign On (SSO) Enabled
Custom State Applications
External Federations & Service Providers
SP Custom District Applications
Local K12 Identity Services
SP SP
SP
Discovery Ed SuccessNet Any SP via SAML
Key
SSO = Single Sign On SP = Service Providers
[email protected] Illinois Open Education Resource Search Educator Dashboard Tab Bar Isle Apps District Apps EC/PK Apps My Page Tab Bar Isle Apps Tenant Apps Office Apps My Page [email protected] Illinois Open Education Resource Search Educator Dashboard Tab Bar Isle Apps District Apps Admin Tools My Page [email protected] Tab Bar Isle Apps Grade 8 Apps Office Apps My Page
General Purpose Login Process
Tenant Portal-Manager Controls
•Portal Skin Customizations