Abstract: A system that provides a fulfillment action (or “action”) is provided. The system defines an action specification including a pattern of a structured request to perform work on a subject. The system further defines data for the action specification, where the data includes an action code template that references action codes, and a parameter list template that references parameters. The system further defines the subject for the action specification, where the subject includes a subject template that references entity specifications. The system further defines a target for the action specification, where the target includes a target template that references resource specifications. The system further generates an instance of the action based on the action specification, where the pattern of the structured request to perform work is transformed into process logic configured to perform the work on the subject.

Abstract: A system that provides a service order is provided. The system defines a service action including metadata that defines a pattern of a structured request to perform work on a customer-facing service that is based on a customer-facing service specification. The system further defines a customer-facing service specification including metadata that defines a customer-facing service that is provided, where a customer-facing service includes a technology-agnostic abstraction of a holistic capability. The system further defines a service order, where the service order includes one or more service order lines, where each service order line includes a service action and a customer-facing service based on a customer-facing service specification.

Abstract: A system that provides a technical catalog is provided. The system defines items including metadata used by a fulfillment solution to drive service order fulfillment, where each item is used by the fulfillment solution to fulfill an order. The system further stores the items within the technical catalog, where the technical catalog includes a data store that stores metadata, and where the technical catalog defines a structure of the items. The metadata defines the key entities and behavioral elements used to specialize service order fulfillment capabilities such as service order orchestration, service order design and assign, etc. The system further designs the fulfillment solution to use an item to fulfill an order. The system further generates the fulfillment solution using the item.

Abstract: An order management system is provided. The order management system creates the fulfillment flow, where the fulfillment flow does not include any fulfillment topology information. The order management system partitions an order into one or more order components using a decomposition sequence, where the decomposition sequence include one or more routing rules, where each routing rule includes fulfillment topology information, and wherein each routing rule determines a target fulfillment provider. The order management system generates an orchestration plan for the order by applying one or more dependencies of the fulfillment flow and the one or more routing rules to the one or more order components, wherein the orchestration plan includes the fulfillment topology information.

Abstract: A system that generates a technical order is provided. The system receives a configuration delta including a change in a configuration of resource-facing services or resources. The system further generates technical actions that effectuate the configuration delta, where each technical action includes metadata that defines a pattern of a structured request to perform work on a resource-facing service that is based on a resource-facing service specification or a resource that is based on a resource specification. The system further generates technical order lines, where each technical order line includes a technical action and a resource-facing service that is based on a resource-facing service specification or a resource that is based on a resource specification.

Abstract: A system that provides a provider function is provided. The system defines a structured set of metadata for the provider function. The system further defines a transformation sequence including customizable process logic for the provider function, where the customizable process logic is structured within stages. The system further dynamically generates a runtime process flow for the provider function based on the metadata and the transformation sequence.

Abstract: A system that provides a fulfillment solution blueprint is provided. The system defines order layers for the fulfillment solution blueprint. The system further defines provider functions for the fulfillment solution blueprint. The system further assigns each provider function to an order layer. The system further defines interface contracts for the fulfillment solution blueprint. The system further assigns each interface contract to a provider function.

Abstract: A system that transforms a customer order into a service order is provided. The system receives a customer order including customer order lines, where each customer order line includes a product action and a product offering that is based on a product specification. The system further defines a structured set of metadata including product specifications, customer-facing service specifications, relationships, and mappings. The system further defines a transformation sequence including customizable process logic, where the customizable process logic is structured within stages. The system further transforms the customer order lines into service order lines based on the metadata and the transformation sequence, where each service order line includes a service action and a customer-facing service based on a customer-facing service specification. The system further generates a service order including the service order lines.

Abstract: An order management system is provided. The order management system receives an order that includes one or more order lines, fulfillment topology data, and fulfillment flow data. The order management system generates one or more first order components from the order, the fulfillment topology data, and the fulfillment flow data based on a first criteria, where the first criteria is based on a first stage of a decomposition sequence, where the decomposition sequence comprises one or more stages. The order management system determines which of the one or more first order components each order line of the order is to be applied to, based on the first criteria. The order management system stores each order line of the order at each of the determined one or more first order components.

Abstract: An order management system is provided. The order management system receives one or more order components. The order management system maps each order line of one or more order lines to a fulfillment pattern. The order management system creates a fulfillment flow by combining one or more fulfillment patterns. The order management system generates an orchestration plan by applying one or more dependencies of the fulfillment flow to the one or more order components. The one or more dependencies of the fulfillment flow are translated into one or more order line dependencies between the one or more order lines of the one or more order components. Each order line dependency is at a completion of a fulfillment function of the order line.

