Difference between revisions of "Planning a SmartBilling Implementation"

From Smartbilling
Jump to: navigation, search
m (linked to Products, Services, etc. pages)
Line 6: Line 6:
 
== Planning a SmartBilling Implementation ==
 
== Planning a SmartBilling Implementation ==
  
 
+
: [[Creating a new instance for new company]]
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.
+
:: [[Users and  roles setup]]
<br/>
+
:: [[Data Migration]]
# '''Data Migration: migrate the Customer's current data into the SmartBilling database, and possibly the historical data as well:''' <span style="font-size:12px">
+
:: [[Data Integrations]]
## Import/Enter Sales Agent data
+
:: [[Additional configurations and modification (customizations)]]
## Import/Enter Customer data;
+
:: [[Testing the new instance]]
## 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; </span>
+
# '''Custom modifications: concurrently with the migration,''' <span style="font-size:12px">
+
## 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)</span>
+
# '''Training: concurrently with the migration,'''<span style="font-size:12px">
+
## 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.  </span>
+
# '''Implementation (following completion of the data migration & custom modifications):''' <span style="font-size:12px">
+
## 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.
+
</span>
+
  
 
<u>[[SmartBilling Documentation Home Page|Home]]</u> &nbsp;&nbsp;  
 
<u>[[SmartBilling Documentation Home Page|Home]]</u> &nbsp;&nbsp;  
 
<u>[[SmartBilling FAQ page|FAQ page]]</u> &nbsp;&nbsp;  
 
<u>[[SmartBilling FAQ page|FAQ page]]</u> &nbsp;&nbsp;  
 
<u>[[SmartBilling 5.0 pages|SmartBilling 5.0]]</u>
 
<u>[[SmartBilling 5.0 pages|SmartBilling 5.0]]</u>

Revision as of 11:04, 7 April 2021

Home    FAQ page    SmartBilling 5.0


Planning a SmartBilling Implementation

Creating a new instance for new company
Users and roles setup
Data Migration
Data Integrations
Additional configurations and modification (customizations)
Testing the new instance

Home    FAQ page    SmartBilling 5.0