TEMENOS T24

AM Dynamic Modelling

User Guide

Information in this document is subject to change without notice.

No part of this document may be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without the express written permission of TEMENOS Holdings NV.

Copyright 2005 TEMENOS Holdings NV. All rights reserved.

AM Dynamic Modelling

Table of Contents
Overview .................................................................................................................................................. 4
Setup ....................................................................................................................................................... 6
T24 Dynamic Model ............................................................................................................................. 7
Configuration Diagrams ....................................................................................................................... 9
New Model Process ......................................................................................................................... 9
Amend Model Process ................................................................................................................... 10
AM.PARAMETER .............................................................................................................................. 10
COMPANY ......................................................................................................................................... 11
AUTO.ID.START................................................................................................................................ 12
AM.VIRTUAL.CUSTOMER ................................................................................................................ 13
SC.PARAMETER............................................................................................................................... 14
TSA.SERVICE records ...................................................................................................................... 14
Deal/Transaction processing ................................................................................................................. 15
AM.DYNAMIC.MODEL ...................................................................................................................... 15
Model Input ..................................................................................................................................... 15
Copy of a Model ............................................................................................................................. 21
Integrity Check ............................................................................................................................... 25
Status summary ............................................................................................................................. 26
Performance ...................................................................................................................................... 34
Enquiry AM.DYNAMIC.MODEL.PERF........................................................................................... 35
Performance Adjustment ................................................................................................................ 37
Archiving ............................................................................................................................................ 41
Archiving Example 1....................................................................................................................... 42
Archiving Example 2....................................................................................................................... 43
Restructuring of the Model Portfolio .................................................................................................. 45
Buy/Sell Mechanism .......................................................................................................................... 47
Cash Position Adjustment of Virtual Accounts .................................................................................. 48
Back Valuation ................................................................................................................................... 49
Enquiries ................................................................................................................................................ 58
AM Dynamic Model Maintenance ...................................................................................................... 59
EDIT ............................................................................................................................................... 61
NEW ............................................................................................................................................... 63
DEACTIVATE ................................................................................................................................. 64
DUPLICATE ................................................................................................................................... 65
TIMELINE ....................................................................................................................................... 66
STATUS ......................................................................................................................................... 67

TEMENOS T24 User Guide Page 2 of 75

AM Dynamic Modelling

REVIEW MODEL BUILD ................................................................................................................ 68

VIEW HIERARCHY ........................................................................................................................ 69
UP................................................................................................................................................... 70
DOWN ............................................................................................................................................ 71
AM Dynamic Model Timeline ............................................................................................................. 72
AM Dynamic Model Integrity Status ................................................................................................... 73
AM Dynamic Model Rebuild Review .................................................................................................. 74

TEMENOS T24 User Guide Page 3 of 75

AM Dynamic Modelling

Overview

T24 Static Modelling provides models in the sense that asset weights once defined in a strategy or
model portfolio are assumed to be constant. Conversely in T24 Dynamic Modelling, for each position
the nominal is fixed which implies that the asset weights change depending on the valuation prices.
Table below provides an example of a dynamic model with four shares. On January 31st the nominal
for each of the four stocks has been selected so that each position is allocated 25% of the portfolio’s
value. Valuation price changes make the allocation drift through time from the initial allowance.
When position nominals are kept constant over a time period, stocks with lower performance lose their
allocation share while stocks performing above average increase their valuation share. It also displays
the evolution of the allocation over time.
A portfolio kept with constant position nominal behaves the same way. Therefore, the goal of dynamic
models is to have models that display the same behaviour as portfolios. This is particularly useful for
portfolio rebalancing to ensure that all portfolios linked to the same model portfolio are tightly aligned
to the same allocation in such a way that they generate equivalent performance.
With static models, the percentage value allocation is fixed over the period thus implies rebalancing.
Common business practice tells that fixed allocations are appropriate for strategies while dynamic
models are more appropriate for the rebalancing of portfolios.
The reason why static allocations are appropriate for strategies is that in practice an asset class is
equated to a risk class. Under such an assumption constant allocations represent constant risk
exposure which is what the Banker usually promotes to his client.

Logitech Novartis Swisslog ABB

Nominal = 92 Nominal = 35.61 Nominal = 2322 Nominal = 179.86
Date Price Weight Price Weight Price Weight Price Weight
31-Jan-06 27.18 25.0% 70.20 25.0% 1.08 25.0% 13.90 25.0%
28-Feb-06 26.50 23.2% 70.60 23.9% 1.18 26.0% 15.70 26.9%
31-Mar-06 26.05 21.0% 72.50 22.6% 1.49 30.4% 16.45 25.9%
28-Apr-06 25.75 20.6% 71.15 22.0% 1.47 29.8% 17.70 27.7%
31-May-06 24.65 21.5% 67.55 22.8% 1.34 29.5% 15.40 26.2%
30-Jun-06 23.60 21.1% 66.20 22.9% 1.26 28.4% 15.90 27.7%
31-Jul-06 25.00 21.4% 69.90 23.2% 1.33 28.8% 15.90 26.6%
31-Aug-06 26.60 22.4% 70.25 22.9% 1.30 27.7% 16.35 27.0%
29-Sep-06 27.15 22.5% 73.00 23.4% 1.31 27.4% 16.45 26.7%
31-Oct-06 32.70 24.5% 75.50 21.9% 1.40 26.5% 18.50 27.1%
30-Nov-06 35.25 25.5% 69.85 19.6% 1.50 27.4% 19.35 27.4%
29-Dec-06 35.15 24.4% 70.25 18.9% 1.54 27.0% 21.85 29.7%

Example of a four stock allocation where each position is equally-weighted at the beginning of the period
(25%). Price changes during the period make the allocation deviate from the initial one.

TEMENOS T24 User Guide Page 4 of 75

AM Dynamic Modelling

Conversely, dynamic portfolio allocations tend to drift over time. The drift can be quite significant in
particular over long periods of time. Such a drift increases the exposure to asset classes that display
higher performance. Unfortunately, these are usually also those that bear the most risk.

T24 provides both static allocations and dynamic model portfolios so that the most appropriate type
can be selected depending on what is to be modelled. Unfortunately, dynamic model portfolios are
more complex to maintain for many reasons: first the models need to be maintained, second
valuations and corporate actions need to be applied daily.

35.0%
Logitech
33.0% Novartis
31.0% Swisslog
ABB
29.0%

