Professional Documents
Culture Documents
T3AAC - R15 1
The AA module provides a flexible framework that allows a number of products
to be created. It has the ability to allow user to construct banking products by
combining different business components through AA Product Builder. To create
a product, we will be using various product components such as Property
classes, properties and product conditions. Temenos has defined broad Product
Lines. We can create a product group under a product line. From a product
group, products can be designed as stand-alone products or as inheritance
products in a product family. The link between a product and an arrangement
will also be covered, checking out various activities in an arrangement.
AA also provides for simulating activities for “what-if” speculation for new and
existing product instances without creating or affecting live records.
5
Till Arrangement architecture came into T24, each T24 module - AC, MG, LD,
MM, AZ etc. had a purpose built silo. Functionality and product features exist
within these silos. Each module has different product definitions and
parameters.
Under Account module , we have different types of accounts, such as Current
Accounts, Savings Accounts, Overdraft Accounts and various parameter tables.
Similarly under LD module, we have deposits and lending functionality, with its
own parameter tables. Each of the T24 Product modules have their own
parameter tables, transaction tables and processing logic.
Even to service a single product, multiple modules have to be implemented.
Local Developments for simple things like Availability of a product was
inevitable. Customisation involved additional local developments as per the
client’s requirements.
6
The AA module provides a flexible framework that allows a number of new T24
modules to be created. The application provides a business component based
architecture for the management of products. Using AA, we will be moving to a
modular Product architecture, whereby clients can create their own Products by
using the Components provided by Temenos, and these components can be
reused across many Products.
8
Product design and servicing are enterprise level functions. Functionality is
encapsulated in a set of common product components. Each component has its
own attributes and actions defined by Temenos.
Within each product group, there are further subdivisions based on various
factors. For instance, the first subdivision is based on the body style of the car
such as a saloon, coupe or touring. This classification creates Product
Derivatives.
Similarly it has Actions or Functions like Start, Stop, etc. across different
Products.
In our example, the Wheel Component of vehicles are compared with the
Interest Component of Banking Products. Similar to other Components of
Vehicles viz. Transmission, Engine, Body, etc. we can think about the
Components Payment schedule, Charges, Term Amount (Period plus Principal)
of Banking Products.
In AA, the Attributes and Actions of Components are defined for every Property
Class.
For example, in case of a Car, the component Wheel has two instances Front
Wheel and Rear Wheel. Both of them viewed as the Component Wheel will
have same Attributes like Radius, Type, etc. but the values of these Attributes
might be different in case of Front and Rear Wheels. Similarly in case of a
Banking product, for example, in a Lending Product, there could be a
requirement to have two types of Interest viz. Principal Interest and Penalty
Interest.
In this case both belong to the Property Class Interest. But they could have
different values for the Attributes like Rate, Type, etc. These named types or
instances of a Property Class are termed as a Property in AA.
In AA, while Client can create new Properties based on Property Classes,
Property Classes themselves can be created only by Temenos.
Further, under the Interest Property Class, we have two Properties - Principal
Interest and Penalty Interest. Under the Account Property Class we have only
one Property, Account.
In the above example there are three Product Conditions for Term Amount
Property class. You can learn in detail about the Property Classes used here in
the AA-Lending course. The Property Commitment has been attached to the
Property Class Term Amount at the Product Group level.
One of the Product Conditions (25 yr Mortgage) of Term Amount Property Class
is attached to the Property Commitment at Product Level.
With the car analogy, the engine cannot be modified, the wheels can optionally
be modified, and the colour must be chosen. This means that while the engine
cannot be negotiated, the wheels and colour can be negotiated.
From product line, we move to product groups which are built through
AA.PRODUCT.GROUP. These can be built by Clients.
The property classes also have been pre defined for each of the Product Lines.
Thus, they get the basic attributes of the product line.
Property classes are pre defined by Temenos. The classes are like Interest,
General Charge etc. However every property class may have one or more
distinct properties. These are user definable. Under interest, user can define a
fixed interest or floating interest with or without margin as different properties
and pick what is needed for a particular product.
The components are reusable and can be used across several Products.
Term Amount property class has attributes CCY, Dated and Non-Tracking. The
product condition of this property has currency as part of its record Id. When the
product is to be made available in say, 4 different currencies, product
conditions have to be created in all of these 4 currencies. This also indicates
that the product condition will have date as part of its record Id and being
marked as Non Tracking, this property cannot be tracked.
Balance prefix is CUR & TOT for Lending product Line and TOT for Deposits
product line. This indicates that this property needs to have balance types
defined before using them in our Product Group and Product. Term amount
property class does not apply to Accounts Product Line, while Customer is
mandatory for all financial product lines.
For each Product Condition you can create different dated records
For each Property class a separate application is created with the name
AA.PRD.DES.<Property class name>.
This allows you to set up any changes to Product Conditions in advance, and
when Product using the conditions has been re-published, they will
automatically switch over to the new condition on the effective date.
When you do not specify a date in the Id of a Product Condition, date part of
the Id defaults to the today’s system date.
Default Values
You can see there are different fields like Amount, Term, etc. which are the
attributes of the TERM.AMOUNT Property Class. Here, we have defined a
value of “25Y” for Term and “No” for Revolving. When this Product Condition
is attached to a Property (of the TERM.AMOUNT class) in a Product, these
values will be defaulted in an Arrangement created for the Product.
Negotiation Rules
We will learn about this tab in the later part of this course.
Must be a valid attribute of the Property Class. In this example, where the
Product Condition is set for the TERM.AMOUNT Property Class, it should be a
valid attribute name of the TERM.AMOUNT Property Class.
This is the value(s) to compare against the value input in the Arrangement.
NR.MESSAGE
Specifies whether to raise an error or override message when the rule is broken
at the Arrangement level.
The top level default attribute option can be modified at attribute level
using the drop down in NR.OPTIONS
For each Periodic Attribute Class we have some predefined Periodic Attribute.
The screen here shows the Product Hierarchy in AA and what they are about at
each level.
The proofing and publishing process can be done either “Online” or by running
a “Service” in the AA.PRODUCT.MANAGER application. If ONLINE is
chosen, system would proof the product immediately. If SERVICE is chosen, the
main product (from which the publishing is triggered) is written on to a LIST
file AA.PUBLISH.SERVICE.LIST for indicating whether it is a
PROOF/PUBLISH initiation. A Service would be introduced –
AA.PUBLISH.SERVICE (from TSA.SERVICE, ) – which would process this
list file. The service would publish products hierarchy-wise. This ensures that a
child would not accidentally get published before the parent has been
processed.
Another one is the Expiry Date, from which the Product will cease to exist and
no Arrangements can be input for the Product. However, existing Arrangements
for the Product will continue.
PRODUCT.ERROR Field displays the errors caused when Proofing fails.
SUGGESTION Field displays suggestions for rectifications of errors.
Now search for your deposit arrangement using the secondary customer you
have added in the arrangement
From R16,
When the property is suspended the accruals are posted to the balance types
suffixed with a “SP” instead of PL.
Arrangements can only be updated via Activity (both online and COB)
Defined by Temenos
In AA, Activities are associated with Properties. A crucial point to note is that,
few activities like ‘Create New’ , ‘View arrangement’, ‘Takeover activity’ acts
on the arrangement (not the property). This is the only exception to the rule.
Properties can have multiple activities associated with them. The Activities
associated with the Commitment Property (of TERM.AMOUNT Class) include
disburse funds, increase committed amount, change term, etc.
We define another term, the “Process”, which represents what is actually being
done by the activity.
Here the process DISBURSE related to LENDING Product Line acts on the
Property: COMMITMENT and the Activity is LENDING-DISBURSE-
COMMITMENT i.e. The amount of the loan is disbursed.
The Can Prop Class, Can Action and Can user input indicates the actions that
would be reversed when the activity is reversed and if user intervention is
required for the same.
They can be run directly from the Arrangement Overview for changing terms
and conditions like the loan term, interest changes, basically changing any of the
product conditions for the loan.
They can be run indirectly via a transaction. These are typically the financial
activities, disbursements, payments, etc which affect balances.
They can be run as part of COB (Close of Business). This includes interest
accruals, bill processing, etc.
This works through a mapping between the T24 transactions and the AA
Activities. Depending on the transaction code you enter, it will know which AA
activity you intend to run. You will learn how to configure these in the AA
business course.
Do you know why some activities are reversed and why some are not reversed.
Can you recollect and explain why the Accruals are not seen in Activity history
and they are not reversed and replayed.
Also can you see the effective accrual amount is changed in interest is correct
even without reversal and replay.
Simulation runner is used to define the period of simulation and list of activities
to be simulated. This runs the data captured through the Simulation data capture.
Before simulating an activity, Simulation service has to be started.
The simulated Arrangement can be executed and bought to live status using the
execute icon indicated.
After giving a meaningful name and description for the catalog being built, We
define the criteria as minimum and maximum amount from COMMITMENT
property with negotiation attributes as minimum and maximum. Similarly for
the Term with minimum and maximum attribute from same property
Interest is to be pulled out from the AA.STANDARD.FIELD.TYPE by
indicating in SOURCE.TYPE