Johan Bruynseels, Global Director Enterprise Architecture at Volvo spoke at the CIO Event, March 2013

1. Johan Bruynseels
Global Director Enterprise Architecture
& Business Solutions
Volvo Financial Services

2. Enterprise Architecture Introduction

3. 3
Enterprise architecture Definition
Enterprise architecture is the process of translating
business vision and strategy into effective enterprise
change by creating, communicating and improving the
key principles and models that describe the
enterprise's future state and enable its evolution.
The scope of the enterprise architecture includes the
people, processes, information and technology of the
enterprise, and their relationships to one another and
to the external environment.
Enterprise architects compose holistic solutions that
address the business challenges of the enterprise and
support the governance needed to implement them.
Gartner

4. The Need of Architecture
The Winchester House, San Jose, California
• 38 years of construction – 147
builders 0 architects
• 160 rooms – 40 bedrooms, 6
kitchens, 2 basements, 950 doors
• 65 doors to blank walls, 13
staircases abandoned, 24 skylights
in floors
• No architectural blueprint exists

5. • Use helicopter to see the “problem” mountain that needs to be climbed
• Use the helicopter to land on the mountain that needs climbing
• Lead the team that trek through the jungle of confusion to the mountain and climb it because this is
a guided journey not an expedition
Role of an Architect – Climbing The Right Mountain
Not all problem mountains are easy to pick
out of their surroundings

6. Architecture Development Process (e.g.TOGAF)
IIllustrative
A
Architecture
Vision
H
Architecture
Change Mgmt
G
Implementation
Governance
Require
ments
B
Business
Architecture
E
Opportunities
and Solutions
F
Migration
Planning
Prelim:
Framework and
Principles
D
Technology
Architecture
Volume Planning
Model Option
Forecasting Vehicle Production & Delivery
Volume Forecasting
& Macro Scheduling Vehicle Order Scheduling & Sequencing
Dealer / Customer Order Management
Vehicle Orders, Inquiry
Production
Orders &
Schedule (weekly)
Vehicle Specs
Sequenced Orders,
Status
Sequenced Orders &
Due Dates
Engineering
Specs
Marketing
Marketing
Intent
Vehicle
Specs
Live Orders
Dealer
Generated
Vehicle Orders
(8 weeks ahead)
Sales
Forecast
(2 years)
Reformatted
Seq. & Sched.
Production
Orders
Order Status,
BOM Exploded Orders
Sales Forecast
at carline
level (monthly)
Production
Orders &
Schedule
Produced
Orders
(UK only)
N/A
VOHS MGO
Alliances (Renault,
Lotus, Bertone)
10707
Specs
10609
Order Processing
System (OPS)
?
Channel 21
N/A
EOG
N/A
FAST
N/A
EPICS
1800
Advanced
Autosequence
(AAS includes
OPAW)
TRAF2
?
GPDS
COP (1726)
Central Scheduling
(CSP/CSDB)
N/A
ALLDEV
Market/carline
requirements / allocation
Confirmed
model/trim
requirements / allocation
Free Demand
Order Forecasting
(FDOF)
Order Matching
(OMA)
Planning Process
(PLP)
NSC
Sales
Forecast
10505
European
Certificate of
Conformity
(GM*Drive -
ECoC)
1890
Car Ordering
Scheduling
System (COSS)
10725
Dynamic Systems
Interface (DSI)
10557
Invoice Triggering
(GM*Drive - IVC)
10572
Logistics
Communication
System (GM*Drive
- LCS)
10704
Locator
10575
Marketing Offer
System (MOS)
10704
Inventory
Management
Repoting (SIS-
IMR)
7188
Terminal System
Distribution (TSV)
Dealer
Management
System (DMS)
?
Dealer
Communications
System (DCS2)
Vehicle Orders, Inquiry
Vehicle Orders
Vehicle
Orders
Vehicle Orders
(from Dealer)
Model Package Versions (MPVs)
Allocation
Generated Orders &
Monthly Schedule
Produced
Orders
(Outside UK)
Order Status
10518
Event Processing
System (EPS)
Order
Events
Order
Events
Order
Events
Order
Events
Order Status
Order Status
Vehicle Details
Supplier Systems
Projected
Materials
NSC
Market/car-line requirements/plan,
stock, uncleared allocation (monthly)
N/A
Inter/Intra
Company Vehicle
Management
(ICVM - future)
Vehicle Orders
Vehicle Invoicing
and Pricing
System (VIPS)
Marketing Info
Pricing Info
Vehicle Spec
Invoice Info
Non-CSP
Production
Systems (country/
region specific)
Order Info, Events
Warranty Systems
(country/region
specific)
Vehicle
Info
Forwarder
Systems
Logistics
Info /
Request
Logistics
Info /
Request
Other External
European Systems
(ECS, CSI, ICATS,
SCOOP)
Vehicle
Info
GM*Drive (1750)
Generated Orders (40 wks)
Free Demand
N/A
Marketing
Alignment Tool
(MALT - UK only)
Vehicle Registrations
Vehicle & Order Data
Engineering
Specs
Master
Scheduler
Production requirements
/ plan (monthly)
Marketing input?
Additional GM*Drive subsystems
 MEN (10580) - Menu subsystem
 MUL (10583) - Multilanguage support
 SEC (10666) - Security
