Quick Reference:

BiZZdesign www.bizzdesign.com

Enterprise Architecture with TOGAF and ArchiMate

The TOGAF 9.1 Components

TOGAF is a registered trademark of The Open Group

The TOGAF Architecture Development Method (ADM)

Preliminary

A.
Architecture
Vision
H. B.
Architecture Business
Change Architecture
Management

G. C.
Implementation Requirements Information
Governance Management Systems
Architectures

F. D.
Migration Technology
Planning Architecture
E.
Opportunities
and
Solutions
 Summary of the ADM process
1. Getting the organization
Preliminary
committed & involved

4. Keep the
A. Preliminary
process H.
Architecture
Vision
B.
running Architecture
Change
Management
Business
Architecture

A.
Architecture
Vision
G. C. H.
Information B.
Implementation Requirements Architecture Business
Governance Management Systems Change
Architectures Architecture
Preliminary Management

F. D. C.
Technology
G.
Migration Implementation Requirements Information
Planning Architecture Management Systems
Governance
E. Architectures
A. Opportunities Preliminary
Architecture and
Vision Solutions
H. B.
Architecture Business D.
Change
F.
Architecture Migration Technology
Management Architecture
Planning
E.
A. Opportunities
Architecture and
Vision Solutions
G. C.
Information H. B.
Implementation Requirements Architecture
Management Systems Business
Governance Change
Architectures Architecture
Management

2. Getting the
D.
architecture
F. C.
Migration Technology G.
Implementation Requirements Information
Planning Architecture Systems
E. Governance Management

right
Architectures
Opportunities
and
Solutions

F. D.
3. Making the Migration
Planning
E.
Technology
Architecture

architecture Opportunities
and
Solutions

work
Input Objectives
1. Reference Materials External: TOGAF, other EA frameworks 1. Determine the Architecture Capability desired by the
2. Non-Architectural Inputs: business strategies, principles, organization
goals, and drivers, portfolio/project management, 2. Establish the Architecture Capability
(architecture) governance, IT strategy
3. Architectural Inputs: Pre-existing models can be used as a
base-line (e.g., Existing Organizational Model for EA, EA
Framework, EA Principles, EA Repository)

Preliminary
Phase

Steps
1. Scope the Enterprise Organizations Impacted Output
2. Confirm Governance and Support Frameworks 1. Organizational Model for EA
3. Define and Establish Enterprise Architecture Team and 2. Tailored Architecture Framework
Organization 3. Configured and deployed tools
4. Identify and Establish Architecture Principles 4. Initial EA Repository
5. Select and Tailor Architecture Frameworks 5. Request for EA Work
6. Implement Architecture Tools 6. Governance Framework
Input Objectives
1. Reference Materials External: Architecture reference 1. Develop a high-level aspirational vision of the capabilities
materials and business value to be delivered as a result of the
2. Non-Architectural Inputs: Request for Architecture Work, proposed enterprise architecture
Business Principles, Business Goals, and Business Drivers 2. Obtain approval for a Statement of Architecture Work that
3. Architectural Inputs: Organizational Model for Enterprise defines a program of works to develop and deploy the
Architecture, Tailored Architecture Framework architecture outlined in the Architecture Vision

Steps
1. Establish the Architecture Project Phase A:
2. Identify Stakeholders, Concerns, and Business Architecture
Requirements vision
3. Confirm and Elaborate Business Goals, Business
Drivers, and Constraints
4. Evaluate Business Capabilities
5. Assess Readiness for Business Transformation Output
6. Define Scope 1. Approved Statement ofArchitecture Work
7. Confirm and Elaborate Architecture Principles 2. Refined statements of Business Principles, Business Goals,
8. Develop Architecture Vision and Business Drivers
9. Define the Target Architecture Value Propositions and KPIs 3. Architecture Principles
10. Identify the Business Transformation Risks and Mitigation 4. Capability Assessment
Activities 5. Tailored Architecture Framework
11. Develop Enterprise Architecture Plans and Statement of 6. Architecture Vision
Architecture Work; Secure Approval 7. Additional content populating the Architecture Repository
Input Objectives
1. Reference Materials External: Architecture reference 1. Develop the Target Business Architecture that describes
materials how the enterprise needs to operate to achieve the business
2. Non-Architectural Inputs: Request for Architecture Work, goals, and respond to the strategic drivers set out in the
Business Principles, Business Goals, and Business Drivers, Architecture Vision, in a way that addresses the Request for
Capability Assessment, Communication Plan Architecture Work and stakeholder concerns
3. Architectural Inputs: Organizational Model for Enterprise 2. Identify candidate Architecture Roadmap components based
Architecture, Tailored Architecture Framework, Approved upon gaps between the Baseline and Target Business
Statement of Architecture Work, Architecture Principles, Architectures
Enterprise Continuum, Architecture Repository, Architecture
Vision

