You are on page 1of 9

Alliance Consulting

Dun and Bradstreet, Inc.

High Level Technical Design Specification


UC-SMBS-DNBi-SMO-ORDER-MANAGEMENT
Dun and Bradstreet, Inc. 28 October 2009
Confidential

Table of Contents
1. Introduction.................................................................................................................................................................3
2. Document Purpose and Scope.....................................................................................................................................3
2.1. In scope................................................................................................................................................................3
2.2. Out of scope.........................................................................................................................................................3
3. System Architecture....................................................................................................................................................3
3.1. Detail Design........................................................................................................................................................3
3.2. Adding the DNBi SelfMonitor product to the shopping Cart..............................................................................4
3.2.1. Actors............................................................................................................................................................4
3.2.2. Pre-conditions...............................................................................................................................................4
3.2.3. Main Flow of events.....................................................................................................................................4
3.2.3.1. Product Detail Page Search .......................................................................................................................4
3.2.4. Alternate Flows.............................................................................................................................................4
3.2.4.1. Home Page Search.....................................................................................................................................4
3.2.4.2. Up-sells or Down-sells from Order Management pages............................................................................5
3.2.4.3. Cross-sells from Product Detail Page........................................................................................................5
3.2.4.4. CSR making purchases on behalf of customers using “Login as Customer” option.................................5
3.2.5. Post-Conditions.............................................................................................................................................5
3.2.6. Service Level Requirements.........................................................................................................................5
.............................................................................................................................................................................5
3.3. Checking out from the Shopping Cart.................................................................................................................5
3.3.1. Actors............................................................................................................................................................5
3.3.2. Pre-conditions...............................................................................................................................................5
3.3.3. Main Flow of events.....................................................................................................................................5
3.3.3.1. Registered Customer Making Purchases in Un-Authenticated Mode .......................................................6
3.3.4. Alternate Flows.............................................................................................................................................6
3.3.4.1. Registered Customer Making Purchases in Authenticated Mode..............................................................6
3.3.4.2. Unregistered Customer Making Purchases................................................................................................6
3.3.4.3. CSR Making Purchases on Behalf of the Customer through “Login as Customer” Option......................6
3.3.5. Post-Conditions.............................................................................................................................................6
3.3.6. Service Level Requirements.........................................................................................................................7
.............................................................................................................................................................................7
3.4. Product Fulfilment and Order Finalization Process after Submitting the Order..................................................7
3.4.1. Actors............................................................................................................................................................7
3.4.2. Pre-conditions...............................................................................................................................................7
3.4.3. Main Flow of events.....................................................................................................................................7
3.4.3.1. Customers having Credit Card Details with e-Commerce.........................................................................7
3.4.4. Alternate Flows.............................................................................................................................................7
3.4.4.1. Customers not having Credit Card Details with e-Commerce...................................................................7
3.4.5. Post-Conditions.............................................................................................................................................7
3.4.6. Service Level Requirements.........................................................................................................................8
.............................................................................................................................................................................8
3.5. Auto Renewal Functionality of DNBi SelfMonitor Product...............................................................................8
3.5.1. Actors............................................................................................................................................................8
3.5.2. Pre-conditions...............................................................................................................................................8
3.5.3. Main Flow of events.....................................................................................................................................8
3.5.3.1. Enabling/Disabling of Auto-Renewal Feature on DNBi SelfMonitor for the Customers.........................8
3.5.4. Alternate Flows.............................................................................................................................................9
3.5.5. Post-Conditions.............................................................................................................................................9
3.5.6. Service Level Requirements.........................................................................................................................9
.............................................................................................................................................................................9
4. References:..................................................................................................................................................................9

2
Dun and Bradstreet, Inc. 28 October 2009
Confidential
4.1. Documents...........................................................................................................................................................9
4.2. Glossary...............................................................................................................................................................9

1. Introduction

The Web Sphere Commerce ePlatform (WCS) provides a mechanism for D&B to sell a number of products into
the small and medium business community. This site is primarily focusing on credit products; and the services
like marketing, monitoring and collections are also offered.

This implementation lets SMBS customers purchase the DNBi SelfMonitor products directly on the customer
facing website. These are Consumer Direct store.

2. Document Purpose and Scope

This document identifies and describes the analysis and design model for implementing the business
requirements BR 4.0, 7.0, 8.0, and 15.0. All these are treated as “Order Management” module for
implementation purpose. These are
• Search Process
• Product Rules
• Pricing
• DNBi SelfMonitor Auto-renewal

