Enterprise Data Warehouse

Business Requirements Document

Current Version: 1.0

Owner: Daniel Wolday
Date Last Updated: 10/17/2008
Last Updated By:
Author:
Date Created:
Approved By:
Approval Date:
 Revision History

Version Date Updated Revision Author Brief Description of Changes

Number
1.0 10/17/2008 Daniel Wolday Initial Creation

Enterprise Data Warehouse Business Requirements Document (BRD)

SDP-21 Template Version 1.7 (R10) Page 2 of 11
 Table of Contents

1 INTRODUCTION.................................................................................................................... 4
1.1 USER PROBLEM/ PROJECT BACKGROUND.............................................................4
1.2 SYSTEM SCOPE...................................................................................................4
1.3 REFERENCES.......................................................................................................5
1.4 BUSINESS USERS OF THE SYSTEM........................................................................5
1.5 DEFINITIONS AND ACRONYMS...............................................................................6
2 TO-BE DETAILED PROCESS MODEL.................................................................................6
3 BUSINESS REQUIREMENTS (FEATURES OF TO-BE PROCESS DESIGN).....................8
3.1 ASSET DATA........................................................................................................8
3.2 LIABILITIES DATA..................................................................................................9
3.3 STOCKHOLDER EQUITIES DATA.............................................................................9
3.4 INTERCOMPANY TRANSACTION DATA....................................................................9
3.5 FOOTNOTES.......................................................................................................10
4 ASSUMPTIONS, CONSTRAINTS AND DEPENDENCIES.................................................10
4.1 REQUIREMENT ASSUMPTIONS.............................................................................10
4.2 Requirement Constraints and Dependencies.................................................10

Enterprise Data Warehouse Business Requirements Document (BRD)

SDP-21 Template Version 1.7 (R10) Page 3 of 11
1 Introduction
1.1 User Problem/ Project Background

General Motors Acceptance Corporation’s (GMAC) decentralized business model has created
multiple islands of information resulting in:
 Lack of robust business and customer insights at the enterprise level
 Inconsistent financial, risk, marketing and operational reporting
 Redundant data stores, resources and processes.

The purpose of the Enterprise Data Warehouse (EDW) is to create a single version of the truth for
reporting and business intelligence. EDW will provide:
 Improved key Business Metrics/Dashboard Reporting at segment and the GMAC
enterprise
 Enhanced capabilities for Financial Analysis & Planning, Risk Reporting & Analysis.
 Transition to an Integrated Marketing Model optimized across all products, channels and
marketing media

EDW will closely be aligned with initiatives underway in the key global function areas of Finance,
Marketing, Treasury and Risk to solve immediate data needs: Finance – Autobahn/Management
Reporting, Marketing – GEMA, and Treasury – QRM.

1.2 System Scope

EDW includes:
 Business requirements and corresponding data sources to support the four key global
functions: Finance, Marketing, Risk, and Treasury.
 Initial delivery will include summary data to support these four key global functions.
 Standardized business data definitions and data model
 Definition of master data sources and systems of record
 Consolidated analytical data stores where possible
 Standardized tool sets
 Deployment of analytics
 Established data governance organizations and processes
 Established internal, sustainable data warehousing expertise
 Monitor and integrate (as appropriate) existing data warehouse efforts throughout the
company.

The finance specific system scope is to:

• Leverage an enterprise-wide, global Chart of Accounts along with global and
common legal, management and organizational hierarchies
• Deliver enhanced capabilities for Financial Analysis & Planning (FP&A) and
hierarchical consolidation along multiple business dimensions
• Provide Key Business Metrics/Dashboard Reporting at both segment and GMAC
enterprise levels.

The scope of the first release of EDW is to load all financial and nonfinancial data contained in
the super table reporting to the EDW.

Enterprise Data Warehouse Business Requirements Document (BRD)

SDP-21 Template Version 1.7 (R10) Page 4 of 11
The Business Units included in release one are :
GMAC Consolidated
North American Automotive
International Automotive
Germany, Italy, UK, Brazil, Mexico
Auto Operations
GMAC Insurance
Commercial Finance Group
ResCap, Corporate
GMAC Consolidated (excluding ResCap).

1.3 References

Dcouments that served as inputs to the Business Requirement Documents:

