Difference between revisions of "GC Enterprise Architecture/Board/Board Details"
Jump to navigation
Jump to search
Jana.jessome (talk | contribs) |
(Update co-chairs) |
||
| (20 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | {{OCIO_GCEARB_Header}} | |
| − | + | <multilang> | |
| − | + | @en|__NOTOC__ | |
| − | |||
| − | |||
| − | { | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | | | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
= Terms of Reference= | = Terms of Reference= | ||
| − | |||
| − | |||
| − | |||
| − | |||
==Background== | ==Background== | ||
| − | On March 23, 2017, the CIO GC established the | + | On March 23, 2017, the CIO GC established the Government of Canada Enterprise Architecture Review Board (GC EARB) <i>“to further the “whole of government as one enterprise” vision. It is integrated into the larger GC governance structure and looks at alignment of initiatives, system and solution gaps and overlaps, development of new digital capabilities and innovation opportunities, setting technology standards and providing IM-IT investment direction”</i>. |
==Effective Date== | ==Effective Date== | ||
| − | The Government of Canada Enterprise Architecture Review Board was established on March 23, 2017. These terms of reference were approved by GC EARB on | + | The Government of Canada Enterprise Architecture Review Board was established on March 23, 2017. These updated terms of reference were approved by GC EARB on March 1, 2019. |
==Mandate== | ==Mandate== | ||
| − | + | The Policy on the Management of Information Technology assigns responsibility to the Chief Information Officer of Canada to establish an implement an enterprise architecture review board that is mandated to define current and target architecture standards for the Government of Canada, and review departmental plans to ensure alignment. | |
| − | |||
| − | |||
==Responsibilities== | ==Responsibilities== | ||
| − | |||
| − | |||
GC EARB will: | GC EARB will: | ||
* Prescribe and recommend approval by the GC CIO government-wide architecture expectations; | * Prescribe and recommend approval by the GC CIO government-wide architecture expectations; | ||
* Define current and promote target architecture standards for the Government of Canada; and | * Define current and promote target architecture standards for the Government of Canada; and | ||
* Review departmental plans to ensure alignment to those architecture expectations and standards. | * Review departmental plans to ensure alignment to those architecture expectations and standards. | ||
| + | |||
| + | |||
| + | The Directive on the Management of Information Technology requires the GC EARB to review proposals concerned with the design, development, installation and implementation of digital services or solutions, information systems, and applications (“digital initiatives”): | ||
| + | *where a department is willing to invest a minimum of the following amounts in order to address the problem or take advantage of the opportunity: | ||
| + | **$2.5 million dollars for departments without an approved Organizational Project Management Capacity Class or with an approved Organizational Project Management Capacity Class of 1; | ||
| + | **$5 million dollars for departments with an approved Organizational Project Management Capacity Class of 2; | ||
| + | **$10 million dollars for departments with an approved Organizational Project Management Capacity Class of 3; | ||
| + | **$15 million dollars for the Department of National Defence; | ||
| + | **$25 million dollars for departments with an approved Organizational Project Management Capacity Class of 4; | ||
| + | *That involve emerging technologies; | ||
| + | *That require an exception to any applicable Directive or Standard under the Policy on the Management of Information Technology; | ||
| + | *That are categorized at the protected B level or below using a deployment model other than public cloud for application hosting (including infrastructure), application deployment, or application development; or, | ||
| + | *As directed by the Chief Information Officer of Canada. | ||
| + | |||
| + | If the investment meets <strong>at least one</strong> of the criteria above, the department must bring forward the proposal to GC EARB. | ||
| + | |||
==Operation== | ==Operation== | ||
| − | GC EARB meets bi-weekly. As required and at the discretion of the | + | GC EARB meets bi-weekly. As required and at the discretion of the Board’s Co-Chairs, special meetings may be called. Quorum must be met for when there are items requiring a decision. Quorum is defined as at least half of the members or their delegate being present. Should quorum not be met, items for decision will be deferred to the next meeting. |
| − | + | ||
Secretariat support is provided by Committee Secretariat, Office of the Chief Information Officer, Treasury Board of Canada Secretariat. | Secretariat support is provided by Committee Secretariat, Office of the Chief Information Officer, Treasury Board of Canada Secretariat. | ||
| − | + | ||
| + | Working groups and other supporting governance may be created, as necessary and at the direction of the Co-Chairs. | ||
==Presentation Requirements== | ==Presentation Requirements== | ||
The purpose of the GC EARB engagement must be clear (information, endorsement or exemption). | The purpose of the GC EARB engagement must be clear (information, endorsement or exemption). | ||
| − | * Departments are encouraged to use the presentation [[Media: | + | * Departments are encouraged to use the presentation [[Media:GC_EARB_Presenter_GENERAL.pptx |template]] to ensure consistent provision of content to enable formal architectural assessment. |
| − | * Departments are expected to submit their finalized materials to the Office of the Chief Information Officer, Treasury Board of Canada Secretariat (TBS OCIO) no later than one week prior to the planned meeting date. | + | * Departments are encouraged to use the presentation template to ensure consistent provision of content to enable formal architectural assessment according to the requirements set out in Appendix C (Mandatory Procedures for Enterprise Architecture Assessment) of the Directive on the Management of IT. |
| − | + | * Departments are expected to submit their finalized materials in both official languages to the Office of the Chief Information Officer, Treasury Board of Canada Secretariat (TBS OCIO) no later than one week prior to the planned meeting date. Late materials may result in deferral of the presentation. | |
| − | |||
* Items that are considered low risk and/or where there are no concerns to raise can be considered as “consent agenda items”. The consent agenda items are not allocated any presentation time however if no concerns are raised at the meeting, the items are considered endorsed. | * Items that are considered low risk and/or where there are no concerns to raise can be considered as “consent agenda items”. The consent agenda items are not allocated any presentation time however if no concerns are raised at the meeting, the items are considered endorsed. | ||
| − | |||
| − | |||
| − | |||
| − | |||
==Membership== | ==Membership== | ||
| Line 78: | Line 60: | ||
The GC EARB is co-chaired by: | The GC EARB is co-chaired by: | ||
| − | * | + | * Paul Wagner, Chief Technology Officer for the GC, Treasury Board of Canada Secretariat; and |
| − | * | + | * Matt Davies, Chief Technology Officer, Shared Services Canada |
| + | |||
| + | Membership is at the Assistant Deputy Minister level and is determined by the Co-Chairs. The membership will be updated on an annual basis, or as required. All proposed changes to the membership must be submitted to the OCIO Committee Secretariat, who will seek the approval of the Co-Chairs. | ||
| + | |||
| + | Members may appoint one delegate who is at the Director General level or above that will serve as an alternate member and be empowered to participate in discussions on their behalf. No other substitutes or delegates will be accepted. | ||
| + | |||
| + | Members are required to commit to a one year term and are expected to attend the majority of meetings. In the event that a member is absent from 6 or more meetings throughout their term, their membership to the EARB may be revoked by the Co-Chairs. The identified alternate may replace a member only when the member advises OCIO Secretariat 24 hours prior to the scheduled meeting date. | ||
| − | + | <!-- FRENCH --> | |
| + | @fr|__NOTOC__ | ||
| + | = Mandat = | ||
| − | + | ==Préambule== | |
| − | + | En vertu du paragraphe 7(1) de la Loi sur la gestion des finances publiques, le Conseil du Trésor est responsable de toutes les questions relatives à la politique administrative générale dans l’administration publique fédérale, y compris l’examen des plans et programmes de dépenses annuels et à long terme des ministères et la détermination des priorités à cet égard. | |
| − | + | ==Contexte== | |
| + | Le 23 mars 2017, le DPI du GC a mis sur pied le [https://www.canada.ca/fr/secretariat-conseil-tresor/services/technologie-information/plan-strategique-2017-2021.html Conseil d’examen de l’architecture intégrée du gouvernement du Canada] (CEAI GC) <i>« pour promouvoir la vision « de l’ensemble du gouvernement comme une seule organisation ». Il est intégré à la structure de gouvernance plus vaste du GC et examine l’harmonisation des initiatives, les lacunes et les chevauchements dans les systèmes et les solutions, le développement de nouvelles capacités numériques et les possibilités d’innovation, l’établissement de normes technologiques et l’orientation des investissements en GI/TI. »</i> | ||
| − | = | + | ==Date d’entrée en vigueur== |
| − | + | Le Conseil d’examen de l’architecture intégrée du gouvernement du Canada a été créé le 23 mars 2017. Ce mandat a été approuvé par le CEAI GC le 1 mars 2019. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | ==Mandat== | ||
| + | [https://www.tbs-sct.gc.ca/pol/doc-fra.aspx?id=12755#appA La Politique sur la gestion de la technologie de l’information] attribue au dirigeant principal de l’information du Canada la responsabilité d’établir un Conseil d’examen de l’architecture intégrée qui a pour mandat de définir les normes d’architecture actuelles et ciblées pour le gouvernement du Canada, et d’examiner les plans ministériels pour en assurer l’harmonisation. | ||
| − | + | Formuler des recommandations techniques et souligner les orientations pangouvernementales au DPI du GC aux fins d’examen et d’approbation. | |
| − | + | ==Responsabilités== | |
| − | + | ||
| − | + | Le CEAI GC fournira l’optique de l’examen technique pour les solutions proposées qui sont : de nature organisationnelle et/ou commune; le public; les technologies émergentes ou perturbatrices; les services infonuagiques; le renouvellement des contrats à long terme pour les solutions existantes; ou les exemptions architecturales proposées aux architectures de référence déjà établies pour tous les ministères (au sens de l’article 2 de la <i>Loi sur la gestion des finances publiques</i>). | |
| − | + | ||
| − | * | + | Le CEAI GC fera ce qui suit : |
| − | * | + | * Prescrire et recommander l’approbation des attentes en matière d’architecture pangouvernementale du DPI du GC; |
| − | * | + | * Définir et promouvoir les normes d’architecture cibles actuelles pour le gouvernement du Canada; |
| + | * Examiner les plans ministériels pour assurer l’harmonisation avec les attentes et les normes relatives à l’architecture. | ||
| + | ==Fonctionnement== | ||
| + | Le CEAI GC se réunit toutes les deux semaines. Au besoin et à la discrétion des coprésidents du Comité, des réunions spéciales peuvent être convoquées pour des questions urgentes. | ||
| + | Le Secrétariat du Comité, le Bureau du dirigeant principal de l’information, et le Secrétariat du Conseil du Trésor du Canada, offrent leur soutien. Pour assurer la continuité et la stabilité de la participation, de la discussion et de la diffusion de l’information, les membres du Comité sont encouragés à participer à toutes les réunions. | ||
| − | + | ==Exigences liées aux présentations== | |
| − | |||
| − | + | Le but de la mission du CEAI GC doit être clair (information, approbation ou exemption). | |
| − | + | * Les ministères sont encouragés à utiliser le [[Media:GC_EARB_Presenter_GENERAL_JAN14.pptx |modèle]] de présentation pour assurer la fourniture uniforme du contenu afin de permettre une évaluation architecturale officielle. | |
| − | + | * Les ministères doivent présenter leurs documents définitifs au Bureau du dirigeant principal de l’information, Secrétariat du Conseil du Trésor du Canada (BDPI du SCT) au plus tard une semaine avant la date prévue de la réunion. | |
| − | + | * Le Secrétariat du Comité se réserve le droit de reporter des points si les documents de présentation sont présentés en retard. | |
| + | * Le Secrétariat du Comité se réserve le droit de distribuer les points d’information par correspondance plutôt que de prévoir du temps à l’ordre du jour. | ||
| + | * Les points considérés comme à faible risque et/ou pour lesquels il n’y a pas de préoccupations à soulever peuvent être considérés comme des « points à l’ordre du jour consensuel ». Les points à l’ordre du jour consensuel ne reçoivent pas de temps de présentation, mais si aucune préoccupation n’est soulevée à la réunion, les points sont considérés comme approuvés. | ||
| + | ==Langues officielles== | ||
| + | * Les réunions du CEAI GC sont bilingues. | ||
| + | ** Les comptes rendus, les présentations et les mises à jour peuvent être présentés dans l’une ou l’autre des langues officielles; les membres peuvent poser des questions et les présentateurs peuvent répondre aux questions dans la langue officielle de leur choix. | ||
| − | + | ==Composition== | |
| − | |||
| − | + | Le CEAI GC est coprésidé par : | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | * Marc Brouillard, dirigeant principal de la technologie pour le GC, Secrétariat du Conseil du Trésor du Canada; | |
| − | + | * Raj Thuppal, dirigeant principal de la technologie, Services partagés Canada. | |
| − | |||
| − | |||
| − | |||
| − | + | Si un membre qui siège au Comité change de poste d’attache, il sera à la discrétion des coprésidents de déterminer si celui-ci doit continuer à participer au Comité ou doit être remplacé afin d’assurer la continuité de l’expérience. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | Les membres peuvent nommer un délégué permanent qui agira à titre de membre suppléant et sera habilité à participer aux discussions en leur nom. Aucun autre remplaçant ou délégué ne sera accepté. | |
| − | + | Si un membre s’absente pour trois réunions consécutives, son adhésion au CEAI sera révoquée par les coprésidents. Le remplaçant désigné peut remplacer un membre seulement si le membre en informe le Secrétariat du BDPI du SCT 48 heures avant la date prévue de la réunion. | |
| − | < | + | <b>Le mandat sera examiné et mis à jour annuellement au cours du deuxième trimestre (date anniversaire).</b> |
| + | </multilang> | ||
| + | {{OCIO_GCEARB_Footer}} | ||
Latest revision as of 08:12, 7 October 2021
Terms of Reference[edit | edit source]
Background[edit | edit source]
On March 23, 2017, the CIO GC established the Government of Canada Enterprise Architecture Review Board (GC EARB) “to further the “whole of government as one enterprise” vision. It is integrated into the larger GC governance structure and looks at alignment of initiatives, system and solution gaps and overlaps, development of new digital capabilities and innovation opportunities, setting technology standards and providing IM-IT investment direction”.
Effective Date[edit | edit source]
The Government of Canada Enterprise Architecture Review Board was established on March 23, 2017. These updated terms of reference were approved by GC EARB on March 1, 2019.
Mandate[edit | edit source]
The Policy on the Management of Information Technology assigns responsibility to the Chief Information Officer of Canada to establish an implement an enterprise architecture review board that is mandated to define current and target architecture standards for the Government of Canada, and review departmental plans to ensure alignment.
Responsibilities[edit | edit source]
GC EARB will:
- Prescribe and recommend approval by the GC CIO government-wide architecture expectations;
- Define current and promote target architecture standards for the Government of Canada; and
- Review departmental plans to ensure alignment to those architecture expectations and standards.
The Directive on the Management of Information Technology requires the GC EARB to review proposals concerned with the design, development, installation and implementation of digital services or solutions, information systems, and applications (“digital initiatives”):
- where a department is willing to invest a minimum of the following amounts in order to address the problem or take advantage of the opportunity:
- $2.5 million dollars for departments without an approved Organizational Project Management Capacity Class or with an approved Organizational Project Management Capacity Class of 1;
- $5 million dollars for departments with an approved Organizational Project Management Capacity Class of 2;
- $10 million dollars for departments with an approved Organizational Project Management Capacity Class of 3;
- $15 million dollars for the Department of National Defence;
- $25 million dollars for departments with an approved Organizational Project Management Capacity Class of 4;
- That involve emerging technologies;
- That require an exception to any applicable Directive or Standard under the Policy on the Management of Information Technology;
- That are categorized at the protected B level or below using a deployment model other than public cloud for application hosting (including infrastructure), application deployment, or application development; or,
- As directed by the Chief Information Officer of Canada.
If the investment meets at least one of the criteria above, the department must bring forward the proposal to GC EARB.
Operation[edit | edit source]
GC EARB meets bi-weekly. As required and at the discretion of the Board’s Co-Chairs, special meetings may be called. Quorum must be met for when there are items requiring a decision. Quorum is defined as at least half of the members or their delegate being present. Should quorum not be met, items for decision will be deferred to the next meeting.
Secretariat support is provided by Committee Secretariat, Office of the Chief Information Officer, Treasury Board of Canada Secretariat.
Working groups and other supporting governance may be created, as necessary and at the direction of the Co-Chairs.
Presentation Requirements[edit | edit source]
The purpose of the GC EARB engagement must be clear (information, endorsement or exemption).
- Departments are encouraged to use the presentation template to ensure consistent provision of content to enable formal architectural assessment.
- Departments are encouraged to use the presentation template to ensure consistent provision of content to enable formal architectural assessment according to the requirements set out in Appendix C (Mandatory Procedures for Enterprise Architecture Assessment) of the Directive on the Management of IT.
- Departments are expected to submit their finalized materials in both official languages to the Office of the Chief Information Officer, Treasury Board of Canada Secretariat (TBS OCIO) no later than one week prior to the planned meeting date. Late materials may result in deferral of the presentation.
- Items that are considered low risk and/or where there are no concerns to raise can be considered as “consent agenda items”. The consent agenda items are not allocated any presentation time however if no concerns are raised at the meeting, the items are considered endorsed.
Membership[edit | edit source]
The GC EARB is co-chaired by:
- Paul Wagner, Chief Technology Officer for the GC, Treasury Board of Canada Secretariat; and
- Matt Davies, Chief Technology Officer, Shared Services Canada
Membership is at the Assistant Deputy Minister level and is determined by the Co-Chairs. The membership will be updated on an annual basis, or as required. All proposed changes to the membership must be submitted to the OCIO Committee Secretariat, who will seek the approval of the Co-Chairs.
Members may appoint one delegate who is at the Director General level or above that will serve as an alternate member and be empowered to participate in discussions on their behalf. No other substitutes or delegates will be accepted.
Members are required to commit to a one year term and are expected to attend the majority of meetings. In the event that a member is absent from 6 or more meetings throughout their term, their membership to the EARB may be revoked by the Co-Chairs. The identified alternate may replace a member only when the member advises OCIO Secretariat 24 hours prior to the scheduled meeting date.