Of all the four DNBi SMO products available, DNBi SelfMonitor is sold from the customer facing site CD site.
The other products will have only the advertising information only. Hence, wherever the DNBi SMO is
mentioned in the rest of the document it refers to DNBi SelfMonitor (Basic) product only.

Note: Per BRD 8.0 - Pricing, no specific description is required in this document, as it just mentions the prices
of the products that are sold from the e-Commerce application. These prices should be taken into consideration
while developing mass load documents.

2.1. In scope
• Adding the DNBi SelfMonitor to the shopping cart and purchasing the same successfully
• Different purchase rules associated with this product
• Renewing the DNBi SelfMonitor product after the initial expiration of the product

2.2. Out of scope


• This document will not cover about the Order Management of the above products in Sales Direct and
Syndication Stores.
• This document also will not cover the DNBi SelfMonitor Plus – Bench Marking entitlement related
business processing for the subscriptions.

3. System Architecture

3.1. Detail Design


In this document, the details steps pertaining to the Order Management of the DNBi SMO related products
are described. It covers the process through witch the company search on which these products are added to

3
Dun and Bradstreet, Inc. 28 October 2009
Confidential
the shopping cart, its associated purchase rules, expiration process, renewal process etc at a high level. It
also covers the Order Management steps involved in purchasing these products through other areas like
home page promotional content spots, up-sells, down-sells and cross-sells.

3.2. Adding the DNBi SelfMonitor product to the shopping Cart

3.2.1. Actors

• Customer – The user who will purchase the products form e-Commerce customer facing web sites
• CSR – Agent, who will make purchases on behalf of the customer by using the option “Login as
Customer” from Sales Direct store of e-Commerce website

3.2.2. Pre-conditions

o If the actor is a CSR, then CSR should have been logged into the Sales Direct store and
reach the Account History page of the customer on whose behalf this purchase is being made.

3.2.3. Main Flow of events

3.2.3.1. Product Detail Page Search

o A search box option should be provided on the DNBi SMO Product Detail page, which
can take the search parameters Company Name, City, State and Country as search criteria. The
country drop down box should have only “US” as option.
o The search box should also have a link to Advanced Search page, clicking on this should
take the customer to the Advanced Search Page.
o Existing functionality of the two search pages should remain the same, except the top
image shown on the Advanced Search Page.
o Product High Light box should have the “Order Now” button, clicking upon this, should
take the customer to the Advanced Search Page.
o Upon the customer entering the search criteria, the existing functionality of the search
process should be utilized and the search results page should be displayed. The search results page
should display the DNBi SMO related images and text on the top of the page as given in section
4.2 of BRD.
o Upon clicking on the name of the company or “Order Now” button, the user should be
taken to the shopping cart page (“My Order”), before which all the existing Order Management
logic should be executed.

3.2.4. Alternate Flows

3.2.4.1. Home Page Search

o The existing home page search functionality should remain the same. Once the customer
enters the search criteria in this box, and clicks on search box, the customer is taken to the search
results page. After clicking on either the company name or the search button, the user is taken to
the “Product Selection Page” as mentioned in section 4.1 of BRD.
o If the search is made directly from the Advanced Search page, then also the same steps as
explained below should be executed.
o On this page, under “Is this your company? …” section, the SelfMonitor product will be
replaced with DNBi SMO product as per the content given in the above section of the BRD.
o It will have two links “Learn More”, “See Product Demo” and an “Order Now” button.

4
Dun and Bradstreet, Inc. 28 October 2009
Confidential
o Clicking on Learn More link should navigate the customer to the DNBi SMO product detail
page. Clicking on “See Product Demo” should open a new window pointing to the URL
http://mycredit.dnb.com/DNBi_SMO.aspx.
o Clicking on “Order Now” button should add this product to the shopping cart, before which
all the existing Order Management logic should be executed.
o The SelfMonitor (traditional), BusinesScope, and ActivityScope products should be removed
from this page.

3.2.4.2. Up-sells or Down-sells from Order Management pages

o If proper up-sells or down-sells are configured in WC Accelerator, then during purchase flows
depending on the type of configuration, either in Review Order or Order Completion page they are
displayed in the bottom of the page. Customer, after clicking on the “Order Now” button, should
be navigated to shopping cart page as in existing functionality.

3.2.4.3. Cross-sells from Product Detail Page

o If proper cross-sells are configured WC Accelerator, then they are displayed in the Product
Detail pages. Once the customer clicks on the “Order Now” button on these configurations, the
customer should be taken to the Advanced Company Search page as explained in section 3.2.3.1
part of this document.
o All the other steps as mentioned in that section should be executed.

3.2.4.4. CSR making purchases on behalf of customers using “Login as Customer” option

