Presentation by Brechtel Dero at the I.T. Works/LoQutus meetup on July 1st, 2014 at Vlerick School Campus Gent. See http://www.meetup.com/The-big-pICTure-how-ICT-changes-business-and-society/events/181256842/ for full details on this event

2. 1 Who am I?

3. 2 Colruyt Group

4. Bakery
1900-1930
Wholesale trade
1930-1955
Discounter
1955-1995
Retail Group
1995-Present
Growth of the company and the family
4
Bakery
Jozef Colruyt
Wholesale
Franz Colruyt
Discounter
Jo Colruyt
Retail Group
Jef Colruyt
Frans Colruyt

5. Retail: 76% of group revenue

6. Wholesale and foodservice:
16% of group revenue

7. Other activities: 9% of group revenue

8. Corporate activities
Support services:
Business Processes & Systems
Finance
Logistics & Production
People & Organisation
Marketing
Premedia
Technics, Real Estate & Energy
Vlevico
8

9. Key figures
9

10. Employees
10

11. 3 Architecture @
Colruyt Group

12. Timeframe
2000
Infoco21
2008
Start
“procesmatig
ondernemen”
2010
Start current
EA approach
2014
Where are
we now?
12
Main focus of
today

13. Architecture helps to realize strategy
Strategy
Planning
Design and
Delivery
EnterprisewidefocusProjectfocus
Strategy
Business Operating Environment
and IT Infrastructure
Business and IT Solutions
support
govern
feedback
steer
EnterpriseArchitecture
Transition Plan (as-is  to-be)
IT
Architecture
- Applications
- Data
- Infrastructure
- Security
Business
Architecture
- Components
- Processes
- Information
EnterpriseArchitecture
13

14. It took us 4 years to develop a mature
architecture discipline
14
Fundaments&
Alignment
Embodiment&
Consolidation
Content&
Improvement
Managging
roadmaps
Pre-
fase
B
A
U
ACoE
Maturity
+1
ACoE
Maturity
+2
ACoE
Maturity
+3
ACoE
Maturity
+4
Nov ‘12 May ‘13 Oct ‘13 March ‘14
ACoE
Maturity
+5
Final
embodiment

15. Why a metamodel?
• To ensure that there is a common understanding
• Between different architecture disciplines
• On different levels (enterprise and solution)
• “Builders” need to understand what architects want
• A means to describe the complete landscape
• A foundation to understand the landscape
15

16. Everyone has the right to make 1 major
mistake (a year )
We tried to build our own metamodel … and failed
gloriously
Too complex
Impossible to get disciplines aligned
Language vs style
Endless discussions
Impossible to exchange experiences outside the
company
Conclusion beginning 2013: stop the crap, introduce
archimate
16

17. 4
Architectural
modelling @
Colruyt Group

18. Structure of our Architecture
Repository part 1
18
Reference Material for
the creation of new
Architectures
The Architectural
representation of the state
of the Enterprise (current
and future state)

19. Reference Model: BCM
19

20. Reference Model: Process Chains
20

21. Architecture Patterns at Colruyt Group
21

22. Example: exposed stand-alone application runtime pattern
22

23. Decision matrix in reference architecture
PowerPoint-presentatie Colruyt Group - 05-23
Protocol Choices MQ HTTP RMI-IIOP Other
IMSL SOAP
(WS)
JMS(10)
SOAP
(WS)
REST
(WS)
Remote
Java
Beans(EJB)
Public
SP
Adapters
Criteria DEPRECATED
(2)
X
(1)
TBD(1)
Asynchronous communication V 
(2)
V V V
(7)
Synchronous communication V(2)
X (2)
V V V V(7)
Supports XA transactions (remote) V ?(3)
V V V(7)
Supports non-java consumer V V V V (9)
V
Message persistency V  V(7)
Guaranteed delivery to provider V V X V
(7)
Supports XML message V V X
(8)
V
(7)
Supports Attachments V V
Supports Encryption V V V(4)
Supports Authentication V
(5)
V V V
(6)
V V
(7)
Open standard V V V V V
Lightweight Message protocol V V V V V

24. So, what do we have so far
24

25. Reference Model Architecture Landscape
ABB
SBB
Relation Reference Library &
Landscape: BCM example
Element of the
BCM
Business Components
defined by the Business
Operating Model

26. Layered setup of Archimate
26
refine refine
Archimate concepts are
used to describe ABBs
and SBBs
Archimate concepts for
SBBs always refer to a
certain solution
Refine relation
between ABB and
SBB

27. Part 2: Project Views vs Landscape Views
27
Project views visualize
entities and relations
relevant for a project
Entities and Relations exist
independent from the
diagrams on which they
appear
Landscape views visualize
the same entities and
relations, but from a
holistic perspective

28. Project Views

29. Example Application Landscape Views
29
L0 ABB Application Overview
Internal Architecture
diagram of L0 component
“HR System”
Internal Architecture
diagram of L1 Local HR
Applications BE
Internal Architecture
diagram of L2
Component “PSFT
HCM 9.1.”

30. Example: Landscape Views for
Application Architecture
Application
Environment
Diagram of
Application
Component Core
HR.

31. 2 repository setup for MEGA
31
A work repository where projects and
programs create new architecture
content
A published repository that
contains all architecture
descriptions that are validated
Transfer between these repositories is
part of the governance process

32. Architecture Validation Flow
32

33. Current status
• All IT architects are trained in ArchiMate
• All new architectural content is modeled in
Archimate in Mega
• Visio remains available for free format diagrams
• By the 2nd half of this year, we will run a project
to give direction on the future IT landscape based
on the combined information of the architecture
repository and cmdb
• Busy building the application function diagram to
explain different scenario’s
33

36. Hope you enjoyed
36