Line 60: |
Line 60: |
| | | |
| | | |
| + | = How do you go about getting on the agenda? = |
| + | |
| + | ==Departmental Input== |
| + | |
| + | *Go to GC Pedia to attain the most recent GC EARB “Presenter Template” |
| + | *Complete the deck |
| + | *Email the deck to the generic mailbox: {{em|ZZCIOBDP@tbs-sct.gc.ca}} |
| + | |
| + | ==TBS - OCIO (EA Review)== |
| + | |
| + | *GC EARB team receives alert of a new submission. |
| + | *A tentative date for the presentation is identified. |
| + | *A GC EA team conducts a review the input material. |
| + | *Comments are provided back to the department for clarification. |
| + | *A call/meeting occurs to discuss feedback and refine understanding. |
| + | *Updated presentation materials may be requested. |
| + | *The EARB meeting date is confirmed. |
| + | |
| + | ==Prepare Assessment== |
| | | |
− | = How do you go about getting on the agenda? = | + | *An architectural assessment is prepared by the GC EA team. |
| + | *Alignment against both the GC Digital and GC Architectural Standards is performed. |
| + | *This feedback is provided to the department as well as used to brief the Co-chairs of the GC EARB prior to the meeting. |
| + | |
| + | =How it works... what to expect= |
| + | |
| + | ==TBS-OCIO Secretariat== |
| + | |
| + | <b>2 weeks</b> ahead: |
| + | *The Secretariat will extend the calendar invitations to the <b>presenters</b> (typically 1-2 people) |
| | | |
− | {| width="100% cellpadding="10"
| + | <b>1 week</b> ahead: |
| + | *They will request the presentation materials (both French and English) 1 week prior to the session |
| + | *They prepare information packages for the EARB membership to review ahead of the meeting. |
| | | |
− | |-valign="top"
| + | ==GC EARB Meeting== |
− | |width="100%" style="border: 1px solid #DD3D0B; color: black;"|
| |
| | | |
− | <!-- COLUMN 1 STARTS: --> | + | *Time to present (being clear to the Board why you are here…. To seek endorsement to xxx ) |
− | 1 GC Pedia
| + | *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. |
− |
| + | *<b>NOTE:</b> The RoD may take several weeks to be officially published, but will be available on the GC EARB GC Pedia site. |
− | <!-- COLUMN 1 ENDS: -->
| |
− | |}
| |
| | | |
| + | ==Follow UP== |
| | | |
| + | *There are times when departments must return to the GC EARB as a result of where the project is in it cycle, or from conditions identified by the Board. |
| + | *The GC EA team will capture the need for a future visit and proactively schedule it on the GC EARB Forward Agenda. |
| | | |
| == Useful Links == | | == Useful Links == |