o When CSR logs in as customer, the CSR is landed to the home page of the CD store. CSR
should able to do any of the activities as mentioned from sections 3.2.3 and 3.2.4 above.

3.2.5. Post-Conditions

o The product is successfully added to the shopping cart.

3.2.6. Service Level Requirements

N/A

3.3. Checking out from the Shopping Cart

3.3.1. Actors

• Customer – The user who will purchase the products form e-Commerce customer facing web sites
• CSR – Agent, who will make purchases on behalf of the customer by using the option “Login as
Customer” from Sales Direct store of e-Commerce website

3.3.2. Pre-conditions

o Either the customer or the CSR on behalf of the customer should have added the products
to the shopping cart.
o Either the CSR or the customer should click on “Check Out” button on My Order
(Shopping Cart) page.

3.3.3. Main Flow of events

5
Dun and Bradstreet, Inc. 28 October 2009
Confidential
3.3.3.1. Registered Customer Making Purchases in Un-Authenticated Mode

o Upon clicking on the “Check Out” button on the shopping cart (“My Order”) page, the
customer should be redirected to the “Login Page”, as in the existing process, where in the
customer enters their credentials.
o Upon successful login process, the existing logic of preparing the order for completion
should be done, in which the eligibility of the product being purchased is determined.
o If the customer is not from US (based on registration details), they should not be allowed
to proceed with the purchase of DNBi SMO product. In this case the message as given in section
BR 7.1.1 of BRD should be displayed at the top of the review order page.
o If the customer is identified as DNB contract (MDP, ADP, PPP), then the product should
not be sold to the customer. It is handled as part of the existing implementation, where in the
customer should not be given the option of buying it online. Instead they should be redirected to
call customer care.
o DNBi SMO product availability check should be performed as in the existing Sales
Direct store. If the product is not available, the error message given in the section 7.4 of the BRD
should be displayed.
o Any customer should have only and one active DNBi SMO product at any time in their
portfolio. For the customers buying this product if they have any DNBi SMO family product in
their portfolio should be displayed an error message as given in section 7.5 of BRD.
o If any customer is trying to buy more than one DNBi SMO in the same cart they should
be prevented from doing so by displaying a message as given in section 7.6 of BRD.
o Customers should not be allowed to purchase a Business Advantage or Risk Advisor
subscription if they already have an active DNBi SelfMonitor product in their portfolio. In this
case an error message as given in section 7.7 of BRD should be displayed.
o Customers should not be allowed to purchase both a DNBi SMO product and a Business
Advantage/Risk Advisor subscription in their cart at the same time. In such case, the error
message as given in section 7.8 of BRD should be displayed.
o An auto renew check box should be displayed and whose full design details are presented
in the section 3.5 of the current document.

3.3.4. Alternate Flows

3.3.4.1. Registered Customer Making Purchases in Authenticated Mode

o Except displaying the Login Page and checking the credentials of the customer, all the
steps as mentioned in 3.3.31 should be executed.

3.3.4.2. Unregistered Customer Making Purchases

o In this case the customer should first be navigated to the User Registration process as
done in the existing functionality of the current application in production.
o Upon successful registration of the customer, the same steps as mentioned in 3.3.31
should be executed, except displaying the Login Screen and checking of the credentials.

3.3.4.3. CSR Making Purchases on Behalf of the Customer through “Login as Customer” Option

o Except displaying the Login Page and checking the credentials of the customer, all the
steps as mentioned in 3.3.31 should be executed.

3.3.5. Post-Conditions

o The customer is successfully navigated to Review Order Page (Order Submission Page).

6
Dun and Bradstreet, Inc. 28 October 2009
Confidential
3.3.6. Service Level Requirements

N/A

3.4. Product Fulfilment and Order Finalization Process after Submitting the Order

3.4.1. Actors

• Customer – The user who will purchase the products form e-Commerce customer facing web sites
• CSR – Agent, who will make purchases on behalf of the customer by using the option “Login as
Customer” from Sales Direct store of e-Commerce website

3.4.2. Pre-conditions

o All purchase rules and eligibility criteria for the product fulfilment process are completed
positively.
o Either the CSR or the customer should click on “Submit Order” button on “Review
Order” (Order Submission) page.

3.4.3. Main Flow of events

3.4.3.1. Customers having Credit Card Details with e-Commerce

