Enterprise Architecture IRD

Enterprise Technology Architecture

Monday, April 10, 2023

ETA at IR - GOVIS.ppt

1

Inland Revenue Enterprise Technology Architecture

GOVIS May 2005




2

Agenda Background ETA – What is it? ETA Challenges and Goals SOE – Standard Operating Environment Architecture Management Framework Lessons Learnt




3

Background

ETA Project was established in early 2003 and completed in September 2003.– Derived from IR’s Technology Strategy.

Based on TOGAF, with appropriate adjustments– To suit IR needs– Engaged IBM expertise to assist in establishing work

products, and enhance IR/Method.

Overall Enterprise Architecture established – 3-year horizon– Key capabilities of Enterprise Application Integration (EAI),

and Identity and Access Management System (IAMS), acquired and deployed.




4

ETA – What is it?

“A framework for making IT investment and design decisions in support of business objectives.” (IBM)

ETA Vision is to establish a technology environment which strives to:

– be responsive to the business.– maximise the use of information technology components.– ensure informed and consistent technology decision making.

ETA consists of the following:– Architecture Drivers which describe what the architecture must do to

support the business.– A set of IT Principles that define the underlying general rules to

deploy technology resources across the organisation.– Reference Architectures which provide a design of how logical

components can fit together for a particular technology.– Standard Operating Environment (SOE) specification which provides

product standards governing the use of hardware, software and application systems.

– Architecture Management Framework (AMF) – defining the processes, roles and responsibilities to manage and implement ETA.




5

StrategyStrategy

IT Infrastructure

• Network

• Sys Mangmt

• App Develop

Infr

astr

. Ap

plic

tn.

Bu

s. A

pp

licat

ion

IT Architecture

Bu

sin

ess

Pro

cess

es

Bu

sin

ess

Eve

nts

Info

rmat

ion

Mo

del

Ro

les

/ Lo

cati

on

s

Business Architecture

Business Strategy IT Strategy

Bu

sin

ess

Cap

abili

ties

Bu

sin

ess

Mo

del

Bu

sin

ess

Sce

nar

ios

Ind

ust

ry M

od

els

“Enterprise Architecture” (EA)Planning

Delivery “Programme Office” (PO)

Pro

ject

Solution Design Architecture

Pro

ject

Pro

ject

Pro

ject

Pro

ject

Pro

ject

Pro

ject

TOGAF

IR’s Enterprise Architecture needs to be aligned with its Business & IT

Strategies in order to put in place an effective ETA.




6

ETA’s Architecture Framework is used as a starting point. The ETA focus, at this time, is on the Information Technology Architecture &

associated Governance.

Enterprise Architecture

Project Office

Corporate StrategyD

eliv

ery

Pla

nn

ing

Str

ateg

y

GovernanceGovernance

Business StrategyBusiness Strategy Information Technology StrategyInformation Technology Strategy


ProjectProject ProjectProject ProjectProject ProjectProject ProjectProject ProjectProject

Business ArchitectureBusiness Architecture Information Technology ArchitectureInformation Technology Architecture

Applications ArchitectureApplications Architecture

Technical ArchitectureTechnical Architecture

Data ArchitectureData Architecture


Co

ntr

ol

Co

ntr

ol

Tax AgentsTax Agents ConsumerConsumer

Hu

ma

n R

es

ou

rce

sH

um

an

Re

so

urc

es

Str

ate

gic

Op

era

tio

ns

Str

ate

gic

Op

era

tio

ns

Business ServicesBusiness Services

Finance and InvestmentsFinance and Investments




7

Level 1 of the ETA Architecture Framework, requires a Conceptual Architecture Description for each layer, known as an “Architecture Domain”

The tools, methods and processes used in the development and maintenance of applications

Data MgtServicesData MgtServices

PlatformServicesPlatformServices

NetworkServicesNetworkServices


PresentationServices

PresentationServices

SoftwareServicesSoftwareServices

Management of data independent of the processes that create or use it, maintained indefinitely,and shared among many processes

The underlying hardware and software used to host applications and other services

The voice and data communications infrastructure for the distributed computing environment

The set of principles, guidelines and processes used to manage the IT portfolio and resources

A class of interface software that provides users with access to functions and data

Info

rmat

ion

Sec

uri

ty S

ervi

ces

Sys

tem

s an

d N

etw

ork

Man

agem

ent

Ser

vice

s

Software that creates uniform mechanisms for application integration across diverse network and platform technologiesIntegrationServices

IntegrationServices

BusinessApplication

Services

BusinessApplication

Services

A class of software that is used to create and maintain business data

BusinessIntelligence

Services

BusinessIntelligence

Services