Phase B:
Business
Architecture

Steps
1. Select Reference Models, Viewpoints,and Tools Output
2. Develop Baseline BA Description 1. Refined and updated versions of the Architecture Vision
3. Develop Target BA Description phase deliverables
4. Perform Gap Analysis 2. Draft Architecture Definition Document
5. Define Roadmap Components 3. Draft Architecture Requirements Specification
6. Resolve Impacts Across the Architecture Landscape 4. BA components of an Architecture Roadmap
7. Conduct Formal Stakeholder Review
8. Finalise the Business Architecture
9. Create Architecture Definition Document
Input Objectives
1. Reference Materials External: Architecture reference 1. Develop the Target Information Systems (Data and
materials Application) Architecture, describing how the enterprise's
2. Non-Architectural Inputs: Request for Architecture Work, Information Systems Architecture will enable the Business
Capability Assessment, Communication Plan Architecture and the Architecture Vision, in a way that
3. Architectural Inputs: Organizational Model for Enterprise addresses the Request for Architecture Work and
Architecture, Tailored Architecture Framework, Application stakeholder concerns
Principles, Data Principles, Statement of Architecture 2. Identify candidate Architecture Roadmap components based
Work, Architecture Vision, Architecture Repository, Draft upon gaps between the Baseline and Target Information
Architecture Definition Document, Draft Architecture Systems (Data and Application) Architectures
Requirements Specification, BA components of an
Architecture Roadmap.

Phase C:
Information
Systems
Architectures

Output
1. Refined and updated versions of the Architecture Vision
phase Deliverables, including updated Statement of
Architecture Work
2. Draft Architecture Definition Document
Steps 3. Draft Architecture Requirements Specification
Detailed steps for Phase C are given separately for each 4. Information systems components of an Architecture
architecture domain. Roadmap
Input Objectives
1. Reference Materials External: Architecture reference 1. Develop the Target Data Architecture that enables the
materials Business Architecture and the Architecture Vision, while
2. Non-Architectural Inputs: Request for Architecture Work, addressing the Request for Architecture Work and
Capability Assessment, Communication Plan stakeholder concerns
3. Architectural Inputs: Organizational Model for Enterprise 2. Identify candidate Architecture Roadmap components
Architecture, Tailored Architecture Framework, Data based upon gaps between the Baseline and Target Data
Principles, Statement of Architecture Work, Architecture Architectures.
Vision, Architecture Repository, Draft Architecture Definition
Document, Draft Architecture Requirements Specification,
BA components of an Architecture Roadmap.

Phase C:
Data
Architecture

Steps
1. Select Reference Models, Viewpoints, and Tools
2. Develop Baseline Data Architecture Description
3. Develop Target Data Architecture Description
4. Perform Gap Analysis Output
5. Define Roadmap Components 1. Refined and updated versions of the Architecture Vision
6. Resolve Impacts Across the Architecture phase Deliverables, including updated Statement of
Landscape Architecture Work
7. Conduct Formal Stakeholder Review 2. Draft Architecture Definition Document
8. Finalise the Data Architecture 3. Draft Architecture Requirements Specification
9. Create Architecture Definition Document 4. DA components of an Architecture Roadmap
Input Objectives
1. Reference Materials External: Architecture reference 1. Develop the Target Application Architecture that enables
materials the Business Architecture and the Architecture Vision,
2. Non-Architectural Inputs: Request for Architecture Work, while addressing the Request for Architecture Work and
Capability Assessment, Communication Plan stakeholder concerns
3. Architectural Inputs: Organizational Model for Enterprise 2. Identify candidate Architecture Roadmap components based
Architecture, Tailored Architecture Framework, Application
Principles, Statement of Architecture Work, Architecture
Vision, Architecture Repository, Draft Architecture Definition
Document, Draft Architecture Requirements Specification,
BA and DA components of an Architecture roadmap.

