Difference between revisions of "GC Enterprise Architecture/Board/When to come"

From wiki
Jump to navigation Jump to search
(Update Service and Digital links)
(add multilang)
(24 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{OCIO_GCEARB_Header}}
+
{{OCIO_GCEA_Header}}
<multilang>  
+
<multilang>
@en|__NOTOC__
+
@en|
= What do I do first? =
+
== '''What do I do first?''' ==
  
<!-- Row-->
+
=== Step 1 ===
<!-- ROW 1 STARTS: -->  
+
'''Self-assess''' against the of your initiative against the "Criteria" in the  <u>[https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=32601 Directive on Service and Digital]</u> to determine if the initiative should be presenting to the GC EARB.
{| width="100%" cellpadding="10" cellspacing=15px
 
  
|-valign="top"
+
Section 4.1.1 the departmental Chief Information Officer (CIO) is responsible for:
|width="25%" style="border: 1px solid steelblue; color: black; background-color: AliceBlue; font-size:1.2em;" |
 
  
1. Conduct a <b>self-assessment</b> of your initiative against the "Criteria" to determine if you should be presenting to the GC EARB
+
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:
|}
 
{| width="100%" cellpadding="10" cellspacing=15px
 
|-valign="top"
 
|width="25%" style="border: 1px dashed steelblue;" |
 
  
<b>CRITERIA</b>: [https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=32601 Directive on Service and Digital]
+
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:
  
*Proposals concerned with the design, development, installation and implementation of digital services or solutions, information systems and applications ("digital initiatives") where the department is willing to invest a minimum of the following amounts in order 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'';
  
:{| width="100%" cellspacing=10px
+
4.1.1.2.1.2$5  million dollars for departments that have an approved Organizational Project Management Capacity Class of 2;
|-valign="top"
 
  
|width="33.3%" style="border: 1px solid lightgrey;" |
+
4.1.1.2.1.3$10  million dollars for departments that have an approved Organizational Project Management Capacity Class of 3;
<!-- COLUMN 1 STARTS: -->
 
* $2.5 million + OPMCA of 0 or 1
 
* $5 million + OPMCA of 2
 
<!-- COLUMN 1 ENDS: -->
 
  
|width="33.3%" style="border: 1px solid lightgrey;"|
+
4.1.1.2.1.4$15  million dollars for the Department of National Defence;
<!-- COLUMN 2 STARTS: -->
 
* $10 million + OPMCA of 3
 
* $15 million Department of National Defence
 
<!-- COLUMN 2 ENDS: -->
 
  
|width="33.3%" style="border: 1px solid lightgrey;"|
+
4.1.1.2.1.5$25  million dollars for departments that have an approved Organizational Project Management Capacity Class of 4;
<!-- COLUMN 3 STARTS: -->
 
* $25 million + OPMCA of 4
 
<!-- COLUMN 3 ENDS: -->
 
|}
 
  
* That involve emerging technologies;
+
4.1.1.2.2That involve emerging technologies;
  
* That require an exception to any applicable Directive or other directives under the Policy on Service and Digital;
+
4.1.1.2.3That require an exception under this directive or other directives under the policy;
  
* 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
+
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
  
* As directed by the Chief Information Officer of Canada.
+
4.1.1.2.5 As directed by the CIO of Canada.
  
<span style="font-size: 1.2em;"><b>Note</b></span>
+
If the investment meets at least one of the criteria above, the department must bring forward the proposal to GC EARB.
  
{| width="100% cellpadding="10" cellspacing=10px
+
=== Step 2 ===
|-valign="top"
+
a. If '''REQUIRED''' to come: '''Complete''' a draft of the [[Media:2020-12-15-GC_EARB_Presenter_GENERAL.pptx|GC EARB Presenter Template]] ([[Media:2020-12-15-GC_EARB_Presenter_GENERAL_FR.pptx|French Presenter Template]]) and send the presentation to the [Mailto:EA.AE@tbs-sct.gc.ca%7CEA.AE@tbs-sct.gc.ca TBS EA team] (EA.AE@tbs-sct.gc.ca)
  
|width="33.3%" style="border: 1px dashed darkblue;" |
+
OR
<!-- COLUMN 1 STARTS: -->
 
<b>1.</b> Please ensure that all proposals submitted for review by the Government of Canada Enterprise Architecture Review Board have <b>first been assessed</b> by the departmental architecture review board where one has been established.
 
<!-- COLUMN 1 ENDS: -->
 
  
|width="33.3%" style="border: 1px dashed darkblue;" |
+
b. If '''NOT REQUIRED''' to come: '''Provide rationale''' in an email then forward to:
<!-- COLUMN 2 STARTS: -->
 
<b>2.</b> Ensure that proposals are submitted to the Government of Canada Enterprise Architecture Review Board following review of <b>[https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=32593&section=procedure&p=C concept cases] </b>for digital projects and <b>before</b> the development of a Treasury Board Submission or Departmental Business Case.
 
<!-- COLUMN 2 ENDS: -->
 
  
|width="33.3%" style="border: 1px dashed darkblue;" | 
+
the [Mailto:EA.AE@tbs-sct.gc.ca%7CEA.AE@tbs-sct.gc.ca TBS EA team] (EA.AE@tbs-sct.gc.ca)
<!-- COLUMN 3 STARTS: -->
 
<b>3.</b> Ensure all departmental initiatives are assessed against and <b>meet the requirements</b> of Appendix A: Mandatory Procedures for Enterprise Architecture Assessment and Appendix B: Mandatory Procedures for Application Programming Interfaces.
 
<!-- COLUMN 3 ENDS: -->
 
|}
 
  
|}
+
== '''Things to note''' ==
<!-- ROW 1 ENDS: -->  
+
Ensure that all proposals submitted for review to GC EARB have first been assessed by your '''DARB''' (Departmental Architecture Review Board) where one has been established as described in the [https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=32601 <u>Directive on Service and Digital.</u>]
  
