...
Once this is done, there is a physical reality to the claim that there is a Shibboleth CI which is the service itself, and then there is a "Shibboleth login for Salesforce" CI that represents the specific files that the Shibboleth service uses to login to Salesforce. It is not clear whether we want to add all these separate CI's to ServiceNow, but it improves the process documentation if we are clear about exactly what a Change affects.
Currently there is some confusion about priorities and problem ownership. If users cannot login to example.com, then this is a big issue for the example.com service owner. However, the Shibboleth service continues to function and handles mission critical functions for the other 100 services it supports. It would be better if we can distinguish an Emergency Change for "login to example.com" which is actually a rather small and safe change from an Emergency Change to Shibboleth which makes the example.com problem sound like a bigger issue.