Phase C:
Application
Architecture

Steps
1. Select Reference Models, Viewpoints, and Tools
2. Develop Baseline Application Architecture Description
3. Develop Target Application Architecture Description
4. Perform Gap Analysis Output
5. Define Roadmap Components 1. Refined and updated versions of the Architecture Vision
6. Resolve Impacts Across the Architecture Landscape phase Deliverables, including updated Statement of
7. Conduct Formal Stakeholder Review Architecture Work, Validated or new application principles
8. Finalise the Application Architecture 2. Draft Architecture Definition Document
9. Create Architecture Definition Document 3. Draft Architecture Requirements Specification
4. AA components of an Architecture Roadmap
Input Objectives
1. Reference Materials External: Architecture reference 1. Develop the Target Technology Architecture that enables
materials, Product information on candidate products the logical and physical application and data components
2. Non-Architectural Inputs: Request for Architecture Work, and the Architecture Vision, addressing the Request for
Capability Assessment, Communication Plan Architecture Work and stakeholder concerns
3. Architectural Inputs: Organizational Model for Enterprise 2. Identify candidate Architecture Roadmap components based
Architecture, Tailored Architecture Framework, Technology upon gaps between the Baseline and Target Technology
Principles, Statement of Architecture Work, Architecture Architectures
Vision, Architecture Repository, Draft Architecture Definition
Document, Draft Architecture Requirements Specification,
BA, DA and AA components of an Architecture Roadmap.

Phase D:
Technology
Architecture

Steps
1. Select Reference Models, Viewpoints, and Tools
2. Develop Baseline Application Architecture Description
3. Develop Target Application Architecture Description Output
4. Perform Gap Analysis 1. Refined and updated versions of the Architecture Vision
5. Define Roadmap Components phase Deliverables, including updated Statement of
6. Resolve Impacts Across the Architecture Landscape Architecture Work, Validated or new Technology principles
7. Conduct Formal Stakeholder Review 2. Draft Architecture Definition Document
8. Finalise the Application Architecture 3. Draft Architecture Requirements Specification
9. Create Architecture Definition Document 4. TA components of an Architecture Roadmap
Input Objectives
1. Reference Materials External: Architecture 1. Generate the initial complete version of the Architecture
referencematerials, Product information Roadmap, based upon the gap analysis and candidate
2. Non-Architectural Inputs:Request for ArchitectureWork, Architecture Roadmap components from Phases B, C, and D
Capability Assessment, Communication Plan, Planning 2. Determine whether an incremental approach is required,
Methodologies and if so identify Transition Architectures that will deliver
3. Architectural Inputs: Organizational Model for Enterprise continuous business value
Architecture, Governance models and frameworks,
Tailored Architecture Framework, Statement of Architecture
Work, Architecture Vision, Architecture Repository, Draft
Architecture Definition Document,Draft ArchitectureRequirem
entsSpecification,Change requests.

Phase E:
Opportunities
And
1. Steps Solutions
2. Determine/Confirm Key Corporate Change Attributes
Output
3. Determine Business Constraints for Implementation
1. Refined and updated versions of the Architecture Vision,
4. Review/Consolidate Gap Analysis Results
BA, ISA and TA phases Deliverables, including Updated
5. Review IT Requirements from a Functional Perspective
Statement of Architecture Work, Architecture Vision
6. Consolidate/Reconcile Interoperability Requirements
2. Draft Architecture Definition Document
7. Refine and Validate Dependencies
3. Draft Architecture Requirements Specification
8. Confirm Readiness/Risk for Business Transformation
4. Consolidated and validated Architecture Roadmap
9. Formulate High-Level Implementation/Migration Strategy
5. Capability Assessment,
10. Identify and Group Major Work Packages
6. Transition Architecture, Version 1.0
11. Identify Transition Architectures
7. Implementation and Migration Plan, Version 0.1, including
12. Create Portfolio/Project Charters, Update Architectures
the high-level Implementation and Migration Strategy
Input Objectives
1. Reference Materials External:Architecture reference 1. Finalize the Architecture Roadmap and the supporting
materials Implementation and Migration Plan
2. Non-Architectural Inputs: Request for Architecture Work, 2. Ensure that the Implementation and Migration Plan is
Capability Assessment, Communication Plan coordinated with the enterprise's approach to managing
3. Architectural Inputs: Organizational Model for Enterprise and implementing change in the enterprise's overall change
Architecture, Governance models and frameworks, portfolio
Statement of Architecture Work, Architecture Vision, 3. Ensure that the business value and cost of work packages
Architecture Repository, Draft Architecture Definition and Transition Architectures is understood by key
Document, Draft Architecture Require-ments Specification, stakeholders
Change requests, Consolidated Architecture Roadmap,
Capability Assessment, Transition Architecture V 1.0,
Implementation and Migration Plan V 1.0.

