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

From wiki
Jump to navigation Jump to search
(37 intermediate revisions by 5 users not shown)
Line 1: Line 1:
__NOTOC__
+
{{OCIO_GCEARB_Header}}
 
+
<multilang>  
[[Image:GCEARB_logo.png|500px|left|Government of Canada Enterprise Architecture Review Board Logo]]
+
@en|__NOTOC__
 
 
<!-- NAV -->
 
 
 
{| class="FCK__ShowTableBorders" style="border-right: 0px; border-top: 0px; border-left: 0px; border-bottom: 0px; background-color: #008080" width="100%" align="center"
 
|-
 
|-
 
| style="border-right: white 1px ridge; padding-right: 0px; padding-left: 0px; padding-bottom: 2px; padding-top: 2px; text-align: center; font-family: (Cooper black); font-size: 13pt" width="10%" | '''[[Governance_for_Digital_Solutions|<span style="color: snow">'''Home'''</span>]]'''
 
 
 
| style="border-right: white 1px ridge; padding-right: 0px; padding-left: 0px; padding-bottom: 2px; padding-top: 2px; text-align: center; font-family: (Cooper black); font-size: 13pt" width="10%" | '''[[What_is_EARB|<span style="color: Snow">'''What is EARB'''</span>]]'''
 
 
 
| style="border-right: white 1px ridge; padding-right: 0px; padding-left: 0px; padding-bottom: 2px; padding-top: 2px; text-align: center; font-family: (Cooper black); font-size: 13pt" width="11%" | '''[[EARB_When_to_come|<span style="color: Snow">'''When to come to EARB'''</span>]] '''
 
 
 
| style="border-right: white 1px ridge; padding-right: 0px; padding-left: 0px; padding-bottom: 2px; padding-top: 2px; text-align: center; font-family: (Cooper black); font-size: 13pt" width="11%" | '''[[EARB_Process|<span style="color: Snow">'''EARB Process'''</span>]] '''
 
 
 
| style="border-right: white 1px ridge; padding-right: 0px; padding-left: 0px; padding-bottom: 2px; padding-top: 2px; text-align: center; font-family: (Cooper black); font-size: 13pt" width="11%" | '''[[EARB_Forward_Agenda|<span style="color: Snow">'''Forward Agenda'''</span>]] '''
 
 
 
| style="border-right: white 1px ridge; padding-right: 0px; padding-left: 0px; padding-bottom: 2px; padding-top: 2px; text-align: center; font-family: (Cooper black); font-size: 13pt" width="11%" | '''[[EARB_Past_Sessions|<span style="color: Snow">'''Past Sessions'''</span>]] '''
 
 
 
|}
 
 
 
<!-- NAV end -->
 
 
 
{{Translation to follow}}
 
 
 
 
= What do I do first? =
 
= What do I do first? =
  
Line 73: Line 49:
  
 
* As directed by the Chief Information Officer of Canada.
 
* As directed by the Chief Information Officer of Canada.
 +
 +
<span style="font-size: 1.2em;"><b>Note</b></span>
 +
 +
{| width="100% cellpadding="10" cellspacing=10px
 +
|-valign="top"
 +
 +
|width="33.3%" style="border: 1px dashed darkblue;" |
 +
<!-- 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;" |
 +
<!-- 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=32578 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;" | 
 +
<!-- COLUMN 3 STARTS: -->
 +
<b>3.</b> Ensure all departmental initiatives are assessed against and <b>meet the requirements</b> of Appendix C: Mandatory Procedures for Enterprise Architecture Assessment and Appendix D: Mandatory Procedures for Application Programming Interfaces.
 +
<!-- COLUMN 3 ENDS: -->
 +
|}
 +
 
|}
 
|}
 
<!-- ROW 1 ENDS: -->  
 
<!-- ROW 1 ENDS: -->  
Line 80: Line 78:
  
 
|-valign="top"
 
|-valign="top"
|width="25%" style="border: 1px solid steelblue; color: black; background-color: AliceBlue; font-size:1.2em;" |  
+
|width="50%" style="border: 1px solid steelblue; color: black; background-color: AliceBlue;" |  
  
2. <b>Complete</b> the "Presenter" intake presentation
+
<span style="font-size:1.2em;">2. <b>REQUIRED</b> to come: <b>Complete</b> the "Presenter" intake presentation below:</span><br>
|}
+
{| width="100%" cellpadding="10" cellspacing=15px
+
<b>TEMPLATE</b>: [[Media:GC_EARB_Presenter_GENERAL_2019-09-13.PPTX | GC EARB Presenter Template]]
|-valign="top"
+
|width="50%" style="border: 1px solid steelblue; color: black; background-color: AliceBlue;" |  
|width="25%" style="border: 1px dashed steelblue;" |  
 
  
<b>TEMPLATE</b>:[http://www.gcpedia.gc.ca/wiki/GC_Enterprise_Architecture_Review_Board_(GC_EARB) http://www.gcpedia.gc.ca/wiki/GC_Enterprise_Architecture_Review_Board_(GC_EARB)]
+
<span style="font-size:1.2em;">2. <b>NOT REQUIRED</b> to come: <b>Provide rationale</b> in email then forward to:</span><br>
 +
 +
<b>EMAIL</b>: {{em|ZZCIOBDP@tbs-sct.gc.ca}}
 
|}
 
|}
 
