ZEXPRESS Future EA Vision

Aligning Enterprise Architecture For

ZEXPRESS
presented by Architect Advisor
Enterprise Architect @ Zexpress
[email protected]

August 2008 October 2008

 Background
In the face of major global competition, one US based package delivery company,
ZExpress, based in the Atlanta, has decided to acquire and merge with a
number of European and Asian delivery companies. They wish to create a major
force in the distribution and logistics markets and use their brand name and
marketing capability, recognized as the best in the industry, to create a worldwide
conglomerate of distribution companies.
Similarly Pacific Rim Logistics and Home and Colonial Carriers had decided to merge to
form a single new United Package Express for exactly the same reason. The major
driver for these market mergers is the existence of a market leader, Global Express
Delivery who threatens the survival of these smaller companies.
The characteristics of the market leader are, Totally global coverage. Ability either directly
or through local partnerships to deliver a package to any location on earth.
Sophisticated tracking capabilities so that the sender and recipient can track a parcel
from origin to destination. Dedicated airline and trucking fleet. Broad market
presence. ZExpress has proposed to the newly forming United Package Express that
they merge together to become one distribution and logistics conglomerate and use
the ZExpress marketing reach. United Package Express are very keen to do this but
their plans and investment are already underway to merge with each other.

August 2008 October 2008

 Background
The management and shareholders have agreed to merge the two businesses and
leverage the best of each.

YOU ARE ASSIGNED AS AN ENTERPRISE ARCHITECT TO deliver an Enterprise

Architecture Strategy for ZEXPRESS.

The REST OF this work product explain a recommended approach based on TOGAF.

Enjoy the rest of the document on your free time.

August 2008 October 2008

 ZEPRESS Need of EA Programs

Current State Need of Future EA

- ZEXPRESS is the future of a global
merge by consolidating three Establish a common vision of the future
shared by business and information units
companies. of ZEXPRESS.
- Each parent companies of ZEXPRESS Establish guidance in the selection,
has tremendous investment in IT to creation and implementation of solutions
serve the current business needs driven by business requirements of
ZEXPRESS.
- Reusability of diverse assets, obtain Establish a means to control growing
highest level of cost cutting, complexities of technology by setting
establish highest level of customer enterprise-wide, leveragable, standards
satisfaction to serve combined for information technology.
Assurance to policy-makers of ZEXPRESS
customer base, be competitive in that IT division of ZEXPRESS are creating
dynamic market condition against new systems and migrating old systems
the major global competitor are the through a consistent process to be
common business objectives of new competitive, reduction of cost and
business IT agility
EA program

August 2008 October 2008

Proposed ZEXPRESS EA Solution

ZEXRRESS EA is not a one-time The new EA model have the following sub
event, but an on-going, iterative processes.
process with each iteration Process Level 1
building off the results of
previous series. ZEXPRESS EA  ZEXPRESS Enterprise Business Architecture (ZEBA)
which defines the enterprise’s key business
solution will follow the path as strategies of ZEXPRESS.
defined below  ZEXPRESS Enterprise Information Architecture
(ZEIA) which defines the key information and
information flows that enable and support
Establish a EA sponsorship body managed business strategies.
by ZEXPRESS COE and run by architecture
 ZEXPRESS Enterprise Technical Architecture
(ZETA) which defines a set of principles that
experts selected from different regions of guides the deployment of IT and IT infrastructure
the company. that supports the information flows.
Establish an EA model based on TOGAF  ZEXPRESS Domain Architectures (ZDA) which
ADM and consists of several major sub- provide the concrete specification of hardware,
software, and infrastructure within areas, or
processes that are performed with varying domains, of technology that will be deployed to
degrees of intensity based on the maturity implement the EWTA for major business domains
level of new enterprise ZEXPRESS. of ZEXPRESS.
Establish an Iterative phased out approach
to execute EA program successfully using Process Level 2
the sub processes as explained in here.  Gap Analysis / Migration and Implementation
Planning which provides the plan for going from
the current state to the desired future state as
described by the Domain Architectures.

August 2008 October 2008

Proposed ZEXPRESS EA Solution Life Cycle

ZEXPRESS Iterative EA program

ZEXPRESS Consolidation Trends
Define
Define Define
ZEXPRESS Define
ZEXPRESS ZEXPRESS
ZEXPRESS EA ZEXPRESS Enterprise ZEXPRESS
Enterprise Enterprise
Sponsorship Business Information Domain
Business Technology Architecture
and governance visioning Architecture Architectures
Architecture ZETA
ZEIA ZDAS
ZEBA

Document AS IS EA environment of three

GAP analysis
ZEXPRESS Parent companies

Implementation Plans Migration Plan

Implementation Plans

ZEXPRESS EA governance and evolution, organizational impacts, communication

Decencies/flow
Phase 1 Phase2 Iterations

August 2008 October 2008

ZEXPRESS Business Architectures
Objectives Steps Outputs
• Select architecture • Develop Baseline • Updated statement of
viewpoints to demonstrate Business Architecture architecture work.
how ZEXPRESS stakeholder Description. • Validated business
concerns are addressed in • Identify Reference principles, business goals,
the Business Architecture. Models, Viewpoints, and and strategic drivers.
• Select tools and techniques Tools. • Detailed target Business
for viewpoints. • Create Business Architecture.
• Describe the existing Architecture models. • Detailed baseline Business
business Architecture (the • Select Business Architecture.
current baseline from thee Architecture building • Views corresponding to the
parent companies). blocks . selected viewpoints
• Develop a Target Business • Conduct a formal addressing key stakeholder
architecture checkpoint review of the concerns .
architecture model and • Technical requirements
building blocks with identifying, categorizing,
stakeholders. and prioritizing the
• Review non-functional implications for work in the
criteria. remaining architecture
• Complete the Business domains.
Architecture. • Business Architecture
Report.
• Updated business
requirements.

August 2008 October 2008

ZEXPRESS Information Architectures
Objectives Steps Outputs
• To develop Target • Develop Baseline • Updated Statement of
Architectures for the Architecture Description. Architecture Work.
ZEXPRESS Business • Review and Select • Updated Baseline Data
Information. Principles, Reference Architecture, Version.
• Define the types and Models, Viewpoints, and • Validated data principles, or
sources of data needed to Tools. new data principles.
support ZEXPRESS • Create Data Architecture • Updated Target Data
business, in a way that can Models. Architecture.
be understood by the • Select Data Architecture • Data Architecture views
stakeholders.
Building Blocks. corresponding to the
• Conduct a Checkpoint selected viewpoints.
Review of the • Data Architecture Report.
Architecture Model. • Updated business
• Review Qualitative requirements.
Criteria .
• Complete the Data
Architecture.
• Conduct
Checkpoint/Impact
Analysis.

August 2008 October 2008

ZEXPRESS Technology Architectures
Objectives Steps Outputs
• To develop a Target • Develop Baseline • Updated statement of
Technology Architecture Technology Architecture Architecture Work.
that will defines a set of Description. • Updated Baseline
principles that guides the • Create a Baseline Technology Architecture.
deployment of IT and IT Technology Architecture • Validated technology
infrastructure that supports Description in IT services principles or new
the ZEXPRESS business terminology. technology principles.
information flows. • Consider different • Technology Architecture
Architecture Reference Report, summarizing what
Models, Viewpoints, and was done and the key
Tools. findings.
• Create an Architecture • Target Technology
Model of Building Blocks. Architecture.
• Select the Services • Viewpoints addressing key
Portfolio per Building stakeholder concerns.
Block. • Views corresponding to the
• Confirm that the selected viewpoints.
Business Goals and
Objectives are met.
• Choose the Criteria for
Specification Selection.
• Complete the
Architecture Definition.

August 2008 October 2008

ZEXPRESS Domain Architectures
Objectives Steps Outputs
• To develop Domain • Develop Baseline Domain • Updated statement of
Architectures that will Architecture Description. Architecture Work.
defines concrete • Create a Baseline Domain • Updated Baseline Domain
specification of hardware, Architecture Description architectures.
software, and infrastructure in software, hardware • Validated domain
within ZEXPRESS business and application service architecture specification
sub domains such as HR, terminology. for each business sub
Accounting, Billing, Office • Consider different domain.
productivity, Transportation hardware and software • Domain architecture report,
management, packaging Reference Models, summarizing what was
and tracking. Viewpoints, and Tools. done and the key findings.
• Create an Domain • Target domain
Architecture Model of architectures.
Building Blocks.
• Select the Services
Portfolio per Building
Block.
• Confirm that the EA goals
are followed.
• Choose the Criteria for
Specification Selection.
• Complete the Domain
Architecture Definition .

August 2008 October 2008

1
ZEXPRESS EA Governance Model

Outlined below is the proposed governance structure and a brief

