Changes

{{OCIO GCEA Header}}

{{OCIO GCEA Header}}

 

=== '''Policy(ies) and directive(s) the Enterprise Architecture Division responsible for:''' ===

=== '''Policy(ies) and directive(s) the Enterprise Architecture Division responsible for:''' ===

* ''[https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=32603 <u>Policy on Service and Digital</u>]'' – article 4.1.2.4

* ''[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 <u>Directive on Service and Digital</u>]'' – articles 4.1.1.2 to 4.1.1.5

* ''[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|<u>''GC Enterprise Architecture Framework''</u>]] (to be published soon on Canada.ca)

* [[GC Enterprise Architecture/Framework|''GC Enterprise Architecture Framework'']] (to be published soon on Canada.ca)

=== '''Due diligence function of the Enterprise Architecture Division:''' ===

=== '''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 <u>''[[GC Enterprise Architecture/Framework|Enterprise Architecture Framework]],''</u> 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.

The Board is co-chaired by the Chief Technology Officer (CTO) of Canada (TBS) and the CTO of SSC, with membership drawn from across the major departments and specialist roles in TBS and SSC.    

The Board is co-chaired by the Chief Technology Officer (CTO) of Canada (TBS) and the CTO of SSC, with membership drawn from across the major departments and specialist roles in TBS and SSC.    

* Develop target architecture standards across the domains of Business, Information/Data, Application, Technology and Security (BIATS)

* Develop target architecture standards across the domains of Business, Information/Data, Application, Technology and Security (BIATS)

* Guide implementation of the [[GC Enterprise Architecture/Framework|<u>''Enterprise Architecture Framework''</u>]] when reviewing departmental proposals for alignment (to be published soon on Canada.ca)

* 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

* 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.

* 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 [[GC Service & Digital Target Enterprise Architecture|'''<u>"</u>'''<u>''Service & Digital Target Enterprise Architecture - White Paper"''</u>]]

