Enterprise DataWarehousing + Management Information

Data Warehousing To BI Reporting Ajay Uppal

My own estimation guide | 17/03/11 p Efforts cover design, development, documentation, security, testing, fix & deployment . Exclude Project Management, Training & Environment Management BI & DWH component Function Point Type Simple (FP / Efforts in man-days) Average Complex Staging Tables/ Non-SAP Extractors External Interface Files 5 FP / 5 man-days 7 FP / 7 man-days 10 FP/ 10 man-days Target Tables/ODS Internal Logical Files 7 FP / 3.5 man-days 10 FP / 5 man-days 15 FP / 7.5 man-days Dimension Tables Internal Logical Files 7 FP / 3.5 man-days 10 FP / 5 man-days 15 FP / 7.5 man-days Fact Tables Internal Logical Files 7 FP / 3.5 man-days 10 FP / 5 man-days 15 FP / 7.5 man-days Lookup Tables Internal Logical Files 7 FP / 3.5 man-days 10 FP / 5 man-days 15 FP / 7.5 man-days Mapping (ETL logic) External Inputs 4 FP / 2 man-days 5 FP/ 2.5 man-days 7 FP/ 3.5 man-days Process Alerts External Outputs 3 FP/ 1.5 man-days 4 FP/ 2 man-days 6 FP/ 3 man-days InfoCubes Internal Logical Files 7 FP / 3.5 man-days 10 FP / 5 man-days 15 FP / 7.5 man-days Multi-Cubes External Outputs 3 FP/ 1.5 man-days 4 FP/ 2 man-days 6 FP/ 3 man-days Queries External Inquiries 4 FP / 2 man-days 5 FP/ 2.5 man-days 7 FP/ 3.5 man-days

MIGRATING & UPGRADING TO SAP BI | 17/03/11 p A B C DWH SAP NetWeaver BI 7.0 D E F

BI / BW TO-BE FOOTPRINT | 17/03/11 p Flat File Upload Future?

Running the EDW – Real-Time Data Acquisition | 17/03/11 p

TYPICAL SAP BI IMPLEMENTATION PLAN 1/2 | 17/03/11 p

TYPICAL SAP BI IMPLEMENTATION PLAN 2/2 | 17/03/11 p

Contents of PQP 1. Project Quality Plan Overview 2. Programme Overview 3. Programme Organisation 4. Programme Governance 5. Programme Planning 6. Programme Management 7. Quality Assurance 8. Technical | 17/03/11 p

Programme Quality & Communication Plan | 17/03/11 p Mon Tues Wed Thurs Fri Meetings with Domains Programme Directors Steering Group MR PMs meet with R1 Manager Weekly R1 Team meeting Programme Leadership Meeting MR PMs /Domain leads draft status report Consolidated status reports Final Programme Weekly status Report Meetings Reports Additional Exceptional Reporting (PMO )

Interaction with Programme Delivery Mechanisms | 17/03/11 p Steering Group - Monthly Meeting Leadership Meeting - Weekly Meeting, consolidated weekly reporting Programme “Domains” / Maintenance Releases Weekly Meeting and structured consistent reporting Workstream Level Activities Regular schedule of reporting and meetings, determined by Domain leads QA3 QA2 QA1 External panel reviews as required, Updates to Steering Group forum Specific deep dive analysis of plan or areas of concern Provides guidance to Level 3 panel and support to Leadership Daily / ongoing whole team commitment Supported by Programme PMO. Documented in Project Quality Plan (see slide 6)

Quality Assurance Scope & Method | 17/03/11 p What? (objectives and scope of responsibilities) When? (Scheduling) How? (mechanism) Who? (membership) QA 1 To manage and deliver the programme using high quality processes and procedures. All Programme activities are in scope All Programme resources are responsible (with support from the Programme PMO) Ongoing – built into all activities. Use of Centrica and Wipro quality methodologies. Evidenced via weekly reporting. Whole Programme Team QA2 To assure that quality has been built into the programme by use of programme and non-programme resource and expertise. “ Deep dive” reviews of the plan. Targeted reviews of any specific areas of concern arising from the above Plan deep dives monthly. Other reviews as required. Deep dives to be led by PMO drawing on resources appropriate to subject under analysis. Outcomes to be fed back into Programme Board meeting. Operates independently of Programme Leadership meeting but may draw on some of it’s members, and will provide feedback / support to it. PMO led plan deep dives. Additional specialists to be invited to specific reviews, depending on topic areas being covered. QA3 To answer the questions: Is Programme fit for purpose? Can we maintain / operate the Programme solution? Will corporate systems / data remain secure? Can the Business accept / absorb the change we deliver? External panel review agenda to be determined as required, but likely to include: Review of Programme plan/critical path Top risks/issues Review with Programme domain leads Deeper investigations into key current issues Monthly / as required. Some standard agenda items followed by feedback from QA2 deep dives plus further discussion. Identify areas of concern for QA2 team to investigate over following period Steering Group membership as described in PQP governance. Panel membership to be confirmed, subject to need and specific requirements definition.

