ETS Transition Update

It’s been the best of times.  It’s been the worst of times.  I’m sure Charles Dickens wasn’t in the middle of standing up Infrastructure services when he wrote these words, but they best describe the ups and downs over the last two weeks! 

There has been focus on final design reviews ready for decision making as we move into our implementation phase.  There has also been focus on procurement of key services, which I will share in more detail in future updates once RFPs and Negotiations are completed. 

One final thing from me before I let you enjoy the updates from the team.  We have worked this week to create MVP (Minimum Viable Product) statements for each of our workstream go-lives.  The intention is that we can describe, in words not jargon, what you can expect from each service when it goes live.  It’s important to note that not every service will be full feature and full functionality from day one and our hope is these MVPs help you with your planning and expectation setting with your business partners. 

Enjoy the updates! 

Your ETS Friends.  
ETS – Ask Us Anything 

Network - Paul Graham

The team has been busy working on the new sites that will be established in Bangalore and Warsaw, which will be key locations for R&D and GBS respectively.  We must ensure that the sites can be setup initially as part of the Lilly network and move seamlessly to the Elanco environment as soon as it is ready.  Significant thought is going into how to make these locations fit for future modes of operation, which will likely rely more heavily on WiFi, striking a balance between absorbing cost now, with greater overall efficiency, or later. 

Preparations are being made for two days of “Segmentation” workshops, which will be taking place next week with our delivery partners, WWT.  Segmentation is the ability to deliver secure and separated IT environments on converged infrastructure, allowing only the traffic that we want to pass between; this is of importance at our manufacturing sites.  The Elanco approach to this essential piece of the architecture intends to allow all the security of the current S95 model, with additional flexibility and reduced cost; the result will be a manufacturing network environment which is more agile and supportable. 

Identity – Calum Bell

The IAM team is currently working on onboarding each of our new engineers and working with the Commercial team to identify key principles and decisions around how we manage our customers external identity and what that means in terms of implementation. Additionally, we are continuing to evaluate all of our IAM options as it pertains with staying synchronised with Lilly so we can ensure that we choose a solution that is both the best fit as well as the best end user experience, to prepare for this we have delivered:  

• Transition Plan - How will GS, InfoSec and ETS still synchronised as we move forwards?  
• Master Identity Management - What does this mean and how should we view it in Elanco’s future?  
• External Identity Guidelines - How do we recommend that external identity is used and collected?  

As always, if you would like access to any of these documents or just more information, please reach out to me and I’d be happy to share.  

Cloud – Calum Bell

In Cloud we have now started designing the full workflows of a developer or app owner requesting a resource (A VM for example) and identifying how will we get that app through the pipeline into production. Within ServiceNow we will be able to provision individual resources and technologies to Azure, however one of the exciting things we are working on is grouping resources, what this means is, we can deliver a website with SSL, a domain and a Contentful back-end using just one service request.  

To help facilitate some of the upcoming application decisions that must be made, we are just finishing off some documentation which should help application owners decide where their applications belong, these documents are:  

1. Decision Matrix - A simple flowchart which asks questions around your application and points you to a hosting pattern.  
2. Hosting Patterns - These talk about the technology patterns we will be using in the future and helps the application owner understand the level of effort and what that means for the application.  

We will be looking to share some short demos in the coming weeks to show some of the new developer experience and help people understand more about the Azure environment. We expect to have Elanco’s own Azure portal up very soon, once we do, we are ready with a series of Infrastructure-as-code scripts to generate a large portion of the environment for different groups to get up and running as soon as possible!  

If you would like to hear more about our progress or discuss getting access to our Lab environment for your own testing, please reach out to me to find out more. 

Collab & Workplace - Jo Joss

A much shorter update from my side this week as we’re waiting for the delivery today of a few items from our partners at WWT. They’re preparing to deliver: 

1. A revised version of the collaboration high-level designs, including telephony, which will set us up for moving into the next phase of design, focusing on call centre and fax/print. 
2. A first draft of the workplace high-level designs for Microsoft O365 and End User Compute. 
3. A more granular project plan, which will help us give more details on what is coming next in this workstream, and what the August Minimum Viable Build will look like in the workplace and collaboration space. 
4. A detailed list of data we need to receive from Lilly to plan our low-level designs and implementation. 

Don’t forget to check out the Decisions tab of the ETS – Ask Us Anything channel on Teams, for more information on technologies under consideration. 

Service Management – Ben Nuthak

Please note, the following is subject to change, but is anticipated to remain largely static. 

This will also come soon in a formal communication from the PMO: 

• Until Elanco launches an independent ServiceNow instance for IT Service Management processes (Change, Incident, etc), these processes will be executed in the Lilly ServiceNow instance, even for independent Elanco assets.  During the Validation Risk Assessment for any new asset, a Configuration Item will be created and specially designated in Lilly’s SNow instance to track the Elanco asset, and allow Elanco IT to conduct Change or Incident Management against that CI.  The CI will be assigned to a special assignment group to prevent the Lilly helpdesk from assigning incidents to it by mistake.  The Lilly helpdesk will not be expected to support independent Elanco assets now or in the future. 
• Current projections show August 1 as the Elanco ServiceNow soft launch.  On this date, Elanco IT will be granted access to begin tracking changes and incidents against Elanco CIs.  During this time, Elanco CIs will largely continue to be manually maintained during the Validation Risk Assessment, as we will not yet have a system in place to automatically feed Software as a Service into the CMDB.  
• Beginning at this time, the Elanco Helpdesk will be completing its service mapping, reconciling Elanco versus Lilly services, in order to receive incidents and properly solve or swivel-chair them as necessary. 
• Between August 1, 2019 and January 1, 2020, all sites cutting over to independence will go live in ServiceNow, non-IT headcount included. 
• On January 1, 2020, the enterprise will formally begin usage of the independent ServiceNow instance.  It is our intention that the non-IT workforce receive a redirect notice from the Lilly SNow instance at this time. 
• Since Elanco IT will have had access to the Elanco SNow to execute processes since Aug 1, we anticipate that all tickets tied to Elanco-owned assets will be closed or completed by Q2 2020.  During Q2 2020 we will work with Lilly to archive all Elanco data as required by legal and regulatory stipulations.