0% found this document useful (0 votes)
104 views

01a Introduction To EA

The document provides an introduction to enterprise architecture (EA). It discusses the benefits of EA such as aligning business and IT, improving productivity and agility. It also covers key EA concepts like business architecture, information architecture and application architecture.

Uploaded by

andhika_sotax
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
104 views

01a Introduction To EA

The document provides an introduction to enterprise architecture (EA). It discusses the benefits of EA such as aligning business and IT, improving productivity and agility. It also covers key EA concepts like business architecture, information architecture and application architecture.

Uploaded by

andhika_sotax
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 105

Introduction to Enterprise

Architecture(EA)
Presented to <name/s> (Arial Bold 18pt)
Presented
By <name/s>by theBold
(Arial Enterprise
18pt) Architect Office
04 April 2011 (Arial Bold 14pt)

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Training Software & License Key
The ARIS IT Designer
is solely meant for the
purpose of training and
evaluation.

Trainees are
responsible to uninstall
the software when the
trial license expires.

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
2
Agenda

1. EA Overview
2. WOG EA and EA Reference Models
3. Public sector case studies
4. Introduction to ARIS EA tools
5. Ensuring EA Success

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
3
1
EA Overview
• EA And Its benefits
• EA Implementation Approaches
• Business Architecture
• Information Architecture
• Application Architecture
• Technology Architecture

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
1.1 EA And Its Benefits

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
The Winchester House

• Home to the heiress of the Winchester


fortune
• Hired 147 builders (and 0 architects)
• No architectural blueprint for the mansion
was ever created
• 38 years of simultaneous building
• 2 basements, 6 kitchens, 40 bedrooms,
160 rooms

This is not a good example of EA.


© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Winchester House Oddities

950 doors?
65 doors to blank walls?
13 staircases built and abandoned
Etc.

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Rome was not built in 1 day…
Good Architecture takes time
and it is on-going

Established since 21st Apr 753BC


 Lasted a thousand years
 Well-linked road system that connected all parts
of the city and other cities
 Well-connected aqueduct system supplying water
to the entire city, including bath houses and public
toilets
 Well-distributed network of catacombs
underground

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Common Business Challenges
New processes and IT costs are up, whilst the
products take longer to number of successful IT
Company
implement projects decrease

New applications
developed by internal IT
don’t correspond to my
needs (E.g. quality, time, Business needs are not
cost) documented consistently

Business IT

Internal IT provides Internal systems are not


inadequate support (E.g. documented, too complex
quality, time, cost) and heterogeneous
Issues

Source: IDS-Scheer Designing and Improving Enterprise Architectures with ARIS IT Architect

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Possible Underlying Causes

Over-capacities and
seasonal fluctuations
Increasing
competition Increasing product
and cost pressure complexity

Faster Challenges Changing


time-to-market & trends business models

New technologies Internationalization,


(e.g. eBusiness, RFID) new markets
Changing business
environment
(M&As, co-operations)

Source: IDS-Scheer Designing and Improving Enterprise Architectures with ARIS IT Architect

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Definition of Enterprise Architecture
Enterprise Architecture (EA) is a map
which links

 Business functions;

 Relevant data standards;

 Common systems and


services; and

 Technologies

across agencies/departments in order


to achieve enterprise level or whole-of-
government goals

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Typical Agency With No Enterprise
Architecture Less productivity

Bad Customer Minimised agility


Customer Experience Government
Wasted funds

Agency X

Regulatory
Economic Processes are
Compliance &
Business Development
Enforcement not integrated
Processes
Industry
Development ... Anti-
Competition
Licence &
Permits
Inspections &
Audits

Systems are
Systems implemented to
ICT investments
...
meet specific
business process
are not
optimised
Industry needs rather than Licence & Permits
Development System cross-agency System
needs – resulting
in silos and
Data
...
fragmented
systems
Data is not being
shared

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
12
EA Benefits

Business benefits
• Helps organization achieve its business strategy
• Faster time to market for new innovations and capabilities
• More consistent business processes and information across
business units
• More reliability and security, less risk

IT benefits
• Better traceability of IT costs
• Lower IT costs – design, buy, operate, support, change
• Faster design and development
• Less complexity
• Less IT risk
Source: TOGAF Standard Courseware V9 Edition

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
1.2 EA Implementation
Approaches

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
EA Frameworks

Commercial Government
 Zachmann  FEAF
 IAF (CapGemini)  MAGENTA
 CLEAR (Atos Origin)

Consortia Defence
 TOGAF  DODAF
 EABOK  MODAF
Source: Wikipedia, Impression of Enterprise Architecture Frameworks evolution  AGATE
(1987-2003)
© 2011 IDA Singapore. RESTRICTED
All Rights Reserved.
Example - TOGAF Architecture
Development Method

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Example - Methodology For Agency
Enterprise Architecture (MAGENTA)
Provides a step-by-step EA development guide

