Install and configure

This page provides the instructions for the AMM skill's installation to the v.10.2.4 instance.

Requirements

Hardware

The AMM skill runs on the standard Intelligent Automation Cloud hardware configuration, as documented in System Requirements.

Server	Recommended OS	CPU (cores)	RAM (GB)	HDD (GB)
Master	RHEL 8.5	8	32	750
Agent	RHEL 8.5	4	16	150
RPA	Windows Server 2016	2	8	50
Analytics	Windows Server 2016	16	32	150
MSSQL	Windows Server 2016	2/4	8/16	500

note

The RPA server is only required if you use Google API as the news source.

The configuration above is designed to handle up to 5,000 articles per hour. For higher volumes, you can add extra BEP servers. You can horizontally scale both BEP and RPA servers to handle up to 50,000 news articles per hour.

• Each Agent server can handle 5,000 articles per hour.
• Each RPA bot can process 200 articles per hour.
• For the Application, Analytics, and SQL servers, the horizontal scaling is not required. For volumes higher than 5,000 articles/hour, a second full deployment is recommended.

Software

IA Cloud Enterprise v.10.2.4 or later. Note that for IA Cloud 10.1.6+, ODF 2 is installed automatically along with the system.

Performance

Adverse Media Monitoring leverages BEP servers and RPA nodes, which can be horizontally scaled for higher volumes.

Below is a sample of the volumes that can be expected when using the below versions and configurations.

The Search provider used is Google API, note that throughputs may vary slightly based on provider.

Configuration:

AMM version	Search provider	Environment topology	IA Cloud version	AutoML Worker configuration	Control Tower Worker configuration
AMM 2.9.0	Google API	Standard 6-server topology (3 BEP agents + 3 RPA nodes)	10.2.4	1 CPU/ 8 GB memory	0.4 CPU/ 2 GB memory

Results:

• Test duration: ~ 25 mins
• Input file Names count: 100
• Processing Names per hour (average): 256
• Average records processing time on RPA node: ~ 1 record per 6 sec

Install AMM

Prerequisites

Before installing AMM, make sure that your environment meets the requirements:

• You have installed IA Cloud Enterprise v.10.2.4+ and have Control Tower and Analytics components enabled.
• You have the bundle with AMM Business Process and ML models.
• You have received the credentials for the required watchlists or license for the external screening software to be integrated with AMM.
• You have the Advanced Package Import and Import/Export permissions in Control Tower.

To check that ODF is installed:

1. Log in to Control Tower, and in the menu, click Advanced > Data Stores.

2. In the list, find data stores with names _odf_transactions and _odf_transactions_status. If they are on the list, ODF is already installed on your instance.

   

If the Data Stores are missing, download ODF and save odf-install-package-10.1.0.7.zip to your local workstation.

There are two ways of installing the skill:

• If you are setting the AI Digital Worker up for the first time, use the Solution Catalog.
• If you have worked with the AI Digital Worker in earlier IA Cloud versions, use the package.

To install the AMM AI Digital Worker:

From Solution Catalog

1. In Control Tower, on the left menu, go to Use Cases > Solution Catalog.

   

2. In the dialog window, find the Adverse Media Monitoring group and click Details in it.

   

3. In the Digital Worker window, click Install.

   

For more information about the installation, see Install AI Agents.

From package

The package consists of the following parts:

• negativenews-package-10.xxx.zip contains the Business Process, Data Stores, Templates, and other artifacts specific to the skill (automatic build).
• negativenews-package-xxx-models.zip is a static package containing a trained model and hypermodel.

1. In Control Tower menu, click Use Cases > View All. The list of use case groups appears.

2. Go to Upload new > Add new Use Case > Add, and select the downloaded archive with the Business Process.

   

   The installation starts automatically.

   

After the successful installation, AMM appears in the corresponding group.

Configure AMM

Set up API credentials in Secrets Vault

