Page 24 - Methodology for inter-operator and cross-border P2P money transfers

Table 2 Structure of a typical Team Assignment Table (TAL)

Column name Example Type Function Hints/Further remarks
Test_Scenario InterNetwork Text Scenario description See further remarks
OwnerTeam MTN Ghana Text Team name Can be set by Excel formula
(default: equal to FromCon-
figName)
FromCountry Ghana Text Country ("From" role) Primary input field
FromOperator MTN Text DFS/network operator, Primary input field
"From" role
ToCountry Ghana Text Country ("To" role)
ToOperator Vodafone Text DFS/network operator,
"To" role
Status Completed Text Status of tests As the TAL can also serve as
planning element, the status may
contain different states such as
"Ongoing" or "Cancelled"
Remarks Unlimited transfers Text Additional scenar-
io-specific information
MaxTAPerDay 10 Integer Indicates if there is a Leave this field empty if there
systematic limit for the is no such limit. The value is
maximum number of intended to be used to compute
transactions per day mask-out indicators during data
evaluation. Enter only values
which affect the number of out-
going transactions
From_Date_Time 11.05.2020 00:00 Date (time Start of assignment
optional)
To_Date_Time 15.05.2020 23:59 Date/time End of assignment Make sure to include time for
(inclusive) proper time windowing
FromConfigName MTN Ghana Text Configuration name, Typically constructed from
"from" role" respective operator/country fields
by formula
ToConfigName Vodafone Ghana Text Configuration name, Typically constructed from
"to" role" respective operator/country fields
by formula
TransactFlow MTN Ghana to Voda- Text Auxiliary field for read- Default: constructed from respec-
fone Ghana ability tive ConfigName fields, can be
overwritten

Remarks: ing. Therefore it is recommended to use formulae
by default and only override content when strictly
• This list is understood to describe the minimum necessary.
required for processing. The list can be amend- • Some of the fields (e.g., TransactFlow) are there
ed by additional columns of seen fit by campaign for convenience of usage. If the TAL is an Excel®
management. or similar list, these fields should also be pre-set
• The TAL uses a couple of primary input fields with respective formulae, to be overwritten when
(e.g., for Operator and Country). This facilitates appropriate.
generation of “logical names” needed for process- • Please note that the TAL uses the Configuration
ing in an automated way, e.g., by Excel® formulas. names (not the Team names) as the purpose of
Experience has shown that when entering free the TAL is to link measurement data to scenarios.
text, errors which are hard to see by eye can eas- • For final processing and computation, a unique
ily slip in (e.g., two blanks instead of one). These scenario descriptor is required (typically, in data-
errors are hard to see with the human exe but can bases aggregation of data into respective KPI is
cause substantial trouble in automated process- done using GROUP statements). This can be done

22 Methodology for inter-operator and cross-border P2P money transfers