Part 1: Methodology

• Step-by-step instruction oriented

Part 2: Practitioner Guide

• Tips and practical advice


• Referenced to specific phase step(s)
• Frequently asked questions

Part 3: Case Study

• Provides a real life scenario


© 2011 IDA Singapore. RESTRICTED
All Rights Reserved.
EA Can Come in Different Sizes
By architecture area (Business, Information, Application and
Technology)
• Full architecture
• By Area
By organization structure
• Across organization
• Specific department/group
• Region/Geography
By stakeholders’ concerns
• Expenditure tracking
• Customers’ experience
Focusing on specific business track or issue
• Specific focus → Display value → Expand
• Most popular approach adopted by organisations
• Illustrate with two case studies on the following slides

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
1.3 Business Architecture



BPM
Description of BA
Objectives of BA
• Challenges without BA
• BA Overview
• BA Development Process
• Benefits of BA

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Conceptual Context of
Enterprise Architecture Management
> Holistic Enterprise Architecture Management is based on frameworks &
processes, needs powerful tools and supporting organizational
structures.

EA Management
BPM

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
20
Business Process and BPM

• A business process is a matching sequence


of activities in a company with the purpose of
producing output (product/service).

• BPM is a comprehensive management approach to


align organisation processes to organisation strategy,
to analyze, optimize and implement best-in-class
processes

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
21
Managing your organisation by managing
your processes
BPM is the gearbox that
makes the business
operate
Lean / Organisation
Six Sigma Design
Organisational
Restructuring Risk & Services Technologies
Compliance
Management

Business BPM
Continuity IT Infrastructure
Performance
Applications
Management
Information
/ Data
IT
Integration Process
Improvement

Process = Transparency >> Measure >> Control >> Improvement


Business = Customer Satisfaction >> Competitive Advantage >> Growth

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Key Principles of BPM Excellence
Alignment to Organisation Strategy
Process Governance
Process Structure
Performance Management
Design & Documentation
Implementation & Change Management
IT Alignment
Monitoring
Continuous Improvement

These principles, underpinned by leadership and culture, have to be


applied to the management of the process lifecycle

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
23
Benefits of BPM
Continuous Increased
process improvement process efficiency

Reduced
Flexibility for
process costs
organisational change

Performance Monitoring Alignment between


business and IT

Competitive advantages BPM


by unique processes Complexity reduction through
process standardisation

Process transparency Increase process


oriented thinking

Control over business


Management of Risk operations and
improvement
© 2011 IDA Singapore. RESTRICTED
All Rights Reserved.
Description of BA
1. Map of the Business that consist of the following:
a. Strategies,
b. Organisation KPIs,
c. Capabilities of the Business,
d. Processes, and
e. How the above interacts to execute the strategies to meet its
KPIs
2. It may also capture other business requirements in
terms of competition, regulatory requirements and other
elements in the business’s ecosystem.
3. Forms the baseline for the IT Foundation

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
25
Objectives of BA
1. Identifies key goals and KPIs that drive performance

2. Executes organization’s strategy to meet KPIs

3. Identify business requirements to stay competitive in market

4. Satisfies customers’ and partners’ needs

5. Meet regulatory requirements

6. To develop a Target Business Architecture, based on the business


principles, business goals, and strategic drivers

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
26
Challenges without BA
1. Unable to identify appropriate business processes to
receive IT investments

2. No holistic view of applications that are supporting


business processes

3. Lack of knowledge of business processes that are


distributed across supporting applications

4. Unable to identify business processes that needs to be


managed and could be redesigned
© 2011 IDA Singapore. RESTRICTED
All Rights Reserved.
27
BA Overview
Line of Business (LOB) Model – Includes all Lines of
Level 1 Business either at a government-wide level or at an agency
Business level (Value-added Chain Diagram)
Domain
The Agency LOB Model should be aligned with the
Singapore Government – Business Reference Model
(SG-BRM)

Business Function Model – Includes all


Business Functions under a Line of
Level 2 Business (Value-added Chain Diagram)
Business
Function The lowest level business function object
will represent individual business
processes

Business Process Model – Includes the individual


steps within a business process and the supporting
Level 3 components such as business units, information
Business objects, and supporting systems (Event-driven Process
Process …
Chain)

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
28
BA Development Process

Architecture Vision Business Architecture

Input Process Output

1. Revisit organizational vision, mission & areas of excellence


2. Reconcile strategies & strategic objectives
3. Reconcile/define customer value proposition
4. Build strategy map & identify strategic themes
5. Define operating model
6. Decompose key business processes iteratively
7. Design & improve target business processes
8. Identify touch-points from business processes to: technology (as-is &
to-be), application (as-is & to-be) & information (as-is & to-be)
9. Identify business level questions addressed

