Skip to main content
Version: 3.4.2

Analyze effectiveness

Tara uses prebuilt analytics dashboards to monitor the automation solution and specific metrics for actionable insights into a Business Process (BP).

Dashboards​

To view Tara dashboards, go to Control Tower > Analytics > Dashboards > Payment sanction screening overview.

note

The Payment sanction screening overview dashboard calculates metrics for finished transactions only. Thus, not all transactions are considered on the dashboard during the BP execution.

The out-of-the-box analytics includes the following business metrics:

  • Alerts
  • Hits
  • Avg hits per alert
  • Alerts trend
  • Hits trend
  • Avg hits per alert trend
  • Alert automation rate
  • Hit automation rate
  • Avg time spent
  • Alert automation trend
  • Hit automation trend
  • Avg time spent (in sec)
  • True positive (hits)
  • False positive (hits)
  • Missed false positive (hits)
  • Missed true positive (hits)
  • Hits trends
  • True positive (alerts)
  • False positive (alerts)
  • Missed false positive (alerts)
  • Missed true positive (alerts)
  • Alerts trends
  • Content format analysis
  • Entity type analysis
  • Tagname analysis (Top 10)
  • Hit decision code distribution

info
  • True Positive: both the gold decision and the AI Agent's decision are NO_DECISION.
  • Missed True Positive: the gold decision is NO_DECISION, but the AI Agent's decision is RESOLVE.
  • False Positive: both the gold decision and the AI Agent's decision are RESOLVE.
  • Missed False Positive: the gold decision is RESOLVE, but the AI Agent's decision is NO_DECISION. The automation rate is calculated as the number of false positives divided by the sum of missed false positives and false positives, provided that gold values are available. Otherwise, it is calculated as the count of RESOLVE divided by the total number of cases.

Data Stores​

Alert-level analytics Data Store​

The pss_messages_analytics_v1 Data Store contains alert-level analytics data.

The available columns are as follows:

  • campaignId: unique identifier of the BP installation
  • runUuid: unique identifier of the BP execution
  • transactionId: unique identifier of a request
  • clientId: client executing BP
  • messageId: identifier of an incoming alert
  • messageType: type of an incoming alert
  • alertsCount: number of hits in the alert
  • msgDecision: alert decision as a JSON string
  • msgReviewDecision: alert gold decision as a JSON string
  • reportLink: generated link of an HTML report
  • lastModified: timestamp indicating when a record was last modified
  • msgFilteredOut: flag if alert was filtered out
  • msgDecisionReapplied: flag if a decision on the alert was made by decision reapplication
  • modelId: decision model identifier
  • nerModelId: Named Entity Recognition (NER) model identifier
  • request_insert_time: timestamp indicating when a record was received
  • status: completion status of a record
  • tara_version: Tara version used during request execution
  • message_subtype: value from the message subtype field

Hit-level analytics Data Store​

The pss_alerts_analytics_v1 Data Store contains alert-level analytics data.

The available columns are as follows:

  • campaignUuid: unique identifier of the BP installation
  • runUuid: unique identifier of the BP execution
  • transactionId: unique identifier of a request
  • clientId: client executing BP
  • messageId: identifier of an incoming alert
  • alertId: identifier of an incoming hit
  • entityType: type of a screened entity
  • alertDecision: final hit decision
  • alertDecisionCode: hit decision code or a name of the rule executed to make a decision
  • alertDecisionDescription: hit decision description; currently, the same as the code
  • alertDecisionExplanation: hit decision explanation, a verbal detailed explanation of the code
  • alertReviewDecision: gold hit decision
  • lastModified: timestamp indicating when a record was last modified
  • filteredOut: flag if a hit was filtered out
  • decisionReapplied: flag if a decision on the hit was made by continuous learning
  • modelId: decision model identifier
  • nerModelId: NER model identifier
  • contentFormat: message content format
  • tagName: name of the tag where the hit occurred

Enrichment data analytics Data Store​

The pss_de_analytics_v1 Data Store contains enrichment data analytics.

The available columns are as follows:

  • type: enrichment data provider
  • time: call execution time
  • message_id: identifier of an incoming alert
  • num_hits: total number of hits in an alert
  • num_hits_searched: number of hits that executed the call
  • num_hits_decision_changed: number of hits for which the decision was changed because of the call
tip

Also, see View CLDS Data Stores.

Last updated on