Difference between revisions of "Planning a SmartBilling Implementation"
From Smartbilling
(New page: Planning a SmartBilling Implementation) |
m (linked to Products, Services, etc. pages) |
||
Line 16: | Line 16: | ||
## Import/Enter Customer Contact data; | ## Import/Enter Customer Contact data; | ||
## Import/Enter Customer Notes data; | ## Import/Enter Customer Notes data; | ||
− | ## Together with the Customer, create the SmartBilling Catalog of [[ | + | ## Together with the Customer, create the SmartBilling Catalog of [[Products]], [[Services]], [[Charges]], [[Sub-Charges]] and Usage [[Rates]]; establish [[Contract Types]] durations & renewals |
## Import/Enter the Subscription data (linked to Customer, Supplier, Contract, subscribed catalog items); | ## Import/Enter the Subscription data (linked to Customer, Supplier, Contract, subscribed catalog items); | ||
## Import historical Balance Forward, Invoice, Payment & Adjustment data; Import historical Invoice .PDF files. | ## Import historical Balance Forward, Invoice, Payment & Adjustment data; Import historical Invoice .PDF files. |
Revision as of 14:56, 9 February 2017
Home FAQ page SmartBilling 5.0
Planning a SmartBilling Implementation
Below is a list of the various steps that can occur during a data migration from a Customer's existing database into the SmartBilling Database.
- Data Migration: migrate the Customer's current data into the SmartBilling database, and possibly the historical data as well:
- Import/Enter Sales Agent data
- Import/Enter Customer data;
- Import/Enter Supplier data;
- Import/Enter Service Location data;
- Import/Enter Customer Contact data;
- Import/Enter Customer Notes data;
- Together with the Customer, create the SmartBilling Catalog of Products, Services, Charges, Sub-Charges and Usage Rates; establish Contract Types durations & renewals
- Import/Enter the Subscription data (linked to Customer, Supplier, Contract, subscribed catalog items);
- Import historical Balance Forward, Invoice, Payment & Adjustment data; Import historical Invoice .PDF files.
- Import/Enter Historical Ticketing data; Import/Enter Historical Prospects & Activity data;
- Design & code the Invoice template according to the Customer’s needs;
- Design & code the various Usage Import templates according to the Customer’s needs; (Avalo CDRs, and other external usage data as required)
- Define, design & code any custom reports that may be required;
- Define, design & code any other templates that may be required; (Customer Statement, Sales Quotation, Commission Reports, etc.)
- Define, design & code any other custom modifications that may be required. (APIs, other functionalities)
- Provide Customer training;
- Define & add any custom fields that the customer may require and train customer to enter & maintain them;
- Configure the various operational parameters and train customer to maintain them;
- Configure the Financial Institution parameters, test the integrations and train customer to maintain them;
- Establish Commission Plans and train customer to enter & maintain them.
- Execute initial testing to ensure that the system is functioning properly;
- Execute ‘parallel operation’ for at least one month’s worth of transactions, either on the full set of customers, or on a set of sample customers that are representative of the different use-cases present in the Customer’s database;
- Switch over to live operation.