Source: Enterprise Architecture Practitioner Program, ISS

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
29
Some benefits of BA
1. Allows organizations to identify redundant, fragmented
business processes.

2. Allows more informed decision on investments for


business value

3. Allows easy implementation of best practices

4. Allows an organisation to be more agile for market


changes

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
30
1.4 Information Architecture



Description of IA
Objectives of IA
Challenges without IA
• IA Overview
• IA Development Process
• Benefits of IA

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Business needs drive
information Requirements

Description of IA
• Identifies and defines the major kinds of data / information
that support the lines of business / business functions
across the organisation and its value chain

Data Information Knowledge Wisdom

Raw facts on durable Meaningful transformation Body of truth and State of being wise
medium of data principles

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
32
Objectives of IA
1. Identifies data gaps that affect business operations

2. Ensure a “single source of data”

3. Ensures data traceability and data life cycle


management

4. Facilitates impact analysis arising from business


changes

Source: Enterprise Architecture Practitioner Program, ISS

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
33
Challenges without IA
• Confusion and misunderstanding due to differences in
data definitions, interpretations and procedures

• Data exchange/sharing problems due to inconsistent


formats or incomplete data

• Data access, reuse, accuracy, confidentiality and integrity


problems due to lack of data management policies,
guidelines and procedures

• Storage and maintenance problems due to data


duplication
© 2011 IDA Singapore. RESTRICTED
All Rights Reserved.
34
IA Overview
Business
User data SLA information process
information
Material data Contract data
Information Object Inventory
Order data Session data Company data Master data
– Includes all information
objects (IE Data Model)
Level 1 Sales Order
Management
data
configuration
Employee data
Pre-owned car
data

Information Change
management Person data IT system data Customer data
data

Domain
Credit
Scanner data Credit application
Ranking

Data Entity Inventory – Car offer data


Credit increase
proposal
Solvency
Logical Data Model –
Includes both structured Vehicle offer ID
Includes the data entities and
data entities and subset of the relevant
geospatial data entities attributes. It also highlights
Level 2 (IE Data Model) the inter-relationship
Data Entity between data entities (IE
Data Model)

Data Entity Model – Includes all


Level 3 data entity components (eERM
Data attribute allocation diagram)
Attributes

Data Format Model – Data Codification Data Validation Model –


Address Type
Code

Level 4 Includes the data


A

B
APT BLK

WITHOUT APT BLK

Model – Includes the Includes the data


Data
X REVERSE OF APT BLK & STR NAME

format for a generic C OVERSEAS ADDRESS


data code values for a validation rules for a data
Format/ data structured format,
D

E
PRIVATED FLATS WITH APT BLK

C/O APT BLK


data attribute, e.g. M - attribute (Data Validation)
Data e.g. Address, Email, F

Q
C/O WITHOUT APT BLK

QUARTER ADDRESS
Male, F - Female, U –
Codification Telephone (Data I ISLAND ADDRESS
Undefined (Data
Format) Codification)

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
35
IA Development Process
• Ensures that all required information for fulfilling
business needs are available, reliable and usable
• Ensures alignment between business and information

Input Process Output


For each business process /
Business Architecture function, identify the key Information
(E.g. Lines of information, data entities,
attributes and relationship Architecture
businesses, business
functions, business between the entities required to
processes) fulfil the business processes /
functions

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
36
Benefits of IA
1. Improved quality of information
• Uniform semantic understanding of business objects (“common language”)
• Unique assignment of responsible staff to business objects

2. Increased data visibility


• Visibility regarding creation, modification, and use of information and filtering of redundant information

3. Increased process efficiency


• Inter-departmental understanding of the wider business context
• Increased effectiveness of data used for business planning and execution
• Development of enterprise-wide IT solutions instead of optimized variants specific to individual
departments

4. Harmonization of Terminology, Formats and Codifications

5. Basis for security and authorization concepts, as well as SOX compliance

6. Foundation for assessing service quality

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
37
1.5 Application Architecture



Description of AA
Objectives of AA
Challenges without AA
• AA Overview
• AA Development Process
• Benefits of AA

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Description of AA
1. Defines the major types of application capabilities that
are required to manage information and support
business functions of the organization

2. Applications are logical capabilities that manage


information in IA and support business functions in BA

3. (Technology-neutral)

Source: Enterprise Architecture Practitioner Program, ISS

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
39
Objectives of AA
1. Identify opportunities for improvements
a. Creation of common services
b. Consolidation of applications of similar functions
c. Simplification of overly complex applications

2. To provide greater agility and flexibility in response to


changing business demands

Source: Enterprise Architecture Practitioner Program, ISS

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
40
Challenges of AA
No overview of:
1. Applications that use multiple technologies for
enablement

2. Organization-wide applications and department-only


