Technical Special Interest
Technical Special Interest
Latin American Regional Conference – 2013 2
Agenda
• Case Study: Banco Central de la Republica Dominicana
Raul Mejia, Banco Central de la Republica Dominicana
Felipe Rios, BCG
• Case Study: Filiales Consolidación Tecnológica Plataforma
SWIFT
Luis Cortina, Alliance Enterprise
• Support Game
• Preguntas de cualquier tema tecnica
Latin American Regional Conference – 2013 3
Case Study 1: Integración
LARC 2013
Integración Sistema de pagos de la República Dominicana
(SIPARD) y Sistema de Interconexión de Pagos regional
(SIP) con SWIFT Alliance Integrator
Miguel Raúl Mejía
Banco Central de la República Dominicana
Cartagena de Indias, Julio 11, 2013
Ban
co C
entr
al d
e la
Rep
úb
lica
Do
min
ican
a
Contenido
Antecedentes
Necesidades
Condiciones
Estrategia
Implementación
Beneficios
Conclusiones
5
Ban
co C
entr
al d
e la
Rep
úb
lica
Do
min
ican
a
SIPLBTR
Regional
GuatemalaLBTR Nacional
El SalvadorLBTR Nacional
República
DominicanaLBTR Nacional
NicaraguaLBTR Nacional
HondurasLBTR
Nacional
SWIFTSWIFT
Antecedentes
Sistema de pagos de la República Dominicana SIPARD: – LBTR – 72 particpantes – FIN-Copy
Sistema de Interconexión de Pagos Regional de Centroamérica y República Dominicana: – Bancos Centrales: DO, GT,
ES, NI, HN, CR – GI: República Dominicana – 54 participantes
indirectos – FIN-Copy
6
Ban
co C
entr
al d
e la
Rep
úb
lica
Do
min
ican
a
Necesidades
Integración Sistema LBTR nacional – Sistema LBTR regional
Automatización proceso acreditación/retiro de fondos de las cuentas participantes del SIP, desde y hacia banco corresponsal
No intervención manual
Trazabilidad, monitoreo, calidad, seguridad, contingencias, notificaciones, etc.
No modificaciones sistemas internos
Opciones para conectividad
Otras necesidades internas
7
Ban
co C
entr
al d
e la
Rep
úb
lica
Do
min
ican
a
Condiciones
Estándar regional de estructura cuentas basado en IBAN
Instructivos para envío transacciones regionales
Acuerdos con banco corresponsal
Normativas internas
Personal capacitado
8
Ban
co C
entr
al d
e la
Rep
úb
lica
Do
min
ican
a
Estrategia
Implementación SWIFT Alliance Integrator:
– Fases: evaluación (assessment), diseño, desarrollo, pruebas de
aceptación, implementación
– Desarrollo diversos tipos flujos: SWIFT-SWIFT, SWIFT-sistemas internos, sistemas internos-SWIFT
– Acompañamiento post-producción, transferencia conocimiento, calidad, seguridad
– Pruebas: flujos, diversos escenarios, contingencias, notificaciones, etc.
– Máximo provecho a facilidades del sistema
– Preparados para futuras necesidades
– Apoyo de SWIFT durante el proceso
9
Ban
co C
entr
al d
e la
Rep
úb
lica
Do
min
ican
a
Implementación
Flujos: – Transacciones de pagos hacia Centroamérica (salientes)
– Transacciones de pagos desde Centroamérica (entrantes)
– Fondeo de cuentas por medio de bancos corresponsales
– Pagos proveedores externos
Generación eventos técnicos y funcionales, flujos monitoreados por usuarios
Servidores virtuales: producción, desarrollo, pruebas, contingencia local, contingencia remota
10
Ba
nc
o
pa
rtic
ipa
nte
SIP
Ba
nc
o
Co
rre
sp
on
sa
l(S
IP)
Ge
sto
r (S
IP)
Instrucción
Crédito a favor
Gestor SIP
CR Gestor SIP
DB Banco Part SIP
MT
91
0
LBTR
CR Part SIP
SAI
Errores
Validaci
ones
Crea
transc
Alertas
No
Si
Normativas
Operaciones
Actualizaciones
Notificaciones (usuarios y
administradores)
Trazabilidad
Seguridad
Contingencias
Validaciones
Detección duplicados
Instructivos para formatos
Acuerdos formalizados
Separación de ambientes
Otras
Ban
co C
entr
al d
e la
Rep
úb
lica
Do
min
ican
a
11
Ban
co C
entr
al d
e la
Rep
úb
lica
Do
min
ican
a
• Transferencias regionales
• Fondeo cuentas regionales
• Pagos proveedores externos
• Pagos dedua 12
Ban
co C
entr
al d
e la
Rep
úb
lica
Do
min
ican
a
Beneficios
Mejoras tiempo procesamiento
No intervención manual
Mejor control de los procesos
Reutilización códigos existentes (ej: validación estructura cuenta estandarizada, otros)
No cambios en sistemas internos
Infraestructura estable
Contingencia parcial y total
Soporte: MT, MX, FileAct,
Códigos complementarios
Control flujo por BIC
Flexibilidad integración SOAP-
AFT-JDBC-etc.
Monitoreo (Web, SNMP)
Eventos funcionales y técnicos
Soporte SWIFT
13
Ban
co C
entr
al d
e la
Rep
úb
lica
Do
min
ican
a
Esquema
14
Service
bureau
Service
bureau
Service
bureau
VPN
VPN
VPN
SAA Prod
SAA Cont
VPN
VPN
VPN
SAA Cont
SAI Cont
SAI Prod
SAI Cont
Re
plic
as
WAN
Re
plic
as
Ce
ntr
o p
roce
sa
mie
nto
prin
cip
al
Ce
ntr
o p
roce
sa
mie
nto
alte
rno
Sitio
alte
rno
de
tra
ba
jo
(SA
T)
Ban
co C
entr
al d
e la
Rep
úb
lica
Do
min
ican
a
Conclusiones
Algunos factores críticos de éxito:
Necesidades claramente definidas
Condiciones previas
Estrategia implementación (evaluaciones, entendimiento
necesidades, diversos tipos de flujos, transferencia
conocimiento, acompañamiento post-producción, etc.)
Evaluación (assessment)
Personal con experiencia
Pruebas de aceptación
Flexibilidad de la herramienta SAI
Soporte permanente de SWIFT
Infraestructura lista para necesidades futuras (MX,
FileAct, etc.)
15
Ban
co C
entr
al d
e la
Rep
úb
lica
Do
min
ican
a
Muchas gracias
16
Latin American Regional Conference – 2013 17
Case Study 2: Conectividad Directa
y Consolidación Tecnologica
Conectividad Directa
y Consolidación Tecnológica
Luis Cortina
CEO, Alliance Enterprise
Alliance Cloud Solutions - Introduction for Americas Business Partners 19 19
Conectividad Directa
Opción 1: Infraestructura Propia
Alliance Cloud Solutions - Introduction for Americas Business Partners 20 20
Conectividad Directa
Opción 2: Hibrido.
Base de Datos Local con Conectividad vía Servicios
Alliance Cloud Solutions - Introduction for Americas Business Partners 21 21
Conectividad Directa
Opción 3: Hibrido.
Infraestructura Propia solo en Sitio de Producción
Infraestructura vía Servicios en Sitio de Contingencia
Alliance Cloud Solutions - Introduction for Americas Business Partners 22 22
Conectividad Directa
Opción 4: Hibrido.
Base Datos Local con conectividad vía servicios en Producción.
Infraestructura via Servicios en Sitio de Contingencia.
Alliance Cloud Solutions - Introduction for Americas Business Partners 23 23
Conectividad Directa
Opción 5: Hibrido.
Infraestructura vía Servicios (cloud)
Consolidación Tecnológica
Plataforma SWIFT
Luis Cortina
CEO, Alliance Enterprise
Alliance Cloud Solutions - Introduction for Americas Business Partners 25
Consolidación Tecnológica / Plataforma SWIFT
Alcance Proyecto
Disponer de un esquema centralizado para la administración de toda la
infraestructura SWIFT.
Asegurar un control distribuido de oficiales de seguridad y la administración de
usuarios y perfiles de acceso.
Mantener un esquema distribuido para la operación y gestión de mensajeria por
filial.
Reducir costos de renovación de hardware y gestión de sistemas.
Simplificar los procesos internos de auditoria
Reutilizar un único esquema de contingencia
Alliance Cloud Solutions - Introduction for Americas Business Partners 26
Economía de escala
Autonomía en las operaciones
Independencia en el control de mensajes
y en los esquemas de seguridad
Centralización de administración y
gestion técnica
Escalabilidad, reutilizacion de sistemas
de valor agregado
Consolidación Tecnológica / Plataforma SWIFT
Beneficios
27 Alliance Cloud Solutions - Introduction for Americas Business Partners
Servicios
de
Implementacion
y
Configuración
Inicial
Servicios de Consultoria
Administración del Proyecto
Servicio de Instalación &
Configuración Capacitación
Soporte
Servicios
de Soporte y
Mantenimiento
Administración del Sistema
Asistencia en Cambios
Monitoreo y Ajutes
Mesa de Ayuda y Soporte
SWIFT / Consultoria y Servicios Técnicos
Alliance Cloud Solutions - Introduction for Americas Business Partners 28
Apps
Users
VPN
Alliance Access Alliance Gateway
SWIFTNet Link
HSM
Customer infrastructure
VPN
28
Apps
Users
VPN
Alliance Access Alliance Gateway
SWIFTNet Link
HSM
Customer infrastructure
VPN
Apps
Users
VPN
Alliance Access Alliance Gateway
SWIFTNet Link
HSM
Customer infrastructure
VPN
CASO 1: Situación Inicial
Infrastructuras Independientes para cada Filial
Casa
Matriz
Filial n
Filial 1
Alliance Cloud Solutions - Introduction for Americas Business Partners 29 29
Apps
Users
VPN
Alliance Access Alliance Gateway
SWIFTNet Link
HSM
Customer infrastructure
VPN
Casa Matriz, Filial 1, Filial n
CASO 1: Situacion Propuesta
Infraestructuras Consolidada en Casa Matriz de la Entidad
30
VPN
Alliance Access Alliance Gateway SWIFTNet Link
HSM
Datacenter Produccion
SWIFT Network
Partners
CASO 2: Situación Inicial
Infraestructura Compartida + Conectividad Indirecta
Service Bureau
VPN
Alliance Access Alliance Gateway SWIFTNet Link
HSM
SWIFT Network
Partners
Service Bureau
Datacenter Contingencia
Apps
Users
Apps
Users
Apps
Users
Casa
Matriz
Filial 1
Filial 2
Filial n
Apps
Users
31
CASO 2: Situación Propuesta
Infraestructura Compartida + Conectividad Directa
31
Apps
Users Alliance Access
Datacenter Produccion
Apps
Users
Apps
Users
Lite 2
Remote Gateway
Datacenter Contingencia
Lite 2
Remote Gateway
Alliance Access
Casa
Matriz
Filial 1
Filial 2
Lite 2
Life Line
Apps
Users
Filial n
32
VPN
Alliance Access Alliance Gateway SWIFTNet Link
HSM
Datacenter Produccion
SWIFT Network
Partners
CASO 3: Situación Inicial
Outsourcing Total Indirecto
Service Bureau
VPN
Alliance Access Alliance Gateway SWIFTNet Link
HSM
SWIFT Network
Partners
Service Bureau
Datacenter Contingencia
Apps
Users
Apps
Users
Apps
Users
Casa
Matriz
Filial 1
Filial 2
Filial n
Apps
Users
33
CASO 3: Situación Propuesta
Conectividad Directa via servicios
33
Lite 2
Apps
Users
Filial n
Apps
Users
Filial 1
Apps
Users
Filial 2
Apps
Users
Lite 2
Lite 2
Lite 2 Casa
Matriz
Luis Cortina
CEO, Alliance Enterprise
Preguntas
Consolidación Tecnológica
Plataforma SWIFT
Latin American Regional Conference – 2013 35
Support Game
• You are a large bank. You have 2 interfaces in 2 sites (primary and backup)
• You are the SWIFT Operational manager
• Your KPIs are to recover traffic within 2 hours especially during critical times such as closing on Friday. You must ensure that you have a support package that allows you to recover from problems within your KPIs and that you have no repeat problems.
It is Friday, 14:00, 2 hours away from closing time. You need to settle the week’s activities and produce a closure report by 17:00
• At 14:00 you receive a call from the operators on the floor telling you that traffic in your interface is being queued, and it’s not passing through…
Goal of the game:
• Select the best possible hand (set of feature cards) to handle the incident, with the least amount of tokens.
• You’ll have 2 minutes max. for each round
• You can only exchange a feature against tokens.
• If you give away a feature that you have selected in order to recuperate the tokens, you cannot buy that feature back later.
• You can ask the table manager for clarifications.
• If at any point you are unsure or need help from the other players around the table, press the panic button! This allows the group to discuss strategies together.
14:15
You have been investigating the
problem with your colleagues
and the tools you have, but are
not sure where it lies – on your
side or SWIFT’s side.
14:15
You have been investigating the
problem with your colleagues
and the tools you have, but are
not sure where it lies – on your
side or SWIFT’s side.
14:45
After calling SWIFT Support,
you have just switched to
your backup site, but it seems
traffic is still not going through
14:15
You have been investigating the
problem with your colleagues
and the tools you have, but are
not sure where it lies – on your
side or SWIFT’s side.
14:45
After calling SWIFT Support,
you have just switched to
your backup site, but it seems
traffic is still not going through
15:35
Your technical team reports that
your backup site was not tested
before, and subsequently did not
have all the latest patches
installed. The team wants to
recover the database from your
production site, but they are not
sure how to do this
14:15
You have been investigating the
problem with your colleagues
and the tools you have, but are
not sure where it lies – on your
side or SWIFT’s side.
14:45
After calling SWIFT Support,
you have just switched to
your backup site, but it seems
traffic is still not going through
It’s now 6 months later, it’s time
for your review with your
manager.
You have to submit a report that
shows that you have taken all
necessary measures to ensure
that you are able to handle
similar incidents within the KPIs.
15:35
Your technical team reports that
your backup site was not tested
before, and subsequently did not
have all the latest patches
installed. The team wants to
recover the database from your
production site, but they are not
sure how to do this
With 3 Sites
Scenario 2
• You are the operational manager within a large bank. You have 3 sites for your SWIFT connections.
• We are now one year before a major SWIFT release upgrade. Your boss expects that you manage this release upgrade without interruptions to the payment systems.
Goal of the game:
• Select the best possible hand (set of feature cards) to handle the incident, with the least amount of tokens.
• You’ll have 2 minutes max. for each round
• You can only exchange a feature against tokens.
• If you give away a feature that you have selected in order to recuperate the tokens, you cannot buy that feature back later.
• You can ask the table manager for clarifications.
• If at any point you are unsure or need help from the other players around the table, press the panic button! This allows the group to discuss strategies together.
1.
You are assessing all the
requirements for the release
upgrade. You notice that your
team of 4 people is not familiar
with the details and implications
2.
You are now 6 months before the
deadline. You have a high level
plan for the upgrade, but you’re
not sure if this plan will affect your
payment systems.
On top of that, 1 of your most
experienced team members left
the company.
2.
You are now 6 months before the
deadline. You have a high level
plan for the upgrade, but you’re
not sure if this plan will affect your
payment systems.
On top of that, 1 of your most
experienced team members left
the company.
3.
You are now 2 months before the
deadline. You upgraded your test
environment, and you discovered
that some hardware is not able to
run the new software.
2.
You are now 6 months before the
deadline. You have a high level
plan for the upgrade, but you’re
not sure if this plan will affect your
payment systems.
On top of that, 1 of your most
experienced team members left
the company.
4.
You are now 1 month before the deadline. You have upgraded your backup site successfully, but while testing to send traffic, the system shuts down unexpectedly.
Your boss expects you to deliver a report focusing on progress & risks.
3.
You are now 2 months before the
deadline. You upgraded your test
environment, and you discovered
that some hardware is not able to
run the new software.
2.
You are now 6 months before the
deadline. You have a high level
plan for the upgrade, but you’re
not sure if this plan will affect your
payment systems.
On top of that, 1 of your most
experienced team members left
the company.
4.
You are now 1 month before the deadline. You have upgraded your backup site successfully, but while testing to send traffic, the system shuts down unexpectedly.
Your boss expects you to deliver a report focusing on progress & risks.
3.
You are now 2 months before the
deadline. You upgraded your test
environment, and you discovered
that some hardware is not able to
run the new software.
5.
You are three weeks before the
deadline. Your production site will
be upgraded during this weekend
(3 days from now), unfortunately
your 2 staff suffer from the flu and
expect to stay home for a couple
of days.