<!-- ROW 2 STARTS: -->
+
Section 4.1.1.1 The departmental Chief Information Officer (CIO) is responsible for: Chairing a departmental architecture review board that is mandated to review and approve the architecture of all departmental digital initiatives and ensure their alignment with enterprise architectures.
{| width="100%" cellpadding="10" cellspacing=15px
 
  
|-valign="top"
+
Ensure your departmental initiatives are evaluated against and '''align''' to the requirements set out as the <u>[[GC_Enterprise_Architecture/Framework|Enterprise Architecture Framework]]</u>
|width="50%" style="border: 1px solid steelblue; color: black; background-color: AliceBlue;" |
+
=='''How do you go about getting on the agenda?'''==
 +
*Complete a draft of the  [[Media:2020-12-15-GC_EARB_Presenter_GENERAL.pptx|GC EARB Presenter Template.]]  ([[Media:2020-12-15-GC_EARB_Presenter_GENERAL_FR.pptx|French Presenter Template]])
 +
*Email the draft GC EARB presentation to the [mailto:EA.AE@tbs-sct.gc.ca EA team] (EA.AE@tbs-sct.gc.ca)
 +
*GC Enterprise Architecture will contact you to review and conduct initial assessment.
 +
*A tentative GC EARB date to present will then be identified.
 +
== '''Architectural Alignment''' ==
 +
* The TBS EA team will use the details provided in the departmental GCEARB presentation to summarize the alignment to the EA Framework.
  
<span style="font-size:1.2em;">2. <b>REQUIRED</b> to come: <b>Complete</b> the "Presenter" intake presentation below:</span><br>
+
* A summary is prepared that summarizes the level of alignment across business, information, application, technology and security domain, areas of possible concern and finally recommendations for endorsement and any application conditions are noted.
 
<b>TEMPLATE</b>: [[Media:GC_EARB_Presenter_Template-2020-11-26.pptx | GC EARB Presenter Template]]
 
|width="50%" style="border: 1px solid steelblue; color: black; background-color: AliceBlue;" |
 
  
<span style="font-size:1.2em;">2. <b>NOT REQUIRED</b> to come: <b>Provide rationale</b> in email then forward to:</span><br>
+
* This EA summary is shared with the departmental contacts, the GC EARB Co-Chairs prior to the meeting and is presented as the summary slide by the TBS EA at the GC EARB presentation.
 
<b>EMAIL</b>: {{em|EA.AE@tbs-sct.gc.ca}}
 
|}
 