• Project Charter
• Context Diagram
• Business Process Model
• Functional SMEs inputs, consolidated management reports, etc
• Workshops, interviews, questionnaires
• Workshop summary report
• Autobahn workshop report notes and PowerPoint presentation
• Super tables

1.4 Business Users of the System

EDW is to enable corporate level decision making with easy and one stop access to timely and
consistent indicators of the business. The first release(s) of the program is to build some of the
foundational capabilities, and thus will not provide end-user access. The program will broaden the
data content and capabilities over time.

However, eventually EDW is expected to serve the following business user groups:

Business Location Subject Matter Technical Preferred Background Other

User Role / Knowledge Knowledge Environment Observation if
User Group any

Enterprise Data Warehouse Business Requirements Document (BRD)

SDP-21 Template Version 1.7 (R10) Page 5 of 11
Management GMAC Understands high Basic MS Laptop, Handheld Focused attention
Users Head Office level dashboards Applications and device with on all GMAC BU
(manage the (Detroit) and how they web Browsers automatic metrics driving
business) apply to the dashboards and costs and profits.
company wide reports distributed Want to see
performance and via email. health of the
profitability. overall business.
Standard reports
would be
sufficient.

Support Various Comprehends MS Applications Laptop/ Will focus

(people world-wide detailed and web Browsers workstation, can particular attention
supporting locations dashboards, retrieve necessary on the metrics
executives) KPIs, and reports with provided around
standard BU minimal training/ their respective
reports Instruction BU.
Analytical Various Understand Basic MS Workstation with See specific
users world-wide detailed reports Applications, access to reports to
(understands locations specific to their Internet Browsers application to run measure success
the business) BU. reports; of a business
dashboards also initiative; apply
delivered. analysis to future
business
initiatives;
Reporting for
budgeting
process.

1.5 Definitions and Acronyms

Refer to Glossary (Appendix A).

2 To-Be Detailed Process Model

Currently information systems which have been developed to support GMAC’s business have
been developed for one vertical slice of the business (e.g., for a particular organization/business
unit or line of business), creating information silos that are fragmented, incomplete, and not
available when and where needed. Business operations lacked needed information, or exist on a
patchwork of information from multiple systems to get the job done. As a result of these practices,
internal reporting systems are expensive, incomplete and deliver inaccurate pictures of business
results. In addition, these unique solution systems create the impossibility of maintaining
integrity, accuracy, and concurrency of corporate information.

This Enterprise Data Warehouse process addresses this current information “silo” environment at
GMAC by providing the following:

1. Gold standard definitions for enterprise master data, sourced from internal and external
resources
2. Management of enterprise master data in a centralized data warehouse infrastructure
3. Access by authorized users and systems of enterprise master data across GMAC
4. Management of meta data about systems of record (Gold Sources,) for enterprise master
data
5. A data architecture and business rule enforcement process that ensures the data
accuracy, quality and consistency of enterprise master data

Enterprise Data Warehouse Business Requirements Document (BRD)

SDP-21 Template Version 1.7 (R10) Page 6 of 11
 6. A data governance organization and process that ensures continued accuracy, and use
of enterprise data standards

The vision of EDW is illustrated in the following diagram.

The first release of EDW provides a data foundation to build upon in subsequent releases for
Finance, Marketing and Risk. EDW will not replace any of the existing reporting or warehouse
solutions. The business-unit specific solution will be maintained and continue to evolve as needed
by the business unit for operational and BU-specific reporting. The business unit solutions will be
aligned with the EDW solution with common data definitions and ultimately a consistent
architecture with the intent to minimize on-going infrastructure costs.

[Going to insert a paragraph that will explain the diagram below – Workshop summary notes]
Currerntly SAP BI is the BU specific solution for the finance function of GMAC which.

Enterprise Data Warehouse Business Requirements Document (BRD)

SDP-21 Template Version 1.7 (R10) Page 7 of 11
 Excel or Flat Files End User
Financial Actual Data Access
Data Data Marts
Financial Forecast Data
Warehouse  Reports
 Analysis
 Modeling
Autobah Enterprise Finance
Autobahn Data 1
n ETL Data
SAP ETL
Stagin Cognos
SAP g
Warehouse
(ECCS) Area
BI
Summary – Count Finance
Information Detail Information – 2
(totals by segment) Reconciled
Actual, Forecast, Plan (totals by segment)
Actual, Forecast, Plan