27.0%

25.0%

23.0%

21.0%

19.0%

17.0%

15.0%
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec

Drift of the allocation over time due to valuation price changes.

TEMENOS T24 User Guide Page 5 of 75

AM Dynamic Modelling

Setup
The structure for dynamic model portfolios is a hierarchy. The dynamic model portfolio is at the top
level (the root). The entries of a dynamic model portfolio (DMP) can be either instruments or reusable
dynamic buckets (RDB). A dynamic bucket is a reusable container which is similar to a dynamic model
portfolio in the sense that it can contain as entries either other reusable buckets or securities. Note the
difference that the entries of a dynamic model cannot refer to other DMP’s while a RDB may refer to
other RDBs. However, a RDB should not refer either directly or indirectly to another RDB that already
refers to it thus forbidding any circular references. Furthermore it is not allowed for an RDB to be
referenced more than once within the hierarchy of a single DMP.
Typically, a model could be first segmented by Asset type, and then the Bonds segment would be
further segmented based on currencies. The Shares segment would as well be further segmented
according to country risk. The security level entries would only be attached to the second
segmentation level.
However, in practice, this flexibility is not used and the models always use a single breakdown level,
typically an Asset type axis with securities and/or RDB entries directly attached to the proper asset
type segment.
Figure 2 A typical structure where a DMP appears on the left side. The DMP refers to the RDB.

A typical structure showing a dynamic model portfolio referring to dynamic buckets. The first row of
each block displays its key.

TEMENOS T24 User Guide Page 6 of 75

AM Dynamic Modelling

Bucket: Global Bonds Hedged

Reference currency USD
Node description Sec ID Nominal Invested amount Absolute Relative
▼ Money Market Instrument 51,940.00 5.02%
● United States of America 1713442 50000.0000000 51,940.00 5.02% 100.00%
▼ Bonds and similar investments 982,607.83 94.98%
● Königreich Dänemark 86149 190000.0000000 193,297.66 18.68% 19.67%
● Royaume de Belgique 248738 195000.0000000 195,657.56 18.91% 19.91%
● Royaume de Belgique 526437 203000.0000000 202,792.86 19.60% 20.64%
● Oesterreich Republik 1036168 160000.0000000 157,315.89 15.21% 16.01%
● République Française 1545229 230000.0000000 233,543.86 22.57% 23.77%
Total 1,034,547.83
Typical display for a dynamic bucket.

T24 Dynamic Model

Dynamic Modelling extends the existing modelling functionality within T24, by allowing the users to
construct dynamic models where the weighting can be amended as requirements change. These
dynamic models can then be used to create virtual portfolios, which in turn is used to create
investment strategies against which rebalancing can take place.
The AM.VIRTUAL.CUSTOMER application is used to define virtual customers. Portfolios created
against these customers will, by definition, be virtual. Normal trading activities should not be
processed against this portfolio or accounts linked to it.
The AM.DYNAMIC.MODEL application allows the specification of a dynamic model (linked to a
virtual portfolio) by building up related ‘nodes’ which point to sub-nodes and/or securities with a given
weighting. A hierarchy of these ‘nodes’ defines a single model.
The system holds this data per node per day and automatically copies valid nodes during close of
business processing so that they are all then carried through to the next working day. The
AM.DYNAMIC.MODEL.COPY application provides functionality to copy nodes or a collection of
nodes manually to different dates as required.
The enquiry AM.DYN.MODEL will provide an entry point into input and maintenance of dynamic models.
The AM.MODEL.PORT.REBUILD service will run automatically when a dynamic model has been
created or amended. This service produces details of recommended purchases or sales of securities.
These are then viewed, amended as required and processed within the enquiry
AM.DYN.MODEL.PORT.REVIEW.
The existing AM.BUILD.MODEL application is used to generate/regenerate the axis/matrix for the
investment strategy that the model represents.
Finally, the existing AM.COMPARE functionality is used to rebalance customer portfolios attached to
an investment program where the matrix defined is that of the dynamic model.
The rebalancing engine (along with Cash Management and the Dynamic Model generation software)
include the ability to round the proposed nominal amounts to a valid trading unit. Therefore where the
Portfolio positions are out of bounds according to the model, are rebalanced to the target, the nominal
of the generated deals is rounded to the defined rounding lot.
A rounding type of UP, DOWN or CLOSER determines the rounding behaviour as follows: -

TEMENOS T24 User Guide Page 7 of 75

AM Dynamic Modelling

• UP: The nominal is to be rounded to the closest round lot above the target
• DOWN: The nominal is to be rounded to the closest round lot below the target
• CLOSER: The nominal is to be rounded up or down to the closest rounding lot depending on
whichever is closest to the target
This is configured at in a central parameter file (AM.PARAMETER field ROUNDING.TYPE) and also
at rebalancing request level (AM.COMPARE field ROUNDING.TYPE).
Apart from the older versions created every time a change is made to a model, the model once it
passes its Validity date by the number of days specified in DYN.MODEL.LIFESPAN on the
AM.PARAMETER , the record is moved to the history file. Refer to Archiving Chapter

TEMENOS T24 User Guide Page 8 of 75

AM Dynamic Modelling

Configuration Diagrams
New Model Process

New Dynamic Model processing

TEMENOS T24 User Guide Page 9 of 75

AM Dynamic Modelling

Amend Model Process

Amendment of Dynamic Model processing

AM.PARAMETER
In order for the following functions to work, certain fields are to be set in AM.PARAMETER
For Archiving, the number of days DYN.MODEL.LIFESPAN needs to be defined to control how many
days a dynamic model record stays on the live file once it passes its validity date; This field also
controls how many days AM.MODEL.PORT.REBUILD.WRK records remain on the system before
they are deleted.

If this field is left blank or set to zero, the records remain indefinitely, and may at some stage cause
performance issues and need to be cleared by setting this parameter.

Furthermore, the field

OFS.SOURCE has to be defined to enable the processing of
AM.MODEL.PORT.REBUILD and subsequent trades generation.

TEMENOS T24 User Guide Page 10 of 75

AM Dynamic Modelling

AM.PARAMETER

Field Name Description

OFS.SOURCE Define the area to be used for the OFS processing for AM
SEC.TRF.VERSION Define the version of SECURITY.TRANSFER input to be used
VIRTUAL.BROKER Must be an AM.VIRTUAL.CUSTOMER of type BROKER in
CUSTOMER.SECURITY
VIRTUAL.DEPOSITORY Must be an AM.VIRTUAL.CUSTOMER of type DEPOSITORY in
CUSTOMER.SECURITY

