Developing & Reviewing IT MAster Plan

7/30/2019 Developing & Reviewing IT MAster Plan

1/32

Developing & ReviewingIT Masterplan

SHARING VISIONSesi 4


2/32

SHARING VISION

IT MASTERPLAN AND REVIEW2

Dengan IT Planning yang benar,investasi TI akan menghasilkan

dampak yang efektif untuk perusahaan!


3/32

SHARING VISION


Enterprise Architecture (IT Architecture)

The C4ISR ArchitectureFramework

Common Object Request

Broker Architecture (CORBA)

Practical Guide to FederalEnterprise Architecture

Federal Enterprise ArchitectureFramework (FEAF)

ISO/IEC 14252 (IEEE Std1003.0)

NCR Enterprise ArchitectureFramework

ISO Reference Model for OpenDistributed Processing (RM-ODP)

SPIRIT Platform Blueprint

Technical ArchitectureFramework for InformationManagement (TAFIM)

TOGUF

Zachman Framework

IT Architecture Toolkit

Enterprise InformationArchitecture


4/32

SHARING VISION


Pengembangan IT Masterplanmenggunakan IT Architecture Toolkit

Function

Platform

Models Inventory

People &Process

Data

StandardPrinciples

IT Architecture FrameworkIT Architecture Framework

Function

Platform

Models Inventory

People &Process

Data

StandardPrinciples


People

Process

Buy-In

MetricsProjects

Implementation FrameworkImplementation Framework

People

Process

Buy-In

MetricsProjects


Target State

Current State

AnalysisDescription

Business FrameworkBusiness Framework

Target State

Current State

AnalysisDescription


DefinitionDefinition

MetricsMetrics

MeasurementMeasurement

BusinessSecurity

Requirement

IT Strategy

IT Master Plan

IT Implementation Plan IT Security Cycle

ISMS

IT SecurityStrategy

ADIM


5/32

SHARING VISION


Steps

1. Business Framework (Connecting Architecture to theBusiness)

1.1 Describing The Business Current State

1.2 Analyzing the Business Current State1.3 Constructing the Business Target State

1.4 Analyzing the Business Target State (Gaps andOpportunities)

2. IT Framework

2.1 Define a principles

2.2 Build the Architecture Models

2.3 Inventory

2.4 Standard

3. Implementation Framework

3.1 Translate Architecture into Projects3.2 Review

Function

Platform

Models Inventory

People &Process

Data

StandardPrinciples


Function

Platform

Models Inventory

People &Process

Data

StandardPrinciples


People

Process

Buy-In

Metrics

Projects


People

Process

Buy-In

Metrics

Projects


Target State

Current State

AnalysisDescription


Target State

Current State

AnalysisDescription



6/32

SHARING VISION



Function

Platform

Models Inventory

People &Process

Data

StandardPrinciples


Function

Platform

Models Inventory

People &Process

Data

StandardPrinciples


People

Process

Buy-In

Metrics

Projects


People

Process

Buy-In

Metrics

Projects


Target State

Current State

AnalysisDescription


Target State

Current State

AnalysisDescription



MetricsMetrics


BusinessSecurity

Requirement

IT Strategy

IT Master Plan

IT Implementation PlanIT Security Cycle

ISMS

IT SecurityStrategy

ADIM


7/32

SHARING VISION


IT Architecture Framework

Business

Target

State

Translate

Business

Target

State to

Principles

Architecture

Repository

Model Current

IT State

Model Target

IT State

Create IT

Inventory

Create

Standards


8/32

SHARING VISION


IT Framework Data:

Fakta tentang bisnis

Function:

Operasi penting untuk

menjalankan bisnis

Platform:

Teknologi yang

memungkinkan

pembuatan danpenggunaan data dan

fungsi

People

Pengguna danpenyedia data, fungsi,

dan operator teknologi.

Function

Platform

Models Inventory

People &

Process

Data

StandardPrinciples


9/32

SHARING VISION


IT Architecture Framework:

1. Defining Principles

Principlesis the abstraction of the business target state to form

guidelines for IT decision making.

Rules of thumb in defining principles:1. Translate the business target state statement to a statement intent for IT

2. KISS, Keep it short and sweet

3. Use principles to communicate the basic tenets the company holds to be

universally true

4. Use principles to impose business contraints on the models and standards to

be developed

5. A set of principles should be contained to one page

Function

Platform

Models Inventory

People &Process

Data

StandardPrinciples

SHARING VISION


10/32

SHARING VISION



2. Defining Principles (CASE: GaneshaCD Co.)

GaneshaCD Co. Statement of Goals:

1. Learn more about our customer to

better market to retain and satisfy

them

2. Increase growth rate and revenue

from music sales, and maintain

growth in publications

3. Leverage the combined

music/publications

4. Eliminate unnecassary expense

5. Become more open to change6. Invest in employee retention

7. Leverage technology

GaneshaCD Co. Statement of Goals:

1. Learn more about our customer to

better market to retain and satisfy

them

2. Increase growth rate and revenue

from music sales, and maintain

growth in publications

3. Leverage the combined

music/publications

4. Eliminate unnecassary expense

5. Become more open to change6. Invest in employee retention

7. Leverage technology

Data Principle

Customer information is critical to

the business. (1)

Function Principle

Functions will be built or bought as

reusable component. (4, 5)

Platform Principle

Vendor viability is as important as

product viability (4, 7)

People Principle

Employee training is a non-

negotiable investment (6)

Data Principle

Customer information is critical to

the business. (1)

Function Principle

Functions will be built or bought as

reusable component. (4, 5)

Platform Principle

Vendor viability is as important as

product viability (4, 7)

People Principle

Employee training is a non-

negotiable investment (6)

SHARING VISION


11/32

SHARING VISION



2. Define IT Architecture Model

IT Architecture Model:

The graphical representation of the business view of data, functions, technology,people, and the relationship and/or interactions between them.

Its the development of the detailed plans.

We will start with high-level model and continue to develop more detailed

model.

The most detailed plan will become the blueprint for implementation.

Setting the context:

Who is the audience?

What will the content include?

What planning horizon will be used?

What part of IT the model need to describe? How formal does the documentation need to be?

Function

Platform

Models Inventory

People &Process

Data

StandardPrinciples

SHARING VISION


12/32

SHARING VISION



The Rules for IT Modelling

1. Agree on a set of standard components

2. Use a standard representation scheme

3. Set a scope

4. Determine the level of detail

Level 0: conceptual, one page model of key component and their

relationship.

Level 1: more detail, specific view of part of level 0.

Level n: more detail, specific view of part of level n-1.

Presentation level: for executive purpose

5. Define the state to be modeled current state, target state, end-of-year state, during migration?

6. Define the environment

execution environment, developmet environment, operation environment

Function

Platform

Models Inventory

People &Process

Data

StandardPrinciples

SHARING VISION


13/32

SHARING VISION



Toolkit Standard Architecture Modeling Notations

REFDATA/

Platform

DATABASE/Platform

DATA WAREHOUSE/Platform

DATA MART/Platform

ARCHITECTURE SERVICE-COMMUNICATION BETWEEN COMPONENTSPlatform

EXTERALINTERFACE

Platform

Broker /Hub

PORTAL

www

EMPLOYEE/SYSTEM

USERCUSTOMER

DATA FLOW &

DIRECTION

EXISTING orMECHANIZED

PLANNED orMANUAL

DUPLICATE

BUSINESSFUNCTION/

Platform

Process

SHARING VISION


14/32

SHARING VISION



Case of ITAF Modeling: IT Current State Modeling

Most current state legacy models we have seen focus on boxes (server,

network, etc) rather on business applications, data, interface, and services.

At least developing level 0 of current state provides many values.

Information Capital assessment provide inputs for current state modelling

A how-to steps

1. Identify major components that provide/use data, e.g. customer.

2. Define data flow each component receives or sources, e.g. payment.

3. Define what operation a function performs on each data flow (a verb-noun),

e.g. validate payment.4. Designate stored data, e.g. account recievable.

5. Determine where services exist between components.

SHARING VISION

d1


15/32

SHARING VISION



Case of ITAF Modeling: IT Current State Modeling

BOOKS INPRINT

BOOKCATALOG

RETAILSTORE

ACCOUNTSRECEIVABLE

ReplenishInventory

/ VendorOrder

Vendor

StaffEmployee

Set Bus.Targets

Book.Mgmt.

ManageInventory

Order

Control

DistributeStock

Sell

Books

ValidatePayment

BillCustomers

PayEmployee

Reconcile$

Ware-House

RetailStore

MailCenter

User Interface

Candidates PAYROLL

EMPLOYEECUSTOMER

VENDOR

WAREHOUSE

Order

Pay-ment

ACCOUNTSPAYABLE

BOOK

INVENTORY

Item, $

Shipment

Book

Info

Picks

Low StockCapacity

AllocatedStock

StockOrder

Payment

Order

Payment

Employee /Job

VendorPayment

$$$

EmployeePayment

CustomerPayment

BillAmt.

Bill

Item, $

Order

Stock,Location

