Business Intelligence Services Capability and Architecture

1. Business Intelligence Services Capability and Architecture Assessment and Roadmap <date>Version: <n>

2. Project Overview Charter and approach Charter • Driver: What was the motivation for the engagement? What does the client want to accomplish? • Objective: What are the objectives of this engagement? • Deliverable: What are expected deliverables/outcome from this engagement? Approach • Duration: Length of the engagement? • Scope: Scope of the engagement? (see Statement of Work (SOW) • IT Services: Business Intelligence (BI) (any other services included?) • Technologies: Microsoft® Office SharePoint® Server and Microsoft® SQL Server® (any others?) • Information Sources: Direct interviews with services and technologies stakeholders information technology (IT). Mention if business stakeholders were also accessed/interviewed. • Framework: Service-based enterprise architecture framework from Microsoft. Acknowledgement • Business: Who in the business was interviewed or involved? • IT: Who in IT was involved or interviewed? • CoreTeam: <client> team members of the project and Microsoft team members

3. Agenda • Executive Summary • Strategic Assessment and Plan • Business environment • Strategic objectives • Key business processes • BI Business Capabilities – Desired and Current State • IT environment • IT Objectives • Capability map and maturity • BI Services map • Architecture vision • Roadmap • Impact • Benefits • Cost • Execution • Risks and Constraints • Governance • Operating Plan

4. Executive Summary Key challenges, observations and the solution/plan Problem Statement • Challenges, pain points, issues and opportunities? Key Observations • What did we “notice” worth mentioning here? Good/bad. Solution • What is the solution to the problem? Plan • How do we intend to make it happen? What are short-term, near-term, and long-term plans?

5. Strategic Assessment and Plan • Business environment • IT environment • IT architecture • Impact • Execution

6. Strategic Assessment and Plan Business environment IT environment IT architecture Impact Execution

7. Business Objectives and Plan Top level goals and capabilities needed to reach them • What is business trying to accomplish and why? • What connected business capabilities are needed to realize these objectives?

8. Key Business Processes Reviewed processes dependent on BI Capabilities • What are the business processes reviewed during the engagement? • What did we find – issues, requirements, impact. • What connected business capabilities do they need?

9. Business Architecture Identifying supporting business Capabilities Business capabilities supporting strategic objectives across business processes and functions are identified.

10. Business Architecture Supporting Business Capability Maturity <summary statement(s) about the maturity> Current State Desired State

11. IT Objectives Success factors and strategies <Summarize key objective(s)>

12. BI Services Enabling required business capabilities • BI Services and capabilities with contextual content can support most business capabilities needed to achieve strategic objectives • Update significant capabilities • Organizational capabilities required for realizing strategic objectives • Capture and deliver • Contextual • data *significant capabilities highlighted

13. BI Services Enabling required business capabilities • BI Services and capabilities with contextual content can support most business capabilities needed to achieve strategic objectives • Update significant capabilities • Organizational capabilities required for realizing strategic objectives • Capture and deliver • Contextual • data *significant capabilities highlighted

14. BI Services Capability maturity The functional, performance and operational characteristics of many information management services must be improved to enable desired business capabilities. Current State Desired State

15. BI Services Architecture Assessment and Vision

16. BI Services Architecture Capability View BI Services Client Interfaces Back Office Services • BI services provide a range of capabilities and are organized into four services domains • Application • Access • Information • Data services • Capabilities may be delivered or access from multiple channels such as mobile devices, web, or PC • BI services depend upon portal and collaboration services for access, distribution , publishing, and sharing data • Due to many strategic initiatives over the next few years, including enterprise customer system, smart meters and grids, the demand for broad spectrum of BI capabilities will significantly increase BI Application Services LOB App Supply Chain Dashboard & Scorecards Managed Reporting Operational BI Self-service BI Human Resources Office Control Systems BI Platform Services Web Browser Access Services Information Services Data Management Services Billing Presentation Reporting Master Data Management Data Storage Mobile Material Management Distribution Analysis Data Integration ETL Web Services Customer Management Financials Foundation: Infrastructure and Operations Services Firewall Load Balancing Security Database Storage Monitoring Workload Management Remote Access Clustering (High Avail) Directory Server OS Backup/ Recovery Auditing/Logging …

17. BI Services Architecture Component View BI Reference Model and BI Applications Archetypes provide detailed technical decomposition of many BI services. The component view is useful for the design, organization, integration, and reuse of any BI solution. Each component is evaluated in terms of current implementation(s), potential constraints, and architecture direction to support desired scalability, functionality, and performance. BI Application Services Derived from BI Application Archetypes Dashboard and Scorecards KPI Management Configuration Consolidation & Integration Events and Monitoring Managed Reporting Operational BI Self-service BI Client Interfaces BI Platform Services Derived from BI Reference Model Client Interfaces Access Services LOB App Presentation Distribution Security Sile Subsystem Ui Control Manager Presentation Format Mgr Delivery Subsystem Schedule Manager Office Page Layout Subsystem Print Manager Alert Manager Publishing Subsystem Subscription Manager Database Web Browser Information Storage Reporting Analysis Report Authoring Tool Report Data Manager Reporting Monitoring Report Subscription OLAP Authoring Tool Data Mining Subsystem Analysis Management Monitoring Mobile Rep. Rendering Subsystem Report Catalog Manager Report Delivery Manager Report Management Cube Subsystem Analysis Storage Backup/Recovery Web Services Data Master Data Management ETL Data Storage Data Integration Auditing/Logging Extract Subsystem Load Subsystem Data mart ODS Replication Transformation Subsystem ETL Management DW OLAP Data Exchange Data Consumers and Providers See BI Reference Model and Archetype documents for details.

18. BI Applications Services Assessment and Plans The application services are business-facing, high-level services provided by instantiating and/or leveraging platform services • KPI Management: Need capability to define and aggregate KPIs at individual (role), departmental, process levels. Currently only financial (lagging indicators) KPIs are reported. • Configuration: A business function should be able to configure what (balanced scorecard) they want to monitor and manage. Currently pre-defined financial view of the group is presented. • Consolidation and Integration: Process KPIs would require data from multiple data sources combined and rationalized to show correlation and to drill down into specific functional area. • Events and Monitoring: In most cases, dashboards are updated monthly. To respond to fluctuating demand and supply, must have dynamic, event-driven dashboards. Dashboard and Scorecards Managed Reporting • Each lines of business (LOB) application and business groups have their own way to managing reports. Must provide consistent user experience and mechanism to identify, produce, distribute and archive reports. Operational BI • Operational reporting and analysis is going to be very critical for internal management as well as for customers to monitor, manage and plan energy consumption and cost. Must consider near real-time meter data gathering and price monitoring, consolidation, reporting, distribution and notification. Self-Service BI Customers and business users should be able to create their own custom reports and analytics. Must provide provisioning of data where the data required for reporting and analysis is not already available.

19. BI Services Architecture Technical View The following architecture models the range of capabilities and interfaces related to BI services. Over time, users want to have a unified and consistent experience across all types of information and transactions. The information access relies on portal and collaboration services for a single point of interface. Users would expect close to real-time analysis and reporting. The underlying technical architecture must be scalable and flexible to process large volume of data. External and internal users may need to have access to similar information. The breadth and depth of integration with data and applications, along with security considerations may drive separation between internal and external access. Note: A server in the diagram does not necessarily imply a separate physical hardware. It is meant to represent a service. The physical implementation of a service or capability may use one or more hardware components.

20. BI Services Current architecture assessment Identify current state and issues – what works (good), what is a concern they must watch/evaluate, what is design constraint or show stopper they must address soon

21. BI Services Technology and physical architecture Assessment of technology and physical architecture implementing BI capabilities

22. BI Services Architecture designed for growth

23. BI Services Roadmap • Short-term: ?? • Mid-term: ?? • Long-term: ?? Short-term (< 6 months) Foundation Mid-term (< 18 months) Analytics Long-term Business of the Future Dashboard and Scorecards Team KPIs Team Dashboards Enterprise Dashboards Modeling Forecasting Scorecards Access Portal: Pull Distribution Push Distribution Publishing Off-line Excel Services Information Reporting Analytics Visualization Data Mining Real-time Data Functional Data Marts & Cubes Notification Services DW to Data Mart/Cube data transformation Master Data Management Infrastructure Partitioning Object-level security Monitoring Provisioning Archiving Clustering Clustering ETL Performance Projects DW and ODS security assessment and planning Operational practices implementation. For example, monitoring, change management, capacity planning DW design optimization Microsoft Office SharePoint Server BI services configuration SQL Server 2008 Upgrade

24. Impact Business and IT benefits Business • ?? IT • ?? Others • ??

25. Execution Potential risks and constraints List implementation and operating costs by phases, if possible • It may not be feasible to estimate cost of all projects. You may just want to provide some estimates for next phase of projects or high-order of estimate for realizing the overall vision. • Include internal and external costs Implementation • Internal • External (HW/SW, Services) Operating • Internal Support • External (Maintenance etc.) Others • ??

26. Execution Potential risks and constraints List potential risks and constraints. Provide a way to mitigate these risks and constraints Business • Adoption risk? IT • Project execution • Skills • Technology Others • ??

27. Execution Implementation Plan Hardware • What should be done for hardware – sufficient or buy? Software • Is the required software already purchased or is there a need to buy? Project activities to address short-term needs • Identify key projects and provide short description of each project Project activities to address mid-term needs • Identify key projects and provide short description of each project

28. Conclusion and Roadmap Summary of key points • IT objectives and current state • Desired BI capabilities • Approach • Next steps

29. © 2010 Microsoft Corporation. All rights reserved. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication andis subject to change at any time without notice to you. This document and its contents are provided AS IS without warranty of any kind, and should not be interpreted as an offer or commitment on the partof Microsoft, and Microsoft cannot guarantee the accuracy of any information presented. The information in this document represents the current view of Microsoft on the content. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT. The descriptions of other companies’ products in this document, if any, are provided only as a convenience to you. Any such references should not be considered an endorsement or support by Microsoft. Microsoft cannot guarantee their accuracy, and the products may change over time. Also, the descriptions are intended as brief highlights to aid understanding, rather than as thorough coverage. For authoritative descriptions of these products, please consult their respective manufacturers.