COMPANY
In order to use automatically generated ids, the relevant COMPANY record(s) field PGM.AUTOM.ID
for AM.DYNAMIC.MODEL.COPY and AM.MODEL.PORT.REBUILD.WRK have to be defined.

COMPANY

TEMENOS T24 User Guide Page 11 of 75

AM Dynamic Modelling

AUTO.ID.START
For each process where auto generated id is required, the corresponding AUTO.ID.START record
needs to be defined.

AUTO.ID.START Record

TEMENOS T24 User Guide Page 12 of 75

AM Dynamic Modelling

AM.VIRTUAL.CUSTOMER
The virtual customers are defined within this application, so that data records and trading activities
created against these customers are treated by the system as virtual. It will only be possible to link
virtual portfolios (i.e. those belonging to virtual customers) against a dynamic model.

This record holds the portfolios and node names that are used for this customer.

AM.VIRTUAL.CUSTOMER

Field Name Description

VIRTUAL.CUSTOMER.ID This is the key to the table and must be a valid customer number
DESCRIPTION This requires up to 35 alphanumeric characters mandatory description
XX.SHORT.NAME This is a NOINPUT field short name obtained from the customer record
XX<PORTFOLIO.ID This NOINPUT field contains all the portfolios ids assigned to root nodes
XX>DYN..MODE.NAME This NOINPUT field contains all the node names for corresponding portfolios

For Virtual Accounting, 3 Virtual Customers (1 for the Portfolio on the root node, one broker, one
depo) need to be set up, as well as the SC.PARAMETER below

TEMENOS T24 User Guide Page 13 of 75

AM Dynamic Modelling

SC.PARAMETER

SC.PARAMETER

The fields VAL.APPL and USR.POS.RTN need to be set up as above.

TSA.SERVICE records

Service Description
.../AM.MODEL.BUY.SELL.SERVICE Buy Sell mechanism for dynamic models
This is the service associated with populating
the virtual portfolio for the dynamic model, it
will be triggered after
…/AM.DYNAMIC.MODEL.SERVICE has
completed.
…/AM.DYNAMIC.MODEL.SERVICE Dynamic Model Service
This service provides all of the validation and
processing required to maintain a dynamic
model and to ensure that it’s valid.

TEMENOS T24 User Guide Page 14 of 75

AM Dynamic Modelling

Deal/Transaction processing
AM.DYNAMIC.MODEL
The dynamic model is created specifying at least a root node, which must detail a virtual portfolio, and
any number of subordinate nodes. The records thus created are stamped with the system date and
are valid for that day.
AM.DYNAMIC.MODEL records contain references to specific securities or links to child nodes
against a specified segmentation scheme. Against each link or reference there is a weighting, either
in terms of a percentage of an arbitrary total value invested, held against the root node and expressed
in terms of the reference currency; or a specified nominal quantity for each security referenced. All
records linked to a root node must share the same reference currency and weighting method (i.e.
nominal or percentage of total invested).
Whenever these records are committed to the system, a background service validates the entire
model ensuring that the records are consistent with each other and constitute a proper hierarchy. This
hierarchy defines the dynamic model and allows for weightings or assignments against each segment
to be defined or amended independently of the whole model.

Model Input
A model is identified by its Node.Name with a date association ie Nodename*YYYYMMDD
e.g. DYNMOD*20030808

AM.DYNAMIC.MODEL Input

TEMENOS T24 User Guide Page 15 of 75

AM Dynamic Modelling

The input is initiated by calling AM.DYNAMIC.MODEL with any of the following

a. DYNMOD - ( today’s date with * separator is defaulted)
b. DYNMOD* - ( today’s date is defaulted)
c. DYNMOD*20030808 (ie Name*YYYYMMDD)
If the record exists, it can be edited or viewed, but not reversed, and should only be copied using
AM.DYNAMIC.MODEL.COPY which is described later.

On input the NODE.NAME and the VALIDITY.DATE are extracted from the Model Id, the START.DATE
is set to the date of input, and the MODEL.STATUS is set as To Be Validated.
Note the status after integrity checks (described later), is set accordingly. If it passes the integrity
checks, and the model has or is a root node, its status is set to Active. Else it is set to Inactive and
Root.node status is set to Error with reason given.

A description of what the model is trying to achieve can be input, along with the Reference Currency of
the model. This currency should be the same throughout the model hierarchy.
The model can be a Root node by selecting Yes for the ROOT.NODE , however it is advisable to create
all the Child nodes first followed by any Parent nodes then the Root node as the latter will insist on a
child node if a Node is specified for an ASSET.TYPE . Note that a child can have more than one
parent or root nodes, and a root node cannot be a child node.
When a root node is being created, a valid Sec.Acc.Master PORTFOLIO.ID needs to be input and
must be unique ie it does not exist in any other root nodes..
If a VALUE.TYPE of Percentage is selected then a PORTFOLIO.VALUE must be input as well,
however if Nominal is selected for VALUE.TYPE then no value is needed.
Nominal type models also have the facility to add a NOMINAL against ‘Node’ ASSET.TYPEs. This
acts as a multiplier for the nominal amounts held in the child node and any subsequent nodes in the
hierarchy. I.e. The Nominal amounts specified against securities are multiplied by the product of all
Nominal values recorded on the parent nodes in the hierarchy, in order to calculate the proposed
holding.

A model requires a valid Segment on the AM.SEGMENTS file, to be defined, as well as any of its
Segment Label that will be used.
Each segment may be split in one or more ASSET.TYPEs consisting of Security or Node, each will be
apportioned a weighting PCT.AST.ALOC together with UPPER.TOLERANCE and LOWER.TOLERANCE
if Percentage Value type was selected, with an overall total 100. However for a Nominal Value type,
the number of Nominal for the Security subject to its Trading Units is defined.

If an ASSET.TYPE of Security is used, then a valid security on the SECURITY.MASTER file needs to
be defined, the model and reference prices and rates are defaulted from the exchange rates and
security records.
If ASSET.TYPE is Node, then the Child Node with the same VALIDITY.DATE, VALUE.TYPE and
REFERENCE.CCY is required.

TEMENOS T24 User Guide Page 16 of 75

AM Dynamic Modelling

