586
edits
Changes
Jump to navigation
Jump to search
Line 42:
Line 42: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
GC Enterprise Architecture/Enterprise Solutions (view source)
Revision as of 14:11, 26 August 2020
, 14:11, 26 August 2020→Enterprise Solutions/Shared Services Guiding principles
* reduce the total cost of ownership to provide external and internal services
* reduce the total cost of ownership to provide external and internal services
* enhance integration and collaboration, create transferable skill sets, and leverage innovative work across the GC and the private sector.
* enhance integration and collaboration, create transferable skill sets, and leverage innovative work across the GC and the private sector.
== Decision Making Framework for Enterprise Solutions[edit | edit source] ==
Presented at GC EARB on June 4th, 2020
Under the Policy on Service and Digital, departmental CIO’s are responsible for “submitting to GC EARB, proposals concerned with the design, development, installation and implementation of digital initiatives”. They are also responsible for “adopting, as applicable, '''enterprise solutions within their respective department'''.”[[File:Decision Making Framework.png|alt=Decision Making Framework|thumb|Decision Making Framework]]Decision Making Framework
Increasingly, a number of departmental digital initiatives propose solutions that address matters with common business capabilities, resulting in a diverse range of applications in operations across the GC IT landscape. TBS has recognized a need to provide assistance to departmental CIO’s to inform decision-making with respect to the '''adoption of enterprise solutions'''.
The following presentation is the first iteration of a working draft of a decision making framework that will be used as a guide for the adoption of enterprise solutions. The framework will be added to the revised GC EARB presenter template. Please send us your feedback on the decision making framework for enterprise solutions to the [[Mailto:EA.AE@tbs-sct.gc.ca|TBS Enterprise Architecture team]]
== DRAFT: Framework for Enterprise Solutions Options ==
'''JOHN to update!'''
Enterprise Solutions may be governed using three general models that provide relative advantages in terms of addressing technical debt, minimizing total cost of ownership, maximizing use of talent, maximizing consistency of technology and business processes, and optimizing infrastructure.
{| class="wikitable"
|+
!Model
!Illustration
|-
|'''Enterprise Service Provider Model.''' This model provides all services to the entire Enterprise in a consolidated manner, governed by a centralized authority, and is fully integrated across all instances. 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.
'''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.
|[[File:Centralized.png|alt=Centralized Model Icon|thumb|100x100px|Centralized Model Icon]]
|-
|'''Product Owner''' '''Model.''' This model uses departmental clusters or business owners to govern distributed instances of enterprise solutions. This model leverages enterprise standards, product owners, departmental clusters, governance and oversight. This model may also leverage distributed technical infrastructure to support solution clusters.
'''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.
|[[File:Decentralized Model Icon.png|alt=Decentralized Model Icon|thumb|100x100px|Decentralized Model Icon]]
|-
|'''Federated Model.''' This stand alone, or decentralized model allows departments to implement their own stack components, influenced by standards, using APIs via interoperability standards. Governance manages exemptions from the Standard; however, a decentralized enterprise with multiple service delivery methods and business units may be successful in finding justifications for significant deviations for standards.
'''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.
|[[File:Federated Model Icon.png|alt=Federated Model Icon|thumb|100x100px|Federated Model Icon]]
|}
== Enterprise Solutions/Shared Services Guiding principles ==
== Enterprise Solutions/Shared Services Guiding principles ==
