Defining the 'Depends On::Used By' relationship between an Application Service and Infrastructure CI
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-14-2022 09:40 PM
I'm hoping someone in the community can add some thoughts on the Depends on::Used by relationship type when used to describe a dependency between an Application Service and an Infrastructure CI (such as a server).
I'm determining whether the relationship represents a current and active dependency between the CIs or if it intends to reflect any historical reliance.
How do others use this relationship type? And how do you maintain the relationship based on different scenarios? (such as the one I've attached as an example)

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-14-2022 10:39 PM
Good day PG2,
CI relations are intended to be current state values. To my knowledge there isn't something that reflects historical states. If so then I would expect that in audits or notes.
BR,
Barry
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-15-2022 05:30 PM
I agree and am attempting to formulate a definition that reflects the relationship types purpose. I have this so far, and I am sharing it in case it is helpful to others.
Depends On::Used By
Relationship type
Describes an operational dependency where a parent CI needs a child CI to function; (e.g. a change or incident on a child CI may impact the function of its parent).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2024 04:59 AM
Hey PG2
Did you ever finish such a list, which defines the relationship types purpose 😊

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-15-2022 08:59 AM
Hi PG2,
If you are licensed for ITOM Service Mapping, one of the population methods for your Application Service should be used to maintain the dependency(stored as Service Configuration Item Associations) between the Application Service and the infrastructure CIs.
If you used a pattern based population method (Mapped Application Service), when the original version of the Application Service is retired, the Load Balancer VIP used as your entry point for the Application Service should have been removed from the LB or the LB service should be modified to no longer reference the infrastructure CI. There is a daily scan of Load Balancer Services that will catch the update to the LB service.