5.1 Automated Scenario Calibration (ASC)

This section describes about Automated Scenario Calibration (ASC).

Prerequisites

Before creating the ASC workspace, the user should follow these steps:

1. The target schema used for the ASC workspace should be a valid BD atomic schema like BD preprod, BD UAT, BD Dev, etc., because we use BD packages and functionality to reproduce alerts as in BD.
2. Create the Tablespace
3. Assign grants to the ASC BD Schema
4. Create a new data store for ASC BD schema

   Note:

   ASC runs scenarios to produce test alerts. Hence, the BD production schema should not be used as an ASC BD target.

To create the data store, see How to Create Data Store section.

For more information on creating tablespace and assign grants to sandbox (ASC BD) schema, see the OFS Compliance Studio Installation Guide.

• Creating ASC Workspace
  On the Workspace Summary page, click Add Workspace. The Create Workspace window is displayed with the following process:
• Importing Workspace Metadata
  
• Using Scenario Conversion Utility for ASC
  Scenario Conversion Utility (SCU) converts BD scenarios to Compliance Studio notebooks for the scenarios and respective thresholds.
• Comparison of Events between BD and Conversion Utility
  Scenario Conversion Utility allows you to compare scenario execution results from BD Engine with the Scenario Conversion utility notebook of Compliance Studio.
• Using Delete Threshold Sets Notebook
  This notebook provides functionality for deleting threshold sets created for SCU, especially when migrating threshold sets from the lower to the higher version of the BD environment by deleting unwanted threshold sets from the systems.
• Using Dynamic Datasets with AML Scenario Conversion
  This notebook provides functionality for loading dynamic datasets while AML scenario conversion using SCU.
• Advanced Concepts for ASC