Case Study: Creating an Enterprise Architecture to Enable Business Agility
To Enable Business Agility, Logimethods is actively engaged with a large financial institution in defining an effective Enterprise Architecture function. Canadian Finance (CF) is a pseudonym for a full service financial institution with 40,000 employees. The creation of an enterprise architecture group described in this case study was for their Insurance division.
Business Goals: Enterprise Architecture Roadmap
CF had acquired other institutions which previously operated independently, with CF acting more as a holding company.
CF decided to merge the information systems of these acquisitions in order to gain consistent visibility across the institutions and engaged with Logimethods to create an Enterprise Architecture plan.
The ultimate goal of this engagement is to provide CF with an Enterprise Architecture Roadmap that will support currents needs and be flexible enough to accommodate future business requirements.
Solution - Enterprise Architecture to Enable Business Agility
Logimethods is actively engaged with CF in defining an effective Enterprise Architecture (EA) function. Utilizing the template provided in Logimethod’s fast track ITAAS Enterprise Architecture Framework, Logimethods expert consultants created an EA Framework within 3 months. The consultant reported that the Framework can be customized in even shorter time periods, but CF required extra time to confirm decisions across disparate stakeholders. Creating a robust EA framework can be accomplished within a relatively short amount of time. The CF EA framework includes the following:
- CF’s EA strategy (mission, vision, principles and strategy)
- A definition of CF’s EA services
- An assessment of CF’s EA maturity, and a project plan to improve it
- Implementation of an improved EA repository that includes mechanisms to support version and roadmaps on existing Casewise infrastructure
- Robust EA governance including:
- Definition of EA processes
- Definition of EA Key Performance Indicators (KPI’s)
- Definition of EA roles and responsibilities, establishment of EA and IT committees and an Architecture Review Board.
In addition, Logimethods participated in aligning various centers of excellence, such as but not limited to: BPM/BPMS, SOA, ECM, in the new EA organization.
Business Results: Architecture Principles to Ensure Business Results
The initial engagement created the customized EA Framework.
The EA principles and the resulting EA strategy clearly articulate that all efforts of the extended EA group must be tied with business requirements.
While CF has not yet executed the plan, the following goals have been established to guide the implementation of the architecture:
- Reduce TCO. This principle will be implemented through rationalizing IT assets, especially sun-setting applications that don’t scale, are expensive, redundant, and not adaptable to changing business requirements. This requires an evaluation of existing applications.
- Improve Business Support. This principle will be implemented by ensuring the current applications meet business needs, and ensuring there are applications for all business capabilities. This goal will be met by defining the core business capabilities and mapping applications to each capability. Redundant applications that support the same business capability, as well as business capabilities not currently supported will be identified.
- Increase of IT agility. This principle will be implemented through implementing SOA solutions, business process management, canonical information models, and implementing good data architecture.
- Reduce risk. This principle will be implemented through creating a resilient technical architecture with disaster recovery, operating redundancy, and comprehensive security.
- Ensure Compliance with Regulations. Regulatory requirements will be identified, and systems created to ensure compliance, including business process monitoring and management.