Proposed Business Processes
Descriptions
The proposed process for carrying out the annual roll forward is to complete key tasks in sequence in order to deliver continuous timetabling services to end users:
| Date | Service | Process |
|---|---|---|
| 26 Jan 2013 | Timetabling Database (SDB) | The timetabling unit will take a snapshot of the 2012/13 database and create a clean image of information to be rolled forward. |
| TBC | Scientia Transfer | The clean image must be converted to a 52 week equivalent by Scientia's process to remove excess weeks and pass back for loading into 1314. |
| 4 March 2013 | Timetabling Database (SDB) | The timetabling unit must create and provide a clean SPF (Syllabus Plus File) containing all the information required for the roll forward to establish a new Timetabling instance. |
| 4 March 2013 | Timetabling Enterprise Applications | The Enterprise Applications (Timetablers, Course Planner, Reference Data Manager) must be rolled out for use by the Timetablers and Gatekeepers |
| 4 March 2013 | Authorisation Manaager | Access will be granted to the upcoming year's applications and access to the current year's applications will be restricted to avoid incorrect entry of information into the current year's timetable. |
| 4 March 2013 | Web Timetables and Web Room Booking (Staff and student) | These three web applications must be launch in order for end users to access timetable information and request rooms. |
| End of February | Timetabling Database (SDB) - Historic Year | The oldest database must be removed from the Live servers in order to keep the resource profile of the Timetabling service at a constant level (please note this process will not be required until Feb 2015) |
26 Aug 2013 | MyEd Launcher channel | The MyEd launcher channels must be repointed to the new academic year's instances of web room booking and web timetables on the day the new database comes into effect. |
| 26 Aug 2013 | Remove old Web Applications | Web Timetables, Web Room Booking and Book Study Space applications for the previous year must be removed from the Live service (historic timetabling data will only be available via the Enterprise tools). *Please note that Web Timetables 2012/13 may be left in place to allow an interim solution for publishing timetables associated with the DRPS. |
| 26 Aug 2013 | Onelan replacements, PADS interface | The outgoing interfaces must be switch to using the new database on the effective date of the change to the new database. These interfaces only present data for "today" so they must be switch when one database runs out and another starts. |
Process Maps
Context Diagram
