Difference between revisions of "GC Enterprise Architecture/10 Things You Need to Know"
Jump to navigation
Jump to search
| (48 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | {{OCIO GCEA Header}} | |
| − | + | <multilang> | |
| − | + | @en| | |
| − | | | + | === '''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=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 | * ''[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| | + | * [[GC Enterprise Architecture/Framework|''GC Enterprise Architecture Framework'']] (to be published soon on Canada.ca) |
| − | === ''' | + | === '''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. |
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. | ||
| Line 35: | Line 15: | ||
* 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|Enterprise Architecture Framework]] 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 [[ | + | 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:''' === |
| − | 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. | ||
| − | === ''' | + | === '''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. | ||
| − | === ''' | + | === '''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? | |
| − | + | * 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 ''Government of Canada Digital Standards'']? | |
| − | + | ** Note: The checklist of criteria applied in the assessments is found in the appendices of the ''[[Media:2022-11-30_GC_EARB_Presenter_GENERAL_EN.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:2022-11-30_GC_EARB_Presenter_GENERAL_EN.pptx|''GC EARB presenter template'']] for 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? | |
| − | === ''' | + | === '''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. | ||
| Line 72: | Line 52: | ||
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. | ||
| − | === ''''' | + | === '''Linkages with other policies:''' === |
| − | + | * [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 | ||
| + | * [https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=32593§ion=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 | ||
| + | * [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 | ||
| + | * [https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=12510 Interim Policy on Privacy Protection,] Interim Directive on Privacy Practices | ||
| + | Privacy layer | ||
| + | |||
| + | === '''Additional sources of information:''' === | ||
| + | * [[GC Enterprise Architecture/Board|''GC EARB wiki on GCcollab'']] | ||
| + | * [[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 ''GC EARB home page on GCconnex''] | ||
| + | * [[GC Enterprise Architecture|''Enterprise Architecture wiki on GCcollab'']] | ||
| + | * [[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:''' === | ||
| + | * ''[[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) | ||
| + | |||
| + | === '''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. | ||
| + | @fr| | ||
| + | === '''Politique(s) et Directive(s) que la Division de l’Architecture d’Intégrée ont Responsable de:''' === | ||
| + | * ''[https://www.tbs-sct.gc.ca/pol/doc-fra.aspx?id=32603 Politique sur les Services et la Numérique]'' – article 4.1.2.4 | ||
| + | * ''[https://www.tbs-sct.gc.ca/pol/doc-fra.aspx?id=32601 Directive sur les Services et la Numérique]'' – articles 4.1.1.2 to 4.1.1.5 | ||
| + | * [[GC Enterprise Architecture/Framework|''Cadre d’Architecture d’Intégré GC'']] (to be published soon on Canada.ca) | ||
| + | |||
| + | === '''Fonction de Diligence Raisonnable de la Division de l’Architecture d’Intégrée:''' === | ||
| + | Le CEAI GC a été créé par le dirigeant principal de l’information du Canada, comme l’exige la Politique sur les services et le numérique, et a pour mandat de définir les normes d’architecture actuelles et cibles pour le gouvernement du Canada et d’examiner les propositions ministérielles en vue de leur harmonisation. Le plus important de ces normes d’architecture est le service GC et l’architecture d’intégrée d'état cible numérique. Il s’agit maintenant de la principale référence en matière d’architecture pour tous les ministères (tel qu’il s’applique) pour l’activation numérique des services du gouvernement du Canada. L’harmonisation avec le modèle de l’État cible, tel qu’évalué par rapport aux critères du ''[[GC Enterprise Architecture/Framework|Cadre d’Architecture Intégrée]],'' éclaire l’approbation des propositions d’investissement numérique ministérielles présentées au CEAI GC. | ||
| + | |||
| + | Le conseil est coprésidé par le dirigeant principal de la technologie (CTO) du Canada (SCT) et le chef de la direction de SPC, composé de membres provenant des principaux ministères et de rôles spécialisés au sein du SCT et de la SSC. | ||
| + | |||
| + | Pour remplir le mandat de CEAI GC, l'Architecture d’Intégrée en BDPI en SCT collabore avec les architectes ministériels pour: | ||
| + | * Développer des normes d’architecture cible dans les domaines de l’entreprise, de l’information / données, des applications, de la technologie et de la sécurité (BIATS) | ||
| + | |||
| + | * Guider la mise en œuvre du [[GC Enterprise Architecture/Framework|''Cadre d’Architecture Intégrée'']] lors de l’examen des propositions ministérielles d’harmonisation (qui sera publié prochainement le Canada.ca) | ||
| + | |||
| + | * Assurer la coordination centrale des réseaux d’expertise pour l’architecture intégrée, les données, l'infonuagique, l’espace de travail numérique et le cyberespace afin de développer des solutions d’entreprise et de partager les meilleures pratiques | ||
| + | |||
| + | * Communiquer avec les responsables ministériels des projets et de l’architecture pour s’assurer que leurs propositions sont bien préparées avant la date d’examen du CEAI GC, et fournir des conseils et des recommandations pour améliorer l’harmonisation. | ||
| + | De plus amples informations sont disponibles dans le [[GC Service & Digital Target Enterprise Architecture|'''"'''''Architecture intégrée cible des services et du numérique Livre blanc"'']] | ||
| + | |||
| + | === '''Quand Consulter la Division de l’Architecture d’Intégrée:''' === | ||
| + | L’équipe d’architecture d’intégrée du GC est disponible pour dialoguer avec les ministères si le ministère communique directement avec l’équipe ou par l’entremise du Secrétariat du comité du DCI, par exemple, lorsque le ministère est tenu de présenter un investissement ou un projet numérique au CEAI GC pour examen et approbation, tel qu’il est indiqué dans le [[GC Enterprise Architecture/Board/When to come|''Quand Venir'']] sur le wiki CEAI GC. | ||
| + | |||
| + | La présentation du CEAI GC a généralement lieu après la fin du cas conceptuel et avant la présentation au Conseil du Trésor, le cas échéant. Les projets qui ne sont pas l’objet d’une soumission de TB peuvent également être tenus de présenter au CEAI GC. Il est terminé dans la phase de planification et de conception du cycle de vie du projet, avant le début de l’exécution formelle. Il expliquera comment le problème opérationnel est résolu par la solution proposée et démontrera l’harmonisation avec les normes numériques et les exigences architecturales du GC. Il peut inclure une analyse des options menant à la solution recommandée. | ||
| + | |||
| + | === '''Types d’Autorités Liées à la Politique''' (lien vers la page Web des autorités couramment recherchées). === | ||
| + | La présentation d’un projet devant le CEAI GC en résulte à une approbation et à une directive du dirigeant principal de l’information du gouvernement du Canada. Bien qu’aucun pouvoir du Conseil du Trésor ne soit sollicité dans le cadre du processus d’examen de l’architecture d’intégrée, lorsqu’une communication du Conseil du Trésor demande des autorisations de lutte contre la tuberculose (p. ex., financement pour le projet ou approbations de projet) plus tard dans le processus, une architecture approuvée ferait partie de la documentation nécessaire au Bureau du dirigeant principal de l’information pour appuyer un projet. | ||
| + | |||
| + | === '''Principales Questions de Diligence Raisonnable à Considéré:''' === | ||
| + | * Est-ce-que le projet ou l’investissement proposé respecter les [[GC Enterprise Architecture/Board/When to come|''critères de seuil'']] établis dans la Directive sur les Services et le Numérique pour exiger l’examen du CEAI GC? | ||
| + | |||
| + | * Dans quelle mesure le projet s’aligne-t-il sur les critères du [[GC Enterprise Architecture/Framework|''Cadre d’Architecture Intégrée'']]? | ||
| + | |||
| + | * Est-ce-que l’initiative alignée avec les [https://www.canada.ca/fr/gouvernement/systeme/gouvernement-numerique/normes-numeriques-gouvernement-canada.html''Normes Relatives au Numérique du Gouvernement du Canada'']? | ||
| + | ** Note: La liste de contrôle des critères appliqués dans les évaluations se trouve dans les annexes du ''[[Media:2022-11-30_GC_EARB_Presenter_GENERAL_FR.pptx|Modèle de Présentateur CEAI GC]]'' utilisé pour les soumissions ministérielles au CEAI GC. | ||
| − | + | * Est-ce-que le service client profiterait d'une collaboration avec l’équipe d’architecture d’intégrée pour aider à rédiger le [[Media:2022-11-30_GC_EARB_Presenter_GENERAL_FR.pptx|''Modèle de Présentateur CEAI GC'']] pour le projet? | |
| − | + | * Existe-t-il un [[GC Enterprise Architecture/Enterprise Solutions|''Solution d'Enterprise'']] qui peuvent être exploités par le projet? | |
| − | + | * Y a-t-il d’autres ministères qui travaillent sur des solutions pour la même capacité opérationnelle qui devraient être engagés? | |
| − | + | === '''Comment la Division de l’Architecture d’Intégrée fournit-elle des Conseils?''' === | |
| + | Dans la plupart des cas, l’équipe d’architecture d’intégrée est consultée pour un examen préliminaire de l’architecture de solution proposée par un ministère afin de fournir des conseils sur la façon de renforcer la présentation afin de mettre en évidence les points clés, a démontré l’harmonisation prévue avec les exigences du GC et éviter les problèmes qui entraveraient l’approbation. L’équipe d’AI produit également une évaluation de l’architecture d’intégrée d’une page du projet qui est incluse dans le modèle dans le cadre de la trousse de révision, avec des notes sur l’alignement, une recommandation sur l’approbation, et les conditions possibles. | ||
| − | + | L’équipe d’AI collabore avec le Secrétariat du Comité du BDPI et d’autres experts en la matière clés du SCT et de la SSC pour examiner la préparation des prochains ordres du jour du CEAI GC avant les séances. Après les réunions, l’équipe d’AI aide également à la rédaction et à l’examen initial des comptes rendus de discussion. | |
| − | + | Les ministères peuvent également communiquer avec l’équipe d’AI pour obtenir des conseils généraux sur l’établissement ou la gestion de la pratique de l’architecture d’intégrée dans leur ministère, ou pour obtenir de l’information sur diverses considérations relatives à l’entreprise GC qui peuvent être liées à leurs projets. | |
| − | + | === '''Liens avec d’Autres Politiques:''' === | |
| + | * [https://www.tbs-sct.gc.ca/pol/doc-fra.aspx?id=31300 Politique sur les Résultats] | ||
| + | En fin de compte, les architectures et les solutions examinées au CEAI GC visent à appuyer les mandats et les programmes des ministères (qui sont des éléments clés de l’architecture opérationnelle) et à obtenir de meilleurs résultats. | ||
| + | * [https://www.tbs-sct.gc.ca/pol/doc-fra.aspx?id=32593 Politique sur la Planification et la Gestion des Investissements] | ||
| + | Les examens du CEAI GC sont généralement liés au cadre de gestion de projet de IM/IT et, par conséquent, liés au cycle de vie de la gestion des investissements. | ||
| + | * [https://www.tbs-sct.gc.ca/pol/doc-fra.aspx?id=16578 Politique sur la Sécurité du Gouvernement], | ||
| + | Directive sur la gestion de l’identité, Directive sur la gestion de la sécurité (couche d’architecture de sécurité) | ||
| + | * [https://www.tbs-sct.gc.ca/pol/doc-fra.aspx?id=12510 Politique sur la Protection de la Vie Privée] | ||
| + | Directive provisoire sur les pratiques en matière de protection de la vie privée (couche de protection de la vie privée) | ||
| − | === ''' | + | === '''Autres Sources d’Information:''' === |
| − | * [[GC Enterprise Architecture/Board|GC | + | * [[GC Enterprise Architecture/Board|''Wiki CEAI GC sur GCcollab'']] |
| − | * [[GC Enterprise Architecture/Board/Forward Agenda|GC | + | * [[GC Enterprise Architecture/Board/Forward Agenda|''Programme avancé du CEAI GC'']] |
| − | * GC | + | * [https://gcconnex.gc.ca/groups/profile/29755185/gc-enterprise-architecture-review-board-comite-dexamen-de-larchitecture-dentreprise-du-gc?language=fr ''Page d’Accueil du CEAI GC sur GCconnex''] |
| − | * [[GC Enterprise Architecture| | + | * [[GC Enterprise Architecture|''Wiki Architecture Intégrée sur GCcollab'']] |
| − | * | + | * [[gccollab:groups/profile/1896301/enenterprise-architecture-community-of-practicefrcommunitu00e9-de-pratique-de-architecture-integru00e9e|''Groupe de la Communauté de Pratique en Architecture d’Intégrée sur GCconnex'']] |
| − | === ''' | + | === '''Exemple de Soumission Liée à CEAI GC:''' === |
| − | * [[ | + | * ''[[GC Enterprise Architecture/Board/Past Sessions|Séances Passées - Ordres du Jour et Présentations Connexes]]'' (Principalement des copies PDF disponibles pour consultation par la communauté GC) |
| − | * [https://gcdocs.tbs-sct.gc.ca/gcdocs/llisapi.dll?func=ll&objId=27131364&objAction=browse&sort=name&viewType=1 | + | * [https://gcdocs.tbs-sct.gc.ca/gcdocs/llisapi.dll?func=ll&objId=27131364&objAction=browse&sort=name&viewType=1 ''Dossier GCdocs pour l'équipe d'AI''] (liens vers des documents originaux et des présentations organisées par sujet) |
| − | * [https://gcdocs.tbs-sct.gc.ca/gcdocs/llisapi.dll?func=ll&objId=26332823&objAction=browse&viewType=1 | + | * [https://gcdocs.tbs-sct.gc.ca/gcdocs/llisapi.dll?func=ll&objId=26332823&objAction=browse&viewType=1 ''Dossier GCdocs du Secrétariat du BDPI''] (liens vers des documents originaux et des présentations organisées par date de réunion) |
| − | === ''' | + | === '''Comment Contacter la Division de l’Architecture d’Intégrée ?''' === |
| − | + | L’équipe surveille activement une boîte aux lettres générique pour les soumissions et les engagements à [Mailto:EA.AE@tbs-sct.gc.ca ''EA.AE@tbs-sct.gc.ca'']. Les analystes du secteur du programme sont encouragés à utiliser ce courriel, mais peuvent également communiquer directement avec les membres de l’équipe du cas conceptuel. | |
| + | </multilang> | ||
Latest revision as of 13:57, 14 December 2022
Policy(ies) and directive(s) the Enterprise Architecture Division responsible for:[edit | edit source]
- Policy on Service and Digital – article 4.1.2.4
- Directive on Service and Digital – articles 4.1.1.2 to 4.1.1.5
- GC Enterprise Architecture Framework (to be published soon on Canada.ca)
Due diligence function of the Enterprise Architecture Division:[edit | edit source]
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 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.
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 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 "Service & Digital Target Enterprise Architecture - White Paper"
When to consult the Enterprise Architecture Division:[edit | edit source]
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 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.
[edit | edit source]
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.
Key due diligence questions to consider:[edit | edit source]
- Does the proposed project/investment meet the 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 Enterprise Architecture Framework?
- Is the initiative aligned with the Government of Canada Digital Standards?
- Note: The checklist of criteria applied in the assessments is found in the appendices of the 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 GC EARB presenter template for the project?
- Is there an existing 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?
How does Enterprise Architecture Division provide advice?[edit | edit source]
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.
The EA team collaborates with the OCIO Committee Secretariat and other key subject matter experts from TBS and SSC to review prepare upcoming GC EARB agendas in advance of the sessions. After the meetings, the EA team also helps with the drafting and initial review of the records of discussion.
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.
Linkages with other policies:[edit | edit source]
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
GC EARB reviews are generally tied to the IM/IT project management framework, and thus linked to the investment management lifecycle
- Policy on Government Security, Directive on Identity Management, Directive on Security Management
Security Architecture layer
- Interim Policy on Privacy Protection, Interim Directive on Privacy Practices
Privacy layer
Additional sources of information:[edit | edit source]
- GC EARB wiki on GCcollab
- GC EARB forward agenda
- GC EARB home page on GCconnex
- Enterprise Architecture wiki on GCcollab
- Enterprise Architecture Community of Practice group on GCconnex
[edit | edit source]
- Past meetings - agendas and related presentations (mostly PDF copies available for viewing by GC community)
- EA Team GCdocs folder (links to original documents and presentations organized by topic)
- OCIO Secretariat GCdocs folder (links to original documents and presentations organized by meeting date)
How to contact the Enterprise Architecture Division?[edit | edit source]
The team actively monitors a generic mailbox for submissions and engagements at 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.
