Partnering for

the cloud
Andrew Reeves
15th January 2018

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, for any purpose,
without the express written permission of TEMENOS HEADQUARTERS SA. COPYRIGHT 2018 TEMENOS HEADQUARTERS SA. All rights reserved.
Agenda

1 Cloud Environments

2 Data Migration

3 Local Development

4 Support
TSS Cloud Services

Channels Retail Front Core Financial Analytics

Office Banking Crime
New New New

Wealth Front Payments Enterprise

Office Data
Cloud environments
We are seeing increased use of cloud to support different lifecycle stages. Important to define up
front the type of environments that are required to support implementation, test and run.

Cloud for test / implementation Cloud for run

Non-production environments Production environments

TRAIN Environment
DEVTemplates TEST PRE- Environment Templates
LIVE DR
PROD

Production environments

PRE- Environment Templates

LIVE DR
PROD
Data Migration

Initiation Mapping Preparation Testing Migration

Definition of requirements Used to understand the Configuration of DM Tools Testing of the tools and Running the live migration
for data migration and mapping of the business to and data extraction from approach developed for of client data through the
overall approach and the target core banking source system, data migration. identified promotional
phases, sources of data, environment, including transformation and Confirmation of process model through to LIVE.
cutover plan and end-to- identification of modules cleansing of data, through sample data Includes preparation of
end strategy. and applications, creation packaging of DM Tool followed by trial migration target environment to
of mapping sheets and configuration into BCON with full data set to confirm correct system data and
extract sheets for pack and creation of test timings and performance. performance of post
reconciliation. file for loading. migration validation.
 Local Development
Develop Test & Submit Verify Release Run

All developments must The developer is
adhere to Temenos coding responsible for ensuring
standards. that the development is
fully tested and is fit for
use and fit for purpose.
TSS will verify the Once verified the During live operations TSS
submitted development development will be need to know how to
using the documents released into the target monitor, control and
outlined below. All environments, using the assess the development.
documents must be provided installation guide.
submitted with each
change.

TEMENOS Test Change Installation Operations

Coding Documentation Request Guide Guide
Standards Template

Change package to be submitted for verification

Service Provider Relationships

Client / Customer 3rd Parties (Client)

Contains the users of
3rd Parties External organisations
Client / Customer
the services (Client) contracted to the client

Temenos Corporate Temenos TSS Cloud Services TSS Cloud Services

Contains the internal The domain used to
business functions, provide the services to
Support
representing support, our clients
product and operational
services Operations

Technology
Cloud Provider
Specific third party
Product provider who has some
accountability for the TSS
Cloud
Cloud Service domain
Provider through the provision of
3rd Parties (Temenos) IaaS / PaaS components
External organisations
3rd Parties (Temenos)
contracted to Temenos.
Summary
Implementation on cloud is slightly
different to on-premise (levels of
access, role of the client,
responsibilities for BAU). We are
working on developing TIM for
Cloud.
Ensure there is clarity on the
role of the different parties
during both implementation
and BAU operations
Follow the Temenos provided
guidance for development,
data migration and ensure
changes have been tested
before submitting to TSS for
verification / deployment
Speak to TSS about your
needs for environments to
support your activities