1. Introduction to Business Intelligence DATE

2. Insight R2 “Pre-canned” reports, based on Liberate, to our business units Back-end database uses MS SQL 2005 Front-end uses SAP Business Objects 3.1 BI Developments Summary 2Introduction to Business Intelligence | Date 3.1 Insight R3 19 “Universes” allowing business to create their own reports All reports based on Liberate, with additional universes added by LIME Back end uses MS SQL 2008 Front-end uses SAP Business Objects 4.1 4.1 Currently being decommissioned (LIME, Macau/CTM)

3. Enterprise Data Warehouse / Operational Data store / KPI reporting 3 month store of operational data including Liberate and other data sources Mediation Zone + MS SQL 2012 + Excel Big Data Migration to Amazon Web Services Set up and migration of EDW / ODS to AWS BI Developments Summary - Continued 3Introduction to Business Intelligence | Date Others Event Data Store (we provide the feeds) Other Legacy: MIDAS, BI Lite, Focus

4. Roadmap Bahamas data New data feeds into EDW (in progress) Modification of code to allow for KPI production Fixed KPIs Release Fixed KPIs for all BUs (Mobile already exists) AWS Redshift Migration Currently in design; template set up First domain (CDR classification) due to migrate April 2014 with other domains following Transition Planning Support of the Group Commercial reporting analysts – new Business Information Layers in the EDW Knowledge transfer Decommission Insight R2 and Legacy systems LIME switch off (in progress) Migration from JCC Feeds into Liberate Landing server, SQL replication Other developments Mediation Zone feeds from all sources and onwards to EDW / EDS, Campaign Management 4Introduction to the Development Team | date The BI Roadmap 2014

5. Insight R2 5Introduction to Business Intelligence | Date Canned reports only – scheduled to refresh daily In use at BUs: LIME (decommissioning in progress) Macau The Backend is not being switched off as most BUs do their own reporting, so have taken Insight R2 for the JCC / CIS feed TSTT / Panama / SURE

6. Insight R3 6Introduction to Business Intelligence | Date Self Service (users can create their own reports) 130+ “canned reports” have been carried over from R2 (scheduled to refresh daily) 19 “Universes” covering: Accounts, Adjustments, Churn, Customer queries, Debt, Faults, Pricing Plans, Product trends, Sales, Service Orders Reports are based on Liberate, with some additional universes added by LIME Accounts Adjustments Churn Customer Queries Debt Faults ….. …. None of these reports contain “usage” information! What ?..When ?.. Who? …. Why?

7. KPI reporting 7Introduction to Business Intelligence | Date A need was identified to have a single source of information for Group reporting, i.e. not just BU specific CWC built a set of KPI reports to allow for this senior management / exco view of data required

8. Operational Data Store 8Introduction to Business Intelligence | Date Requirement for “usage” data to be able to calculate revenue and trends The ODS holds 3 months / 125 days of usage data and resulting KPI information Sources are taken from Liberate and other sources (GGSN, Interconnect, Telus (call centre stats)) Current reports – subscriber active base for: Prepaid mobile Fixed lines of Business All LIME business units, except Bahamas postpaid Current users are the BI Commercial reporting team (access ODS and run adhoc SQL queries)

9. ODS reporting KPI ODS Comverse ONE Core mobile network GGSN InterConnect Liberate 9Introduction to Business Intelligence | Date

10. ODS Challenges 10Introduction to Business Intelligence | Date Big data issue: MS-SQL server 2012 good for small –> medium enterprise reporting The CDR table currently has 1.9 billion records and is 155GB in size! 1.7 TB – ODS, BIL – 430 GB (compressed) As reporting wants to join more and more data together we need to embrace newer technologies to cope with demand

11. The problem we are trying to overcome – Housing our Big Data efficiently: Amazon Web Services - Redshift 11Introduction to Business Intelligence | Date

12. We need to be able to set up and migrate our data simply: Amazon Web Services - Redshift 12Introduction to Business Intelligence | Date

13. Amazon Web Services - Redshift 13Introduction to Business Intelligence | Date It needs to be scalable:

14. And resilient Amazon Web Services - Redshift 14Introduction to Business Intelligence | Date As well as cost effective!

15. Big Data, Redshift, the next 6 months Our Redshift project is truly under way This is being run as an Agile project; we expect to migrate most of the ODS in 12 sprints. Solution Architecture, Designs and Templates have been created We will look to migrate the most complex and long running queries and KPIs first – particularly CDR classification. 15Introduction to Business Intelligence | Date

16. And it’s a big job! 16Introduction to Business Intelligence | Date

17. The challenge: Lots of useful usage data is wasted (location data, mobile data usage) Some CDR storage is broken (MIDAS, Comverse DB) LEA and other regulatory requirements are difficult and costly to comply with Analysing how our subscribers use our services is difficult EDS complements ODS/EDW by providing long-term usage storage with query capabilities. What EDS is: Long-term and cost-effective way to store and query detailed data Uses commodity hardware and attached disk for better $/GB performance Managed service to keep solution running within SLAs Service to Marketing to provide on-demand “what-if” queries on subscriber usage Service for LEA and other regulatory requirements Query tool for back-office charging and billing investigations Event Data Store in One Slide 17Introduction to Business Intelligence | Date

18. 18Introduction to Business Intelligence | Date Current State of Play - Major Systems Gap Churn / Upgrades CampaignsOperations Supply Chain Network Capacity Channel Commercial / Finance Disclosure / Regulatory Product Management Sales Assurance Service Usage CRM Cust Insight CEM Customer Usage Event Data ComverseONE migration creates new usage storage requirements Retirement of legacy CDR (MIDAS) repositories creates a system gap Increased business demands to understand usage habits and trends Lack of compliance with regulatory requirements on usage storage and LEA search requests

19. Operational Service to our Customers 19Introduction to Business Intelligence | Date Ensure un-interrupted service of information delivery on daily, weekly and monthly basis Communicate any delays/impediments in information delivery to our customers (Commercial Analyst Team and Senior Executives) Triage with source teams and our BI development team to resolve any impediments Daily Weekly Monthly

20. Service back to BI DevOps 20Introduction to Business Intelligence | Date Share any exceptions in performance statistics of processes for recommendations on further performance tuning Provide operational requirements in the development stage of any new systems/developments Estimate the capacity requirements for hosting data from new source systems and run continuous capacity management

21. Service to Management 21Introduction to Business Intelligence | Date Publish dashboards that show operations performance quantitatively and qualitatively Help highlight the best and worst performers in terms of KPIs (zero values, long running, delayed) and data load jobs from operations perspective

22. Key Takeaways 22Introduction to Business Intelligence | Date Insight R2 is being decommissioned, but the backend will remain – as BUs want CIS data (JCC feed) Insight R3 is in use in LIME Enterprise Data Warehouse = Operational Data store KPI reporting -> high visibility and commercially sensitive Event Data Store –> not a BI Development project, as run by Tony Melvin and as a managed service by Cartesian Other Legacy (not in our scope): MIDAS, BI Lite, Focus End users – we get requests in from everywhere. Ideally, requirements will align to a qualified business need. Reporting requests do not necessarily come to the development team