Additional GM*Drive subsytems
 ESDS (10517) - part of OPS
 PDH (10636) - Production Deviation Handling
 PRL (10629) - Prereleasing
 SVO (10673) - Special Vehicle Ordering - part of OPS
 VIS (10702) - Vehicle Inquiry System
Additional GM*Drive subsytems
 HPS (10546) - Hold Processing
 NVH (10584) - NSC Vehicle Handling
 SSS (10672) - Source Shipping Intake
 TAI (10687) - Type Approval
 DES (N/A) - Retail & Registration
 DDC (N/A) - Dealer & Dest. Changes
Additional external systems
 Local Company Car
 SGM, Mexico, Holden, Yanase
 CKD
 Portugal SKD
 Local Dealer Information Systems
 Local Fleet Management
 Fleet Customers
 Local Customs
 Product Costing EPCS, WPCS, CLAN
 Local Type Approval
 Local Registration
 GMAC
 Local Accounting
 Dealer Audit
 Agencies & Insurance
 Customer Assistance
 GM*CUSTOM Customer Information
 GM*MOVE Vehicle Information
 FFCS Field Force Communication
 MRS Manufacturer Reporting
Order information
for local legal requirements,
customs documents,
type approval documents, etc
Sales Forecast
at carline level
(monthly)
N/A
Vehicle Sales &
Stock Statistics
(VSSS)
Final Volume
(monthly)
Production
requirements
(monthly)
BOM
Exploded
Orders
?
Production
Scheduling (PS -
Saab)
?
Order Processing
(OP - Saab)
?
BLOD (Saab)
?
CAS-E (Saab)
?
PEM (Saab)
?
PEG (Saab)
?
PMU (Saab)
Generated Orders
Engineering
Specs
Central
Restrictions
Table
Migration Plan Technical Architecture
Business Architecture
Governance & Chg Mgmt
IIllustrative
IIllustrative IIllustrative
C
Information
System
Architectures

7. Enterprise Architecture in Action

8. Enterprise Architecture Analogy: The OODA Loop
The OODA Loop was originated by U.S. Air Force Colonel John Boyd, who developed it to define a way to understand how
fighter pilots, often in inferior aircraft, consistently won air combat engagements against enemy pilots. What Boyd observed was
that winning pilots acted more quickly than their less successful opponents by cycling rapidly through four states:
•Observe — See the situation and adversary.
•Orient — Size up the vulnerabilities and opportunities.
•Decide — Determine which combat maneuver to take.
•Act — Execute the maneuver.

9. Although modern vision talk
about governance models,
iterative approaches and
focus on value and business
case, however …
There is only one way and
that is the top-down
approach
• Observe : business contect
• Orient : define future state
• Decide : create the plan
• Act : Execute the plan
EA : The Multi Year Plan

10. Link to Business Strategic Planning and
Budget Process
“In a well-architected enterprise, EA is the
coordinating process that helps guide the
strategic and management processes of the
enterprise to be in sync with respect to
evolving toward a future state vision.”
“EA efforts must continually be revisited and
updated to reflect the current business.”
Source: Gartner - The Thirteen Worst EA Practices
10

11. Enterprise Architecture Example

12. Alice stands at a crossroads and asks the cat
which path she should take.
He asks “Where are you going?”
She says she doesn’t know.
“Well then, it doesn’t really matter which path
you take.”
The meaning of the painting is indicated by the
title La Clairvoyance (perspicacity). The egg will
become a bird. The artist sees what it will
become. Through understanding the artist
knows that the egg will become a bird.
Enterprise Architecture : The Essentials

13. Q & A