Problem
In most ServiceNow instances, Business Services accumulate without a portfolio frame: there is no consistent way to group them, no shared taxonomy across teams, and no reliable link from the strategic portfolio view down to the concrete service offerings used by the business. That makes it hard to report at portfolio level, to compare services across domains, and to assign accountability for them in a way that scales. This blueprint solves that by anchoring every Business Service to a portfolio and a taxonomy hierarchy, and by requiring ownership, approval, support, and offering relationships to be in place.
What the Blueprint Includes
The blueprint places Business Service at the center and surrounds it with the portfolio structure that organizes it (Service Portfolio, Taxonomy Node, Taxonomy Layer Definition), the offering it delivers (Business Service Offering), and the people and groups that own, approve, manage, and support it.
- Business Service – Root entity representing a strategic business-facing service in the portfolio.
- Service Portfolio – The portfolio the Business Service belongs to. Anchors the service to a portfolio-level view that can be reported on as a whole.
- Taxonomy Node – Categorises the Business Service inside the portfolio. Used at two levels in this blueprint: a parent node and a child node, so services can be grouped first by a high-level category and then refined.
- Taxonomy Layer Definition – Defines what a layer in the taxonomy means (for example, “Domain” vs “Sub-domain”). Every Taxonomy Node is bound to a layer so the hierarchy stays consistent.
- Business Service Offering – The concrete offering delivered under a Business Service. Scoped to records where the service classification is Business Service so general Service Offerings stay out of scope.
- User – Provides accountability: assigned as Business Service Owner and as the Manager of each Business Service Offering.
- Group – Provides operational responsibility: assigned as Approval Group and Managed By Group on the Business Service, and as Support Group on the Business Service Offering.
Considerations
This blueprint is most useful when an organisation is moving past basic CMDB hygiene and wants the Business Service catalog to behave as a managed portfolio. The taxonomy layer and portfolio links are what unlock that, but they only deliver value if maintained intentionally.
- Plugin dependency. The model relies on the Service Portfolio Management Foundation plugin (com.snc.service_portfolio). Confirm it is installed and the SPM tables (spm_service_portfolio, spm_taxonomy_node, spm_taxonomy_layer_definition) are populated before rolling this blueprint out.
- Taxonomy depth. The blueprint uses two levels of Taxonomy Nodes (a parent node and a child node). You can flatten to one level or extend to more by adjusting the mandatory vs. optional links between the classes and adding or removing Taxonomy Node tiers.
- Use the Alternative Link Group consciously. A Taxonomy Node must reach a Service Portfolio either directly (its own Service portfolio link) or indirectly through its Parent Taxonomy Node. Decide which pattern your data team will enforce and apply it consistently across the portfolio.
- Lock the service classification. Business Service Offerings are restricted to records where service_classification = Business Service. This keeps technical or application-level Service Offerings from leaking into the portfolio. Re-check that filter if you customise classifications.
- Populate ownership at both levels. Business Owner sits on the Business Service, while Manager sits on the Business Service Offering. Both should resolve to active Users — otherwise portfolio reviews and approval flows lose their accountable contact.
- Pick group roles deliberately. The same Group class fills three roles in this blueprint (Approval, Managed By, Support). Make sure the groups you select for each role reflect your operating model — using a single catch-all group across all three roles dilutes the meaning of the model.
Benefits
When the portfolio and taxonomy structure is maintained, the Business Service catalog stops being a flat list and starts behaving like a real portfolio. You can report at the portfolio level, drill down by taxonomy layer, and trust that every Business Service has accountable owners and a clear path to the offerings underneath it.
- Portfolio-level visibility. Every Business Service is anchored to a Service Portfolio, enabling executive and strategic views of the catalog without ad hoc grouping.
- Consistent classification. The Taxonomy Layer Definition + Taxonomy Node pattern enforces a shared vocabulary across teams, making comparisons of services across domains meaningful.
- End-to-end accountability. Business Owner, Approval Group, and Managed By Group sit on the service; Manager and Support Group sit on the offering. Approval and operational flows have an unambiguous target on either side.
- Offering-aware reporting. Business Service Offerings are linked back to their parent Business Service, so portfolio reports can roll up consumption, demand, or incident data from the offering up to the service.
- A foundation for SPM workflows. Once the portfolio, taxonomy, and offering relationships are clean, downstream SPM capabilities (planning, demand, financials) have the reliable data structure they need.
Related Information
Check other templates related to the Service Consumption.
How to Get This Blueprint?
If you’re already a Data Content Manager Customer, you can download the Blueprint from the Knowledge Base. You will need your login credentials to access the blueprint download page.
