1) The document discusses various tools and frameworks that can be used to make sense of supply chain information architecture, including bubble diagrams, capability pyramids, swimlanes, and transition matrices. 2) These tools help analyze requirements, map capabilities, understand relationships, and plan the evolution of organizations, processes, and systems over multiple phases. 3) The goal is to design an information architecture that serves customers and meets their needs, rather than just replicating current systems.

1. Working with supply chain information architecture
I have found...
Most people agree that
making sense out of things
makes sense.
ECSCIA, European Centre of Supply Chain
Information Architecture

2. ”Making sense” starts with being clear on
EA for the supply chain
ís created from supply chain requirements,
not historical or current system capabilities
The end goal of EA, as every other activity in the supply chain community
is to sell products to consumers,
not sell systems to departments.
EA serves the customers,
not system vendors
ECSCIA, European Centre of Supply Chain
Information Architecture

3. Another step in ”making sense” is to have
a reasonably simple
EA toolbox
for supply chain information architecture
To support exploration and clarificationboth
Project preparation and grand roadmap formulation
I use some simpletemplates/models
ECSCIA, European Centre of Supply Chain
Information Architecture

4. Each bubble holds one statement,
one part of the noise”The box helps group
the bubbles statements,
to find the themes
The conclusion/essence
end up in top right corner
c
I use the ”bubble & box” to make sense out of a state where there
is noise and unclarity . The bubbles are a bit like ”finding the voice of the
customer” in LSS but the boxes takes the analyzis further than LSS as it also brings
some structure that leads up to a ”essence” statement
I might do one
B&B for
functional
requirements,
one for technical
and one for.....
ECSCIA, European Centre of Supply Chain
Information Architecture

5. DCOR
Plan
Research Design
Integarte Amend
CCOR
Plan
Relate Contract
Sell Assist
SCOR
Plan
Source Make
Deliver Return
I use the capability pyramid and the supply chain council
frameworkto
A) Map and understand what capability areas requirement fits into and if there are
overlaps/ dependencies
B) Do the same for the IT systems
Fulfill
Plan
PDM Integrate
ECSCIA, European Centre of Supply Chain
Information Architecture

6. Integrate
Fulfill
Sell
PLM
Plan
Source Make
Deliver
Research Design
Integrate
Integrate Relate
Enable
Plan source Plan Make
Plan deliverPlan sell
PDM
Document mgmt Connectivity & access
Refrencing the
supply chain
council saves a lot
of time and
reduces
misunderstanding
ECSCIA, European Centre of Supply Chain Information Architecture

7. I use ”Pool and Silo” to position the solution in terms (grade) of
”shared/global” (Pool)
or ”distinct/local”
”Areas” ”Pools”
”Silos”
Functional areas Pools holds global
systems supporting
the area
Silos holds
regional
systems
supporting
the area
Colors
indicate gaps
ECSCIA, European Centre of Supply Chain Information Architecture

8. Good old
swimlanes
provides the ”Who” and
the ”What”
”ER for EA”
Simple object models
Adds detail
ECSCIA, European Centre of Supply Chain Information Architecture

9. Organisational desig
Phase 1
Organisational desig
Phase 2
Organisational desig
Process design
Phase 4 ”Golden state”
Organisational desig
Process design
Phase 3
Process designProcess design
System design System design
System design System design
The Transition matrix describes the interaction organisation
change, process-and system evolving over (4...) phases where ”4” is the golden
(unobtainable?) final state
ECSCIA, European Centre of Supply Chain
Information Architecture