This document provides contact information for various Booz & Company consultants located around the world who specialize in enterprise architecture. It then discusses the key findings of a Booz & Company study on how enterprise architecture maturity impacts business value. The study found that organizations with higher EA maturity captured more business value in terms of reduced costs, complexity, risk and increased agility. It also found that the relationship between maturity and value is linked, with more mature organizations capturing value across more areas. The document provides examples of how specific organizations captured various types of value from their EA programs.
TechBlue / Dux Diligens webinar - Business Value Analysis - Enterprise Archit...Claye Greene
This document provides an overview of enterprise architecture and business value analysis. It introduces the presenters and defines enterprise architecture as a practice that can optimize business and IT alignment, transform the enterprise, and drive innovation. The document discusses how enterprise architecture can increase business value by improving areas like integration, agility, and collaboration. It also outlines potential benefits, challenges, and provides a case study example of how business value analysis was used to help a customer improve financial transaction processing.
Reference Model for ISEB Certificates in Enterprise and Solution ArchitectureAryashree Pritikrishna
This document is a reference model that defines terms used in ISEB examinations for enterprise and solution architecture. It structures architecture concepts into foundation, intermediate, and practitioner levels. The reference model covers multiple architecture domains including business, data, applications, software, infrastructure, and architecture management. It provides definitions for key architecture terms and concepts to help examiners, examinees, and training providers.
The document provides an overview of enterprise architecture foundations, including stakeholders, views and viewpoints, the enterprise continuum, and architecture repositories. It explains that the enterprise continuum classifies architecture and solution artifacts and consists of the architecture, solution, and enterprise continua. The architecture continuum shows the relationships between foundational, common, industry, and enterprise architectures, aiming to discover commonality and eliminate redundancy. It also establishes an architecture repository structure and tool standardization.
The document discusses the structure and competency areas of the Digital and Business Operations Body of Knowledge (DPBOK). It describes how DPBOK is structured into four contexts representing different stages of organizational evolution: individual/founder, team, team of teams, and enduring enterprise. Each context contains competency areas that decompose the skills needed. Context I focuses on competencies for an individual/founder and includes digital fundamentals, digital infrastructure, and application delivery. Digital fundamentals covers understanding digital value methods, contexts and lifecycles. Digital infrastructure discusses IT components, virtualization, containers, cloud-native architectures and configuration management. Application delivery outlines agile development practices and application architectures like microservices and APIs.
Introducing the World's First Information Architecture ToolDATAVERSITY
David Dichmann explains how modeling your information will improve data quality, reliability, integrity and agility to facilitate your BI initiatives and demonstrate the new PowerDesigner. New Features of PowerDesigner 16 include:
Support for over 80 RDBMSs, more than any other modeling tool in the industry;
Modernized, role-based user interface for customizable usability and management;
Enterprise Glossary to ensure business terms and definitions are consistently managed throughout all models, and getting everyone speaking "the same language";
Improved Link & Sync technology with Impact Analysis ensures users are gathering all the connections throughout the entire enterprise to provide mission-critical decision support;
The Power Designer Portal ensures all users have access to authorized metadata including graphics and full element definitions;
Sybase IQ Reference Architecture Advisor allows users to understand the scope and size of their specific requirements.
The new release PowerDesigner 16 will help you:
Fix data quality issues caused by poor adherence to business processes or lack of standardization across systems;
Provide business decision makers access to real-time analytics to understand if business strategies are on track;
Respond to business changes quickly by adding additional reports or analytics or by changing hardware or software.
IntelliSense EA Practice - EA Framework ComparisonCarl Barnes
This document compares and summarizes four major enterprise architecture methodologies: the Zachman Framework, TOGAF, FEA, and Gartner. It uses a case study of a fictional drug store chain, MedAMore, to illustrate how each methodology would approach challenges the company is facing with increasingly complex and costly IT systems that are hindering its ability to adapt to market changes. The document provides background on the history and development of enterprise architecture as a field over the past 20 years. It defines key terms and then analyzes each methodology in more detail to compare their approaches before proposing a blended methodology approach.
Value proposition of architecture driven business solutionsDoug Walters
This document discusses the importance of enterprise architecture and planning for business solutions. It argues that failing to plan is like planning to fail, and provides examples of how individual systems developed without an overall plan can result in issues like those seen in the Winchester Mystery House. The document recommends defining a conceptual architecture with principles, policies, standards and taxonomy to provide a blueprint or high-level plan before embarking on projects. This helps understand current and future costs and capabilities, and provides a roadmap to transform systems in a coordinated way rather than creating duplicative, incompatible or unsustainable solutions.
TechBlue / Dux Diligens webinar - Business Value Analysis - Enterprise Archit...Claye Greene
This document provides an overview of enterprise architecture and business value analysis. It introduces the presenters and defines enterprise architecture as a practice that can optimize business and IT alignment, transform the enterprise, and drive innovation. The document discusses how enterprise architecture can increase business value by improving areas like integration, agility, and collaboration. It also outlines potential benefits, challenges, and provides a case study example of how business value analysis was used to help a customer improve financial transaction processing.
Reference Model for ISEB Certificates in Enterprise and Solution ArchitectureAryashree Pritikrishna
This document is a reference model that defines terms used in ISEB examinations for enterprise and solution architecture. It structures architecture concepts into foundation, intermediate, and practitioner levels. The reference model covers multiple architecture domains including business, data, applications, software, infrastructure, and architecture management. It provides definitions for key architecture terms and concepts to help examiners, examinees, and training providers.
The document provides an overview of enterprise architecture foundations, including stakeholders, views and viewpoints, the enterprise continuum, and architecture repositories. It explains that the enterprise continuum classifies architecture and solution artifacts and consists of the architecture, solution, and enterprise continua. The architecture continuum shows the relationships between foundational, common, industry, and enterprise architectures, aiming to discover commonality and eliminate redundancy. It also establishes an architecture repository structure and tool standardization.
The document discusses the structure and competency areas of the Digital and Business Operations Body of Knowledge (DPBOK). It describes how DPBOK is structured into four contexts representing different stages of organizational evolution: individual/founder, team, team of teams, and enduring enterprise. Each context contains competency areas that decompose the skills needed. Context I focuses on competencies for an individual/founder and includes digital fundamentals, digital infrastructure, and application delivery. Digital fundamentals covers understanding digital value methods, contexts and lifecycles. Digital infrastructure discusses IT components, virtualization, containers, cloud-native architectures and configuration management. Application delivery outlines agile development practices and application architectures like microservices and APIs.
Introducing the World's First Information Architecture ToolDATAVERSITY
David Dichmann explains how modeling your information will improve data quality, reliability, integrity and agility to facilitate your BI initiatives and demonstrate the new PowerDesigner. New Features of PowerDesigner 16 include:
Support for over 80 RDBMSs, more than any other modeling tool in the industry;
Modernized, role-based user interface for customizable usability and management;
Enterprise Glossary to ensure business terms and definitions are consistently managed throughout all models, and getting everyone speaking "the same language";
Improved Link & Sync technology with Impact Analysis ensures users are gathering all the connections throughout the entire enterprise to provide mission-critical decision support;
The Power Designer Portal ensures all users have access to authorized metadata including graphics and full element definitions;
Sybase IQ Reference Architecture Advisor allows users to understand the scope and size of their specific requirements.
The new release PowerDesigner 16 will help you:
Fix data quality issues caused by poor adherence to business processes or lack of standardization across systems;
Provide business decision makers access to real-time analytics to understand if business strategies are on track;
Respond to business changes quickly by adding additional reports or analytics or by changing hardware or software.
IntelliSense EA Practice - EA Framework ComparisonCarl Barnes
This document compares and summarizes four major enterprise architecture methodologies: the Zachman Framework, TOGAF, FEA, and Gartner. It uses a case study of a fictional drug store chain, MedAMore, to illustrate how each methodology would approach challenges the company is facing with increasingly complex and costly IT systems that are hindering its ability to adapt to market changes. The document provides background on the history and development of enterprise architecture as a field over the past 20 years. It defines key terms and then analyzes each methodology in more detail to compare their approaches before proposing a blended methodology approach.
Value proposition of architecture driven business solutionsDoug Walters
This document discusses the importance of enterprise architecture and planning for business solutions. It argues that failing to plan is like planning to fail, and provides examples of how individual systems developed without an overall plan can result in issues like those seen in the Winchester Mystery House. The document recommends defining a conceptual architecture with principles, policies, standards and taxonomy to provide a blueprint or high-level plan before embarking on projects. This helps understand current and future costs and capabilities, and provides a roadmap to transform systems in a coordinated way rather than creating duplicative, incompatible or unsustainable solutions.
Serco is a global company that provides outsourcing services across multiple industries and geographies. It has over 120,000 employees and annual revenue of over £4 billion. The document discusses Serco's approach to mobilizing a global enterprise architecture in a digital world, including establishing an IT operating model, principles, governance, reference architectures, standards and guidance, metrics and measures, and an enterprise architecture portal. It provides tips for implementing an effective enterprise architecture, emphasizing communication, integration with the business, and establishing a collaborative approach.
A method to_define_an_enterprise_architecture_using_the_zachman_frameworkbambangpadhi
This document describes a method for defining an enterprise architecture using the Zachman Framework. The method proposes a set of artifacts to represent the content of each cell in the Zachman Framework. It also defines rules for filling in the cells in a top-down, incremental order based on dependencies between cells. The artifacts and method are intended to provide structure and guidance for applying the Zachman Framework to develop an enterprise architecture.
The document discusses two popular enterprise architecture frameworks - TOGAF and Zachman. It provides an overview of what enterprise architecture is, its key drivers and benefits. It then describes the major components of TOGAF including the Architecture Development Method (ADM) and supporting artifacts. Next, it outlines the Zachman Framework and how it classifies architectures based on perspectives and communication questions. Finally, it summarizes the benefits architectures provide including standardized processes, reduced complexity and improved decision making.
The document discusses two reference models in TOGAF - the Technical Reference Model (TRM) and the Integrated Information Infrastructure Reference Model (III-RM).
The TRM defines a common taxonomy for application platforms and their interfaces. It aims to standardize platforms and enable communication. The III-RM focuses on enabling "boundaryless information flow" by providing common applications like Information Provider Applications, Brokerage Applications, and Information Consumer Applications that can extract, aggregate, and present data across organizational silos.
Both models are intended to provide common frameworks that organizations can extend and adapt to develop their own integrated architectures and enable better access to and sharing of information across departments.
Enterprise Architecture and TOGAF, Quick LookSukru Kocakaya
Enterprise architecture is the process and product of planning, designing and constructing an organization's operations from a business and information technology perspective. It involves analyzing an organization's current state and desired future state across business, information, and technology dimensions. The goals of enterprise architecture include aligning business and IT strategies, increasing business and IT agility, and governing technology decisions. Common frameworks used for enterprise architecture include TOGAF, Zachman, and DODAF.
This document proposes an innovative approach called SIM (Secure Identity Management) that aims to make access management policies closer aligned with business objectives. It does this in two ways:
1) By focusing the policy engineering process on business goals and responsibilities defined in processes, using concepts from the ISO/IEC 15504 standard. This links capabilities and accountabilities to process outcomes and work products.
2) By defining a multi-agent system architecture to automate the deployment of policies across heterogeneous IT components and devices. The agents provide autonomy and ability to adapt rapidly according to context.
The approach was prototyped using open source components and aims to improve how access rights are defined according to business needs and deployed across an organization
ArchiMate is a modeling language that provides concepts and techniques to support enterprise architects. It includes concepts for modeling the business, application, and technology layers of an enterprise. At the business layer, concepts include business actors, roles, processes, objects, and services. The application layer focuses on application components, interfaces, functions, services, and interactions. The technology layer covers infrastructure, hardware, and software. Relationships connect concepts across layers to illustrate dependencies and information flow throughout the enterprise architecture.
This is the deck of a webinar that I presented at the OpenGroup. The focus of this webinar is on the challenge of using these standards in practice to build a strong architecture capability in organizations.
Performance Driven Architecture V2 August 2010dfnewman
This document outlines Booz & Company's performance-driven architecture framework. The framework aims to focus and align an organization's architecture capabilities to create business value. It does this through a strategy-led approach that unlocks and delivers business value across the architecture lifecycle. The framework provides capabilities to integrate architectural efforts across enterprise, domain, and solution levels and manage performance through metrics. Booz & Company recommends a multi-phased approach to implement the framework for an organization.
Optimizing Value to the Enterprise with Integrated Enterprise ArchitectureNathaniel Palmer
The document discusses building and using enterprise architecture to optimize value to an enterprise. It defines enterprise architecture and describes how it can coordinate business, operations, automation and technology aspects of an enterprise. It outlines steps to develop an enterprise architecture, including defining the enterprise scope, strategic direction, current and future architectures, gaps, and strategies to address gaps. Developing enterprise architecture requires organizational commitment and lessons include ensuring executive sponsorship, communication, and identifying metrics to measure impact.
Effectiveness Of Service Oriented Architecture In Enterprise Architecture F...mdfachowdhury
This document provides a comparative analysis of popular enterprise architecture (EA) frameworks and the effectiveness of service-oriented architecture (SOA) implementation in EA. It outlines EA frameworks including TOGAF, DoDAF, FEAF, C4ISR, and Zachman and compares their supported architectures, architecture development methods, artifacts, and deliverables. The document also discusses the benefits and challenges of implementing SOA in EA frameworks.
The world has not really settled on precise definitions of IT architecture or architecture description as these terms relate to the enterprises and its systems or software
Introduction to Enterprise ArchitectureMohammed Omar
what is Enterprise Architecture
Enterprise Architecture Life-cycle
Enterprise Architecture benefits
Enterprise Architecture challenges
EA driven approach for IT strategy
Enterprise Architecture frameworks
Why do we Need Enterprise Architecture
This document outlines principles and patterns for service-oriented architecture (SOA) design. It begins with an introduction and agenda, then covers service fundamentals like loose coupling and statelessness. Major sections discuss service design principles like autonomy and standardized contracts, inventory design patterns like normalization and layers, individual service design patterns like agnostic capabilities and messaging, and composition design patterns like routing and security. The goal is to discover principles for effective service-oriented design and how patterns support those principles.
To be truly effective, organizations have to really understand and embrace the holistic concept of Enterprise Architecture. Focusing solely on the standards aspect greatly limits the benefits that an enterprise can achieve. Enterprise Architecture (EA) is the description and design of a portfolio of processes, applications, information and their supporting technologies that enable business strategy. It addresses the structure of that portfolio over time and its interactions through guidelines including principles, rules, patterns, reference models, standards, initiatives and governance structures and processes to use when building new IT capability.
Enterprise Representation An Analysis Of+Standards Issueslegal2
This document discusses issues related to standardizing enterprise modeling and integration. It addresses:
1) The need for standards to define key components of enterprise models in order to facilitate information sharing and integration between enterprises. However, enterprises also require freedom to define their own processes and products.
2) The characteristics of effective enterprise models, including using consistent views and modeling processes and components in a standardized way to allow for interoperability.
3) The role of an enterprise reference architecture in providing a framework and guidelines for enterprise representation and modeling to achieve integration goals. However, completely standardizing enterprise structures may not be practical or desirable.
Business and Strategic Alignment in EA – Practical Guidelines Based on Indust...IASA
Business and Strategic Alignment in EA – Practical Guidelines Based on Industry Best Practices - Dave Guevara
As IASA members we are constantly reminded that architects are responsible for connecting business to IT. Business alignment is indicated in architecture frameworks like TOGAF or Zachman as an important step. However, the challenge comes in getting this done where EA is not top-down driven, short term deadlines always win over strategic efforts and standards like ITIL, COBIT and BPMN help but don’t really answer how There is a great deal of writing about EA, SOA, their benefits and how they need to be driven by business needs. The architect is still left with diverse guidance that provides little practical help on how exactly to conduct line-of-sight alignment between business strategy and system implementation. In this discussion, we will look at this issue from four perspectives:
1. Practical means of determining business value and impact, then creating alignment to your future state architectures.
2. Top-down view using an EA framework.
3. Bottoms up view in a future state architecture
4. Business functional model related to an application functional model
5. Practical suggestions that work now and can scale over time
Enterprise architecture (EA) is a well-defined practice for conducting enterprise analysis, design, planning, and implementation, using a comprehensive approach at all times, for the successful development and execution of strategy.
Maximising The Value and Benefits of Enterprise ArchitectureAlan McSweeney
This document discusses enterprise architecture (EA), including:
1) The benefits of EA such as aligning IT with business strategy and reducing IT complexity.
2) The key elements of EA including business, data, applications, and technology architectures.
3) How effective EA implementation and management can standardize systems and infrastructure, lower costs, and improve business agility.
Delivering value. Enterprise architecture MUST deliver business value and do it now. Companies understand the need for architecture in general, but what are the specific benefits? Architecture processes are sometimes perceived as slow and bureaucratic. Architects are often insufficiently connected to strategic investment decisions on the one hand, and realization processes on the other. Architects have difficulty expressing their added value..
Serco is a global company that provides outsourcing services across multiple industries and geographies. It has over 120,000 employees and annual revenue of over £4 billion. The document discusses Serco's approach to mobilizing a global enterprise architecture in a digital world, including establishing an IT operating model, principles, governance, reference architectures, standards and guidance, metrics and measures, and an enterprise architecture portal. It provides tips for implementing an effective enterprise architecture, emphasizing communication, integration with the business, and establishing a collaborative approach.
A method to_define_an_enterprise_architecture_using_the_zachman_frameworkbambangpadhi
This document describes a method for defining an enterprise architecture using the Zachman Framework. The method proposes a set of artifacts to represent the content of each cell in the Zachman Framework. It also defines rules for filling in the cells in a top-down, incremental order based on dependencies between cells. The artifacts and method are intended to provide structure and guidance for applying the Zachman Framework to develop an enterprise architecture.
The document discusses two popular enterprise architecture frameworks - TOGAF and Zachman. It provides an overview of what enterprise architecture is, its key drivers and benefits. It then describes the major components of TOGAF including the Architecture Development Method (ADM) and supporting artifacts. Next, it outlines the Zachman Framework and how it classifies architectures based on perspectives and communication questions. Finally, it summarizes the benefits architectures provide including standardized processes, reduced complexity and improved decision making.
The document discusses two reference models in TOGAF - the Technical Reference Model (TRM) and the Integrated Information Infrastructure Reference Model (III-RM).
The TRM defines a common taxonomy for application platforms and their interfaces. It aims to standardize platforms and enable communication. The III-RM focuses on enabling "boundaryless information flow" by providing common applications like Information Provider Applications, Brokerage Applications, and Information Consumer Applications that can extract, aggregate, and present data across organizational silos.
Both models are intended to provide common frameworks that organizations can extend and adapt to develop their own integrated architectures and enable better access to and sharing of information across departments.
Enterprise Architecture and TOGAF, Quick LookSukru Kocakaya
Enterprise architecture is the process and product of planning, designing and constructing an organization's operations from a business and information technology perspective. It involves analyzing an organization's current state and desired future state across business, information, and technology dimensions. The goals of enterprise architecture include aligning business and IT strategies, increasing business and IT agility, and governing technology decisions. Common frameworks used for enterprise architecture include TOGAF, Zachman, and DODAF.
This document proposes an innovative approach called SIM (Secure Identity Management) that aims to make access management policies closer aligned with business objectives. It does this in two ways:
1) By focusing the policy engineering process on business goals and responsibilities defined in processes, using concepts from the ISO/IEC 15504 standard. This links capabilities and accountabilities to process outcomes and work products.
2) By defining a multi-agent system architecture to automate the deployment of policies across heterogeneous IT components and devices. The agents provide autonomy and ability to adapt rapidly according to context.
The approach was prototyped using open source components and aims to improve how access rights are defined according to business needs and deployed across an organization
ArchiMate is a modeling language that provides concepts and techniques to support enterprise architects. It includes concepts for modeling the business, application, and technology layers of an enterprise. At the business layer, concepts include business actors, roles, processes, objects, and services. The application layer focuses on application components, interfaces, functions, services, and interactions. The technology layer covers infrastructure, hardware, and software. Relationships connect concepts across layers to illustrate dependencies and information flow throughout the enterprise architecture.
This is the deck of a webinar that I presented at the OpenGroup. The focus of this webinar is on the challenge of using these standards in practice to build a strong architecture capability in organizations.
Performance Driven Architecture V2 August 2010dfnewman
This document outlines Booz & Company's performance-driven architecture framework. The framework aims to focus and align an organization's architecture capabilities to create business value. It does this through a strategy-led approach that unlocks and delivers business value across the architecture lifecycle. The framework provides capabilities to integrate architectural efforts across enterprise, domain, and solution levels and manage performance through metrics. Booz & Company recommends a multi-phased approach to implement the framework for an organization.
Optimizing Value to the Enterprise with Integrated Enterprise ArchitectureNathaniel Palmer
The document discusses building and using enterprise architecture to optimize value to an enterprise. It defines enterprise architecture and describes how it can coordinate business, operations, automation and technology aspects of an enterprise. It outlines steps to develop an enterprise architecture, including defining the enterprise scope, strategic direction, current and future architectures, gaps, and strategies to address gaps. Developing enterprise architecture requires organizational commitment and lessons include ensuring executive sponsorship, communication, and identifying metrics to measure impact.
Effectiveness Of Service Oriented Architecture In Enterprise Architecture F...mdfachowdhury
This document provides a comparative analysis of popular enterprise architecture (EA) frameworks and the effectiveness of service-oriented architecture (SOA) implementation in EA. It outlines EA frameworks including TOGAF, DoDAF, FEAF, C4ISR, and Zachman and compares their supported architectures, architecture development methods, artifacts, and deliverables. The document also discusses the benefits and challenges of implementing SOA in EA frameworks.
The world has not really settled on precise definitions of IT architecture or architecture description as these terms relate to the enterprises and its systems or software
Introduction to Enterprise ArchitectureMohammed Omar
what is Enterprise Architecture
Enterprise Architecture Life-cycle
Enterprise Architecture benefits
Enterprise Architecture challenges
EA driven approach for IT strategy
Enterprise Architecture frameworks
Why do we Need Enterprise Architecture
This document outlines principles and patterns for service-oriented architecture (SOA) design. It begins with an introduction and agenda, then covers service fundamentals like loose coupling and statelessness. Major sections discuss service design principles like autonomy and standardized contracts, inventory design patterns like normalization and layers, individual service design patterns like agnostic capabilities and messaging, and composition design patterns like routing and security. The goal is to discover principles for effective service-oriented design and how patterns support those principles.
To be truly effective, organizations have to really understand and embrace the holistic concept of Enterprise Architecture. Focusing solely on the standards aspect greatly limits the benefits that an enterprise can achieve. Enterprise Architecture (EA) is the description and design of a portfolio of processes, applications, information and their supporting technologies that enable business strategy. It addresses the structure of that portfolio over time and its interactions through guidelines including principles, rules, patterns, reference models, standards, initiatives and governance structures and processes to use when building new IT capability.
Enterprise Representation An Analysis Of+Standards Issueslegal2
This document discusses issues related to standardizing enterprise modeling and integration. It addresses:
1) The need for standards to define key components of enterprise models in order to facilitate information sharing and integration between enterprises. However, enterprises also require freedom to define their own processes and products.
2) The characteristics of effective enterprise models, including using consistent views and modeling processes and components in a standardized way to allow for interoperability.
3) The role of an enterprise reference architecture in providing a framework and guidelines for enterprise representation and modeling to achieve integration goals. However, completely standardizing enterprise structures may not be practical or desirable.
Business and Strategic Alignment in EA – Practical Guidelines Based on Indust...IASA
Business and Strategic Alignment in EA – Practical Guidelines Based on Industry Best Practices - Dave Guevara
As IASA members we are constantly reminded that architects are responsible for connecting business to IT. Business alignment is indicated in architecture frameworks like TOGAF or Zachman as an important step. However, the challenge comes in getting this done where EA is not top-down driven, short term deadlines always win over strategic efforts and standards like ITIL, COBIT and BPMN help but don’t really answer how There is a great deal of writing about EA, SOA, their benefits and how they need to be driven by business needs. The architect is still left with diverse guidance that provides little practical help on how exactly to conduct line-of-sight alignment between business strategy and system implementation. In this discussion, we will look at this issue from four perspectives:
1. Practical means of determining business value and impact, then creating alignment to your future state architectures.
2. Top-down view using an EA framework.
3. Bottoms up view in a future state architecture
4. Business functional model related to an application functional model
5. Practical suggestions that work now and can scale over time
Enterprise architecture (EA) is a well-defined practice for conducting enterprise analysis, design, planning, and implementation, using a comprehensive approach at all times, for the successful development and execution of strategy.
Maximising The Value and Benefits of Enterprise ArchitectureAlan McSweeney
This document discusses enterprise architecture (EA), including:
1) The benefits of EA such as aligning IT with business strategy and reducing IT complexity.
2) The key elements of EA including business, data, applications, and technology architectures.
3) How effective EA implementation and management can standardize systems and infrastructure, lower costs, and improve business agility.
Delivering value. Enterprise architecture MUST deliver business value and do it now. Companies understand the need for architecture in general, but what are the specific benefits? Architecture processes are sometimes perceived as slow and bureaucratic. Architects are often insufficiently connected to strategic investment decisions on the one hand, and realization processes on the other. Architects have difficulty expressing their added value..
The document discusses how the old rules of enterprise architecture are becoming irrelevant and new rules are needed. It argues that the rise of unbusiness has challenged traditional IT cycles and strategies. The new rules that should be followed are to focus on what really matters, externalize non-core functions, and reduce the cost of planning.
Estudio 27 is a translation and interpretation company based in Mexico that provides linguistic services for corporate, financial, and business clients. They have over 5 million words translated and 2,000 hours of interpretation experience. They offer translations, interpretations, and complementary services in over 35 languages, and have a portfolio of clients in various industries. Their vertically integrated services handle all global communication needs such as translations, interpretations, transcription, and localization.
The document discusses the value of enterprise architecture and how it can help align business and IT strategies. It argues that a more organic, pragmatic approach is needed to plan IT strategies that can flexibly support changing business needs over time. Such an approach involves understanding the current landscape, considering different paths forward, selecting an initial path, then continually reviewing and adjusting the strategy based on outcomes.
The document provides an overview of getting started with digitization for an organization. It discusses organizing a digitization project, including prioritizing projects and creating a team. It also covers choosing equipment like hardware and software, setting up a scanning station, and scanning processes. Finally, it discusses options for publishing and storing digital files, including free services like Flickr and preserving content through the North Carolina Digital Heritage Center.
What is the Value of Architecture. Andrew L Macaulay. Global Head of Architects Community. March 2006. In collaboration with. Microsoft Architect Insight ...
Millennium Business Group (MBG) is a business consulting firm that focuses on accelerating revenue growth for its clients. It provides business development services such as developing marketing strategies, opening new markets and customers, sales expertise, and uncovering new opportunities. MBG tailors its approach for each client, understanding their business and leveraging MBG's industry network and experience to innovate the client's market strategy and execution.
Sysphera is a Latin American software company specializing in financial planning and control solutions. Headquartered in Brazil, Sysphera aims to be recognized as a high-quality supplier and outperform similar solutions in cost and benefit. The company's products help users increase productivity and access the right information for decision making. Sysphera delivers its products through partners in Brazil, Argentina, Chile, Mexico and Portugal to support customers through all stages of budgeting from initial setup to monitoring and scenario planning.
The New Role of the architect - central to growing your business in todays di...Gunnar Menzel
In the digital era, the role of the architect is becoming less technical, and is more closely getting aligned to business strategy. Architects are able to help the business envision its future and integrate IT into the business, providing better value for money, faster benefit realization and improved market competitiveness.
I apologize, upon reviewing the document I do not feel comfortable generating a summary without the full context and intended purpose of the original work. Direct quotes or significant paraphrasing from copyrighted content would not be appropriate without permission.
The document discusses Lenovo's use of crowdsourcing and engagement marketing strategies. It describes a crowdsourcing platform pilot called Lenovo Exchange that generated user-generated content. It also discusses lessons learned, including starting simply, owning intellectual property, leveraging industry expertise, and being prepared to fail and try again. The goal is to better engage the "Net Generation" by sparking participation, generating content, and listening to customer insights.
Value Chain Canvas Model an Enterprise Architecture FrameworkRené MANDEL
This document introduces the Value Chain Canvas Model (VCCM), a top-down approach created by René Mandel to visualize an enterprise's value chains and transformations. The VCCM represents an enterprise's ecosystem through "universes" bounded by events. Within each universe, value chains comprise three levels - proximity, integration, and resources - connected by operators. The document provides examples of applying the VCCM to an airport, retail offering creation, IT service support, and a call for proposals. It describes how the flexible multi-dimensional model can be adapted to changing enterprise boundaries and transformations.
The document provides tips for designing effective PowerPoint presentations. It recommends making slides big, simple, clear, progressive and consistent. Specifically, it suggests using large font sizes, simple language and visuals, high color contrast, focal points to guide attention, and consistency in design elements. The presentation should be built in a step-by-step manner and focus on the key ideas being conveyed at each point. Speakers are advised to practice their delivery and engage the audience during the presentation.
Enterprise Architecture Framework: Chase Global BankHampus Ahlqvist
The document summarizes a service-centric enterprise architecture developed for Chase Global Bank. It includes an abstract, development cycle outline, drivers for the architecture, a strategic alignment model, associated risks and opportunities, internal/external analyses, a top-level organizational chart, and conceptual IT/business services map. The architecture aims to align business and IT strategies through common services and views to create customer value.
Executives are the Simon Cowell of the business world: impatient, critical, often caustic. But they're also desperately searching for talent. How do you make the right impression? These 5 tips will get you started
5 timeless color themes for presentationsPresentitude
Color preferences changes over time. Each decade collects its own set of colors to express emotions and attitudes. Inspired by the Pantone list "50 years of colors" we have made five, timeless, historical color themes for presentations. How about a psychedelic 1960s, earthy 1970s feel or a vibrant 1980s feel?
Profitiviti Business Operations Intelligence ArticleSteve Raack
The document discusses a methodology called Business Operations Intelligence that helps companies gain insights into their business operations through data analysis. It involves defining all business processes, including both departmental and enterprise-wide processes. The methodology then ranks processes based on their impact and efficiency to identify opportunities for improvement. Implementing this methodology provides executives with information to make more informed decisions and pursue initiatives that can significantly improve profitability.
The specialist leaders of HR, IT, finance, and other functions have had their time, attention, and (in some cases) money freed up by more efficient practices. They now have the ability--and the mandate--to play a more influential role, especially when building capabilities. Instead of balancing services among all business units equally, or striving to be best in class in everything, they can become increasingly "fit for purpose," thinking and acting in line with the enterprise strategy.
The document discusses the role of human resources in mergers and acquisitions. It begins by defining mergers and acquisitions as representing ultimate change for businesses that can be difficult and chaotic. It then provides statistics on M&A activity and discusses why understanding the process is important. The rest of the document outlines the M&A process and key roles for HR, including assessing cultural alignment, developing integration plans, managing communications, and ensuring retention of key employees.
Accelerate Value Creation: The Virtuous Cycle of Using Technology to Maximize...FindWhitePapers
Explore the relationship between IT investment and performance and productivity gains. This paper describes how companies can best maximize value from their IT investments and can take part in the virtuous cycle of IT.
Creating a Lean Business System white paperPeterHines
The document provides an overview of the Lean Business Model created by Professor Peter Hines. The model was developed based on research of Toyota's operations and supply chain management. It consists of five elements: strategy deployment, value stream management, tools and techniques, people enabled processes, and extended enterprise. The Lean Business Model can be used to assess an organization's lean maturity and develop a roadmap to create a lean business system.
If you are a senior IT leader, you need to make the same kinds of disciplined choices for your department that the CEO and top leadership team are making about the strategic direction of the enterprise. Here's how to develop a sophisticated, more strategically oriented information technology approach--based on six ways to create value for the enterprise, and five archetypes that resolve the tension among those six value drivers.
The Path To Operational Excellence 5 Components Of SuccessNat Evans
The document discusses operational excellence and provides a definition and framework. It argues that operational excellence must be strategically focused on areas where an organization can outperform competitors to provide competitive advantage. It emphasizes that leadership must select a tight focus area and guide implementation, and that operational excellence initiatives should align with strategic goals to ensure support and sustainability. The framework identifies five drivers of operational competitive advantage: safety, asset productivity, human capabilities, process excellence, and supply chain management.
This document provides an overview and agenda for a presentation on successful IT business integration. Some key points:
1. It discusses the challenges facing IT and business executives in a difficult economic environment with flat IT budgets and increased pressure to demonstrate value.
2. Statistics are presented on top business and technology priorities from a Gartner survey, showing business process improvement and business intelligence as the top priorities.
3. An approach is outlined to transform organizations through self-assessment, defining strategic outcomes, and using balanced scorecards to drive change and close competency gaps.
4. The importance of IT business alignment, governance, and moving from an operational to strategic focus is emphasized to support business goals.
Planning and Budgeting in Vietnam: Top challenges and solutionsTrang Nguyen
This presentation slide is used for the "Planning and Budgeting in Vietnam: Top challenges and solutions" seminar on August 9, 2012.
This seminar is organized by TRG International and PwC Vietnam.
The slide is shared through TRG International Blog. If you are really interested in this topic, I recommend you download the full slide at http://blog.trginternational.com/seminar-slides-download-planning-budgeting-in-vietnam/.
As a c-suite executive in an organization and industry, it is almost imperative that the job demanded to create value for driving the profitability, growth and the ‘sustenance’ of the demanded growth. The intent is the navigating, exploring and detecting the right direction along with your chosen team to avoid disruptions and change facing the industry.
In the prevalent times the corporate executives faces ever growing challenges in shape of financial, political, demographics, economic and above all the ‘technology’, altering the shape and intensity of competition.
This document is a project report submitted by Poonam Yadav to their university on working capital management at Code Platter Softwares Ltd. It provides an introduction to the company, which was founded in 2001 and provides IT services and solutions. It also includes an executive summary on the CEO, Arihant Jain, and his vision for making Code Platter a global company. The report appears to analyze working capital management practices at Code Platter and make recommendations.
Business Transformation Outsourcing (BTO) is an extension of BPO, a strategic partnership between the customer and the outsourcer with the advantage of sophisticated financing mechanisms. BTO involves sharing risks and gains with an outsource business partner. It is all about governing the priorities, people and processes of organizations. It merges IT and business strategy of a company while optimizing quality, performance and business availability.
The document discusses Prime Value Chain Analysis (PVC), a technique used to analyze an organization's critical activities that deliver value to customers. PVC helps organizations realign around key priorities by breaking down silos and prioritizing improvement efforts. It creates a dynamic view of major value-creating activities across the organization, regardless of functional boundaries. This helps organizations understand how different parts of the business support strategic goals and identify opportunities to improve performance through better alignment, structure, and execution. The document provides an example of a company that used PVC analysis to improve product development efficiency and effectiveness across silos.
Project management offices (PMOs) evolve through the project, program and portfolio management stages as they mature to meet ever-increasing business needs. A project management office can reduce the risk of project schedule slippage, cost overruns and scope creep by focusing on a standard project management process, basic tools and project manager development. A program management office can improve resource management across business and IT projects and programs by combining related business and IS projects into programs, as well as by implementing governance, communications programs and collaboration tools. A portfolio management office can contribute to business growth by optimizing the mix of project and program investments and focusing on benefits realization and knowledge management. CIOs must ensure that their PMOs master the basics of their current stage before they evolve them to the next stage
Discute as facilidades que uma ferramenta como portal corporativo pode oferecer a uma organização, apresenta os critérios de avaliação, infra-estrutura de tecnologia de informação, e o posicionamento, visão e impacto do portal na corporação.
www.terraforum.com.br
Why strategic alignment of business actions is important for sustainability a...Tshidiso Moetapele
The document discusses the importance of strategically aligning business actions with organizational goals of sustainability and profitability. It defines strategic alignment and notes that it requires aligning practices with broad goals and objectives. The CEO and executive team must ensure alignment is prioritized and driven from the top down. Strategic alignment is especially important during strategy development processes, when goals are identified and planned for, and when implementing strategic initiatives, to increase the chances of successful execution and reduce risks. Properly aligning business actions can streamline processes, leverage organizational assets effectively, and allow an organization to assess its ability to achieve its goals and longevity.
Creating the Performance Driven Organisation - Paul LimPaul Lim
The document discusses the importance of performance management for organizations. It outlines a methodology called VisionBridge for developing performance management programs. The methodology has three phases - identify, design, and execute. The identify phase uncovers business assumptions and maps operations. The design phase identifies key performance drivers, objectives, and indicators. The execute phase implements the performance system. The document argues that properly identifying and prioritizing the right performance metrics is critical for success. VisionBridge uses a technology architecture to integrate performance data across systems and support decision making.
The document outlines 10 critical success factors for successful project portfolio management: 1) Senior management commitment and consensus, 2) Communication of strategic objectives, 3) Strategically aligned investment selection, 4) Institutionalized investment management process, 5) Governance framework aligned with enterprise decision making, 6) Integrated program/project management discipline, 7) Consistent risk and performance measurement, 8) Portfolio reviews to support investment priority realignment, 9) Effective balance of investments, and 10) Strategic focus transforming strategy into operational excellence. Adopting more of these factors provides more value, but success is still possible if senior management commits to the process. Project portfolio management infuses strategy into investment decisions.
De afgelopen maanden heb ik met veel CFO´s gesproken over de transformaties die hun Finance Organisatie moet doormaken om aan de veranderende eisen en wensen van Executives, managers en stakeholders te voldoen. Ligt hun focus momenteel nog op transactionele core finance activiteiten, voor de nabije toekomst is het hun ambitie om bedrijfsbreed veel meer waarde te leveren op het gebied van analyse en beslissingssupport.
Bedrijven die goed scoren op Finance Efficiëncy alsmede in staat zijn om betrouwbare Business Insight te leveren aan de diverse business units, zijn volgens de IBM Global CFO Survey 2010 aantoonbaar succesvoller op het gebied van omzetgroei, EBITDA en Retun of Invested Capital.
Ik wil graag de uitkomsten van 1500 face-to-face interviews met CFO´s met jullie delen, daarom ´share´ ik het rapport ´The New Value Integrator – Insights from the CFO Survey´.
Who is increasingly instrumental in helping CEOs and Boards make high-impact decisions – the choices and trade-offs that build or destroy enterprise value? CFOs.
Based on input from more than 1,900 CFOs and senior Finance leaders worldwide, the IBM Global CFO Study indicates that the demands on CFOs are rising and extend well beyond traditional financial control and supervision.
But in a constantly changing environment, how can CFOs provide their enterprises with a competitive edge? How can they help the business make not just faster but smarter decisions?
In the 2010 study, one group of Finance organizations – called Value Integrators – consistently outperforms their peers. They are not only more effective, but their enterprises also perform better financially.
Their secret? Driving a combination of two key capabilities – Finance efficiency and business insight – across their organizations. Although study results show that each capability provides important benefits, the highest performers excel at both.
Read the study to learn more about this multiplier effect and how to create it within your own organization.
Similar to Building Value Through Enterprise Architecture (20)
Reimagining Your Library Space: How to Increase the Vibes in Your Library No ...Diana Rendina
Librarians are leading the way in creating future-ready citizens – now we need to update our spaces to match. In this session, attendees will get inspiration for transforming their library spaces. You’ll learn how to survey students and patrons, create a focus group, and use design thinking to brainstorm ideas for your space. We’ll discuss budget friendly ways to change your space as well as how to find funding. No matter where you’re at, you’ll find ideas for reimagining your space in this session.
A review of the growth of the Israel Genealogy Research Association Database Collection for the last 12 months. Our collection is now passed the 3 million mark and still growing. See which archives have contributed the most. See the different types of records we have, and which years have had records added. You can also see what we have for the future.
How to Setup Warehouse & Location in Odoo 17 InventoryCeline George
In this slide, we'll explore how to set up warehouses and locations in Odoo 17 Inventory. This will help us manage our stock effectively, track inventory levels, and streamline warehouse operations.
How to Add Chatter in the odoo 17 ERP ModuleCeline George
In Odoo, the chatter is like a chat tool that helps you work together on records. You can leave notes and track things, making it easier to talk with your team and partners. Inside chatter, all communication history, activity, and changes will be displayed.
How to Fix the Import Error in the Odoo 17Celine George
An import error occurs when a program fails to import a module or library, disrupting its execution. In languages like Python, this issue arises when the specified module cannot be found or accessed, hindering the program's functionality. Resolving import errors is crucial for maintaining smooth software operation and uninterrupted development processes.
This presentation includes basic of PCOS their pathology and treatment and also Ayurveda correlation of PCOS and Ayurvedic line of treatment mentioned in classics.
ISO/IEC 27001, ISO/IEC 42001, and GDPR: Best Practices for Implementation and...PECB
Denis is a dynamic and results-driven Chief Information Officer (CIO) with a distinguished career spanning information systems analysis and technical project management. With a proven track record of spearheading the design and delivery of cutting-edge Information Management solutions, he has consistently elevated business operations, streamlined reporting functions, and maximized process efficiency.
Certified as an ISO/IEC 27001: Information Security Management Systems (ISMS) Lead Implementer, Data Protection Officer, and Cyber Risks Analyst, Denis brings a heightened focus on data security, privacy, and cyber resilience to every endeavor.
His expertise extends across a diverse spectrum of reporting, database, and web development applications, underpinned by an exceptional grasp of data storage and virtualization technologies. His proficiency in application testing, database administration, and data cleansing ensures seamless execution of complex projects.
What sets Denis apart is his comprehensive understanding of Business and Systems Analysis technologies, honed through involvement in all phases of the Software Development Lifecycle (SDLC). From meticulous requirements gathering to precise analysis, innovative design, rigorous development, thorough testing, and successful implementation, he has consistently delivered exceptional results.
Throughout his career, he has taken on multifaceted roles, from leading technical project management teams to owning solutions that drive operational excellence. His conscientious and proactive approach is unwavering, whether he is working independently or collaboratively within a team. His ability to connect with colleagues on a personal level underscores his commitment to fostering a harmonious and productive workplace environment.
Date: May 29, 2024
Tags: Information Security, ISO/IEC 27001, ISO/IEC 42001, Artificial Intelligence, GDPR
-------------------------------------------------------------------------------
Find out more about ISO training and certification services
Training: ISO/IEC 27001 Information Security Management System - EN | PECB
ISO/IEC 42001 Artificial Intelligence Management System - EN | PECB
General Data Protection Regulation (GDPR) - Training Courses - EN | PECB
Webinars: https://pecb.com/webinars
Article: https://pecb.com/article
-------------------------------------------------------------------------------
For more information about PECB:
Website: https://pecb.com/
LinkedIn: https://www.linkedin.com/company/pecb/
Facebook: https://www.facebook.com/PECBInternational/
Slideshare: http://www.slideshare.net/PECBCERTIFICATION
Strategies for Effective Upskilling is a presentation by Chinwendu Peace in a Your Skill Boost Masterclass organisation by the Excellence Foundation for South Sudan on 08th and 09th June 2024 from 1 PM to 3 PM on each day.
it describes the bony anatomy including the femoral head , acetabulum, labrum . also discusses the capsule , ligaments . muscle that act on the hip joint and the range of motion are outlined. factors affecting hip joint stability and weight transmission through the joint are summarized.
How to Build a Module in Odoo 17 Using the Scaffold MethodCeline George
Odoo provides an option for creating a module by using a single line command. By using this command the user can make a whole structure of a module. It is very easy for a beginner to make a module. There is no need to make each file manually. This slide will show how to create a module using the scaffold method.
A workshop hosted by the South African Journal of Science aimed at postgraduate students and early career researchers with little or no experience in writing and publishing journal articles.
South African Journal of Science: Writing with integrity workshop (2024)
Building Value Through Enterprise Architecture
1. Perspective Peter Burns
Michael Neutens
Daniel Newman
Tim Power
Building Value through
Enterprise Architecture
A Global Study
2. Contact Information
Beirut
Ramez Shehadi Homayoun Dayani-fard
Partner Senior Associate
+961-1-336-433 +44-20-7393-3509
ramez.shehadi@booz.com homayoun.dayani-fard@booz.com
Raymond Makhoul Tim Power
Senior Associate Associate
+961-1-336-433 +44-20-7393-3725
raymond.makhoul@booz.com tim.power@booz.com
Canberra Munich
Andrew Johnstone-Burt Johannes Bussmann
Partner Partner
+61-2-6279-1965 +49-89-54525-535
andrew.johnstone-burt@booz.com johannes.bussmann@booz.com
Daniel Newman Jörg Sandrock
Senior Associate Senior Associate
+61-2-6279-1962 +49-89-54525-656
daniel.newman@booz.com joerg.sandrock@booz.com
London New York
Greg Baxter John Plansky
Partner Partner
+44-20-7393-3795 +1-212-551-6492
greg.baxter@booz.com john.plansky@booz.com
Hugo Trepant Jamie Solomon
Partner Principal
+44-20-7393-3230 +1-212-551-6709
hugo.trepant@booz.com jamie.solomon@booz.com
Michael Neutens Sydney
Principal Peter Burns
+44-20-7393-3215 Partner
michael.neutens@booz.com +61-2-9321-1974
peter.burns@booz.com
Hugo Trepant and Homayoun Dayani-fard also contributed to this Perspective.
Booz & Company
3. EXECUTIVE The economic crisis has taught organisations a critical lesson:
Only by focusing on long-term value can they ensure their
SUMMARY
survival during difficult times—and be ready to change when the
opportunity or the need arises. Among the capabilities required
to create value now and in the long term is mastery of enterprise
architecture (EA)—the effort to align an enterprise’s operations,
including business functions, processes, and information
systems, with its business goals and strategic direction.
To determine how much value EA can contribute to the
business, Booz & Company recently surveyed executives across
a mix of financial services and government organisations. The
results are revealing.
• Respondents across the board viewed EA as a key capability
for building long-term business value, and are making
significant investments in advancing their EA capabilities.
• EA maturity levels vary greatly among the organisations
surveyed.
• The amount of value captured through EA was clearly
linked to EA maturity level.
Companies looking to improve their EA maturity must work
to develop their capabilities in five critical areas: strategic
alignment, staff competency, performance measurement,
organisational structure, and formal EA processes. That can
be difficult for any organisation, but the rewards are clear:
better value from investment decisions and improved strategic
advantage, now and in the future.
Booz & Company 1
4. WHY ENTERPRISE Business lessons learned during
recessions are often learned painfully.
services and government sectors,
it is becoming increasingly evident
ARCHITECTURE Organisations that had focused that maturity of an organisation’s
MATTERS their planning efforts and capital
deployment on short-term indicators,
EA efforts can have a significant
positive impact on business value in
appealing to the psychology of market several areas, including decreased
speculation, learned that survival operating costs, improved speed-to-
depended on short-term actions— market, reduction of complexity and
across-the-board budget cuts, massive risk, and greater overall technology
layoffs, reduced capital investment— effectiveness.
that set them back as they reentered
the growth cycle. Only by building We are aware that many
the right capabilities for generating organisations have questions about
lasting, long-term value can the value of EA: Does investment
organisations survive, and even thrive, in EA really deliver value to the
during the inevitable downturn, and business? If so, what types of
be agile enough to benefit from new value are being realised? What are
market opportunities as they arise. successful organisations doing to
capture value from EA, and what are
Now is the time, we believe, to make the greatest challenges to attaining
the shift from speculation to real, an effective EA? What actions are
long-term investment in the enterprise. most important for companies in
Service-oriented organisations in developing their EA capabilities?
particular must create value across the And how can EA be used in the short
entire enterprise, from front-office, term and the longer term, given the
customer-facing activities through challenges in the economic climate?
business operations and processes to
the underlying technology. To answer these questions,
Booz & Company recently completed
A critical element in the process of a global enterprise architecture study.
creating value involves enterprise As part of the study, we surveyed
architecture (EA), the effort to EA practitioners and key business
align an enterprise’s operations—its representatives at more than 60
core business functions, processes, organisations in the financial services
information systems, and services— and government sectors around
with its business goals and strategic the globe, then gained additional
direction (see Appendix 1 for a more understanding through one-on-one
complete definition of enterprise interviews with C-level executives,
architecture). For service-oriented including CIOs, COOs, and heads of
organisations throughout the financial strategy and planning.
2 Booz & Company
5. INVESTING IN The results of the study were
revealing. First, every organisation
of EA across both business and IT,
or ‘institutionalised.’ More than 80
EA MATURITY we surveyed is making significant percent of organisations fell within
investments in its EA capability, either the ‘standardised’ (level 3)
and sees it as a continuing priority. or the ‘operationalised’ (level 4)
Furthermore, more than 60 percent categories, indicating that EA is
of the executives interviewed say they gaining traction as a value lever
view investing in their EA capabilities across the business (see Exhibit 1,
as a top-five priority for executing page 4). For those that fell within
their strategy in the coming year. the ‘emerging’ and ‘standardised’
categories, however, EA remains
At the same time, however, the study limited primarily to the IT function.
revealed a wide range of maturity None of the organisations we
levels across organisations. On the surveyed were rated either ‘none’ or
basis of their responses, we assigned ‘institutionalised,’ indicating that
organisations a number from 1 to 5 every organisation is investing in EA
on an EA maturity index that reflected to some degree, but there is still much
a range between no investment in ground to be gained to reach the
EA, or ‘none,’ and full integration highest level of maturity.
“Maturing our EA capabilities is a
top-three priority this year. We will
be using EA as the basis to re-scope
and prioritise our multibillion-dollar
investment program.”
—CIO, government agency
Booz & Company 3
6. As Exhibit 1 indicates, by and large, evolved sometimes inconsistently cant architectural challenges confront-
the financial services firms surveyed over time. With the exception of one ing public-sector organisations, which
scored higher than the government small agency, government organisa- are often complex and interlinked
agencies, a difference that may be tions all displayed either ‘emerging’ or with other organisations through
due to the public sector having more ‘standardised’ EA capabilities. These cross-department portfolios.
complex business models that have capability levels indicate the signifi-
Exhibit 1
The EA Maturity Index and Survey Results
LEVEL 1 LEVEL 2 LEVEL 3 LEVEL 4 LEVEL 5
NONE EMERGING STANDARDISED OPERATIONALISED INSTITUTIONALISED
- Little or no EA maturity - Emerging but limited and - Capability is becoming - Capability is operationalised - Capability is institutionalised
within the organisation ad-hoc capability within the standardised, yet is not fully and operates as an effective and is critical in delivering
- EA is not formally supported organisation effective or consistently core function innovation, agility, and
or executed within the - Limited by lack of alignment followed throughout the - Effectively aligns business strategic advantage, and
organisation to business and IT, organisation and IT through governance, enabling key outcomes of
- No formal investment governance and - Typically limited to the IT communication, and the organisation
planning commitment domain only engagement - Operates across the breadth
of the organisation and at its
most senior levels
Financial Services
Government
EA Maturity Index
EA Maturity Group Key Value Type Key
Lowest index Least mature third of organisations
Median index Middle third of organisations
Upper index Most mature third of organisations
Source: Booz & Company Enterprise Architecture Maturity Model
4 Booz & Company
7. Case Example: Cutting Costs
Over the course of a two-year EA program, a leading Australian bank realised
cost savings of more than AU$200 million (US$161 million), or about 1.4 percent
of total operating expenses—primarily through consolidation, sharing, and reuse
of technology assets. The bank’s EA maturity score placed it in the top third of
organisations surveyed.
The bank integrated EA deeply into its operations, an effort that has been
fundamental to its success. Bank executives point to three key mechanisms in
pursuing that integration:
• Ensuring that the strategic planning process includes input from the EA
program, particularly where investment decisions are required.
• Securing EA input into other governance processes, such as project planning,
which in turn has steadily increased EA’s profile across the organisation.
• Building a federated EA model with a central EA practice supporting domain
experts in each business unit. This enabled the delivery of business-specific
information underpinned by consistent frameworks.
The proven value of EA has only whetted the bank’s appetite for expanding
its EA capability. “There is sufficient feedback,” the bank’s head of enterprise
architecture noted, “to suggest that senior management expects EA to step up to
the next level to set the strategic agenda.” For that to happen, however, the bank
must develop the hybrid business and technology skills enterprise architects
need. Doing so means creating more attractive career paths for enterprise
architects to ensure that their skills are retained.
Booz & Company 5
8. CoNNECTING Booz & Company experience and
initial interviews with executives
The few organisations reporting that
their EA efforts have reaped little or
MATURITY indicated these four areas were no value are all at the ‘emerging’ level
ANd VAlUE the most common benefits being
achieved by EA capabilities. Of the
of EA maturity. In each of these cases,
EA is restricted to the IT function,
one-third of organisations with the with no clear engagement with the
highest EA maturity ratings, more business—in sharp contrast to those
than 60 percent reported having higher on the maturity scale.
In our efforts to establish the link realised all four sources of business
between EA maturity and value, value. Those organisations are also Our study further suggests that there
we looked at four critical areas continuing to invest in EA, indicating is an order to the sources of value
of business value: decreased cost, that they believe there is still value delivered via EA. As organisations
reduced complexity, reduced risk, to be captured by pushing their EA mature, they capture cost savings
and increased agility (see Exhibit 2). maturity further. and operational risk reduction
Exhibit 2
The Relationship between EA Maturity and Value
Least mature third Middle third of Most mature third
of organisations organisations of organisations
100
Proportion of Organisations Reporting Value (% per group)
EA Maturity Group Key
90
Lower
80
Median
Reported value
70 increases with Upper
EA maturity
60
Value Type Key
50
Cost
40
Agility
30
Complexity
20
Risk
10
0
1.0 2.0 3.0 4.0 5.0
NONE EMERGING STANDARDISED OPERATIONALISED INSTITUTIONALISED
EA Maturity Index
Source: Booz & Company analysis
6 Booz & Company
9. earliest, whereas reduced complexity • As with cost benefits, organisations sectors indicate that standardisation
and increased agility become more realised the benefits of reduced risk across the IT function is the key
apparent as their EA maturity relatively early in their maturity factor in reducing complexity.
increases. As companies reach higher efforts. That, we believe, can be
levels of maturity, value tends to be attributed to EA’s ability to provide • Organisations found that
realised across all four of the sources an enterprise-wide view of planned agility—a combination of the
identified. investments, and thus to limit the flexibility needed to create new
problems that can arise through business products and the speed
• Virtually every organisation we misaligned programs. at which they can be brought to
surveyed cited cost reduction as one market—is the most challenging
of the most commonly captured • Managing complexity remains source of value to capture. For
sources of value. Yet those with a challenge for organisations many organisations, only strong
the highest levels of maturity that have yet to reach at least a architectural alignment between
reported significantly greater cost ‘standardised’ level of EA maturity. business and technology could
savings, implying that the tighter Many organisations in both the enable the nimbleness needed
the alignment between business financial services and government for effective change, such as
and technology, the greater the cost
advantage.
“The bank has leveraged EA to
manage the governance and
complexity of its channels, processes,
and systems, resulting in increased
customer satisfaction and growth
in key customer segments.”
—Executive VP, financial services organisation
Booz & Company 7
10. Case Example: Improving Efficiency and Customer Service
As part of a government mandate, a large U.K. government agency embarked
on a transformation to improve its efficiency and customer service. The agency
had been largely paper-based, with separate business processes for the various
benefits it administered. Fragmented workflow processes and outdated IT
systems had adversely affected customer service, efficiency, and staff morale.
The use of EA was a key enabler in the transformation, which resulted in
a reduction of the average time it took to process claims by more than 70
percent, from more than four weeks to just five days, and reduced the number
of processing centres by 60 percent, from 25 to 10. Among the benefits of the
agency’s EA efforts:
• EA provided clarity for the agency’s vision and helped it facilitate the transition
from its paper-based processes to modern CRM-based processes. The
transition plan allowed for the coexistence of old and new processes, while
targeting quality assurance on activities in critical areas. This helped reduce
reengineering an existing product operational risk while the transformation was taking place.
to respond to market changes
• EA drove the alignment of business and IT objectives by following focused
quickly. Furthermore, they found
principles and discipline. It enabled the use of common software packages
that the business must lead the
with minimal customisation, for example, and the implementation of a CRM
effort to identify and coordinate
system in a “wrapper” pattern to cut costs and minimise the new system’s
the various enterprise functions
impact on legacy systems.
needed to enhance speed-to-market.
• EA encouraged the reevaluation of a number of third-party contracts;
Organisations in both the financial subsequent renegotiations resulted in a reduction of 25 percent on the
services and government sectors agency’s end-to-end IT systems integrator contracts, for a total savings
gain business value as their EA estimated at £10 million (US$14 million).
maturity improves. Yet the study
indicates that the two sectors vary By providing an integrated view of its business and IT architectures, EA was
significantly in how they use EA, and instrumental in helping the agency meet its transformation objectives, while
in their expectations for the kinds managing operational risk along the way. The agency had initially outsourced
of value they might get out of it. its EA efforts to external professionals, but by adopting a systematic approach
Financial services companies typically to capturing the knowledge gained, it now has the expertise to continue with
focus on using EA to help guide minimal external support.
organisation-wide strategies such as
cost control, pre-merger and post-
merger integration, infrastructure
consolidation, and the delivery of
new products. They see EA as a tool
for gaining competitive advantage.
Government-sector organisations,
on the other hand, see EA as a tool
to enhance internal collaboration,
interoperability, and the ability
to share information among
different departments and agencies.
By focusing their EA efforts on
standardising government services,
these organisations aim to manage
their portfolios of resources more
effectively, particularly for the
implementation of large programs.
8 Booz & Company
11. dRIVING VAlUE explain, however, what it takes to
reach the higher levels of maturity.
Furthermore, those elements with the
greatest link between maturity and
Achieving EA maturity involves five value are also the ones respondents
critical elements: strategic alignment, viewed as the biggest challenges (see
staff competence, performance Exhibit 3). Unsurprisingly, there is
measurement, organisational structure, no free lunch, but those who can
The connection between EA maturity and formal processes. Each is vital to overcome the most significant EA
and business value is clear—the value the success of every EA effort, yet they challenges will reap the rewards.
captured is directly correlated with vary significantly in their link to the
the level of maturity. That doesn’t value created through EA.
Exhibit 3
The Five Elements of EA Maturity
MATURITY ELEMENT ELEMENT DESCRIPTION LINK TO VALUE CHALLENGES
Relative difference in element Respondents noting the maturity
maturity between organisations that element as a key challenge to
did and did not report value(1) maturing EA(2)
The extent to which the EA function is involved
STRATEGIC in both business and technology strategic
planning and how well EA engages with the 1.7 40%
ALIGNMENT
wider organisation
The level of competency of EA’s leaders and
STAFF practitioners and how well EA is recognised and 1.6 40%
COMPETENCE fostered as a career path
PERFORMANCE How well EA’s success is defined, measured,
and improved with formal metrics 1.5 24%
MEASUREMENT
The extent to which the EA function is formally
ORGANISATIONAL structured and governed, the seniority of EA’s
practitioners, and the level of recognition of EA 1.1 18%
STRUCTURE
throughout the business
The extent to which formalised frameworks,
FORMAL methodologies, and supporting technologies
PROCESSES are used within the EA function and the breadth 1.0 7%
of the adoption of EA standards firm-wide
1 The average difference in maturity scores between organisations that did and did not report value was calculated for each maturity element. The differences displayed are
normalised to the lowest difference, which is set to 1.0 (i.e., on the formal processes maturity element).
2 Percentage of respondents noting the maturity element as a key challenge to maturing an EA capability.
Source: Booz & Company analysis
Booz & Company 9
12. The use of EA to aid in the alignment across the organisation. However, One could argue that the success of
between an organisation’s operations a large percentage of respondents every service firm relies ultimately
and its business goals is the most recognised the difficulty of building on the quality of its people, and
critical driver in achieving business that engagement, particularly when an EA program is no different.
value; every EA effort must be the wider organisation has only a Organisations with high levels of EA
focused on actual business results. limited understanding of what EA maturity have typically succeeded in
Hence, successful organisations consists of or why it matters. If overcoming two major competence
overwhelmingly design their EA an EA program is to succeed, it is hurdles: They have cultivated leaders
functions to be included in both critical that it remain relevant to who can effectively communicate
technology and business strategic the firm’s strategic agenda, and that EA’s value throughout the
planning processes—to force strong the overall organisation remains organisation (in both technical and
formal engagement between the two cognizant of its importance. non-technical settings), and they have
“Previous IT-led attempts to mature
EA failed. EA is now located
within and led by the business,
making the organisation more
responsive to changing priorities
and business challenges.”
—CIO, government agency
10 Booz & Company
13. established training and development that EA is not simply the preserve of
paths for enterprise architects to the IT department.
grow the practice from within.
Investing in internal development Interestingly, the study reveals that
not only helps alleviate difficulties in organisation (how the EA function is
procuring external talent, but also structured) and process (EA-related
breeds architects with the necessary frameworks, tools, methodologies,
intimacy with business knowledge. and the like) maturity were less
significant differentiating elements
Performance measurement is in the value realised from EA than
the third key maturity element. were the other maturity elements.
Successful organisations have learned By and large, organisations find
how to measure accurately the these maturity elements easy to
outcomes of their EA efforts and use ‘do’ well. This being the case, these
the results to further drive support elements should be considered as
in the business. Alignment of those ‘givens’ in developing a functional EA
metrics with organisational strategy capability—they are important but not
is critical. Successful EA functions differentiating. Organisations would
measure, and communicate, results do well to focus effort primarily on
that matter to the business, which strategic alignment, staff competency,
in turn only strengthens the message and performance measurement.
Booz & Company 11
14. Case Example: Managing Complexity
A leading European bank needed to ensure that its recently outsourced IT
activities continued to provide optimum service to the business. By expanding
its EA capability, which had traditionally resided within the IT function, the bank
successfully integrated those outsourced services. And by reusing applications
and processes across its previously siloed business lines, it also reduced
complexity and costs. The success of the program was driven by:
• Formalising EA’s strategic role in the governance of the new outsourcing
arrangements to ensure that services provided by the extended organisation
were aligned with the needs of the business.
• Building comprehensive organisational knowledge of the EA capability by
locating architects within each business line.
• Maintaining EA’s technology roots through close engagement between
internal solution and infrastructure architects internally and the new
outsourcing partners.
The bank has begun to reap the rewards of EA’s growing profile and influence,
dElIVERING
in part because it is now the only function able to provide an integrated VAlUE
view across the extended enterprise. The bank’s key future challenges lie in
further strengthening the relationship between business and IT, and their joint
governance of EA, and in formalising its business processes and aligning them
with a corresponding master plan for IT.
Each of the five drivers of value
discussed above carries its own
set of challenges, and overcoming
those challenges is key to getting the
most impact from investments in
EA. The results of the study reveal
that successful organisations—those
that have managed to capture,
demonstrate, and communicate the
value of their EA investments—all
turn to a similar set of practices to
reach those goals. Exhibit 4 lays
out in detail both the challenges
organisations encounter in capturing
value through EA, and the leading
practices they put in place to do so.
Embed EA into Strategic Planning
Ultimately, the success of any EA
program depends on its relevance to
business decision makers, and the
business value it creates—and that,
in turn, depends on how helpful it
is in aligning enterprise structure
with overall business strategy. Thus,
every EA program must be structured
from the start to ensure its efforts are
directed toward projects of significant
business importance.
12 Booz & Company
15. In practice, achieving strategic Similarly, another respondent, a highly skilled resources’ as the biggest
alignment requires a conscious, indeed senior executive at a government challenge to EA success. Mature
formal, effort. Said one banking organisation, noted that EA must be EA organisations have succeeded in
executive whose organisation has an integral part of strategic planning. overcoming this challenge by focusing
achieved a high level of EA maturity: ‘EA is embedded in [the] business,’ on building internal competencies,
‘Within each business unit exist joint he said, ‘not exposed as a separate particularly through strong leadership
business and technology strategy function called EA.’ and by encouraging architecture-
boards through which the business related training. These practices, in
directs and prioritises the architecture Grow EA Experts from Within turn, allow mature organisations
effort against its strategic imperatives.’ Along with strategic alignment, to promote EA as a professional
survey respondents cited ‘access to career path with formalised roles,
Exhibit 4
Leading Practices of Firms with Mature EA Capabilities
MATURITY ELEMENT VALUE DRIVERS CHALLENGES LEADING PRACTICES
- Involvement in strategic planning - Poor business engagement with and Embed EA into strategic planning
STRATEGIC - Formal engagement models adoption of EA - Build strong formal engagement with the
ALIGNMENT - Alignment to both business and - Lack of understanding of EA organisation
IT agendas throughout organisation – perceived - Focus EA on issues most relevant to the business
as an IT or compliance function
Grow EA experts from within
- Strong leadership to drive - Difficulty sourcing staff with
positioning of EA across the appropriate skills - Nurture experts who can communicate with both
STAFF business and technology
organisation - Finding leaders who can effectively
COMPETENCE
- Strong internal training and communicate value of EA to both IT Measure meaningful success
development and business staff
Increasing Importance
- Link EA to enterprise KPIs
- Monitor EA’s impact (e.g., before-and-after
- Formalised performance - Measurement of EA outcomes,
comparisons)
PERFORMANCE measurement underpinning difficulty in selling it to
MEASUREMENT the wider organisation Promote EA to the organisation
- Highlight EA’s measured impact on enterprise
priorities
- Clearly defined governance - Lack of support at senior levels - Build senior management support
ORGANISATIONAL and decision rights
Grow EA through the organisation and into the
STRUCTURE extended enterprise
- Retain a solid core EA practice
- Incorporation of EA standards - Ensuring use of standardised - Consider federated models, building business
into formal project delivery frameworks, methodologies, ownership of EA content
FORMAL and tools - Grow into the extended enterprise (e.g., partners,
PROCESSES customers)
Source: Booz & Company analysis
Booz & Company 13
16. responsibilities, and decision rights, Organisations with mature EA made and the outcomes achieved.
offering employees a compelling functions have addressed this Such organisations make a point
value proposition. As one senior challenge by creating formal of embedding EA into the fabric
director at a prominent government performance measurement built on of business and operational
agency put it, ‘EA leaders are the both qualitative and quantitative data. decisions, rather than making
leaders in the business, information, At a broad level, quantitative metrics separate technology decisions. These
and technology domains by nature of used by banks include changes over organisations typically also ensure the
their roles, and [this] positions [them] time to cost/income ratio, correlated involvement of senior management
as part of the planning organisation.’ with EA-driven projects focused on in supporting EA investment and
cost. Qualitative metrics often focus in communicating its value to the
Measure Meaningful Success on collective enterprise architects’ organisation. In the words of one
Like any other business function, performance and feedback from banking executive, ‘The acid test for
EA must be accountable for how within the organisation. A banking this is that our CEO is always asking
well it performs and measures up executive at a mature organisation if we have enough resources.’
against key performance indicators. reports measuring architects as part of
And measurement and attribution an annual process that includes ‘the Yet one of the most commonly cited
of results is even more critical for percentage of funding allocated on challenges to EA maturity included
an emerging capability looking to the basis of architecture deliverables, the level of business awareness and
prove its value to the organisation. value of the input into projects by the generation of an organisation-
Survey respondents identified the the key stakeholders, how creative wide understanding of the importance
need to prove ongoing success as one and proactive we are in our solution of EA. To address these issues,
of the most common challenges in architectures, and our understanding it is critical to develop a strong
developing a mature EA function. of the business and its problems. communication mechanism that can
‘A lack of demonstrable value to the Measures are scored through a survey educate the organisation on both the
organisation [means] no successes to sent to stakeholders.’ nature and value of EA. As a banking
generate interest [in EA],’ a senior business architect put it, ‘During
government executive explained. Promote EA Across the Organisation a survey, we found that a formal
Once they gain the capacity to In organisations with mature communication plan—including case
measure results, mature organisations EA capabilities, EA champions studies to prove the realisation of
often focus on completing quick- typically communicate the value benefits—should improve [the bank’s]
win projects that allow them to of EA to the business in terms of view of EA.’
demonstrate EA’s ability to add value. the strategic business decisions
14 Booz & Company
17. Case Example: Driving IT Portfolio Prioritisation
A sophisticated EA program allowed a large U.S. government agency to unify its
disparate portfolio management processes across its many business lines and
guide its US$1.04 billion IT investment portfolio. Over three years, the agency
estimates, the effort saved approximately $102 million—more than 3 percent
of its annual IT budget—primarily by eliminating duplicate investments and
capturing gains in business process efficiency.
Furthermore, the ability to reprioritise IT investments allowed the agency to
reap significant business benefits by completing major IT projects early. One
IT investment, a system designed to speed up a case resolution process, was
delivered a year early; now cases are being resolved 25 percent faster, resulting
in efficiency gains and cost savings.
The agency attributes the success of its new IT portfolio management process to
several key factors:
• EA provided executives with a common language and a single integrated
Grow EA through the Organisation
business–IT planning framework for navigating complex planning and
and into the Extended Enterprise
investment activities. The new EA-driven process enabled the agency to make
As organisations build their
trade-offs with an understanding of the implications of and dependencies
internal EA capabilities, the effort
between business processes, IT systems, and data.
to unlock value beyond their
traditional boundaries and into • EA encouraged the use of a collaborative, business-driven engagement
the extended enterprise becomes model that ensured a high level of executive and business involvement.
increasingly important. Key areas
for opportunity include supplier and • EA allowed planners to take a ‘top-down’ perspective on the many business
partner interactions. By making these challenges and capabilities that the modernisation effort needed to address.
efforts, organisations can ensure the That perspective sharpened the focus on high-priority initiatives, building
standardisation needed to provide an momentum and maintaining credibility with the business.
effective, efficient, and consistent user
Thanks to its EA efforts, the agency has significantly improved its decision-
experience and delivery of service.
making and planning capabilities; now it intends to integrate EA into planning
across all business lines. Despite the success of this pilot effort, however, the
As an executive at one government
agency faces a key challenge shared by many not-for-profit organisations:
agency put it, ‘To support IT
measuring and communicating the value of EA to the rest of the business.
strategic planning, [we are] leading
“Much of the value is related to achieving business benefits [such as increased
the effort to design and develop
operational efficiencies], not just reduction of costs,” says the agency’s senior
a single enterprise architecture,
advisor for EA.
using a strategy that federates with
external partners and incorporates
an integrated, coordinated, flexible,
and long-term strategically focused
approach.’ That view was echoed
from the banking sector by another
executive: ‘Architecture develops
and communicates the key guidelines
by which technology procurement
and development is carried out,’ he
said. ‘We influence the allocation of
funding to technology initiatives and
major business initiatives.’
Booz & Company 15
18. EA IN THE • Controlling costs and budget:
When cost pressures are high,
choose the winning vendors.
By helping executives better
SHoRT ANd executives must find ways of doing understand how specific outsourced
loNG TERM more with less. During downturns,
organisations often make the
services are being supplied to
specific business lines, EA can help
mistake of cutting costs by a executives manage their portfolio
predetermined percentage across of vendor relationships as these
every part of the business, a tactic changes take place.
that too often results in destroying
Enterprise architecture is a critical value and alienating customers. • Generating capital at a time of
capability for organisations looking EA provides executives with the need: Given the high cost of capital
to create long-term value. Building transparency to look across aspects in tough times, particularly at
long-term value, however, will also of the business holistically, to assess financial services organisations, IT
bring benefits in the shorter term. their investments in operations and and operations assets can serve as
By improving transparency, refining specific projects, and thus prioritise a source of leverage. By providing
business processes, and tightening those areas that will bring in the a holistic view across the landscape
the connections between tactics most value. of IT systems and vendor services,
and strategy, EA can help support EA can help executives carve out
prudent near-term planning and • Managing the extended enterprise areas that can generate cash. These
decision making—a vital capability for value: As demand for offshore might include creating innovative
as organisations work to improve services shifts and currency financing arrangements when
their agility in response to every markets fluctuate, the offshore buying hardware or software,
market situation. vendor landscape and offerings switching to leasing deals for major
will likely change. In order to keep assets such as server farms, or
EA can help executives make up, executives, particularly those moving to more highly leveraged
significant contributions to the in operations and IT, will need to financing arrangements for large-
business in the near term in four make the right decisions to extract scale outsourcing contracts.
key areas: value from vendor contracts and
16 Booz & Company
19. • Developing positive relations with offering effective solutions while that can put them at a competitive
regulators and external parties: limiting the cost and distraction. advantage as markets change and
Regulators are demanding more grow. In this scenario, EA can help
and more data from organisations Short-term agility offers a further organisations over the longer term in
and greater control over IT as they long-term advantage. At a time three key areas:
try to manage risk, particularly when industries are being reshaped,
at financial services companies. organisations must be sure to define • Efficiency and lean operations:
At the same time, public service their strategies clearly, and implement Providing visibility across the
organisations find themselves and maintain cohesive architectures enterprise, EA helps ensure
under greater scrutiny as oversight of operations and IT capabilities disciplined standardisation and
agencies demand more transparency around those strategies—including consolidation across operations
and internal controls. By providing the extended enterprise of partners, and IT functions by removing
top-down clarity into IT assets and vendors, and other stakeholders. redundant systems, phasing
information, EA can help executives Organisations possessing these capa- out costly and complex legacy
respond to regulatory requirements bilities will be best equipped to create systems, and managing across the
and external stakeholder demands, innovative new products and services extended enterprise. That in turn
“EA is a core function; investment
in it remains a high priority. EA
plays a major role in enabling
a common vision and strategy
across our five business units.”
—CIO, financial services organization
Booz & Company 17
20. CoNClUSIoN
By establishing, improving, and
measuring the connection between
an organisation’s operations and
technology and its overall strategic
goals, a mature EA capability has the
potential to create value no matter
how weak or strong the economic
climate. The key is the ability to be
agile, to be responsive to markets
and customers, to be flexible in
approaching partnership and
delivers real savings, measured by customers with a single view of the acquisition opportunities—in short,
monitoring metrics such as cost/ organisation. Doing so requires the to be able to change. Change is never
income ratio, total and targeted focused integration of information easy, but EA offers the potential to
cost savings achieved, and number and customer preferences across guide companies in their efforts to
of processes improved. multiple channels, as well as change, to link business processes
the standardisation of processes and technology more tightly with
• Agility and innovation: The value familiar to the customer across strategy, to make better investment
of any innovation lies not just in the enterprise and across decisions, and to measure the results
the innovation itself, but in the geographic boundaries. of those decisions—all in the service
ability to deliver it quickly. A of generating greater business value.
mature EA function will improve Here, EA helps enhance the
the agility needed to bring new traditional distribution system
products to market more quickly, by enabling the identification of
while increasing the number of new lucrative new channels, as well as
products launched in alignment the channel mix that will produce
with overall business strategy. How the greatest margins. This might
EA contributes to agility can be include developing the common
difficult to measure; still, executives IT infrastructure needed for
can track metrics such as time- multichannel sales, and supporting
to-market for new products and business process integration with
the number of new business plans transaction layers between the front
executed with the help of EA. and back ends.
• Customer-focused services: Again, measuring the gains
Building and maintaining attributable to EA can be
competitive advantage depends challenging. Some of the basics,
greatly on continuously improving such as the number of new
the services and support offered channels and services developed
to customers. EA can play a key for the customer, can be measured
role in planning and executing easily. More complex, but just as
customer-focused services and important, are comparative
managing the end-to-end customer metrics such as customer care
experience. That means creating performance changes for specific
the right product and service channels and services, and new
mix, offering compelling and customers acquired versus customer
integrated channels, and providing groups targeted.
18 Booz & Company
21. APPENDIX
Defining EA: A Strategic Framework and an Operating Practice
Despite its importance, EA remains a fuzzy concept in corporate strategic
planning. No common industry definition really exists, and there is no general
agreement on its role, scope, and functional responsibilities. If anything, it is
typically seen primarily as an IT function, limited to the design of IT infrastructure
and systems. Yet that notion severely constrains both the organisation-wide
importance of EA and its ability to deliver real business value.
We define EA as a logical framework that establishes the links between overall
strategy and the organisational structures, business processes, information, and
technology needed to fulfil that strategy and deliver the enterprise’s business
vision. By providing an end-to-end holistic view of the enterprise, EA aims to
support the decision-making process needed to continuously improve and fine-
tune the effectiveness and efficiency of the business.
As a framework, EA serves as a guiding reference and a communication bridge
connecting business operations with IT. Because it is a dynamic function,
it should be actively managed to support the business as its competitive
environment changes. EA ideally depicts two views: the existing enterprise, and
the enterprise of the future as it is envisioned to achieve its business goals.
On paper, EA is the blueprint and the road map for the development and
management of several components (see Exhibit 5). In practice, it must include
how all those components operate and work together. That includes putting
in place the proper organisational structure and hybrid business/IT roles,
consolidating and standardising information and data stores, and integrating
applications and infrastructure to support the right business processes across
the enterprise.
Exhibit 5
Key Components of Enterprise Architecture
Results (for Business and Customers)
Business Vision and Strategies
(Enterprise) Business Processes1
- Strategy planning - Product processing - Financial management
- Sales and marketing - Account management - Portfolio management
- Customer services - Payment processing - Regulatory reporting
services
requirements
Alignment
Standards
Organisation Information Technology Integration
- Structure - Data architecture and - Application services
- Roles and responsibilities management - Product platforms
- Skills/competencies - Business information - Integration layers
- Performance management - Customer data - Infrastructure
Extended Enterprise
- Associations - Third-party service - External systems
providers
1 Example business processes. Not exhaustive.
Source: Booz & Company Enterprise Architecture Definition
Booz & Company 19
22. Research Methodology
The Booz & Company enterprise architecture study was conducted between
October 2008 and March 2009. There were 129 respondents representing 64
companies worldwide who participated in an interview, online survey, or both. The
respondents were directors or heads of technology, leaders within business lines,
and chief architects across the targeted enterprises.
In order to provide a balanced view of EA maturity across both the public and
private service sectors, half of the responding organisations came from financial
services and half from government. We also set out to achieve a geographic
balance—33 percent of participating organisations were based in North America;
36 percent were based in Europe, the Middle East, and Africa; and 31 percent
were based in Asia and Australia.
All quantitative data presented in this report was drawn from the results of the
online survey. Participants were asked to rate elements of their organisations’
EA maturity on a five-point scale and identify different forms of value
attributable to their EA capabilities. In cases where more than one employee
responded from a single organisation, we calculated the maturity score for
that organisation by averaging the responses. The qualitative data, including
quotations and case studies, was drawn from detailed interviews and text
responses to online survey questions.
20 Booz & Company
23. About the Authors
Peter Burns is a partner with Daniel Newman is a senior
Booz & Company based associate at Booz & Company
in Sydney. As the leader of based in Canberra. He has
the firm’s service operations extensive experience working
business in the ANZSEA region, with government clients
he focuses on financial services on business & IT strategy,
and government clients. enterprise architecture, and
operating model development.
Michael Neutens is a principal
based in Booz & Company’s Tim Power is an associate in
London office. He focuses Booz & Company’s London
on strategy, operations, and office. He focuses on business
performance improvement with strategy and IT across the
financial services companies. financial services and civil
government sectors.
Booz & Company 21