Difference between revisions of "GC Enterprise Architecture/Board/When to come"
Jump to navigation
Jump to search
Jana.jessome (talk | contribs) |
Jana.jessome (talk | contribs) |
||
Line 23: | Line 23: | ||
= What do I do first? = | = What do I do first? = | ||
− | + | ||
<!-- Row--> | <!-- Row--> | ||
<!-- ROW 1 STARTS: --> | <!-- ROW 1 STARTS: --> | ||
− | {| width="100% cellpadding="10" cellspacing=15px | + | {| width="100%" cellpadding="10" cellspacing=15px |
|-valign="top" | |-valign="top" | ||
− | |width="25%" style="border: 1px solid | + | |width="25%" style="border: 1px solid steelblue; color: black; background-color: AliceBlue; font-size:1.2em;" | |
− | 1. Conduct a <b>self-assessment</b> of your initiative against the "Criteria" to determine if you should be presenting to the GC EARB | + | 1. Conduct a <b>self-assessment</b> of your initiative against the "Criteria" to determine if you should be presenting to the GC EARB |
|} | |} | ||
− | {| width="100% cellpadding="10" cellspacing=15px | + | {| width="100%" cellpadding="10" cellspacing=15px |
|-valign="top" | |-valign="top" | ||
− | |width="25%" style="border: 1px dashed | + | |width="25%" style="border: 1px dashed steelblue;" | |
− | <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] | + | <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: | ||
Line 72: | Line 72: | ||
<!-- ROW 1 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>Complete</b> the "Presenter" intake presentation | ||
+ | |} | ||
+ | {| width="100%" cellpadding="10" cellspacing=15px | ||
+ | |-valign="top" | ||
+ | |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)] | ||
+ | |} | ||
+ | <!-- 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>Send</b> completed presentation to GC EARB group | ||
+ | |} | ||
+ | {| width="100%" cellpadding="10" cellspacing=15px | ||
+ | |-valign="top" | ||
+ | |width="25%" style="border: 1px dashed steelblue;" | | ||
+ | |||
+ | <b>EMAIL</b>: {{ZZCIOBDP@tbs-sct.gc.ca}} | ||
+ | |} | ||
+ | <!-- ROW 3 ENDS: --> | ||
+ | |||
+ | |||
+ | ==Things to note== | ||
+ | |||
+ | * 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. | ||
+ | * Ensure your departmental initiatives are assessed against and <b>align</b> to the requirements set out as the [GC Architectural Standards]. | ||
+ | |||
+ | |||
+ | ==How do you go about getting on the agenda?== | ||
+ | |||
+ | * 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== | ||
+ | |||
+ | * 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== | ||
+ | |||
+ | <span style="font-size: 1.2em; font-weight: bold;"> TBS OCIO Secretariat </span> | ||
+ | |||
+ | <b>2 weeks</b> ahead: | ||
+ | * The Secretariat will extend the calendar invitations to the presenters (typically 1-2 people) | ||
+ | <b>1 week</b> 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. | ||
+ | <b>Day of:</b> | ||
+ | * 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. | ||
+ | <b>Post EARB Meeting:</b> | ||
+ | * 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. | ||
Revision as of 10:19, 9 January 2019
Home | What is EARB | When to come to EARB | EARB Process | Forward Agenda | Past Sessions |
What do I do first?
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
|
2. Complete the "Presenter" intake presentation |
TEMPLATE:http://www.gcpedia.gc.ca/wiki/GC_Enterprise_Architecture_Review_Board_(GC_EARB) |
3. Send completed presentation to GC EARB group |
Things to note
- 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?
- Complete the presenter intake deck.
- Email the deck to the generic mailbox: Template: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
- 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
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.
Useful Links
- GC EARB Handy Materials
- Directive on the Management of Information Technology
- Policy on Management of Information Technology
- [EARB Presenter Template]
- [GC Digital Standards]
- [GC Architectural Standards]
- [Application Programming Standards]