A Treatise on Creating an Enterprise Architecture

8/10/2019 A Treatise on Creating an Enterprise Architecture

1/18

For internal use only Not for distribution

Shashi Prakash

(October 2014)

A Treatise on

Creating an Enterprise Information Architecture

2013 NET SERPENTS LLC ALL RIGHTS RESERVED


2/18


CONTENTS

2013 Net Serpents LLC All rights reserved

Definition

Business Drivers

EIA Capabilities

Creating the information Architecture

EIA in relation to Business and Technology Architecture

Deliverables and Approach


3/18


ENTERPRISE INFORMATION ARCHITECTURE DEFINITION (1/ 2)

Enterprise Information Architecture (EIA)is the part of the

enterprise architecture process that describes through a set ofrequirements, principles and models the current state, future state

and guidancenecessary to flexibly share and exchange informationassets to achieve effective enterprise change.Source: Gartner (http://www.gartner.com/it-glossary/enterprise-information-architecture

)

IA is the art and science of organizing information so that it is findable,manageable and useful. There is also a perspective from enterprise

architecture that views information architecture as an enterprise wide

activity that includes such aspects as data architecture, metadatamanagement and knowledge management(Stiglich, 2007).



4/18


Organization of information to support findability,

manageability and usefulnessfrom the infrastructural level to

the user interface level.Source: Downey, L., & Banerjee, S. (2011). Building an Information Architecture Checklist. Journal ofInformation Architecture. Vol. 2, No. 2. [Available at http://journalofia.org/volume2/issue2/03-downey/]


ENTERPRISE INFORMATION ARCHITECTURE DEFINITION (2/ 2)


5/18


BUSINESS DRIVERS (1/ 2)

etter management of information leads to

Agility ability to implement changes to data structures and analyze impact of changes

quickly

Conformed/Integrated data across the organization

Better Data Quality, Integrity and Security

Cost Savings

Better use of information can reduce overheads associated with information management

Better utilization of licenses on BI / Analytics & related technologies

Reduction in training costs

Reduction in support and maintenance costs



6/18


BUSINESS DRIVERS (2 /2)

Improving customer relationships

Better access to information promotes customer intimacy and maximizes therelationships value for both the customer and the organization

Higher Productivity

Through improved utilization of shared information resources

Efficient Operations Management

Improved decision making with better information availability

Better communication within the organization

Improved Regulatory Compliance

Through harmonization between business processes tied to regulatory data



7/18For internal use only Not for distribution

ESSENTIAL CAPABILITIES

! Identification and

Classification

!

Standardization

! Access & Storage

! Integration

! Governance & QC

Primary Components

Findability,

Manag

eability&

Usefulnes

s




EIA CAPABILITIES (1/ 5)


Classification

! Standardization

! Access & Storage

! Integration

! Governance & QC

Identification and Classification

Data identification and classification provides a framework for defining

and classifying organizational data based on its level of sensitivity,business value and criticality to the organization.

Benefit:

Promotes visibility across the enterprise

Common nomenclature reduces mis-interpretation

Creates an efficient framework for sharing data

Promotes harmony between business units

Promotes regulatory compliance

Use Case:

Establishing a taxonomy that categorises data into Master Data, MetaData, Transactional Data, Secure Data, Structured Data, Unstructured

Data, Planning Data, Setup & Design Data, Submission Data,

Analytics Data etc





Classification

! Standardization

! Access & Storage

! Integration

! Governance & QC

Standardization

Data standardization means converting and storing data in a manner

that promotes commonality and consistency in selection,definition, structure, format, transformation and transfer across

systems.

Benefit:

Makes data reliable

Makes data identifiable

Makes data understandable

Use Case:

Using CDISC (SDTM) standards during data capture reduces errorsduring submission and makes it understandable to FDA

Following the DIA reference model for electronic Trial Master Files

establishes a common understanding of data contained within trial

files






Classification

! Standardization

! Access & Storage

! Integration

! Governance & QC

Access & Storage

Data access and storage is the process of securing data from various

transactional systems, market vendors, business partners and internalentities into efficient, integrated data centric repositories well governed

with security

Benefit:

Improves application performance

Allows for devising security controls

Reduces time to implement data changes

Reduces down time for data migrationsAids the ETL process (Extract, Transform, Load)

Enables efficient data transport between systems

Use Case:

Creating a global data warehouse for storing data and granting access to

it based on business roles

Using an HDFS file system to store large datasets






Classification

! Standardization

! Access & Storage

! Integration

! Governance & QC

Integration

Data Integration is the implementation of business processes that

leverage interface technologies to source data from disparate systemsand provide that data consumption by downstream systems.

Benefit:

Reduces project integration costsImproves project time to market

Enables business agility through reuse

Reduces duplicate information stores

Improved visualization of data across business functions and units

Prevents duplicate processes

Use Case:

Using a Service Oriented Architecture for sharing data between businessunits

A hub and spoke model that collects data from multiple sources and

makes it available to multiple target systems






Classification

! Standardization

! Access & Storage

! Integration

! Governance & QC

Governance and Quality Control

Governance and quality control refer to the overall management of

data in order to serve the purpose of improving data quality,protecting sensitive data and enabling sharing of data across the

enterprise

Benefit:

Improves financial performance

Enables regulatory compliance

Protects data from unauthorized use

Improves efficiency of operations

Use Case:

Implementing Master Data Management and Meta DataManagementImplementing policies for data retention and archiving





CREATING THE INFORMATION ARCHITECTURE

(1/ 4)

BusinessArchitecture

Information Architecture

Technology Architecture

First This

Then This

This Last




CREATING THE INFORMATION ARCHITECTURE (2/ 4)




First This

Then This

This Last

Define Capabilities

Define the Process Flow Map Processes to

Applications



15/18


CREATING THE INFORMATION ARCHITECTURE (3/ 4)




First This

Then This

This Last

Define Capabilities


Applications

Create Process-Data Entity Matrix Create Application-Data Entity Matrix

Create Source-Target Map

Define and Classify Data

Define Data Standards

Define System of Record

Define governance process

Create data models/ canonicals



16/18


CREATING THE INFORMATION ARCHITECTURE (4/ 4 )




First This

Then This

This Last

Define Capabilities


Applications

Define H/W infrastructureDefine Software Platforms

Define Network Topology

Map data to Storage Devices


Create Process-Data Entity Matrix Create Application-Data Entity Matrix

Create Source-Target Map

Define and Classify Data

Define Data Standards

Define System of Record

Define governance process

Create data models/ canonicals


17/18


EIA IN RELATION TO BUSINESS TECHNOLOGY

ARCHITECTURE

Business architecture is

composed of Business

capabilities driving

business processes


comprising of Data

generated from business

applications and services


consisting of storagedevices, servers and

networks



18/18

DELIVERABLES AND APPROACH

Deliverables

Data Definition & Classification

Data Standards

System of Record

Governance process Process-Data Entity Matrix

Application-Data Entity Matrix

Source-Target Map

Data Models/ Canonicals

Define the

teams

Plan Meetings

Plan Workshops

Identify

Architecture

Tools

Create

Architecture

Deliverables


Approach

Documents

A Treatise on Creating an Enterprise Architecture