ItemInfo

PayVendors

Employee

Hours

11

2

5

3

64

GaneshaCD

Co.


16/32

SHARING VISION


17/32

SHARING VISION



Case of ITAF Modeling: IT Target State Modeling

IT target state is a transalation of business target state

How-to steps:

1. Extract the opportunities identified from business traget state analysis. E.g.:

Opportunity:Develop offers for combos of book/music products,

make offers online.

2. Translate the opportunity to IT components. E.g.: GaneshaCD Co. & Bookseller product data store, a combo offer data store

A function that creates/updates Offers

A function that accept online payment

Website access to Offers Modification/addition of user interface

3. Transfer the identified components to a Level 0 target state model

4. Refine the Level 0 model to Level 1 n until the desired level of detail

achieved

SHARING VISION


18/32

SHARING VISION



Case of ITAF Modeling: IT Target State Modeling

Ganesh

aCD

Co.

Key DecisionSupport Data

KeyOperationalData

ArchitectureService

KeyFunctions

ExternalInteraction

TrackResults

DevelopPlan &Budget

AssessCustomer/ ProductViability

UpdateFinancial

Plan

Pay Staff& VendorExpense

FixCustomerProblem

Send Bill& AcceptCustomerPayment

5.0

Track

InventoryOrders

Shipping

SellOffers

Target

CustomerWith

Offers

Hire,TrainStaff

CUSTOMEROFFER

HISTORY

EMPLOYEE

JOBSKILL

PRODUCT

OFFER

INVENTORY

SALESCHANNEL CUSTOMER

ORDER

VENDORAP /

EXPENSE

A / RINCOME

PLAN /BUDGET

REPLICATION / DISTRIBUTION SERVICES

ACCESS SERVICES

EAI PROCESS MANAGEMENT / FLOW

CUSTOMER RELATIONSHIP MANAGEMENT / USER INTERFACE

ElectronicTitles

Vendor

5

4

3

6

1

2

EXTRACT

Payment Order

HelpService Rep

Titles

2

SHARING VISION


19/32

SHARING VISION



3. IT Inventory

The rules of thumb:

Set a scope, e.g.:

A data inventory table for key data stores

An application (function) inventory

An infrastructrute (platform) inventory

A skills inventory listing employee

Determine level of detail

Inclusivity, properties, model or item, brief commercial info

Define the state (current or target state), some suggestion:

Data, application (function), and people inventory: current state Platform inventory: current and target state

Define the environment

Execution, development, and operation environment

Agree on format

Function

Platform

Models Inventory

People &Process

Data

StandardPrinciples

SHARING VISION


20/32



3. IT Inventory (Case: GaneshaCD Co.)

DATA AREA FILE NAME /ANNUALEXPENSE

ACRONYM VOLUME SIZE TECHNOLOGY

Product Books in Print

$0.7 Mil.

BIP 5,675,800 Properietary

Product BooksellerPublication

Catalog

PUBCAT 1,625,400 SQL Server

Product PreferredRecordings

$0.1 Mil.

PRCRDZ 200,300 MS Access

SHARING VISION


21/32



3. IT Standards

Standard(in here) is the agreed-to or corporate set of

key data entities, functions (applications), technologies,

or process, including their names, definition, ordescription.

Setting standards serve as another step in translatingthe business view for developers.

Function

Platform

Models Inventory

People &Process

Data

StandardPrinciples

SHARING VISION


22/32



3. IT Standards

Rules of thumb:Establish ownership

Clear ownership will assure that standards are consistent

Define the state Usually standards are for target state

Define the environment

Recommendation: execution operation developmentDefine the level of detail

Use the Level n target state

Function

Platform

Models Inventory

People &Process

Data

StandardPrinciples

SHARING VISION


23/32



3. IT Standards

Data standard

For each key data, we have to standardize the identifiers

Some good identifiers attribute:

Unique, non-intelligent, under our control

Function/application standards:

Includes the name, meaning/description, type/priority, candidate for migration to

target

Platform/Technology standards:

Operating System, Database platform, Database architecture, User Interface,

Hardware standards,

People standards

For each strategic job families related to each strategic internal process, define

knowledge and skill required.

SHARING VISION


24/32



How to select technology/platform standards?

1. Identify the type of components (OS, DBMS, Programming Language,

Middleware, etc.)

2. Define & describe selection criteria (fail-safe, performance, reliability,

scalability, etc)

3. Define the measurement scale.

1. E.g. Behaviorally anchored rating scale (BARS):1. 4 = provides complete capability

2. 3 = provides most (75% or more) capability

3. 2 = provides some (35% 75%) capability

