Abstract: According to one method, the method comprises: receiving, from a client via a REST API, input in a first format; converting, using predetermined metadata, the input in the first format into input in a second format; sending the input in the second format to a legacy system for performing an operation using the input in the second format; receiving, from the legacy system, output in the second format, wherein the output is based at least in part on the operation performed using the input in the second format; converting, using the predetermined metadata, the output in the second format into output in the first format; and sending, to the client via the REST API, the output in the first format.

Abstract: According to one method, the method comprises: receiving, from a client via a REST API, input in a first format; converting, using predetermined metadata, the input in the first format into input in a second format; sending the input in the second format to a legacy system for performing an operation using the input in the second format; receiving, from the legacy system, output in the second format, wherein the output is based at least in part on the operation performed using the input in the second format; converting, using the predetermined metadata, the output in the second format into output in the first format; and sending, to the client via the REST API, the output in the first format.

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: A system is provided that that recognizes an order item. The system defines an order item specification including a recognition property and a dynamic parameter property. The system further receives an order item of an order, the order item including a key that uniquely identifies a conceptual model entity and arbitrary parameters, each arbitrary parameter comprising a parameter name and a parameter value. The system further extracts the key from the order item. The system further stores the key within the recognition property. The system further identifies the conceptual model entity based on the recognition property. The system further dynamically binds parameter values from the arbitrary parameters to the dynamic parameter property based on the identified conceptual model entity.

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: A system is provided that that recognizes an order item. The system defines an order item specification including a recognition property and a dynamic parameter property. The system further receives an order item of an order, the order item including a key that uniquely identifies a conceptual model entity and arbitrary parameters, each arbitrary parameter comprising a parameter name and a parameter value. The system further extracts the key from the order item. The system further stores the key within the recognition property. The system further identifies the conceptual model entity based on the recognition property. The system further dynamically binds parameter values from the arbitrary parameters to the dynamic parameter property based on the identified conceptual model entity.

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