description of each components responsibilities.
ZEXPRESS Executive EA Sponsoring Committee (ZEEASC) is responsible for prioritizing all IT
efforts in relation to the business requirements and for reaching a common vision between the
business and IT on the business drivers and on the role of EA and technology. This committee is
lead by new COE of ZEXPRESS. This committee is also responsible for tracking all projects,
resources, budgets, and project interdependencies to provide ZEXPRESS stakeholders with the
information it will require to set the priorities of business.
The ZEXPRESS EA Review Board (ZARB) is responsible for providing input for and reviewing and
approving the conceptual and domain architectures, including products, domain technologies
and standards and granting exceptions to the published standards. This board is managed by
COE, board members are nominated by COE based on Architecture skills of internal an external
resources.
ZEXPRESS Architecture Team (ZAT) is responsible for facilitating the enterprise architecture
process, creating and maintaining deliverables, communicating architecture standards to all
interested parties, and reviewing technology infrastructure projects for compliance to the
architecture. This team is build on Demand and work with ZARB.
ZEXPRESS Domain Architecture Teams (ZDAT) are responsible for selecting product standards,
defining standard configurations, and collaborating on component architecture design principles
with the architecture team.

August 2008 October 2008

1
ZEXPRESS EA Governance Model Life Cycle

ZEXPRESS Executive Enterprise Architecture Sponsoring Committee

ZEESC

ZEXPRESS EA Review Board ZEXPRESS Architecture Team

ZARB ZAT

ZEXPRESS Domain
ZEXPRESS EA Governance Architecture Teams
Task forces and committees ZDATS

August 2008 October 2008

1
ZEXPRESS EA Project Milestones Deliverables

Planning Status and Architecture Architecture EA EA

Requirements Principles Modeling Governance Action Plan

Wk
Wk 1-3 Wk
1-3 Wk
Wk 3-9
3-5 Wk 2-24
2-12 Wk
Wk 9-24
9-12
Gather and Develop Develop Develop
Wk11
Wk Summarize Wk Conceptual Evaluation Transition
Wk 2-24
2-12
Inputs Model Criteria Plan
Planning Principles
Sessions Definition Wk
Wk 9 24
6-9
Workshops
Document Gap Define
Key Analysis Architecture Final
Requirements Architecture Review Board Workshops Management Presentation
§ Set expectations Architecture
§ Kickoff Review Board
(half day) Processes
§ Review
§ Set expectations
contract § EA§ Kickoff (half day)
Principles
§ Review
§ Identify ARB contract
members § EA Principles
---------------
§ Identify § Conceptual Model
§ Identify keyARB members § Strategic documents § EA
stakeholders ---------------
Visioning § Conceptual EA Models § EA Processes
§ Identifyinterviews
key stakeholders § Strategic documents§ EA§ EA Visioning § Access, Security § EA Processes § Complete
§ Schedule § Business models Roles/Responsibilities § AS IS EA Models § Evaluation § Complete
§ Schedule interviews § User
§ Business § Applications Documentation
§ Schedule Workshops groups models § EA § EA Roles/Responsibilities
Metrics § TO BE EA Models
§ Evaluation
Criteria Documentation
§ Schedule Workshops § Pilots
§ User groups § EA Metrics § Data Criteria § Initiatives
§ Team orientation --------------- § EA gapServices
analysis reports § Arch Review
§ Team orientation § Pilots position --------------- § Common § Arch Review § B&P
§ Other logistics § Sourcing § EA Processes Migration plan Board
§ Other logistics § Sourcing position § EA§ EA Processes Application Development, Board
§ locations § Baseline assessment Tools § Technical
§ locations § Baseline assessment § EA Tools Cross-Implementation plan § Technical
§ space --------------- Steering
§ space --------------- § Systems- Mgt Steering
§ communications § EA Transition Plan Committee
§ communications § EA Transition Plan , Committee
§ Intranet Access --------------- § EA in a Box
§ Intranet Access --------------- Peripherals § EA in a Box
§ Autonomic/Grid/UMI

August 2008 October 2008

1
Expected Outcomes: Top Down, Across and Bottom Up

Build target enterprise architecture models for

ZEXPRESS.
Enterprise Promote EA concepts for business community.
Establish an infrastructure for collaboration and
Architectures sharing EA information across ZEXPRESS
boundaries.

Reuse ZEXPRESS EA to ensure enterprise visions

Domain are recognized. Domain specific architecture
implementation is achieved for sub domain
Architecture areas such as HR, Finance, Packet Tracking etc.

Establish a community of architects to share

Architects experiences, build skills, and reuse EA
architectural products.
New Global business realization with Agile IT
ZEXPRESS and Business alignment to serve the Demand
of challenging business in a cost effective
approach.
August 2008 October 2008
1
 ZEXPRESS
” ZEXPRESS Future EA Vision”

August 2008 October 2008

1