Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.

Create business capability and relate the capability with an application

Log in to subscribe to topics and get notified when content changes.

Create business capability and relate the capability with an application

Business capabilities are the abilities of an organization to do an activity to fulfill its business goals. Align your organization goals with business capabilities by creating capabilities.

Before you begin

Role required: sn_apm.apm_admin

About this task

Use the Business Capability form to create and update a business capability. If you add a new capability, update an existing capability, delete a capability at a leaf node level, then the levels of all the capabilities and the leaf node in that hierarchy must be updated accordingly. Click the Update Capability Level and HierarchyID related link to update the levels in the hierarchy so that the capability map reflects the updates. The Leaf Node and the Level fields are rendered uneditable to you, yet you can view the level of the capability if it is at leaf node and its position in the hierarchy.

Following are the conditions to update or delete a capability:

  • When you add a capability, the level of the new capability in the hierarchy is automatically assigned based on the level of the parent capability that is attached.
  • If a parent capability is updated in the hierarchy, then the levels of all its child capabilities are recalculated. Otherwise, a capability can only be updated of its name, description, or parent.
  • While adding or updating a capability the total number of levels cannot exceed more than six in the hierarchy. For example, the levels can be from 0 to 5, where 0 is the root level.
  • You can delete capabilities that are at the leaf node level only. Or, a capability that does not have a child capability of its own.
  • Do not create circular relationships. In creating a parent capability, a child capability cannot be its parent.

Procedure

  1. Navigate to Application Portfolio Management > Administration > Business Capabilities.

    You can also navigate to Organization > Business Capabilities.

  2. Fill in the form fields.
    Table 1. Business Capability form
    Field Description
    Name Name of the business capability.
    Parent Select the parent capability for the capability that you are creating.

    Assigning a parent capability renders the business capability as a child capability. If no parent is assigned or if the parent is null, then the level of the capability is at 0 level or root, which means it is a root node capability. If the parent field is made null, then a message prompts you to run a scheduled job to update the business capability levels.

    Level View the level at which the capability is in the hierarchy. If there is no parent capability then the level is 0, which indicates that the capability is at the root level.

    Level at which the capability is in the hierarchy. Up to six levels are supported.

    If you add a capability or update it by changing its parent, then run the Update Business Capability Levels job, on demand. The job determines the capability level and updates all the capabilities with the level information.

    Note: The system updates the field and the user cannot.
    Business Unit Attach a business capability to the business unit organizational structure.
    Order Assign any integer value. Applicable only for level-0 capability.

    The number you assign determines the position of the capability in the sequential order of all other business capabilities in that capability hierarchy.

    The Order field is available only for root node or level-0 capabilities. The scheduled job checks for conditions such as order values entered for non-root capabilities, duplicate order values, and null value and eliminates such values. It calculates and sets the level and hierarchy ID for each capability.

    Department Attach a business capability to the departmental organizational structure.
    Leaf Node If the check box is enabled, then it means that it does not have child capability.

    Capability follows a parent-child hierarchy. Leaf node attribute in the capability denotes that it is not a parent of any other capability.

    Note: The system updates the field and the user cannot.
    Hierarchy ID For level 0 capability hierarchy ID is generated based on the order. For all non-root capabilities the hierarchy ID is generated based on the hierarchy ID of its parent. The number is prefixed to the business capability and you can view it in the capability hierarchy map.

    The capabilities are structured vertically according to their hierarchy IDs. Whenever a capability is updated such as if a parent is added or deleted then the hierarchy ID is automatically updated.

    Note: By default, the system updates the field. Hence you cannot edit the field.

    However, if you prefer a different number or value for the hierarchy ID from what the system generates, you can reset the system property flag to True. Setting the property to true makes the Hierarchy ID field editable in the Business Capability form and you can enter the value. By this action, the system default logic of generating the hierarchy ID is overridden by your custom hierarchy ID.

    Asset tag Tag assigned to track the asset. It is an attribute of the parent capability that is inherited by the child.
    Description A short description of the business capability.
  3. Click Submit.

    If a root or a level-0 capability is created or if the parent field of a capability is rendered null, then a message prompts you to run the business capability update levels job to recalculate the hierarchy IDs.

  4. To make the Hierarchy ID field editable, navigate to System Properties > All Properties.
    1. Click the use_business_capability_custom_hierarchy_id system property in the sys_properties.list.
    2. Enter true in the Value field.
    3. Click Update.
      Note: Since the hierarchy ID is customized, the system does not check for any conflicts in the number or value that you set.
  5. To create child capabilities for the capability that you created, open the record and click New button in the Capabilities related list of the Business Capability form.
  6. In the related links, click Update Capability Level and HierarchyID to update the levels in the hierarchy. Clicking the Update Capability Level and HierarchyID link executes the Update Capability Level and HierarchyID scheduled script. You can view the updated hierarchy in the capability map.

    If you had navigated to the Capability Hierarchy Map after updating the parent, order, or hierarchy ID but without running the update capability levels job, then a message prompts you to run the Update Capability Levels job and relaunch the page to render the capability hierarchy map with the latest change.

  7. To relate the capability with an application, click open the business capability.
  8. Click the Add CI relationship (CI relationship editor icon) icon in the Related Items section of the business capability form to launch the relationship editor and create the CI relationship.

    The relation between a business capability and business application must always be of type provided by::provides.

What to do next

View capability based planning to understand the hierarchy of capabilities mapped with its related applications and plan investments in applications if the technology of the applications is at a risk.
Feedback