Before setting the news providers, make you you have obtained the corresponding license with credentials.

If you wish to use a provider other than Google API, you must first set up the above credentials in the Secrets Vault. For the step-by-step instructions, see this guide.

Select provider

To select a news provider, do the following:

1. In the Control Tower menu, in the Use Cases section, find your newly installed AMM skill, and click the Prepare use case button.

   The Use Case Configuration window containing the configuration form appears.

2. In the window, on the Provider tab, select a news provider for searching for news about the entity or individual. "Google API" is set by default.

   The required configurations may differ based on the selected news provider.

   

Configure provider

The Negative News skill supports news retrieval from the following news providers:

• Google API v1-rev86-1.25.0
• Dow Jones Factiva Analytics 2.0
• LexisNexis L&P News v1
• World-Check One

You also have to customize and train the skill to use other providers.

The Factiva options can be used with the provided API keys for development, testing, and demonstration purposes. For production usage, you must acquire corresponding production keys from Dow Jones.

To configure a provider, specify the providers' parameters. For a detailed description of each setting, see the following sections.

Google API

• Google API Credentials Location. Specify the corresponding Secret Vault alias for the Google API system.
• Article Language. Select the language of articles to search in. ‘Any’ language is used by default.
• Number of articles to extract. Specify the maximum number of reports to fetch from 1 to 20. By default, up to 20 articles are retrieved.
• Search Time period. Select an option to find information published during a specific time frame. To specify the starting and the ending date for the articles' search, select Custom Range.

Factiva

• Factiva API URL. Select the address of the Factiva API. Available options:

  • https://api.beta.dowjones.com
  • https://djrc.api.dowjones.com

• Factiva Credentials Location. Specify the corresponding Secret Vault alias for the Factiva system.

• Article Language. Select the language of articles to search in. ‘English’ language is used by default.

• Number of articles to extract. Specify the maximum number of reports to fetch from 1 to 100. By default, up to 20 articles are retrieved.

• Search Time period. Select an option to find information published during a specific time frame.

LexisNexis

• LexisNexis API URL. Select the address of the LexisNexis API. By default, https://services-api.lexisnexis.com.
• LexisNexis Authentication URL. Specify the Authentication URL for the LexisNexis News. By default, https://auth-api.lexisnexis.com.
• LexisNexis Credentials Location. Specify the corresponding Secret Vault alias for the LexisNexis News system.
• Article Language. Select the language of articles to search in. ‘English’ language is used by default.
• Number of articles to extract. Specify the maximum number of reports to fetch from 1 to 100. By default, up to 20 articles are retrieved.
• Search Time period. Select an option to find information published during a specific time frame.

World-Check One

• World-Check One API URL. Select the address of the World-Check One API, by default, https://api-worldcheck.refinitiv.com.
• World-Check One Group. Specify the Group Id for the World-Check One system.
• World-Check One Credentials Location. Specify the corresponding Secret Vault alias for the World-Check One system.
• Article Language. Select the language of articles to search in. ‘English’ language is used by default.
• Number of articles to extract. Specify the maximum number of reports to fetch from 1 to 100. By default, up to 20 articles are retrieved.
• Search Time period. Select an option to find information published during a specific time frame.

Configure keywords

In the Prepare your use case box, on the Keywords tab, specify keywords to be used for search. You can add a maximum of 28 words.

The following keywords are added by default:

• English:

  ACCUSE, ARREST, BRIBE, CONVICT, CORRUPT, COUNTERFEIT, CRIME, EMBEZZLEMENT, FRAUD, GUILT, ILLEGAL, INDICTMENT, INVESTIGATION, KICKBACK, MONEY LAUNDERING, NARCOTIC, PENALTY, SANCTION, SENTENCED, EVASION, TERRORIST, THEFT, TRAFFICKING, VIOLATION

