The order capture application is one of the core components of SimpleOrder. OCS provides the ability to reflect the order negotiating processes, which are required to capture the various aspects of the order. These aspects include customer name, address, order details, and so on.
This application runs a complete validation on a customer order before storing the customer order in the order master database. It is also responsible for submitting the order to downstream order manager applications, and providing interfaces for fulfillment status capture.
SimpleOrder performs the Authorize Credit check during the order capture process. The essential details for this check include:
Currently, this application is implemented over a stub. In an engagement, SimpleOrder can be integrated to appropriate credit agencies for authorization on real-time basis.
Logical number inventories are allocated during order capture for a new or an existing customer. SimpleOrder supports inventories like telephone numbers (Wireline), MDN (wireless), and VOIP numbers. It also checks for available network resources for a particular service address.
Presently, the logical and network inventory allocations are implemented over stubs. In an engagement, inventories can be allocated and blocked on a real time basis during the order entry process.
Service address validation is part of the pre-order feasibility check. This check determines if the customer address is serviceable and valid products and service offerings are in place.
Product filtering based on service address is a key differentiator in winning over competitor offerings. Service address feasibility is currently implemented over a stub, and in an engagement, can be integrated to appropriate customer application.
To obtain the activation due date for Wireline products, SimpleOrder can integrate to the customer-specific work force management application on a real time basis. This due date forms the basis for the service level agreement.
The In-service profile consists of the active customer service profiles in the network elements. Customer service profiles are created after the services are provisioned. If subsequent orders are placed by an existing customer, then the active services information is retrieved along with any pending orders that are in the queue. This information helps in revalidating the eligible products and services.
The In-service profile is currently implemented using a stub.
Currently, SimpleOrder uses a stub implementation of the service. SimpleOrder can be integrated to any customer-specific application in an engagement.
This application performs a generic payment validation via its ordering channels. All payments are made using credit cards.
This application is currently implemented over a stub. It will be an assigned product in an engagement.
This application is currently implemented over a stub. Typically, LDAP could be used as persistence for maintaining user profiles for authorization, and a role-based access control can be implemented.
Click
