Difference between revisions of "GC Enterprise Architecture/Enterprise Solutions"
m |
m |
||
(12 intermediate revisions by 3 users not shown) | |||
Line 4: | Line 4: | ||
== The following content is a synopsis of the December 15, 2020 DM CEPP presentation. == | == The following content is a synopsis of the December 15, 2020 DM CEPP presentation. == | ||
− | *<u>[[Media:DMCEPP EnterpriseSolutions Dec 15 20 v3.pptx|Advancing Enterprise Solutions]]</u> | + | *<u>[[Media:DMCEPP EnterpriseSolutions Dec 15 20 v3.pptx|Advancing Enterprise Solutions - Presentation to the DM CEPP on Dec 15, 2020]]</u> |
== What is enterprise? == | == What is enterprise? == | ||
Line 26: | Line 26: | ||
=== How to get your solution declared as Enterprise Solution === | === How to get your solution declared as Enterprise Solution === | ||
− | * To get your solution declared as an Enterprise Solution in GC EARB, please fill out a [[Media: | + | * To get your solution declared as an Enterprise Solution in GC EARB, please fill out a <u>[[Media:2022-03-09-GC EARB Presenter Enterprise Solution.pptx|special GC EARB Presenter Template]] ([[Media:2022-03-09-GC_EARB_Presenter_Enterprise_Solution_FR.pptx|Special GC EARB French Presenter Template]])</u> specifically for Enterprise Solution. |
It is similar to the regular GC EARB deck template with additional pages added to provide supporting rationale of why your solution needs to be declared as an Enterprise Solution and that you have fulfilled all the necessary requirements to support an enterprise solution. | It is similar to the regular GC EARB deck template with additional pages added to provide supporting rationale of why your solution needs to be declared as an Enterprise Solution and that you have fulfilled all the necessary requirements to support an enterprise solution. | ||
− | * When ready, then look at [[GC_Enterprise_Architecture/Board/Forward_Agenda| forward agenda]] and send the deck along with a request to [mailto:EA.AE@tbs-sct.gc.ca EA team] to schedule a date for GC EARB | + | * When ready, then look at <u>[[GC_Enterprise_Architecture/Board/Forward_Agenda| forward agenda]]</u> and send the deck along with a request to <u>[mailto:EA.AE@tbs-sct.gc.ca EA team]</u> to schedule a date for GC EARB |
* GC Enterprise Architecture Team will contact you to review and conduct initial assessment with the extended EA team. | * GC Enterprise Architecture Team will contact you to review and conduct initial assessment with the extended EA team. | ||
Line 71: | Line 71: | ||
== Enterprise Solutions Framework Assessment Key Findings == | == Enterprise Solutions Framework Assessment Key Findings == | ||
− | = | + | {| class="wikitable" |
+ | |+ Key Findings | ||
+ | |- | ||
+ | !Governance !! Culture !! Solutions | ||
+ | |- | ||
+ | | | ||
'''''OK -''''' Pilots have been able to describe their solutions using the BCM, identify the business problem, and value proposition to address user needs | '''''OK -''''' Pilots have been able to describe their solutions using the BCM, identify the business problem, and value proposition to address user needs | ||
Line 79: | Line 84: | ||
'''''Issue -''''' Departments are not mandated and lack incentives to provide services to other departments, need a dedicated organization for enterprise solutions. | '''''Issue -''''' Departments are not mandated and lack incentives to provide services to other departments, need a dedicated organization for enterprise solutions. | ||
− | |||
'''''Issue -''''' Cost recovery and appropriation models are adequate for operational costs, but up-front funding is required for initial development and evolution of enterprise solutions. | '''''Issue -''''' Cost recovery and appropriation models are adequate for operational costs, but up-front funding is required for initial development and evolution of enterprise solutions. | ||
− | + | || | |
− | |||
'''''OK -''''' Departments are ready to buy into Enterprise solutions once they exist, but lack of available ready to use solutions result in departments developing their own. | '''''OK -''''' Departments are ready to buy into Enterprise solutions once they exist, but lack of available ready to use solutions result in departments developing their own. | ||
Line 88: | Line 91: | ||
'''''Issue -''''' Mandate use and appropriate departmental funds. Define a clear role and responsibility for users to determine needs and for the Business Owners and Service Provider to be accountable. | '''''Issue -''''' Mandate use and appropriate departmental funds. Define a clear role and responsibility for users to determine needs and for the Business Owners and Service Provider to be accountable. | ||
− | + | || | |
− | |||
'''''OK -''''' Identifying and developing enterprise solutions is not a problem, focus needs to be on governance and culture | '''''OK -''''' Identifying and developing enterprise solutions is not a problem, focus needs to be on governance and culture | ||
Line 95: | Line 97: | ||
'''''OK -''''' Cloud base solutions from public cloud service providers are enabling business owners to envision enterprise solutions but they need technical partnerships from dedicated solution providers to provision IT | '''''OK -''''' Cloud base solutions from public cloud service providers are enabling business owners to envision enterprise solutions but they need technical partnerships from dedicated solution providers to provision IT | ||
+ | |} | ||
== Proposed Roles and Responsibilities for Enterprise solutions == | == Proposed Roles and Responsibilities for Enterprise solutions == | ||
− | |||
+ | {| class=wikitable | ||
+ | |+ Roles and Responsibilities | ||
+ | ! Stakeholders, defines ”who” | ||
+ | | | ||
Stakeholders in the form of a ‘product board’ determine and validate user needs, prioritize the delivery roadmap and manage the related expenditures. | Stakeholders in the form of a ‘product board’ determine and validate user needs, prioritize the delivery roadmap and manage the related expenditures. | ||
− | + | *business/program representatives from across departments | |
− | + | *sponsors enterprise solution | |
− | + | *identify users | |
− | + | *determine user needs | |
− | + | *consumes | |
− | + | *contributes funds | |
− | + | |- | |
− | + | ! Business Owner, defines ”what” | |
− | + | | | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
The Business Owner has overall accountability for delivering on the business outcomes and achieving the benefits that a solution is meant to enable or facilitate. | The Business Owner has overall accountability for delivering on the business outcomes and achieving the benefits that a solution is meant to enable or facilitate. | ||
− | + | *Defines the required capabilities and intended business outcomes and benefits | |
− | + | *Serves as sponsor and is accountable for the achievement of the business outcomes and benefits following implementation | |
− | + | *Establishes and maintains governance | |
− | + | *Secures funding and resources and provides oversight | |
− | + | *Consults with and engages stakeholders and other implicated parties to ensure alignment towards delivery | |
− | + | *Reviews and signs-off on key strategic risks | |
− | + | *Authorizes the IT service | |
− | + | *Oversees data stewardship practices at the production solution-level | |
− | + | *Creates roadmap for service or product improvements | |
− | + | |- | |
− | + | ! Service Provider, defines ”how” | |
− | + | | | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
The Service Provider operates and manages IT solutions and/or services and provides them to end users. | The Service Provider operates and manages IT solutions and/or services and provides them to end users. | ||
− | + | *Responsible on behalf of an organization for requirements definitions, service delivery, security and reliability | |
+ | *Implement the requirements | ||
+ | *Signs off on platform scope | ||
+ | *Collect data to measure service levels and key performance indicators | ||
+ | *Ensure compliance with standards | ||
+ | *Monitor, test and adjust as required | ||
+ | *Support innovative products and services | ||
+ | *Conduct security assessments | ||
+ | |} | ||
− | + | == Proposed Governance for Enterprise solutions == | |
− | + | === '''DM CEPP''' === | |
− | + | • Enterprise Business Direction | |
− | • | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
=== '''Product management board per solution''' === | === '''Product management board per solution''' === | ||
• Cross departmental stakeholder representation | • Cross departmental stakeholder representation | ||
− | |||
− | |||
− | |||
=== '''GC EARB''' === | === '''GC EARB''' === | ||
Line 168: | Line 153: | ||
== Draft DM CEPP presentation still to be presented == | == Draft DM CEPP presentation still to be presented == | ||
− | *<u>[[Media:DMCEPP Enterprise Solutions May 5 2021 GARTNER Updates.pptx|Updates and progress | + | *<u>[[Media:DMCEPP Enterprise Solutions May 5 2021 GARTNER Updates.pptx|Updates and progress on Enterprise Solution - May 17, 2021]]</u> |
== The following initiatives endorsed by GC EARB have characteristics of Enterprise Solutions == | == The following initiatives endorsed by GC EARB have characteristics of Enterprise Solutions == | ||
Line 221: | Line 206: | ||
Case Management: | Case Management: | ||
− | * [https://gcconnex.gc.ca/file/view/ | + | * [https://gcconnex.gc.ca/file/view/52272014/gc-earb-2019-08-22-02-gc-case-gc-earb-2019-08-22-02-gc-case-pdf?language=en GCcase Cloud Enterprise platform for Case Management, 2019-08-22] |
* [https://gcconnex.gc.ca/file/view/39898395/gc-earb-2018-06-28-06-a-gccase-pdf?language=en GCcase Service catalogue,2018-06-28] | * [https://gcconnex.gc.ca/file/view/39898395/gc-earb-2018-06-28-06-a-gccase-pdf?language=en GCcase Service catalogue,2018-06-28] | ||
* [https://gcconnex.gc.ca/file/view/36167160/gc-earb-2018-03-08-02-scms-pdf?language=en Shared Case Management Solution (SCMS), 2018-03-08] | * [https://gcconnex.gc.ca/file/view/36167160/gc-earb-2018-03-08-02-scms-pdf?language=en Shared Case Management Solution (SCMS), 2018-03-08] | ||
Line 310: | Line 295: | ||
* [https://cloud-broker.canada.ca/s/?language=en_CA Government of Canada Cloud Brokering Services] | * [https://cloud-broker.canada.ca/s/?language=en_CA Government of Canada Cloud Brokering Services] | ||
* [https://gcconnex.gc.ca/file/view/45648501/gc-earb-2019-01-24-03-overall-cloud-program-pdf?language=en Overall Cloud Program, 2019-01-24] | * [https://gcconnex.gc.ca/file/view/45648501/gc-earb-2019-01-24-03-overall-cloud-program-pdf?language=en Overall Cloud Program, 2019-01-24] | ||
− | * [[ | + | * [[GC_Cloud_Infocentre|Cloud Infocentre, Everything you need to know for Cloud & DevOps]] |
* [https://gcconnex.gc.ca/file/view/58109995/gc-earb-2019-12-19-02-gc-cloud-enablement-cloud-connection-patterns-pptx?language=en GC Cloud Enablement: Cloud Connection Patterns, 2019-12-19] | * [https://gcconnex.gc.ca/file/view/58109995/gc-earb-2019-12-19-02-gc-cloud-enablement-cloud-connection-patterns-pptx?language=en GC Cloud Enablement: Cloud Connection Patterns, 2019-12-19] | ||
Line 402: | Line 387: | ||
* Jobs.gc.ca | * Jobs.gc.ca | ||
− | '''ESDC''' Canada.ca '''SSC''' | + | '''ESDC''' |
+ | |||
+ | * [https://gcconnex.gc.ca/file/view/38370966/ceai-gc-2018-05-10-02-12-presentation-de-edsc-pdf?language=en Canada.ca, 2018-05-10] | ||
+ | |||
+ | '''SSC''' | ||
* Email | * Email | ||
Line 464: | Line 453: | ||
== Le contenu suivant est une recherche menée par l’équipe EA après la présentation du CEPP DM du 15 décembre 2020. == | == Le contenu suivant est une recherche menée par l’équipe EA après la présentation du CEPP DM du 15 décembre 2020. == | ||
− | == | + | == Principales conclusions de l’évaluation du cadre des solutions d’entreprise == |
− | = | + | {| class="wikitable" |
+ | |+ Principales conclusions | ||
+ | |- | ||
+ | !Gouvernance !! Culture !! Solutions | ||
+ | |- | ||
+ | | | ||
'''''OK -''''' Les pilotes ont été en mesure de décrire leurs solutions à l’aide du BCM, d’identifier le problème commercial et la proposition de valeur pour répondre aux besoins des utilisateurs. | '''''OK -''''' Les pilotes ont été en mesure de décrire leurs solutions à l’aide du BCM, d’identifier le problème commercial et la proposition de valeur pour répondre aux besoins des utilisateurs. | ||
Line 476: | Line 470: | ||
'''''Problème -''''' Les modèles de recouvrement des coûts et d’affectation des crédits sont adéquats pour les coûts opérationnels, mais un financement initial est nécessaire pour le développement initial et l’évolution des solutions d’entreprise. | '''''Problème -''''' Les modèles de recouvrement des coûts et d’affectation des crédits sont adéquats pour les coûts opérationnels, mais un financement initial est nécessaire pour le développement initial et l’évolution des solutions d’entreprise. | ||
− | + | || | |
− | |||
'''''OK -''''' Les départements sont prêts à acheter des solutions d’entreprise une fois qu’elles existent, mais le manque de solutions prêtes à l’emploi disponibles entraîne le développement des leurs par les départements. | '''''OK -''''' Les départements sont prêts à acheter des solutions d’entreprise une fois qu’elles existent, mais le manque de solutions prêtes à l’emploi disponibles entraîne le développement des leurs par les départements. | ||
Line 483: | Line 476: | ||
'''''Problème -''''' Utilisation du mandat et fonds ministériels appropriés. Définissez un rôle et une responsabilité clairs pour les utilisateurs afin de déterminer les besoins et pour les propriétaires opérationnelle et le fournisseur de services d’être responsables. | '''''Problème -''''' Utilisation du mandat et fonds ministériels appropriés. Définissez un rôle et une responsabilité clairs pour les utilisateurs afin de déterminer les besoins et pour les propriétaires opérationnelle et le fournisseur de services d’être responsables. | ||
− | + | || | |
− | |||
'''''OK -''''' Identifier et développer des solutions d’entreprise n’est pas un problème, l’accent doit être mis sur la gouvernance et la culture. | '''''OK -''''' Identifier et développer des solutions d’entreprise n’est pas un problème, l’accent doit être mis sur la gouvernance et la culture. | ||
Line 490: | Line 482: | ||
'''''OK -'''''Les solutions de base cloud des fournisseurs de services de cloud public permettent aux propriétaires d’entreprise d’envisager des solutions d’entreprise, mais ils ont besoin de partenariats techniques de fournisseurs de solutions dédiés pour provisionner l’informatique. | '''''OK -'''''Les solutions de base cloud des fournisseurs de services de cloud public permettent aux propriétaires d’entreprise d’envisager des solutions d’entreprise, mais ils ont besoin de partenariats techniques de fournisseurs de solutions dédiés pour provisionner l’informatique. | ||
+ | |} | ||
− | == | + | == Rôles et Responsabilités Proposés pour les Solutions d’Entreprise == |
− | |||
+ | {| class=wikitable | ||
+ | |+ Rôles et Responsabilités | ||
+ | ! Parties prenantes, définit « qui » | ||
+ | | | ||
Les parties prenantes dans la forme d’un « tableau de produits » déterminent et valident les besoins des utilisateurs, hiérarchisent la feuille de route de livraison et gèrent les dépenses connexes. | Les parties prenantes dans la forme d’un « tableau de produits » déterminent et valident les besoins des utilisateurs, hiérarchisent la feuille de route de livraison et gèrent les dépenses connexes. | ||
− | |||
*Représentants des entreprises et des programmes de tous les ministères | *Représentants des entreprises et des programmes de tous les ministères | ||
*Sponsorise une solution d’entreprise | *Sponsorise une solution d’entreprise | ||
Line 502: | Line 497: | ||
*Consomme | *Consomme | ||
*Contribue aux fonds | *Contribue aux fonds | ||
− | + | |- | |
− | + | ! Propriétaire opérationnelle, définit « quoi » | |
− | + | | | |
Le propriétaire opérationnelle a la responsabilité globale d’obtenir les résultats de l’entreprise et d’obtenir les avantages qu’une solution est censée permettre ou faciliter. | Le propriétaire opérationnelle a la responsabilité globale d’obtenir les résultats de l’entreprise et d’obtenir les avantages qu’une solution est censée permettre ou faciliter. | ||
− | |||
*Définit les capacités requises et les résultats et avantages commerciaux escomptés | *Définit les capacités requises et les résultats et avantages commerciaux escomptés | ||
*Agit à titre de commanditaire et est responsable de l’atteinte des résultats et des avantages opérationnels après la implémentation | *Agit à titre de commanditaire et est responsable de l’atteinte des résultats et des avantages opérationnels après la implémentation | ||
Line 516: | Line 510: | ||
*Superviser les pratiques de gestion des données au niveau de la solution de production | *Superviser les pratiques de gestion des données au niveau de la solution de production | ||
*Crée une feuille de route pour les améliorations de service ou de produit | *Crée une feuille de route pour les améliorations de service ou de produit | ||
− | + | |- | |
− | + | ! Fournisseur de services, définit « comment » | |
− | + | | | |
Le fournisseur de services exploite et gère des solutions et/ou services informatiques et les fournit aux utilisateurs finaux. | Le fournisseur de services exploite et gère des solutions et/ou services informatiques et les fournit aux utilisateurs finaux. | ||
Line 529: | Line 523: | ||
*Soutenir des produits et services innovants | *Soutenir des produits et services innovants | ||
*Effectuer des évaluations de sécurité | *Effectuer des évaluations de sécurité | ||
+ | |} | ||
− | == | + | ==Solutions de Gouvernance d’Entreprise Proposées== |
+ | === ''' SMA CPPI''' === | ||
+ | : Direction commerciale de l’entreprise | ||
− | + | === '''Tableau de gestion des produits par solution''' === | |
: Représentation interdépartementale des intervenants | : Représentation interdépartementale des intervenants | ||
− | + | === '''CEAI GC''' === | |
− | |||
− | |||
− | |||
: Alignement sur le cadre d’architecture d’entreprise | : Alignement sur le cadre d’architecture d’entreprise | ||
Line 595: | Line 589: | ||
Gestion de cas: | Gestion de cas: | ||
− | * [https://gcconnex.gc.ca/file/view/ | + | * [https://gcconnex.gc.ca/file/view/52271937/ceai-gc-2019-08-22-02-gccas-ceai-gc-2019-08-22-02-gccas-pdf?language=en GCcase Cloud Enterprise platform for Case Management, 2019-08-22] |
* [https://gcconnex.gc.ca/file/view/39898395/gc-earb-2018-06-28-06-a-gccase-pdf?language=en GCcase Service catalogue,2018-06-28] | * [https://gcconnex.gc.ca/file/view/39898395/gc-earb-2018-06-28-06-a-gccase-pdf?language=en GCcase Service catalogue,2018-06-28] | ||
* [https://gcconnex.gc.ca/file/view/36167160/gc-earb-2018-03-08-02-scms-pdf?language=en Shared Case Management Solution (SCMS), 2018-03-08] | * [https://gcconnex.gc.ca/file/view/36167160/gc-earb-2018-03-08-02-scms-pdf?language=en Shared Case Management Solution (SCMS), 2018-03-08] | ||
Line 674: | Line 668: | ||
=== Architecture de la Technologie === | === Architecture de la Technologie === | ||
− | + | Accès: | |
* [https://gcconnex.gc.ca/file/view/79247716/e-binder-gc-earb-2021-04-22-pdf?language=en SSC - Network Device Authentication (NDA) Project, SSC - Endpoint Vulnerability Awareness and Security (EVAS), SSC – Security Information and Event Management (SIEM), SSC - Secure Remote Access Migration (SRAM), 2021-04-22] | * [https://gcconnex.gc.ca/file/view/79247716/e-binder-gc-earb-2021-04-22-pdf?language=en SSC - Network Device Authentication (NDA) Project, SSC - Endpoint Vulnerability Awareness and Security (EVAS), SSC – Security Information and Event Management (SIEM), SSC - Secure Remote Access Migration (SRAM), 2021-04-22] | ||
− | + | Infonuagique: | |
* [https://gcconnex.gc.ca/file/view/59227335/gc-earb-2020-01-17-03-stats-canada-drupal-reference-cloud-architecture-pptx?language=en Statistics Canada cloud architecture for Drupal, GC reference architecture for the GC, 2020-01-17] | * [https://gcconnex.gc.ca/file/view/59227335/gc-earb-2020-01-17-03-stats-canada-drupal-reference-cloud-architecture-pptx?language=en Statistics Canada cloud architecture for Drupal, GC reference architecture for the GC, 2020-01-17] | ||
* [https://gcconnex.gc.ca/file/view/59833196/gc-earb-2020-01-31-02-tbs-ssc-readiness-and-prioritization-for-cxp-connectivity-pdf?language=en Cloud eXchange Point (CXP) readiness process, 2020-01-31] | * [https://gcconnex.gc.ca/file/view/59833196/gc-earb-2020-01-31-02-tbs-ssc-readiness-and-prioritization-for-cxp-connectivity-pdf?language=en Cloud eXchange Point (CXP) readiness process, 2020-01-31] | ||
Line 684: | Line 678: | ||
* [https://cloud-broker.canada.ca/s/?language=en_CA Government of Canada Cloud Brokering Services] | * [https://cloud-broker.canada.ca/s/?language=en_CA Government of Canada Cloud Brokering Services] | ||
* [https://gcconnex.gc.ca/file/view/45648501/gc-earb-2019-01-24-03-overall-cloud-program-pdf?language=en Overall Cloud Program, 2019-01-24] | * [https://gcconnex.gc.ca/file/view/45648501/gc-earb-2019-01-24-03-overall-cloud-program-pdf?language=en Overall Cloud Program, 2019-01-24] | ||
− | * [[ | + | * [[GC_Cloud_Infocentre|Le centre d'information de l'infonuagique, pour tous que vous voulez savoir de l'infonuagique et l'opérations de développement]] |
* [https://gcconnex.gc.ca/file/view/58109995/gc-earb-2019-12-19-02-gc-cloud-enablement-cloud-connection-patterns-pptx?language=en GC Cloud Enablement: Cloud Connection Patterns, 2019-12-19] | * [https://gcconnex.gc.ca/file/view/58109995/gc-earb-2019-12-19-02-gc-cloud-enablement-cloud-connection-patterns-pptx?language=en GC Cloud Enablement: Cloud Connection Patterns, 2019-12-19] | ||
− | + | Appareil: | |
* [https://gcconnex.gc.ca/file/view/73156556/e-binder-gc-earb-2020-12-17-pdf?language=en SSC – Government of Canada Smart Phone for Classified (SPfC) Project, 2020-12-17] | * [https://gcconnex.gc.ca/file/view/73156556/e-binder-gc-earb-2020-12-17-pdf?language=en SSC – Government of Canada Smart Phone for Classified (SPfC) Project, 2020-12-17] | ||
* [https://gcconnex.gc.ca/file/view/50167121/gc-earb-2019-06-13-03-enterprise-mobile-device-management-emdm-evolution-gc-earb-2019-06-13-03-enterprise-mobile-device-management-emdm-evolution-pdf?language=en Enterprise Mobile Device Management, 2019-06-13] | * [https://gcconnex.gc.ca/file/view/50167121/gc-earb-2019-06-13-03-enterprise-mobile-device-management-emdm-evolution-gc-earb-2019-06-13-03-enterprise-mobile-device-management-emdm-evolution-pdf?language=en Enterprise Mobile Device Management, 2019-06-13] | ||
Line 696: | Line 690: | ||
* [https://gcconnex.gc.ca/file/view/73156556/e-binder-gc-earb-2020-12-17-pdf?language=en SSC – Government of Canada Secret Infrastructure (GCSI) Expansion Project, 2020-12-17] | * [https://gcconnex.gc.ca/file/view/73156556/e-binder-gc-earb-2020-12-17-pdf?language=en SSC – Government of Canada Secret Infrastructure (GCSI) Expansion Project, 2020-12-17] | ||
− | Split | + | Tunnel de Split: |
* [https://gcconnex.gc.ca/file/view/65557446/gc-earb-2020-06-18-03-summary-of-split-tunneling-requests-pdf?language=en TBS – Process and status of Split Tunneling requests, 2020-06-18] | * [https://gcconnex.gc.ca/file/view/65557446/gc-earb-2020-06-18-03-summary-of-split-tunneling-requests-pdf?language=en TBS – Process and status of Split Tunneling requests, 2020-06-18] | ||
− | + | Politique/Norme/Cadre/Stratégies/Outils: | |
* [https://gcconnex.gc.ca/file/group/29755185/all#75734784 SSC – Network Modernization Strategy, 2021-02-25] | * [https://gcconnex.gc.ca/file/group/29755185/all#75734784 SSC – Network Modernization Strategy, 2021-02-25] | ||
Line 705: | Line 699: | ||
=== Architecture de Sécurité et Confidentialité === | === Architecture de Sécurité et Confidentialité === | ||
− | + | Gestion des identités et des accès: | |
* [https://gcconnex.gc.ca/file/view/50751216/gc-earb-2019-07-04-04-cyber-security-digital-identity-reference-architecture-gc-earb-2019-07-04-04-cyber-security-digital-identity-reference-architecture-pdf?language=en Cyber Security Digital Identity Reference Architecture, 2019-07-04] | * [https://gcconnex.gc.ca/file/view/50751216/gc-earb-2019-07-04-04-cyber-security-digital-identity-reference-architecture-gc-earb-2019-07-04-04-cyber-security-digital-identity-reference-architecture-pdf?language=en Cyber Security Digital Identity Reference Architecture, 2019-07-04] | ||
* [https://gcconnex.gc.ca/file/download/75092467 SSC - ICAS 2Key Implementation, 2020-02-11] | * [https://gcconnex.gc.ca/file/download/75092467 SSC - ICAS 2Key Implementation, 2020-02-11] | ||
Line 716: | Line 710: | ||
* [https://gcconnex.gc.ca/file/view/45223921/gc-earb-2019-01-10-03-update-of-the-gc-digital-identity-strategy-pdf?language=en Update of the GC Digital Identity Strategy, 2019-01-10] | * [https://gcconnex.gc.ca/file/view/45223921/gc-earb-2019-01-10-03-update-of-the-gc-digital-identity-strategy-pdf?language=en Update of the GC Digital Identity Strategy, 2019-01-10] | ||
− | + | Sécurité électronique: | |
* [https://gcconnex.gc.ca/file/view/71576468/ebinder-gc-earb-2020-11-19-pdf?language=en PSPC – Electronic Security System, 2020-11-19] | * [https://gcconnex.gc.ca/file/view/71576468/ebinder-gc-earb-2020-11-19-pdf?language=en PSPC – Electronic Security System, 2020-11-19] | ||
− | + | Sécurité des e-mails: | |
* [https://gcconnex.gc.ca/file/view/59833198/gc-earb-2020-01-31-03-tbs-cccs-enhancing-email-security-with-dmarc-pdf?language=en Enhancing email security with Domain-based Message Authentication, Reporting & Conformance (DMARC)., 2020-01-31] | * [https://gcconnex.gc.ca/file/view/59833198/gc-earb-2020-01-31-03-tbs-cccs-enhancing-email-security-with-dmarc-pdf?language=en Enhancing email security with Domain-based Message Authentication, Reporting & Conformance (DMARC)., 2020-01-31] | ||
− | + | Politique/Norme/Cadre/Stratégies/Outils: | |
* [https://gcconnex.gc.ca/file/view/48741427/gc-earb-2019-05-02-06-pan-canadian-trust-framework-update-pdf?language=en Pan-Canadian Trust Framework, 2019-05-02] | * [https://gcconnex.gc.ca/file/view/48741427/gc-earb-2019-05-02-06-pan-canadian-trust-framework-update-pdf?language=en Pan-Canadian Trust Framework, 2019-05-02] | ||
* [https://gcconnex.gc.ca/file/view/36167163/gc-earb-2018-03-08-04-https-everywhere-pdf?language=en HTTPS Everywhere” Standard, 2018-03-08] | * [https://gcconnex.gc.ca/file/view/36167163/gc-earb-2018-03-08-04-https-everywhere-pdf?language=en HTTPS Everywhere” Standard, 2018-03-08] | ||
</multilang> | </multilang> |
Latest revision as of 12:58, 21 February 2023
The following content is a synopsis of the December 15, 2020 DM CEPP presentation.[edit | edit source]
What is enterprise?[edit | edit source]
Enterprise is generally defined as “an organization” or “organizational unit”
In the GC, ‘enterprise’ refers to a whole-of-government holistic approach.
An enterprise approach can be applied various facets, like governance, solutions, standards and culture.
Enterprise solutions definition[edit | edit source]
Enterprise solutions are internal and external Government of Canada assets that can be re-used in and across multiple parts of the organization.
Why focus on enterprise solutions?[edit | edit source]
To “operate as one” and advance the CEPP mandate we propose to focus on enterprise solutions defined by to business capabilities.
Role of business capabilities[edit | edit source]
Business capabilities are an expression of what a business does and can do.
It is proposed that enterprise solutions are defined as business capabilities
How to get your solution declared as Enterprise Solution[edit | edit source]
- To get your solution declared as an Enterprise Solution in GC EARB, please fill out a special GC EARB Presenter Template (Special GC EARB French Presenter Template) specifically for Enterprise Solution.
It is similar to the regular GC EARB deck template with additional pages added to provide supporting rationale of why your solution needs to be declared as an Enterprise Solution and that you have fulfilled all the necessary requirements to support an enterprise solution.
- When ready, then look at forward agenda and send the deck along with a request to EA team to schedule a date for GC EARB
- GC Enterprise Architecture Team will contact you to review and conduct initial assessment with the extended EA team.
Once GC EARB approve it as an Enterprise Solution, then department needs to ready itself to provide service to other departments, which may include:
- create a MOU / agreement with the subscribing department for funding model and service model
What is needed for Enterprise Solutions to work in the GC?[edit | edit source]
The Enterprise Solutions framework has 3 facets.
Governance | Culture | Solutions |
---|---|---|
|
|
|
The following content is research conducted by the EA team after December 15, 2020 DM CEPP presentation.[edit | edit source]
Enterprise Solutions Framework Assessment Key Findings[edit | edit source]
Governance | Culture | Solutions |
---|---|---|
OK - Pilots have been able to describe their solutions using the BCM, identify the business problem, and value proposition to address user needs Issue - Enterprise solution opportunities lack a defined path to advance and as a result tend to fizzle out Issue - Operational enterprise solutions governance and support is at a low maturity level Issue - Departments are not mandated and lack incentives to provide services to other departments, need a dedicated organization for enterprise solutions. Issue - Cost recovery and appropriation models are adequate for operational costs, but up-front funding is required for initial development and evolution of enterprise solutions. |
OK - Departments are ready to buy into Enterprise solutions once they exist, but lack of available ready to use solutions result in departments developing their own. Issue - Need dedicated teams of “enterprise” business owners and service providers to develop, operate and evolve enterprise solutions, do we need a Shared Services organization to act as the service provider? Do expand SSC mandate to include applications? Issue - Mandate use and appropriate departmental funds. Define a clear role and responsibility for users to determine needs and for the Business Owners and Service Provider to be accountable. |
OK - Identifying and developing enterprise solutions is not a problem, focus needs to be on governance and culture OK - Pilots have been able to define the business problem and processes like the concept case and GCEARB are existing tools that can be used OK - Cloud base solutions from public cloud service providers are enabling business owners to envision enterprise solutions but they need technical partnerships from dedicated solution providers to provision IT |
Proposed Roles and Responsibilities for Enterprise solutions[edit | edit source]
Stakeholders, defines ”who” |
Stakeholders in the form of a ‘product board’ determine and validate user needs, prioritize the delivery roadmap and manage the related expenditures.
|
---|---|
Business Owner, defines ”what” |
The Business Owner has overall accountability for delivering on the business outcomes and achieving the benefits that a solution is meant to enable or facilitate.
|
Service Provider, defines ”how” |
The Service Provider operates and manages IT solutions and/or services and provides them to end users.
|
Proposed Governance for Enterprise solutions[edit | edit source]
DM CEPP[edit | edit source]
• Enterprise Business Direction
Product management board per solution[edit | edit source]
• Cross departmental stakeholder representation
GC EARB[edit | edit source]
• Alignment with Enterprise Architecture Framework
Draft DM CEPP presentation still to be presented[edit | edit source]
The following initiatives endorsed by GC EARB have characteristics of Enterprise Solutions[edit | edit source]
This registry of GC Enterprise Solutions are classified in the layers of the EA framework
Business Architecture[edit | edit source]
Business Intelligence:
Policy/Standard/Framework/Tools:
- Business Capability Model (GC BCM v2.1)
- Investing in Enterprise Capabilities at CBSA, 2020-01-31
- Extensions to the Directive on Service and Digital
- Digital Workspace Standards & Profiles. 2019-10-31
- Digital Workspace Reference Architecture, 2018-02-22
- Accessible Information and Communication Technology (ICT), 2019-06-19
- Standard for ITSM Integration, 2018-06-28
Information Architecture[edit | edit source]
Collaboration Platform:
Data Analytics:
Information Management:
- GCdocs and GCdocs Managed Service, 2018-05-31
- M365 as Systems that manages Information - Pathfinders, 2021-11-18, 2022-01-27
Policy/Standard/Framework/Strategies/Tools:
- A Framework for Government-Wide Data Governance & Stewardship, 2020-03-02
- Enterprise Data: Update to the Enterprise Architecture Review Board, 2019-07-04
- GC Data Strategy, 2018-05-31
- Enterprise Data Management and Architecture, 2018-05-31
- Data Sovereignty & Public Cloud, 2018-03-22
Application Architecture[edit | edit source]
ATIP:
Asset Management
Case Management:
- GCcase Cloud Enterprise platform for Case Management, 2019-08-22
- GCcase Service catalogue,2018-06-28
- Shared Case Management Solution (SCMS), 2018-03-08
Contact Centre:
Finance:
- TBS – TeamMate+ Enterprise Initiative, 2021-01-14
- FMT Coordinated Model and GC Digital Core, 2020-04-09
- PSPC SAP Moving Forward (to SAP S/4HANA) Project, 2020-04-09
- Financial Management Transformation (Endorsement of SAP software for OCG)
- SAP Hana licenses (initially for AAFC)
- CBSA SAP HANA
- Gartner Assessment of CRA/CBSA SAP Strategy, 2019-03-21
Grants & Contributions:
- Grants and Contributions, 2017-11-09
- NSERC/SSHRC/CIHR – Tri-Agency Grants Management Solution, 2019-11-14
- ISED Canadian Digital Adoption Program, 2021-07-29
- NRCAN - Greener Homes Program, 2021-05-06
- NRCAN - 2 Billion Trees Portal, 2021-10-07
- AAFC - GC Digital Platform, 2019-03-07
Geospatial:
- NRCan – Canadian Geospatial Platform (Federal Geospatial Platform), 2020-03-26
- Multi Department Impact Assessment and Cumulative Effects Related Systems
Human Resources:
- CSE – Next Gen HR and Pay for Heightened Security Departments - Follow up, 2020-12-17
- CSE – NextGen HR and Pay for High Security Organizations - 2020-06-04
- PSPC – Next Generation Travel Project, 2020-09-24
Interoperability:
- TBS – Application Programme Interface (API)-First Patterns for Platform as a Service (PaaS), 2021-03-25
- API Store, 2019-04-04
- GC Interoperability: X-Roads Update and Digital Exchange, 2018-03-08
- GC API for Interoperability
- Government of Canada Standards on APIs
Jobs / Talent Management:
- PSC – GC Jobs Transformation (GCJT), 2021-04-22
- VidCruiter SaaS, 2018-11-18
- Talent Cloud, 2018-07-12
Learning / Training:
- CSPS – Next Generation Digital Learning Environment - Follow up, 2021-01-14
- CSPS – Next Generation Digital Learning Environment, 2020-07-02
Project & Portfolio Management:
Procurement:
Security Clearance:
Service Management:
Search:
Policy/Standard/Framework/Strategies/Tools:
- SSC/TBS – Government of Canada Mainframe Landscape & Strategy Update, 2021-04-08
- GC Mainframe Strategy report, 2019-06-19
- GC Mainframe Strategy presentation
- Open Source Standards and Whitepaper, 2019-10-03
- Open First Whitepaper, 2018-09-13
Technology Architecture[edit | edit source]
Access:
Cloud:
- Statistics Canada cloud architecture for Drupal, GC reference architecture for the GC, 2020-01-17
- Cloud eXchange Point (CXP) readiness process, 2020-01-31
- SCED and A unified, consolidated, and regionalized hub strategy for interconnectivity to and from the GC infrastructure, 2019-12-05
- SSC Cloud Access Security Broker (CASB) service, 2020-07-30
- Government of Canada Cloud Brokering Services
- Overall Cloud Program, 2019-01-24
- Cloud Infocentre, Everything you need to know for Cloud & DevOps
- GC Cloud Enablement: Cloud Connection Patterns, 2019-12-19
Device:
- SSC – Government of Canada Smart Phone for Classified (SPfC) Project, 2020-12-17
- Enterprise Mobile Device Management, 2019-06-13
- Digital Communications and Collaboration (DCC): Network and Security Design Principles, 2020-03-26
- Digital Communications and Collaboration (DCC), 2019-11-14
Infrastructure:
Split Tunnel:
Policy/Standard/Framework/Strategies/Tools:
Security Architecture and Privacy[edit | edit source]
Electronic Security:
Email Security:
Identity & Access Management
- Cyber Security Digital Identity Reference Architecture, 2019-07-04
- SSC - ICAS 2Key Implementation, 2020-02-11
- TC/TBS – e-Signature Service Standing Offer Procurement, 2021-01-28
- Digital Credential and Access Management, 2019-09-19
- Enabling Secure Access to Protected B Cloud Services, 2019-09-19
- Sign IN Canada Way Forward, 2019-05-02
- Verified.Me POC, 2019-05-02
- MyAlberta Digital Identity, MADI-2019-05-02
- Update of the GC Digital Identity Strategy, 2019-01-10
- ICAM
Policy/Standard/Framework/Strategies/Tools:
Archived Enterprise Solutions material[edit | edit source]
List of Enterprise Solutions from 2017[edit | edit source]
PSPC
- GCdocs
- Shared Case Management
- BuyandSell.ca
- Termium
- eProcurement Solution
- National Service Call Centre
- WebEx
- Shared Travel Services
- Phoenix
- myGCHR
- Compensation Web Apps
CSPS
- Integrated Learning Management System / Gccampus
TBS
- GC EARB presentation, 2019-01-19
- GC BCM 2.0 Model
- GC BCM 2.0 Definition Document
- Government of Canada Business Capability Model 2.0, 2019-05-02
- Financial management transformation
- GCTools
- Project & portfolio management (IT Plan, APM, IT expenditures, Project Oversight, Business Services)
- Callipers
- Executive Talent Management System
- Public Service Performance Management
- TBS Application Portal
- GC Interoperability Platform
- Enterprise Grants & Contributions System
- Wellness Productivity System
- Identity Credential and Access Management System
- Credential Broker Services
- Internal Credential Management
- Open Government Portal
- Access to Information Portal
- Talent Cloud
PSC
- Jobs.gc.ca
ESDC
SSC
- GCSRA
- GCSI
- GEDS
- GCKey