What
is a Data Environment?
What industries are supported?
What is a 'data model'?
What is the Enterprise Data Model?
What is the Data Warehouse Model?
What are Business Area Models?
How are the data models integrated?
Who can take advantage of data models?
How can you design a 'template' data model for an industry?
How long would it take me to develop similar models?
What services does ADRM provide?
*
* *
What
is a Data Environment?
A Data Environment is a suite of integrated data models
specifically designed to support business organizations in a specific industry.
> Enterprise Models
> Business Area Models
> Data Warehouse Models
> Data Mart Models
Each data model is:
> Developed specifically for the associated industry
> Complete, industry-specific definitions and terms
> Single-page, large-format, plotted diagram (36""x175")
> Developed using a popular CASE tool
*
* *
What
industries are supported?
The following industries have associated Data Environment products.
Communications and Media
> Cable Services
> Internet and Data Services
> LEC and Long Distance
> Wireless
> 3G Wireless
Financial Services
> Brokerage
> Commercial Banking
> Corporate & Investment Banking
> Credit & Payment Card Services
> Credit Union
> Mutual Funds & Fund Management
> Mortgage Services
> Retail Banking
High Tech Products
> Computers
> Medical Systems
> High Tech Components
> Networking Equipment
> Semiconductor
> Software
Insurance
> Life Insurance
> Healthcare Insurance
> Property & Casualty Insurance
Manufactured Products
> Agricultural Chemicals
> Automobile Manufacturing
> Aviation Products
> Consumer Packaged Goods
> Durable Medical Equipment
> Industrial Chemical
> Luxury Goods
> Pharmaceutical
Retail
> Grocery
> Retail Products
> Food Services
Transportation and Hospitality
> Airline Industry
> Freight & Logistics
> Gaming Services
> National Postal Services
> Parcel and Mail Delivery
Utilities
> Water Utility
> Gas & Electric Utility
*
* *
What
is a data model?
A data model is a graphic representation of the data within a specific area
of interest.
A data model is the standard and accepted way of analyzing data, designing
and implementing databases.
Data
models are developed using CASE tools. CASE tools provides the supporting
software for development of the model including the graphics, data dictionary,
links to other tools and supporting utilities.
That area of interest may be as broad as all the integrated data requirements
of a complete business organization ("enterprise data model") or
as focused as a single business area or application ("subject area data
models").
Frequently a data model represents a business functional area (CUSTOMER, MARKETING,
SALES, MANUFACTURING) or a business area that is to be analyzed or automated
(LEAD TRACKING, PROBLEM REPORTING, WARRANTIES).
A good data model depicts or describes the following:
> Entities (tables)
> Attributes (columns)
> Relationships
> Data cardinality
> Business rules
> Complete definitions of entities and attributes
> Primary, secondary and alternate keys
> Large-format, clear graphics
The goal of the data model is to clearly convey the meaning of data, the relationships amongst data, the attributes of the data and record the precise definitions of data.
The data model for a business organization tends not to change greatly over time unless the business changes the fundamental way that it does business or enters into a new line of business. However, the way that data is used, the processes, can vary greatly even between organizations functioning in the same industry.
The data
required by organizations within the same industry tend to be very similar.
This is why we can assume that data models have basic stability within
the organization while process models are relatively unstable. This
commonality of functional data is the basic tenant that allows 'template'
data models for an industry to be applied by organizations operating in that
industry.
*
* *
What
is an Enterprise Data Model?
The Enterprise Model incorporates the integrated data requirements of a best-of-breed organization in that industry within a single model consisting of approximately 400 entities and 2,500 attributes.
It is the essential data model for strategic planning, communicating information requirements across the organization, developing integrated systems and organizing data in the Business Area, Data Warehouse and Data Mart models.
Each Enterprise Model is built upon a common core of entity 'building blocks', which contributes those same common entities for construction of business area, data warehouse, data and application models. This common set of core entities enables the related models to be data architected to be consistent and extendable. The same common core of entities are used wherever applicable in other industries, thus providing a means of integrating data across different industries or lines of business.
ADRM Enterprise Models have several common design characteristics:
> Industry-specific design
> Comprehensive subject area coverage
> Fully-attributed
> Complete and detailed definitions
> Semantically clear and easy-to-understand
> Reflects current industry data practices
> Flexible and extendable design
> Utilizes industry-standard data whenever possible
> Large format graphic representation
> Supports a wide audience of interests
> Integrated with Business Area, DW and Data Mart Models
Enterprise
Models are physically presented as a 36"x250" single-page, multicolor,
plotted diagram.
The Enterprise Data Model is fully-attributes in 3NF form with complete definitions
and documentation.
*
* *
What
is the Data Warehouse Model?
The data warehouse is the central
repository for corporation information representing the integrated data requirements
of the enterprise and designed to support the analysis, DSS and reporting
requirements of the entire organization.
It has characteristics unique to its function:
> Based upon a comprehensive enterprise model
> Provides integrated data to the organization
> Serves a broad user community
> Contains cleaned, consistent data
> Data is at granular level of detail
> Significant or often-used data is summarized
> Contains time-based "historical" data
> Driven by analytic requirements
> Structured by aligned business areas
> Addresses evolving information needs
> Is not updated
> Contains summary data
The Data Warehouse Model for each industry describes the target data structures and their data relationships in support of the enterprise-wide information requirements of a typical organization operating within that industry.
Each industry-specific Data Warehouse Model is derived directly from the same-industry Enterprise Data Model.
The Enterprise
Data Model logical data structures are the foundation for development of corresponding
data warehouse data structures.
*
* *
What
are Business Area Models?
Business Area
Models describe functional business or subject areas found in many industries
or developed for a specific industry.
Each Business Area Model is constructed from a common set of entities from
the corresponding industry Enterprise Model, which insures that Business Area
Models will have common keys, attributes and definitions throughout the data
architecture.
Business Area Models expand upon the 'thumbnail' of business area data represented
in the industry Enterprise Model and provide complete coverage for that subject.
Business Area Models contain the greatest level of detail and provide the
lowest level of data granularity in the ADRM model hierarchy - while maintaining
definitions consistent across the entire model suite.
Business Area Models provide a data architecture for business analysis and planning, applications design and development of data marts and the data warehouse.
This approach enables the organization to design top-down and propagate changes and new requirements consistently between models. As new information is added to a Business Area Model it can also be propagated to the Enterprise Model, Data Warehouse Model, Data Mart Model or application models.
Business Area
Models are used in conjunction with the Enterprise Model to develop star schema
data mart models. Having both the Enterprise Model and Business Area Models
for reference facilitates consistent dimension design and a resulting data
architecture that implementing conforming dimensions.
Business Area data models have the same components as Enterprise and
Data Warehouse models:
> Single-page, color, plotted diagrams
> Detailed dictionaries
> Complete definitions
> Defined domains
> CASE software
The following are current Business Area models:
Accounting & Financial Reporting
Advertising
Bookings/Billings/Backlog
Budget
Business Metrics
Channel
Contract
Customer Service
Geography
Human Resources
Individual Customer
Individual Customer Credit & Collections
Inventory
Legal Entity Customer
Legal Entity Customer Credit & Collections
Marketing
MFG/Shop Floor Control
Order
Party
Product
Property & Equipment
Purchasing
Training & Education
*
* *
How
are the data models integrated?
Each model is derived from the Enterprise Data Model for that industry. This
supports the integration of data across each level of models.
The Enterprise Data Model becomes the source for creating new functional Subject
Area models and extending the Data Warehouse Model.
New data,
identified during business area development, that is considered to be of sufficient
importance can be propagated up to the Enterprise Data Model.
This enhances the Enterprise Data Model and reflects new information learned
about the enterprise during detailed business area analysis.
Similarly, the same analysis can contribute significant new data structures to the Data Warehouse Model and other Subject Area data models.
CASE tools support the integration of data between models via utilities, subschemas and the central dictionary.
*
* *
Who
can take advantage of data models?
Almost everyone within the organization.
> PLANNERS
Now have a graphical and dictionary-based model that they can use to develop new systems and integrate existing systems. Data models are valuable for determining the suitability of software packages and their application across an entire organization. Data models also have components that are ideal for recording information about projects, applications, events and costs. Data models can serve as vehicle for conveying this information across organizations and providing a source of continuity.
> SENIOR EXECUTIVES
Use data
models to understand the integrated information responsibilities of the functional
organizations within their command. Data models are powerful vehicles for
communicating ideas and strategic plans.
> MANAGERS
Have
a tools for defining projects, assigning tasks, determining resources and
prioritizing activities. Data models are also an excellent way for managers
to describe their business responsibilities to others in terms of plans, objectives
and goals.
> SOFTWARE DEVELOPERS
Use data models as the foundation for their designs. Training personnel use data models to train and familiarize staff with the organization at large.
*
* *
How
can you design a 'template' data model for an industry?
Organizations within the same industry tend to perform the same basic functions,
which require similar data. The processes that work upon the data can vary
dramatically. However, the data, which is the foundation for current and future
analysis and development, tends to remain stable unless the organization enters
a new line of business ('a new industry').
This makes it possible to create detailed, sophisticated 'template' data models that can be edited, extended and customized to meet organization-specific requirements. This ability to edit, extend, customize and integrate each level of data model to meet the needs of a specific business organization is the key to the use of template data models.
ADRM template data models make it is easy to work with each level of data models independently. This supports work-group development and facilitates rapid development of the data models as knowledge of each subject area is gathered.
It's also true that almost every company requires a core of similar functional components: Customers, Markets, Market Segments, Orders, Inventory, Pricing, Organization, Surveys, Standard Terms and Conditions, Pricing, Channels, Financial Accounts, BBB...
The use of template data models can dramatically improve the understanding of business areas and accelerate development of related systems. The ability to move forward immediately without the lengthy period normally required to build baseline models is the tremendous advantage of template data models.
Template
data models can be of value to almost any company.
*
* *
How long would it take me to develop similar models?
Data models are very time-consuming to develop. They are time-consuming because
basic analysis must be performed such as the analysis of Order, Customer,
Market, Channel and so on. This type of analysis could be obtained from 'template'
models and edited to meet specific requirements.
An 'enterprise-wide'
model takes one year or more to develop.
Subject area models typically take 3-6 months or more.
Decision Support models require six months to 1 year to develop
Data Warehouse models require a minimum of 1 year to develop
It is not unusual for comprehensive modeling projects to cost millions of
dollars. Considerable time is required to just get people together because
of busy schedules. Rather than use that valuable time for doing baseline work,
it is more productive to start with existing template models and edit them
as a group.
We think it is wiser to buy detailed template models, take advantage of the knowledge contained therein and customize only the areas that need to be changed. Quickly. Efficiently. Seeing far in advance a near-complete approximation of what will be achieved.
The advantages of buying template data models are:
> Save time
> Save money
> Reduce staff
> Avoid repetitive analysis
> Knowledge transfer
> See results immediately
> Guaranteed quality
Planning is essential and expensive.
The way to shorten the process and reduce the costs is to buy sophisticated
'template' data models.
*
* *
What
services does ADRM provide?
ADRM and Business Partners provide consulting services in support of each
Data Environment.
> Knowledge Transfer
> IP Licensing/Applications
> Strategic Planning
> Business Subject Area Analysis
> Client Mentoring
> Data Resource Planning
> Data Modeling
> Data Warehouse Design
> Data Warehouse Reviews
> DSS Design and Development
> EIS Development
> Strategic Planning
Contact ADRM to discuss your
specific requirements
