AzEDS Updates


May 17th, 2017

UPDATE: SPED Integrity Rule -40055

The Exceptional Student Services Team has sent out the following alert via the ESS Data Management Listserv:

On May 22nd, integrity rule -40055 will revert back to being an integrity failure (error). For more information on the original change, please refer to the email sent on April 7th, 2017 below. For more information on SPED exit codes, please refer to the most recent SPED Exit Validations Matrix.

Please contact [email protected] if you have any questions.

Posted in AzEDS Updates, Integrity |
May 2nd, 2017

EOY FY17 and FY18 for AzEDS

Year end is quickly approaching, here is a summary of EOY dates:

  • FY17 data can be submitted until July 14th at 5pm via AzEDS 2.3 API for ALL LEAs (not just AOIs)
  • FY18 data can be submitted on July 1st via AzEDS 3.0 API

This is follow-up from the recent ASCUS meeting to confirm the dates and who can submit until July 14th, which has been reconfirmed as ALL LEAs. Integrity and Aggregation nightly processing priority will be FY17 data and after that completes, the plan is to run Integrity for FY18 data.

Posted in API and Data Processing, AzEDS Updates, Integrity, News from IT |
May 2nd, 2017

UPDATE: Integrity Rule -21001 incorrectly failing for students with “SC,” “C,” and “P” withdrawal codes

UPDATE: A resolution for this bug will not be released the week of 5/11 due to the School Finance data capture deadline. Please be aware that -21001 is a Non-Payment rule, therefore a student failing ONLY -21001 will still be eligible for ADM.

AzEDS Integrity Rule -21001 states, “Every membership needs an exit date and reason. Please submit a Year End Status or Withdrawal code and exit date.”

The AzEDS Team has identified that students with Withdrawal codes of “SC,” “C,” and “P” are incorrectly failing this Accountability Non-Payment rule.

Development is also researching the possibility that other withdrawal codes are invalidly failing this rule. We will be updating this post with these other scenarios and an ETA for a resolution.

Thank you for your continued patience.

Posted in AzEDS Updates, Bugs, Integrity |
April 21st, 2017

Integrity Rule Changes releasing April 20, 2017

On 4/20/17, Development will release the Integrity rules listed below. For a final list of FY17 rule changes, please see FY17 Integrity Rules changes posted under “AzEDS Reference \ Integrity Rules \ Integrity Rules Reference”, here is a link for easy reference.

Membership: AzEDS Integrity Rule 10071 states: “Absences must be submitted instead of attendance minutes for this student.”

AzEDS Integrity Rule 10075 states: “Attendance minutes must be submitted instead of absences for preschool and AOI students.”

AzEDS Integrity Rule 10096 states: ‘Attendance minutes are required when the field “In Attendance” is reported. Attendance minutes cannot be null or zero.”

Posted in AzEDS Updates, Integrity, Releases |
April 13th, 2017

Integrity Rule Changes releasing April 13, 2017

On 4/13/17, Development will release the Integrity rules listed below. For a final list of FY17 rule changes, please see FY17 Integrity Rules changes posted under “AzEDS Reference \ Integrity Rules \ Integrity Rules Reference”, here is a link for easy reference.

Accountability non-payment: AzEDS Integrity Rule 21000 states: “Incorrect Year End Status Code submitted for this student’s grade level.” This is a new rule

AzEDS Integrity Rule 21005 states: “Summer withdrawals other than S7 are only valid between July 1 and the first instructional day.” This is a new rule

AzEDS Integrity Rule 21007 states: “This student has been reported without a home language.” This is a new rule

AzEDS Integrity Rule 21008 states: “This student has been reported without a race.” This is a new rule

ELL: AzEDS Integrity Rule 30000 states “If there is an ELL Program overlap for a single language need, then report the discrepancy as an error.” This rule was incorrectly failing is failing even though there is no overlapping ELL need and programming.

