Service order decomposition

  • Release version: Australia
  • Updated March 12, 2026
  • 2 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 Service order decomposition

    Service order decomposition in ServiceNow breaks down a captured service order into domain-specific orders for fulfillment. This process is driven by the relationships defined between product, service, and resource specifications, ensuring that orders are appropriately created and linked for delivery to customers.

    Show full answer Show less

    Decomposition Based on Specification Relationships

    Specification relationships establish how products, services, and resources relate and dictate the decomposition process. When a service order is decomposed, if the relationship between source and target specifications is of type Bundles, Realized as, or Requires, ServiceNow generates product, service, or resource orders for the target specifications. This creates a hierarchical structure linking the original order to its domain orders. Decomposition does not occur for relationships of the Composed of type.

    Decomposition Based on Defined Decomposition Rules

    In addition to specification relationships, decomposition rules can be defined to further control order breakdown. These rules act as exclusion criteria, preventing the creation of domain orders if specific characteristics or characteristic options are absent from the service order.

    For example, in the Managed Firewall service:

    • The customer-facing Managed Firewall service links to resource-facing service specifications like Firewall Administrator, Firewall and DMZ, and Threat and Intrusion Prevention services.
    • Each resource-facing service specification further relates to resource specifications needed to deliver the service.

    Decomposition based on these relationships generates three types of orders:

    • Customer-Facing Service Order (CFS): For services performed directly for the customer.
    • Resource-Facing Service Order (RFS): For internal resource activities supporting the service.
    • Resource Order: For the actual resources required to fulfill the service.

    The decomposition process establishes and maintains the hierarchical relationships among these orders to facilitate fulfillment.

    Specification Relationship and Decomposition Rule Components

    • Source Specification: The specification defining the relationship.
    • Target Specification: The specification related to the source.
    • Decomposition Rules: Optional rules tied to specification relationships that use characteristics and characteristic values of the source specification to selectively include or exclude target specifications during decomposition.

    These elements enable precise and flexible decomposition tailored to the characteristics of the service order.

    Practical Benefits for ServiceNow Customers

    Understanding and configuring specification relationships and decomposition rules allows customers to:

    • Ensure service orders are automatically and accurately broken down into the necessary domain and resource orders.
    • Control which domain orders are created based on specific service characteristics, improving fulfillment efficiency.
    • Maintain clear hierarchical relationships among orders to facilitate tracking and management throughout the service delivery process.

    Learn how a service order is decomposed into its domain orders for fulfillment.

    Decomposition that is based on specification relationships

    Specification relationships define the relationships between product, service, and resource specifications. Specification relationships and decomposition rules specify how a service order is decomposed, fulfilled, and delivered to your customer.

    Decomposition runs on the specification that is associated with the captured service order line item and its hierarchy of specifications. It works as follows:
    • If the relationships between the source and target specifications are Bundles, Realized as, or Requires types, the product, service, or resource orders are created for the target specification. This action takes place when the captured service order is decomposed.
    • Decomposition establishes the hierarchical relationship between the source and targets while generating the service and resource orders.
    • Decomposition doesn't happen if the specification relationship is of a Composed of type.
      Note:
      To learn more about specification relationship types, see Create specification relationships, quantity mapping, and decomposition rules for Order Management.

    Decomposition that is based on defined decomposition rules

    Specification relationships define the relationships between product, service, and resource specifications. When you define specification relationships, you can optionally create decomposition rules. Specification relationships and decomposition rules dictate how a service order is decomposed, fulfilled, and delivered to the customer.

    The best way to view a decomposition rule is as an exclusion rule. You use decomposition rules to exclude the creation of domain orders when you receive a service order that doesn’t contain a specific characteristic or characteristic option.

    For example, in the Managed firewall service demo data, the Managed Firewall service is defined as a customer-facing service specification. It has a relationship with the following three resource-facing service specifications:
    • Firewall administrator
    • Firewall and DMZ
    • Threat and Intrusion Prevention service
    Each of these resource-facing service specifications has relationships with the corresponding resource specifications that are required to deliver the Managed Firewall service.
    • If the relationships between the source and target specifications are Bundles, Realized as, or Requires types, decomposition creates the following types of orders for the target specification:
      • A corresponding customer-facing service order (CFS), which is a service order that is generated for performance of customer-faced services.
      • A resource-facing service order (RFS), which is a service order that is generated for internal use of resources required to perform the actual services for the customer.
      • Resource order.
    • Decomposition establishes the relationship between the source and targets while generating domain service orders and resource orders. The following elements comprise the specification relationship:
      • The source specification is the specification that is defining the specification relationship.
      • The target specification is the specification that the relationship is being defined to.
      • Both values are automatically defined when the decomposition rule was created for the specification relationship.
    Optional decomposition rules are defined for a specification relationship between a source specification and a target specification. The rules use the characteristic and characteristic value (optional) of a source specification, for mapping to a target specification. These rules enable targeted order decomposition of a source specification that is based on the characteristic and characteristic value available in the source specification.
    Note:
    To learn more about specification relationships and decomposition rules, see Create specification relationships, quantity mapping, and decomposition rules for Order Management.