Score Card Phase I Ii Edw Charter


Published on

The following charter focuses specifically on EDW plans which support the Management Accounting Project (MAP) / Standard Costing Organizational Reporting Environment (SCORE) initiatives. Client and IT Partner group activities, plans and costs are not included.

  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Score Card Phase I Ii Edw Charter

  1. 1. PACIFIC BELL PRISM Job Aid Page 1 of 8 Project Charter STANDARD COSTING ORGANIZATIONAL REPORTING ENVIRONMENT (SCORE) Prepared by: Orlando Moreno 408.656.2498 Date: 408.656.2498
  2. 2. PACIFIC BELL PRISM Job Aid Page 2 of 8 Project Charter Work Effort Name: SCORE / Management Accounting Work Effort ID: EAP Program Prepared By : Orlando Moreno UUID: JS5312 Phone: 408-656-2498 Date Created: August 6, 2003 Document Version: 1.0 Last Updated By: Orlando Moreno Date: 11/04/2003 Last Updated By: Date: Note: The following charter focuses specifically on EDW plans which support the Management Accounting Project (MAP) / Standard Costing Organizational Reporting Environment (SCORE) initiatives. Client and IT Partner group activities, plans and costs are not included. Project Description Standard Costing – Income Statement The Management Accounting Project will provide a Standard Costing system for SBC Wireline Operations. The System will establish significantly enhanced cost control by measuring and reporting results in operational terms. Factory results will be measured based upon cost/unit performance. Geographic results will capture costs driven by volumes, allowing for a complete picture of the impact those organizations have on the SBC bottom line. This information will drive a results oriented organization to focus on products that achieve the best marginal return to SBC. Factories will be focused on impacting costs they control and not have results skewed by significant deviations from plan resulting from unexpected sales volumes. The focus will improve cost reduction initiatives throughout SBC. The information will also provide benchmarking capabilities at the activity level, allowing management to quickly identify opportunities for cost reduction and/or service improvement. Standard Costing – Capital (only Proof-of-Concept and Basic Design work approved) A Capital Costing system will be developed. This addition to the overall understanding of SBC’s cost structure will include a charge for capital to individual products. Information regarding available capacity at the Network Element level will provide support for business case analysis and target setting. The result will be enhanced controls over capital spending. This process will also enhance comparability between regions as the network elements are measured using a common definition across all of SBC. Customer Reporting (potential future enhancement) Costing information will be available on a greater number of products with more complete information regarding expense and capital. Enhanced work on identifying fixed/variable and direct/indirect costs at the customer and product level will create a more accurate view of profitability for the selected dimension. Reporting on Customer segments, including Consumer, SME, Major and Carrier, will support the needs of Sales and Marketing to improve analysis and target marketing strategies. Current Environment – Business Problem Phase 1 of the Management Accounting Project delivers profitability on a different basis than is currently available through the existing Management Reporting 2000 (MR2000) application. MR2000 uses a responsibility center approach whereas MAP Phase 1 will use a process and activity based approach to costing. MR2000 maps costs to responsibility codes (RCs) in a high level process that matches costs to revenues based on organization. This groups costs with potentially very different patterns of expenditure and purpose together and ties them to revenues to which they may individually lack a direct or indirect relationship. By comparison, Phase 1 extends the activity based costing Navigator system to break down costs based on process and activity and matches costs to the revenues that they support. This alignment recognizes a causal relationship between cost and revenue. MR2000 does not match all costs to revenues, while MAP Phase 1 will process costs to both a greater level of completeness and detail. MR2000 is based on a responsibility center approach that uses organization to map costs to revenues, leaving significant costs that are not aligned to revenues (see diagram following page). No reporting application currently provides a completely allocated profit and loss view - all views are subsets of total wireline cost. By comparison, Phase 1 matches costs to revenue as applicable to the reporting dimension (e.g. direct fixed costs by region, indirect variables costs by product and thence to the region in which the product is sold). Specific differences include:  Fixed vs. Variable Differentiation in Phase 1: No differentiation exists between fixed and variable costs in either MR2000 or Navigator. Phase 1 reclassifies costs into sub-cost pools on a fixed and variable basis for all in-scope costs. 408.656.2498
  3. 3. PACIFIC BELL PRISM Job Aid Page 3 of 8 Project Charter  Allocation of General & Administration in Phase 1: G&A is pooled into one (MR2000) or a small number (Navigator) of undifferentiated buckets currently. Phase 1 takes a portion of these costs through the assignment and allocation process to increase coverage.  Additional Legal Entities in Phase 1: Phase 1 augments the number of legal entities, e.g. SBC Services, costed within Navigator prior to their integration into the MR2000 reporting environment (see point 5).  Groundwork for Standard Costing in Phase 1: Neither MR2000 nor Navigator include standard costing. Phase 1 sets the groundwork for standard costing in its re-design of the costing process. MR2000 does not factor volumes into its costing approach and MAP Phase 1 will. MR2000 matches cost to revenue without reference to volumes. Navigator use volumes as drivers but does not report them in its current standard reports. MR2000 does not use volume within its assignment process. By Comparison, Phase 1 requires an integration of revenue, cost and volume around the initial reporting object of region. MR2000 and MAP Phase 1 treat depreciation and capital cost differently. MR2000 views depreciation and capital costs in relation to revenue or operating expense at highly aggregated levels. Phase 1 applies a methodology to capital charges that anticipates the deployment of a logical network element based working model similar in purpose to that for operating expenses. This will complete cost coverage and provide more complete measures of total profitability. MR2000 does not include Navigator-based reporting and MAP Phase 1 will. Navigator data is currently not available in the MR2000 reporting interfaces. Phase 1 will integrate Navigator allocated data back into the MR2000 reporting environment where it will be more accessible to a greater number of users in a familiar format so that the organization will begin using Navigator data more prevalently. Project Objectives To address the business problems identified above, the MAP/SCORE EDW project objectives for Phase I/II are to: A. Add mechanized revenue state dimension, improve RC Hierarchy logic, add Midwest ASI & AIT Non- Switched volumes to MR2000 in order to provide the complete reporting functionality required in the attached MAP/SCORE requirements document: (State, RC Hierarchy, Midwest ASI - October 2003 Release; AIT Non-Switched – Jan 2004 Release?) B. Acquire and store mechanized messaging revenue from SMSI, PBIS and PETS/AS400 into the EDW, MR2000 data mart, MR2000 application, and SCORE application. (SMSI – Oct 2003 Release; PBIS, PETS/AS400 – June 2004 Release?) Users Approximately 100 executives and financial analysts will access the system at the end of 2003. Client/Sponsor Information Sponsor VP: Pete Ritcher – Corporate Finance Client Exec. Dir: Jerry Healy – Corporate Finance Client PM: Jerry Healy IT Project Lead: Carol Steiner – ERS 408.656.2498
  4. 4. PACIFIC BELL PRISM Job Aid Page 4 of 8 Project Charter Proposed Solution The high level EDW solution architecture for this initiative, for MAP Phases 1 and 2, are located in the following document: C:Documents and Settingsjs5312My DocumentsManagement AccountingGeneral Project InformationProject CharterMAP MR2000 Architecture V1.doc In Scope (EDW) 1. Add state code to MR2000 revenue detailed core tables, MR2000 summary core tables, and MR2000 summary mart tables. Update default state code value for existing volumes and expense MR2000 detailed core tables and MR2000 summary mart tables. 2. Update RC Hierarchy processing to better match parent RC to proper high level organizational RC. 3. Implement new monthly Midwest ASI mechanized volumes core to MR2000 detailed core process. 4. Implement new daily and monthly mechanized SMSI Messaging revenue core to mart process. 5. Implement new monthly Midwest AIT Non-Switched mechanized volumes core to MR2000 detailed core process. 6. Acquire new BTN level PETS/AS400 Messaging journal source feed into EDW core, and implement new monthly mechanized PETS/AS400 Messaging core to mart process. 7. Acquire new BTN level PBIS Messaging journal source feed into EDW core, and implement new monthly mechanized PETS/AS400 Messaging core to mart process. 8. Provide design and data modeling consultation to ERS on MAP/SCORE reporting application. 9. Provide feasibility assessment for Capital Score Release. For each in-scope work effort identified above, the EDW team will: • Create specifications required to acquire data into EDW core tables, and transform it into an integrated data mart. • Update the EDW shareable and MR2000 data mart logical and physical data models. • Capture EDW owned Teradata table elements on the EDW’s web-based metadata tool. • Build transformation programs on Teradata to load the required data elements into the daily and/ or monthly EDW revenue core, MR2000 detailed core, MR2000 summary core, and MR2000 summary data mart tables. • Utilize existing MR2000 technical architecture that supports the current EDW table and data naming standards. • Create EDW shareable core and MR2000 application views that enforce EDW and MR2000 data access security requirements. • Perform unit and system testing for all new daily and monthly core table loads and new/updated daily & monthly core to mart transformation programs. Out of Scope The EDW team will not: • Develop or maintain the SCORE reporting application including Business Objects, Alphablox, Essbase, and Navigator ABC components. • Acquire detailed revenue data for legal entities not in scope for SCORE Phase I/II (e.g. LD, SNET, , Prodigy, etc). (See in/out of scope legal entities in SCORE Requirements document) 408.656.2498
  5. 5. PACIFIC BELL PRISM Job Aid Page 5 of 8 Project Charter Project Assumptions • No additional Teradata lease space will be required for new revenue sources in scope for this initiative, as this data is covered under the MR2000 planned capacity growth to 6.5 terabytes. • All EDW development labor and non-labor costs will be charged to the MR2000 Management Accounting Project EAP code in Artemis/Evista. • Regular project team check-ins will be held with meet-me lines available since team members are located at different sites; team deliverables and timelines will be observed. • Any critical path deliverable jeopardy discovered will be escalated to IT and/or Finance leadership for resolution within 48 hours due to the short project timeframes. • All baselined key deliverables will be stored in the Panagon library. • Data reconciliation plans, and analysis of other Finance application revenue, expense or volumes differences, will be the responsibility of the Finance client. The EDW team will provide system test results from source to EDW target. • Change Management will be enforced upon implementation and user acceptance of each EDW deliverable. • Revenue and volumes data from prior months will not be reprocessed from the EDWcore to mart. Changes in assignment rules for state and any other MR2000 dimension will be processed on a going forward basis. Expense recasts may be performed as needed through the existing mart to mart recast processed. • New mechanized sources for revenue and volumes will begin collecting history from the month implemented going forward until reaching the 13 months in the EDW core tables, and 37 months in the summary mechanized mart. • No backouts of MR2000 detailed core and MR2000 summary data mart data will be permitted after monthly processing is final. • MR2000 dimensional mapping rules will be provided and maintained by the finance team. • Ongoing maintenance of all new and existing MR2000 cross-reference and hierarchy tables is performed by finance or existing data SMEs with support from the Finance ERS team. • EDW manual expense/revenue/volumes entry applications will be maintained by the Finance ERS application team. 408.656.2498
  6. 6. PACIFIC BELL PRISM Job Aid Page 6 of 8 Project Charter Current Issues None Risks Delays in delivery of MR2000 and/or FDW dependent subprojects could impact the completion of scope required for MAP by the 10/31/2003 date. At this time, the MR2000 Internet revenue and FDW Data Comm releases are complete. The FDW West Consolidation is on track for July release. The MR2000 AIT ASI and AIT Non-Switched Volumes efforts have not started but have assigned resources to start in July. AS400 and PBIS source system feeds are not likely to be provided until earliest September 2003 and December 2003 respectively due to resource constraints and existing priority project work for that source system. Jerry Healy, Exec Director and overall project manager of the MAP project, confirmed that the AS400 specific work effort is not material enough in revenue dollars to justify pulling in the date using contract resources, therefore is willing to accept that implementation after 10/31/2003 if necessary. He also agreed to the 1Q2004 delivery of PBIS data in order to get complete PBIS journal data. The alternative short term solution would have resulted in less complete and accurate journal data for PBIS. Related Projects Inter-Dependent Projects • MR2000 Release 4 Enhancements • AIT ASI Volumes • AIT Non-Switched Volumes • RC Hierarchy • FDW – Telco 11i conversion 408.656.2498
  7. 7. PACIFIC BELL PRISM Job Aid Page 7 of 8 Project Charter High-Level Project Plan below lists the major implementation milestones and expected completion dates. These dates should be used to evaluate the project’s progress. Any deviation in the achievement of these milestones will immediately be made known to management by the project management team. Deliverable Milestone Planned Production Milestone Date Add State Dimension to Add State to MR2000 Revenue Daily Detailed Core 08/13/2003 MR2000 Revenue, Expense, Volumes Mechanized Mart Add State_Cd to MR2000 Revenue Monthly Detailed 08/31/2003 Core Add State_Cd Default to Expense Mart 08/13/2003 Add State_Cd to MR2000 Volumes Monthly Detailed 08/31/2003 Core Add State_Cd to MR2000 Revenue Daily Mart 09/12/2003 Add State_Cd to MR2000 Revenue Monthly Mart 09/30/2003 RC Hierarchy Logic Update RC Hierarchy Logic per Beth Wiest Specifications 08/20/2003 Update Add AIT ASI Volumes to Add AIT core to MR2000 detailed core processing to 10/20/2003 mechanized volumes mart existing ASI Volumes Feed Add AIT Non-Switched Add new monthly AIT Non-Switched core to MR2000 12/30/2003? Volumes to mechanized detailed core table processing volumes mart Add Messaging to MR2000 Add SMSI CRIS monthly core to MR2000 detailed core / 09/30/2003 mechanized mart mechanized mart processing Add SMSI GL monthly core to MR2000 detailed core / 09/30/2003 mechanized mart processing Add PBIS Core table to EDW 12/31/2003? Add PBIS monthly core to MR2000 detailed core / 2/28/2004? mechanized mart processing Add PBIS GL monthly core to MR2000 detailed core / 2/28/2004? mechanized mart processing Add AS400 Core table to EDW 1/31/2004? Add PETS/AS400 monthly core to MR2000 detailed core / 3/31/2004? mechanized mart processing Project Milestones and Completion Dates Note: All milestone dates with question marks are not committed due to lack of baselined detailed requirements for that effort, and/or lack of resources & commitment dates from source systems outside of the EDW. They are not targeted nor expected for the October 31st release of the MAP reporting application. 408.656.2498
  8. 8. PACIFIC BELL PRISM Job Aid Page 8 of 8 Project Charter Project Cost Estimates (2003-2004) EDW resource hours and cost estimates for 2003-4 are included in the following T&C document: C:Documents and Settingsjs5312My DocumentsManagement AccountingGeneral Project InformationCost EstimatesMAP T&C Version 0-5.doc Note: Additional 15 gig (pre-fallback) estimated space required for reporting mart. New data sourcing for Messaging including in the scope for the initial 28 node purchase for MR2000 Phase I, therefore no additional capacity costs are included for this sourcing. For more information, please contact Orlando Moreno, PMP at 408.656.2498 or 408.656.2498