Showing posts with label Information exchange matrix. Show all posts
Showing posts with label Information exchange matrix. Show all posts

April 25, 2008

Enterprise Information Architecture

We all know that enterprise architecture is a strategic-level synthesis of business and technology information to drive enhanced decision-making. To develop the EA we must build out the individual perspectives, such as performance, business, information, services, technology, security, and human capital. This blog focuses on one of those, enterprise information architecture.

Enterprise Information Architecture (EIA) is the strategic-level information architecture for the organization.

Note: Information refers to both information (processed data) and data.

GOAL:

The overall goal of EIA is to provide the right information to the right people anytime, anywhere.

MANDATE:

Legislative:

The federal mandate in law enforcement is the Intelligence Reform and Prevention Act (IRTPA) of 2004. Further, The Office of the Director of National Intelligence (ODNI) has developed the Information Sharing Environment (ISE) Implementation Plan in 2006 and the Department of Defense created the Net-centric Data Strategy in 2001.

Common Sense:

We need information to perform our mission/business function and processes: we can’t do without it! Moreover, in an information economy, information is power and information is currency.

PROCESS:

Developing the enterprise information architecture is an outgrowth of developing the business, data, and system models to understand the business processes, the information required to perform those, and the systems that serve up the information.

According to the Federal Enterprise Architecture, Data Reference Model, there are three parts to developing your information architecture.

  1. Data Descriptions—identify what your information needs are.
  2. Data Context—determining how the information is related.
  3. Data Sharing—developing the mechanisms for discovering and exchanging information.

Data Descriptions is the semantics and syntax. It involves developing your “data asset catalogue” and the metadata. This includes developing a lexicon or data dictionary with harmonized terms and schemas to describe them, as well as tagging the data. This helps define what the terms mean and identifies the rules for arranging them.

Data Context is the relationships. It includes categorizing the information using taxonomies and ontologies. It includes developing models, such as entity relationship diagrams (ERDs) to identify entities or information objects (and their attributes or properties) and associating them.

Data Sharing is the transactional processes. It entails the decomposition of information exchanges (in an Information Exchange Matrix or in a Information Exchange Package Description, IEPD) to determine the provider, the consumer, the trigger, the frequency, the media, the security, and so forth for each type of transaction. This phases also includes developing information repositories/registries, information sharing access agreements, and other mechanisms for sharing the information, such as portals, web services, enterprise service bus (ESB), and so on.

In the end, EIA is about transforming the organization: Culturally, from information hoarding to information sharing; from a business process perspective, optimizing information flows and usage, and in terms of governance, managing information as an enterprise asset.


Share/Save/Bookmark

September 7, 2007

Information Exchange Matrix and Enterprise Architecture

The Information Exchange Matrix (IEM) —a.k.a. OV-3 from the Department of Defense Architecture Framework (DODAF)—identifies the information exchanged between entities and the relevant attributes of that exchange such as source, destination, type of information, trigger for the exchange, media, frequency, quality (timeliness, completeness, etc.), quantity, and security.

Major characteristics include:

  • Information requirements: IEMs document information exchange requirements for the enterprise. They identify who is exchanging what information to whom, when, why, where and how. The IEM describes the flow of information in the organization.
  • Business Process Driven: IEMs are driven by business processes and activities and demonstrate what information is required to perform the mission-business functions of the organization.
  • Major Information Exchanges: IEMs are usually not comprehensive, but rather capture the major information flows that support the mission-business.

In User-centric EA, information exchange matrixes are one of the most critical products in the architecture. By knowing and understanding the information required by the enterprise (as identified in the IEM), architects are able to do the following:

  • Identify the systems that are providing information required by users.
  • Identify systems that are providing information that is not (or is no longer) required by users.
  • Determine which systems are redundant (i.e. meeting identical requirements).
  • Determine where there are system gaps (i.e. no system is providing the requisite information) .
  • Plan new technology solutions to meet new or changed information requirements.
  • Develop an environment conducive to information sharing by distinguishing which information exchanges must be on a need to know basis (secure) and where greater openness and sharing can occur.
  • Pinpoint what business processes should be reengineered or improved to better make use of available information and meet performance outcomes.

IEMs must have user participation. They cannot just be reversed engineered from existing systems, since that will only tell what information is currently being provided (and what information should be provided). Also, pulling the IEM information from systems does not address existing manual information exchanges that could very possibly be automated going forward.


Share/Save/Bookmark