applications

3. Applications without vendor support

4. Applications that need integration capabilities both


internally and externally
Source: Enterprise Architecture Practitioner Program, ISS

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
41
AA Overview
Application Domain – Includes the Application
Level 1 Domains used to classify applications (Application
Application System Type Diagram)
Domain

Application Inventory – Includes systems that are


owned or used (Application System Type Diagram)
Level 2
Application

Application Application Application


Module Context Model – Interface
Inventory – Includes system Model –
Level 3 Includes the
modules of a
information, with
regards to
Includes the
interfaces
Application
system system’s owner, between
Details (Application support, applications
System Type technology (Program Flow
Diagram) components Chart)
used, etc.
(Access
Diagram)
© 2011 IDA Singapore. RESTRICTED
All Rights Reserved.
42
AA Development Process

BA (BRM) and IA (DRM) AA, gaps &


opportunities

Input Process Output

1. Identify application(s)
required to support each
business function
2. Perform gaps analysis

Source: Enterprise Architecture Practitioner Program, ISS

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
43
Benefits of AA
1. Facilitates the alignment of application with business
processes
2. Facilitates reuse and integration across business
processes
3. Identifies and builds application services and
components that could be added or modified easily
without negative impact
4. Identifies potential consolidation of existing systems with
duplicate functionalities

Source: Enterprise Architecture Practitioner Program, ISS

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
44
1.6 Technology Architecture



Description of TA
Objectives of TA
Challenges without TA
• TA Overview
• TA Development Process
• Benefits of TA

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Description of TA
1. Defines the major types of technologies required to
provide a platform for applications that are managing
information and supporting enterprise business
functions

2. Realize IA and AA by providing technical capabilities

3. Address non-functional requirements (e.g. scalability,


reliability, security, etc)

Source: Enterprise Architecture Practitioner Program, ISS

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
46
Objectives of TA
1. Map IA and AA into technologies and standards

2. Address stakeholders’ non-functional requirements

3. Address QoS issues that are not fully addressed in IA


and AA

4. Provide a framework where technologies / products are


managed to support IA and AA, and indirectly BA

Source: Enterprise Architecture Practitioner Program, ISS

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
47
Challenges without TA
No overview of:
1. Technologies that are used by most business processes

2. Technologies that are used by most applications

3. Organization-wide and department-only technologies

4. Technologies that are supported by multiple vendors

Source: Enterprise Architecture Practitioner Program, ISS

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
48
TA Overview
Level 1 Technology Domain
Technology – Includes the Technology
Domain Technology Domains, Category – Includes
usually adapted from the classification of
SG-TRM (Structuring technology
Model) components (IT
Architecture Mapping)

Level 2 Technology
Catalogue –
Technology
Includes
/ Product technologies and
products that can be
selected for use (IT
Technology Architecture Matrix)
Inventory – Includes
technologies and
products being used
(IT Architecture
Matrix)

Logical Server
Infrastructure Model – Instance Model –
Level 3 Includes the infrastructure Includes the logical
implementation surrounding server instances in a
Infrastructure
an application (Network physical server
Diagram) (Network Diagram)

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
49
TA Development Process

1. IA and AA
2. QoS requirements
3. Information and
application gaps TA, gaps &
opportunities

Input Process Output

1. Define TRM
2. Define principles,
technology/product standards &
best practices
3. Perform gap analysis

Source: Enterprise Architecture Practitioner Program, ISS

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
50
Benefits of TA
1. Divides & conquers technical & organizational complexities
2. Serves as a construction blue-print and ensures consistency across
systems
3. Provides a basic framework for major change initiatives
4. Increases in the predictability of the architecture
5. Minimise effort for agency to comply to IM8B Policy on Technical
Architecture
6. To have an inventory of products and technologies allowed for
implementation within an agency
• Prevents technologies between systems to become too diversified to support
7. Promotes chances to:
• Aggregate demand
• Analyse for vendor reliance

Source: EA Awareness Seminar: Technical Architecture 101, Maryland Department of Budget & Management

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
51
2 Whole-Of-Government EA
and EA Reference Models

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
eGov 2015 Masterplan
T1: Co-creating for T2: Connecting for T3: Catalysing WoG
Higher Value Active Participation Transformation

Supports Enhanced Citizen & Private


Sector Engagements Directly Supports

Enables

Connected Whole-of- Government EA


Government
“…IDA will design the next generation ICT infrastructure for the whole-of-government. This infrastructure will
facilitate mass collaboration, shared systems, services and processes under a Whole-of-Government
Enterprise Architecture.”
Keynote Speech by Mr Peter Ho, Former Head Civil Service & PS(MFA)
Singapore at iGOV Global

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Benefits To Agencies

1. Can capture, store and analyse all EA Information that serves as a


single source of truth

 Direct access to EA Reference Models and MAGENTA methodology which