A class of software that provides managers with tools to monitor and evaluate the

performance of the business

ProductivityServices

ProductivityServices

DataServices

DataServices

Applications that provide a variety of personal or team productivity operations

Structured and unstructured data created and maintained by business applications

- such as Integration Services




8

IBM 6611

Regional Con'tor (1) Devt Env (1)

Corp Srv + Syst Mgmt (1)

IBM Netfinity 3500, Display, Quality Printer, ProPrinter

IBM PC 300, Touch Display, 4717-mag rdr

To FinancialInstitution

Data Server (1)

Cust W/S (12)

OS/2 WarpDB2/2 ClientIconAuthor rt

Front-end Proc

OS/2 WarpPCOMM, NTS/2LAN ServerDB2/2 serverDDCS/2RXR/2

OS/2 2.1 CICS/2PCOMM, NTS/2 DB2/2 ClientIconAuthor rt

LocalArea

Network

NOTE: Models andDASD sizes are to be confirmed later

MVS/ESADB/2CICS/ESAVTAM

LocalArea

Network

Partitioned IBM S/390 (1)

E1 to E10

13, 14, D1 -D5 (copies),D6 & D7

IBM Netfinity 3500, Display, Quality Printer, ProPrinter

N/w, Ptr & Lan Mgt server (1)

OS/2 Warp,PCOMM, NTS/2LAN ServerDB2/2 serverDDCS/2RXR/2

E15 - E17,D8, I1 to I12

IBM PC 300, Display, 4717-3 mag rdr/wrtr

Clerk W/S (5)

E1 to E12