Example of an AM.SEGMENTS

Example of a SECURITY.MASTER

TEMENOS T24 User Guide Page 17 of 75

AM Dynamic Modelling

AM.DYNAMIC.MODEL using Segment and Security

The above example show an Active root node model Id DYNMOD*20030808 with the NODE.NAME
being the first part of the id - DYNMOD and the VALIDITY.DATE being the second part – 20030808
ie 08 AUG 2003.
The reference currency is USD and hence any child node if any, in the hierarchy must be USD as its
reference currency.
A Segment of ASSET of which the label STOCK has been selected, with a VALUE.TYPE of Nominal,
thus ensuring that when the Security 100040-000 is chosen, only a multiple of the Trading Units (250)
for this stock is input for the Nominal – 500.
The MODEL.PRICE of 98 is obtained from the LAST.PRICE of the Security record and as It is USD –
local ccy then the MODEL.RATE exchange rate is 1, this will stay unchanged while the REF.PRICE
and the REF.RATE are the corresponding price and rate at the validity date of the model.

Note the Model status is To Be Validated as it has not been Integrity Checked yet by the background
Program AM.DYNAMIC.MODEL.SERVICE. The service is run either automatically or manually by
setting the corresponding TSA.SERVICE record, and is subject to TSM running.

TEMENOS T24 User Guide Page 18 of 75

AM Dynamic Modelling

Child and Parent Nodes with Status To Be Validated

The above examples display a Child node and its Parent node, note that the child node identifies its
Parent node similarly the Parent node identifies its Child node. Note their status is To Be Validated.

TEMENOS T24 User Guide Page 19 of 75

AM Dynamic Modelling

However once the Model Service Program processes the records, the status are changed accordingly,
in the following cases they are Active.

Child and Parent Nodes with Status Active

TEMENOS T24 User Guide Page 20 of 75

AM Dynamic Modelling

Copy of a Model
It is not advisable to use copy function to create a copy of a model for a different date as it would not
ensure that the integrity of the model hierarchy. Therefore, in order to ensure this integrity, the model
copy program AM.DYNAMIC.MODEL.COPY should be used at all times.

The Id is a free format, however if automatically generated id is to be used then define it within the
relevant COMPANY record(s) within the field PGM.AUTOM.ID.

The copy program enables a specified model of a particular date FROM.DATE to be copied as either
the same node name or a new node name NEW.MODEL Id of another date TO.DATE , subject to the
Copy.Type and Overwrite definitions.

The input program requires a unique Id with a suitable description, together with the node name of the
Am.Dynamic.Model to be copied.

The FROM.DATE identifies the specific date of the model to be copied and therefore must exist, but the
TO.DATE - the date for the copy for which the model may or may not exist.

Depending on the COPY.TYPE input ie All, Single, Parent or Child and the OVERWRITE input the
copy behaves differently.

If OVERWRITE is set to Yes, then any new model specified with same date is overwritten, however if it
is set to No, it displays an error if target models exist for the TO.DATE.

These are the following actions for the COPY.TYPE selection –

All The Source node and every model in its hierarchy are copied.
Single The Source node only is copied, and also this is the only type that allows copy to new
Id.
Parent The Source node and all its parent models up to the root nodes in its hierarchy are
copied.
Child The Source node and all its child models in its hierarchy are copied.

TEMENOS T24 User Guide Page 21 of 75

AM Dynamic Modelling

The following example shows that a model DYNMODCHILD for the 08 AUG 2003 is copied to a new
date of 10 AUG 2003, with COPY.TYPE All and OVERWRITE No. Since the child record has a parent,
they are all copied for the new date.

Copy of a Model

TEMENOS T24 User Guide Page 22 of 75

AM Dynamic Modelling

Copy of a Model (Child)

TEMENOS T24 User Guide Page 23 of 75

AM Dynamic Modelling

Copy of a Model (Parent)

TEMENOS T24 User Guide Page 24 of 75

AM Dynamic Modelling

Integrity Check

Integrity Check of the dynamic model is done both online and in Close of Business (Cob) processing.
It validates the model as well as ensures that there are no cyclical references between the models. It
more or less complements the Input validation process.
Upon Input of a dynamic model, the MODEL.STATUS is set as To Be Validated , and on Validation or
Authorisation, the validation process generates an error if the model meets any of the following error
conditions.
Child node or security is referenced more than once within a model.
Reference currency of the root node and the child node is not the same.
Reference currency of the root node and the child node is not the same of as that of the portfolio /
virtual portfolio reference currency.
The portfolio is not unique ie used in another root node.
A Security does not comply with the segmentation scheme of the model.

Once the model has passed all input validations and accepted, the AM.DYNAMIC.MODEL.SERVICE
which is run as a background service, processes the record with MODEL.STATUS set as To Be
Validated .
If an error condition is met, it sets the MODEL.STATUS of the root.node to Error and displays the error
in the REASON field.
It also ensures that
If in any child node, the field ACTIVE is set to No, then the MODEL.STATUS of the root node is made
Inactive
If in all the child nodes, the field ACTIVE is set to Yes , then all the parent and root nodes status are
set to Active.
If models have any cyclical reference an integrity failure occurs which is then reflected in the
MODEL.STATUS and REASON fields.
In Cob start of business processing, Active nodes are rolled over with a new working day date, this is
done by the program AM.COB.DYNAMIC.MODEL.REGEN; an API hook has been allowed so that the
user may create a subroutine called AM.COB.DYNAMIC.MODEL.REGEN.LOCAL which takes in an
AM.DYNAMIC.MODEL record as its only parameter, thus enabling the user to manipulate the local
reference fields from day to day.

In Cob start of business processing, models reaching their validity dates are set to Active.

TEMENOS T24 User Guide Page 25 of 75

AM Dynamic Modelling

Status summary
.The integrity check will validate the hierarchy of the specified node(s) and set the MODEL.STATUS
and REASON fields of the root node(s) depending on the detected condition;

Root Node
Condition / Reason
Status

INACTIVE If any node in the hierarchy has its ACTIVE field set to N

If a node or security are referenced more than once in the hierarchy or

There is a cyclical reference within the hierarchy or
The assets referred to in sub nodes do not fit into their assigned part of the root
ERROR
level segmentation scheme.
The reference currency is not consistent throughout the hierarchy

ACTIVE If none of the nodes in the hierarchy are inactive and there are no error conditions.