Phase F:
Steps Migration
1. Confirm Management Framework Interactions for Planning
Implementation and Migration Plan
2. Assign a Business Value to Each Project Output
3. Estimate Resource Requirements, Project Timings, and 1. Implementation & Migration Plan,V1.0
Availability/Delivery Vehicles 2. Finalised Architecture Definition Document
4. Prioritise Migration Projects through Cost/Benefit 3. Finalised Architecture Requirements Spec.
Assessment/Risk Validation 4. Finalised Architecture Roadmap
5. Confirm Transition Architecture Increments/Phases and 5. Finalised Transition Architecture
Update Architecture Definition Document 6. Re-Usable Architecture Building Blocks
6. Generate the Architecture Implementation Roadmap and 7. Requests for Architecture Work for the architecture aspects
Migration Plan of implementation projects
7. Establish the Architecture Evolution Cycle and Document 8. Architecture Contracts for implementation projects
Lessons Learned 9. Implementation Governance Model
10. Change Requests from lessons learned
Input Objectives
1. Reference Materials External: Architecture reference 1. Ensure conformance with the Target Architecture by imple-
materials mentation projects
2. Non-Architectural Inputs: Request for Architecture Work, 2. Perform appropriate Architecture Governance functions for
Capability Assessment the solution and any implementation-driven architecture
3. Architectural Inputs: Organizational Model for Enterprise Change Requests
Architecture, Tailored Architecture Framework, Statement
of Architecture Work, Architecture Vision, Architecture
Repository, Architecture Definition Document, Architecture
Requirements Specification, Architecture Roadmap,
Transition Architecture including Implementation
Governance Model, Architecture Contract, Request
for Architecture Work (from phase E and F),
Implementation and Migration Plan
Phase G:
Implementation
Governance

Steps
1. Confirm Scope and Priorities for Deployment with Develop-
ment Management
2. Identify Deployment Resources and Skills Output
3. Guide Development of Solutions Deployment 1. Architecture Contract (signed), as recommended in the
4. Perform Enterprise Architecture Compliance Reviews architecture-compliant implemented architectures
5. Implement Business and IT Operations 2. Compliance Assessments
6. Perform Post-Implementation Review and Close Implemen- 3. Change Requests
tation 4. Architecture-compliant solutions deployed
Input Objectives
1. Reference Materials External: Architecture reference 1. Ensure that the architecture lifecycle is maintained
materials 2. Ensure that the Architecture Governance Framework is
2. Non-Architectural Inputs: Request for Architecture Work from executed
phases E & F 3. Ensure that the enterprise Architecture Capability meets
3. Architectural Inputs: Organizational Model for Enterprise current requirements
Architecture, Tailored Architecture Framework, Statement
of Architecture Work, Architecture Vision, Architecture
Repository, Architecture Definition Document, Architecture
Requirements Specification, Architecture Roadmap,
Change Request technology & business changes, from
lessons learned, Transition Architecture including
Implementation Governance Model, Architecture
Contract, Request for Compliance Assessments, Phase H:
Implementation and Migration Plan Architecture
Change
Management

Steps
1. Establish Value Realisation Process
2. Deploy Monitoring Tools
3. Manage Risks
4. Provide Analysis for Architecture Change Management
5. Develop Change Requirements to Meet Performance Output
Targets 1. Architecture Contract (signed), as Requirements Impact
6. Manage Governance Process Assessment
7. Activate the Process to Implement Change 2. Architecture Requirements Specification
Input Objectives
1. Architecture Repository 1. Ensure that the Requirements Management process is sus-
2. Organizational Model for EA tained and operates for all relevant ADM phases
3. Tailored Architecture Framework, 2. Manage architecture requirements identified during any
4. Statement of Architecture Work execution of the ADM cycle or a phase
5. Architecture Vision 3. Ensure that relevant architecture requirements are available
6. Architecture Requirements for use by each phase as the phase is executed
7. Requirements Impact Assessment

