586
edits
Changes
Jump to navigation
Jump to search
Line 71:
Line 71: − · 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.+ Line 81:
Line 81: − + − · The Secretariat will extend the calendar invitations to the presenters (typically 1-2 people) − + − · 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. − − + − · Documents for the meeting are posted on GCEARB GCconnex site. − − + − · Attend via Join Microsoft Teams Meeting link found in the meeting invite − + − · 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.+ + + − · 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. −
GC Enterprise Architecture/Board/When to come (view source)
Revision as of 11:58, 21 December 2020
, 11:58, 21 December 2020→Architectural Alignment
*A tentative GC EARB date to present will then be identified.
*A tentative GC EARB date to present will then be identified.
== '''Architectural Alignment''' ==
== '''Architectural Alignment''' ==
* 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''' ==
== '''Meeting Logistics – How It Works''' ==
'''2 weeks''' ahead:
'''2 weeks''' ahead:
* The Secretariat will extend the calendar invitations to the presenters (typically 1-2 people)
'''1 week''' ahead:
'''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:'''
'''Day of:'''
* Documents for the meeting are posted on GCEARB GCconnex site.
'''Virtual:'''
'''Virtual:'''
* Attend via Join Microsoft Teams Meeting link found in the meeting invite
'''In Person:'''
'''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:'''
'''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.
<nowiki>#########################################################################################################</nowiki>
<nowiki>#########################################################################################################</nowiki>
