Enterprise Information Architecture (EIA) - Revision history

User at 10:53, 16 July 2023

2023-07-16T10:53:17Z

User at 23:21, 18 January 2023

2023-01-18T23:21:56Z

User: The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

2021-02-06T15:42:14Z

The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

User at 18:56, 5 December 2019

2019-12-05T18:56:19Z

User at 18:55, 5 December 2019

2019-12-05T18:55:26Z

User: Enterprise information architecture (EIA) is the part of the enterprise architecture process that describes the current state, future state and guidance necessary to flexibly share and exchange information assets to achieve effective enterprise change.

2018-12-24T20:03:28Z

Enterprise information architecture (EIA) is the part of the enterprise architecture process that describes the current state, future state and guidance necessary to flexibly share and exchange information assets to achieve effective enterprise change.

New page

Enterprise information architecture (EIA) is the part of the enterprise architecture process that describes — through a set of requirements, principles and models — the current state, future state and guidance necessary to flexibly share and exchange information assets to achieve effective enterprise change.<ref>Definition of Enterprise Information Architecture (EIA) [https://www.gartner.com/it-glossary/enterprise-information-architecture Gartner]</ref>

'''Explaining Enterprise Information Architecture (EIA)'''<ref>Explaining Enterprise Information Architecture (EIA) [http://www.ies.aust.com/papers/Architecture.html Clive Finkelstein]</ref> 
Linking an enterprise’s strategic plan with its enterprise data architecture, enterprise application architecture and enterprise technical architecture results in enterprise information architecture. A well-documented architecture is a logical organization of information pertaining to the following corporate-level, enterprise-wide elements:
*Strategic goals, objectives, and strategies
*Business rules and measures
*Information requirements
*Application systems
*Relationships between applications and data elements
*Technology infrastructure

Enterprise information architecture also establishes guidelines, standards, and operational services that define the enterprise’s systems development environment. When an enterprise’s architecture is so documented, it can be used to accomplish the following:
*Facilitate change management by linking strategic requirements to systems that support them and by linking the business model to application designs
*Enable strategic information to be consistently and accurately derived from operational data
*Promote data sharing, thus reducing data redundancy and reducing maintenance costs
*Improve productivity through component development, management and reuse
*Reduce software development cycle time

'''Components of Enterprise Information Architecture (EIA)'''<ref>Components of Enterprise Information Architecture (EIA) [https://www.techopedia.com/definition/30587/enterprise-information-architecture-eia Techopedia]</ref> 
The enterprise information architecture comprises of three sub-components/sub-architectures, namely:
*Business architecture: Business architecture provides the integrated view of the data from a business-oriented perspective.
*Technical architecture: Technical architecture provides the outlook of the present technical environment and the migration plan to bring the desired technical environment.
*Organization architecture: Organization architecture deals with high level organizational structure as well as the processes done by each individual unit in the organizational units in the company.

[[File:Enterprise Information Architecture.gif|300px|Enterprise Information Architecture (EIA)]] 
source: [http://tdan.com/enterprise-information-architecture/4231 TDAN]

'''Characteristics of a well-defined EIA implementation'''<ref>Characteristics of a well-defined EIA implementation [https://brainmass.com/file/1566573/The.Art.of.Enterprise.Information.Architecture-236.pdf Mario Godinez et al.]</ref> 
Primary characteristics that can be used to distinguish a well-defined EIA implementation include the following:
*Gaining transparency —The information remains independent from application specifications, application implementations, and user interfaces. It provides a transparency layer between the information and application domains.
*Considering enterprise business requirements —The architecture takes into account the overall information needs of the entire enterprise and specific LOBs or individual organizations.
*Avoiding inconsistencies — It helps identify inconsistencies, conflicts, overlaps, and aps in the data and information, and offers a concept, framework, and methods to resolve this, and it is useful to select adequate solutions.
*Managing Service Level Agreements (SLA) — It provides mechanisms for the definition and management of information-centric SLAs which can be monitored and enforced.
*Enabling decision making —The architecture enables more consistent and efficient IT decision making that is linked to business needs. It does this because it is both flexible and extensible.
*Addressing reusability aspects — Enforcing an EIA means that information assets are shared and reused, avoiding data duplication and thus reducing development, service, and support costs.
*Addressing data scope —The Information Reference Model used by the enterprise describes the scope of the used data and information supported by the EIA.
*Defining a technology strategy — It establishes the framework upon which the technology strategies adopted by the enterprise depend. In addition, it defines the set of principles that guide how an organization’s information systems and technology infrastructure are engineered.

'''Benefits of Enterprise Information Architecture (EIA)'''<ref>Benefits of Enterprise Information Architecture (EIA) [http://tdan.com/enterprise-information-architecture/4231 Paul Sturlis]</ref> 
Some benefits of building and maintaining an EIA are:
*Facilitates assessment of packaged applications for “fit” within the organization (assuming a Corporate Data Model and Function Model is developed)
*Eases integration of acquired companies’ data into our systems environment because the data can be “mapped” into a “logical” Corporate Data Model (rather than directly into physical tables)
*Facilitates development of a common language (and understanding) amongst our lines of business because the models are developed from an enterprise-wide perspective
*Speeds the orientation process of new employees because they can quickly become acquainted with the business through analysis of selected portions of the models
*Provides a “roadmap”, via the Corporate Data Model, for assessing existing (in-house built) operational data structures and planning for their re-engineering into an integrated set of structures

===References===
<references/>

===Further Reading===
*Enterprise Information Architecture: Strategic thinking around Data and Processes [http://www.dataversity.net/enterprise-information-architecture-strategic-thinking-around-data-and-processes/ Dataversity]</ref>
*Enterprise Information Architecture: A Semantic and Organizational Foundation [http://boxesandarrows.com/enterprise-information-architecture-a-semantic-and-organizational-foundation/ Tom Reamy]
*The Art of Enterprise Information Architecture: A Systems-Based Approach for Unlocking Business Insight [https://brainmass.com/file/1566573/The.Art.of.Enterprise.Information.Architecture-236.pdf Mario Godinez, Eberhard Hechler, Klaus Koenig, Steve Lockwood, Martin Oberhofer, Michael Schroeck]
*An Enterprise Information Architecture: A Case Study for Decentralized Organizations [https://www.computer.org/csdl/proceedings/hicss/2000/0493/07/04937059.pdf Richard W. Watson]

← Older revision		Revision as of 10:53, 16 July 2023
Line 1:		Line 1:
−	'''Enterprise Information Architecture (EIA)''' is the part of the enterprise architecture process that describes — through a set of requirements, principles, and models — the current state, future state, and guidance necessary to flexibly share and exchange information assets to achieve effective enterprise change.<ref>Definition of Enterprise Information Architecture (EIA) [https://www.gartner.com/it-glossary/enterprise-information-architecture Gartner]</ref>	+	'''Enterprise Information Architecture (EIA)''' is the part of the [[Enterprise Architecture\|enterprise architecture]] process that describes — through a set of requirements, principles, and models — the current state, future state, and guidance necessary to flexibly share and exchange information assets to achieve effective enterprise change.<ref>Definition of Enterprise Information Architecture (EIA) [https://www.gartner.com/it-glossary/enterprise-information-architecture Gartner]</ref>

@@ Line 1: / Line 1: @@
-'''Enterprise Information [[Architecture]] (EIA)''' is the part of the [[Enterprise Architecture|enterprise architecture]] [[process]] that describes — through a set of requirements, principles and models — the current state, future state and guidance necessary to flexibly share and exchange information assets to achieve effective [[Organizational Change|enterprise change]].<ref>Definition of Enterprise [[Information Architecture]] (EIA) [https://www.gartner.com/it-glossary/enterprise-information-architecture Gartner]</ref>
+'''Enterprise Information Architecture (EIA)''' is the part of the enterprise architecture process that describes — through a set of requirements, principles, and models — the current state, future state, and guidance necessary to flexibly share and exchange information assets to achieve effective enterprise change.<ref>Definition of Enterprise Information Architecture (EIA) [https://www.gartner.com/it-glossary/enterprise-information-architecture Gartner]</ref>
 '''Explaining Enterprise Information Architecture (EIA)'''<ref>Explaining Enterprise Information Architecture (EIA) [http://www.ies.aust.com/papers/Architecture.html Clive Finkelstein]</ref><br />
-Linking an enterprise’s [[Strategic Planning|strategic plan]] with its enterprise [[Data Architecture|data architecture]], enterprise [[Application Architecture|application architecture]] and enterprise [[Information Technology Architecture|technical architecture]] results in enterprise information architecture. A well-documented architecture is a logical [[organization]] of information pertaining to the following corporate-level, enterprise-wide elements:
+Linking an enterprise’s strategic plan with its enterprise data architecture, enterprise application architecture and enterprise technical architecture results in enterprise information architecture. A well-documented architecture is a logical organization of information pertaining to the following corporate-level, enterprise-wide elements:
-*Strategic [[Business Goals|goals]], [[Business Objective|objectives]], and [[Business Strategy|strategies]]
+*Strategic goals, objectives, and strategies
-*[[Business]] rules and measures
+*Business rules and measures
 *Information requirements
-*[[Application]] systems
+*Application systems
-*Relationships between applications and [[data]] elements
+*Relationships between applications and data elements
-*[[IT Infrastructure|Technology infrastructure]]
+*Technology infrastructure
-Enterprise information architecture also establishes guidelines, standards, and operational services that define the enterprise’s [[Application Development|systems development]] environment. When an [[Enterprise Architecture|enterprise’s architecture]] is so documented, it can be used to accomplish the following:
+Enterprise information architecture also establishes guidelines, standards, and operational services that define the enterprise’s systems development environment. When an enterprise’s architecture is so documented, it can be used to accomplish the following:
-*Facilitate [[Change Management|change management]] by linking strategic requirements to systems that support them and by linking the [[Business Model|business model]] to application designs
+*Facilitate change management by linking strategic requirements to systems that support them and by linking the business model to application designs
 *Enable strategic information to be consistently and accurately derived from operational data
 *Promote data sharing, thus reducing data redundancy and reducing maintenance costs
-*Improve [[Productivity|productivity]] through component development, [[management]] and reuse
+*Improve productivity through component development, management and reuse
 *Reduce [[Software Development Life Cycle (SDLC)|software development cycle]] time
@@ Line 21: / Line 21: @@
 '''Components of Enterprise Information Architecture (EIA)'''<ref>Components of Enterprise Information Architecture (EIA) [https://www.techopedia.com/definition/30587/enterprise-information-architecture-eia Techopedia]</ref><br />
 The enterprise information architecture comprises of three sub-components/sub-architectures, namely:
-*[[Business Architecture]]: Business architecture provides the integrated view of the data from a business-oriented perspective.
+*Business Architecture: Business architecture provides the integrated view of the data from a business-oriented perspective.
-*[[Information Technology Architecture|Technical Architecture]]: Technical architecture provides the outlook of the present technical environment and the migration plan to bring the desired technical environment.
+*Technical Architecture: Technical architecture provides the outlook of the present technical environment and the migration plan to bring the desired technical environment.
-*Organization Architecture: Organization architecture deals with high level [[Organizational Structure|organizational structure]] as well as the processes done by each individual unit in the organizational units in the company.
+*Organization Architecture: Organization architecture deals with high-level organizational structure as well as the processes done by each individual unit in the organizational units in the company.
@@ Line 32: / Line 32: @@
 '''Characteristics of a well-defined EIA implementation'''<ref>Characteristics of a well-defined EIA implementation [https://brainmass.com/file/1566573/The.Art.of.Enterprise.Information.Architecture-236.pdf Mario Godinez et al.]</ref><br />
 Primary characteristics that can be used to distinguish a well-defined EIA implementation include the following:
-*Gaining transparency —The information remains independent from application specifications, application implementations, and [[User Interface|user interfaces]]. It provides a transparency layer between the information and application domains.
+*Gaining transparency —The information remains independent from application specifications, application implementations, and user interfaces. It provides a transparency layer between the information and application domains.
-*Considering enterprise business requirements —The architecture takes into account the overall information needs of the entire enterprise and specific [[Line of Business (LOB)|LOBs]] or individual organizations.
+*Considering enterprise business requirements —The architecture takes into account the overall information needs of the entire enterprise and specific LOBs or individual organizations.
-*Avoiding inconsistencies — It helps identify inconsistencies, conflicts, overlaps, and aps in the data and information, and offers a concept, [[framework]], and methods to resolve this, and it is useful to select adequate solutions.
+*Avoiding inconsistencies — It helps identify inconsistencies, conflicts, overlaps, and aps in the data and information, and offers a concept, framework, and methods to resolve this, and it is useful to select adequate solutions.
-*Managing [[Service Level Agreement (SLA)|Service Level Agreements (SLA)]] — It provides mechanisms for the definition and management of information-centric [[Service Level Agreement (SLA)|SLAs]] which can be monitored and enforced.
+*Managing Service Level Agreements (SLA) — It provides mechanisms for the definition and management of information-centric SLAs which can be monitored and enforced.
 *Enabling decision making —The architecture enables more consistent and efficient IT decision making that is linked to business needs. It does this because it is both flexible and extensible.
-*Addressing reusability aspects — Enforcing an EIA means that information assets are shared and reused, avoiding data duplication and thus reducing development, [[service]], and support costs.
+*Addressing reusability aspects — Enforcing an EIA means that information assets are shared and reused, avoiding data duplication and thus reducing development, service, and support costs.
-*Addressing data scope —The Information [[Reference Model]] used by the enterprise describes the scope of the used data and information supported by the EIA.
+*Addressing data scope —The Information Reference Model used by the enterprise describes the scope of the used data and information supported by the EIA.
-*Defining a technology [[strategy]] — It establishes the framework upon which the [[IT Strategy (Information Technology Strategy)|technology strategies]] adopted by the enterprise depend. In addition, it defines the set of principles that guide how an organization’s [[Information System (IS)|information systems]] and [[IT Infrastructure|technology infrastructure]] are engineered.
+*Defining a technology strategy — It establishes the framework upon which the technology strategies adopted by the enterprise depend. In addition, it defines the set of principles that guide how an organization’s information systems and technology infrastructure are engineered.
 '''Benefits of Enterprise Information Architecture (EIA)'''<ref>Benefits of Enterprise Information Architecture (EIA) [http://tdan.com/enterprise-information-architecture/4231 Paul Sturlis]</ref><br />
 Some benefits of building and maintaining an EIA are:
-*Facilitates assessment of packaged applications for “fit” within the organization (assuming a Corporate [[Data Model]] and [[Function Model]] is developed)
+*Facilitates assessment of packaged applications for “fit” within the organization (assuming a Corporate Data Model and Function Model is developed)
-*Eases [[Data Integration|integration of acquired companies’ data]] into our systems environment because the [data can be “mapped” into a “logical” Corporate Data [[Model]] (rather than directly into physical tables)
+*Eases [[Data Integration|integration of acquired companies’ data]] into our systems environment because the [data can be “mapped” into a “logical” Corporate Data Model (rather than directly into physical tables)
-*Facilitates development of a common language (and understanding) amongst our [[Line of Business (LOB)|lines of business]] because the models are developed from an enterprise-wide perspective
+*Facilitates development of a common language (and understanding) amongst our lines of business because the models are developed from an enterprise-wide perspective
 *Speeds the orientation process of new employees because they can quickly become acquainted with the business through analysis of selected portions of the models
-*Provides a “[[Roadmap|roadmap]]”, via the Corporate Data Model, for assessing existing (in-house built) operational [[Data Structure|data structures]] and planning for their re-engineering into an integrated set of structures
+*Provides a “roadmap”, via the Corporate Data Model, for assessing existing (in-house built) operational data structures and planning for their re-engineering into an integrated set of structures
 == See Also ==
-[[Enterprise Architecture|Enterprise Architecture]]

@@ Line 1: / Line 1: @@
-'''Enterprise Information Architecture (EIA)''' is the part of the [[Enterprise Architecture|enterprise architecture]] process that describes — through a set of requirements, principles and models — the current state, future state and guidance necessary to flexibly share and exchange information assets to achieve effective [[Organizational Change|enterprise change]].<ref>Definition of Enterprise Information Architecture (EIA) [https://www.gartner.com/it-glossary/enterprise-information-architecture Gartner]</ref>
+'''Enterprise Information [[Architecture]] (EIA)''' is the part of the [[Enterprise Architecture|enterprise architecture]] [[process]] that describes — through a set of requirements, principles and models — the current state, future state and guidance necessary to flexibly share and exchange information assets to achieve effective [[Organizational Change|enterprise change]].<ref>Definition of Enterprise [[Information Architecture]] (EIA) [https://www.gartner.com/it-glossary/enterprise-information-architecture Gartner]</ref>
 '''Explaining Enterprise Information Architecture (EIA)'''<ref>Explaining Enterprise Information Architecture (EIA) [http://www.ies.aust.com/papers/Architecture.html Clive Finkelstein]</ref><br />
-Linking an enterprise’s [[Strategic Planning|strategic plan]] with its enterprise [[Data Architecture|data architecture]], enterprise [[Application Architecture|application architecture]] and enterprise [[Information Technology Architecture|technical architecture]] results in enterprise information architecture. A well-documented architecture is a logical organization of information pertaining to the following corporate-level, enterprise-wide elements:
+Linking an enterprise’s [[Strategic Planning|strategic plan]] with its enterprise [[Data Architecture|data architecture]], enterprise [[Application Architecture|application architecture]] and enterprise [[Information Technology Architecture|technical architecture]] results in enterprise information architecture. A well-documented architecture is a logical [[organization]] of information pertaining to the following corporate-level, enterprise-wide elements:
 *Strategic [[Business Goals|goals]], [[Business Objective|objectives]], and [[Business Strategy|strategies]]
-*Business rules and measures
+*[[Business]] rules and measures
 *Information requirements
-*Application systems
+*[[Application]] systems
-*Relationships between applications and data elements
+*Relationships between applications and [[data]] elements
 *[[IT Infrastructure|Technology infrastructure]]
@@ Line 15: / Line 15: @@
 *Enable strategic information to be consistently and accurately derived from operational data
 *Promote data sharing, thus reducing data redundancy and reducing maintenance costs
-*Improve [[Productivity|productivity]] through component development, management and reuse
+*Improve [[Productivity|productivity]] through component development, [[management]] and reuse
 *Reduce [[Software Development Life Cycle (SDLC)|software development cycle]] time
@@ Line 34: / Line 34: @@
 *Gaining transparency —The information remains independent from application specifications, application implementations, and [[User Interface|user interfaces]]. It provides a transparency layer between the information and application domains.
 *Considering enterprise business requirements —The architecture takes into account the overall information needs of the entire enterprise and specific [[Line of Business (LOB)|LOBs]] or individual organizations.
-*Avoiding inconsistencies — It helps identify inconsistencies, conflicts, overlaps, and aps in the data and information, and offers a concept, framework, and methods to resolve this, and it is useful to select adequate solutions.
+*Avoiding inconsistencies — It helps identify inconsistencies, conflicts, overlaps, and aps in the data and information, and offers a concept, [[framework]], and methods to resolve this, and it is useful to select adequate solutions.
 *Managing [[Service Level Agreement (SLA)|Service Level Agreements (SLA)]] — It provides mechanisms for the definition and management of information-centric [[Service Level Agreement (SLA)|SLAs]] which can be monitored and enforced.
 *Enabling decision making —The architecture enables more consistent and efficient IT decision making that is linked to business needs. It does this because it is both flexible and extensible.
-*Addressing reusability aspects — Enforcing an EIA means that information assets are shared and reused, avoiding data duplication and thus reducing development, service, and support costs.
+*Addressing reusability aspects — Enforcing an EIA means that information assets are shared and reused, avoiding data duplication and thus reducing development, [[service]], and support costs.
 *Addressing data scope —The Information [[Reference Model]] used by the enterprise describes the scope of the used data and information supported by the EIA.
-*Defining a technology strategy — It establishes the framework upon which the [[IT Strategy (Information Technology Strategy)|technology strategies]] adopted by the enterprise depend. In addition, it defines the set of principles that guide how an organization’s [[Information System (IS)|information systems]] and [[IT Infrastructure|technology infrastructure]] are engineered.
+*Defining a technology [[strategy]] — It establishes the framework upon which the [[IT Strategy (Information Technology Strategy)|technology strategies]] adopted by the enterprise depend. In addition, it defines the set of principles that guide how an organization’s [[Information System (IS)|information systems]] and [[IT Infrastructure|technology infrastructure]] are engineered.
@@ Line 45: / Line 45: @@
 Some benefits of building and maintaining an EIA are:
 *Facilitates assessment of packaged applications for “fit” within the organization (assuming a Corporate [[Data Model]] and [[Function Model]] is developed)
-*Eases [[Data Integration|integration of acquired companies’ data]] into our systems environment because the [data can be “mapped” into a “logical” Corporate Data Model (rather than directly into physical tables)
+*Eases [[Data Integration|integration of acquired companies’ data]] into our systems environment because the [data can be “mapped” into a “logical” Corporate Data [[Model]] (rather than directly into physical tables)
 *Facilitates development of a common language (and understanding) amongst our [[Line of Business (LOB)|lines of business]] because the models are developed from an enterprise-wide perspective
 *Speeds the orientation process of new employees because they can quickly become acquainted with the business through analysis of selected portions of the models

@@ Line 3: / Line 3: @@
 '''Explaining Enterprise Information Architecture (EIA)'''<ref>Explaining Enterprise Information Architecture (EIA) [http://www.ies.aust.com/papers/Architecture.html Clive Finkelstein]</ref><br />
-Linking an enterprise’s [[Strategic Planning|strategic plan]] with its enterprise[[Data Architecture|data architecture]], enterprise [[Application Architecture|application architecture]] and enterprise [[Information Technology Architecture|technical architecture]] results in enterprise information architecture. A well-documented architecture is a logical organization of information pertaining to the following corporate-level, enterprise-wide elements:
+Linking an enterprise’s [[Strategic Planning|strategic plan]] with its enterprise [[Data Architecture|data architecture]], enterprise [[Application Architecture|application architecture]] and enterprise [[Information Technology Architecture|technical architecture]] results in enterprise information architecture. A well-documented architecture is a logical organization of information pertaining to the following corporate-level, enterprise-wide elements:
 *Strategic [[Business Goals|goals]], [[Business Objective|objectives]], and [[Business Strategy|strategies]]
 *Business rules and measures