Types of components

A component that is triggered by the absence of a specific activity preceding a specific activity.

A behavior that is defined by recognizing the occurrence of a specific event and then looking back in time (a defined time period) to see whether another specific event has occurred. The Backward Inactivity component fires if the event being “looked for” did not occur.

Example: Trigger an event if event A happens and event B did not happen in the specified prior time frame.

Example: Trigger an event when a customer makes use of the ATM after more than 1 month of not using any teller services.

Also known as Backward Looking Inactivity and BLI.

Container Manipulator

Can trigger actions

A definition of a process used to manipulate the data in containers. Add, delete, and manipulate contents of Containers. Can trigger events based on the content of Containers. Do clauses include: insert, delete, and soft insert.

Example: When the dollar amount of product a customer purchased in one month exceeds $200 (value in the container), offer a discount.

Forward Inactivity

Can trigger actions

A component that is triggered by the absence of usual activity. A behavior that is defined by recognizing the occurrence of a specified event and waiting a specified time to see whether or not another specified event occurs. The Forward Inactivity component fires when the time period expires without the occurrence of the event it for which it was waiting.

Example: Trigger when a web-trade customer, who usually trades once a month, does not trade for two consecutive months.

Example: Trigger an event if event A happens and event B does not happen in the time frame specified in the future.

Also known as Forward Looking Inactivity and FLI.

Pattern

Can trigger actions

A group of events occurring within a defined time frame.

Example: Trigger when customer uses his credit card four times a month during a three month period and is a platinum card holder.

Simple

Can trigger actions

A defined set of business-relevant conditions that recognize certain attributes in a particular transaction. Trigger an event if the specified conditions are satisfied.

Example: Credit card purchase over $5000 or an international phone call to Italy

Action

Writes outcomes to the Outcome database

