5.4.4.2 AMLES Scoring

1. This is a pre-seeded batch and will be available in all workspaces (production and sandboxes)
2. This Batch is to be executed in the Production workspace.

Execution Frequency

Scenario frequency gives the flexibility to schedule event-scoring solution at appropriate frequency so that daily, weekly and monthly events can easily be handled by event-scoring notebook.

As a solution, raw data which is input for event-scoring is pulled on daily basis. It consists of daily, weekly and monthly alerts.

Since alerts are pulled from ECM on daily basis, it is possible weekly and monthly alerts are not pulled daily. In this case, weekly and monthly event-scoring notebook exits gracefully and makes one entry in amles_event_score table with status as No Data and with the status as successful.

Output of AMLES event-scoring is stored in following static tables in BD schema.

• amles_event_score
• amles_event_score_details

Batch and Task Parameters

The batch contains the following tasks:

• Scoring_Event_Data_Load
• ML_Scoring

  Figure 5-77 Define Task

  
  

  
  Description of "Figure 5-77 Define Task"

  
  

Scoring_Event_Data_Load, Task Parameters

• Objective folder for this task:

  Home / Modeling / Pipelines / AMLES Batch Framework / Load Events / AMLES
  Data Load

• Model: Retain the default settings.

  Note:

  • For a fresh installation, do not modify any parameters except Optional Parameters.
  • For upgrade, see the How to Execute Model Scoring/Annual Model Validation with the Batch Framework section.
• Optional Parameters:
  • is_ECM_on_remote_schema: Flag indicates ECM Schema is on different schema or not. Options True or False
  • enable_debug_mode: enable debug mode or not. Options True or False

    Example : is_ECM_on_remote_schema=True

  • Optional Parameters can be edited from the Schedule Batch option.

ML_Scoring, Task Parameters

• Objective folder for this task:

  Home / Modeling / Pipelines / AMLES

• Navigate to respective model group/scenario folders for actual model templates.
• Model: Retain the default settings.

  Note:

  • For a fresh installation, do not modify any parameters except Optional Parameters and Link Types.
  • For upgrade, see the How to Execute Model Scoring/Annual Model Validation with the Batch Framework section.
• Optional Parameters:
  • threshold: Input threshold or cutoff to create events. Events will be created if the score of an entity exceeds the threshold. Example: 0.7
  • debug_flag: flag to set for debugging purpose. Few records will be selected.

    Options: True or False

  • Optional Parameters can be edited from the Schedule Batch option.
  • Choose Link Types as Scoring.

    Figure 5-78 Edit Task for AMLES_Scoring

    
    

    
    Description of "Figure 5-78 Edit Task for AMLES_Scoring"