SimpleOrder implements rule-based product configuration solutions. The rule is based on the design that SimpleOrder implements are essentially driven by business constraints. These business constraints correspond to product availability, customer eligibility of products and services, customer profiles, products offers and services that can be made available to specific ordering channel. There are other types of constraints that are decided dynamically as customer progresses with negotiations and selections. (For example: customer configuring a bundle must conform to the rule of selecting minimum number of products and services). Wireline Voice Service may be added when the customer selects DSL Internet service.
The diagram below depicts the SimpleOrder solution stack with ordering channel interfaces built on top of order handling. The order handling is built on top of product domain (Product Catalogue) on one side and customer domain on the other. The diagram depicts how SimpleOrder achieves convergence both at customer level and products/services level.
>> Click here
SimpleOrder validates the key components upfront during the order-handling process. By implementing pre-order validations, SimpleOrder helps prevent inaccurate customer orders and achieves large degree of flow-through. Currently, SimpleOrder validates the following business functions:
SimpleOrder, for its ordering channel interfaces, displays and captures products and their attributes by their generic enterprise definition i.e., customer language (product short names). SimpleOrder implements a solution that is used to translate generic product definition to that of downstream/legacy interpretation of product and services and vice versa (forward and backward translation). For each of the products and product attributes, product translation determines corresponding legacy product code types and values, if any (Example: product short names are translated to appropriate USOC codes).
SimpleOrder provides ordering channel interfaces to create and retrieve a customer order over different sales channels with a consistent view. Ordering channel interfaces are built on top of Order Capture Service. This service has the capabilities to capture a customer order initiated from one sales channel, and present it to another sales channel in a consistent and channel independent way for viewing and/or modifying. This feature provides a powerful cross-channel customer experience and support order entry across multiple channels.
SimpleOrder conforms to the SOA architecture principals. SimpleOrder implements business services that are based upon open standard WSDL definition and realized via Web services at transport level. SimpleOrder also implements business services that are built on top of a SOA framework (i.e. a common meta-model of SOA). This SOA framework integrates with actual providers (packaged applications, custom applications at the back end) via technology adapters (for example Web service adapters). This means, the service provider and service consumer contractual agreement remains unaffected with the replacement of back-end application components.
Example 1: SimpleOrder provides ‘product availability’ and ‘product configuration services’ that work in conjunction with WPC.
Example 2: SimpleOrder provides ‘product availability’ and ‘product configuration’ services that are consumed over multiple ordering channels (e.g. call center interfaces and blackberry interfaces uses the same business services. Similarly, customer orders captured via different ordering channels use the same ‘order submission’ service to submit a customer order).
In this release of SimpleOrder, interactions between the different components are based on SOA principles.
Click