Page 36 - A2A-interoperability_Online
P. 36
HoW to moVe aHeaD
Develop the business case
once the desired approach has been identified and agreed, the parties involved need to define the commercial details of the approach
and a business model that is sustainable for all involved parties.
Agree approach with regulators
once the industry participants have ratified the proposed approach, it is likely that it will need to be discussed with the payment
systems regulator.
once agreement of the approach has been reached, detailed planning and specification work can progress.
Define
Plan Approach Determine detailed collaborative Define commercial Formalise
requirementss approach elements agreements
the work in this phase could be separated into technical and operational/commercial workstreams.
the technical workstream will define the technical implementation for the chosen option, the technical service level requirements and
the design of the standard interfaces that need to be created.
the operational and commercial workstream will define target pricing models, operational procedures (such as fraud and risk mitiga-
tion and customer care), and the formal agreement between the participants, including service level agreements.
potential activities in this phase include:
Formalise Task Force and plan workstreams
Following agreement of the approach with regulators, formal sign-off and commitment to continue should be gained from each partici-
pating organisation. in order to achieve this, an activity plan for task Force collaboration, with an accurate understanding of the resources
required, should be created for socialisation within participating companies. naturally, internal resource commitments will need to be
understood in addition to the commitments to task Force work.
Define functional and service level requirements
once agreement to proceed has been achieved, the first activity is to refine the business requirements determined in an earlier activity
and define the more detailed functional and service level requirements for the participants. these requirements and processes will feed
into both technical and operational workstreams and will allow traceability and reference points for acceptance testing of the imple-
mented solution.
consideration will be required for the following areas of functionality:
a. inter-scheme mobile money transfers;
B. mobile money and bank transfers;
c. transaction queries and reversals;
D. settlement and reconciliation;
e. Financial and regulatory reporting;
F. risk management and fraud reporting;
G. collaborative customer care.
33
Develop the business case
once the desired approach has been identified and agreed, the parties involved need to define the commercial details of the approach
and a business model that is sustainable for all involved parties.
Agree approach with regulators
once the industry participants have ratified the proposed approach, it is likely that it will need to be discussed with the payment
systems regulator.
once agreement of the approach has been reached, detailed planning and specification work can progress.
Define
Plan Approach Determine detailed collaborative Define commercial Formalise
requirementss approach elements agreements
the work in this phase could be separated into technical and operational/commercial workstreams.
the technical workstream will define the technical implementation for the chosen option, the technical service level requirements and
the design of the standard interfaces that need to be created.
the operational and commercial workstream will define target pricing models, operational procedures (such as fraud and risk mitiga-
tion and customer care), and the formal agreement between the participants, including service level agreements.
potential activities in this phase include:
Formalise Task Force and plan workstreams
Following agreement of the approach with regulators, formal sign-off and commitment to continue should be gained from each partici-
pating organisation. in order to achieve this, an activity plan for task Force collaboration, with an accurate understanding of the resources
required, should be created for socialisation within participating companies. naturally, internal resource commitments will need to be
understood in addition to the commitments to task Force work.
Define functional and service level requirements
once agreement to proceed has been achieved, the first activity is to refine the business requirements determined in an earlier activity
and define the more detailed functional and service level requirements for the participants. these requirements and processes will feed
into both technical and operational workstreams and will allow traceability and reference points for acceptance testing of the imple-
mented solution.
consideration will be required for the following areas of functionality:
a. inter-scheme mobile money transfers;
B. mobile money and bank transfers;
c. transaction queries and reversals;
D. settlement and reconciliation;
e. Financial and regulatory reporting;
F. risk management and fraud reporting;
G. collaborative customer care.
33
