Difference between revisions of "GC Enterprise Architecture/Board/When to come"
Line 64: | Line 64: | ||
Section 4.1.1.1 The departmental Chief Information Officer (CIO) is responsible for: Chairing a departmental architecture review board that is mandated to review and approve the architecture of all departmental digital initiatives and ensure their alignment with enterprise architectures. | Section 4.1.1.1 The departmental Chief Information Officer (CIO) is responsible for: Chairing a departmental architecture review board that is mandated to review and approve the architecture of all departmental digital initiatives and ensure their alignment with enterprise architectures. | ||
− | Ensure your departmental initiatives are evaluated against and '''align''' to the requirements set out as the <u>[[Enterprise Architecture Framework]]</u> | + | Ensure your departmental initiatives are evaluated against and '''align''' to the requirements set out as the <u>[[:en:GC_Enterprise_Architecture/Framework|Enterprise Architecture Framework]]</u> |
== '''How do you go about getting on the agenda?''' == | == '''How do you go about getting on the agenda?''' == | ||
− | + | * Complete a draft of the [[Images/b/bb/2020-12-15-GC EARB Presenter GENERAL.pptx|GC EARB Presenter Template]]. | |
− | + | * Email the draft GC EARB presentation to the EA team: [[Mailto:EA.AE@tbs-sct.gc.ca|EA.AE@tbs-sct.gc.ca]] | |
− | + | * GC Enterprise Architecture will contact you to review and conduct initial assessment. | |
− | + | * A tentative GC EARB date to present will then be identified. | |
− | |||
− | |||
− | |||
== '''Architectural Alignment''' == | == '''Architectural Alignment''' == |
Revision as of 11:46, 21 December 2020
What do I do first?
Step 1
Self-assess against the of your initiative against the "Criteria" in the Directive on Service and Digital to determine if the initiative should be presenting to the GC EARB.
Section 4.1.1 the departmental Chief Information Officer (CIO) is responsible for:
4.1.1.2 Submitting to the Government of Canada enterprise architecture review board proposals concerned with the design, development, installation and implementation of digital initiatives:
4.1.1.2.1 Where the department is willing to invest a minimum of the following amounts to address the problem or take advantage of the opportunity:
4.1.1.2.1.1 $2.5 million dollars for departments that do not have an approved Organizational Project Management Capacity Class or that have an approved Organizational Project Management Capacity Class of 1 according to the Directive on the Management of Projects and Programmes;
4.1.1.2.1.2$5 million dollars for departments that have an approved Organizational Project Management Capacity Class of 2;
4.1.1.2.1.3$10 million dollars for departments that have an approved Organizational Project Management Capacity Class of 3;
4.1.1.2.1.4$15 million dollars for the Department of National Defence;
4.1.1.2.1.5$25 million dollars for departments that have an approved Organizational Project Management Capacity Class of 4;
4.1.1.2.2That involve emerging technologies;
4.1.1.2.3That require an exception under this directive or other directives under the policy;
4.1.1.2.4That 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
4.1.1.2.5 As directed by the CIO of Canada.
If the investment meets at least one of the criteria above, the department must bring forward the proposal to GC EARB.
Step 2
a. If REQUIRED to come: Complete a draft of the GC EARB Presenter Template (French Presenter Template) and send the presentation to the TBS EA team (EA.AE@tbs-sct.gc.ca)
OR
b. If NOT REQUIRED to come: Provide rationale in an email then forward to:
the TBS EA team (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 as described in the Directive on Service and Digital.
Section 4.1.1.1 The departmental Chief Information Officer (CIO) is responsible for: Chairing a departmental architecture review board that is mandated to review and approve the architecture of all departmental digital initiatives and ensure their alignment with enterprise architectures.
Ensure your departmental initiatives are evaluated against and align to the requirements set out as the Enterprise Architecture Framework
How do you go about getting on the agenda?
- Complete a draft of the GC EARB Presenter Template.
- Email the draft GC EARB presentation to the EA team: [[1]]
- GC Enterprise Architecture will contact you to review and conduct initial assessment.
- A tentative GC EARB date to present will then be identified.
Architectural Alignment
· The TBS EA team will use the details provided in the departmental GCEARB presentation to summarize the alignment to the EA Framework.
· A summary is prepared that summarizes the level of alignment across business, information, application, technology and security domain, areas of possible concern and finally recommendations for endorsement and any application conditions are noted.
· This EA summary is shared with the departmental contacts, the GC EARB Co-Chairs prior to the meeting and is presented as the summary slide by the TBS EA at the GC EARB presentation.
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 GC EARB members for their review prior to the scheduled meeting.
Day of:
· Documents for the meeting are posted on GCEARB GCconnex site.
Virtual:
· Attend via Join Microsoft Teams Meeting link found in the meeting invite
In Person:
· 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 GCEARB GCconnex site.
#########################################################################################################
EA and GCEARB WIKI under construction, CONTENT below TO BE ARCHEIVED
#########################################################################################################
What do I do first?[edit | edit source]
1. Conduct a self-assessment of your initiative against the "Criteria" to determine if you should be presenting to the GC EARB |
CRITERIA: Directive on Service and Digital
Note
|
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[edit | edit source]
- 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?[edit | edit source]
- 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[edit | edit source]
- 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[edit | edit source]
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.