5.8.1.2 Event Generation for Custom Scenario

This pre-seeded batch is available in both Production and Sandbox workspaces.

Note:

This batch has to be executed in the Production workspace.

Batch and Task Parameters

The batch contains the following tasks:

• Task 1: Aggregate_Scoring_Base_Features
• Task 2: Event_Processing

  Figure 5-107 Define Task for Event Generation

  
  

  
  Description of "Figure 5-107 Define Task for Event Generation"

  
  

Task 1: Task Parameters for Aggregate_Scoring_Base_Features

• Objective folder for this task:

  Home / Modeling / Pipelines / ML4AML / Custom Scenario / Batch / Base Features

  Note:

  You should not change any parameter except Optional Parameters.
• Optional Parameters:
  • prod_flag: This flag indicates Training/Scoring scenario. The option is either Y or N. For production/ scoring scenarios, the prod_flag should be set to Y.
  • model_group_name: Name of the Model Group for which Base Feature Aggregation is created. For example, LOB1.
  • model_name: Name of the Model used while importing model template using Admin Notebook. For example, RMF.
  • focus: The model entity name provided in the Admin notebook dataframe while creating the model group. The option is either CUSTOMER or ACCOUNT.

    For example: prod_flag=Y,model_group_name=GROUP1,model_name=M1,focus=CUSTOMER.

• Edit Task Parameters and Save.

  Figure 5-108 Edit Task for Aggregate_Scoring_Base_Features for Custom Scenario

  
  

  
  Description of "Figure 5-108 Edit Task for Aggregate_Scoring_Base_Features for Custom Scenario"

  
  

Task 2: Task Parameters for Event_Processing

• Objective folder for this task:

  Home / Modeling / Pipelines / ML4AML / Custom Scenario / Models / Event Processing

  Note:

  You should not change any parameter except Optional Parameters.
• Optional Parameters:
  • prod_flag: This flag indicates Training/Scoring scenario. The option is either Y or N. For production/ scoring scenarios, the prod_flag should be set to Y.
  • model_group_name: Name of the Model Group for which Base Feature Aggregation is created. Example: LOB1.
  • model_name: Name of the Model used while importing the model template using Admin Notebook. For example, RMF.
  • focus: The model entity name provided in the Admin notebook dataframe while creating the model group. The option is either CUSTOMER or ACCOUNT.

    For example: prod_flag=y, model_group_name=GROUP1,model_name=M1,focus=CUSTOMER

    .
• Edit Task Parameters and Save.

  Figure 5-109 Edit Task for Event_Processing of Custom Scenario

  
  

  
  Description of "Figure 5-109 Edit Task for Event_Processing of Custom Scenario"

  
  

  Note:

  Once the batch execution is successful, the results are available in the CS_EVENT_SCORE and CS_EVENT_SCORE_DETAILS tables. For more information on these table structure, see OFS Compliance Studio Data Model Reference Guide.