A component that triggers an outcome message (to the external system) based on criteria being met on a trigger system. Defined pieces of data (customer#, time, reason to contact) that are written to the Outcome database when a specified event occurs.

Could represent a recommendation to contact a customer due to a pattern of behavior.

Example: Send coupon for free 10 minute international call when customers who have GOLD status complete 15 international phone calls in one month.

Join Function

Returns results from an operation on a database table

A definition of a process that joins two record-set objects. It returns another record set whose type structure has been pre-defined using the Type Descriptor.

Example: Join the container holding customer purchases including store number with the look-up table containing information about all stores which contains store numbers and regions in order to determine the region of each customer purchase in the container

Example: Join the container holding stock trades including the stock CUSIP number with the look-up table containing information about all stocks which contains CUSIP numbers and industry sectors in order to determine the industry sector of each stock purchase in the container

Example: Join the banking product code on an incoming transaction to a container containing all products the customer has. If the result contains a line in the join, then the customer has this product. If it contains no lines then the customer does not have the product, and hence this transaction represents a new product for this customer.

Select Function

Returns results from an operation on a database table

A definition of a process that reduces the information in a table according to some specified criteria.

Math

Used internally by other components

A defined mathematical formula that calculates a numeric result based on numeric data from one or more data sources and can be used in Simple Event components to refine the event which must occur.

Example: Credit card purchase over $5000 (Simple Event component) where the purchase amount is 95% of the available account balance (refining mathematical formula.)

Container

Used internally by other components

An area used to store data from transactions or a profile. Holds data that can be collected, used in calculations, and tested by a Container Manipulator.

Example: Save the dollar amount of products a customer purchased in one month.

Qualifier

Used internally by other components

Customer attributes that help define the selection criteria of whether the component should trigger or not. A defined set of customer characteristics that reveal a quality about the customer as opposed to recognizing the behavior of that customer.

Qualifier components act as filters, refining the firing of Simple Event components and Action components to those customers who posses the defined quality.

Example: GOLD customer is part of the action component described at the beginning of this table, and is a Qualifier.

Trend

Used internally by other components

component that simplifies the system’s ability to detect trends and unusual transactions. It can detects trends, significant spike transactions, or transactions that exceed standard deviations.

Examples: The average monthly balance has been increasing by 10% over the last six months, a deposit is 25% larger than any other deposit made in the last 6 months, or a balance that is more than two standard deviations above the monthly average for the past year.

Component Type	General Function	Description
Backward Inactivity	Can trigger actions	A component that is triggered by the absence of a specific activity preceding a specific activity. A behavior that is defined by recognizing the occurrence of a specific event and then looking back in time (a defined time period) to see whether another specific event has occurred. The Backward Inactivity component fires if the event being “looked for” did not occur. Example: Trigger an event if event A happens and event B did not happen in the specified prior time frame. Example: Trigger an event when a customer makes use of the ATM after more than 1 month of not using any teller services. Also known as Backward Looking Inactivity and BLI.
Container Manipulator	Can trigger actions	A definition of a process used to manipulate the data in containers. Add, delete, and manipulate contents of Containers. Can trigger events based on the content of Containers. Do clauses include: insert, delete, and soft insert. Example: When the dollar amount of product a customer purchased in one month exceeds $200 (value in the container), offer a discount.
Forward Inactivity	Can trigger actions	A component that is triggered by the absence of usual activity. A behavior that is defined by recognizing the occurrence of a specified event and waiting a specified time to see whether or not another specified event occurs. The Forward Inactivity component fires when the time period expires without the occurrence of the event it for which it was waiting. Example: Trigger when a web-trade customer, who usually trades once a month, does not trade for two consecutive months. Example: Trigger an event if event A happens and event B does not happen in the time frame specified in the future. Also known as Forward Looking Inactivity and FLI.
Pattern	Can trigger actions	A group of events occurring within a defined time frame. Example: Trigger when customer uses his credit card four times a month during a three month period and is a platinum card holder.
Simple	Can trigger actions	A defined set of business-relevant conditions that recognize certain attributes in a particular transaction. Trigger an event if the specified conditions are satisfied. Example: Credit card purchase over $5000 or an international phone call to Italy
Action	Writes outcomes to the Outcome database	A component that triggers an outcome message (to the external system) based on criteria being met on a trigger system. Defined pieces of data (customer#, time, reason to contact) that are written to the Outcome database when a specified event occurs. Could represent a recommendation to contact a customer due to a pattern of behavior. Example: Send coupon for free 10 minute international call when customers who have GOLD status complete 15 international phone calls in one month.
Join Function	Returns results from an operation on a database table	A definition of a process that joins two record-set objects. It returns another record set whose type structure has been pre-defined using the Type Descriptor. Example: Join the container holding customer purchases including store number with the look-up table containing information about all stores which contains store numbers and regions in order to determine the region of each customer purchase in the container Example: Join the container holding stock trades including the stock CUSIP number with the look-up table containing information about all stocks which contains CUSIP numbers and industry sectors in order to determine the industry sector of each stock purchase in the container Example: Join the banking product code on an incoming transaction to a container containing all products the customer has. If the result contains a line in the join, then the customer has this product. If it contains no lines then the customer does not have the product, and hence this transaction represents a new product for this customer.
Select Function	Returns results from an operation on a database table	A definition of a process that reduces the information in a table according to some specified criteria.
Math	Used internally by other components	A defined mathematical formula that calculates a numeric result based on numeric data from one or more data sources and can be used in Simple Event components to refine the event which must occur. Example: Credit card purchase over $5000 (Simple Event component) where the purchase amount is 95% of the available account balance (refining mathematical formula.)
Container	Used internally by other components	An area used to store data from transactions or a profile. Holds data that can be collected, used in calculations, and tested by a Container Manipulator. Example: Save the dollar amount of products a customer purchased in one month.
Qualifier	Used internally by other components	Customer attributes that help define the selection criteria of whether the component should trigger or not. A defined set of customer characteristics that reveal a quality about the customer as opposed to recognizing the behavior of that customer. Qualifier components act as filters, refining the firing of Simple Event components and Action components to those customers who posses the defined quality. Example: GOLD customer is part of the action component described at the beginning of this table, and is a Qualifier.
Trend	Used internally by other components	component that simplifies the system’s ability to detect trends and unusual transactions. It can detects trends, significant spike transactions, or transactions that exceed standard deviations. Examples: The average monthly balance has been increasing by 10% over the last six months, a deposit is 25% larger than any other deposit made in the last 6 months, or a balance that is more than two standard deviations above the monthly average for the past year.