Further information is available in the [[GC Service & Digital Target Enterprise Architecture|'''"'''''Service & Digital Target Enterprise Architecture - White Paper"'']]

=== '''When to consult the Enterprise Architecture Division:''' ===

=== '''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|<u>''When to come''</u>]] 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.

=== '''Key due diligence questions to consider:''' ===

=== '''Key due diligence questions to consider:''' ===

* Does the proposed project/investment meet the [[GC Enterprise Architecture/Board/When to come|<u>''threshold criteria''</u>]] 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?  

* To what extent does the project align to the criteria in the [[GC Enterprise Architecture/Framework|<u>''Enterprise Architecture Framework''</u>]]?

* To what extent does the project align to the criteria in the [[GC Enterprise Architecture/Framework|''Enterprise Architecture Framework'']]?

* Is the initiative aligned with the [https://www.canada.ca/en/government/system/digital-government/government-canada-digital-standards.html <u>''Government of Canada Digital Standards''</u>]?  

* Is the initiative aligned with the [https://www.canada.ca/en/government/system/digital-government/government-canada-digital-standards.html ''Government of Canada Digital Standards'']?  

** Note: The checklist of criteria applied in the assessments is found in the appendices of the <u>''[[Media:2020-12-15-GC EARB Presenter GENERAL.pptx|GC EARB Presenter Template]]''</u> used for departmental submissions to GC EARB.

** Note: The checklist of criteria applied in the assessments is found in the appendices of the ''[[Media:2020-12-15-GC_EARB_Presenter_GENERAL.pptx|GC EARB Presenter Template]]''  used for departmental submissions to GC EARB.

* Would the client department benefit from an engagement with the GC Enterprise Architecture team to help draft the [[Media:2020-12-15-GC EARB Presenter GENERAL.pptx|GC EARB presenter template]] for the project?

* Would the client department benefit from an engagement with the GC Enterprise Architecture team to help draft the [[Media:2020-12-15-GC_EARB_Presenter_GENERAL.pptx|''GC EARB presenter template'']] for the project?

* Is there an existing [[GC Enterprise Architecture/Enterprise Solutions|<u>''Enterprise Solution''</u>]] that can be leveraged by the project?

* Is there an existing [[GC Enterprise Architecture/Enterprise Solutions|''Enterprise Solution'']] that can be leveraged by the project?

* 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?

=== '''Linkages with other policies:''' ===

=== '''Linkages with other policies:''' ===

* [https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=31300 <u>Policy on Results</u>]

* [https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=31300 Policy on Results]

Ultimately the architectures and solutions reviewed at the GC EARB are intended to support the mandates and programs of departments (which are key elements of the business architecture), and to bring about improved results

Ultimately the architectures and solutions reviewed at the GC EARB are intended to support the mandates and programs of departments (which are key elements of the business architecture), and to bring about improved results

* [https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=32593&section=procedure&p=C <u>Policy on the Planning and Management of Investments</u>]

* [https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=32593&section=procedure&p=C Policy on the Planning and Management of Investments]

GC EARB reviews are generally tied to the IM/IT project management framework, and thus linked to the investment management lifecycle

GC EARB reviews are generally tied to the IM/IT project management framework, and thus linked to the investment management lifecycle

* [https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=16578 <u>Policy on Government Security</u>], Directive on Identity Management, Directive on Security Management

* [https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=16578 Policy on Government Security], Directive on Identity Management, Directive on Security Management

Security Architecture layer

Security Architecture layer

* [https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=12510 <u>Interim Policy on Privacy Protection</u>,] Interim Directive on Privacy Practices

* [https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=12510 Interim Policy on Privacy Protection,] Interim Directive on Privacy Practices

Privacy layer

Privacy layer

=== '''Additional sources of information:''' ===

=== '''Additional sources of information:''' ===

* [[GC Enterprise Architecture/Board|<u>''GC EARB wiki on GCcollab''</u>]]

* [[GC Enterprise Architecture/Board|''GC EARB wiki on GCcollab'']]

* [[GC Enterprise Architecture/Board/Forward Agenda|<u>''GC    EARB forward agenda''</u>]]

* [[GC Enterprise Architecture/Board/Forward Agenda|''GC    EARB forward agenda'']]

* [https://gcconnex.gc.ca/groups/profile/29755185/gc-enterprise-architecture-review-board-comite-dexamen-de-larchitecture-dentreprise-du-gc?language=en <u>''GC EARB home page on GCconnex''</u>]     

* [https://gcconnex.gc.ca/groups/profile/29755185/gc-enterprise-architecture-review-board-comite-dexamen-de-larchitecture-dentreprise-du-gc?language=en ''GC EARB home page on GCconnex'']     

* [[GC Enterprise Architecture|<u>''Enterprise Architecture wiki on    GCcollab''</u>]]

* [[GC Enterprise Architecture|''Enterprise Architecture wiki on    GCcollab'']]

* [[gccollab:groups/profile/1896301/enenterprise-architecture-community-of-practicefrcommunitu00e9-de-pratique-de-architecture-integru00e9e|<u>''Enterprise    Architecture Community of Practice group on GCconnex''</u>]]

* [[gccollab:groups/profile/1896301/enenterprise-architecture-community-of-practicefrcommunitu00e9-de-pratique-de-architecture-integru00e9e|''Enterprise    Architecture Community of Practice group on GCconnex'']]

=== '''Example submission related to GC EARB:''' ===

=== '''Example submission related to GC EARB:''' ===

* ''[[GC Enterprise Architecture/Board/Past Sessions|Past meetings - agendas and related presentations]]'' (mostly PDF copies available for viewing by GC community)

* ''[[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 <u>''EA Team GCdocs folder''</u>] (links to original documents and presentations organized by topic)  

* [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 <u>''OCIO Secretariat GCdocs folder''</u>] (links to original documents and presentations organized by meeting date)

* [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)

=== '''How to contact the Enterprise Architecture Division?''' ===

=== '''How to contact the Enterprise Architecture Division?''' ===

The team actively monitors a generic mailbox for submissions and engagements at <u>[Mailto:EA.AE@tbs-sct.gc.ca ''EA.AE@tbs-sct.gc.ca'']</u>. 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.