2,055
edits
Changes
Jump to navigation
Jump to search
Line 48:
Line 48: − + − + − + − + − *A tentative GC EARB date to present will then be identified.+ − + + + + + + + + + + + + + + − * 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.+ − + + − + − '''TBS OCIO Secretariat''' − + − '''1 week''' ahead:+ − + + + + + + + + + + − * Packages are prepared and distributed to GC EARB members for their review prior to the scheduled meeting. − '''Day of:''' − * 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:''' − + + − * Make your way to the identified meeting room.+ − * Once in the meeting room, please RETURN the temporary pass to OCIO representatives. − '''Post EARB Meeting:''' + + + + − * 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>.
GC Enterprise Architecture/Board/When to come (view source)
Revision as of 12:28, 4 March 2021
, 12:28, 4 March 2021Update logistics section
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>
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>
=='''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]]). For 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.
== How do you go about getting on the agenda? ==
*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.
* Look at [[GC_Enterprise_Architecture/Board/Forward_Agenda| forward agenda]] and send a request to [mailto:EA.AE@tbs-sct.gc.ca EA team] to schedule a date
* 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]]). For 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.
== '''Architectural Alignment''' ==
* 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.
== Architectural Alignment ==
* The TBS EA team will use the details provided in the departmental GCEARB presentation to summarize the alignment to the EA Framework.
* 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 ==
=== 2-3 weeks ahead ===
* TBS EA shares your draft with the other subject matter experts (SMEs) from TBS Cyber, CCCS, SSC EA, etc...
* A meeting with the SMEs and department is setup for feedback and review
=== 1 weeks ahead ===
* 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.
* '''Monday (end of day): Draft English deck for the co-chair pre-brief is due'''
* Thursday: Co-chair pre-brief happens and any final feedback from them will be shared
== '''Meeting Logistics – How It Works''' ==
=== Week of EARB ===
'''2 weeks''' ahead:
* '''Monday (end of day): FINAL presentation materials (both French and English) is due'''
* 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)
* 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 ===
* Documents for the meeting are posted on [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].
==== Virtual ====
* Attend via Join Microsoft Teams Meeting link found in the meeting invite. Link also available on the GCconnex site
==== 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)
* 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.
* 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.
* 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.
* Invite will be sent from the OCIO Secretariat for the Monday following the meeting for the presenters to review the draft RoD and contribute any edits
* The RoD may take several weeks to be officially published, but will be made available on the [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].
* A decision letter is sent from the co-chairs to confirm the conditions and endorsement if applicable
* The RoD is brought to a future meeting to be approved by the members
@fr|
@fr|
To be translated
To be translated
</multilang>
</multilang>