Note: The two store servers provide mutual take-over services, and therefore are rsponsible for backup copies of a[ppropriate process and data groups

Store (400)

Regional HQ (10)

HQ Con'tor (1)

Basic IBM PC 300

Auth Switch (1)

E15-E17, 18, 19D1 -D5 (masters)D9 - D11, I15-I19

Central HQ (1)

IBM 3745

IBM 6611Reference Architecture (EAI)S

yste

ms

and

Net

wor

k S

ervi

ces

Sys

tem

s an

d N

etw

ork

Ser

vice

s

Info

rmat

ion

Sec

urity

Ser

vice

s In

form

atio

n S

ecur

ity S

ervi

ces

Integration Services

Data Management Services

Platform Services

Network Services


Business ArchitectureBusiness Architecture

Software Engineering Services

Productivity Services

Presentation Services

Business ApplicationsBusiness Applications Business IntelligenceBusiness Intelligence

Component Model

Operational Model

Data ServicesData Services

Reference Architecture (such as one for EAI) requires components from several “Architecture Domains” of the ETA Architecture Framework (including

components from Integration Services)




9

Architecture Management Framework

Business Architecture

ENTEPRISE TECHNICAL ARCHITECTURE (ETA) METHODOLOGY

Business

Strategy

IT Strategy Standard Operating Environment

Standard Operating Environment

Evaluation & Selection

Framework

Evaluation & Selection

Framework

Technology Model – Architecture Domains

Technology Model – Architecture Domains

Transition Plan

Transition Plan

Current Technology Environment Assessment

Current Technology Environment Assessment

Gap Assessment

Gap AssessmentETA Vision

ETA Vision

ETA Drivers

ETA Drivers

ETA Principles

ETA Principles

Functional Requirements

Functional Requirements

Component Model

Component Model

Non –Functional Requirements


Operational Model

Operational Model

Reference Architecture

ScenariosScenarios

ProjectsProjects

Context DiagramContext Diagram

Component Model

Component Model



Class/Type Diagram

Class/Type Diagram

Solutions Outline

Scenarios & Use Cases

Scenarios & Use Cases

The Enterprise Architecture (EA) Development Methodology followed by the ETA project, best describes the way in which the Project Deliverables were

produced.




10

Common Corporate Components

Unique Business

Unit Infrastructure

Unique Business

Unit Infrastructure

Unique Business

Unit Infrastructure

Shared Components

Infrastructure Project (eg. EAI)

ETA Focus

Building a Framework for Reuse




11

ETA Challenges and Goals




12

ETA Challenges

Increasing speed to market – ability to quickly react to change.

Moving away from build to re-use to buy – embrace open industry standards.

Aligning business and IT – making informed business decisions.

Facilitating greater accessibility of IR services – diverse mix of channels that are highly available.

Lowering cost of ownership of IR systems – Systems consolidation, rationalisation and standardisation.




13

ETA Goals

Virtual Organisation – providing location independence for IR staff

Systems Consolidation – providing standardised and simplified IT infrastructure

Channel Independence – providing consistent user experience across multiple channels

High Availability – providing standards and techniques to deliver reliable and highly accessible customer services

Single Identity – providing consistent security treatment for internal users and external customers

Time Horizon – 3 years (05/06 to 07/08)




14

SOE – Standard Operating Environment

Platform




15

SOE Decision Criteria

Core Existing assets that we want to re-use (e.g. maintenance).

Emerging Existing and future Assets that are going to feature in our strategy going forward (e.g. new development).

Declining Existing assets that will not be invested in or re-used, and, are ultimately candidates for de-commissioning.

Special Case

Assets that are not Core or Emerging, but granted special dispensation (i.e. Apple Mac’s for publishing).

Each asset will be categorised with these decision criteria…




16

SOE Evaluation Process

Current Assessment

Analysis - Standards

• Base-lining• Categorisation (TOGAF)

• SOE decision criteria• Options Development• Options Analysis• Preferred Options

Analysis -Validation

Gap & Impact Assessment

• Market Capability / Alignment

• Determine extent of change• Identify actions:

• Consolidation• Rationalisation• De-commission• Simplification

IT Infrastructure

Initiatives

SOE

ArchitectureDrivers Overarching IT Principles

Market Trends, other

organisations




17

Future SOE Goals

Simplification Improved utilisation Reduced Cost of Ownership Minimised development effort of integrating new

technologies Simplified technology decision making




18

Platform tiers - diagram




19

Platform SOE Decisions

Greater impact at mid tier where there is high proliferation of platforms

Edge

User Interface Network Mid Enterprise Platform Intel - core

Sun - declining Intel - emerging Sun -declining

Intel - emerging Sun - core

Sun - core Unisys NX Clearpath - core

Operating System

MS Windows desktop -core Solaris - declining

Linux - emerging Solaris - declining

Linux -emerging Solaris -core Netware - declining Windows server 2000 -declining Windows server NT - declining

Solaris – core Unisys MCP-AS - core

Examples Desktop PCs IR-file SUN web server s

LARS, CHRIS Evolve-IT

Mainframe DataWarehouse




20





21

ETA Governance Model

ETA Governance Model has two objectives, namely:

– The effective ongoing development and maintenance of the ETA as a whole.

– The enforcement of architecture compliance within Inland Revenue.




22


Project Governance – PSCs supported by Project Office

Project Project Project

Corporate Governance - SMT

Business Strategy – The Way Forward

Technology Strategy

Technology Governance - ITGB

ETA Governance - ETA

Business Representation

PSG

Competency Centres

ETA

Enterprise Technical Architecture –Application, Data and Infrastructure

Solution Design Architects

Project Governance – PSCs supported by Project Office

Project Project Project

Corporate Governance - SMT

Business Strategy – The Way Forward

Technology Strategy

Technology Governance - ITGB

ETA Governance - ETA

Business Representation

PSG

Competency Centres

ETA

Enterprise Technical Architecture –Application, Data and Infrastructure

Solution Design Architects




23

ETA within the Architecture Management Framework

Projects

Directions, Strategies

The Way Forward and Technology Strategy

Alignment

Information Technology Governance Board

BUSINESS

-business direction-requirements-prioritisation

ETA

-technical direction-technology trends

- standards

IT STRATEGY

-technology strategic direction

DELIVERY

-design-dev/acquisition- implementation- maintenance

-support

Project support, funding, methodologies

Standards, models, SOE, Reference Architectures

Projects



Alignment


BUSINESS


ETA


- standards

IT STRATEGY


DELIVERY


-support



Projects



Alignment


BUSINESS


ETA


- standards

IT STRATEGY


DELIVERY


-support

BUSINESS


ETA


- standards

IT STRATEGY


DELIVERY


-support






24

Implications

Project life cycle will be different Project initiation – ETA delivers architected solutions outline

up front Project design – ETA assures architecture compliance Project completion – ETA adds re-usable components to

asset base

Project funding model will support both business and technology benefits (ie. projects’ contribution to technology asset base)




25

Lessons Learnt




26

Lessons (being) Learnt

ETA is more effective when focusing on the future – difficult to influence projects already commenced.

– ETA & Project goals are in conflict – balancing “enterprise goodness” goals against delivery goals of time and cost.

Need to be better connected with key parts of the organisation– Strategic Planning, Finance, Risk & Assurance– Project Governance groups

Need to watch out for “short termism” or “quick wins”– Short term always looks cheaper– ETA benefits are always in the long term.

Standards enforcement is difficult– Must demonstrate business value – why the standard is important– Guidelines to projects on how they can conform – shift in emphasis to Vendors– “Take away the choice” from projects – provide a standards based

infrastructure

Sound and top-down Governance is key

Documents

Enterprise Architecture IRD