This guideline outlines the strategy and activities required to complete the implementation of Varibill successfully.
TABLE OF CONTENTS
Assumptions and Constraints
- A Varibill account is setup and accessible.
- Source Systems track usage of products and services.
- The Source System has an API or other method of communication (SSH, Database, etc.) available to extract read-only data
- Implementation may be affected by employees’ normal workload which may prevent them from completing the initial setup, training with and using the new application.
Minimum Hardware and Software Requirements
- The actual hardware and software requirements will depend on the size and scale of the Customers’ requirements. The design decision regarding hardware and software falls outside of the scope of this implementation.
- All third party software, except where specifically noted, must be installed, configured and maintained by the client and falls outside of the scope of this implementation.
- The client will be responsible for licencing of all 3rd party software required.
- All third party software must be on a version supported by the vendor.
- All third party software with which Varibill must integrate must have a vendor provided API available.
- The client is also responsible for the license, setup and monitoring of business continuity and disaster recovery.
- Varibill requires SMTP functionality, and as such will implement an SMTP server for the delivery of email. The client can elect to have the Varibill SMTP server directly deliver the email to the destinations, with consideration given to SPF, DKIM and the requisite firewall policies to ensure the proper flow of emails. The client can also elect to have the Varibill SMTP server relay the emails to a smart host, over an unauthenticated, port 25 connection. In this case the client is responsible to ensure that the proper IP filtering, relay permissions and firewall rules are implemented for the smart host relaying to work properly. Varibill prefers to directly deliver emails, for simplicity.
- Consultation to understand the requirements of the Source Collector, including the products/services that should be collected as well as the method of billing for these products/services.
- Development of the Source Collector.
- Testing of Source Collector.
- Sample data extract using the Source Collector.
- Implementation of the Source Collector.
- Training, if required
Varibill follows an “instant-on” implementation methodology. Once project scope items 1 have been completed the Source Collector will start importing billing data at the scheduled time. The date of Production implementation is dependent on the type of information imported by the Source Collector.
Billing data will be imported into Pre-Production (if available) up to the point that the Source Collector is implemented in Production.
- Source Analysis - Product and Billing methodology
- Review products to be collected per source.
- Provision Source Collector Server
- Source Collector Server. (Preferred if required)
- Ensure the Varibill API is reachable via the API URL.
- Ensure Source System hostname and port is accessible from the Source Collector server.
- Varibill requires relay permission via an SMTP server. Configure your SMTP settings to allow system notifications to be sent from Varibill. This SMTP server should allow anonymous connections on port 25 and should not require SSL or TLS. The SMTP server should allow message relay from the Varibill host server. The required allowances should be made for SPF, DKIM and other protection mechanisms.
- Provide Remote Access
- Provide the Varibill technical team with remote access, including a read-only username and non-expiring password, in order to complete the required setup.
- Install additional Software required
- JDK (if applicable)
- Download and install the latest version of the Java Development Kit on the Source Collector server (Available here)
- Setup Source Collector on Varibill
- Design and Develop the Source Collector
- Extract sample data
- Client sign-off on extract of subset data collected using the developed Source Collector
- Implement Source Collector
- Schedule the execution of the Source Collector according to requirements.
- Pre-Production Dry run
- Confirm that all the billing data is imported correctly
- Terminate contract services, if required.
- Update product codes, if required.
- Configure the Source Collector to import billing data into the Production environment.
- Import Historic Data (optional).
- Document the Source Collector and related processes.
- Training - on Source Collector and related processes.
A successful implementation can be seen as one where:
- A Source Collector has been configured and accurately imports data into a Pre-Production / Production environment.
- Varibill has collected all usage-data for the period <<>> to <<>>.
- Varibill has collected all products expected to be collected for the billing period specified.
- Varibill has collected at the correct unit of measure per product.
- Varibill has collected the correct quantity and dates provisioned.
- The record ID is collected in an acceptable format.
- Authorised users can configure Source Collectors via Varibill.
- Authorised users can view imported billing data using Varibill