<!-- ROW 2 ENDS: -->
 
  
<!-- ROW 3 STARTS: -->
+
== '''Meeting Logistics – How It Works''' ==
{| width="100%" cellpadding="10" cellspacing=15px
+
'''TBS OCIO Secretariat'''
  
|-valign="top"
+
'''2 weeks''' ahead:
|width="25%" style="border: 1px solid steelblue; color: black; background-color: AliceBlue; font-size:1.2em;" |
 
 
 
3. <b>Send</b> completed presentation or rationale to GC EARB group
 
|}
 
{| width="100%" cellpadding="10" cellspacing=15px
 
|-valign="top"
 
|width="25%" style="border: 1px dashed steelblue;" |
 
 
 
<b>EMAIL</b>: {{em|EA.AE@tbs-sct.gc.ca}}
 
|}
 
<!-- ROW 3 ENDS: -->
 
 
 
 
 
=Things to note=
 
 
 
* Ensure that all proposals submitted for review to GC EARB have first been assessed by your <b>DARB</b> (Departmental Architecture Review Board) where one has been established.
 
* Ensure your departmental initiatives are assessed against and <b>align</b> to the requirements set out as the [GC Architectural Standards].
 
 
 
 
 
=How do you go about getting on the agenda?=
 
 
 
* Complete the presenter intake deck.
 
* Email the deck to the generic mailbox: {{em|EA.AE@tbs-sct.gc.ca}}
 
* GC Enterprise Architecture will review and conduct initial assessment.
 
* Tentative date to present is secured and you will be notified by email.
 
 
 
 
 
=Architectural Assessment=
 
 
 
* GC Enterprise Architecture will review your project material against the [https://www.canada.ca/en/government/system/digital-government/government-canada-digital-standards.html GC Digital] and [[Government_of_Canada_Architectural_Standards | GC Architectural Standards]].
 
* A summary is prepared that notes areas of alignment and areas of possible concern.
 
* This summary is shared with the departmental contacts and the EARB Co-Chairs prior to the meeting.
 
 
 
 
 
=Meeting Logistics – How It Works=
 
 
 
<span style="font-size: 1.2em; font-weight: bold;"> TBS OCIO Secretariat </span>
 
 
 
<b>2 weeks</b> ahead:
 
 
* The Secretariat will extend the calendar invitations to the presenters (typically 1-2 people)
 
* The Secretariat will extend the calendar invitations to the presenters (typically 1-2 people)
 +
'''1 week''' ahead:
 +
* FINAL presentation materials (both French and English) are required.
  
<b>1 week</b> ahead:
+
* Packages are prepared and distributed to GC EARB members for their review prior to the scheduled meeting.
* FINAL presentation materials (both French and English) are required.
+
'''Day of:'''
* Packages are prepared and distributed to EARB members for their review prior to the scheduled meeting.
+
* Documents for the meeting are posted on <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 GCEARB GCconnex site]</u>.
 +
'''Virtual:'''
 +
* Attend via Join Microsoft Teams Meeting link found in the meeting invite
 +
'''In Person:'''
 +
* Present yourself to the separate security TABLE and see the OCIO Secretariat Representative. (Note: It is recommended to arrive 15 minutes prior to the meeting)
  
<b>Day of:</b>
 
* Present yourself to the separate security TABLE and see the OCIO Secretariat Representative.  (Note:  It is recommended to arrive 15 minutes prior to the meeting)
 
 
* You will be signed in and provided a temporary security pass.
 
* You will be signed in and provided a temporary security pass.
 +
 
* Make your way to the identified meeting room.
 
* Make your way to the identified meeting room.
 +
 
* Once in the meeting room, please RETURN the temporary pass to OCIO representatives.
 
* Once in the meeting room, please RETURN the temporary pass to OCIO representatives.
 
+
'''Post EARB Meeting:'''
<b>Post EARB Meeting:</b>
 
 
* A Record of Discussion (RoD) is prepared after the meeting to capture any highlights that the Board noted, as well as the decision of the Board with any conditions.
 
* A Record of Discussion (RoD) is prepared after the meeting to capture any highlights that the Board noted, as well as the decision of the Board with any conditions.
* The RoD may take several weeks to be officially published, but will be made available on the GC Wiki site.
 
 
 