• Spanish:

  ACUSAR, ARRESTAR, SOBORNO, CORRUPTO, FALSIFICACIÓN, CRIMEN, MALVERSACIÓN, FRAUDE, CULPA, ILEGAL, ACUSACIÓN, INVESTIGACIÓN, CONTRAGOLPE, LAVADO DE DINERO, NARCÓTICO, MULTA, SANCIÓN, SENTENCIADO, EVASIÓN, TERRORISTA, ROBO, TRÁFICO, VIOLACIÓN

info

For the World-Check One provider, the keywords highlight important sections within each article returned by the search, but not for the API call. You must configure keywords to be used in a search at the World-Check One’s website.

Configure high-risk countries

Select countries from the dropdown or enter thier names in the search field. The high-risk countries configured here are highlighted in articles returned from each investigation.

Configure output

In the Prepare your use case box, on the Output tab, specify the following parameters of the report for a screening request:

• Enable Manual Review. Select Yes to enable Manual Review Step.
• Format. Select the file format of the report for a screening request to be generated: HTML or PDF.
• Delivery. Select the delivery method in which the report is sent after generation. By default, Object storage.
• Object Storage. Specify the secured storage location for saving the report after generating it. By default, S3 location.

Configure data purge

The Data Purge Business Process is an additional part of Adverse Media Monitoring AI Digital Worker that allows to clean up old data on the environment.

Configure Data Purge settings

To configure Data Purge settings, do the following:

1. Log in to the Control Tower.

2. Click the Advanced tab and select Data Stores.

3. Select uc_amm_configuration_v1 and set the following parameters:

   Name	Value	Example	Description
   dataPurge.storagePeriodInDays	Integer	30	How many days should pass after the completion of the transaction to delete the data
   dataPurge.deleteReports	true/false	false	Set to "true" to delete generated reports
   dataPurge.deleteAnalyticsData	true/false	false	Set to "true" to delete analytics data

Configure Data Purge scheduling

You can run the Data Purge BP manually or on a schedule.

To configure the schedule, do the following:

1. Log in to Control Tower.

2. Go to the Advanced tab and select Schedules.

3. Click Create.

4. On the Create Schedule window, select the following parameters:

   • In Task or Process Definition, select "Adverse Media Monitoring Data Purge vX.X.X | AMM | X.X.X".
   • In Input Data, select “Empty”.
   • Specify Schedule Period to run Data Purge only for some period. Otherwise, leave it empty.
   • In Schedule Name, set the operation's name, for example, "Adverse Media Monitoring Data Purge".
   • In Schedule Frequency, specify days and times when Data Purge must be started. It is recommended to set the time when the environment is least loaded, for example, nightly hours on weekends.

   

5. Click Save.

After that, the purge operation runs automatically on a specified day and time.

To learn more about data clearing, see the following sections on Purge in the Enterprise Edition documentation:

• Overview
• Configure and run
• API

Review settings

Once you complete the required fields, review the configuration. If everything looks correct, click Finish. You are now ready to use the Adverse Media Monitoring skill.

Verify installation

To check that the Business Process is imported correctly, perform the following steps:

1. Log in to Control Tower.

2. Click Use Cases > View All. The list of use case groups appears.

   

   Find the Evelyn: Adverse Media Monitoring on this list.

3. Click this Business Process to open, go to the Data tab, and click Upload Data. The Upload your main data window appears.

   

4. In the window, click Add, select the CSV input file, click Open, and then click Upload. The data is uploaded to the Business Process.

5. Run the Business Process. Wait for the execution to reach the Manual task 'YYY'.

6. Log in to Workspace and open the earlier Manual task.

7. On the right side, under the 'Would articles trigger additional investigation?' answer, select Yes, and submit the Manual task.

   

   The Business Process will be completed in a minute.

8. Go back to Control Tower, and in the Business Process, see Event log. Ensure that there are no errors reported.

   

9. In the html_report_link or pdf_report_link columns, click the link to open the evidence report and ensure that it is not empty.