Notes
• Only Active root nodes are used to rebuild model portfolios. If no active portfolio is found during
the daily rebuild processing, the system retains the current model structure held in the virtual
portfolio. No adjustments to the virtual portfolio can take place until a valid model is presented.
• It is possible to update the root node and child node to make it effective from a future date. The
integrity of that model is checked during SOD (start of day processing ) of that future date.

TEMENOS T24 User Guide Page 26 of 75

AM Dynamic Modelling

Example 1
AM.DYNAMIC.MODEL of Child and Root Nodes with status To Be Validated before the
AM.DYNAMIC.MODEL.SERVICE is run

Child Node

Child node before Service

TEMENOS T24 User Guide Page 27 of 75

AM Dynamic Modelling

Root Node

Root node before Service

TEMENOS T24 User Guide Page 28 of 75

AM Dynamic Modelling

Example 2
AM.DYNAMIC.MODEL of the Child and Root Nodes with status Active after the
AM.DYNAMIC.MODEL.SERVICE has run.

Child Node

Root Node

Child & Root Nodes after Service

TEMENOS T24 User Guide Page 29 of 75

AM Dynamic Modelling

Example 3

AM.DYNAMIC.MODEL of a Root Node with Active field set to Yes, and two Child Nodes, after the
AM.DYNAMIC.MODEL.SERVICE is run, showing their status have been changed to Active.

Root Node with Yes to Active

TEMENOS T24 User Guide Page 30 of 75

AM Dynamic Modelling

Child Nodes with Yes to Active

TEMENOS T24 User Guide Page 31 of 75

AM Dynamic Modelling

Example 4
AM.DYNAMIC.MODEL of an Active Child Node after the Cob run, showing the corresponding new
Child Node for the new working day 20001204.
Before COB

Child node before Cob

TEMENOS T24 User Guide Page 32 of 75

AM Dynamic Modelling

After COB

Child Node after Cob

TEMENOS T24 User Guide Page 33 of 75

AM Dynamic Modelling

Performance

The fields GROSS.DIVISOR, NET.DIVISOR, GROSS.C.PERF and NET.C.PERF on the file

SC.PERF.DETAIL (the performance repository) are used in the computing of dynamic model portfolio
performance, using the following formula, where i is the day.
Eval i
div i = × div i −1 .
Eval i − (IF i + OF i )
The Divisor is computed daily during the calculation of performance and also during back value
recalculation of model portfolio.

The performance of the portfolio is computed as follows and updated in GROSS.C.PERF and
NET.C.PERF

EVal i
PI i =
div i
Note for first day, the start Divisor is taken as (Eval.1 /100) so as to give an initial performance of 100

SC.PERF.DETAIL Record

TEMENOS T24 User Guide Page 34 of 75

AM Dynamic Modelling

Enquiry AM.DYNAMIC.MODEL.PERF
This enquiry enables the performance of the portfolio to be viewed.

SC.PERF.DETAIL record for the portfolio 50042-1

TEMENOS T24 User Guide Page 35 of 75

AM Dynamic Modelling

This record can be viewed using the enquiry ENQ AM.DYNAMIC.MODEL.PERF

Enquiry display for portfolio 50042-1

TEMENOS T24 User Guide Page 36 of 75

AM Dynamic Modelling

Performance Adjustment
It is possible to correct performance manually using SC.PERF.DETAIL.MAN.

SC.PERF.DETAIL.MAN before adjustment

TEMENOS T24 User Guide Page 37 of 75

AM Dynamic Modelling

Input of an inflow of 500,000 for the 15 Dec 2000

TEMENOS T24 User Guide Page 38 of 75

AM Dynamic Modelling

After COB SC.PERF.DETAIL is updated ( In Flow.2)

TEMENOS T24 User Guide Page 39 of 75

AM Dynamic Modelling

Using the Performance enquiry, the inflow of 500,000 is reflected on the 15 Dec 2000

Enquiry AM.DYNAMIC.MODEL.PERF

TEMENOS T24 User Guide Page 40 of 75

AM Dynamic Modelling

Archiving
A history of the dynamic model portfolio structure is maintained so that it is possible to go back in time
to any date and retrieve (and visualise) a snapshot of the structure valid at that date, accounting for
any change to the contents and structure of the dynamic model portfolios.
The orders generated by the rebalancing of a given model are traceable
Once an Am.Dynamic.Model passes its Validity Date, the length of time it remains Active on the live
file before going to history is dictated by the number of days set in DYN.MODEL.LIFESPAN on the
AM.PARAMETER file. If this is not set, it stays on the live file indefinitely.

AM.PARAMETER with Dyn.Model.Lifespan set

TEMENOS T24 User Guide Page 41 of 75

AM Dynamic Modelling

Archiving Example 1
Shows a list of Am.Dynamic.Models whose validity dates have been rolled over from 30/Nov/2000 to
the working day 04/Dec/2000 after the Cob run, and also showing initially no history records, as well
as the Node names file.

List of rollover dynamic models

No records in HIS file

No history file

AM.DYNAMIC.NODE.NAME

List of Nodes

TEMENOS T24 User Guide Page 42 of 75

AM Dynamic Modelling

Archiving Example 2
Shows a list of Models whose validity dates have been rolled over from 04/Dec/2000 to next working
day 15/Dec/2000 after the Cob run, and also showing history records of model of 30/Nov/2000
archived, as well as the current Node names file

List of rolled over models

AM.DYNAMIC.MODEL$HIS records after COB

History list after Close Of Business

TEMENOS T24 User Guide Page 43 of 75

AM Dynamic Modelling

AM.DYNAMIC.NODE.NAME

List of Node names

TEMENOS T24 User Guide Page 44 of 75

AM Dynamic Modelling

Restructuring of the Model Portfolio

The restructuring of a model portfolio requires a valid AM.DYNAMIC.MODEL structure to be in
place with a portfolio defined on its root node.
When a Dynamic Model structure is input or updated for the current validity date, and has passed the
integrity checks, the Model Build service traverses the model and creates proposed BUYs and SELLs
to align the model portfolio (recorded on the root node) to the recommended security allocations
defined on the related Dynamic Model structure.
When Percentage is specified in the VALUE.TYPE of the model then the value defined in the
PORTFOLIO.VALUE field on the root, is used as the basis for creating proposed BUYs and SELLs
Details of the proposed Buys/Sells are recorded in the application AM.MODEL.PORT.REBUILD.
One record is created per Security/Parent Node/Root Node combination
Note – Proposed nominals are only created if the MODEL.STATUS field on the model is set to
‘ACTIVE’. Therefore models with a future validity date will only create proposed BUYs and SELLs in
the ‘Start of Day’ run of the validity date (Assuming that the model passes Integrity Checks)
Subsequent model updates during the day result in the Model Build service being run, and any
existing unauthorised AM.MODEL.PORT.REBUILD records being overwritten with the updated
proposed nominal.

