13 Control and Tactical Center

This chapter describes the Control and Tactical Center, where an administrative user can access and manage configurations for different applications.

Under the Control and Tactical Center, a user can access Strategy and Policy Management, which is the central place for managing the configurations of different applications and for setting up and configuring the demand forecasting runs. In addition, the modules for managing product attributes (Attribute Extraction and Attribute Binning) as well as the link for managing web service-related credentials can be also found under the Control and Tactical Center.

Depending on the role, a user will see one or multiple of the following links, as shown in Figure 13-1. Typically, the administrative user has access to all of the following.

Strategy and Policy Management
Manage Credential Stores
Attribute Extraction
Attribute Binning

Figure 13-1 Control and Tactical Center

Description of ''Figure 13-1 Control and Tactical Center''

Strategy and Policy Management

In Strategy and Policy Management, a user can edit the configurations of different applications using the Manage System Configurations screen. Only the tables that are editable can be accessed in this screen. Within each table, one or multiple columns are editable and a user can override the values in those columns.

Manage Forecast Configurations can be used to set up, manage, and configure the demand forecasting runs for different applications such as Offer Optimization (OO), Inventory Optimization (OO), Retail Demand Forecasting (RDF), and Merchandise Financial Planning (MFP).

Forecast Configuration for MFP

To configure the forecast process for MFP, complete the following two steps:

Use the Manage System Configurations screen to review and modify the global configurations in RSE_CONFIG. For further details, see "Configuration Updates". The relevant configurations in RSE_CONFIG that must be reviewed and edited as required are listed in Table 13-1.

Table 13-1 Configurations

APPL CODE	PARAM NAME	PARAM VALUE	DESCR
RSE	EXTENDED_HIERARCHY_SRC	Default value is NON-RMS.	Data source providing extended hierarchy data RMS/NON-RMS.
RSE	LOAD_EXTENDED_PROD_HIER	Default value is Y. If the product hierarchy data had nine levels, keep this value as Y. If it has seven levels, change this value to N.	Y/N Value. This parameter is used by the product hierarchy ETL to determine if the extended product hierarchy is required.
PMO	PMO_PROD_HIER_TYPE	Default value is 3. If the product hierarchy data has nine levels (i.e., it has an extended hierarchy), keep this value as 3. If it has seven levels, change this value to 1.	The hierarchy ID to use for the product (installation configuration).
RSE	PROD_HIER_SLSTXN_HIER_LEVEL_ID	Default value is 9.	This parameter identifies the hierarchy level at which sales transactions are provided (7-Style, 8-Style/color, or 9 Style/color/Size). It must match the extended hierarchy leaf level.
PMO	PMO_AGGR_INVENTORY_DATA_FLG	Default value is Y.	Specifies if inventory data is present and if it must be used when aggregating activities data. Set this value to N if inventory data is not loaded. (Inventory data is not required for MFP forecasting but it is required for other applications such as Offer Optimization, Inventory Optimization and Retail Demand Forecasting.)

Use the Manage Forecast Configurations screen to set up the forecast runs for MFP, as follows.

Start by setting up a run type in the Setup train stop. Click the + icon above the table and fill in the fields in the pop-up. For MFP forecasting, the forecast method must be selected as Automatic Exponential Smoothing. You must create a run type for each forecast measure/forecast intersection combination that is required for MFP.

Once you have finished setting up the run types, click Start Data Aggregation in the Setup train stop. Select all the run types that were created and click Submit. When the aggregation is complete, the aggregation status will change to Complete. At this point, ad-hoc test runs and batch runs can be created and executed to generate a forecast.

To create an ad-hoc run, go to the Test train stop. First, click a run type in the top table and then click the + icon in the bottom table to create a run. In the Create Run pop-up, you can change the configurations parameters related to estimation process and forecast process in their respective tabs. For example, if you want to test a run using the Bayesian method, edit the Estimation Method parameter in the Estimation tab using the Edit icon above the table. After modifying and reviewing the configuration parameters, click Submit to start the run. Once the run is complete, the status will change to Forecast Generation Complete.