will be incorporated into the tool

 Are assured that their collected information will be in a format with semantics
that are consistent with other Central EA Tool users

 Need not configure the EA software for use

 Will enjoy the benefits of any improvements (e.g. Newly created scripts or
reports, changes to methodology, new features)

2. Can enjoy better EA product pricing

 Need not invest in setting up the infrastructure (e.g. Hardware, Network,


All Rights Reserved. Operating System, Database, Backup, Anti-Virus, Firewall)
© 2011 IDA Singapore. RESTRICTED
Singapore Government Enterprise
Architecture (SGEA) Reference Models

Business Data Application Technology


Reference Reference Reference Reference
Model Model Model Model

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
2.1 Business Reference
Model

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Business Reference Model (BRM) –
Provides organised view and common
terminology of Government business

Business 2 Business Areas – Represents the


INCREASED GRANULARITY AND DETAIL

Areas highest level description of the business


operations of the Government

33 Lines of Business – These Lines of


Lines of Business give more detail on the
Business services and products the Government
provides to its stakeholders

137 Business Functions – Describes


Business the specific activities that Agencies
perform within each Line of Business
Functions

See – http://intranet.igov.gov.sg/GovernanceandManagement/PoliciesAndStandards/SGEA/Index.htm

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Business Reference Model (BRM)
2. Line of Business 1. Business Area

No LOB/Business Description
Function

1 Family Involves activities which create an environment conducive to


3. Business Function Development family formation and the strengthening of family ties. This
includes administering marriage, promoting the formation of
family, promote the development of children and youth, and
ensuring the welfare of the young and old are protected.

1.1 Promoting Involves activities that promote and administer


marriage marriages.

1.2 Development & Involves activities that ensure protection of the welfare
protection of and the development of children and youth
children and
© 2011 IDA Singapore. youth RESTRICTED
All Rights Reserved.
Agencies vs. Business Functions Matrix

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
59
How does the BRM help?

> At a government-wide level


 Identification of priority business
functions, resulting in inter-agency
collaboration

> At an agency level


 As a basis to identify collaboration
opportunities with other agencies ◄

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
60
2.2 Data Reference
Model

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Data Reference Model (DRM) – Defines the
data standards for effective data exchange
Person

Unique
Principal Abbreviated HanyuPinyin Address
Identification ID Type Code
Name Name Name
Number

Highest
1. Data Entity
Country of Nationality
Birth Date Gender Code Dialect Code Education
Birth Code Code
Code

Death
Marital Status
Code
Race Code Religion Code Death Date Certificate
Number
2. Data Element
...
3. Codification

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
How does the DRM help?

> At a government-wide level


 Facilitates data interoperability amongst
agencies

> At an agency level


 Identifies data sources for reuse – instead
of collecting the same data again

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
63
2.3 Application
Reference Model

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Application Reference Model (ARM) –
provides a portfolio of reusable ICT
resources

System Service Component

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Example: Shared Systems

Lines of Business
Shared Systems

Corporate Planning Information Management Project & Logistics


Finance HR Public Communications
& Development and Consulting Management

BLISS MCPS PM2S eventshub@sg GeBIZ SGMS

SAS@Gov NFS@Gov PRAISE eventshub@sg

PM2S PaC@Gov TRAISI

VOG

Shared System

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Example: Shared Service Components
Shared SC Category
Service Components

Establishment Land
Security Payment People Information
Information Information

Inquiry of Businesses’
SingPass eNETS Credit People Data Service
Status Web Service

eNETS Debit
EASY

FlexiPay Shared SC

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
How does the ARM help?

> At a government-wide level

 Provides a view of systems and service


components across the public sector – reducing
the potential for duplication

> At an agency level

 Facilitates the identification of reusable systems


/ service components – instead of having to
develop these from scratch ◄

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
68
2.4 Technology Reference Model

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Singapore Government – (ICT)
Technology Reference Model or “SG-
TRM”
Previously known as the Service-

Internet & Intranet


Data Management
Application

Wide Technical Architecture

Distributed Environment
Collaboration &
Workflow

Management
(SWTA)

Security
Middleware

Platform Architecture
Principles
Provides the standards that
Network
Domain
enable inter-agency Architecture

interoperability 9 Domain Architectures Design Principles

Technology
Categories

Technology
Standards
Consists of Interoperability
Standards
 Framework – Organized structure
Product Register
to describe the content of the TRM
Related Links to
 Architecture Principles – a set of Other Domains

Best Practices
statements to articulate the Structure of a Domain
Architecture Technology
strategic intent and guide TRM Watch

...
development See –
 Domain Architectures – Building http://intranet.igov.gov.sg/GovernanceandManagement/PoliciesAndSt