Abstract: An order management system is provided. The order management system receives a provisioning order, where the provisioning order includes at least one order line, and where the at least one order line of the provisioning order references a product specification. The order management system transforms the provisioning order into a service order, where the service order includes at least one order line, and where at least one order line of the service order references a customer-facing service specification. The order management system transforms the service order into a technical order, where the technical order includes at least one order line, and where at least one order line of the service order references one of: a resource-facing service specification; or a resource. Thus, the order management system can define a customer-facing service that is not coupled to a technical implementation, nor coupled to a product offering.

Abstract: A system that transforms a customer order into a service order is provided. The system receives a customer order including customer order lines, where each customer order line includes a product action and a product offering that is based on a product specification. The system further defines a structured set of metadata including product specifications, customer-facing service specifications, relationships, and mappings. The system further defines a transformation sequence including customizable process logic, where the customizable process logic is structured within stages. The system further transforms the customer order lines into service order lines based on the metadata and the transformation sequence, where each service order line includes a service action and a customer-facing service based on a customer-facing service specification. The system further generates a service order including the service order lines.

Abstract: A system that decouples a product offering from a fulfillment flow is provided. The system defines a product offering including product specifications. The system further maps the product specifications to fulfillment patterns, where each fulfillment pattern includes metadata that defines a set of fulfillment functions and dependencies. The system further generates a customer order including customer order lines, where each customer order line includes a product action and a product offering that is based on a product specification, and where each product action is a fulfillment action (or “action”) including metadata that defines a pattern of a structured request to perform work on the product offering that is based on the product specification. The system further fulfills the customer order using a fulfillment flow based on the fulfillment pattern mapped to the product specifications.

Abstract: A system that provides a technical catalog is provided. The system defines items including metadata used by a fulfillment solution to drive service order fulfillment, where each item is used by the fulfillment solution to fulfill an order. The system further stores the items within the technical catalog, where the technical catalog includes a data store that stores metadata, and where the technical catalog defines a structure of the items. The metadata defines the key entities and behavioral elements used to specialize service order fulfillment capabilities such as service order orchestration, service order design and assign, etc. The system further designs the fulfillment solution to use an item to fulfill an order. The system further generates the fulfillment solution using the item.

Abstract: A system that provides a service order is provided. The system defines a service action including metadata that defines a pattern of a structured request to perform work on a customer-facing service that is based on a customer-facing service specification. The system further defines a customer-facing service specification including metadata that defines a customer-facing service that is provided, where a customer-facing service includes a technology-agnostic abstraction of a holistic capability. The system further defines a service order, where the service order includes one or more service order lines, where each service order line includes a service action and a customer-facing service based on a customer-facing service specification.

Abstract: A system that provides a fulfillment solution blueprint is provided. The system defines order layers for the fulfillment solution blueprint. The system further defines provider functions for the fulfillment solution blueprint. The system further assigns each provider function to an order layer. The system further defines interface contracts for the fulfillment solution blueprint. The system further assigns each interface contract to a provider function.

Abstract: A system that designs a fulfillment solution and fulfills an order using the fulfillment solution is provided. The system defines a technical catalog that includes items including metadata used by a fulfillment solution. The system further defines a fulfillment solution blueprint that includes multiple order layers that define multiple layers of the fulfillment solution, multiple provider functions structured according to a dynamic pattern-driven model, and multiple interface contracts defining multiple interactions between multiple provider functions. The system further designs the fulfillment solution to use at least one item of the technical catalog to fulfill an order. The system further designs the fulfillment solution based on the fulfillment solution blueprint. The system further generates the fulfillment solution based on the fulfillment solution blueprint using at least one item of the technical catalog.

Abstract: A system that provides a fulfillment action (or “action”) is provided. The system defines an action specification including a pattern of a structured request to perform work on a subject. The system further defines data for the action specification, where the data includes an action code template that references action codes, and a parameter list template that references parameters. The system further defines the subject for the action specification, where the subject includes a subject template that references entity specifications. The system further defines a target for the action specification, where the target includes a target template that references resource specifications. The system further generates an instance of the action based on the action specification, where the pattern of the structured request to perform work is transformed into process logic configured to perform the work on the subject.

Abstract: A system that generates a technical order is provided. The system receives a configuration delta including a change in a configuration of resource-facing services or resources. The system further generates technical actions that effectuate the configuration delta, where each technical action includes metadata that defines a pattern of a structured request to perform work on a resource-facing service that is based on a resource-facing service specification or a resource that is based on a resource specification. The system further generates technical order lines, where each technical order line includes a technical action and a resource-facing service that is based on a resource-facing service specification or a resource that is based on a resource specification.

Abstract: A system that provides a provider function is provided. The system defines a structured set of metadata for the provider function. The system further defines a transformation sequence including customizable process logic for the provider function, where the customizable process logic is structured within stages. The system further dynamically generates a runtime process flow for the provider function based on the metadata and the transformation sequence.