<!-- ROW 2 ENDS: -->  
 
<!-- ROW 2 ENDS: -->  
Line 98: Line 97:
 
|width="25%" style="border: 1px solid steelblue; color: black; background-color: AliceBlue; font-size:1.2em;" |  
 
|width="25%" style="border: 1px solid steelblue; color: black; background-color: AliceBlue; font-size:1.2em;" |  
  
3. <b>Send</b> completed presentation to GC EARB group
+
3. <b>Send</b> completed presentation or rationale to GC EARB group
 
|}
 
|}
 
{| width="100%" cellpadding="10" cellspacing=15px
 
{| width="100%" cellpadding="10" cellspacing=15px
Line 104: Line 103:
 
|width="25%" style="border: 1px dashed steelblue;" |  
 
|width="25%" style="border: 1px dashed steelblue;" |  
  
<b>EMAIL</b>: {{ZZCIOBDP@tbs-sct.gc.ca}}
+
<b>EMAIL</b>: {{em|ZZCIOBDP@tbs-sct.gc.ca}}
 
|}
 
|}
 
<!-- ROW 3 ENDS: -->  
 
<!-- ROW 3 ENDS: -->  
Line 118: Line 117:
  
 
* Complete the presenter intake deck.
 
* Complete the presenter intake deck.
* Email the deck to the generic mailbox: {{ZZCIOBDP@tbs-sct.gc.ca}}
+
* Email the deck to the generic mailbox: {{em|ZZCIOBDP@tbs-sct.gc.ca}}
 
* GC Enterprise Architecture will review and conduct initial assessment.
 
* GC Enterprise Architecture will review and conduct initial assessment.
 
* Tentative date to present is secured and you will be notified by email.
 
* Tentative date to present is secured and you will be notified by email.
Line 125: Line 124:
 
=Architectural Assessment=
 
=Architectural Assessment=
  
* GC Enterprise Architecture will review your project material against the [GC Digital] and [GC Architectural Standards].
+
* GC Enterprise Architecture will review your project material against the [[Government_of_Canada_Digital_Standards |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.
 
* 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.
 
* This summary is shared with the departmental contacts and the EARB Co-Chairs prior to the meeting.
Line 152: Line 151:
  
  
== Useful Links ==
+
<!-- FRENCH -->
* [[GC_EARB | GC EARB Handy Materials]]
+
@fr|__NOTOC__
* [https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=15249 Directive on the Management of Information Technology]
+
= Que dois-je faire en premier? =
* [https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=12755#appA Policy on Management of Information Technology]
+
 
* [EARB Presenter Template]
+
<!-- Row-->
* [GC Digital Standards]
+
<!-- ROW 1 STARTS: -->
* [GC Architectural Standards]
+
{| width="100%" cellpadding="10" cellspacing=15px
* [Application Programming Standards]
+
 
 +
|-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=15249 https://www.tbs-sct.gc.ca/pol/doc-fra.aspx?id=15249]
 +
 
 +
*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 à toute directive ou norme applicable en vertu de la Politique sur la gestion de la technologie de l’information;
 +
* 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=32578 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 C : Procédures obligatoires pour l’évaluation de l’architecture intégrée et de l’annexe D : 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|ZZCIOBDP@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|ZZCIOBDP@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 [[Government_of_Canada_Digital_Standards |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>
 +
* 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.
 +
* 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.
 +
</multilang>
 +
{{OCIO_GCEARB_Footer}}

Revision as of 14:10, 27 July 2020

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

1. Conduct a self-assessment of your initiative against the "Criteria" to determine if you should be presenting to the GC EARB

CRITERIA: https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=15249

  • 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:
  • $2.5 million + OPMCA of 0 or 1
  • $5 million + OPMCA of 2
  • $10 million + OPMCA of 3
  • $15 million Department of National Defence
  • $25 million + OPMCA 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.

Note

1. Please ensure that all proposals submitted for review by the Government of Canada Enterprise Architecture Review Board have first been assessed by the departmental architecture review board where one has been established.

2. Ensure that proposals are submitted to the Government of Canada Enterprise Architecture Review Board following review of concept cases for digital projects and before the development of a Treasury Board Submission or Departmental Business Case.

3. Ensure all departmental initiatives are assessed against and meet the requirements of Appendix C: Mandatory Procedures for Enterprise Architecture Assessment and Appendix D: Mandatory Procedures for Application Programming Interfaces.

2. REQUIRED to come: Complete the "Presenter" intake presentation below:

TEMPLATE: GC EARB Presenter Template

2. NOT REQUIRED to come: Provide rationale in email then forward to:

EMAIL: ZZCIOBDP@tbs-sct.gc.ca

3. Send completed presentation or rationale to GC EARB group

EMAIL: ZZCIOBDP@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.
  • Ensure your departmental initiatives are assessed against and align to the requirements set out as the [GC Architectural Standards].


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

  • Complete the presenter intake deck.
  • Email the deck to the generic mailbox: ZZCIOBDP@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[edit | edit source]

  • GC Enterprise Architecture will review your project material against the GC Digital and 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[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 EARB members for their review prior to the scheduled meeting.

Day of:

  • 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 GC Wiki site.