EDW Source-to-Core Context
ETL Processes Core Tables
NEMO will use current EDW processes and Existing core tables will remain in tact.
tables for data that is already in place. Affiliate tables will be created as needed.
The NEMO estimates do not care for the Daily billing data processes for the Midwest
modification of existing processes and tables. region are not included in the NEMO estimates.
Informatica is being positioned as the ETL tool Timing requirements may dictate the need for
Telco West for new data sources. daily Midwest region data.
Historical data will be extended where
necessary to accommodate the 13 month history
Telco East requirements for NEMO.
Telco Southwest Custom er
Telco Midwest ETL Billing
Cingular Revenue Expense
Long Distance SBC IS
Data Comm Com m
Yellow Dem o-
3rd Party Data
EDW Core-to-Integrated Context
Order Aggregate & Integrate
EOM CIM and SDR keys assigned to all account level data
Geog Journal Revenue will be assigned to NPC based on
Journal Journal Cust Prof In-service product counts, Movement and Derived
Revenue Expense Revenue will be mapped to Regional Product Codes Product
based on existing processes (i.e. PRG, PI, etc. must
be mapped to NPC) and then further mapped to NPC
Affiliate products must be included in NPC mapping
NPC level will be the lowest level of product counts
Cingular LD Dim z available in the Integrated Layer (TBD)
Calculation of location level attributes must be
Data defined (i.e. Dominant Account per location)
Com m Business defined mapping rules across all regions Events
Hier-A and affiliates are needed for each data dimension
Hier-B Business supplied hierarchy definitions are needed
for each dimension requiring aggregation drilldown
Hier-C Others ...
Yellow Dem o- or drillup capabilities
Core Tables Tables Tables