Maintenance process & FAQs

A clear set of consistent and predictable rules are in place for the approval and maintenance of Common Global Implementation (CGI) deliverables. The officially approved process provides transparency to CGI members, as well as to implementers and potential adopters.

The term ‘CGI deliverables’ is used as a general term for all guidelines and supporting documentation that CGI produces for message implementation.

Purpose

The purpose of having an officially approved process for the Approval and Maintenance of CGI deliverables is to have a clear set of consistent and predictable rules in order to provide transparency both to CGI members as well as to implementers/potential adopters on the approval and maintenance process for CGI deliverables.

Content

This document falls in two parts, one section for the approval of CGI deliverables and another section for the maintenance of those. The term CGI deliverables is used as a general term for all guidelines and supporting documentation that CGI produces for message implementation.

Status

This document is approved by the CGI Members 02 September 2011

CGI approval of deliverables

All CGI deliverables, once approved by the CGI members as a work item for CGI, are designated to a Work Group led by a CGI Management-appointed facilitator. The facilitator, together with the Work Group, is responsible for performing the work in order to produce and deliver it as a final CGI deliverable.

Each Work Group will – supported by CGI Management and CGI Support – be responsible for all parts of the process around the production of the CGI deliverables. If they cannot agree, the issue will be referred to CGI voting membership.

Approval process

The approval process of a CGI deliverable follows the following steps and timelines:

  1. The Work Group produces and agrees a draft deliverable for public review (CGI and the public). The draft deliverable is sent to CGI Support, which posts it on the CGI website and also distributes it to CGI members with a notice of public review.
  2. The public review period is 45 days and can, upon request from a CGI member, be extended for a maximum of 10 additional days.
  3. At the end of the public review period, the Work Group responsible reviews and disposes of all the comments. The Work Group is encouraged to include the comment submitters in the review process in order to clarify and resolve all comments in a satisfactory manner. The Work Group then prepares a final draft for approval by CGI voting members.
  4. The Work Group submits the final draft to CGI Management Team, which distributes it to CGI membership for approval.
  5. CGI voting members review the final draft and vote (via email) on the final draft within a 14-day ballot. If a CGI voting member votes no, the reason must be submitted with the no-vote.
  6. If approved according to the Governance Model, CGI Support publishes the final approved draft to the CGI website and CGI Plenary.
  7. If not approved, the CGI deliverable is returned to the Work Group with the comments received. The Work Group, together with CGI, will then dispose of all the comments in co-operation with the CGI members that have voted no with comments.
  8. Steps 4-6 are then repeated.
  9. If the CGI deliverable is not approved on a second round, the CGI deliverable is withdrawn from the work programme of CGI.

Maintenance process

The maintenance process has two tracks for the normative and the informative elements of CGI deliverables:

  • Normative refers to the referenced Message Implementation Guideline basic template.
  • Informative refers to the annexes, such as country specific market practice or examples.

Normative CGI deliverables

The maintenance process for normative CGI deliverables is based on an annual release cycle. The principles for the maintenance process are based on the maintenance process for ISO 20022. The fixed release dated every year is July 1st.

The following steps are required:

  1. The submitter of the CGI Change Request (CCR) submits it to CGI Support, which in turn forwards it to the relevant Work Group.
  2. The CCR must include the following information:
    • The name of the submitter (does not have to be a CGI member).
    • The message(s) in scope.
    • The business reason for the CCR.
  3. The cut-off date for CCRs is March 1st.
  4. If the CCR is approved by the relevant CGI Work Group, the CCR follows steps 1-6 of the approval process above. In addition, a separate change report is appended to the updated version of the CGI deliverable detailing the changes as applied. The CCR submitter is encouraged to participate in the Work Group discussion of the CCR.
  5. If the CGI Work Group does not approve the CCR, the reason for rejection is returned to the submitter. The submitter may appeal the decision to the CGI voting membership.

In exceptional cases, the CGI membership may decide to modify the process described above and schedule an urgent release.

In addition, a corrigendum may be issued if it concerns minor corrections or editorial errors found in the published documentation.

Informative CGI deliverables

A CGI member or external party can ask for informative CGI deliverables to be updated at any time. Informative deliverables follow a quarterly release cycle based on the annual release cycle of July 1st.

The following steps are required:

Submission by a non-CGI member

  1. The external party submits a CGI Change Request (CCR) to CGI Support, which will forward it to the relevant Work Group.
  2. The CCR must include the following information:
  • The name and organisation of the submitter.
  • The message(s) in scope.
  • The business reason for the CCR.
  1. The relevant CGI Work Group will make the necessary changes and update the supporting documentation, including returning feedback to the submitter if the change is rejected.

Submission by a CGI member

  1. The CGI member submits an email with details of additional content or change to Informative Deliverables to the appropriate CGI Work Group.
  2. The CGI member attends a scheduled CGI Work Group meeting to present the proposed content or change.
  3. The relevant CGI Work Group will make the necessary changes and update the supporting documentation.
  • All changes to Informative Documents are documented in the ‘Change Control' tab or paragraph of the applicable document.
  • No later than a month before an actual new quarterly release, CGI members will be informed of the changes and the updated supporting documentation. Any comments received from CGI members will be taken under review by the CGI Work Group issuing the document.

The CGI membership may decide to modify the process described above and schedule an urgent release of the supporting deliverable.

Notes

Please note that this process does not currently include any other decision-making process covered by the Governance Model document. Nor does it cover any other issue concerning the daily operation of CGI in the operational or organisational domain for which the CGI Management or Plenary is responsible.

FAQs

Find the answers to the most recurrent questions about CGI-MP.

Read more

Disclaimer

Read more