Skip to main content

AIM accelerator architecture

In Pega Alert and Investigation Management (AIM), alert producing systems such as Transaction Monitoring initiate the Alerts. The Event-driven Architecture receives the Alerts before handing off the Alert for processing through two key case types, the Alert Intake case and the Investigation case. This topic explores the architecture of AIM and provides an overview of terms and functional areas of AIM.

Architecture

The following diagram provides a high-level overview of the solution:

Terms and functional areas

The following list outlines the terms and functional areas that comprise the AIM accelerator:

Alert: An Alert is a set of data generated by an Alerting system, such as Transaction Monitoring or Sanctions Screening. Alerts should contain sufficient information, directly or via reference IDs, to allow another system to process the Alert and take the appropriate business-driven actions.

Alert reception (Event-driven Architecture): The reception of Alerts is critical for AIM, which needs to manage Alerts coming from different systems and modules to help financial institutions ensure continuous regulatory compliance. For this purpose, the solution includes an infrastructural component, EDA, that facilitates the implementation of event-driven processes. The component manages the reception of Alerts and events from different sources and routes them to the appropriate applications and processes in charge of their resolution.

Alert Intake: The core function of the Alert Intake case is to ingest each Alert that is received, ensure sufficient data and instructions are available to progress the processing of the Alert, and, where necessary, assign it to an Investigation case. The system automatically creates an Alert Intake case for each Alert.

Investigation: The core function of the Investigation case is to provide a robust and efficient process whereby at least one Alert can be triaged and investigated and, on conclusion of the investigation, run potential Post-Investigation actions such as filing a Suspicious Activity Report to the necessary regulator.

Research Task: The core function of the Research task case is to collect information and record activities external to the system related to a specific task (for example, information about the Source of Funds related to a transaction). This is facilitated using a questionnaire linked to each task. Specific questions from each questionnaire can be applied based on input driver data.

Data Analyzer: The Data Analyzer (DA) component maintains a network of key data related to Alerts and Investigations to support the investigation: Transactions, Accounts, and Subjects. The ability to visualize this network of data and relationships and apply filters accordingly helps investigators see the connections they need to complete their work.

Subject: A Subject is an individual or organization that is included in an Investigation. The relationship that the financial institution has with a Subject impacts the amount of data that is initially available. Subjects are categorized as follows: an active customer, a known related party of a customer, such as a beneficial owner of an existing customer, or an external party unknown to the financial institution. During the Alert Intake process, Subjects are extracted directly from the available data in the Alert. During the automated Enrichment Step in this Process the system can also automatically add additional Subjects to the Investigation as discovered (for example, a joint account holder of the Account included in an Alert).


This Topic is available in the following Module:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice