GC Enterprise Architecture/Board/When to come

GC Enterprise Architecture	GC Enterprise Architecture Review Board, GC EARB
GC Service & Digital Target Enterprise Architecture	When to come
Enterprise Architecture Framework	Forward Agenda
Business Capability Model (BCM)	Past Sessions
Exemplar and Reference Architectures	10 Things You Need to Know
Enterprise Solutions	Governance for Digital Solutions
Working Groups	EA and GC EARB Overview – Presentation
Other References

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 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: $2.5 million + OPMCA of 0 or 1 $5 million + OPMCA of 2 $10 million + OPMCA of 3 $15 million Department of National Defence $25 million + OPMCA of 4 That involve emerging technologies; That require an exception to any applicable Directive or Standard under the Policy on the Management of Information Technology; That are categorized at the protected B level or below‎ using a deployment model other than public cloud for application hosting (including infrastructure), application deployment, or application development; or As directed by the Chief Information Officer of Canada. Note 1. Please ensure that all proposals submitted for review by the Government of Canada Enterprise Architecture Review Board have first been assessed by the departmental architecture review board where one has been established. 2. Ensure that proposals are submitted to the Government of Canada Enterprise Architecture Review Board following review of concept cases for digital projects and before the development of a Treasury Board Submission or Departmental Business Case. 3. Ensure all departmental initiatives are assessed against and meet the requirements of Appendix C: Mandatory Procedures for Enterprise Architecture Assessment and Appendix D: Mandatory Procedures for Application Programming Interfaces.

2. REQUIRED to come: Complete the "Presenter" intake presentation below: TEMPLATE: GC EARB Presenter Template

2. NOT REQUIRED to come: Provide rationale in email then forward to: EMAIL: EA.AE@tbs-sct.gc.ca

3. Send completed presentation or rationale to GC EARB group

EMAIL: EA.AE@tbs-sct.gc.ca

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: EA.AE@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.

Need help? Contact us. EA.AE@tbs-sct.gc.ca Enterprise Architecture Community of Practice GCconnex