3. CAPACITY PLANNING DATABASE › 3.5 Business Element Files › 3.5.2 Screen Operation › 3.5.2.1 File Definition
3.5.2.1 File Definition
The first step in creating a business element file definition
is to identify the timespan of the data that will be
maintained in the file and to specify the data retention
control parameters. You may specify these parameters on the
Business Element File Definition screen shown in Figure
3-125.
/---------------------- Business Element File Definition ---------------------\
|Command ===> |
|Enter a ? in any data entry field for more information on valid values. |
|Composing CAP DB File def.: BEF - Business Element File |
| |
| |
|Time-span ===> MONTHS (DAYS/WEEKS/MONTHS) |
|Starting date ===> _______ (ddmonyy) |
|Number of months ===> ___ (for pre-formatting records) |
| |
| |
|Maximum amount of data available for analysis ===> 60 (1-9999 months) |
|Age of oldest forecast ===> 24 (1-9999 months) |
|Number of cycles retained: History file ===> 3 (1-99 cycles) |
| Forecast file ===> 3 (1-99 cycles) |
| |
| |
| |
| |
| |
| |
| |
|Specify business element file data elements ===> N (Y/N) |
\------------------------------------------------------------------------------/
Figure 3-125. Business Element File Definition Screen
The Business Element File Definition screen shown in Figure
3-125 is the main control screen for defining business
element files. It contains the following fields:
Timespan: The timespan (either DAYS, WEEKS, or MONTHS) of
the CA MICS file(s) that you wish to use as
input for processing when the business element
file is loaded. This timespan must match that
of the resource element or standard application
files against which business-related measures
are analyzed.
Starting An optional parameter that provides the starting
date: date for the initialized entries in your
business element file if file initialization is
to be performed. Section 3.5.1 discusses
the initialization process.
Number of The number of initialized observations that are
months: placed in your business element file if file
initialization is performed.
Maximum
amount of The number of months or weeks of historical data
data to be retained in the database. Any
available observations older than what you specify for
for this parameter are dropped from the file during
analysis: update processing.
Age of The number of days, weeks, or months that you
oldest wish to retain a forecast after it is generated.
forecast: Any forecast older than what you specify for
this parameter is dropped whenever a new
forecast is generated. The values of the
FORYEAR and FORMNDY/FORWEEK/FORMONTH are used to
determine the age of the forecast.
Number of The number of cycles or versions of the
history historical data that you wish to retain. A new
cycles cycle is created when the file is updated and
retained: the existing cycles are aged (that is, Cycle 01
becomes Cycle 02 and Cycle 02 becomes Cycle 03).
Number of The number of cycles or versions of the forecast
forecast data that you wish to retain. A new cycle is
cycles created when the file aging is specified on one
retained: of the workload forecasting routine control
screens and the existing cycles are aged (that
is, Cycle 01 becomes Cycle 02 and Cycle 02
becomes Cycle 03).
Specify
business The specification for the business element file
element file data elements. If you specify a Y (YES),
data the Business Element File Data Elements screen
elements: shown in Figure 3-126 is displayed.
Copyright © 2014 CA.
All rights reserved.
|
|