Difference between revisions of "GC Enterprise Architecture/Board/When to come"
Jana.jessome (talk | contribs) |
Jana.jessome (talk | contribs) |
||
Line 73: | Line 73: | ||
* As directed by the Chief Information Officer of Canada. | * As directed by the Chief Information Officer of Canada. | ||
+ | |||
+ | <span style="font-size: 1.2em;"><b>Note</b></span> | ||
+ | |||
+ | {| width="100% cellpadding="10" cellspacing=10px | ||
+ | |-valign="top" | ||
+ | |||
+ | |width="33.3%" style="border: 1px dashed darkblue;" | | ||
+ | <!-- COLUMN 1 STARTS: --> | ||
+ | <b>1.</b> Please ensure that all proposals submitted for review by the Government of Canada Enterprise Architecture Review Board have <b>first been assessed</b> by the departmental architecture review board where one has been established. | ||
+ | <!-- COLUMN 1 ENDS: --> | ||
+ | |||
+ | |width="33.3%" style="border: 1px dashed darkblue;" | | ||
+ | <!-- COLUMN 2 STARTS: --> | ||
+ | <b>2.</b> Ensure that proposals are submitted to the Government of Canada Enterprise Architecture Review Board following review of <b>[https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=32578 concept cases] </b>for digital projects and <b>before</b> the development of a Treasury Board Submission or Departmental Business Case. | ||
+ | <!-- COLUMN 2 ENDS: --> | ||
+ | |||
+ | |width="33.3%" style="border: 1px dashed darkblue;" | | ||
+ | <!-- COLUMN 3 STARTS: --> | ||
+ | <b>3.</b> Ensure all departmental initiatives are assessed against and <b>meet the requirements</b> of Appendix C: Mandatory Procedures for Enterprise Architecture Assessment and Appendix D: Mandatory Procedures for Application Programming Interfaces. | ||
+ | <!-- COLUMN 3 ENDS: --> | ||
+ | |} | ||
+ | |||
|} | |} | ||
<!-- ROW 1 ENDS: --> | <!-- ROW 1 ENDS: --> |
Revision as of 13:24, 11 January 2019
Home | What is EARB | When to come to EARB | EARB Process | Forward Agenda | Past Sessions |
This page is a work in progress. We welcome your feedback. Please use the discussion page for suggestions and comments. When the page is approved and finalized, we will send it for translation. |
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
Note
|
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]