Doing test runs is an optional step. In addition to that, you must modify and review the configurations of the run type, activate the run type, enable auto-approve, and map the run type to the downstream application (in this case to MFP). In the Manage train stop, select a row, click Edit Configurations Parameters, and edit the estimation and forecast parameters as necessary. Once you are done, go to Review tab and click Validate and then close tab.

Note:
If the run type is active, you will only be able to view the parameters. In order to edit the parameters, the run type must be inactive.

To activate the run type and enable the auto-approve, select a run type in the table and click the corresponding buttons above the table. Lastly, to map the run type to MFP, go to Map train stop and click the + icon to create a new mapping.

Run Type Configurations for MFP to Set Up GA Runs

To set up GA runs, create one run type for each forecast intersection/measure combination. Table 13-2 shows the configurations for each run type.

Table 13-2 Run Type Configurations

	Forecast Level (Merchandise/Location/Calendar)	Forecast Measure	Forecast Method	Data Source
Location Plan	Department/Location/Week	Total Gross Sales Units	Automatic Exponential Smoothing for all run types	Store Sales for all run types
		Total Gross Sales Amount
		Total Returns Units
		Total Returns Amount
Location Target	Company/Location/Week	Total Gross Sales Units
		Total Gross Sales Amount
		Total Returns Units
		Total Returns Amount
Merchandise Plan	Subclass/Area/Week	Clearance Gross Sales Units
		Clearance Gross Sales Amount
		Regular and Promotion Gross Sales Units
		Regular and Promotion Gross Sales Amount
		Total Returns Units
		Total Returns Amount
Merchandise Target	Department/Area/Week	Clearance Gross Sales Units
		Clearance Gross Sales Amount
		Regular and Promotion Gross Sales Units
		Regular and Promotion Gross Sales Amount
		Total Returns Units
		Total Returns Amount

Note:

For all batch runs, in addition to the pre-season forecast, the Bayesian forecast is also generated by default. So in Manage train stop, you must only set the method for the pre-season forecast (either as Automatic Exponential Smoothing or Seasonal Exponential Smoothing).

Batch and Ad-Hoc jobs for MFP Forecasting

The Batch and Ad-Hoc jobs listed in Table 13-3 are used for loading foundation data (product hierarchy, location hierarchy, calendar, product attributes, and so on).

Table 13-3 Batch and Ad-Hoc Jobs for MFP Forecasting

JobName	Description	RmsBatch
ORASE_START_BATCH_JOB	ORASE_START_BATCH_JOB	rse_process_state_update.ksh
ORASE_START_BATCH_SET_ACTIVE_JOB	ORASE_START_BATCH_SET_ACTIVE_JOB	rse_batch_type_active.ksh
ORASE_START_BATCH_REFRESH_RESTR_JOB	ORASE_START_BATCH_REFRESH_RESTR_JOB	rse_batch_freq_restriction.ksh
ORASE_START_BATCH_END_JOB	ORASE_START_BATCH_END_JOB	rse_process_state_update.ksh
RSE_WEEKLY_INPUT_FILES_START_JOB	RSE_WEEKLY_INPUT_FILES_START_JOB	rse_process_state_update.ksh
RSE_WEEKLY_INPUT_FILES_END_JOB	RSE_WEEKLY_INPUT_FILES_END_JOB	rse_process_state_update.ksh
RSE_PROD_HIER_ETL_START_JOB	RSE_PROD_HIER_ETL_START_JOB	rse_process_state_update.ksh
RSE_PROD_SRC_XREF_LOAD_JOB	RSE_PROD_SRC_XREF_LOAD_JOB	rse_prod_src_xref_load.ksh
RSE_PROD_HIER_LOAD_JOB	RSE_PROD_HIER_LOAD_JOB	rse_prod_hier_load.ksh
RSE_PROD_TC_LOAD_JOB	RSE_PROD_TC_LOAD_JOB	rse_prod_tc_load.ksh
RSE_PROD_DH_LOAD_JOB	RSE_PROD_DH_LOAD_JOB	rse_prod_dh_load.ksh
RSE_PROD_GROUP_LOAD_JOB	RSE_PROD_GROUP_LOAD_JOB	rse_load_prod_group.ksh
RSE_PROD_HIER_ETL_END_JOB	RSE_PROD_HIER_ETL_END_JOB	rse_process_state_update.ksh
RSE_LOC_HIER_ETL_START_JOB	RSE_LOC_HIER_ETL_START_JOB	rse_process_state_update.ksh
RSE_LOC_SRC_XREF_LOAD_JOB	RSE_LOC_SRC_XREF_LOAD_JOB	rse_loc_src_xref_load.ksh
RSE_LOC_HIER_LOAD_JOB	RSE_LOC_HIER_LOAD_JOB	rse_loc_hier_load.ksh
RSE_LOC_HIER_TC_LOAD_JOB	RSE_LOC_HIER_TC_LOAD_JOB	rse_loc_hier_tc_load.ksh
RSE_LOC_HIER_DH_LOAD_JOB	RSE_LOC_HIER_DH_LOAD_JOB	rse_loc_hier_dh_load.ksh
RSE_LOC_HIER_ETL_END_JOB	RSE_LOC_HIER_ETL_END_JOB	rse_process_state_update.ksh
RSE_PROD_ATTR_LOAD_START_JOB	RSE_PROD_ATTR_LOAD_START_JOB	rse_process_state_update.ksh
RSE_PROD_ATTR_LOAD_END_JOB	RSE_PROD_ATTR_LOAD_END_JOB	rse_process_state_update.ksh
RSE_CM_GRP_HIER_LOAD_START_JOB	RSE_CM_GRP_HIER_LOAD_START_JOB	rse_process_state_update.ksh
RSE_CM_GRP_HIER_LOAD_END_JOB	RSE_CM_GRP_HIER_LOAD_END_JOB	rse_process_state_update.ksh
RSE_TRADE_AREA_HIER_LOAD_START_JOB	RSE_TRADE_AREA_HIER_LOAD_START_JOB	rse_process_state_update.ksh
RSE_TRADE_AREA_SRC_XREF_LOAD_JOB	RSE_TRADE_AREA_SRC_XREF_LOAD_JOB	rse_trade_area_src_xref_load.ksh
RSE_TRADE_AREA_HIER_LOAD_JOB	RSE_TRADE_AREA_HIER_LOAD_JOB	rse_trade_area_hier_load.ksh
RSE_TRADE_AREA_TC_LOAD_JOB	RSE_TRADE_AREA_TC_LOAD_JOB	rse_trade_area_tc_load.ksh
RSE_TRADE_AREA_DH_LOAD_JOB	RSE_TRADE_AREA_DH_LOAD_JOB	rse_trade_area_dh_load.ksh
RSE_TRADE_AREA_HIER_LOAD_END_JOB	RSE_TRADE_AREA_HIER_LOAD_END_JOB	rse_process_state_update.ksh
RSE_CAL_HIER_ETL_START_JOB	RSE_CAL_HIER_ETL_START_JOB	rse_process_state_update.ksh
RSE_REGULAR_MAIN_LOAD_JOB	RSE_REGULAR_MAIN_LOAD_JOB	rse_regular_main_load.ksh
RSE_FISCAL_MAIN_LOAD_JOB	RSE_FISCAL_MAIN_LOAD_JOB	rse_fiscal_main_load.ksh
RSE_CAL_HIER_ETL_END_JOB	RSE_CAL_HIER_ETL_END_JOB	rse_process_state_update.ksh
RSE_DIMENSION_LOAD_END_START_JOB	RSE_DIMENSION_LOAD_END_START_JOB	rse_process_state_update.ksh
RSE_DIMENSION_LOAD_END_END_JOB	RSE_DIMENSION_LOAD_END_END_JOB	rse_process_state_update.ksh
RSE_DIMENSION_LOAD_START_START_JOB	RSE_DIMENSION_LOAD_START_START_JOB	rse_process_state_update.ksh
RSE_DIMENSION_LOAD_START_END_JOB	RSE_DIMENSION_LOAD_START_END_JOB	rse_process_state_update.ksh
RSE_SLS_START_START_JOB	RSE_SLS_START_START_JOB	rse_process_state_update.ksh
RSE_SLS_START_END_JOB	RSE_SLS_START_END_JOB	rse_process_state_update.ksh
RSE_SLS_END_START_JOB	RSE_SLS_END_START_JOB	rse_process_state_update.ksh
RSE_SLS_END_END_JOB	RSE_SLS_END_END_JOB	rse_process_state_update.ksh
ORASE_END_START_JOB	ORASE_END_START_JOB	rse_process_state_update.ksh
ORASE_END_RUN_DATE_UPDT_JOB	ORASE_END_RUN_DATE_UPDT_JOB	rse_batch_run_date_update.ksh
ORASE_END_END_JOB	ORASE_END_END_JOB	rse_process_state_update.ksh
RSE_BATCH_ENABLE_ADHOC_JOB	Enable the running of AdHoc batches while disabling Scheduled batches	rse_batch_enable_adhoc.ksh
RSE_BATCH_DISABLE_ADHOC_JOB	Disable the running of AdHoc batches while enabling Scheduled batches	rse_batch_enable_scheduled.ksh
RSE_FCST_SALES_PLAN_START_JOB (needed for Bayesian method)	Start job for sales plan data load	rse_process_state_update.ksh
RSE_FCST_SALES_PLAN_LOAD_JOB (needed for Bayesian method)	Load job for sales plan data	rse_fcst_sales_plan_load.ksh
RSE_FCST_SALES_PLAN_END_JOB(needed for Bayesian method)	End job for sales plan data load	rse_process_state_update.ksh
RSE_MASTER_ADHOC_JOB	Run RSE master script	rse_master.ksh
PMO_ACTIVITY_LOAD_START_JOB	PMO Activity load start job	rse_process_state_update.ksh
PMO_ACTIVITY_STG_JOB	PMO Activity data staging	pmo_activity_load_setup.ksh
PMO_ACTIVITY_LOAD_JOB	PMO Activity load job	pmo_activity_load_process.ksh
PMO_ACTIVITY_LOAD_END_JOB	PMO Activity load end job	rse_process_state_update.ksh
RSE_MFP_FCST_BATCH_RUN_START_JOB	Start job for executing MFP forecast batch runs	rse_process_state_update.ksh
RSE_CREATE_MFP_BATCH_RUN_PROC_JOB	Create MFP batch runs	rse_create_mfp_batch_run_procksh
RSE_MFP_FCST_BATCH_PROCESS_JOB	Execute MFP forecast batch	rse_fcst_mfp_batch_process.ksh
RSE_MFP_FCST_BATCH_RUN_END_JOB	End job for executing MFP forecast batch runs	rse_process_state_update.ksh
RSE_CREATE_MFP_BATCH_RUN_PROC_ADHOC_JOB	Ad hoc job to create MFP batch runs	rse_create_mfp_batch_run_procksh
RSE_MFP_FCST_BATCH_PROCESS_ADHOC_JOB	Ad hoc job to execute MFO forecast batch	rse_fcst_mfp_batch_process.ksh

The forecast values generated by runs that are associated with active run types are exported to the RDX schema. The jobs for exporting the outputs to the RDX schema are listed in Table 13-4.

Table 13-4 Export Jobs

JobName	Description	RmsBatch
RSE_MFP_FCST_EXPORT_JOB	Export MFP forecast	rse_mfp_export.ksh
RSE_MFP_FCST_EXPORT_ADHOC_JOB	Ad hoc job to export MFP forecast	rse_mfp_export.ksh