Executive Summary


Published on

This constitutes a sample of an Executive Summary done for a project I speared as leader in SBC

1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Use GigaMAN as a sample guide for the key information Identify if this project is a productivity enhancement, regulatory mandate or infrastructure initiative (Classification should be accurate to avoid delays in review/authorization) Should be simple enough that a non-SBC employee can understand it Include alternative solutions considered and major risks and concerns What is the justification for this project? Time savings? Force reductions? Materials savings? Regulatory mandate (penalty avoidance)? Improved network reliability / infrastructure?
  • Executive Summary

    1. 1. Project Manager: Orlando Moreno Phone Number: 408 – 365 -8589 SBC Communications, Inc. Executive Summary: iNtegrated Enterprise Marketing Opportunities (NEMO) Business Case Type of Project: Productivity Enhancement / Infrastructure Date: August 29, 2003
    2. 2. Project Description <ul><li>Provide consistent reporting and support “self-service” of reporting needs </li></ul><ul><ul><li>Data mapped to MR2000 for common financial reporting </li></ul></ul><ul><ul><li>Enhance usability </li></ul></ul><ul><ul><li>Publish standard reports </li></ul></ul><ul><ul><li>Develop a marketing dashboard and scorecard </li></ul></ul><ul><ul><li>Support self-service </li></ul></ul><ul><ul><li>Enhanced performance tracking </li></ul></ul><ul><li>Enable an integrated view of customer data to derive insight across all telecom and related product sets </li></ul><ul><ul><li>Single customer identifier across all affiliates </li></ul></ul><ul><ul><li>Consolidated data from multiple sources for more precise segmentation </li></ul></ul><ul><ul><li>Improved intelligence for predictive segmentation </li></ul></ul><ul><ul><li>Simplify ability to pull business intelligence and formulate market strategies </li></ul></ul><ul><li>Support ability to rapidly plan, execute and analyze campaigns with greater precision </li></ul><ul><ul><li>Enhanced product bundling capabilities </li></ul></ul><ul><ul><li>Improved lead list creation and optimization for more precise targeting </li></ul></ul><ul><ul><li>Increased number of campaigns </li></ul></ul><ul><ul><li>Integrated customer contact history </li></ul></ul>Understand Customer Needs and Define Attractive Customer Segments Define Product Offerings/ Bundles Identify Optimal Channels Track Campaign Effectiveness / Profitability Develop and Execute Campaigns Marketing Requirements Solution Need Executive Summary SBC’s ability to quickly identify and target attractive customers is currently impaired by the complex data environment, lack of common business definitions and time intensive process to generate reports. Addressing these issues requires both a process and technology change that automates and simples information retrieval and analysis for marketing decision makers.
    3. 3. Proposed Solution Project NEMO (iNtegrated Enterprise Marketing Opportunities) is the technology solution envisioned to support the delivery of business intelligence reporting. NEMO redefines the current data structures, analytical capabilities, and user interfaces to enable more precise customer targeting, segmentation, and product positioning. <ul><li>NEMO Solution Components </li></ul><ul><li>End Users : An integrated customer view will be a useful analysis tool for Marketing and other SBC users, including Sales, Billing and Finance </li></ul><ul><li>Information Delivery. Creates intuitive application interfaces to enable standard reporting and self service capabilities for marketing end users </li></ul><ul><li>Data Architecture. Develop a data structure that will establish common customer keys across all SBC entities and define consistent hierarchies for products </li></ul><ul><li>Data Infrastructure. Establish a standard data infrastructure across all regions and affiliates to ensure data consistency in reporting and analysis </li></ul>POP Leadership Business & Consumer Portfolio Mgmt Customer Insight Corporate Planning Channel Delivery Experience Delivery NEMO END USERS Standard Reports Dashboard & Scorecard Self-Service Report Query Cingular ASI SBCIS LD Data Comm EchoStar Yellow Pages SBC Telco – East SBC Telco – Midwest SBC Telco – Southwest SBC Telco – West Telecom ABI Claritas D&B TNS Revenue Expense Billing Completed Orders Issued Orders Product Volume Product Availability Contact History INFORMATION DELIVERY Data Modeling Data Aggregation Source to Core Core to Mart Customer & Product Hierarchy Business Rules & Logic DATA ARCHITECTURE DATA INFRASTRUCTURE Executive Summary
    4. 4. NEMO Scope NEMO scope was defined by marketing leaders from both the business and consumer segments. To minimize system costs, requirements were limited to those that directly support marketing decisions. These requirements were then linked to business decisions and prioritized to specific releases based on business priority, technical complexity and ability to impact revenue. Executive Summary Release 1 Objectives (12 Months) Release 2 Objectives (12 Months) Release 3 Objectives (9 Months) <ul><li>Introduce affiliate data and define a single customer identifier across all SBC affiliates </li></ul><ul><ul><li>Affiliate data source: Cingular, ASI, SBCIS, DataComm, LD, EchoStar, Telco, Yellow Pages </li></ul></ul><ul><ul><li>Data dimensions: segmentation, billing, geography, contact, telco billed orders (ASI & Telco), MR2000 Revenues, ABI, Caritas </li></ul></ul><ul><li>Establish consistent product and customer definitions and hierarchies </li></ul><ul><li>Support lead list creation & optimization </li></ul><ul><li>Create preliminary standard reporting capabilities </li></ul><ul><li>Map to MR2000 expense and product volume to gain reporting accuracy and enable improved customer profitability measures </li></ul><ul><li>Supplement single customer view by incorporating affiliate posted orders </li></ul><ul><ul><li>Cingular, SBCIS, DataComm, EchoStar and LD </li></ul></ul><ul><li>Enhance self service and reporting capabilities through desktop reporting tools that support customer querying and ad hoc report generation </li></ul><ul><li>Inclusion of SBC Telecom into single customer view </li></ul><ul><li>Distinguish between issued orders, and completed order status </li></ul><ul><li>Track customer contact history for all customer touch points </li></ul><ul><li>A single view of the customer allows marketing to optimize product portfolios, channel structures, and pricing for various customer segments </li></ul><ul><ul><li>Improved bundling campaigns create retention benefits </li></ul></ul><ul><ul><li>Optimizing product plans increase product ARPU </li></ul></ul><ul><li>Self service capabilities and standard reporting allow more rapid deployment of targeted campaigns </li></ul><ul><ul><li>More precise targeting improves campaign take rates and campaign frequency </li></ul></ul><ul><li>Ability to track customer contacts provides insight into the appropriate timing and channels for future sales contacts </li></ul>
    5. 5. Benefits Overview <ul><li>Qualitative Benefits </li></ul><ul><li>Aggregating data from numerous source systems and establishing consistent business rules enables greater self service and standard reporting capabilities, thereby </li></ul><ul><ul><li>reducing the long cycle times currently associated with complex data requests </li></ul></ul><ul><ul><li>Allowing marketing to redirect resources toward activities more directly linked to revenue generation </li></ul></ul><ul><li>Aggregating regional data and establishing common customer and product hierarchies will ensure presentation of consistent data between finance and marketing </li></ul><ul><li>Future marketing and network investment strategies require that SBC understand customer demographic and usage patterns specific to geographies / wire centers. NEMO provides the required customer and segment specific data to guide network and product deployment decisions </li></ul><ul><li>NEMO’s ability to provide an improved understanding of customer behavior (i.e. consumption patterns) allows development of more dynamic segmentation schemes and improved predictive modeling (i.e. what if scenarios) </li></ul><ul><li>NEMO provides the ability to rapidly generate a snap-shot view of critical performance metrics that can guide strategy or process refinements </li></ul>Customer Targets Consumer / Small Biz Enterprise / Global / GEM Data Enhancements Availability Consistency Precision Targeting Improved Positioning Bundling Channel Optimization Enhanced Self Service Standard Reporting Strategy Formulation and Execution Improved Segmentation Benefits quantified on following pages Performance Tracking Quantification of NEMO benefits focused on the aggregation of affiliate data to support improved campaign and retention efforts for consumers and small businesses. Benefits to the medium and large business segments have not been quantified. Executive Summary
    6. 6. Benefits Calculation Approach Take Rate: Improved campaign targeting and the ability to develop more tailored promotion offerings increases response rates and take rates and yields incremental subscribers. Customer Retention: Service providers who offer video, data, voice, or wireless bundles can reduce churn on all products. A single customer view across all affiliates will improve SBC’s ability to successfully target high value customer segments with churn reducing bundles. ARPU: Optimizing price plans to meet the needs of specific customers drives ARPU increases for usage based services (e.g. wireless and LD). Hit List Size: Specific customer intelligence will help generate more leads per campaign across all channels. Illustrative Illustrative Illustrative Illustrative X X X X X X X X = = X X X X = = X X X X X X X X = = = = X X = = X X Assumes that no benefits will be captured from inbound calls that can not be attributed to an executed campaign Benefits only applied to small business and consumer products Executive Summary Hit List Size Resp. Rate Take Rate Camp-aigns Margin Benefit Baseline 100K 7% 30% 4 $12 $101K NEMO 100K 8% 33% 4 $12 $126K $25K Hit List Size Resp. Rate Take Rate Camp-aigns Margin Benefit Baseline 100K 1.5% 30% 4 $10 18K NEMO 120K 1.5% 30% 4 $10 21.6K 3.6K Churn Subs Retained Subs Margin Benefits Baseline 49% 1M 51K $15 $76M NEMO 48.5% 1M 51.5K $15 $77M $1M Subs in Service ARPU Margin Benefit Baseline 1M $18 20% 3.6M NEMO 1M $18.5 20% 3.7M 100K
    7. 7. Summary of Quantitative Benefits <ul><li>To prevent double counting of benefits with the CCTP business case, no benefits were assumed for the inbound telemarketing channel </li></ul><ul><li>Business benefits are limited to the small businesses or the segment most effected by database marketing techniques </li></ul><ul><li>Quantitative benefits have been limited to those affected by improved targeting and offer development (positioning), thereby reducing the influence of exogenous market, regulatory, or competitive factors </li></ul>Benefits Breakdown by Product Benefits Breakdown by Benefit Category Executive Summary
    8. 8. Totals Cost Summary by Release One Time Implementation Costs Annual Recurring Maintenance Cost <ul><li>Assumptions </li></ul><ul><li>Hardware and software costs do not include costs associated with physical data center setup to house servers. This will be completed mid September </li></ul><ul><li>Hardware and software cost estimated at $3500/GB of storage and includes hardware, software capacity expansion for EDW environments </li></ul><ul><li>Maintenance costs associated with Teradata hardware and software (generally calculated at 15% of total hardware and software) will be absorbed within current Teradata maintenance contract. (assumes that system in deployed in St. Louis data center). </li></ul><ul><li>Hardware and software costs include: </li></ul><ul><ul><li>Hardware </li></ul></ul><ul><ul><ul><li>Servers (CPU) </li></ul></ul></ul><ul><ul><ul><li>Disk space </li></ul></ul></ul><ul><ul><ul><li>Redundant systems (backup) </li></ul></ul></ul><ul><ul><ul><li>Development and Production environment for the data storage and ETL logic environments </li></ul></ul></ul><ul><ul><li>Software </li></ul></ul><ul><ul><ul><li>Teradata database and DBA tools </li></ul></ul></ul><ul><ul><ul><li>Queryman (SQL / ad hoc query tool </li></ul></ul></ul><ul><li>Implementation costs are one time costs by release </li></ul><ul><li>All maintenance costs will take effect after the corresponding Release has been implemented and continue annually </li></ul>Executive Summary
    9. 9. SBC FM Cash Flow and Economic Summary Option 1- Fully Loaded Calculations assume discount rate of 9.5% *Capitalized 60% of development costs and 100% of hardware and software RTU cost Executive Summary SBC_FM Version 4.0
    10. 10. SBC FM Income Statement Option 1 – Fully Loaded Executive Summary SBC_FM Version 4.0
    11. 11. Alternative Solutions Considered Three additional alternatives to the full NEMO solution were considered. These alternatives would enable SBC and the marketing organization to achieve NEMO benefits associated without the full cost of implementation. * SBC FM Statistics * Executive Summary
    12. 12. Pre - Release (09/03 – 12/03) Plan (9/03 – 12/04) Analysis (9/03 – 12/04) Release 1 (1/04 – 12/04) Analysis (1/04 – 3/04) Design (1/04 – 7/04) Build (4/04 – 10/04) Test (9/04 – 11/04) Deploy (12/04) NEMO Timeline 9 10 11 12 1 2 3 4 5 6 7 8 9 10 11 12 1 2 3 4 5 6 7 8 9 10 11 12 1 2 3 8 Weeks 16 Weeks 12 Weeks 28 Weeks 28 Weeks 12 Weeks 4 Wks Release 2 (05/04 – 9/05) Analysis (5/04 – 9/04) Design (9/04 – 2/05) Build (12/04 – 6/05) Test (6/05 – 8/05) Deploy (9/05) 20 Weeks 24 Weeks 28 Weeks 12 Weeks Release 3 (02/05 – 3/06) Analysis (2/05 – 7/05) Design (5/05 – 10/05) Build (8/05 – 12/05) Test (12/05 – 2/06) Deploy (3/06) 24 Weeks 24 Weeks 20 Weeks 12 Weeks 2003 2004 2005 2006 NEMO The timeframe outlined for NEMO mandates coordination between marketing, sales, finance, and IT to develop the NEMO solution. 4 Wks 4 Wks <ul><li>Common customer key </li></ul><ul><li>Affiliate & 3 rd party data sources </li></ul><ul><li>Data Dimensions: Segmentation, geography MR2000 revenue, billing, contact, telco billed orders (ASI and Telco) </li></ul><ul><li>Customer lead list creation & optimization </li></ul><ul><li>Standard marketing reports & dashboard </li></ul><ul><li>Affiliate posted orders </li></ul><ul><li>MR2000 expense </li></ul><ul><li>MR2000 product volume & availability </li></ul><ul><li>Reporting enhancement </li></ul><ul><li>SBC telecom </li></ul><ul><li>Issued service orders </li></ul><ul><li>Customer contact history </li></ul><ul><li>Enhanced standard reports </li></ul>Executive Summary <ul><li>Business case approval & socialization </li></ul><ul><li>Detailed functional requirements </li></ul><ul><li>Logical design for product definitions </li></ul>Scope Scope Scope Scope
    13. 13. Risk and Mitigation Strategies The risks identified for NEMO have the potential to affect delivery timeframes, total costs and release scope. To mitigate these risks, specific recommendations have been identified, and where possible, already executed. Executive Summary Ares Risk Mitigation Recommendation Project Complexity NEMO is a complex project that requires coordination across SBC functions for successful delivery <ul><li>NEMO timeframes were developed jointly between IT and the business to deliver business capability </li></ul><ul><li>A pre-release phase will start September 2003 for analysis and design activities </li></ul><ul><li>A NEMO PMO function will be established to control and monitor scope, delivery timeframes and costs </li></ul><ul><li>Separate development resources will be allocated for each release </li></ul>Delays with Linked Initiatives NEMO has dependencies with CIM, CCTP – CCHL and MR2000/SCORE initiatives <ul><li>NEMO project team has begun coordination with the CIM, CCTP and finance project team to align product delivery dates </li></ul><ul><li>Critical path activities, status and issues management will be centrally coordinate by a NEMO PMO function </li></ul>Product Hierarchy Product hierarchy definitions can not be aligned between finance and marketing <ul><li>The logical design approach and product mapping will be initiated in Release 1 </li></ul><ul><li>Close coordination will be scheduled between finance and marketing to re-use completed work and to work through design elements for both organizations </li></ul><ul><li>A joint business and technology SWAT team will be responsible for the product hierarchy definition </li></ul>User Adoption Users may not fully leverage NEMO reporting capabilities and continue with business as usual <ul><li>End user communications, training and operational support strategy will be developed to support the NEMO deployment </li></ul><ul><li>A business process review will be completed to identify all business changes with the introduction of NEMO </li></ul>Benefits Measure Quantifiable business benefits purely from NEMO may be difficult to measure <ul><li>Baseline metrics will be captured prior to NEMO and post deployment to assess NEMO benefits impact </li></ul><ul><li>Benefits measurement will be established as an on-going component of the PMO </li></ul>Total Cost of Ownership Total cost of ownership may be greater than planned <ul><li>Project costs have been jointly identified by IT and the business </li></ul><ul><li>Detailed estimating factors have been identified for all work components </li></ul><ul><li>NEMO PMO function will monitor, track and manage all program costs </li></ul>
    14. 14. Appendices SBC Communications, Inc.
    15. 15. <ul><li>LD </li></ul><ul><li>EchoStar </li></ul><ul><li>Telco </li></ul><ul><li>Yellow Pages </li></ul><ul><li>Geography </li></ul><ul><li>Contact </li></ul>Release Scope Summary Executive Summary Release 1 12 Months (1/04 – 12/04) Release 2 12 Months (09/04 – 9/05) Release 3 9 Months (5/05 – 3/06) <ul><li>Affiliate Data Source </li></ul><ul><ul><li>Cingular </li></ul></ul><ul><ul><li>ASI </li></ul></ul><ul><ul><li>SBCIS </li></ul></ul><ul><ul><li>DataComm </li></ul></ul><ul><li>3 rd Party Data Source </li></ul><ul><ul><li>ABI </li></ul></ul><ul><ul><li>Claritas </li></ul></ul><ul><li>Data Dimension </li></ul><ul><ul><li>Segmentation </li></ul></ul><ul><ul><li>Billing </li></ul></ul><ul><ul><li>Telco Billed Posted Order (ASI and Telco) </li></ul></ul><ul><ul><li>MR 2000 Revenues </li></ul></ul><ul><li>Common Customer Key </li></ul><ul><ul><li>Establish common customer keys at BTN Level and propagate to EDW </li></ul></ul><ul><li>Establish Consistent Product Definitions </li></ul><ul><ul><li>Establish consistent product hierarchy definitions through business rules, aggregation procedures and standardized architecture solutions for customer and product hierarchies </li></ul></ul><ul><li>Customer Lead List Optimization </li></ul><ul><ul><li>Ability to reserve customers for specific lists </li></ul></ul><ul><li>CONTACT Source Migration </li></ul><ul><ul><li>Migrate CONTACT source to NEMO data </li></ul></ul><ul><li>Reports </li></ul><ul><ul><li>Standard Reports </li></ul></ul><ul><ul><li>Marketing Scorecard and Dashboard </li></ul></ul><ul><li>Affiliate Data Source </li></ul><ul><ul><li>None </li></ul></ul><ul><li>Data Dimension </li></ul><ul><ul><li>Affiliate Posted Orders . Integrate Posted Order information across affiliates not included in Release 1 (Cingular, SBCIS, DataComm, EchoStar and LD) </li></ul></ul><ul><ul><li>MR2000 Expense . Develop customer profitability through inclusion of MR2000 expense data driven to the customer level </li></ul></ul><ul><ul><li>MR2000 Product Volume and Availability . Deliver consistent product volume counts and product availability with MR2000 for SBCIS, LD, DataComm, EchoStar, Yellow Pages and Telco East Region </li></ul></ul><ul><li>Reports </li></ul><ul><ul><li>Self Service Reporting Capabilities . Enhance eBIP and desktop reporting tools to support customer querying capability and self service ad hoc report generation </li></ul></ul><ul><ul><li>Enhanced Standard Reports . Enhance standard reports to reflect product volume information. Introduce additional standard reports such as the exception based reports </li></ul></ul><ul><li>Affiliate Data Source </li></ul><ul><ul><li>SBC Telecom (SBCT) </li></ul></ul><ul><li>Data Dimension </li></ul><ul><ul><li>Issued (Issued & Complete) Service Orders Information . Provide issued service order information for orders taken and order provisioned. Issued service order information will be supported for all Cingular, ASI, SBCIS, DataComm, LD, EchoStar, Telco and SBCT </li></ul></ul><ul><ul><li>SBCT. Source and integrate other SBCT related data for billing, posted orders, MR2000 revenue, MR2000 product volume and MR2000 product availability </li></ul></ul><ul><li>Common Customer Key </li></ul><ul><ul><li>Establish common customer keys for SBCT </li></ul></ul><ul><li>Customer Contact History </li></ul><ul><ul><li>Customer contact history information for contact center, web, outbound tele-marketing and direct mail will be integrated </li></ul></ul><ul><li>Reports </li></ul><ul><ul><li>Enhanced Standard Reports . Enhance standard reports to reflect issued service orders information and customer contact history information </li></ul></ul>
    16. 16. Program Management Office (PMO) Sales Karen Mrachek ECM MR 2000 Revenue & Expense Order SCORE SMS Michael Moore CIS Linda Fuechtman EDW David Browne Requirements Testing Training Deployment POP Portfolio Mgmt Customer Insight CA&R IT Business CCTP MR2000 Billing CONTACT Athena CIM SDR ERS Renee Ramano Channel Delivery Finance Jerry Healy CA&R Chris Urbanek Release 1 of NEMO is scheduled for a 12 month delivery with a cost of over $35M and 140+ resources dedicated from IT and CA&R. Given the release complexity, timing and number of resources engaged, a tightly structured NEMO PMO is required to control and deliver the project on time and on budget Revenue & Expense Linkages Delivery Product Volume & Availability Contact Center History Log <ul><li>Progress Management </li></ul><ul><ul><li>Project Plan </li></ul></ul><ul><ul><li>Issue Management </li></ul></ul><ul><ul><li>Budget Management </li></ul></ul><ul><ul><li>Scope management </li></ul></ul><ul><li>Communications </li></ul><ul><ul><li>Status Reporting </li></ul></ul><ul><ul><li>Communication </li></ul></ul><ul><ul><li>Process Impact Review </li></ul></ul><ul><ul><li>User Adoption </li></ul></ul><ul><li>Quality Assurance </li></ul><ul><ul><li>Performance Reporting </li></ul></ul><ul><ul><li>Budget Management </li></ul></ul><ul><ul><li>Risk Management </li></ul></ul><ul><ul><li>Benefits Measurement Strategy </li></ul></ul><ul><li>Linkages </li></ul><ul><ul><li>Scope </li></ul></ul><ul><ul><li>Timing </li></ul></ul><ul><ul><li>Deliverables </li></ul></ul><ul><ul><li>Key Business Decisions </li></ul></ul>NEMO PMO Build Components Areas Activities Sponsor Users Executive Summary
    17. 17. Yearly Cost Summary Highlights Totals Development Costs (FTE) $37M Total Hardware Costs $33M Total Software Costs $17M Total One Time $87M Total Maintenance Costs (FTE) $43M Total Hardware Maintenance $2M Total Software Maintenance $5M Total Maintenance through 2009 $50M Executive Summary
    18. 18. Benefits Summary By Region NEMO Benefit Breakdown by Category Executive Summary Take Rate 4% Retention 85% ARPU 5% Volume 6%
    19. 19. Benefits Tracking Approach Hit List Size Response Rate Take Rate # of Campaigns Churn Rate % ARPU To track NEMO-related benefits, business case assumptions will be compared against the actual benefits observed during the initial stages of the implementation. Variables to Track Tracking Process This approach assumes no incremental overlap with the benefits to be derived from the CCTP project. Benefits measured on traceable campaign statistics only, not on sales associated with inbound calls that can not be attributed to a campaign. Executive Summary Baseline Control Group Create a control group by re-baselining current SBC Actuals for these variables at the end of FY04. These baseline figures will be used as a basis of comparison for tracking NEMO Revenue benefits. NEMO Control Group NEMO-forecasted variables (from the business case) should be used as another basis of comparison to track the actual benefits of NEMO. If needed, NEMO-forecasted variables should be adjusted relative to the re-baselining of SBC Actuals at the end of FY04. Actuals: FY05-FY09 Beginning at the end of Q1 of FY05, actual SBC values for these variables should be captured on a quarterly, semi-annual, and annual basis. These values should be compared against both the Baseline Control Group and NEMO Control Group to assess the measurable impact of NEMO. Actuals: FY05-FY09 Beginning at the end of Q1 of FY05, actual SBC values for these variables should be captured on a quarterly, semi-annual, and annual basis. These values should be compared against both the Baseline Control Group and NEMO Control Group to assess the measurable impact of NEMO.
    20. 20. Technology Assessment ` <ul><li>Extension of analytical reporting and eBIP (e Business Intelligence Portal) environments </li></ul><ul><li>Creation of OLAP and balanced score-card environments </li></ul><ul><li>Integration of data structure and reporting tools with existing and future analytics software tools </li></ul>Technical development of NEMO will focus on data infrastructure, integration and information delivery. Component processes of the technical solution include: Information Delivery Data Architecture <ul><li>SDR (Strategic Data Repository) customer matching processes will be extended to accommodate all affiliate and telco data sources </li></ul><ul><li>Data extract processes to retrieve incremental affiliate and partner data </li></ul><ul><li>Migration of Enterprise Campaign Management (ECM) application functionality to access the integrated EDW data stores </li></ul><ul><li>Extraction, transformation and loading of the legacy system information to the EDW environment </li></ul><ul><li>Business rule cross-reference tables and processes will be used to integrate data from multiple affiliates into common customer and product family hierarchies </li></ul><ul><li>Aggregation and integration of detailed legacy system data (stored in the EDW) </li></ul><ul><li>Extension of existing CIM processes to develop single view of customer spend across all SBC affiliates </li></ul><ul><li>Posting of reporting information to a Unix-based reporting application server layer </li></ul>Data Infrastructure CABS ABI CPNI CRIS LD Telegence BPP CCA EM UPS MP CAMPS HB ACIS Revenue ASI Cingular SNET PAC AIT SWBT Product Customer Affiliate Orders DataComm EchoStar LD SBCIS Yellow Pages Extraction Processes Business Portal, Scheduling, email, Filtering, OLAP Consumer Executive Summary NEMO Analytical Reporting Structure Advanced Analytics Discovery and Data Mining Performance Management i.e., SBC Table Driven Aggregation & Integration