Frameworx Home

Application Framework (TAM)

Business Process Framework (eTOM)

Business Process Framework Flows

Information Framework (SID)

Business Metrics High Level

All Diagrams

Frameworx Processes

Frameworx Applications

Information Framework ABEs

Frameworx Metrics

Views

Frameworx Process: Information and Data Processing

Category: (4) eTOM Process Type

Process Identifier: 1.7.2.3.2.1

Original Process Identifier: 1.3.2.3.2.1

Maturity Level: 4

Description

This process is the ongoing processing of information and data against rules designed to detect threats, and the subsequent alerts and alarms resulting from rule violations and other detection processes.

Extended Description

Fraud operations in general should be receiving data almost continuously, and analysis of the received data should take place without delay where possible. Earlier processing and/or analysis of datasets enables not only more rapid detection of fraud, but also the subsequent ability to take meaningful action to stop fraudulent activities before (any) damage is incurred by the business. There are 3 primary functional areas within this process to address and define: 1. Rule Processing: During rule processing activities, information and data is passed through rules either through automated (technology-based) means or other manual processes. Depending on the volume of data and the complexity of the rules (interdependencies, aggregated or weighted triggering, etc.), increasing levels of technology will be necessary to quickly implement rules against data and determine the results. 2. Alert Generation: Configuration of alerts. Alerts may be generated when certain expected conditions are not met, including missing dataset delivery, failure to act on investigation requests (escalations), etc. Alerts may also be issued when certain conditions are exceeded, including excessive alarm quantities resulting from “loose” rules producing false positive results. 3. Alarm Generation: Configuration of alarms. Alarms are typically the result of detected events or activities that are suspicious and should be investigated as possible fraud. Alarms may be the result of single rule violations, or of multiple rule violations that contribute to weighted levels of suspicion (more complex scenario) etc. Other functions may also include the configuration of supplementary reports for scenarios not configured through rules and alarms as listed above. The configuration of rules, alerts, and alarms should be governed by policies as described in the 1.1.x processes for Fraud Management. Additionally, the procedures that should be followed as a result of the issuance of an alert or alarm should be governed by policies as described within the 1.1.x processes for Fraud Management.

Explanatory

Reserved for future use.

Mandatory

Reserved for future use.

Optional

Reserved for future use.

Interactions

Candidate Explanatory

Candidate Mandatory

Reserved for future use.

Candidate Optional

Reserved for future use.

Candidate Interactions

Reserved for future use.

(4) eTOM Process Type Information and Data Processing

Appears on these diagrams:

Issues

  • Business Process Framework 14.5 Addition
  • Business Process Framework 15.0 Modification
  • Business Process Framework 15.5 Modification

This was created from the Frameworx 16.0 Model


Created from the TM Forum Model Frameworx 16.0.0 on 6/13/2016 at 22:23