Project ISIDORE

1
Project ISIDORE
Presentation to Colleges IT Group Tuesday 14th
May 2002
2
Project ISIDORE

• Background to project
• Key cross functional processes not very
  efficient/ dependent on paper
• Existing systems not bad but not integrated and
  not widely available
• Key information can be out of date
• Planning for the future difficult - particularly
  the collation of reliable data

3
ISIDORE the name

• Isidore of Seville(560-636) - Archbishop of
  Seville(600-636)
• Great believer in education
• Compiled an encyclopaedia of all knowledge which
  remained an important reference book
• ISIDORE the project will compile an encyclopaedia
  (of sorts) about students.
• ISIDORE could stand for Integrated Student
  Information and Data Recording Exercise

4
Project ISIDORE - processes

• Undergraduate admissions
• Graduate admissions
• Graduate studies administration
• Matriculation and the University Card
• Examination entries and results
• Degree conferment administration
• Planning inc returns to HEFCE, HESA, QAA, First
  Destination

5
Project ISIDORE Current systems

• Ingres Graduate Admissions module
• Ingres Student Records module
• Undergraduate admissions system plus links to
  UCAS
• Access Dossier system for graduates
• Access Submissions system for graduates
• University Card system
• Examinations OASIS database
• Examinations Invigilators database
• Examinations examiners fee payments system
• Other minor tactical local systems

6
Project ISIDORE Other key considerations

• Most other large universities now have an
  integrated software package in place or being
  implemented
• Cambridge also have a project running
• Oxford is complex and implementation will take
  some time during which the world will change
• Greater efficiency should produce benefits for
  all concerned more concentration on the key
  decisions less on the mechanics of the process
• Concentrate on changing the processes to fit the
  system not vice versa

7
Project ISIDORE Next Steps

• Define current cross functional processes to a
  level of detail. Involve the participants in the
  definition process. Complete by Sept 2002.
• Define areas for improvement and agree if
  possible for each cross functional process tbe
  desired To Be process
• Investigate the market for potential package
  suppliers
• OJEC Notice by July 2002 with 2 phase procurement
  complete by Spring 2003
• Plan implementation in detail including add ons,
  interfaces, detailed processes.

8
Project ISIDORE Project organisation

• Run under PRINCE
• Project Board
• Project Manager
• Project Consultative Group
• Based in Banbury Road with OSIRIS
• Various other communication forums

9
Project ISIDORE Key deliverables

• Integrated software package to replace current
  Central systems
• New system available to local college and
  department administrators if required
• Cross functional/ cross organisational processes
  re-engineered to fit in with new system and to
  improve efficiency. Pilot approach for colleges/
  departments to update own data.
• New processes for transcripts, annual
  registration, new UCAS system Hercules