THE LIBRARY CORPORATION CORPORATION THE LIBRARY Solutions that Deliver Consequently, TLC•Cloud Services opened up Implementation Meanwhile, technical service specialists were Recommendation Additionally, the Library was aware of the underlying geographic access for TLC to oer hosting services in completing similar tasks from their own homes: making technical architecture. The Library had been using Linux Part of choosing the alternative option meant the all OCI data regions, globally. In the co-location model, sure the reports worked, the databases were connected, Two details were top of mind for WCL in their servers in their operations and continuing in a Linux Library would coordinate between all of the entities to TLC customers would have needed to connect to SIP connections were established, and so on. Similarly, decision-making process: the technical compatibility environment, which is what was oered with the safely move data from the previous vendor into the either the Denver, CO, or Ashburn, VA, hosting facilities the Smart Council team was conrming the network that a new hosting provider could oer within the TLC•Cloud Services option, would be advantageous for cloud. At this point in the spring and early summer, respective of their ILS product. connectivity and trac, plus checking the integrations existing library foundations, and how the solution the Library in terms of maintaining servers, diagnosing teams in Wellington were starting to return to their issues, and general application knowledge. between OCI into the City's AWS environment. TLC expanded into the international market, oering a would work in practice with a new data hosting libraries and oces while the TLC teams were still closer network endpoint and decreased global network partner. Because the CARL product suite integrates working virtually. This necessitated regular calls After a year-long process with an intense lead-up to one In practice, the Library needed to determine how a new latency to customers, including a fault-tolerant data with so many other services and vendors, the hosting between TLC, WCL, and Smart Council, plus teams from Go-Live weekend, a new cloud hosting environment hosted solution would work from a support partnership center in Sydney, Australia. Wellington City Libraries solution would need to accommodate and maintain the network provider and occasional AWS consultants. separate from the City, and minimal service disruption, perspective, while also maintaining excellent library were made aware of this as an extremely viable and this integration. Wellington City Libraries completed the switchover to WELLINGTON CITY LIBRARIES service. By receiving hosting services from the vendor As the Library coordinated between the technical sta • natural solution to their hosting quandary. TLC Cloud Services. By the end of that workday, the For technical compatibility, there was a sense of that already provided their integrated library software, and strategic sta at TLC with their counterparts within Library felt condent moving forward, and they WCL would benet from that existing partnership. Smart Council, Wellington City Council remained aware Evaluation expediency rst and foremost, since the Library needed conrmed that everything was set up properly as CASE STUDY of the benet of having a partnership agreement with required and working smoothly as expected. Problem to have all of their servers out of the previous Solution TLC would be able to actively maintain, monitor, and TLC. This demonstrable spirit of collaboration and open When Wellington, New Zealand, Working virtually from their environment by late 2020. update remotely within the cloud. Additionally, the two communication further validated the vendor decision Since WCL’s migration, City Council made the choice to In the last months of 2019, Wellington City Council, in kitchen tables at the start of the The solution needed to be After an extensive evaluation, working with Smart organizations could take advantage of the diering and would ultimately be required throughout the TLC•Cloud Services has been switch hosting providers for a conjunction with the Shared Services organizations, COVID-19 pandemic, sta from implemented quickly, and Council and TLC, WCL submitted their recommendation international time zones to coordinate work between elaborate project undertaking. named the Service of the Year for group of organizations using agreed to move away from their current third party Wellington City Libraries worked preferably in an to City Council; they suggested pursuing TLC's OCI library open hours and regular support hours. TLC could the 2021 Modern Library Awards. Shared Services, Wellington City infrastructure provider. The City decided to move to with a team from Smart Council, environment with a cloud hosting option over the AWS option used for all complete work that required downtime while New The project was facilitated and completed on time, with Libraries (WCL) opted to migrate an AWS server facility located in Sydney, Australia, their IT liaison to the City Council, disaster recovery response other Council services, including other Library servers. Zealand slept and test any changes collaboratively TLC collaborating actively with Smart Council as technical their library data to TLC•Cloud Services, managed by where the bulk of the Council services and many to initiate an evaluation process in the highly seismic during the overlap. experts and the Library acting as content experts. The Library Corporation (TLC) and powered by Oracle other New Zealand institutional servers are hosted. and consider TLC•Cloud South Pacic. TLC could TLC•Cloud Services checked all the boxes on WCL's Cloud Infrastructure (OCI), after completing an Services alongside the City's meet this need with an technical considerations checklist, and the existing With their sights on the future, TLC would also be Results extensive comparison to the City Council's new For WCL, a coordinated plan was needed to handle AWS option. implementation in the partnership with TLC allowed WCL to feel more Amazon Web Services (AWS) hosting option. 13 servers, including servers for the library website, Sydney data center. developing CARL with TLC•Cloud Services in mind. condent coordinating the server migration, as it WCL saw the benets of hosting within an environment On a Sunday morning in September, the day of Go-Live, third party vendors, public internet computers, Smart Council was responsible aected other services integrated with TLC. WCL also a few key WCL sta members were awake by 6:00 AM, Background Secondly, the Library had optimized for cloud hosting. Its scalability and its online payment processing, and more. The City IT for the change process, including anticipated the positive eect on sta and customers, ready for the switchover. Others made themselves a strong responsibility to combination of architecture, technology, and applied sta working on the larger migration project had extraction from the third party and the future implications of using a single vendor for available on-site by 8:00 AM at one of the sites that Wellington City Libraries consist of 14 locations along protect and uphold the process, would provide WCL with a more secure and migrated hundreds of servers throughout the year, contract and setting up the City's both their integrated library system and hosted data would be opening to the public that day. By 11:00 AM at the waterfront of Wellington Harbour in the densely integrity of its customers' high-performing environment than most on-premise and the WCL migration would be one of the more AWS environment for all other services. The only item left was to meet the deadline for the latest, they had checked that the CARL Sta client populated hills of New Zealand's capital city. This nook data. The solution would facilities or other public clouds. complex moves. Council services. Smart Council implementing this new service. application was working for all circulation tasks, the of the world sits along the Pacic Ocean's Ring of Fire, need to comply with New Zealand laws and also respect worked closely and pragmatically with the Library to catalog data was appearing, all the transactions were an area named for its high rate of earthquakes, The Library had to make a choice: a) relocate their the privacy and security of their customer data. WCL understand the technical and user implications of showing in the patron database, and all the third party volcanoes, and other seismic activity — a natural threat library data along with the City to the AWS server; or, would benet from the data-at-rest encryption selecting TLC•Cloud Services. integrated products were connected properly and to servers and their data. b) nd another hosting option, separate from the capability, as well as integrated security services authenticating accurately with patron information. Since 2013, the majority of the Library’s services were City's technical support services, and coordinate This information was then worked into a formal provided by TLC•Cloud Services, to protect data and hosted at a local o-site server facility provided by the moving a complicated amount of servers between recommendation for City Council management, control access using security-rst design principles. City Council, with neighboring city entities under the entities — all before a late 2020 deadline. showing the advantages, disadvantages, considerations, Hosting the servers in Australia gave compatibility with Shared Services program. Each organization operated and opportunities involved in the process and beyond. New Zealand legal requirements. independently, but shared various infrastructure and Meanwhile support needs under one supplier. While these events were unfolding in New Zealand, For their library services, WCL has been using the CARL TLC had happenstantially also announced an integrated library management software product suite initiative in the Fall of 2019 to migrate away from from TLC since 2001. Following the initial on-site their second generation co-location hosting model hardware installation, the CARL team has provided to a fully cloud third generation hosting model assistance during previous server relocations.