The Ex Libris implementation & PM team all report to Melissa Hilbert. Marci shared slides showing team members and escalation paths.
Training has already started. It is happening throughout the project and after go-live.
Largest piece of project is from Alma delivery Feb 19 to cutover planning done by June 30.
Currently, we have standard sandboxes with generic data (2 IZs and 1 NZ) - primarily used for training and testing; Following go live, we’ll get premium sandboxes with UC data. You want your system stable and the data the way you want it before the copy of your data is made for the premium sandbox.
Alma/PrimoVE - production: Work during implementation is done on Production (for existing alma’s, it’s a copy of your production instance). Data is reloaded at cutover.
Alma Configurations: Access to some configurations will be provided to those campuses who have completed Alma Certification. Existing Alma campuses are excused from this requirement.
Marci discussed the certification requirements with ExL project team and Professional Services management - and revised the requirements a bit to make it easier:
Alma Certifications
Existing Alma campuses are excused from the Alma certification requirements.
For any new campus, they must have 1 person certified in Alma by Test Load completion for us to deliver the Alma environment with open configurations.
For any new campus, they must have 2 people certified in Alma by Go Live.
Follow-up question from yesterday: The NZ will have the same new campus requirements as above.
Primo VE Certifications
Existing Primo VE campuses are excused from the Primo VE certification requirements.
For any campus new to Primo VE, they will need to have 2 people certified in Primo VE by Go Live.
There are quite a few configurations that staff will still have access to - so it’s not completely restrictive.ExL team will be providing a list of what is configurable or not if/when configurations remain locked.
Integrations: review documentation and resources with your IT staff. Critical integrations are Authentication and Patron Loader/SIS. Prioritize other go live “must haves” Additional integration sessions will be scheduled as needed. Feb - May is integrations config and testing.
Migration cutover: See the Alma and Discovery Cutover Process documentation for detailed info.
Go Live: Start using the system and running jobs. Staff are now using Alma for day to day activities; patrons have access to Primo VE. You are using the system; your patrons are using the system.
Post Go-Live: Knowledge Acceleration Program - live webinar program for institutions up and running within the last 6 months; live sessions with Q&A focused on optimizing the system. Timing would be after switch to support. 1 hour/week. Possibly late fall or early spring.