4.8 Overview of OFSAA Rules

OFS Analytical Application models are constructed using combinations of OFSAA rules. For example:

• An Allocation rule might utilize a Hierarchy Filter rule, an Expression rule, and a Static Table Driver rule
• A Transfer Pricing rule might utilize a Hierarchy rule, a Data Element Filter rule, and a Prepay­ment rule
• A Data Element Filter rule might utilize an Expression rule
• A Group Filter rule always incorporates one or more underlying Data Element Filter rules
• Hierarchy Filter rules always utilize an underlying Hierarchy rule

The advantage of constructing models from discrete rule components is that individual rules may be re-used dozens or even hundreds of times. For example, if you wish to build a large series of allocation rules which operate on non-interest expense data in the Western region, you may build filters for (1) non-interest expense and (2) the Western region and then utilize these filters in every allocation rule. As another example, if you wanted to assign the same transfer pricing method and assumptions to all mortgage products, you could build a Hierarchy on the product dimension containing a Mortgage Products rollup point and assign your method and assumptions at the rollup level. You could subse­quently utilize the same Hierarchy rule for allocation processing or reporting purposes.

Many rule types are specific to individual analytical applications (For example, Transfer Pricing rules, Cash Flow Engine rules, Allocation rules, and so on.) while OFSAA Infrastructure rules are shared across all OFS applications. Rule types that are shared across all applications include:

• Hierarchies
• Hierarchy Filters
• Data Element Filters
• Group Filters

Dimensions, dimension members, attributes, and currency exchange rates are also shared across all applications.