Table of Contents | ||||
---|---|---|---|---|
|
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 |
...