andards/eWAVE.htm
blocks or logical technology
groupings
© 2011 IDA Singapore. RESTRICTED
All Rights Reserved.
Domain Architecture Content
Architecture Architecture Principles
Principles E.g. Standard User Interfaces and Access Protocols

Domain Design Principles - Derived from Architecture


Architecture Principles. They guide the evaluation, selection,
design, construction, and implementation of the
Design Principles domain and its elements
Example:
Technology
Categories Network design should be:
Technology a. Scalable to meet increasing demands of
Standards
bandwidth
Interoperability
Standards b. Adaptive to cater for new features and
functionalities
Product Register
Justification
Related Links to • Network forms the underlying infrastructure for
Other Domains
other ICT elements such as Platform, Applications,
etc. It is a critical and integral part of the
Best Practices
Singapore Government’s business functions and
Technology
processes.
Watch
• Usage of open standards and protocols in the
...

design reduces time to respond to the increasing


© 2011 IDA Singapore. bandwidth needs of applications.
RESTRICTED
All Rights Reserved.
71
Domain Architecture Content
Architecture
Principles

Domain
Architecture

Design Principles

Technology
Categories
Technology Categories - Technologies
governed by the domain
Technology
Standards Example – Network Domain Architecture:
Interoperability • LAN Switches
Standards
• LAN Routers
Product Register • Wireless LAN
Related Links to • Wide Area Network and Protocols
Other Domains
• Remote Access Networking
Best Practices
• Structured Cabling System
Technology • Free Space Optics
Watch
...

• IP Telephony
© 2011 IDA Singapore. RESTRICTED
All Rights Reserved.
72
Domain Architecture Content
Architecture
Principles

Domain
Architecture

Design Principles
Technology Standards - International standards
Technology
and Industry standards (E.g. Java EE 5)
Categories

Technology
SG-TRM Standards

Standards Interoperability
Standards Interoperability Standards - Standards
mandatory for Inter-agency Interoperability (E.g.
Product Register LDAP 3.0)

Related Links to
Other Domains

Best Practices Product Register - Products that are used


within the public sector and also in the industry
Technology (E.g. IBM WebSphere Application Server 6.1)
Watch
...

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
73
Technology Standards

Format
S/N Standard Description Reference Status
X Standard Standard Reference authority Not Supported, Transitional,
Name Description and URL Supported, Strategic, Emerging

Status Implication to existing Systems Implication to new Systems


Not Should migrate to ones in strategic or Should refrain from using
Supported supported status as soon as possible
Transitional Should plan to migrate to ones in Should refrain from using unless there
strategic or supported status is no other alternative
Supported Acceptable to continue use Acceptable to use
Strategic Supported and recommended to Supported and recommended to use
continue use
Emerging Unlikely to be widely in use Should use in production systems only
after a technical assessment is
conducted

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Example: Technology Standards

S/N Standard Description Reference Status


1 JDBC 2.0 Java JDBC Supported
and Database Technology
above Connectivity www.java.sun.
com/products/
jdbc

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Interoperability Standards

Covers the standards and other requirements that are


mandatory for inter-agency interoperability

Example

Data Access Middleware


 LDAP and Oracle SQLNet/Net8 are mandatory inter-agency
Interoperability standards

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
76
Product Register

Format
Product
Descriptio No New
Domain Product Launch Support Type &
Technology n, Vendor Feature License
S/N Architect & Date (DD- End License Usage and Review
Category and Date (DD- Type
ure Version MM-YYYY) Date Type
Reference MM-YYYY)

X SG-TRM Technology Product Product Date when Date when Date Commer List of Government agencies
technology Category Name & Description, the product the product when the cial or Open and Private Sector
domain within the List of Vendor and was will not have product Open Source Organisations that have
such as technology the Reference generally any new will no Source License used the product
Internet & domain product URL available features longer be Reviews from
Intranet versions being made supporte Government agencies
available d by the and 3rd parties (e.g.
(e.g. only vendor / product features,
security organisat strengths and
patches ion weaknesses, overall
provided) experience)

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Example: Product Register

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Domain Architecture Content
Architecture
Principles

Domain
Architecture

Related Links to Other Domains - Interfaces


Design Principles with other domains
Technology
Categories

Technology
Standards
Best Practices - Guidelines & practical advice
based on experience & research (E.g. Best
Interoperability practices for evaluation and selection of
Standards
Application Servers)
Product Register

Related Links to
Other Domains
Technology Watch - New technologies requiring
research or evaluation
Best Practices

Technology
Watch
...

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
79
3 Public Sector Case Studies

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Case Study 1 – Ministry of Defence
Problem
 Disparate IT systems supporting the
Building and Infrastructure (B&I)
business
 Duplicate data in multiple repositories
 Slow and error-prone manual report
generation

Building and Infrastructure (B&I) line-of-


business transformation using EA

