Академический Документы
Профессиональный Документы
Культура Документы
Considerations
Overview
Implementation Considerations
Effective mm/dd/yy
Page 1 of 20
338445062.doc
Rev 1
Implementation Considerations
System References
None
Distribution
Oracle Demantra Fundamentals
Job Title*
Ownership
The Job Title [list@YourCompany.com?Subject=338445062.doc] is responsible for ensuring that
this document is necessary and that it reflects actual practice.
Implementation Considerations
Effective mm/dd/yy
Page 2 of 20
338445062.doc
Rev 1
Implementation Considerations
Schedule:
Timing
45 minutes
XX minutes
45 minutes
Topic
Lecture
Practice
Total
Implementation Considerations
Effective mm/dd/yy
Page 3 of 20
338445062.doc
Rev 1
Objectives
Objectives
Implementation Considerations
Effective mm/dd/yy
Page 4 of 20
338445062.doc
Rev 1
Agenda
Agenda
Implementation Considerations
Effective mm/dd/yy
Page 5 of 20
338445062.doc
Rev 1
Implementation Roadmap
Implementation Roadmap
Implementation Considerations
Effective mm/dd/yy
Page 6 of 20
338445062.doc
Rev 1
Sales history, including what was sold, where, the quantity and the dates on which an
item was shipped
Implementation Considerations
Effective mm/dd/yy
Page 7 of 20
338445062.doc
Rev 1
Information about the various item and location hierarchies that are meaningful to this
organization
After gathering this information, you should create a detailed design document for later use
during the implementation process.
Implementation Considerations
Effective mm/dd/yy
Page 8 of 20
338445062.doc
Rev 1
The planning units that your model will use (for example, physical cases, cost, weight,
and so on.)
Defining the global and local causal factors that will affect your forecast.
Implementation Considerations
Effective mm/dd/yy
Page 9 of 20
338445062.doc
Rev 1
After designing the data model, you should map the requirements to the Demantra data model
and identifying the gaps.
Implementation Considerations
Effective mm/dd/yy
Page 10 of 20
338445062.doc
Rev 1
Implementation Considerations
Effective mm/dd/yy
Page 11 of 20
338445062.doc
Rev 1
Configuring the data model to accommodate any gaps that were identified as part of step
one.
Adding any additional series and levels that your data model requires.
Building new worksheets (or alternately modify existing worksheets) to include the
series, levels, etc. in which youre interested.
After you define the data model and the components, it is often necessary to iterate by making
adjustments to both the data model and the components.
You may need to use the Business Modeler for the following tasks:
Copyright Oracle, 2007. All rights reserved.
Implementation Considerations
Effective mm/dd/yy
Page 12 of 20
338445062.doc
Rev 1
Implementation Considerations
Effective mm/dd/yy
Page 13 of 20
338445062.doc
Rev 1
Implementation Considerations
Effective mm/dd/yy
Page 14 of 20
338445062.doc
Rev 1
The forecast tree should contain 3 to 6 levels on which the engine can traverse and
forecast. This number does not include any levels below the minimum forecast level.
Copyright Oracle, 2007. All rights reserved.
Implementation Considerations
Effective mm/dd/yy
Page 15 of 20
338445062.doc
Rev 1
The levels of the forecast tree need to have meaningfully changing data sets per level in
order to be effective. A move from level to level should substantially increase the amount
of data that is being analyzed by the Analytical Engine while maintaining an aggregation
method that makes sense from a business perspective.
The minimum and maximum forecast levels should contain reasonable and relevant data.
The minimum forecast level should have enough data to facilitate a forecast desirable by
the customer, while the maximum forecast level should still be disaggregated enough to
maintain some data granularity.
The default parameters used by the Analytical Engine may not be suitable for all
customers/implementations. Based on the initial forecast, you may choose to adjust these
parameters that control how the individual models work. This fine-tuning allows you to
maximize the Analytical Engines performance.
Implementation Considerations
Effective mm/dd/yy
Page 16 of 20
338445062.doc
Rev 1
Architecture Considerations
Architecture Considerations
Implementation Considerations
Effective mm/dd/yy
Page 17 of 20
338445062.doc
Rev 1
Performance Considerations
Performance Considerations
The Analytical Engines run time is dependent upon several factors:
1.
2.
3.
Use these considerations when performance tuning and estimating your hardware requirements:
Make sure that your worksheets are configured correctly (for example, filtered to
a manageable size, based on the user who will use them, and so on).
Implementation Considerations
Effective mm/dd/yy
Page 18 of 20
338445062.doc
Rev 1
Implementation Considerations
Effective mm/dd/yy
Page 19 of 20
338445062.doc
Rev 1
Summary
Summary
Implementation Considerations
Effective mm/dd/yy
Page 20 of 20
338445062.doc
Rev 1