Skip Navigation
small NCES header image

The Personnel Exchange

Past Exchange Summary Reports -

Return to Past Exchange Summary Reports

Initiating Agency:
Utah Department of Education

Cooperating Agencies:
Oregon Department of Education

Dates of Exchange:
September 7-9, 2004

Title of Exchange:
State Student Identification Systems


As is the case in many other states, with the advent of No Child Left Behind (NCLB) and state mandated accountability reporting, it has become apparent that Utah must begin assigning a unique statewide student identifier to all data being reported to the state from the district level. This is especially important as individual students are followed longitudinally for the purpose of accountability reporting and educational research. Such an ID would remain with he student for their entire stay within the Utah public education systems. Utah is planning on having its own SSID fully function by July 2005 for all data to be submitted to the state during the 2005-06 school year and beyond.

The Utah State Office of Education reviewed the unique student identifier systems of a number of states and felt that both the design and the implementation of Oregon's SSID system matches most of Utah's requirements. A personnel exchange would allow Utah staff to see firsthand how Oregon manages unique statewide student identifiers and their integration with other statewide education data.

Three staff from Utah visited Oregon. Utah staff were able to meet with Gary Ellwanger and several of his staff. Larry, his dba, walked us through the collection times for district and school information. He gave us the history behind the student identifier project.

  • The student identifier is an auto-incrementing numeric with a check-digit. Larry and two developers were able to do a JAD session and finish the initial project specs in 90-days. Prior to this, student tests were the only student-level collection mechanism.
  • The tools that were used in development were PowerDesigner 6.15 (Sybase). Also, several trigger tools were used.
  • In Portland, there are up to 1000 suggested matches for the student ID. Eugene has up to 500 suggested matches.
  • Oregon has succeeded where many a SEA has failed. They are able to have the Ed Specialists drive the process for data ownership. They take responsibility for definitions and business processes.
  • Their current database has over 35GB using RAID 0 striped and Raid 5. Will probably be going to a hyperthreaded box next.
  • Security - Oregon is using SSL certificates on HTTPS. They are also sending data back and forth using encrypted FTP. A VB program does the encryption.
  • After the session with Larry, we were able to meet with the Web Development Team and walk through the UI.
  • All of this information was incredibly useful. Heading down the statewide student identifier path is a difficult task. This trip has shaved some serious time from the development process.

    Utah Department of Education Contact:

    Randy Raphael, rraphael@usoe.k12.ut.us

    Download and print report (73 KB) PDF File


    Would you like to help us improve our products and website by taking a short survey?

    YES, I would like to take the survey

    or

    No Thanks

    The survey consists of a few short questions and takes less than one minute to complete.