See – http://intranet.igov.gov.sg/NR/rdonlyres/F7EF5F5A-10D6-466E-8716-
7C8CE2DCAF52/15144/20100802SingaporeGovernmentEAGuidebook1.pdf
© 2011 IDA Singapore. RESTRICTED
All Rights Reserved.
81
Implementation approach
Prioritize and select business function

Develop target business architecture

Develop conceptual solution

Implement solution

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
82
Business benefits derived by MINDEF
Estimated cost avoidance of $1.5mil from the re-use of 30
business process blueprints in logistics system
 Based on $50k minimal cost saving per re-use

Estimated annual cost savings of $8mil on the next


generation Land & Building management system
 IT automation, cost avoidance, savings

ROI of 18.07% over three years

Achieved true business-driven SOA

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
83
Case Study 2 – Singapore Health Services
Problem
 Current healthcare policies, procedures,
processes and systems are designed for
acute care, while a growing dominant
group of diseases point to chronic
conditions, creating a mismatch between
supply and demand

An EA was necessitated to complete a


transformation of business to
 Provide and improve care for people with
long‐term conditions
 Manage chronic diseases using a fresh
approach in thinking
See – http://intranet.igov.gov.sg/NR/rdonlyres/F7EF5F5A-10D6-466E-8716-
7C8CE2DCAF52/15144/20100802SingaporeGovernmentEAGuidebook1.pdf
© 2011 IDA Singapore. RESTRICTED
All Rights Reserved.
84
Implementation approach of SingHealth

Establish scope and strategic intent

Develop current and target business architecture

Develop current and target IT architecture

Analyse gaps and identify opportunities

Develop transition plan

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
85
Business benefits of EA by SingHealth
National healthcare services
 Predictive, preventive, personalized, chronic care, life‐long and coordinated management
 Patient centric, evidence-based standardised care through integrated service channels
 Shared interoperable, accessible, secure and private guiding clinical decisions at the point of care
Sponsors of care
 Targeted services across a broader healthcare spectrum of needs and delivery channels
Healthcare providers
 Faster adoption of good practices and methods
 Differentiated value focused on higher value services
 Financial incentives for better outcomes and for following evidence based standards
Healthcare professionals
 Value‐based services, aligned to accountabilities across preventive, acute and chronic care
 Rapid adoption of new knowledge and approaches through the use of clinical decision support tools
 Supported by electronic systems with comprehensive patient information and advanced clinical decision support
 Collaborative partnerships
 Standardised and evidence‐based care tailored to individual patients To citizens and patients
Citizens and patients
 Maximize value from health services
 Patient empowerment and self‐management
Government policy makers & regulators
 Balance short and long term needs
 Data availability and transparency to support chronic disease research

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
86
4 Introduction to ARIS EA
Tools

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
The ARIS Platform

Ms. Rosenfeld Ms. Maier


Technical departments
 Architecture  Project
 Staff in charge
solution and design manager

Architekturschicht Architekturelement
Umfasst

Business process-specific
Umfasst

components and services Management Primary Support


processes processes processes

Standard technology & basic Office


solutions e-Mail Collaboration
applications

Business Document and System and


Business
process content application
Intelligence
management management management
Umfasst

Enterprise
Applications Workflow
Integration

AIM (Access
Databases Data Directory
and Identity
(DBMS) warehouse services
Management)

Infrastructure Operating Frontend Web Network


systems Technologies technology protocols
Umfasst

Worldwide communication
Hardware Storage Network
server solutions components

Development Frameworks
Development Methodology Programming
Umfasst

and software
tools development languages
technologies

Framework, architectural planning Analysis, optimization, and of process knowledge to all


and analysis administration employees

• Central Repository • Publish contents in Central


• Models Repository to a Web Portal
• Objects • Attributes environment for enterprise-
• Connections wide communication
• Analysis using Reports,
Queries, Comparisons
ARIS
Business Server

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Central EA Tool – Architecture
EA Server Infrastructure

Central EA Repository
Central EA Server Central EA Publisher

SGNET

EA Clients

...
Enterprise Architect Enterprise Architect / Reader of Business / System Owner/
Business Analyst IT Information Project Manager
Central EA Team Agency 1 Agency n

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
89
User Roles & EA Client Components
Legend
1 Model
EA Server Infrastructure
2 Analyse
3 Present

Central EA Repository
Central EA Server Central EA Publisher

SGNET

IT Architect 1 IT Designer EA Clients 3 Business Publisher User


2

...
Enterprise Architect Enterprise Architect / Reader of Business / System Owner/
Business Analyst IT Information Project Manager
Central EA Team Agency 1 Agency n

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
90
Model using IT Architect/Designer

3
2
5
1 6

4
4

1. Which task is executed?