Steps
1. Identify/document requirements (ADM phase)
2. Baseline requirements (RM)
3. Monitor baseline requirements (RM)
4. Identify changed requirements (ADM phase) Requirements
5. Identify changed requirements and record priorities Management
(RM)
6. Assess impact of changed requirements on current
phase, assess impact of changed requirements on
previous phases, determine whether to implement
change, or defer to later ADM cycle, issue Require-
ments Impact Statement, V n+1 (ADM phase)
7. Implement requirements arising from Phase H (ADM phase)
8. Update the requirements repository with information relating
to the changes requested, including stakeholder views af-
fected (RM)
9. Implement change in the current phase (ADM phase) Output
10. Assess and revise gap analysis for past phases (ADM 1. Requirements Impact Assessment
phase) 2. Architecture Requirements Specification
TOGAF Technical Reference Model (TRM)
Qualities
Infrastructure Business
Applications Applications

Application Platform Interface

System and Network

Management

Management
International
Engineering

Interchange
Transaction
Processing

Graphics &
Operations
Location &
Directory
Software

Interface
Security

Image
User

Data

Data

Qualities
Qualities

Operating System Services

Network Services

Communications Infrastructure Interface

Communications
Infrastructure
Qualities
ArchiMate framework

ArchiMate is a registered trademark of The Open Group

 The ArchiMate Language

High-level ArchiMate language

modeling
within a
domain Basis for
visualizations

Modeling relations Basis for

Relate to analysis
between domains
standards
 ArchiMate language summary

Business interface
Business
Representation
Business

service

Business Business Business

Business process role actor
object

Application Application
Application

service interface

Application Application
Data function component
object

Infrastructure
Technology

Infrastructure
service interface

Artifact Infrastructure Network

function Node
 ArchiMate business layer metamodel

Product
Meaning Value

Contract
Business Business Business
Representation
service interface collaboration

Event

Business object Business

process / Business Business
function / role actor
interaction

Location
 ArchiMate business layer concepts (1)

Concept Definition
An organizational entity that is capable of performing behavior
Business
actor

The responsibility for performing specific behavior, to which an actor can be

Business
assigned
role

An aggregate of two or more business roles that work together to perform

Business
collective behavior
collaboration

A point of access where a business service is made available to the environment

Business
interface

A conceptual point or extent in space

Location
Business
role

A passive element that has relevance from a business perspective

Business
object
interface
 ArchiMate business layer concepts (2)

Concept Definition
A behavior element that groups behavior based on an ordering of activities; it is
Business intended to produce a defined set of products or business services
process

A behavior element that groups behavior based on a chosen set of criteria

Business (typically required business resources and/or competences).
function

A behavior element that describes the behavior of a business collaboration

Business
interaction
service

Something that happens (internally or externally) and influences behavior

Business
event

A service that fulfills a business need for a customer (internal or external to the
Business organization).
service
 ArchiMate business layer concepts (3)

Concept Definition
The perceptible form of the information carried by a business object
Representation

The knowledge or expertise present in the representation of a business object,

Meaning given a particular context

The relative worth, utility, or importance of a business service or product

Value

Product A coherent collection of services, accompanied by a contract/set of agreements,

which is offered as a whole to (internal or external) customers

Product A formal or informal specification of agreement that specifies the rights and
obligations associated with a product
Contract
ArchiMate business layer example model
 ArchiMate application layer metamodel

Application Application
service interface

Data object Application

Application Application
function / component collaboration
interaction
 ArchiMate application layer concepts (1)

Concept Definition
A modular, deployable, and replaceable part of a system that encapsulates its
Application
component
contents and exposes its functionality through a set of interfaces

An aggregate of two or more application components that work together to

Application perform collective behavior
collaboration

A point of access where an application service is made available to a user or

Application
Application
another application component
component
interface

A passive element suitable for automated processing

Application
Data
component
object
 ArchiMate application layer concepts (2)

Concept Definition
A behavior element that groups automated behavior that can be performed by an
Application application component
function

A behavior element that describes the behavior of an application collaboration

Application
interaction

Application A service that exposes automated behavior

service
ArchiMate application layer example model
Process/application support example
 ArchiMate technology layer metamodel

