Implementation Plan Source Collector

Transcription

1 Implementation Plan Source Collector Last Modified: :09 AM Version: 11.0 Page 1 of 10

2 Table of Contents 1. Introduction Purpose System Overview Assumptions and Constraints System Architecture Management Overview Description of Implementation Points-of-Contact Major Tasks Implementation Support Acceptance Criteria Appendix B: References... 9 Page 2 of 10

3 1. Introduction 1.1. Purpose This implementation plan outline the strategy and activities required to successfully complete the implementation of Varibill Source Collectors System Overview Varibill is a billing system which is offered as an on-premise or Cloud based Software-as-a-Service solution. Varibill is equipped to cater for both recurring and usage-based billing and integrates with your accounting system for the purpose of invoice processing. Varibill is able to automatically collect data from heterogeneous source systems to bill according to the quantities of products and services consumed by clients. This requires a once-off setup and possible integration into various source systems. Once this initial setup is complete, the integration settings can be managed via Varibill. This provides the client with the flexibility to integrate with as many source systems as required and eliminates any manual intervention during billing processing Assumptions and Constraints Assumptions 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 work load which may prevent them from completing the initial setup, training with and using the new application. Page 3 of 10

4 System Architecture Page 4 of 10

5 Minimum Hardware and Software Requirements 1. 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, but needs to conform to the best practices as defined by Microsoft for Microsoft 2012 R2 Standard, or higher, to ensure the optimal performance, availability and redundancy as required by the client. 2. 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. 3. The client will be responsible for licencing of all 3rd party software required. 4. All third party software must be on a version supported by the vendor. 5. All third party software with which Varibill must integrate must have a vendor provided API available. 6. The client is also responsible for the license, setup and monitoring of business continuity and disaster recovery. 7. Varibill requires SMTP functionality, and as such will implement an SMTP server for the delivery of . The client can elect to have the Varibill SMTP server directly deliver the to the destinations, with consideration given to SPF, DKIM and the requisite firewall policies to ensure the proper flow of s. The client can also elect to have the Varibill SMTP server relay the s 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 s, for simplicity. 8. Varibill recommendeds a stand-alone machine (best practice), virtual or physical, that meets the minimum requirements of the selected operating system. 9. The Source Collector server must have access to the applicable source system hosts. 10. The selected operating system must support the latest JDK (Java Development Kit). It can be downloaded here. 11. Ensure that port 80 (http) and 443 (https) are open to the Varibill API (The cloud based API is api.varibill.com) 12. Connectivity should be available to all source systems from the Source Collector machine. 13. Ensure the source system hostname and port are accessible from the Source Collector server. 2. Management Overview 2.1. Description of Implementation Project Scope 1. 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. Page 5 of 10

6 2. Development of the Source Collector. 3. Testing of Source Collector. 4. Sample data extract using the Source Collector. 5. Implementation of the Source Collector. 6. Training, if required. Approach 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 Points-of-Contact This section of the Implementation Plan identifies the stakeholders involved in and who serve as points of contact for the system implementation. Role Name Contact Number Varibill Implementation Consultant Varibill Client Business Sponsor Project/Program Manager Client Client Implementation Representative Page 6 of 10

7 2.3. Major Tasks [Microsoft Project Implementation Template] Product & Billing methodology Source Analysis Task Description Responsible Resource Review products to be collected per source. Appendix B: References / Product Source Analysis Sheet Varibill / Client Provision Source Collector Server Source Collector Server. (Preferred if required) Client Provide Remote Access Install additional Software required JDK (if applicable) Setup Source Collector on Varibill Design and Develop the Source Collector Extract sample data 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 the Varibill technical team with remote access, including a read-only username and non-expiring password, in order to complete the required setup. Download and install the latest version of the Java Development Kit on the Source Collector server. (Available here) Create a Source Collector on Varibill. Design and develop the Source Collector. Client sign-off on extract of subset data collected using the developed Source Collector Client Client Client Client Client Varibill / Client Varibill / Client Varibill / Client Page 7 of 10

8 Implement Source Collector Schedule Source Collector Pre-Production Dry run Production Implementation Import Historic Data Task Description Responsible Resource Implement the Source Collector. Schedule the execution of the Source Collector according to requirements. 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. (Optional) Varibill / Client Varibill / Client Client / Client Implementation Representative Client Implementation Representative Client Implementation Representative Varibill / Client Client / Client Implementation Representative Documentation Document the Source Collector and related processes Varibill Training Train the customer on Source Collector and related processes Varibill / Client Page 8 of 10

9 3. Implementation Support Varibill has user guides that the implementation team can make use of. Alternatively the implementation team can contact the appropriate person as listed in 2.2 (points-of-contact). 4. Acceptance Criteria A successful implementation can be seen as one where: 1. A Source Collector has been configured and accurately imports data into a Pre-Production / Production environment. 2. Authorised users can configure Source Collectors via Varibill. 3. Authorised users can view imported billing data using Varibill. Page 9 of 10

10 5. Appendix B: References The following table summarizes the documents referenced in this document. Document Name Product Source Analysis Sheet Billing Data Template Implementation Plan Source Collectors Implementation Checklist Source Collectors Source Collector Setup Process Description Used to map products to source systems and determine the details to be imported. Used to import the data for which invoices must be generated. The Source Collector must be configured to import data in the same format. Describes the implementation project, resources required, duration and start date. Used to ensure all activities during the Source Collector implementation is completed. To describe the various activities to be performed and the order in which it should be done. Page 10 of 10