2. Who is responsible for this task?
3. Which system supports this business activity?
4. Which data is input/output for this task?
5. How long is it required to complete this task?
6. Which system capabilities are required?
© 2011 IDA Singapore. RESTRICTED
All Rights Reserved.
Using Modelled Business Processes
to Aid Analysis
2
1

….

Business Process 1 Business Process n

Model business Use modelled business processes


process to generate matrices for analysis
© 2011 IDA Singapore. RESTRICTED
All Rights Reserved.
92
Analysis Example (1 of 2)

Finding
1. Customers need to submit the same information multiple times for different processes
2. There are multiple customer touch points – potential area to improve customer satisfaction
© 2011 IDA Singapore. RESTRICTED
All Rights Reserved.
93
Analysis Example (2 of 2)

Finding
1. There are 4 applications that
manipulate the same set of
customer data – indicating
potential duplication of
functionality across different
applications

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
94
IT Architect/Designer
Capabilities & Benefits
• Integration of IT architecture and process
management in a repository
• Creation of a single inventory of systems and
technologies within the enterprise
• Specification and documentation of the
organization’s IT standards
• Reduced complexity and costs of the IT
environment
• Facilitates IT environment evolution.
• In-built functionalities to aid detection of system
redundancy

Source: www.ids-scheer.com

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Present using Business Publisher

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Presentation Example

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
97
Business Publisher
Capabilities & Benefits
• Dynamic on-demand publishing of business process
knowledge or IT environments
• Efficient change management ensures lasting
process quality, even when changes are frequent
• Dynamic, work group-oriented and role-based
delivery of content
• Fast search of information
• Seamless integration into enterprise portals (single
sign-on, link to existing user administration, etc.)
• User-friendly administration directory
• Operational integration with Office products and
document management systems (such as, Lotus
Notes, SAP, etc.)

Source:
© 2011 IDA www.ids-scheer.com
Singapore. RESTRICTED
All Rights Reserved.
Benefits of using EA Tools

> Minimize Effort Costs


 Higher initial costs compared to EVA (Excel, Visio, Access) suite – tool acquisition and learning
curve
 Consequent costs of long-term effort to create and maintain models in are unbearable

> Maximize Information Gain


 With increasing complexity and volume of EA data, modeling tool brings consistent and useful
information due to interlinked objects and diagrams, while EVA suite* becomes to be messy
and unusable.
Effort to maintain the information

Ability to use the information


Excel/ Visio Modelling Tool

Access/ Visio

Access/ Visio
Excel/ Visio

Modelling Tool

Complexity/Volume Complexity/Volume
• Source: www.PragmaticEA.com

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
5 Ensuring EA Success

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Common difficulties cited in EA projects
• “Connecting EA to business strategies is difficult”

• “EA is not given enough status & expectations”

• “Insufficient commitment and compliance from stakeholders”

• “EA is not a generally accepted concept in daily business activities


(EA Awareness)”

• “Financial and political issues”

• “Setting up an architecture took longer than expected”

Source: ARIS Expert Paper - Why two thirds of Enterprise Architecture projects fail

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Considerations for EA Success
• Set clear, enterprise-wide EA objectives

• EA objectives management ( Don’t boil the ocean!)

• Set up EA Governance

• EA Awareness among C-levels & communications

• Business to be sufficiently involved in EA practice

Source: ARIS Expert Paper - Why two thirds of Enterprise Architecture projects fail

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
Value of EA to Agencies
a. Facilitates the
identification of
business innovations &
opportunities
b. Highlights the
impact from business
process change to
associated business
units & ICT systems

c. Highlights the
impact from ICT f. Highlights the data
systems to critical being used or
business processes needed, allowing for
(e.g. Failure of ICT standardisation and
Applications) optimisation. To
create a single view
d. Facilitate the e. Highlights redundant of truth.
identification of systems – reducing
services that can be overall cost of ICT, and
integrated for better optimise resource
customer experience utilisation.
and increased
operational
efficiencies. g. Highlights the ICT components required
to support ICT Applications, allowing for
demand aggregation, technical co-
existence and resource optimisation.

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.
IDA EA Office Offerings
2. Develop Agency’s EA
Competencies (e.g. EA Tool
Training, EA Knowledge 5. Alignment to Central EA
Transfer) Standards & Practices
(e.g. Reference Models,
1. Initiate EA for Agency MAGENTA Methodology,
Modelling Standards &
Notations, Facilitate
Compliance to Policy on
Technical Architecture,
and Policy on Data
Management)

3. Provision of EA Tools at a 4. Structured Analysis &


subsidised rate Recommendation (E.g. Identify
© 2011 IDA Singapore. RESTRICTED opportunities for inter-Division /
All Rights Reserved. Agency collaboration, automation)
Thank You
ida_ea_secy@ida.gov.sg

© 2011 IDA Singapore. RESTRICTED


All Rights Reserved.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy