E.6.5 Control Data Management
Control data uses a specific set of dates to ensure that all the lock-stock scenarios are tested using this data. The maximum lookback that control data considers is of 13 months, which is for change in behavior scenarios. The control data is spread over 25 different dates in 13 months. The dates (YYYYMMDD format) being used by control data are:
Table E-4 Dates used by Control Data
| Dates | Dates |
|---|---|
| 20141231 | 20151123 |
| 20150130 | 20151124 |
| 20150227 | 20151125 |
| 20150331 | 20151126 |
| 20150430 | 20151127 |
| 20150529 | 20151130 |
| 20150630 | 20151203 |
| 20150731 | 20151204 |
| 20150831 | 20151208 |
| 20150930 | 20151209 |
| 20151030 | 20151210 |
| 20151201 | 20151202 |
| 20151121 | - |
On all these dates, ingest the data and run the complete batch for the respective date.
Except for TBAML and Post-Processing tasks, perform all other activities for the Control
Data Management dates. Activities required during any Behavior Detection Framework
business day are - START BATCH > DRM > DATA INGESTION > BEHAVIOR DETECTION >
POST PROCESSING > END BATCH.
- Copy all control data from the golden data directory in the database subsystem
(
/database/ golden_data directory) to the Ingestion Manager /inbox directory bdf /inbox. - Run ingestion for all the control Data Management dates. Refer to
section Ingestion Timeline - Intra-Day Ingestion Processing, for more
information about the ingestion process.
Note:
You must adjust the partitions of the database tables as per the new dates, if you intend to process Control Data after the database upgrade to TBAML.