- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-16-2022 06:46 AM
Is there an OOB method to populate the Business Unit field on configurations items?
Can discovery do this? It seems like this might be impractical unless the IP ranges were different, which might not be the case.
Can Technical Service Offerings or Business Service Offerings do this, just like they populate other fields? It seems like this would be the way to go, but I haven't found any official documentation or post that describes this.
Or maybe populate it via Service Mapping?
If there is no OOB method, does anyone have a tried and true approach?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-16-2022 10:28 AM
Thank you Scott, this is helpful. I believe TSOs can automatically populate attributes like Managed by group and Support group. Do BSOs offer similar auto-population methods? Can other fields (like Business Unit) be added to the TSOs or BSOs to auto-populate the contained CIs, or would this need to be done with a BR? Not sure yet that this would be the best method, because identifying the criteria to associate the TSO/BSO to a BU still needs thought. Also thinking it might be done as you suggest with BAs or even App Services.
You might include some of the history and recommendations in the next CSDM white paper.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-16-2022 06:54 AM
Question what is the relevance to have a Business Unit value on CI level?
I am familiar that BU is owning/funding Business Applications. And probably that way they 'own' everything below with the exception of shared components maybe. But I don't know other use cases that requires a Business Unit reference on CI level.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-16-2022 07:40 AM
Well, Business Unit is an OOB field on CIs, and I imagine it is there for purposes like: reporting the inventory of CIs that are owned by or operated by a business unit; and from an SPM/APM perspective the associated costs and resources and lifecycles associated with those CIs.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-16-2022 07:54 AM
For cost/resource purpose I would maintain the Business Unit on the Business Application and you can lookup up the relations from any CI which Business Application is supported by that asset/ci. The invoice can be done total cost of the service.
I doubt if there is a need to sync the Business Application BU value to each and every CI record.
If it comes to operations the idea is to grouped the assets/CIs by (a) Dynamic CI Group(s) and related to a Technical Service Offerings. The TSO Groups are responsible for the operational part of the asset/CI
BR,
Barry
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-27-2022 12:30 AM
Just remember that a Business Service (or just service) and business Applications are also a CI.
A lot seems to think that only infrastructure components are CIs that is far from the truth.
A CI is a record in the CMDB classes (which services belong to) so a Business Unit can easily have direct relations to a CI
