Skip to content

Technology - RASCI View

The Technology function at Simpaisa builds and operates the Phoenix platform and all supporting infrastructure. Led by the Chief Technology Officer (CTO), Technology owns incident management, the product development lifecycle, and all technology change management. The CTO is Accountable for architecture review, technical integration, and production deployment across the business.

The Principal Architect (Princ.Arch) holds Accountable designation on architecture reviews. The Head of DevOps (H-DevOps) owns live incident detection and execution. DevOps Leads (DevOps.L) execute the day-to-day operational steps.


Primary Processes

7.11 Incident Management and Escalation

Technology (CTO / H-DevOps / DevOps.L) is collectively Accountable and Responsible for the full incident lifecycle. The CTO holds Accountable designation on investigation, resolution, post-incident review, and root cause remediation.

Kroki

Case Management (CMMN)

Incident management is inherently case-based. Each incident has unique characteristics requiring judgement-driven task selection. The BPMN above shows the standard flow, but incident commanders may adapt the sequence, add parallel investigation streams, or escalate at any point based on evolving understanding of the incident.

Role Key

Abbreviation Full Role
CEO Chief Executive Officer
COO Chief Operating Officer
CTO Chief Technology Officer
CISO Chief Information Security Officer
CRO Chief Revenue Officer
H-DevOps Head of DevOps
DevOps.L DevOps Lead
Princ.Arch Principal Architect
Int.Lead Integration Lead
SQA SQA Lead
PM Product Manager
PMO PMO Manager
Comp.An Compliance/Regulatory Analyst
Process Step CEO COO CTO CISO CRO H-DevOps DevOps.L Princ.Arch Int.Lead SQA PM PMO Comp.An
1. Incident detection (NOC / SOC) - I I I - I R - - - - - -
2. Classification (P1-P4) - I C C I A R C - S I - I
3. Initial response - I C C - A R S S - I - I
4. Investigation - C A C C S R R R S C - C
5. Resolution - C A C - S R R R R C - -
6. Stakeholder communication I A C C C - - - - - R R C
7. Post-incident review - C A C C S R R S S C R C
8. Root cause remediation - C A C - S R R S S C R -

7.13 Product Development Lifecycle

Technology (CTO) is Accountable for the architecture review step. The Integration Lead and Principal Architect are Responsible for development. H-DevOps is Accountable for production deployment.

Kroki

Role Key

Abbreviation Full Role
CPO Chief Product Officer
CTO Chief Technology Officer
COO Chief Operating Officer
CISO Chief Information Security Officer
CRO Chief Revenue Officer
GH-RA Global Head Regulatory Affairs
PM Product Manager
Int.Lead Integration Lead
Princ.Arch Principal Architect
H-DevOps Head of DevOps
DevOps.L DevOps Lead
SQA SQA Lead
PMO PMO Manager
Comp.An Compliance/Regulatory Analyst
Process Step CPO CTO COO CISO CRO GH-RA PM Int.Lead Princ.Arch H-DevOps DevOps.L SQA PMO Comp.An
1. Market research / discovery A I C - - C R - - - - - S C
2. PRD authoring A C C C C C R S C - - - S C
3. Architecture review C A - C - - C S R S - - S -
4. Sprint planning C C - - - - R R S S S S A -
5. Development I A - C - - C R S S R S S -
6. QA testing I C - C - - C S S S S A S -
7. UAT C I C C C C A S - - - R S S
8. Production deployment I A I C - - C S S R R S S -
9. Post-launch monitoring C C C C C I A S - R R S R S

7.16 Technology Change Management (Releases)

CTO is Accountable for the full technology change process, including CAB (Change Advisory Board) approval. Architecture review is owned by the Principal Architect. Deployment is owned by H-DevOps.

Kroki

Role Key

Abbreviation Full Role
CTO Chief Technology Officer
COO Chief Operating Officer
CISO Chief Information Security Officer
CRO Chief Revenue Officer
H-DevOps Head of DevOps
DevOps.L DevOps Lead
Princ.Arch Principal Architect
Int.Lead Integration Lead
SQA SQA Lead
PM Product Manager
PMO PMO Manager
Comp.An Compliance/Regulatory Analyst
Process Step CTO COO CISO CRO H-DevOps DevOps.L Princ.Arch Int.Lead SQA PM PMO Comp.An
1. Change request I I I - I - - S - A R -
2. Impact assessment C I C C S S R S S S A C
3. Architecture review C - C - S - A S - C S -
4. Development I - - - S R S R S C S -
5. QA / testing I - C - S S S S A C S -
6. Security review C - A - S - S - S - S C
7. CAB approval A I R I R - R - R R S C
8. Deployment I I I - A R S S - I S -
9. Post-deployment monitoring C I C - A R S S R C R -

Supporting Role Summary

Technology is Consulted or Informed across all operational processes:

Process Domain Owner Technology Role
7.2 Merchant Onboarding Payments Int.Lead: A on technical integration; SQA: A on testing/UAT
7.3 Pay-In Processing Payments CTO: C; H-DevOps: A on API request, routing, authorisation, processing, notification
7.4 Pay-Out Processing Payments CTO: C; H-DevOps: A on request received, channel routing, funds transfer
7.5 Remittance Corridor Activation Payments Int.Lead: A on technical integration; SQA: A on testing
7.6 Crypto Off-Ramp Technology CTO: C on blockchain verification; H-DevOps: A on receipt and verification
7.7 White-Label Wallet Provisioning Product CTO: A on technical setup; Int.Lead: A on product configuration
7.10 Settlement and Reconciliation Finance CTO: C on data aggregation; DevOps.L: R on aggregation
7.12 New Market Entry CEO / Regulatory Int.Lead: A on payment channel integration step
7.15 Vendor Onboarding Procurement CTO: A on technical integration; Princ.Arch: R on technical integration