Difference between revisions of "GC Enterprise Architecture/Board"
Jana.jessome (talk | contribs) |
(changed links to templates to the new versions) |
||
(88 intermediate revisions by 11 users not shown) | |||
Line 1: | Line 1: | ||
− | + | {{OCIO_GCEA_Header}} | |
+ | <multilang> | ||
+ | @en| | ||
+ | Note: These revised ToR are draft and awaiting final approval. Please send us any comments that you may have. | ||
− | + | == Terms of Reference == | |
− | + | === Background === | |
− | + | On March 23, 2017, the CIO of Canada established the Government of Canada Enterprise Architecture Review Board (GC EARB). Since then, it has continued to support the achievement of the digital government vision: | |
− | |||
− | |||
− | + | “The Government of Canada is an open and service-oriented organization that delivers programs and services to citizens and businesses in simple, modern and effective ways that are optimized for digital and available anytime, anywhere and from any device. | |
− | + | Digitally, the GC must operate as one to benefit all Canadians.” | |
− | + | === Effective Date === | |
+ | These updated terms of reference are planned for endorsement by GC EARB and approval by the Chief Information Officer of Canada in early 2021. | ||
− | + | === Mandate === | |
+ | The [https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=32603 <u>Policy on Service and Digital</u>] assigns responsibility to the Chief Information Officer of Canada to: | ||
− | + | Section 4.1.2.3 Prescribing expectations with regard to enterprise architecture. | |
− | + | Section 4.1.2.4 to establish and chair an enterprise architecture review board that is mandated to define current and target architecture standards for the Government of Canada and review departmental proposals for alignment. | |
− | + | === Responsibilities === | |
+ | GC EARB will: | ||
+ | Recommend endorsements of expectations with regard to enterprise architecture that will be prescribed by the CIO of Canada. | ||
− | + | Define current and target architecture standards for the Government of Canada and review departmental proposals for alignment. | |
− | |||
− | < | + | The <u>[https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=32601 Directive on Service and Digital articulates]</u> how Government of Canada organizations manage service delivery, information and data, information technology, and cyber security in the digital era. |
− | + | Section 4.1.1the departmental Chief Information Officer (CIO) is responsible for: | |
− | |||
− | + | 4.1.1.2 Submitting to the Government of Canada enterprise architecture review board proposals concerned with the design, development, installation and implementation of digital initiatives: | |
− | + | 4.1.1.2.1 Where the department is willing to invest a minimum of the following amounts to address the problem or take advantage of the opportunity: | |
− | |||
− | |||
− | + | 4.1.1.2.1.1 $2.5 million dollars for departments that do not have an approved Organizational Project Management Capacity Class or that have an approved Organizational Project Management Capacity Class of 1 according to the ''Directive on the Management of Projects and Programmes''; | |
− | |||
+ | 4.1.1.2.1.2$5 million dollars for departments that have an approved Organizational Project Management Capacity Class of 2; | ||
− | + | 4.1.1.2.1.3$10 million dollars for departments that have an approved Organizational Project Management Capacity Class of 3; | |
− | + | 4.1.1.2.1.4$15 million dollars for the Department of National Defence; | |
− | |||
− | |||
− | + | 4.1.1.2.1.5$25 million dollars for departments that have an approved Organizational Project Management Capacity Class of 4; | |
− | + | 4.1.1.2.2That involve emerging technologies; | |
− | |||
− | |||
+ | 4.1.1.2.3That require an exception under this directive or other directives under the policy; | ||
+ | 4.1.1.2.4That 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 | ||
+ | 4.1.1.2.5As directed by the CIO of Canada. | ||
− | + | If the investment meets at least one of the criteria above, the department must bring forward the proposal to GC EARB. | |
− | + | === Operation === | |
+ | 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. | |
− | |||
− | < | + | Records of discussions and GC EARB presentations are posted on the GC Enterprise Architecture Review Board <u>[https://gcconnex.gc.ca/groups/profile/29755185/gc-enterprise-architecture-review-board-comite-dexamen-de-larchitecture-integree-du-gc-comite-dexamen-de-larchitecture-dentreprise-du-gc?language=en GCconnex page.]</u> |
− | |||
− | |||
− | + | Working groups and other supporting governance may be created, as necessary and at the direction of the Co-Chairs. | |
− | |||
+ | === Presentation Requirements === | ||
+ | The purpose of the GC EARB engagement must be clear (information or endorsement). | ||
+ | * Departments are requested to use the GC EARB Presenter Template <b>([[Media:2022-11-30_GC_EARB_Presenter_GENERAL_EN.pptx|English Template]] / [[Media:2022-11-30_GC_EARB_Presenter_GENERAL_FR.pptx|French Template]])</b> and ensure consistent provision of content to enable formal architectural assessment according to the requirements set out in the Service and Digital Target Enterprise Architecture and the GC Enterprise Architecture Framework. | ||
+ | * Departments are expected to submit their initial draft materials to the Office of the Chief Information Officer, Treasury Board of Canada Secretariat (TBS OCIO) no later than three weeks prior to the planned meeting date to initiate discussions with the TBS EA team to allow time for their review and analysis. | ||
+ | * 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, and if no concerns are raised at the meeting, the items are considered endorsed. | ||
+ | * Items that are informational or follow-up reports on conditions or actions from previous presentations, and where there are no concerns to raise, can be considered as “consent agenda items.” The review agenda items are not allocated any presentation time at the meeting. Departments are requested to use the Condition Templates [[Media:GCEARB Condition Template (DRAFT).pptx|DRAFT English GC EARB Condition Template]] / [[Media:GCEARB Condition Template (DRAFT)-FR.pptx|DRAFT French GC EARB Condition Template]] to demonstrate compliance with conditions. | ||
− | + | === Membership === | |
+ | The GC EARB is co-chaired by: | ||
+ | * Chief Information Security and Technology Officer (CISTO)<sup>1</sup> for the GC, Treasury Board of Canada Secretariat; and | ||
+ | * 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 [Mailto:ciob-ddpi@tbs-sct.gc.ca 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. | |
− | + | <sup>1</sup> The Policy on Service and Digital states that “The Chief Information Officer (CIO) of Canada is responsible for … Establishing and chairing an enterprise architecture review board.” Following the practice established over the initial years of GC EARB, the CIO may delegate the co-chair role to the CISTO. | |
− | < | + | @fr| |
− | | | + | To be translated |
+ | == Termes de la Référence == | ||
+ | === Contexte === | ||
+ | Sur le 23 mars 2017, le DPI du Canada a créé le Conseil d’examen de l’architecture d’intégrée du gouvernement du Canada (CEAI GC). Depuis, il n’a cessé de soutenir la réalisation de la vision numérique du gouvernement: | ||
− | + | « Le gouvernement du Canada est un organisme ouvert et axé sur les services qui offre des programmes et des services aux citoyens et aux operations de façon simple, moderne et efficace, optimisés pour le numérique et disponibles en tout temps, n’importe où et à partir de n’importe quel appareil. Sur le plan numérique, le GC doit fonctionner comme un seul homme au profit de tous les Canadiens.» | |
− | + | === Date d’Entrée en Vigueur === | |
+ | Ces termes de la référence mis à jour devrait être approuvé par le CEAI GC et approuvé par le dirigeant principal de l’information du Canada au début de 2021. | ||
− | + | === Mandat === | |
− | + | La [https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=32603 <u>Politique sur les services et le numérique</u>] attribue au dirigeant principal de l’information du Canada la responsabilité de: | |
− | < | + | <b>Section 4.1.2.3</b> Prescrire des attentes en matière d’architecture d’entreprise. |
− | |||
− | |||
− | + | <b>Section 4.1.2.4</b> Établir et présider un comité d’examen de l’architecture d’entreprise chargé de définir les normes d’architecture actuelles et cibles pour le gouvernement du Canada et d’examiner les propositions ministérielles en vue de leur harmonisation. | |
− | + | === Responsabilités === | |
− | |||
+ | CEAI GC va: | ||
− | + | Recommander l’approbation des attentes à l’égard de l’architecture d’entreprise qui seront prescrites par le DPI du Canada. | |
− | + | Définir les normes d’architecture actuelles et cibles pour le gouvernement du Canada et examiner les propositions ministérielles en vue de leur harmonisation. | |
− | |||
− | |||
− | + | La <u>[https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=32601 directive sur les services et le numérique articule]</u> la façon dont les organismes du gouvernement du Canada gèrent la prestation de services, l’information et les données, les technologies de l’information et la cybersécurité à l’ère numérique. | |
− | + | <b>Section 4.1.1</b> le dirigeant principal de l’information (DPI) ministériel est responsable des éléments suivants: | |
− | < | ||
− | |||
+ | : <b>4.1.1.2</b> Soumettre au comité d’examen de l’architecture d’intégrée du gouvernement du Canada des propositions concernant la conception, le développement, l’installation et la mise en œuvre d’initiatives numériques: | ||
+ | ::<b>4.1.1.2.1</b> Lorsque le ministère est prêt à investir au moins les montants suivants pour régler le problème ou profiter de l’occasion: | ||
− | < | + | ::::<b>4.1.1.2.1.1</b> $2.5 millions de dollars pour les ministères qui n’ont pas de catégorie de capacité de gestion de projet organisationnel approuvée, ou qui ont une classe de capacité de gestion de projet organisationnel approuvée de 1 selon la ''Directive sur la gestion des projets et programmes''; |
+ | ::::<b>4.1.1.2.1.2</b> $5 millions de dollars pour les ministères qui ont une catégorie de capacité de gestion de projet organisationnel approuvée de 2; | ||
− | + | ::::<b>4.1.1.2.1.3</b> $10 millions de dollars pour les ministères qui ont une classe de capacité de gestion de projet organisationnel approuvée de 3; | |
− | + | ::::<b>4.1.1.2.1.4</b> $15 millions de dollars pour le ministère de la Défense nationale; | |
− | |||
− | < | ||
− | |||
+ | ::::<b>4.1.1.2.1.5</b> $25 millions de dollars pour les ministères qui ont une classe de capacité de gestion de projet organisationnel approuvée de 4; | ||
+ | ::<b>4.1.1.2.2</b> Cela implique des technologies émergentes; | ||
− | < | + | ::<b>4.1.1.2.3</b> Qui nécessitent une exception en vertu de la présente directive ou d’autres directives en vertu de la politique; |
− | |||
− | + | ::<b>4.1.1.2.4</b> Qui sont classés au niveau B protégé ou inférieur à l’aide d’un modèle de déploiement autre que le cloud public pour l’hébergement d’applications (y compris l’infrastructure), le déploiement d’applications ou le développement d’applications; ou | |
− | |||
− | |||
− | |||
− | |||
− | < | + | ::<b>4.1.1.2.5</b> Selon les directives du DPI du Canada. |
− | |||
− | |||
− | |||
− | |||
− | + | Si l’investissement répond à au moins un des critères ci-dessus, le ministère doit présenter la proposition au CEAI GC. | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | === Opération === | |
+ | CEAI GC se réunit toutes les deux semaines. Au besoin et à la discrétion des coprésidents du Conseil, des réunions extraordinaires peuvent être convoquées. Le quorum doit être atteint lorsqu’il y a des éléments nécessitant une décision. Le quorum est défini comme étant présent au moins la moitié des membres ou de leur délégué. Si le quorum n’est pas atteint, les points à décider seront reportés à la prochaine réunion. | ||
− | + | L’appui du Secrétariat est assuré par le Secrétariat du Comité, le Bureau du dirigeant principal de l’information et le Secrétariat du Conseil du Trésor du Canada. | |
− | < | + | Les comptes rendus des discussions et des présentations du GC EARB sont affichés sur le Comité d’examen de l’architecture d’intégrée du GC <u>[https://gcconnex.gc.ca/groups/profile/29755185/gc-enterprise-architecture-review-board-comite-dexamen-de-larchitecture-integree-du-gc-comite-dexamen-de-larchitecture-dentreprise-du-gc?language=en Page GCconnex.]</u> |
+ | |||
+ | Des groupes de travail et d’autres organismes de soutien à la gouvernance peuvent être créés, au besoin et sous la direction des coprésidents. | ||
+ | |||
+ | === Exigences de Présentation === | ||
+ | |||
+ | L’objectif de la mission du CEAI GC doit être clair (information ou approbation). | ||
+ | |||
+ | * Les ministères sont priés d’utiliser le Modèle de présentateur CEAI GC <b>([[Media:2022-11-30_GC_EARB_Presenter_GENERAL_EN.pptx|Modèle anglais]] / [[Media:2022-11-30_GC_EARB_Presenter_GENERAL_FR.pptx|Modèle français]])</b> et assurer une fourniture cohérente de contenu pour permettre une évaluation architecturale formelle conformément aux exigences énoncées dans l’architecture d’entreprise de service et de cible numérique et le cadre d’architecture d’entreprise du GC. | ||
+ | * On s’attend à ce que les ministères soumettent leurs documents préliminaires initiaux au Bureau du dirigeant principal de l’information, Secrétariat du Conseil du Trésor du Canada (BCIO du SCT) au plus tard trois semaines avant la date prévue de la réunion, afin d’entamer des discussions avec l’équipe d’AI du SCT afin de leur donner le temps de les examiner et de les analyser. | ||
+ | * Les points qui sont 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 de consentement à l’ordre du jour ». Toutefois, les points de l’ordre du jour relatifs au consentement ne se voient attribuer aucun temps de présentation et, si aucune préoccupation n’est soulevée lors de la réunion, les points sont considérés comme approuvés. | ||
+ | * Les points qui sont des rapports d’information ou de suivi sur les conditions ou les mesures prises lors de présentations antérieures, et pour lesquels il n’y a pas de préoccupations à soulever, peuvent être considérés comme des « points de consentement à l’ordre du jour ». Les points de l’ordre du jour de l’examen ne sont pas attribués de temps de présentation à la réunion. Les ministères sont priés d’utiliser les modèles de conditions [[Media:GCEARB Condition Template (DRAFT).pptx|ÉBAUCHE de la Modèle de condition du CEAI GC en anglais]] / [[Media:GCEARB Condition Template (DRAFT)-FR.pptx|ÉBAUCHE de la Modèle de condition du CEAI GC en francais]] pour démontrer le respect des conditions. | ||
+ | |||
+ | === Adhésion === | ||
+ | Le GC EARB est coprésidé par: | ||
+ | * Dirigeante principale de la sécurité de l’information et de la technologie (DPSIT) <sup>1</sup> pour le GC, Secrétariat du Conseil du Trésor du Canada; et | ||
+ | * Dirigeant Principal de la Technologie, Services Partagés Canada | ||
+ | La composition est au niveau du sous-ministre adjoint et est déterminée par les coprésidents. L’adhésion sera mise à jour sur une base annuelle ou au besoin. Tous les changements proposés à la composition doivent être soumis au [Mailto:ciob-ddpi@tbs-sct.gc.ca Secrétariat du Comité du BCIO ], qui demandera l’approbation des coprésidents. | ||
+ | |||
+ | Les membres peuvent nommer un délégué qui est au niveau du directeur général ou au-dessus qui servira de membre suppléant et sera habilité à participer aux discussions en leur nom. Aucun autre suppléant ou délégué ne sera accepté. | ||
+ | |||
+ | Les membres sont tenus de s’engager pour un mandat d’un an et sont censés assister à la majorité des réunions. Dans le cas où un membre est absent de 6 réunions ou plus tout au long de son mandat, son adhésion à le CEAI peut être révoquée par les coprésidents. Le suppléant désigné ne peut remplacer un membre que lorsqu’il avise le Secrétariat du BCIO 24 heures avant la date prévue de la réunion. | ||
+ | |||
+ | <sup>1</sup> La Politique sur les services et le numérique stipule que « le dirigeant principal de l’information (DPI) du Canada est responsable de... Établir et présider un comité d’examen de l’architecture d’entreprise. Suivant la pratique établie au cours des premières années du CEAI GC, le DPI peut déléguer le rôle de coprésident au DPSIT. | ||
+ | |||
+ | |||
+ | </multilang> |
Latest revision as of 12:20, 30 January 2023
Note: These revised ToR are draft and awaiting final approval. Please send us any comments that you may have.
Terms of Reference[edit | edit source]
Background[edit | edit source]
On March 23, 2017, the CIO of Canada established the Government of Canada Enterprise Architecture Review Board (GC EARB). Since then, it has continued to support the achievement of the digital government vision:
“The Government of Canada is an open and service-oriented organization that delivers programs and services to citizens and businesses in simple, modern and effective ways that are optimized for digital and available anytime, anywhere and from any device.
Digitally, the GC must operate as one to benefit all Canadians.”
Effective Date[edit | edit source]
These updated terms of reference are planned for endorsement by GC EARB and approval by the Chief Information Officer of Canada in early 2021.
Mandate[edit | edit source]
The Policy on Service and Digital assigns responsibility to the Chief Information Officer of Canada to:
Section 4.1.2.3 Prescribing expectations with regard to enterprise architecture.
Section 4.1.2.4 to establish and chair an enterprise architecture review board that is mandated to define current and target architecture standards for the Government of Canada and review departmental proposals for alignment.
Responsibilities[edit | edit source]
GC EARB will:
Recommend endorsements of expectations with regard to enterprise architecture that will be prescribed by the CIO of Canada.
Define current and target architecture standards for the Government of Canada and review departmental proposals for alignment.
The Directive on Service and Digital articulates how Government of Canada organizations manage service delivery, information and data, information technology, and cyber security in the digital era.
Section 4.1.1the departmental Chief Information Officer (CIO) is responsible for:
4.1.1.2 Submitting to the Government of Canada enterprise architecture review board proposals concerned with the design, development, installation and implementation of digital initiatives:
4.1.1.2.1 Where the department is willing to invest a minimum of the following amounts to address the problem or take advantage of the opportunity:
4.1.1.2.1.1 $2.5 million dollars for departments that do not have an approved Organizational Project Management Capacity Class or that have an approved Organizational Project Management Capacity Class of 1 according to the Directive on the Management of Projects and Programmes;
4.1.1.2.1.2$5 million dollars for departments that have an approved Organizational Project Management Capacity Class of 2;
4.1.1.2.1.3$10 million dollars for departments that have an approved Organizational Project Management Capacity Class of 3;
4.1.1.2.1.4$15 million dollars for the Department of National Defence;
4.1.1.2.1.5$25 million dollars for departments that have an approved Organizational Project Management Capacity Class of 4;
4.1.1.2.2That involve emerging technologies;
4.1.1.2.3That require an exception under this directive or other directives under the policy;
4.1.1.2.4That 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
4.1.1.2.5As directed by the CIO 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.
Records of discussions and GC EARB presentations are posted on the GC Enterprise Architecture Review Board GCconnex page.
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 or endorsement).
- Departments are requested to use the GC EARB Presenter Template (English Template / French Template) and ensure consistent provision of content to enable formal architectural assessment according to the requirements set out in the Service and Digital Target Enterprise Architecture and the GC Enterprise Architecture Framework.
- Departments are expected to submit their initial draft materials to the Office of the Chief Information Officer, Treasury Board of Canada Secretariat (TBS OCIO) no later than three weeks prior to the planned meeting date to initiate discussions with the TBS EA team to allow time for their review and analysis.
- 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, and if no concerns are raised at the meeting, the items are considered endorsed.
- Items that are informational or follow-up reports on conditions or actions from previous presentations, and where there are no concerns to raise, can be considered as “consent agenda items.” The review agenda items are not allocated any presentation time at the meeting. Departments are requested to use the Condition Templates DRAFT English GC EARB Condition Template / DRAFT French GC EARB Condition Template to demonstrate compliance with conditions.
Membership[edit | edit source]
The GC EARB is co-chaired by:
- Chief Information Security and Technology Officer (CISTO)1 for the GC, Treasury Board of Canada Secretariat; and
- 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.
1 The Policy on Service and Digital states that “The Chief Information Officer (CIO) of Canada is responsible for … Establishing and chairing an enterprise architecture review board.” Following the practice established over the initial years of GC EARB, the CIO may delegate the co-chair role to the CISTO.