Typical Timing & Communication Plan | 17/03/11 p Timing Audience Channel Message By whom Jan BGB Wide SBU Headl message Beacon is coming Progress of UAT Alignment with other initiatives SW – Content AU – Production/Publish 8 th Jan BGB Wide Buddy Update Progress SW – content and distribution 15 th Jan BGB Wide Business Update Successes in December Key milestones for January – Key focus Any call to action/cascade of information team specific level SW – Content AU – Production/Publish 9 th , 12 th, 16th Jan Leicester Creative Initiative Market Stalls Posters SW- Event Mgmt AU – Publish Invite 16 th , 23 rd and 30 th Jan Leicester Creative Initiative UAT Open House AU- coordination and content of invite SW publish invite 22nd Jan BGB wide Intranet Training milestone message AU – content SW – publish 22 nd Jan Beacon Team Prog. Director Team update Progress and achievements SW – Content SG – Publish

Categorisation of Issues | 17/03/11 p An issue must be assessed and scored for impact (negative or beneficial). Issues include: A change in requirements A change in the environment An anticipated risk occurring An unanticipated problem occurring A problem or error occurring in work under way or completed A query about any aspect of the Project <50% R <75% O <90% Y >90% G SEVERITY HOW CONFIDENT ARE YOU THAT THIS WON’T AFFECT TIME / COST / QUALITY? High impact on project time, cost or quality Medium impact on project time, cost or quality Low impact on project time, cost or quality Minimal impact on project time, cost or quality

Categorisation of Risks | 17/03/11 p Risks include: Strategic/Commercial risks Economic/Financial Legal and Regulatory Organizational/ Management/ Human factors Technical/Operational/ Infrastructure ROYG Diagram <50% R O O R R <75% O Y O O R <90% Y G Y O O >90% G G G Y O G Y O R >90% <90% <75% <50% SEVERITY HOW CONFIDENT ARE YOU THAT THIS WON’T AFFECT TIME / COST / QUALITY? PROBABILITY HOW CONFIDENT ARE YOU THAT THIS WON’T OCCUR? High impact on project time, cost or quality Medium impact on project time, cost or quality Low impact on project time, cost or quality Minimal impact on project time, cost or quality

Programme Quality Plan | 17/03/11 p

Typical BW Extraction & Data Model | 17/03/11 p

Typical Deliverable 1. BW DEVELOPMENT STANDARDS 1.3 Assumptions 1.4 BW Overview 1.5 BW Development Process 1.5.1 Identification of Reporting Requirements: 1.5.2 New Reporting Requirements: 1.5.3 Technical Assessment: 1.5.4 Data Model Document 1.5.5 Data Extraction Document 1.6 Risk Assessment 1.7 Sizing 1.8 IMG Settings 1.10 Query Development 1.11 Web Development 1.11.1 Web Reporting / Design 1.11.2 Standard ‘’Company’’ Web Ad-hoc Template 1.11.3 Standards for Custom Web Development 1.11.4 Centrica Web Object Library 1.11.5 Centrica Branding 1.11.6 Information Broadcasting 1.12 Loading Data 1.12.1 Process Chains 1.13 Naming Standards 1.13.1 Basic Considerations 1.14 Administrator Workbench – Naming Standards 1.14.1 InfoObject Catalog 1.14.2 InfoObject 1.14.3 InfoArea 1.14.4 Infocubes/ODS 1.14.5 Aggregate 1.14.6 Routines 1.14.7 InfoSource – Transaction Data 1.14.8 InfoSource – Master Data 1.14.9 InfoPackage 1.14.10 InfoPackage Group 1.14.11 InfoSet 1.15 Business Explorer – Naming Standards 1.15.1 Variables 1.15.2 Restricted/Calculated Key Figures 1.15.3 Structures 1.15.4 Query 1.15.5 Temp Query 1.15.6 Web Templates 1.15.7 Role 1.15.8 Workbook 1.15.9 Exception 1.15.10 Scheduling Package for Exceptions 1.15.11 Scheduling Package for print Settings 1.16 R/3 – Naming Standards 1.16.1 Datasource (Transaction Data) 1.16.2 Datasource (Master Data) | 17/03/11 p 1.17 Process Chains – Naming Standards 1.17.1 Process Chain 1.17.2 Process Chain Folder 1.17.3 Variants for Process Types 1.17.4 Message 1.17.5 Process Type 1.18 Performance Considerations 1.18.1 MultiProviders 1.18.2 Aggregation 1.18.3 Pre Calculation 1.18.4 Reporting Agent 1.19 On/Off shore Development 1.20 Authorisations 1.21 Performance Review 1.22 Report Commentaries and BW documents 1.23 Variables

STREAMLINING BI ROLES & USERS BI Author IT & Business User who need to create reports for others Supports & trouble-shoot reports for others 2nd tier support Publish reports to roles BI Analyst Business Users who do their own analysis Create reports for their own use May present reports to others (using Bookmark) BI Consumer Informational Consumers who run prepared reports Doesn’t interact extensively with data Diversified in many ways (skill-sets, guided navigations etc) Standard Reports are developed by BI Development Team – Web Reports, Crystal Reports (going forward) | 17/03/11 p

ROADMAP – SAP BI & BUSINESS OBJECTS | 17/03/11 p

TYPICAL SUPPORT MODEL LEVERAGING EXISTING SET-UP | 17/03/11 p

Enterprise DataWarehousing + Management Information

More Related Content

What's hot (20)

Similar to Enterprise DataWarehousing + Management Information (20)

More from Ajay Kumar Uppal (20)

Enterprise DataWarehousing + Management Information

Editor's Notes