AM.MODEL.PORT.REBUILD

As can be seen in the screenshot, the proposed nominal and action can be overridden prior to
authorisation, via the fields AMEND.PROP.NOM and AMEND.ACTION. It is recommended that this is
performed via the enquiry AM.DYN.MODEL.PORT.REVIEW. This provides a view of a selected
model in terms of the Current and Recommended holdings, and the Delta value.

TEMENOS T24 User Guide Page 45 of 75

AM Dynamic Modelling

It also provides the facility to update and commit the Proposed Nominal and Action. Refer to the
‘Presentation’ section for further details. In the event that the Proposed Nominal is updated to a value
that isn’t a multiple of the trading units, the Nominal will be automatically rounded up/down at the
commit stage, to the nearest trading unit depending on the rounding setting in AM.PARAMETER

In the event that a Corporate Action takes place that results in a change to the nominal held in the
Virtual Portfolio (e.g. Stock Split), the Dynamic Model hierarchy is synchronised with the new portfolio
holding. This only takes place for Nominal type models by updating the relevant NOMINAL field(s) in
the model hierarchy. This takes place during the Close of Business (Batch record -
BNK/SOD.SC.VAL.EXT)
Note – In the event that a Corporate Action results in odd lots being held in the model portfolio, some
manual intervention may be required in addition to the above synchronisation.

TEMENOS T24 User Guide Page 46 of 75

AM Dynamic Modelling

Buy/Sell Mechanism

Creation of Security.Transfers

Buy or Sell Security Transfers are created as a rebalancing recommendation for a portfolio.
When an AM.DYNAMIC.MODEL is created, the background service
AM.DYNAMIC.MODEL.SERVICE rebalances the model.

It generates an AM.MODEL.PORT.REBUILD record in IHLD for each security within the portfolio,
with the proposed nominal value and recommendation for buying or selling in order to bring it to the
required target investment.

After any adjustment on the IHLD AM.MODEL.PORT.REBUILD record input, and authorisation, a
SECURITY.TRANSFER transaction for the security, is generated by another background service
AM.MODEL.BUY.SELL.SERVICE.

The generation of the Security Transfer records from the AM.MODEL.PORT.REBUILD records
are automated through the use of the new Presentation Enquiries. Please refer to Dynamic Model
Enquiries section.

TEMENOS T24 User Guide Page 47 of 75

AM Dynamic Modelling

Cash Position Adjustment of Virtual Accounts

The application AM.AMEND.VIRTUAL.BALANCE is used to amend the cash position of virtual
accounts without affecting P&L as no accounting is performed on these movements. The application
can only be used with accounts belonging to virtual portfolios, and each record can only be posted
once. The postings may then be viewed in the AM.VIRTUAL.ACCOUNT application.

Amending the balance of a virtual account

Entry shown in AM.VIRTUAL.ACCOUNT

TEMENOS T24 User Guide Page 48 of 75

AM Dynamic Modelling

Back Valuation

Using the fields AMEND.PRICE and AMEND.RATE of a dynamic model to amend price or exchange
rate for a security, triggers the new Buy/Sell recommendations.

AM Dynamic Model

Field Name Description

AMEND.PRICE This allows the user to manually enter a price for a security, must be
null if not a security.
AMEND.RATE This allows the user to manually enter an exchange rate, must be null
if not a security.

Amendment of the price or rate of a back-value or today’s dynamic model record, results in new
buy/sell recommendations for the model, which can then result in security transfer being produced if
the recommendations are accepted.
The amended dynamic model record is checked by the integrity background service, and is set to
Active if correct.
The background services react to correctly align the virtual portfolio to the model by selling off any
positions that are held by the virtual portfolio that not in the model.
The model build service only operates on models whose status is “Active”. and deletes any existing
corresponding IHLD records for the model.
A Buy/Sell recommendation is produced as AM.MODEL.PORT.REBUILD (AMPR) records which
may be accessed individually or through the fastpath enquiries, for either accepting or amending.
Once the record is committed, a back ground service process this AMPR record to generate a
Security Transfer record using the version specified in the Am parameter, with the value date as that
of the model date.
If the security transfer are to be updated on the AM history file AM.VEH.nnn, then the
ONLINE.BACKVALUE.LAUNCH facility may be used to update the history record for the portfolio.

TEMENOS T24 User Guide Page 49 of 75

AM Dynamic Modelling

Example 1
.

AM History record for 1137-1 for 20001215

Amendment of price to 90 for security 210100-000 and 91 for 200107-000

As a result of the change, the following AM.MODEL.PORT.REBUILD records are created

TEMENOS T24 User Guide Page 50 of 75

AM Dynamic Modelling

List of AM.MODEL.PORT.REBUILD records

Security 200106-000

TEMENOS T24 User Guide Page 51 of 75

AM Dynamic Modelling

Security 200108-000

Security 200107-000

TEMENOS T24 User Guide Page 52 of 75

AM Dynamic Modelling

Security 210100-000

Acceptance of an AMPR

If an AMPR record is selected for acceptance, then a Security transfer record is generated as below
for the security.

TEMENOS T24 User Guide Page 53 of 75

AM Dynamic Modelling

Security Transfer produced

Online Back Value Launch for Portfolio 1137-1

TEMENOS T24 User Guide Page 54 of 75

AM Dynamic Modelling

If the AM history file for the portfolio 1137-1 is to be updated, then this is done by Verifying the above
record.

Verification of Online Back Value Launch for Portfolio 1137-1

Enquiry AM.VAL.HIST above shows that 2000000 of security 200106-000 have been sold

TEMENOS T24 User Guide Page 55 of 75

AM Dynamic Modelling

Example 2

Using the presentation enquiry ENQ AM.DYN.MODEL.TIMELINE for back value model.

Presentation Enquiry for Node NOMBONDAD for 20001215 showing ALL levels

Selection of only 1 recommendation

TEMENOS T24 User Guide Page 56 of 75

