The GIR is coming and IAM excited!
You might find this article helpful if you are an application owner and your application currently uses workforce data from the HR SAD.
How do things work today?
Currently if applications in Elanco need to consume workforce data, like employee names, roles or email addresses, they can get this information from Lilly’s ERP: SAP. By requesting a subscription to the HR SAD, application owners get provisioned a database of their requested workforce data which they can connect to their application. This database then gets updated from SAP on a regular cadence.
How will things work in the future?
Looking forwards, we will be looking to have a like-capability to the HRSAD called the Global Identity Repository, or GIR for short. This will pull a similar set of attributes from Elanco’s Workday system. The GIR is due to go live in Q3 2020.
Perfect, so everything is absolutely straightforward?
Unfortunately, time does not stand still on the Lilly side of the world either. Lilly are currently in the process of moving to Workday to manage their employee data too. This means the HRSAD is being retired and the cSAD from Workday is being introduced. This is scheduled to happen around April 2020.
Uh Oh, my application uses the HRSAD!
The cSAD will still have Elanco workforce data. This means Elanco applications can consume the cSAD like the HR SAD. TCS is working with all application owners to remediate any HRSAD subscriptions and get them changed over to the cSAD. They should reach out to you to help. If you want more information we’ve uploaded some resources in this folder.
It’s worth noting that not all fields in the HRSAD will match those in the new cSAD so there will be some testing and potential remediation to do.
Given the migration, how will that affect my application?
In most cases the transition will be HRSAD > cSAD > GIR. See the following scenarios for guidance:
- Your application is being retired before April 2020: No problem, you won’t need to worry! You can stop reading here and go grab a coffee.
- Your application is migrating before Q3 2020 but there will be no changes to attributes needed: Both the HRSAD and the cSAD were designed to be consumed by partners as well as internally. This means they can still be consumed by applications which have been migrated to Elanco’s new environment, by sending data files generated by CSAD to external SFTP sites. This will work as an interim solution until Q3 2020 when you can swap over to the GIR for a subscription to our Elanco Workday. Note: This point is not true for API calls. The API calls would need additional gateway configuration and setup.
- Your application is migrating before Q3 2020 and there will be changes to the attributes it uses: There may be occasions where applications need to consume an attribute which is different in the New Elanco to how it was in Lilly. For example, if the method of authentication that the application uses needs to change. The login becomes jo.joss instead of C123456. jo.joss doesn’t exist in as an attribute in the cSAD so the new data format will need to be consumed. There are options to get around this.
- If your application is business critical, we may be able to allow applications to consume Elanco Workforce data from Elanco Workday using Boomi. Workday have completed a proof of concept to show that this is possible, but this should not be a common practice.
- If your application is not business critical, you may need to put some local identity management processes in place as a workaround until the GIR is ready for consumption. We’re working on what this might look like.
- Your application is migrating after Q3 2020: You swap over to consuming the cSAD and when the GIR is ready, you can simply update your connection to point to this as a data source instead of the cSAD.
Has this article raised questions for you? Is there a topic you’d like more information on? Give us a shout on the ETS – Ask Us Anything Teams channel. We want to hear from you!