<!-- FRENCH -->
 
@fr|__NOTOC__
 
= Que dois-je faire en premier? =
 
 
<!-- Row-->
 
<!-- ROW 1 STARTS: -->
 
{| width="100%" cellpadding="10" cellspacing=15px
 
 
|-valign="top"
 
|width="25%" style="border: 1px solid steelblue; color: black; background-color: AliceBlue; font-size:1.2em;" |
 
 
1. Procéder à une <b>autoévaluation</b> de votre initiative en fonction des « critères » afin de déterminer si vous devriez faire une présentation au CEAI GC.
 
|}
 
{| width="100%" cellpadding="10" cellspacing=15px
 
|-valign="top"
 
|width="25%" style="border: 1px dashed steelblue;" |
 
 
<b>CRITÈRES</b>: [https://www.tbs-sct.gc.ca/pol/doc-fra.aspx?id=32601 Directive sur les services et le numérique]
 
 
*Propositions concernant la conception, le développement, l’installation et la mise en œuvre de services ou de solutions numériques, de systèmes d’information et d’applications (« initiatives numériques ») lorsque le ministère est disposé à investir un minimum des montants suivants afin de régler le problème ou de profiter de l’occasion :
 
 
:{| width="100%" cellspacing=10px
 
|-valign="top"
 
 
|width="33.3%" style="border: 1px solid lightgrey;" |
 
<!-- COLUMN 1 STARTS: -->
 
* 2,5 millions de dollars + ECOGP de 0 ou 1
 
* 5 millions de dollars + ECOGP de 2
 
<!-- COLUMN 1 ENDS: -->
 
 
|width="33.3%" style="border: 1px solid lightgrey;"|
 
<!-- COLUMN 2 STARTS: -->
 
* 10 millions de dollars + ECOGP de 3
 
* 15 millions de dollars du ministère de la Défense nationale
 
<!-- COLUMN 2 ENDS: -->
 
 
|width="33.3%" style="border: 1px solid lightgrey;"|
 
<!-- COLUMN 3 STARTS: -->
 
* 25 millions de dollars + ECOGP de 4
 
<!-- COLUMN 3 ENDS: -->
 
|}
 
 
* qui comportent des technologies émergentes;
 
* qui exigent une exception à la présente directive ou à d’autres directives liées à la Politique sur les services et le numérique;
 
* qui sont catégorisés au niveau Protégé B ou à un niveau inférieur à l’aide d’un modèle de déploiement autre que le nuage public pour l’hébergement d’applications (y compris l’infrastructure), le déploiement d’applications ou le développement d’applications; ou
 
* selon les indications du dirigeant principal de l’information du Canada.
 
 
<span style="font-size: 1.2em;"><b>Remarque</b></span>
 
 
{| width="100% cellpadding="10" cellspacing=10px
 
|-valign="top"
 
 
|width="33.3%" style="border: 1px dashed darkblue;" |
 
<!-- COLUMN 1 STARTS: -->
 
<b>1.</b> Veillez à ce que les propositions présentées à des fins d’études au Conseil d’examen de l’architecture intégrée du gouvernement du Canada aient <b>d’abord été évaluées</b> par le conseil d’examen de l’architecture du ministère, lorsqu’il en existe un.
 
<!-- COLUMN 1 ENDS: -->
 
 
|width="33.3%" style="border: 1px dashed darkblue;" |
 
<!-- COLUMN 2 STARTS: -->
 
<b>2.</b> Veillez à ce que les propositions soient présentées au Conseil d’examen de l’architecture intégrée du gouvernement du Canada (CEAI GC) après l’examen des [https://www.tbs-sct.gc.ca/pol/doc-fra.aspx?id=32593 cas conceptuels] pour les projets numériques et <b>avant</b> l’élaboration d’une présentation au Conseil du Trésor ou d’une analyse de rentabilisation ministérielle.
 
<!-- COLUMN 2 ENDS: -->
 
 
|width="33.3%" style="border: 1px dashed darkblue;" | 
 
<!-- COLUMN 3 STARTS: -->
 
<b>3.</b> Veillez à ce que toutes les initiatives ministérielles soient évaluées en fonction des <b>exigences</b> de l’annexe A : Procédures obligatoires pour l’évaluation de l’architecture intégrée et de l’annexe B : Procédures obligatoires pour les interfaces de programmation des applications.
 
<!-- COLUMN 3 ENDS: -->
 
|}
 
 
|}
 
<!-- ROW 1 ENDS: -->
 
 
<!-- ROW 2 STARTS: -->
 
{| width="100%" cellpadding="10" cellspacing=15px
 
 
|-valign="top"
 
|width="25%" style="border: 1px solid steelblue; color: black; background-color: AliceBlue; font-size:1.2em;" |
 
 
2.  <b>Remplir</b> la présentation des demandes du « Présentateur ».
 
|}
 
{| width="100%" cellpadding="10" cellspacing=15px
 
|-valign="top"
 
|width="25%" style="border: 1px dashed steelblue;" |
 
 
<b>MODÈLE </b>:<span style="font-size: 1.5em;"><b>[[Media:GC_EARB_Presenter_GENERAL_2019-09-13_FR.PPTX | Modèle du présentateur du CEAI]]</b></span>
 
|}
 
<!-- ROW 2 ENDS: -->
 
 
<!-- ROW 3 STARTS: -->
 
{| width="100%" cellpadding="10" cellspacing=15px
 
 
|-valign="top"
 
|width="25%" style="border: 1px solid steelblue; color: black; background-color: AliceBlue; font-size:1.2em;" |
 
 
3. <b>Envoyer</b> la présentation remplie au groupe du CEAI GC.
 
|}
 
{| width="100%" cellpadding="10" cellspacing=15px
 
|-valign="top"
 
|width="25%" style="border: 1px dashed steelblue;" |
 
 
<b>COURRIEL </b>: {{em|EA.AE@tbs-sct.gc.ca}}
 
|}
 
<!-- ROW 3 ENDS: -->
 
 
 
=Points à prendre en note=
 
 
* Veillez à ce que toutes les propositions soumises à l’examen du CEAI GC aient d’abord été évaluées par votre <b>CEAM</b> (Conseil d’examen de l’architecture du Ministère), lorsqu’une telle commission a été établie.
 
* Veillez à ce que les initiatives de votre ministère soient évaluées en fonction des exigences énoncées dans les [[Government_of_Canada_Architectural_Standards |Normes architecturales du GC]] et qu’elles sont <b>harmonisées</b> avec celles-ci.
 
 
 
=Comment procédez-vous pour vous inscrire à l’ordre du jour?=
 
 
* Remplissez le dossier de présentation des demandes du présentateur.
 
* Envoyez le dossier de présentation par courriel à la boîte aux lettres générique : {{em|EA.AE@tbs-sct.gc.ca}}
 
* L’architecture intégrée du GC examinera et effectuera l’évaluation initiale.
 
* La date provisoire de présentation est fixée et vous serez avisé par courriel.
 
 
 
=Évaluation de l’architecture=
 
 
* L’architecture intégrée du GC examinera les documents de votre projet en fonction du [https://www.canada.ca/fr/gouvernement/systeme/gouvernement-numerique/normes-numeriques-gouvernement-canada.html GC Numérique] et [[Government_of_Canada_Architectural_Standards | Normes architecturales du GC]].
 
* Un résumé est préparé pour indiquer les secteurs d’harmonisation et les secteurs de préoccupation possibles.
 
* Ce résumé est communiqué aux personnes-ressources du Ministère et aux coprésidents du CEAI avant la réunion.
 
 
 
=Logistique des réunions – Comment ça fonctionne=
 
 
<span style="font-size: 1.2em; font-weight: bold;"> Secrétariat du BDPI du SCT</span>
 
 
<b>Deux semaines</b> à l’avance :
 
* Le Secrétariat enverra les invitations au calendrier aux présentateurs (généralement une ou deux personnes).
 
 
<b>Une semaine</b> à l’avance :
 
* Les documents de présentation FINAUX (en français et en anglais) sont exigés.
 
* Des trousses sont préparées et distribuées aux membres du CEAI pour examen avant la réunion prévue.
 
 
<b>Jour de l’exercice</b>
 
* Présentez-vous à la TABLE de sécurité distincte et parlez au représentant du secrétariat du BDPI. (Nota : Il est recommandé d’arriver 15 minutes avant la réunion.)
 
* Vous recevrez un laissez-passer de sécurité temporaire.
 
* Rendez-vous à la salle de réunion désignée.
 
* Une fois dans la salle de réunion, veuillez RETOURNER le laissez-passer temporaire aux représentants du BDPI
 
  
<b>Après la réunion du CEAI :</b>
+
* The RoD may take several weeks to be officially published, but will be made available on the <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 GCEARB GCconnex site]</u>.
* Un compte rendu des discussions (CRD) est préparé après la réunion pour présenter les points saillants que le Conseil a notés, ainsi que la décision du Conseil, sous réserve de certaines conditions.
+
@fr|
* Le compte rendu des décisions peut prendre plusieurs semaines avant d’être publié officiellement, mais il sera accessible par l’entremise du site Wiki du GC.
+
To be translated
 
</multilang>
 
</multilang>
{{OCIO_GCEARB_Footer}}
 

Revision as of 12:34, 5 January 2021

What do I do first?[edit | edit source]

Step 1[edit | edit source]

Self-assess against the of your initiative against the "Criteria" in the  Directive on Service and Digital to determine if the initiative should be presenting to the GC EARB.

Section 4.1.1 the 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.5 As 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.

Step 2[edit | edit source]

a. If REQUIRED to come: Complete a draft of the GC EARB Presenter Template (French Presenter Template) and send the presentation to the TBS EA team (EA.AE@tbs-sct.gc.ca)

OR

b. If NOT REQUIRED to come: Provide rationale in an email then forward to:

the TBS EA team (EA.AE@tbs-sct.gc.ca)

Things to note[edit | edit source]

Ensure that all proposals submitted for review to GC EARB have first been assessed by your DARB (Departmental Architecture Review Board) where one has been established as described in the Directive on Service and Digital.

Section 4.1.1.1 The departmental Chief Information Officer (CIO) is responsible for: Chairing a departmental architecture review board that is mandated to review and approve the architecture of all departmental digital initiatives and ensure their alignment with enterprise architectures.

Ensure your departmental initiatives are evaluated against and align to the requirements set out as the Enterprise Architecture Framework

How do you go about getting on the agenda?[edit | edit source]

  • Complete a draft of the GC EARB Presenter Template. (French Presenter Template)
  • Email the draft GC EARB presentation to the EA team (EA.AE@tbs-sct.gc.ca)
  • GC Enterprise Architecture will contact you to review and conduct initial assessment.
  • A tentative GC EARB date to present will then be identified.

Architectural Alignment[edit | edit source]

  • The TBS EA team will use the details provided in the departmental GCEARB presentation to summarize the alignment to the EA Framework.
  • A summary is prepared that summarizes the level of alignment across business, information, application, technology and security domain, areas of possible concern and finally recommendations for endorsement and any application conditions are noted.
  • This EA summary is shared with the departmental contacts, the GC EARB Co-Chairs prior to the meeting and is presented as the summary slide by the TBS EA at the GC EARB presentation.

Meeting Logistics – How It Works[edit | edit source]

TBS OCIO Secretariat

2 weeks ahead:

  • The Secretariat will extend the calendar invitations to the presenters (typically 1-2 people)

1 week ahead:

  • FINAL presentation materials (both French and English) are required.
  • Packages are prepared and distributed to GC EARB members for their review prior to the scheduled meeting.

Day of:

Virtual:

  • Attend via Join Microsoft Teams Meeting link found in the meeting invite

In Person:

  • Present yourself to the separate security TABLE and see the OCIO Secretariat Representative. (Note: It is recommended to arrive 15 minutes prior to the meeting)
  • You will be signed in and provided a temporary security pass.
  • Make your way to the identified meeting room.
  • Once in the meeting room, please RETURN the temporary pass to OCIO representatives.

Post EARB Meeting:

  • A Record of Discussion (RoD) is prepared after the meeting to capture any highlights that the Board noted, as well as the decision of the Board with any conditions.
  • The RoD may take several weeks to be officially published, but will be made available on the GCEARB GCconnex site.