AM Dynamic Modelling

Security Transfer generated for a Buy recommendation of 1000 of Security 200108-000

TEMENOS T24 User Guide Page 57 of 75

AM Dynamic Modelling

Enquiries
The Enquiries allow the user to:
• Maintain the Model Portfolio created by the Dynamic Model, adjusting the proposed Buy and
Sell quantities.
• List the Dynamic Models, with drill-downs to appropriate enquiries or functions.
• View the results of the Dynamic Model Integrity Check.
• List and maintain the history for one or more Dynamic Models.

Some enquiries are provided to aid in maintenance and overview of the AM.DYNAMIC.MODEL
records created; along with the AM.DYNAMIC.MODEL.PORT.REBUILD records created by the
model rebuild process, which links into the Buy/Sell mechanism.
These are as follows:

Enquiry Description
AM.DYN.MODEL Maintain the currently valid model
AM.DYN.MODEL.TIMELINE Maintain Dynamic Model records for other dates
AM.DYN.MODEL.INTEGRITY.STATUS View the status of Dynamic Model records after the
integrity check
AM.DYN.MODEL.PORT.REVIEW Review the proposed Buy/Sell orders against a model
and commit them.

AM Dynamic Model Enquiries

TEMENOS T24 User Guide Page 58 of 75

AM Dynamic Modelling

AM Dynamic Model Maintenance

The enquiry AM.DYN.MODEL allows the user to view and maintain the model(s) for the current validity
date.
The enquiry offers a number of selection criteria which perform the following functions:

Selection Field Valid Input Function

NODE.NAME A key to a record in Specifies the node name of the
AM.DYNAMIC.NODE.NAME or blank AM.DYNAMIC.MODEL records to be
reported on – if LEVEL is set to
‘CHILD’, will display a hierarchy of
nodes below this one. If LEVEL is set
to ‘ALL’ will display hierarchy of all
nodes connected to this one.
PORTFOLIO.ID A key to a record in Search for the AM.DYNAMIC.MODEL
AM.DYNAMIC.PORT.NODE or blank root node to which this portfolio is
linked – if LEVEL is set to ‘CHILD’ or
‘ALL’, will display a hierarchy of nodes
below the root.
CHILD.NODE A key to a record in Search for parents of this
AM.DYNAMIC.NODE.NAME or blank NODE.NAME.
PARENT.NODE A key to a record in Search for nodes for which this
AM.DYNAMIC.NODE.NAME or blank NODE.NAME is a parent
LEVEL ‘ROOT’, ‘ALL’, ‘CHILD’ or blank ‘ROOT’ will return the root node of the
NODE.NAME input. ‘ALL’ will return
all nodes linked to the NODE.NAME
input and ‘CHILD’ will return all the
nodes below and including the
NODE.NAME input.
ROOT.NODE.NAME A key to a record in Specifies the root node name to
AM.DYNAMIC.NODE.NAME which which all displayed records are linked
corresponds to a root node or blank – only hierarchies or nodes belonging
to this root node will be displayed.
MODEL.STATUS ‘Active’, ‘Inactive’, ‘To Be Validated’, Search for nodes with a specific
‘Error’ or blank model status.

Selection Criteria for the AM.DYN.MODEL enquiry

TEMENOS T24 User Guide Page 59 of 75

AM Dynamic Modelling

The enquiry gives the ability to drill down to the following functions:

• Edit Amend AM.DYNAMIC.MODEL or AM.SEGMENTS record*

• New Create new AM.DYNAMIC.MODEL or AM.SEGMENTS record*

• Deactivate Mark the node as inactive

• Duplicate Copy the node via AM.DYNAMIC.MODEL.COPY.

• Timeline Launch the AM.DYN.MODEL.TIMELINE enquiry for this node.

• Status Launch the AM.DYN.MODEL.INTEGRITY.STATUS enquiry for this node

• Review Model Build Launch the AM.DYN.MODEL.PORT.REVIEW enquiry for this node

• View Hierarchy View the hierarchy from this node down.

• Up Go up a level (view the parent nodes of this node).

• Down Go down a level (view the child nodes of this node).

* Will launch either application, depending on line selected. Other drilldowns are invalid for a segment.

TEMENOS T24 User Guide Page 60 of 75

AM Dynamic Modelling

EDIT

Selecting a line display with a facility available and Clicking on the launches
the Edit function.
The example below shows how one can edit a dynamic model from a display of a portfolio root node.

Launch an edit of Am.Dynamic.Model from Enquiry

TEMENOS T24 User Guide Page 61 of 75

AM Dynamic Modelling

Another Example below , shows how a segment can be accessed for edit.
Clicking the Edit for the STOCK AND SHARES line, launches the AM.SEGMENTS edit screen.

Launch of Am.Segments edit from Enquiry

TEMENOS T24 User Guide Page 62 of 75

AM Dynamic Modelling

NEW

Selecting a line display with a facility available and Clicking on the

launches the Input function.
Example below shows how one can input a new dynamic model or a new segment from a display of a

portfolio by clicking on the corresponding

Input screen for AM.DYNAMIC.MODEL

Input screen for AM.SEGMENTS

TEMENOS T24 User Guide Page 63 of 75

AM Dynamic Modelling

DEACTIVATE

Selecting a line display with a and Clicking on the launches the

dynamic model Input version AM.DYNAMIC.MODEL,DEACTIVATE that sets the Active prompt to No.

Deactivation of a node

This will update the record, if it is committed.

TEMENOS T24 User Guide Page 64 of 75

AM Dynamic Modelling

DUPLICATE

Selecting a line display with a and Clicking on the launches the

dynamic model copy version AM.DYNAMIC.MODEL.COPY,AUTO

Copy of a node

This will create the new record NOMCHILD*20001230, if it is committed

TEMENOS T24 User Guide Page 65 of 75

AM Dynamic Modelling

TIMELINE

Selecting a line display with a and Clicking on the launches the

AM.DYN.MODEL.TIMELINE enquiry for this node. See also Section AM Dynamic Model Timeline
This shows all records against a node name, i.e. all dates for which a particular node is valid.

Timeline display

TEMENOS T24 User Guide Page 66 of 75

AM Dynamic Modelling

STATUS

Selecting a line display with a and Clicking on the launches the

AM.DYN.MODEL.INTEGRITY.STATUS enquiry for this node

Status display

TEMENOS T24 User Guide Page 67 of 75

