- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-22-2019 07:35 AM
I understand that the Business Capabilities can have a hierarchy (1.0 - 6.0) and that there can only be a single layer of Service Offerings, but is there any restriction on the other classes?
For example, can I have a portfolio for Supply Chain (1.0) and then a 'sub-portfolio' underneath that as a 2.0 before I break into the Service layer?
The same question applies to the Business Applications, Services (Technical and Business) and Application Service.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-23-2019 07:37 PM
Hi Kelly,
Beginning with New York we will no longer recommend a hierarchy in Business Service. In the past we often built hierarchies with Business Services. Too often these hierarchies were more about Capabilities or an Org structure. And largely they were for reporting purposes rather than actual impacted Business Services. So we have eliminated those use cases by providing Business Capabilities as CI's (in Kingston) and Portfolio's as CI's (in New York).
Additionally, we will be introducing some fancy reporting on the Business Service inherited from their Service Offerings. This data roll-up has a technical limitation that Service Offering data can only roll up to a single Business Service. Thus no more hierarchies of Business Service.
Portfolio's may have hierarchies
Application Services may have hierarchies - we have a use case of a Platform Host and their various Platform Apps. In this use case the Platform Apps depend on the Platform Host. Thus a hierarchy.
Business Applications, based on the platform use case above, can also have a hierarchy. We also use ServiceNow as a use case where the different modules (HR, Discovery, SAM, APM, etc.) are Platform Apps dependent on the Platform host of ServiceNow.
At this time Technical Services are a single layer, no hierarchy, and I suspect will stay that way.
Hope this helped! If not, you know how to reach me 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-06-2020 08:16 AM
That diagram is starting to put this into perspective for me. Does anyone have a real-world diagram of this done right? I'm nervous to think there can be multiple ways to do this when I've seen the relationships explicitly defined in other platforms and architecture models.
