The Provisioning web application supports provisioning services and features via order workflows. Benefits include:
Improved availability and scalability.
reducing calls into IDI support for assistance in setting up and managing provisioning.
reducing the need for Adaptive Requests to update provisioning scripts.
helping IDI platform user’s to be more self-sufficient in troubleshooting, and reducing the time to diagnose issues.
Click here for a quick overview.
here
Product Catalog SKUs – Any SKUs (services and features) that require provisioning must be configured in the CostGuard Product Catalog. The granularity to which you’ll need to create SKUs will depend upon your business requirements. For example, you may only require one SKU to cover all business service types, or several different SKUs if the same service type needs to be provisioned at different Providers.
Notes:
Any SKU being provisioned is associated to the Order by an Internal Object ID. In this release of the Provisioning web application an internal ID can be either be an account number or service number.
With the Provisioning web application you will no longer be required to maintain products in the Product Catalog set up specifically to support provisioning.
Provisionable Object Definitions - Provisionable Objects represent the items (SKUs) to be provisioned on a network. Provisionable Object Definitions (PODs) let you configure the properties sent with the provisioning request for a product. A POD can be mapped to one or more SKUs. Certain properties are established by the system such as account or service number, and you can create additional custom properties based on your unique business processes.
Profiles - Profiles map PODs to a Provider (network element or end-point where products are provisioned) and a provisioning action. An example provisioning action may be: add a business line or suspend a wireless line. You select the Provider and action you’d like to take, and the system will display the parameters the Provider needs to fulfill that request. From there you simply drag and drop the properties from the POD (and/or other data sources) to the respective parameters.
Workflow - Profiles are mapped to workflows through Provision From Order actions. One such action is required per provisioning request. The action identifies the Order (Cart ID) and the specific Profile to be applied to fulfill the request. The Workflow sends the data in the Profile parameters to the provisioning process.
Provisioning - sends information to network element.
Access is via the Web Apps tray.
Show Picture
Selecting Provisioning lands you on the Profiles page.
Show Picture
Using the Provisioning Web Application
See:
Running and Managing Provisioning Requests
What's New
To find out what's new since the last release, see What's New.