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 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 creates a service instance is provided. The system receives a service order including an entity, where the entity includes metadata that defines a capability that is provided, and where the entity includes child entities. The system further designs a configuration for the entity, where the configuration includes the entity, the child entities, and relationships between the entity and the child entities. The system further creates, for each child entity, a design context, where each child entity is a subject for the design context. The system further designs, for each child context, an instance of the child entity using the design context.

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: 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 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 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 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 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 creates a service instance is provided. The system receives a service order including an entity, where the entity includes metadata that defines a capability that is provided, and where the entity includes child entities. The system further designs a configuration for the entity, where the configuration includes the entity, the child entities, and relationships between the entity and the child entities. The system further creates, for each child entity, a design context, where each child entity is a subject for the design context. The system further designs, for each child context, an instance of the child entity using the design context.

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: 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.