586
edits
Changes
GC Enterprise Architecture/10 Things You Need to Know (view source)
Revision as of 10:00, 18 December 2020
, 10:00, 18 December 2020no edit summary
|
|
|}
|}
=== '''1. Policy(ies) and directive(s) the Enterprise Architecture Division responsible for:''' ===
* ''[https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=32603 Policy on Service and Digital]'' – article 4.1.2.4
* ''[https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=32601 Directive on Service and Digital]'' – articles 4.1.1.2 to 4.1.1.5
* [[GC Enterprise Architecture/Framework|Appendix A: Enterprise Architecture Framework]] (to be published soon on Canada.ca)
=== '''2. Due diligence function of the Enterprise Architecture Division:''' ===
The GC EARB was established by the Chief Information Officer of Canada, as required by the Policy on Service and Digital, and is mandated to define current and target architecture standards for the Government of Canada and review departmental proposals for alignment. Most pivotal of these architecture standards is the GC Service and Digital Target State Enterprise Architecture. This is now the primary architecture reference for all departments (as applies) for the digital enablement of Government of Canada services. Alignment to the target state model, as assessed against the criteria of the [[GC Enterprise Architecture/Framework|Enterprise Architecture Framework]], informs the endorsement of departmental digital investment proposals presented to the GC EARB.
The GC EARB was established by the Chief Information Officer of Canada, as required by the Policy on Service and Digital, and is mandated to define current and target architecture standards for the Government of Canada and review departmental proposals for alignment. Most pivotal of these architecture standards is the GC Service and Digital Target State Enterprise Architecture. This is now the primary architecture reference for all departments (as applies) for the digital enablement of Government of Canada services. Alignment to the target state model, as assessed against the criteria of the [[GC Enterprise Architecture/Framework|Enterprise Architecture Framework]], informs the endorsement of departmental digital investment proposals presented to the GC EARB.
To fulfill the GC EARB mandate, TBS OCIO Enterprise Architecture collaborates with departmental architects to:
To fulfill the GC EARB mandate, TBS OCIO Enterprise Architecture collaborates with departmental architects to:
* Develop target architecture standards across the domains of Business, Information/Data, Application, Technology and Security (BIATS)
* Guide implementation of the [[GC Enterprise Architecture/Framework|Enterprise Architecture Framework]] when reviewing departmental proposals for alignment (to be published soon on Canada.ca)
* Provide central coordination of Networks of Expertise for Enterprise Architecture, Data, Cloud, Digital workspace & Cyber to develop enterprise solutions and share best practices
* Engage with Departmental project and architecture leads to help ensure their proposals are well-prepared in advance of their GC EARB review date, and provide advice and recommendations to improve alignment.
Further information is available in the [[:en:GC_Service_&_Digital_Target_Enterprise_Architecture|"Service & Digital Target Enterprise Architecture - White Paper"]]
Further information is available in the [[:en:GC_Service_&_Digital_Target_Enterprise_Architecture|"Service & Digital Target Enterprise Architecture - White Paper"]]
'''3. When to consult the Enterprise Architecture Division:'''
=== '''3. When to consult the Enterprise Architecture Division:''' ===
The GC Enterprise Architecture team is available to engage with departments if the department contact the team directly or through the OCIO Committee Secretariat, such as when the department is required to present a digital investment or project to the GC EARB for review and endorsement, as outlined in the [[GC Enterprise Architecture/Board/When to come|When to come]] page on the GC EARB wiki.
The GC Enterprise Architecture team is available to engage with departments if the department contact the team directly or through the OCIO Committee Secretariat, such as when the department is required to present a digital investment or project to the GC EARB for review and endorsement, as outlined in the [[GC Enterprise Architecture/Board/When to come|When to come]] page on the GC EARB wiki.
The GC EARB presentation typically occurs after the Concept Case has been completed and before the Treasury Board submission, if one is required. Projects not subject to a TB submission may also be required to present at GC EARB. This is done in the planning and design phase of the project lifecycle, before formal execution has begun. It will articulate how the business problem is addressed by the proposed solution and demonstrate alignment with GC digital standards and architectural requirements. It may include an options analysis leading to the recommended solution.
The GC EARB presentation typically occurs after the Concept Case has been completed and before the Treasury Board submission, if one is required. Projects not subject to a TB submission may also be required to present at GC EARB. This is done in the planning and design phase of the project lifecycle, before formal execution has begun. It will articulate how the business problem is addressed by the proposed solution and demonstrate alignment with GC digital standards and architectural requirements. It may include an options analysis leading to the recommended solution.
'''4. Types of authorities related to the Policy''' (link to commonly sought authorities webpage).
=== '''4. Types of authorities related to the Policy''' (link to commonly sought authorities webpage). ===
Presentation of a project before the GC EARB results in an endorsement and direction from the Government of Canada Chief Information Officer. Although no Treasury Board authorities are sought in the enterprise architecture review process, when a Treasury Board Submission seeks TB authorities (e.g., funding for the project or project approvals) later in the process, an endorsed architecture would form part of the necessary documentation for the Office of the Chief Information Officer to support a project.
Presentation of a project before the GC EARB results in an endorsement and direction from the Government of Canada Chief Information Officer. Although no Treasury Board authorities are sought in the enterprise architecture review process, when a Treasury Board Submission seeks TB authorities (e.g., funding for the project or project approvals) later in the process, an endorsed architecture would form part of the necessary documentation for the Office of the Chief Information Officer to support a project.
'''5. Key due diligence questions to consider:'''
=== '''5. Key due diligence questions to consider:''' ===
· Does the proposed project/investment meet the [[GC Enterprise Architecture/Board/When to come|threshold criteria]] set in the Directive on Service and Digital for requiring GC EARB review?
· Does the proposed project/investment meet the [[GC Enterprise Architecture/Board/When to come|threshold criteria]] set in the Directive on Service and Digital for requiring GC EARB review?
· Are there other departments working on solutions for the same business capability that should be engaged?
· Are there other departments working on solutions for the same business capability that should be engaged?
'''6. How does Enterprise Architecture Division provide advice?'''
=== '''6. How does Enterprise Architecture Division provide advice?''' ===
In most instances, the Enterprise Architecture team is consulted for preliminary review of a department’s proposed solution architecture to provide advice on how to strengthen the presentation to highlight key points, demonstrated expected alignment to GC requirements and avoid issues that would hinder endorsement. The EA team also produces a one-page Enterprise Architecture Assessment of the project that is included in the template as part of the review package, with ratings on alignment, a recommendation on endorsement, and possible conditions.
In most instances, the Enterprise Architecture team is consulted for preliminary review of a department’s proposed solution architecture to provide advice on how to strengthen the presentation to highlight key points, demonstrated expected alignment to GC requirements and avoid issues that would hinder endorsement. The EA team also produces a one-page Enterprise Architecture Assessment of the project that is included in the template as part of the review package, with ratings on alignment, a recommendation on endorsement, and possible conditions.
Departments may also contact the EA team for general advice in establishing or managing the enterprise architecture practice in their department, or for information on various GC enterprise considerations that may related to their projects.
Departments may also contact the EA team for general advice in establishing or managing the enterprise architecture practice in their department, or for information on various GC enterprise considerations that may related to their projects.
'''''7. ''Linkages with other policies:'''
=== '''''7. ''Linkages with other policies:''' ===
· ''Policy on Results''
· ''Policy on Results''
o Privacy layer
o Privacy layer
'''8. Additional sources of information:'''
=== '''8. Additional sources of information:''' ===
* [[GC Enterprise Architecture/Board|GC EARB wiki on GCcollab]]
* [[GC Enterprise Architecture/Board|GC EARB wiki on GCcollab]]
* [[GC Enterprise Architecture/Board/Forward Agenda|GC EARB forward agenda]]
* [[GC Enterprise Architecture/Board/Forward Agenda|GC EARB forward agenda]]
* [[GC Enterprise Architecture|Enterprise Architecture wiki on GCcollab]]
* [[GC Enterprise Architecture|Enterprise Architecture wiki on GCcollab]]
* Enterprise Architecture Community of Practice group on GCconnex
* Enterprise Architecture Community of Practice group on GCconnex
=== '''9. Example submission related to GC EARB:''' ===
* [[:en:GC_Enterprise_Architecture/Board/Past_Sessions|Past meetings - agendas and related presentations]] (mostly PDF copies available for viewing by GC community)
* [https://gcdocs.tbs-sct.gc.ca/gcdocs/llisapi.dll?func=ll&objId=27131364&objAction=browse&sort=name&viewType=1 EA Team GCdocs folder] (links to original documents and presentations organized by topic)
* [https://gcdocs.tbs-sct.gc.ca/gcdocs/llisapi.dll?func=ll&objId=26332823&objAction=browse&viewType=1 OCIO Secretariat GCdocs folder] (links to original documents and presentations organized by meeting date)
=== '''10. How to contact the Enterprise Architecture Division?''' ===
The team actively monitors a generic mailbox for submissions and engagements at [[Mailto:EA.AE@tbs-sct.gc.ca|EA.AE@tbs-sct.gc.ca]]. Program sector analysts are encouraged to use this email but can also reach out directly to the concept case team members.
The team actively monitors a generic mailbox for submissions and engagements at [[Mailto:EA.AE@tbs-sct.gc.ca|EA.AE@tbs-sct.gc.ca]]. Program sector analysts are encouraged to use this email but can also reach out directly to the concept case team members.