Excel or System Files

Statistical Actual Data
Statistical Forecast Data

Multiple Data Sources

3 Business Requirements (Features of To-Be Process Design)

3.1 Asset Data

Requirement ID BR 144655 Priority Essential
Status New
Description The System shall capture all the detailed asset data (Earning
Asset Data, Cash and other assets) in US dollars excluding any
intercompany earning assets across all Business Units in scope.

Earning asset data includes:

 Consumer
 Commercial loans
 Operating leases
 Loans held for sale
 Cash Equivalents
 Marketable securities
 Restricted Cash
 Insurance Investment Portofolio
 Investment securities – Other
 Notes Receivable from GM
 Real Estate and Other Assets
In US dollars (USD) for all business units in scope (refer to
System Scope section for a list of all BUs that are in scope for

Enterprise Data Warehouse Business Requirements Document (BRD)

SDP-21 Template Version 1.7 (R10) Page 8 of 11
 R1).
Rationale /
Dependencies
Source

3.2 Liabilities Data

Requirement ID BR 144657 Priority Essential
Status New
Description The system shall capture all liabilities data (interest-earning
liabilities and other liabilities data) excluding intercompany
transactions in USD across all Business Unites in scope.

Interest earning liabilities includes:

 Short term Debt
 Unsecured long term debt
 Secured long term debt
 Customer deposits
 Wholesale deposits
Rationale /
Dependencies
Source

3.3 Stockholder Equities Data

Requirement ID BR 144657 Priority Essential

Status New
Description The system shall capture all stockholders’ equity data in USD for
all Business Unites in scope.
Rationale /
Dependencies
Source The source document is the Supertable

3.4 Intercompany Transaction Data

Requirement ID BR 144657 Priority Essential
Status New
Description The System shall capture all intercompany transaction data in
USD across all BU in scope.

Intercompany transaction data includes:

 Intercompany Receivables
 Intercompany Debt
Rationale /
Dependencies
Source

Enterprise Data Warehouse Business Requirements Document (BRD)

SDP-21 Template Version 1.7 (R10) Page 9 of 11
3.5 Footnotes
Requirement ID BR 144657 Priority Essential
Status New
Description The System shall capture all variance explanation across all
business units in scope.
Rationale /
Dependencies
Source

4 Assumptions, Constraints and Dependencies

4.1 Requirement Assumptions

ID Description
The initial release will include the following business units: GMAC Consolidated, Auto
Operations (North America Automotive and International Automotive), Germany,Italy,
Review
UK, Brazil, Mexico, GMAC Insurance, Commercial Finance Group, ResCap, and
Corporate.
The initial Scope of delivery will include only the summary data.
The EDW will not replace Business Unit specific operational and managerial reporting.
Review No Reporting requirements will exist in EDW Finance Release 1.
Data will be refreshed daily.
EDW will capture 5 years of data going forward.
Review EDW Finance Release 1 should be considered a building block for Release 2.
Subsequent releases for finance solution will include management reporting of
financial and non-financial data to support corporate level reporting requirements.
Business unit specific reporting requirements are out of scope.
Project Autobahn will deliver a single, global chart of accounts that will be the basis for
financial reporting across the organization. The initial solution is at the consolidated
level which will require less detail available in the reporting solution until a full CoA is
deployed.
Project Autobahn will deliver a single general ledger. The understanding is that this
will be over the next several years and EDW will provide a solution for some reporting
in the interim.
The scope of the EDW will not deliver operational reports for applications.
EDW will not deliver reports specific to each business unit when the global reports will
not meet regulatory or legal requirements. It will not localize reporting solutions when
there are country specific reporting requirements, legal or regulatory, not met by either
the global or segment solutions.

4.2 Requirement Constraints and Dependencies

ID Name Description
CONSTR 144663 Dependency Project Autobahn definition of single, global chart of
accounts.

Enterprise Data Warehouse Business Requirements Document (BRD)

SDP-21 Template Version 1.7 (R10) Page 10 of 11
CONSTR 145260 Dependency Project Autobahn definition of legal, managerial, and
product hierarchies
Dependency Project Autobahn deployment timeline is maintained

Enterprise Data Warehouse Business Requirements Document (BRD)

SDP-21 Template Version 1.7 (R10) Page 11 of 11