AM Dynamic Modelling

REVIEW MODEL BUILD

Selecting a line display with a and Clicking on the launches the

AM.DYN.MODEL.PORT.REVIEW enquiry for this node

Am.Model.Port.Rebuild.Wrk

TEMENOS T24 User Guide Page 68 of 75

AM Dynamic Modelling

VIEW HIERARCHY

Selecting a line display with a and Clicking on the launches the View
of the hierarchy from this node down.

These selection criteria can be used together to show hierarchies. For instance, to display the
hierarchy linked to a portfolio, the PORTFOLIO.ID selection field is set to the portfolio id and the
LEVEL is set to ‘ALL’. The following is an example of an hierarchy .

Viewing a hierarchy

The hierarchy display shows the nodes arranged in hierarchical order (parent to child order) where the
Segment labels are also displayed. The indentation markers (>) give an indication of the depth within
the model. Note that in the above example, DMP-EQ-USD-GROWTH is the root node, which contains
the segment labels MM Instr and Equity, below which are DB-MM-USD-A+, DB-MM-USD-A- and DB-
EQ-AGGR respectively. Note also that Securities defined in the models are not shown on the enquiry.

TEMENOS T24 User Guide Page 69 of 75

AM Dynamic Modelling

UP

Selecting a line display with a and Clicking on the goes up a level to

enable the viewing of the parent nodes of this node.

Display of node at upper level

TEMENOS T24 User Guide Page 70 of 75

AM Dynamic Modelling

DOWN

Selecting a line display with a and Clicking on the goes down a level
to enable the viewing of the child nodes of this node.

Display of node at lower level

TEMENOS T24 User Guide Page 71 of 75

AM Dynamic Modelling

AM Dynamic Model Timeline

The enquiry AM.DYN.MODEL.TIMELINE shows all records against a node name, i.e. all dates for
which a particular node is valid, along with a timestamp.

Input of NODE.NAME is mandatory within the selection criteria. The MODEL.STATUS can also be
selected via the selection criteria.

AM Dynamic Model Timeline enquiry

Drilldowns allow the user to:

• Edit Amend AM.DYNAMIC.MODEL record.

• Deactivate Mark the node as inactive on this date.

• Duplicate Copy the node from this date via AM.DYNAMIC.MODEL.COPY.

• Status Launch the AM.DYN.MODEL.INTEGRITY.STATUS enquiry for this node.

• Review Model Build Launch the AM.DYN.MODEL.PORT.REVIEW enquiry for this node and date.

TEMENOS T24 User Guide Page 72 of 75

AM Dynamic Modelling

AM Dynamic Model Integrity Status

The enquiry AM.DYN.MODEL.INTEGRITY.STATUS shows the status of the AM.DYNAMIC.MODEL
records including any errors found as a result of the integrity check.
As this enquiry is driven directly from file, the selection criteria relate directly to the fields on the
AM.DYNAMIC.MODEL records.

AM Dynamic Model Integrity Status

The drilldowns from this enquiry enable the user to:

• Maintain Launch the AM.DYN.MODEL or AM.DYN.MODEL.TIMELINE enquiry
for this node. *
• Review Model Build Launch the AM.DYN.MODEL.PORT.REVIEW enquiry for this node.

• Review Model Build All Launch the AM.DYN.MODEL.PORT.REVIEW enquiry for this
hierarchy
* dependent upon whether this line is for the current validity date or not.

TEMENOS T24 User Guide Page 73 of 75

AM Dynamic Modelling

AM Dynamic Model Rebuild Review

The enquiry AM.DYN.MODEL.PORT.REVIEW shows the AM.MODEL.PORT.REBUILD
unauthorised records relating to the AM.DYNAMIC.MODEL records that are selected.
Essentially, the records are shown in a hierarchy as defined by AM.DYNAMIC.MODEL. Therefore,
the selection criteria are similar to those for the AM.DYN.MODEL enquiry.

Selection Field Valid Input Function

NODE.NAME A key to a record in Specifies the node name
AM.DYNAMIC.NODE.NAME or blank corresponding to the
AM.MODEL.PORT.REBUILD
records to be reported on – if
LEVEL is set to ‘CHILD’, will display
a hierarchy relating to this node and
nodes below it. If LEVEL is set to
‘ALL’ will display hierarchy relating
to all nodes connected to this one.
PORTFOLIO.ID A key to a record in Search for the
AM.DYNAMIC.PORT.NODE or blank AM.DYNAMIC.MODEL root node to
which this portfolio is linked, and
therefore corresponding
AM.MODEL.PORT.REBUILD
record – if LEVEL is set to ‘CHILD’
or ‘ALL’, will display a hierarchy
below the root.
LEVEL ‘ROOT’, ‘ALL’, ‘CHILD’ or blank ‘ROOT’ will return the record
relating to the root node of the
NODE.NAME input. ‘ALL’ will
return all records linked to the
NODE.NAME input and ‘CHILD’ will
return all the records relating to the
NODE.NAME input and below.
VALIDITY.DATE A valid date for which Specifies the date for which the
AM.MODEL.PORT.REBUILD records AM.MODEL.PORT.REBUILD
exist. records are to be retrieved. If this is
null, then the current date is
assumed.

AM Dynamic Model Rebuild Review – Selection Criteria

The enquiry lists the AM.MODEL.PORT.REBUILD$NAU records in hierarchical order, and

contains collapsible columns detailing Node Name, Description (from the relevant
AM.DYNAMIC.MODEL record), Segment Label and Asset Description (SHORT.NAME from the
relevant SECURITY.MASTER record). This editable enquiry allows the user to select the preferred
nominal buy and sell amounts and commit the deals. If the Buy/Sell service has been activated, the
orders will be generated in IHLD.

TEMENOS T24 User Guide Page 74 of 75

AM Dynamic Modelling

AM Dynamic Model Rebuild Review enquiry

When the enquiry is committed, the Actual Nominal, Actual Direction and
AM.MODEL.PORT.REBUILD keys are input into the AM.MODEL.PORT.REBUILD.WRK
workfile. This automatically amends and authorises the relevant AM.MODEL.PORT.REBUILD
records.
NOTE that AM.MODEL.PORT.REBUILD.WRK needs to be set up to use automatically generated
ids by defining it within the relevant COMPANY record(s) within the field PGM.AUTOM.ID.

TEMENOS T24 User Guide Page 75 of 75