4. 1 = provides little (35% or less) capability

5. 0 = provides no capability

4. Rate each component and criteria using BAR scale

5. Summarize findings for management

SHARING VISION


25/32


Putting it together!

PRINCIPLES

1. Our customerinformation is our mostvaluable asset.

2. Key information will beavailable anytime,anywhere

PRINCIPLES

1. Our customerinformation is our mostvaluable asset.

2. Key information will beavailable anytime,anywhere

CUSTOMERCUSTOMER

MODELS

SellOffers

SellOffers

CustomerOrder DB

SQL;Access $14

M mtce230 gb total

HQ; Retailstores

CustomerBill DB

Oracle$4.5M mtce

70 gb Denver

CustomerMaster

DB2 $2 Mmtce

25 gb HQ

STANDARDS

A customer is any person or groupwho has purchased a product fromGaneshaCD Co. within the last 5yearsand is identified byMaster Customer Card Number

STANDARDS

A customer is any person or groupwho has purchased a product fromGaneshaCD Co. within the last 5yearsand is identified by

Master Customer Card Number

SHARING VISION


26/32



Function

Platform

Models Inventory

People &Process

Data

StandardPrinciples


Function

Platform

Models Inventory

People &Process

Data

StandardPrinciples


People

Process

Buy-In

Metrics

Projects


People

Process

Buy-In

Metrics

Projects


Target State

Current State

AnalysisDescription


Target State

Current State

AnalysisDescription



MetricsMetrics


BusinessSecurity

Requirement

IT Strategy

IT Master Plan

IT Implementation Plan

IT Security Cycle

ISMS

IT SecurityStrategy

ADIM

SHARING VISION


27/32


3. Implementation Framework

Right people for the right jobP e o p l e

Ensuring process complianceP r o c e s s

Lets do it!!Buy-in

Measuring effectivenessMetrics

Selecting & defining projectsProjects

SHARING VISION


28/32


Implementation Framework:

Budget Allocation Survey

90% expense tahunan untuk operasional dan perawatan

10% expense untuk investasi baru yang bebas inilah yang membentuk

strategic investment

Kaplan & Norton mengusulkan 5% - 15% untuk investasi baru information

capital dari seluruh total pengeluaran IT.

Total Informational Capital Spending ( how much?) :

1.0%Retail

1.7%Manufacturing7.0%Financial

4.1%All Industries

Level of Spending (IT/Revenue)

Total Information

Capital Spending

Source: Peter Weil l & Mariane Broadbent Research

Harvard Business School 2000

SHARING VISION


29/32


Implementation Framework:

Budget Allocation Survey

Information Capital Typical Source of Value Typical Budget Mix

TransformationalApplications

Improved speed to market or premiumpricing results in higher revenue per

employee

14 %

Analytical Application

Provides Information to manage the

enterprise. Particularly important ininformation-intense industries (customer

information, product quality)

16%

Transaction Applications Primary focus is on cost reduction 12%

IT InfrastructureCreates business flexibility and integration,fosters cross-selling, new product

introduction

58%

Source: Peter Weil l & Mariane Broadbent Research

Harvard Business School 2000

SHARING VISION


30/32


Reviewing Masterplan

Jadwal review:

Pada setiap tahapan

pengembangan masterplan

Setelah development:

Reguler, misalnya 1 tahun

sekali

Ad-hoc, jika ada kondisi yangdianggap penting

Penyebab perubahan masterplan:

Ada kelemahan

Perubahan kondisi organisasi

Perubahan peta bisnis

CurrentState

TargetState

Principles

Modelling

Inventory

StandardsProjects

Metrics

Buy-in

Process

People

SHARING VISION


31/32


Penutup

IT Masterplan dimulai dengan proses analisis bisnis (current state dan

target state), sehingga dijamin align dengan tujuan perusahaan dan

mendukung target perusahaan

IT Masterplan adalah sesuatu yang sangat penting untuk dikembangkan

dalam suatu perusahaan dan akan menjadi acuan pengembangan dan

penerapan IT

IT Architecture Toolkit mencakup : Business Framework, IT Architecture

Framework, dan Implementation Framework, sehingga menjamin integrasi

yang lengkap mulai aligning dengan proses bisnis, pengembangan

arsitektur dan implementasinya.

SHARING VISION


32/32


t e r imate r ima kas ihkas ih !!

Merci bienArigatooMatur NuwunHatur Nuhun

Matur se KelangkongSyukronKheili MamnunDanke

Developing & Reviewing IT MAster Plan

Documents

Transcript of Developing & Reviewing IT MAster Plan