Line 27: |
Line 27: |
| | | |
| = Terms of Reference= | | = Terms of Reference= |
− |
| |
− | ==Preamble==
| |
− |
| |
− | Treasury Board is responsible, under the Section 7 (1) of the Financial Administration Act, for all matters relating to general administrative policy in the federal public administration including the review of annual and longer term expenditure plans and programs of departments and the determination of priorities with respect therein.
| |
| | | |
| ==Background== | | ==Background== |
| | | |
− | On March 23, 2017, the CIO GC established the [https://www.canada.ca/en/treasury-board-secretariat/services/information-technology/strategic-plan-2017-2021.html 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>. | + | 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 xxx , 2019. | + | 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== |
| | | |
− | [https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=12755#appA 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.
| + | 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. |
− | | |
− | Provide technical recommendations and highlight enterprise-wide directions to the GC CIO for consideration and approval.
| |
| | | |
| ==Responsibilities== | | ==Responsibilities== |
| | | |
− | GC EARB will provide the technical review lens for proposed solutions that are: Enterprise and/or common in nature; public facing; emerging or disruptive technology; cloud services; long-term contract renewals for existing solutions; or proposed architectural exemptions to currently established reference architectures for all departments (as defined in section 2 of the Financial Administration Act).
| |
− |
| |
| 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 Committee Co-Chairs, special meetings may be called for urgent matters. | + | 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. |
− | To ensure continuity and stability of involvement, discussion, and information flow, committee members are encouraged to participate in all meetings.
| + | |
| + | Working groups and other supporting governance may be created, as necessary and at the direction of the Co-Chairs. |
| | | |
| ==Presentation Requirements== | | ==Presentation Requirements== |
Line 66: |
Line 75: |
| 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:GC_EARB_Presenter_GENERAL_JAN14.pptx |template]] to ensure consistent provision of content to enable formal architectural assessment. | | * Departments are encouraged to use the presentation [[Media:GC_EARB_Presenter_GENERAL_JAN14.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. |
− | * Committee Secretariat reserves the right to defer items if presentation materials are submitted late.
| + | * 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. |
− | * Committee Secretariat reserves the right to circulate information items secretarially rather than allocate time on the agenda.
| |
| * 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. |
| | | |
− | ==Official Languages==
| |
− |
| |
− | * GC EARB meetings are bilingual.
| |
− | ** Debriefs, presentations, and updates may be delivered in either official language; members may ask questions and presenters may respond to questions in the official language of their choice.
| |
| | | |
| ==Membership== | | ==Membership== |
Line 81: |
Line 85: |
| | | |
| * Marc Brouillard, Chief Technology Officer for the GC, Treasury Board of Canada Secretariat; and | | * Marc Brouillard, Chief Technology Officer for the GC, Treasury Board of Canada Secretariat; and |
− | * Sarah Paquet, Executive Vice President, Shared Services Canada | + | * Luc Gagnon, Chief Technology Officer, Shared Services Canada |
| | | |
− | If a sitting member of the Committee changes his or her substantive position, the member’s continued participation or replacement will be at the discretion of the Co-Chairs in order to ensure continuity of experience.
| + | 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 permanent delegate 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 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. |
| | | |
− | In the event that a Member is absent for 3 consecutive meetings, their membership to the EARB will be revoked by the Co-Chairs. The identified alternate may replace a member only when the member advises TBS CIOB Secretariat 48 hours prior to the scheduled meeting date. | + | 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. |
| | | |
− | <b>Terms of Reference will be reviewed and updated annually in Q2 (anniversary date).</b>
| |
| | | |
| + | |
| + | <strong>Terms of reference will be reviewed and updated annually in Q2 (anniversary date).</strong> |
| + | |
| | | |
| | | |