586
edits
Changes
Jump to navigation
Jump to search
Line 46:
Line 46: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Archived Enterprise Solutions material (view source)
Revision as of 09:09, 11 January 2021
, 09:09, 11 January 2021no edit summary
Enterprise or shared IT solutions, assets, and services.
Enterprise or shared IT solutions, assets, and services.
== Value proposition ==
* '''For''' Government of Canada employees,
* '''Who''' are involved in modernizing their departmental programs and services.
* '''Enterprise solutions re-usability framework''' is a classification framework and registry of GC reusable assets based on common business capabilities and user journeys,
* '''That''' enables employees to provision reusable assets when modernizing their departmental programs and services and to contribute reusable assets for others to reuse.
* '''Unlike today''' where there is limited guidance for reusability resulting in GC departments implementing duplicated assets.
* '''The Enterprise solutions re-usability framework''' establishes an operational framework to increase reusability across GC departments that will result in the following benefits:
== Reusability Classification Framework ==
{| class="wikitable"
|+
!Option
!Description
!Illustration
|-
|Centralizated
|These reusable assets are standardized to the entire GC in a consolidated manner, governed by a centralized authority and are provisioned by a single centralized service provider. It maximizes utility of major investments which address common business needs, have Enterprise-wide scope, long durations, and require participation from all departments and agencies.
Example: SSC Secure Cloud Enablement and Defense (SCED), desktop standards, data standards
Pros: Enables cohesive, horizontal integration across Enterprise to enables consistent frictionless utilization by stakeholders and administration. Maximizes consistency of technology.
Cons: Increases risk of vendor lock in. Does not allow for department specific customizations to address non-standardized business processes.
|
|-
|Distributed
|These reusable assets are identified by common departmental needs, governed by those departments and are provisioned through distributions and shared/clustered instances of the assets. This model leverages enterprise standards, product owners, departmental clusters, governance and oversight. This model may also leverage distributed technical infrastructure to support solution clusters.
Examples: FMT accelerators / Product Owner guardrails / Open Source toolkits, distributions, and templates, M365 (MS Teams) – Federated via DCAM tenants.
Pros: Recognizes layered approach of Enterprise Architecture Framework and enables governance of one or many aspects of Business, Information/Data, Application, Technology, Security, and Privacy for reuse by departments with similar business processes or non-functional requirements.
Cons: Although the risk of vendor lock in is mitigated comparted to the Enterprise Service Model, it may be challenging to replace technology components that span multiple departments.
|
|-
|Interoperable
|Reusable assets are developed by departments using standards and published for provisioning by others. This stand alone, or decentralized option allows departments to implement their own unique assets but publish and consume APIs and Open Source software centrally led guidance and standards.
Examples: IBM Curam (BDM – Public Cloud-hosted Containterized microservices exposed as APIs)
Pros: Enables reactive solutions to address business processes not shared across departments. Limited risk of vendor lock in.
Cons: Limits reuse across departments. Talent supporting technology components in the federated model have fewer opportunities to build skill sets useful across the Enterprise.
|
|-
|Departmental
|Reusable assets are developed for provisioning within a department or are not reusable at all as there is are no common business capabilities and user journeys.
This option allows departments to implement one-off, niche services, with reuse within their department or none at all.
Examples: Agriculture Canada SeqDB – Botany, Mycology, and Entomology Collection Management
Pros: Enables maximum flexibility for departments
Cons: Does not easily allow for reuse. Encourages niche skills not portable across the GC
|
|}
== Registry of GC reusable assets ==
{| class="wikitable"
|+Proposed model for registry
!Classification
!
!Business capabilities addressed
!User Journeys addressed
!Source of assett
|-
|Centralizated
|
|
|
|
|-
|
|asset name
|
|
|
|-
|
|asset name
|
|
|
|-
|Distributed
|
|
|
|
|-
|
|asset name
|
|
|
|-
|
|asset name
|
|
|
|-
|Interoperable
|
|
|
|
|-
|
|asset name
|
|
|
|-
|
|asset name
|
|
|
|-
|Departmental
|
|
|
|
|-
|
|asset name
|
|
|
|-
|
|asset name
|
|
|
|}
== Detailed Enterprise Solution Fact Sheet ==
Any truly enterprise solution should be able to easily describe itself and it's qualities & properties. Use the following fact sheet to hold and maintain the quick reference information for any solution that has merit for the enterprise. The values can then be used by anyone either looking to compare potential alternatives or looking to improve / extend the existing enterprise solution. The information in this chart also provides an indirect guideline for those involved with the enterprise solution to highlight gaps and develop a roadmap towards a more well rounded solution.
{| class="wikitable"
|+
! colspan="4" |General
|-
|Name:
| colspan="3" |
|-
|Major Business Capability:
|
|Business Owner:
|
|-
|Minor Business Capability:
|
|Service Owner:
|
|-
|Specific Business Capability:
|
|
|
|-
|Nuanced Business Capability:
|
|
|
|-
|Date endorsed by GC EARB:
|
|
|
|-
|Website:
|
|
|
|-
|How many departments use it?
|
|How many users?
|
|-
! colspan="4" |Operational Costs
|-
|Last Year CAP EX ($k)
|
|Last Year OP EX ($k)
|
|-
|This Year CAP EX ($k)
|
|This Year OP EX ($k)
|
|-
|Next Year CAP EX($k)
|
|Next Year OP EX ($k)
|
|-
|# of people to operate:
|
|
|
|-
|Last Year:
|
|
|
|-
|This Year:
|
|
|
|-
|Next Year:
|
|
|
|-
! colspan="4" |Information
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|}
== DRAFT: Framework for Enterprise Solutions Options ==
== DRAFT: Framework for Enterprise Solutions Options ==
'''JOHN to update!'''
'''JOHN to update!'''