Infrastructure Infrastructure
service interface

Infrastructure
function Communication
Artifact Node
path

System Device Network

software
 ArchiMate technology layer concepts (1)

Concept Definition
A computational resource upon which artifacts may be deployed for execution
Node

A hardware resource upon which artifacts may be stored or deployed for execution
Device

A communication medium between two or more devices

Network

A link between two or more nodes, through which these nodes can exchange data
Communication
path
 ArchiMate technology layer concepts (2)

Concept Definition
A point of access where the functionality offered by a node can be accessed by
Infrastructure other nodes and application components
interface

A software environment for specific types of components and objects that are
System deployed on it in the form of artifacts
software

A behavior element that groups infrastructural behavior that can be performed by

Infrastructure
Application a node
function

Infrastructure An externally visible unit of functionality, provided by one or more nodes, exposed
service through well-defined interfaces, and meaningful to the environment

A physical piece of information that is used or produced in a software development

Artifact process, or by deployment and operation of a system
ArchiMate technology layer example model
Application-technology support example
 ArchiMate structural relationships

Relationship Definition
Association A relationship between objects that is not covered by another, more specific
relationship

Access The access of behavioral concepts to business or data objects

Used by The use of services by processes, functions, or interactions and the access to
interfaces by roles, components, or collaborations

Realization Links a logical entity with a more concrete entity that realizes it

Assignment Links units of behavior with active elements (e.g., roles, components) that perform
them, or roles with actors that fulfill them
Aggregation Indicates that an object groups a number of other objects

Composition Indicates that an object consists of a number of other objects

 ArchiMate dynamic and other relationships

Relationship Definition
Flow Describes the exchange or transfer of, for example, information or value between
processes, function, interactions, and events

Triggering Describes the temporal or causal relations between processes, functions,

interactions, and events

Grouping Indicates that objects, of the same type or different types, belong together based
on some common characteristic

Junction Is used to connect relationships of the same type

Specialization Indicates that an object is a specialization of another object

ArchiMate layered view example
ArchiMate motivation extension metamodel
 ArchiMate motivation extension concepts

Concept Definition
The role of an individual, team, or organization (or classes thereof) that represents
their interests in, or concerns relative to, the outcome of the architecture

Something that creates, motivates, and fuels the change in an organization

The outcome of some analysis of some driver

An end state that a stakeholder intends to achieve

A normative property of all systems in a given context, or the way in which they
are realized.

A statement of need that must be realized by a system

A restriction on the way in which a system is realized

 ArchiMate motivation extension relationships

Relationship Definition
Aggregation (decomposition) Models that some intentional element is divided into multiple intentional elements

Realization (means-end) Models that some end is realized by some means

Specialization Indicates that an object is a specialization of another object (of the same type)

Association Is re-used from the ArchiMate Core to relate stakeholders to concerns, concerns
to assessment, and assessments to goals

Influence Models that some motivational element has a positive or negative influence on the
+/- realization of another motivational element
ArchiMate motivation extension metamodel
ArchiMate implementation & migration extension metamodel
 ArchiMate implementation & migration extension concepts

Concept Definition
A series of actions designed to accomplish a unique goal within a specified time

A precisely defined outcome of a work package

A relatively stable state of the architecture that exists during a limited period of
time

An outcome of a gap analysis between two plateaus

ArchiMate implementation & migration extension example model
Building Strong Organizations

Managing complexity and change, flexibility and agility, faster time-to-market, improving
competitive standingBiZZdesign makes strategy work! BiZZdesign offers complete and
integrated solutions to design and improve organizations: effective, proven and focused on
results. The primary goal: business agility.

Our integrated solutions consist of user-friendly tools, best practice models and methods,
training and consultancy for:
Enterprise Architecture Management
Business Requirements Management
Business Model Management
Business Process Management
Governance and Risk Management

BiZZdesign is an innovative and leading knowledge organization, continually striving to

deliver added value to our customers. Our solutions are inventive. BiZZdesign supports
open standards and actively participates in The Open Group (TOGAF, ArchiMate).
BiZZdesign works closely with research centers, universities and market organizations.
Companies and organizations all over the world already benefit from BiZZdesigns tools,
consultancy and training.

For more information about our solutions and locations worldwide, please visit:
www.bizzdesign.com

For more information about the opportunities for your organization, please email us at
[email protected] or call: +31 33 7600 280