662
edits
Changes
Jump to navigation
Jump to search
Line 37:
Line 37: − + Line 76:
Line 76: − − − − − <!-- ROW 2 STARTS: --> − {| width="100% cellpadding="10" cellspacing=15px − − |-valign="top" − |width="25%" style="border: 1px solid LightBlue; color: black; background-color: AliceBlue;" | − − 2. 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. − |} − <!-- ROW 2 ENDS: --> − − <!-- ROW 3 STARTS: --> − {| width="100% cellpadding="10" cellspacing=15px − − |-valign="top" − |width="25%" style="border: 1px solid LightBlue; color: black; background-color: AliceBlue;" | − − 3. Ensure your departmental initiatives are assessed against and <b>align</b> to the requirements set out as the GC Architectural Standards. − |} − <!-- ROW 3 ENDS: --> − − <!-- ROW 4 STARTS: --> − {| width="100% cellpadding="10" cellspacing=15px − − |-valign="top" − |width="25%" style="border: 1px solid LightBlue; color: black; background-color: AliceBlue;" | − − 4. Ensure your departmental initiatives are assessed against and <b>align</b> to the requirements set out as the GC Architectural Standards. − |} − <!-- ROW 4 ENDS: --> − − = 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== − − *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) − − <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. − − ==GC EARB Meeting== − − *Time to present (being clear to the Board why you are here…. To seek endorsement to xxx ) − *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. − − ==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.
GC Enterprise Architecture/Board/When to come (view source)
Revision as of 16:09, 8 January 2019
, 16:09, 8 January 2019no edit summary
|width="25%" style="border: 1px dashed LightBlue;" |
|width="25%" style="border: 1px dashed LightBlue;" |
<b>CRITERIA</b>:[https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=15249]
<b>CRITERIA</b>:[https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=15249 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:
*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:
== Useful Links ==
== Useful Links ==
