5.4.4.2 AMLES Scoring
- This is a pre-seeded batch and will be available in all workspaces (production and sandboxes)
- This Batch is to be executed in the Production workspace.
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.
- amles_event_score
- amles_event_score_details
- Scoring_Event_Data_Load
- ML_Scoring
- Objective folder for this task
:
Home / Modeling / Pipelines / AMLES Batch Framework / Load Events / AMLES Data Load - Do not change any parameter, except Optional Parameters.
- 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.
- Do not change any other batch /task parameters, except Optional Parameters.
- Objective folder for this task
:
Home / Modeling / Pipelines / AMLES - Navigate to respective model group/scenario folders for actual model templates.
- 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.
- Do not change any batch/task parameters, except Optional Parameters.
- Choose Link Types as Scoring.
