ISO/TS 20022-5:2004

Foreword
1 Introduction
2 Terms and definitions
3 Activities and deliverables
  3.1 Gap analysis
  3.2 Development of ISO 20022 compliant Business Transactions
      and Message Sets
  3.3 ISO 20022 Registration
  3.4 Preparation of migration
4 Workflow
  4.1 Gap analysis
      4.1.1 Industry Message Set documentation collection
      4.1.2 Business Area gap analysis
      4.1.3 Business Process gap analysis
      4.1.4 Business Transaction gap analysis
      4.1.5 Message Definition gap analysis
      4.1.6 Business Roles gap analysis
  4.2 Development of ISO 20022 compliant Business Transactions
      and Message Sets
      4.2.1 A new Business Area
      4.2.2 A modified Business Area
      4.2.3 A new Business Process
      4.2.4 A modified Business Process
      4.2.5 A requirements use case
      4.2.6 A new Business Transaction
      4.2.7 A modified Business Transaction
      4.2.8 A new Message
      4.2.9 A modified Message
      4.2.10 A new or modified Business Role
  4.3 ISO 20022 registration
  4.4 Preparation of migration
      4.4.1 Convergence documentation
      4.4.2 Coexistence documentation
      4.4.3 Migration planning
Annex A: Convergence documentation
  A.1 Data Type convergence tables
  A.2 Element convergence tables
  A.3 Message convergence tables
  A.4 Message Item convergence tables
  A.5 Some simple examples
      A.5.1 Data Type convergence tables
      A.5.2 Element convergence tables
      A.5.3 Message convergence tables

ISO/TS 20022-5:2004 describes the activities of "ISO 20022 reverse engineering" from the point of view of the user who wants to verify that the business functionality, covered by his own Industry Message Set, is covered by ISO 20022 compliant Business Transactions and Message Sets. It is not an attempt to define a"methodology" for reverse engineering.

ISO/TS 20022-5:2004 describes the following set of required activities:

• extract relevant information from existing Industry Message Sets and compare it to the related information in the ISO 20022 Repository;
• use the results of this comparison for the development of ISO 20022 compliant Business Transactions and Message Sets;
• submit the resulting update requests to the Registration Authority;
• prepare the migration to the ISO 20022 compliant Business Transactions and Message Sets.

The main objectives of the "ISO 20022 reverse engineering" are as follows:

• capture the industry knowledge covered by existing Industry Message Sets;
• build upon former standardization efforts in the industry when building ISO 20022 compliant Business Transactions and Message Sets;
• ensure that the resulting ISO 20022 compliant Business Transactions and Message Sets fully cover the business scope of existing Industry Message Sets;
• maximize interoperability between existing Industry Message Sets and ISO 20022 compliant Business Transactions and Message Sets;
• support the migration from existing Industry Message Sets to ISO 20022 compliant Business Transactions and Message Sets.

ISO/TS 20022-5:2004 gives some specific terms that are used in the document. It then describes the major activities that will be conducted during reverse engineering and also describes at a high level the resulting deliverables. A detailed workflow is presented, explaining all activities, inputs and outputs. Finally, a detailed description of the Convergence Documentation is given in an appendix.