(Test Load + Go Live & 3 months) Network Zone configuration changes by Ex Libris

Legend: not started IN PROGRESS STALLED decided

Recommendation

Prior to EOD (5pm PT) June 25*

• EXL will notify the NZ Admins when advising that a resolution to a problem involves an NZ config change before EXL actually makes any change

• EXL will agree to not do any NZ change unless an NZ Admin (Gem Stone-Logan or Alison Ray) approves it

  • Note that this workflow may understandably cause some delays

• For communication with the NZ Admins:

  • EXL will tag the NZ Admins in the related Basecamp post

  • Should the request for a change come from a SalesForce case, EXL will copy the UCS Systems Office List via the additional email field in the case: sils-sysops-l@ucop.edu

    • Please note that due to recent extensive testing by Fulfillment Group and others, there may be NZ-related reports or questions this week that will need immediate attention and may include possible requests for or changes to the NZ.

  • Consideration: It may be better to wait until after Go Live for any additional NZ configuration changes to ensure proper testing in advance of changes. See the Post Go Live section below for more details.

Upcoming NZ Work by EXL: During Cutover and Prior to Go Live

• EXL previously communicated with the UCS Fulfillment Group about necessary NZ work that will need to be done [by EXL] prior to Go Live.

  • This mostly entails distributing AFN configurations from the NZ to the current live Almas via some manual updates and some updates via a job in the NZ.

• EXL is currently working on documenting what this work entails and will post it when readied on Basecamp, tagging the UCS NZ administrators for their review and approval prior to EXL’s necessary work.

Post Go Live

• Following acceptance and Go Live of the NZ on NA07, EXL is expecting that changes to the NZ will be owned by and predominantly made by the UCS NZ Admins.

  • Should EXL be requested to make NZ changes for the UCS, EXL will continue to use the Basecamp and SalesForce permission and communication methods outlined above.

• Due to concerns about configuration changes to the NZ and unknown consequences they might produce, EXL strongly suggests the use of the premium sandboxes (once created/delivered).

  • This will enable the NZ admins to test any/all possible NZ changes and their effects before putting such changes into production.

Documenting NZ Configuration Changes

• EXL will document the (NZ admin pre-approved) changes they make via the Basecamp posts and/or SalesForce cases where the specific request was made.

• For overall tracking, EXL strongly encourages the UCS (Systems Office, NZ Admins, etc.) to devise an internal plan to formally log and track all changes to the NZ (and to ensure cross-referencing of details from EXL staff that were included in Basecamp posts and SalesForce cases).

Background

ExL staff sometimes make changes to the NZ config (example: https://3.Basecamp.com/3765443/buckets/15553579/messages/3850460811 ) based on UC campus staff issues. Our NZ Admins / PPC are concerned about undocumented changes, and would “like to avoid last minute modifications that change expected, and already tested, behavior for all campuses.”

Dependencies

• This decision page will be revised after 6/25 and again after Go-Live to ensure that all processes with ExL and UC Libraries staff are appropriate to the work at hand.

Questions to consider

Action Log