SPED: AzEDS Integrity rule 40050 states “If a student with a SPED Need Participation does not have one Federal Primary Need indicator and receiving SPED Services, then report the discrepancy as an error.” This rule was incorrectly failing when a student had multiple concurrent Needs with the same Entry Date, and the Primary Need was withdrawn before the non-Primary Needs.

AzEDS Integrity rule 40055 states “If a student’s SPED Exit Reason does not match the student’s regular membership Year End or Withdrawal Membership status, then report the discrepancy as an error. This rule needs to re-run beginning April 1st of the fiscal year to capture mismatches and not reported. (see attachment for SPED to Withdrawal Codes matrix)

1. If a student has all of the following four values then it can run before April a. Withdrawal/Year-End exit value (Code/Reason) b. Withdrawal/Year-End exit date c. SPED Exit Code (Reason) d. SPED Exit Date 2. If any of these elements are missing, then this rule should only run after April 1 for students.” Error severity was updated to Informational from Error.

AzEDS Integrity rule 40057 states “Only one Main SPED school is allowed at a single point in time. One or more schools have also identified themselves as the Main school providing services. Please contact ESS Data Management or School Finance to determine which school(s) have concurrently indicated the Main SPED School designation. Please collaborate with these school(s) to determine the correct Main SPED School designation.” Error message was updated to: exclude “or School Finance” from ”Please contact ESS Data Management or School Finance”

AzEDS Integrity Rule 40065 states “Need categories that must exist for MD to be valid are: Two or more of HI, MOID, OI, VI; or one of HI, MOID, OI, VI and at least one of ED, MIID, SLD.” If a student has needs that satisfy the first scenario of “two or more HI, MOID, OI, VI,” and then withdraws from one to enter another need to satisfy the second scenario of “one of HI, MOID, OI, VI and at least one of ED, MIID, SLD” then this student would incorrectly fail this rule.

AzEDS Integrity Rule 40069 states “Student SPED participation must be within a membership at a school. If each day of SPED program participation does not have an enrollment at a given school in a given Fiscal Year, then report the discrepancy as an error.” Error message was updated to: A student SPED participation must be within a valid membership at a school. Please note the error may be caused by student not having valid membership due to missing DOR, Grade or Track.

AzEDS Integrity Rule 40070 states “MDSSI requires the following categories to co-exist: severe HI and severe VI or one of severe HI, severe VI and another severe disability (group B): A, EDP, MOID, OI, SID.” This is a new rule.

Posted in AzEDS Updates, Integrity, Releases |
April 4th, 2017

Final list of FY17 Integrity Rule Changes (as of March 31, 2017)

The final list of FY17 Integrity Rules either new or changing rules is complete and posted under “AzEDS Reference \ Integrity Rules \ Integrity Rules Reference”, here is a link for easy reference.

** The only exception would be technical issues that require a fix; even for these if possible the AzEDS Team will communicate in advance what the issue is and when the fix is expected.

Posted in AzEDS Updates, Integrity |
April 4th, 2017

AzEDS Performance Status Update

On 4/3/2017, ADE IT transitioned the AzEDS servers back to the previous Azure Model in order to resolve the intermittent performance issues. Following this maintenance window, AzEDS performance has now improved across the board to the original sustained levels. Data can now be submitted with consistent server acceptance.

We thank you for your hard work and continued patience throughout the past week.

Posted in API and Data Processing, AzEDS Updates, Maintenance, News from IT |
March 22nd, 2017

UPDATE: AzEDS Performance Issues

Update 3/30/17: ADE IT has been making progress with Microsoft on the AzEDS performance issue. The AzEDS Team is continuing to monitor closely and will provide further information once available. We thank you for your continued patience and apologize for the inconvenience.

Update 3/24/17: The AzEDS performance issue is currently in an escalated state and being addressed with Microsoft. We are continuing to monitor this issue closely.

The AzEDS REST API will encounter some intermittent performance issues over the next few days. ADE IT is currently engaging Microsoft to resolve this and will provide more information as soon as it is available.

Thank you for your continued patience.

Posted in API and Data Processing, AzEDS Updates |