ULMS Project Timeline
- brandon dudley (Unlicensed)
- Mallory DeBartolo (Unlicensed)
Upon contract signature | CSU project manager, implementation team, institution contacts, and IT |
| resources established |
| Ex Libris implementation team allocated |
| Communication plan developed |
| Detailed implementation plan developed |
| "Getting Ready" kit review, including data preparation |
October 2015 | Planning phase ‐ kickoff meeting |
| Production environment provisioned to be populated with the data |
| from 3 "vanguard" member institutions (to be used for planning) |
| Standard sandbox environment provisioned (to be used for training) |
| CSU reviews recorded training |
| Weekly project status/functional Q&A sessions between CSU and Ex |
| Libris implementation teams begin and continue throughout project |
November‐December 2015 | Consultative review of Alma data model, workflows, migration and implementation details, to facilitate shared practices and policy planning |
late December 2015‐January 2016 | Winter break |
| Initial Alma test load/data migration to production environment with |
| data from 3 "vanguard" member institutions and network zone begins |
| Initial Alma configuration for 3 "vanguard" member institutions and |
| network zone begins |
late January‐February 2016 | Initial Alma test load/data migration to production environment for 3 |
| "vanguard" member institutions and network zone delivered to CSU |
| Initial Alma configuration for 3 "vanguard" member institutions and |
| network zone delivered to CSU Initial Primo configuration and data load |
| delivered for 3 "vanguard" member institutions |
February 2016 | Workflow and data review by CSU |
| Configuration refinements |
| Planning for migration refinements |
March 2016 | Full implementation kickoff meeting |
| Onsite meeting including analysis sessions |
| Production environment provisioned for all member institutions |
| CSU reviews recorded training (continuation and/or broader audience) |
| Go live readiness checklist introduced (monitored on an ongoing |
| basis for remainder of project) |
April 2016 | Preparation for full test load/data migration to production environment |
May 2016 | Full test load/data migration to production environment begins – all |
| member institutions and network zone |
| Initial Alma configuration begins – all member institutions and network |
| zone |
June 2016 | Begin 3rd party integrations |
July 2016 | Full test load/data migration to production environment delivered to |
| CSU – all member institutions and network zone (early July) |
| Initial Alma configuration delivered to CSU – all member institutions |
| and network zone (early July) |
| Full Primo configuration and data load delivered to CSU – all member |
| institutions (late July) |
August 2016 | Workflow and data review by CSU (ongoing for remainder of project) |
| Onsite Workshop (1 of 2) |
| Configuration and integration refinements (ongoing for remainder of |
| project) |
| Planning for migration refinements (ongoing until start of cutover) |
September 2016 | Resource sharing set up |
| Prepare for San Marcos and Sacramento integration into CSU lending |
| environment |
November 2016 | Certification training |
December 2016‐ January 2017 | Winter break |
January 2017 | Onsite Workshop (2 of 2) |
March 2017 | Library staff training |
April-May 2017 | Cutover load/data migration begins – all member institutions |
| Library staff training |
June 2017 | Go Live with Alma and Primo Relink existing Alma sites (San Marcos and Sacramento) to the CSU network zone. |
June-July 2017 | Alma health check |
August 2017 | Switch from implementation to ongoing support |