o While processing the order the current logic of fulfilment process should be leveraged.
o An XML request should be constructed and sent to DNBi/ESB for policy creation, and
product fulfilment as done in the existing Sales Direct functionality.
o If the received response is successful, then the customer should be billed against their
credit card on file.
o If the billing is not successful, then the item should be removed from the cart and product
not fulfilled message should be displayed on “Order Confirmation” page as done in the existing
implementation for other products.
o If the billing is successful, the product’s expiration date should be set to one year from
the date of this billing and the order should be finalized as done for all other products. Appropriate
message should be displayed to the customer after all these successful processing.
o If the customer chooses auto renew option, then auto renewal date should be set to the
next day of expiration date of the product, on which day the product should be renewed
automatically by charging the customer appropriately.
o If the response received from DNBi/ESB shows an error, appropriate error message
should be displayed to the customer on the screen.
o If the error from the external servers indicates that the sale is denied because of the
reason that this customer is a DNBi Core Customer, then the message as given in section 7.3.1 of
BRD should be displayed.

3.4.4. Alternate Flows

3.4.4.1. Customers not having Credit Card Details with e-Commerce

o The customer should be redirected to Hosted Order Page for registering their credit card
details with Central Payment Services of DNB. Upon successful registration of credit card details,
the same steps as given in section 3.4.3.1 of this document should be executed.

3.4.5. Post-Conditions

7
Dun and Bradstreet, Inc. 28 October 2009
Confidential
o The DNBi SMO should be available in the customer’s portfolio.

3.4.6. Service Level Requirements

o As the fulfilment involves with interactions form external interfaces, a specific time-out value
should be set for each such interaction. This time-out parameter should be a configurable one
during runtime.

3.5. Auto Renewal Functionality of DNBi SelfMonitor Product

3.5.1. Actors

• Customer – The user who will purchase the products form e-Commerce customer facing web sites
• CSR – Agent, who will make purchases on behalf of the customer by using the option “Login as
Customer” from Sales Direct store of e-Commerce website

3.5.2. Pre-conditions

o Either the customer or the CSR on behalf of the customer should have added the products
to the shopping cart.
o Either the CSR or the customer should click on “Check Out” button on My Order
(Shopping Cart) page.

3.5.3. Main Flow of events

3.5.3.1. Enabling/Disabling of Auto-Renewal Feature on DNBi SelfMonitor for the Customers

o A flag should be maintained at product level in the database which should indicate
whether this product is auto-renewable or not.
o At the time of launch of DNBi SMO initially, this flag should be set to OFF. The flag as
OFF indicates that the product is non-renewable.
o If the flag is ON at product level, then during purchase flow in “Review Order” page, a
check box should be displayed with checked by default as given in section 15.3 of BRD.
o If the customer leaves this check box as checked itself, then the fulfilled product should
be marked as auto-renew product and auto-renewal date should be set to next day to the expiration
date of the product.
o On the renew date, the customer should be charged automatically by offline billing
process. Both the successful and unsuccessful renewal process is described in UC-SMBS-DNBi-
SMO-OFFLINE-CHARGES document of Offline Charges module.
o If the customer un-checks the auto-renew check box, the product should be treated as
non-renewable.
o For DNBi/CA bundles, irrespective of the number of flags set to ON at product level,
only one check box should be shown to the customer.
o If the customer chooses the option of auto-renew, then only those products, for which the
flag is ON, should be marked as auto-renewable by setting the auto-renew date. The other
products should be treated as non-renewable.
o These should be designed as given in section 15.3.5.2 of BRD, where in it is explained
with examples.
o After the successful completion of the purchase of auto-renewable DNBi SMO product,
an email should be sent to the customer informing of them this feature. The template should be as
given in 15.4.1 of BRD.
o Customers should be given the option of disabling auto-renew feature through CSR post-
sale, but not directly on the customer facing CD web site. CSR initiates this process by clicking on

8
Dun and Bradstreet, Inc. 28 October 2009
Confidential
“Disable auto-renew” on the billing history section of customer account administration page on
Sales Direct.

3.5.4. Alternate Flows

N/A

3.5.5. Post-Conditions

o The product should be made auto-renewable /non-renewable respectively.

3.5.6. Service Level Requirements

N/A

4. References:
4.1. Documents
The business requirements for this component are available at:
https://collab.alliance-consulting.com/knowledgeTree/view.php?fDocumentId=8411

4.2. Glossary
o CD: Consumer Direct
o SMBS: Small and Medium Business Solutions
o MBC: My Business Credit
o N/A: Not Available
o DNBi CA: DNBi Credit Advisor
o ESB: Enterprise Service Bus
o WC: Websphere eCommerce Server
o DNBi SMO: DNBi SelfMonitor Online
o CSR: Customer Service Representative
o e-Commerce: http://smallbusiness.dnb.com, the e-Commerce site of D & B for serving the needs
of Small and Medium Business Solutions

You might also like