Navigate portfolio types in Digital Portfolio Management

  • Release version: Washingtondc
  • Updated March 2, 2024
  • 6 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Navigate Portfolio Types in Digital Portfolio Management

    In the Digital Portfolio Management (DPM) application, you can navigate three types of enterprise portfolios: service, business applications, and application service. Each portfolio type is structured in a nested content tree format for easy navigation. Access these portfolios through the Enterprise portfolio icon.

    Show full answer Show less

    Key Features

    • Service Portfolios: Created from Service Portfolio Management tables, featuring a taxonomy node that displays performance metrics, needs attention alerts, and a breakdown of services.
    • Business Application Portfolios: Built using enterprise portfolio tables, showing enterprise taxonomy nodes with key metrics, incidents, and a detailed view of business applications.
    • Application Service Portfolios: Similar to business application portfolios but tailored for application services, providing insights on success metrics, incidents, and operational status.

    Key Outcomes

    By navigating these portfolio types, ServiceNow customers can effectively manage and monitor their services and applications, ensuring improved performance and proactive incident management. The structured view allows for quick access to critical information, enhancing decision-making processes and overall portfolio management efficiency.

    Navigate three types of enterprise portfolios in the Digital Portfolio Management (DPM) application — service, business applications, and application service. Even though you can view service enterprise portfolios in DPM, they're created using Service Portfolio Management tables. Enterprise portfolios for business applications and application service are created from enterprise portfolio tables.

    Enterprise portfolios are structured in a nesting content tree format so you can easily navigate each type of enterprise portfolio. Access Enterprise portfolios using the Enterprise portfolio icon (Enterprise portfolios icon.). For more information about accessing enterprise portfolios, see Navigate enterprise portfolios in Digital Portfolio Management.

    Each type of enterprise portfolio offers unique data pertinent to its type.

    Service portfolios

    Service enterprise portfolios are created from Service Portfolio Management tables. The DPM Workspace displays service portfolios in a nested content tree with the taxonomy node, and then the services that are in the service portfolio.
    Table 1. Portfolio structure for services
    Section Description
    Taxonomy node
    • The first level in the content tree under the service enterprise portfolio.
    • The following information is provided for the taxonomy node:
      • Header with a short description, owned by name, and total subscribers.
      • Performance snapshot metrics for availability, open incidents, incidents not updated for 5 days, and new requests.
      • Needs attention cards for critical incidents, outages, and changes.
    • The View details link provides the following information about the taxonomy node.
      • Header with the service portfolio name, manager name, and total subscribers.
      • Overview tab with performance snapshot metrics and the breakdown of services in the category.
        Note:
        DPM versions prior to 2.2.15 may have duplicate services showing in the Service breakdown section. For information, see KB1123710.
      • Taxonomy node tab with all the taxonomy nodes related to the portfolio.
      • Services tab that lists all services in the portfolio, with their parent, classification (business or technical), phase, status, criticality, and owned by name. You can also select Create business service or Create technical service to perform those tasks in Service Builder.
      • Info tab with a description and general information about the taxonomy node.
      • Needs attention panel that lists critical incidents, outages, and changes.
    Service and service offering

    Business application portfolios

    Business application enterprise portfolios are created using the enterprise portfolio tables. The DPM Workspace displays enterprise portfolios in a nested content tree starting with the enterprise taxonomy node at the top level (there could be more than one). After the top node, it lists the business applications that are in the enterprise portfolio. Here’s an example of a business application enterprise portfolio content tree.

    Figure 1. Business application enterprise portfolio content tree example
    Business application enterprise portfolio content tree example
    Important:
    The image shows the Portfolio field as Enterprise business applications. To select a different type of enterprise portfolio from the one you're in, delete the value in the Portfolio field, and then select the field (again) to see the other portfolio types (service, business, or application service).
    Table 2. Portfolio structure for business application
    Section Description
    Enterprise taxonomy node
    • The first level in the content tree under the business application enterprise portfolio. Could contain a second or third level if it has child enterprise taxonomy nodes.
    • The header:
      • Short description.
      • Owned by name.
      • Managed by name.
      • Total subscribers
    • The portfolio success metrics for availability, incidents with a breached service level agreement (SLA), incidents caused by changes, and successful changes.
    • Needs attention cards for critical incidents, outages, changes,alerts, risks, and audits.
    • The View details link provides the following information about the enterprise taxonomy node.
      • Header with the Owned by name and the Managed by name.
      • Overview tab with portfolio success metrics and the breakdown of business applications in the enterprise taxonomy node.
      • Taxonomy nodes tab that lists all the related taxonomy nodes.
      • Business applications tab with a list of the business applications that are in the enterprise taxonomy node.
      • Info tab with a description and general information about the enterprise taxonomy node.
      • Needs attention panel that lists critical incidents, outages, changes, alerts, risks, and audits, for the enterprise taxonomy node.
    Business application
    • The next level in the content tree under the enterprise taxonomy node.
    • The header:
      • Short description.
      • Application owner name.
      • Business owner name.
      • Total subscribers.
      • Status.

        The Overall risk is empty.

    • The portfolio success metrics for availability, incidents with a breached SLA, incidents caused by changes, and successful changes.
    • The Needs attention cards for critical incidents, changes, risks, and audits.
    • The More menu icon (More menu icon) enables you to add the business application to a personal portfolio. For more information, see Create a personal portfolio in Digital Portfolio Management.
    • The View details link launches the business application details. For more information, see the Business applications section in Digital Portfolio Management related applications and data sources.

    Application service portfolios

    Application service enterprise portfolios are created using the enterprise portfolio tables. The information in application service portfolios is similar to that of business application portfolios with some differences that pertain to application services.

    For information about KPI groups in application service portfolios, see View application service details.

    Table 3. Portfolio structure for application service
    Section Description
    Enterprise taxonomy node
    • The first level in the content tree under the application service enterprise portfolio. Could contain a second or third level if it has child enterprise taxonomy nodes.
    • The header:
      • Short description.
      • Owned by name.
      • Managed by name.
      • Total subscribers.
    • The portfolio success metrics for availability, mean days to resolve (MTTR), incidents caused by changes, and successful changes.
    • The Needs attention cards for critical incidents, outages, changes, alerts, risks, and audits.
    • The View details link provides the following information about the enterprise taxonomy node.
      • Header with the Owned by name and the Managed by name.
      • Overview tab with portfolio success metrics and the breakdown of application services in the enterprise taxonomy node.
      • Application services tab with a list of the application services that are in the enterprise taxonomy node.
      • Info tab with a description and general information about the enterprise taxonomy node.
      • Needs attention panel that lists critical incidents, outages, changes, alerts, risks, and audits for the enterprise taxonomy node.
    Application service
    • The next level in the content tree under the enterprise taxonomy node.
    • The header:
      • Short description.
      • Owned by name.
      • Managed by name.
      • Operational status.

        The Overall risk is empty.

    • The portfolio success metrics for availability, incidents with a breached SLA, incidents caused by changes, and successful changes.
    • The Needs attention cards for critical incidents, changes, outages, risks, and alerts.
    • The More menu icon (More menu icon) enables you to add the application service to a personal portfolio. For more information, see Create a personal portfolio in Digital Portfolio Management.
    • The View details link launches the application service details. For information on what this screen includes, see the Application services section in Digital Portfolio Management related applications and data sources.