DSM (Global Dutch leader in nutritional ingredients)

Back to / research home / research data

On this page, you will find the submitted architecture principles for the research.

Overview of the uncut submitted DSM Organization Architecture Principles

(IT) Architecture Principles

DSM's approach to IT system and service development is based on the following architecture principles to ensure alignment of IT strategies with business strategies and visions:

  1. DSM uses internet technology to connect end-nodes and strives for zero DSM-footprinted end-user devices, also called the Internet Centric concept.
  2. DSM IT provides on-demand services that can be charged based on the usage of a user or business/service group, also called the On-Demand principle.
  3. DSM IT services can be consumed with any tool, any product, or any device, which is common in the IT consumer market, also called Consumerization.
  4. DSM IT provides rich end-user services for transparently accessing information. These services can be easily added, changed, or removed, the so-called Orchestrated Services.

(IT) Design Principles

  1. Use standard out of the box available IT solutions wherever possible; reduce variations (Standardization ) and lower TCO.
  2. Simple IT services are preferred over more complex ones from an end-user and maintenance perspective, which includes intuitive operation and intuitive user interface (Simplification).
  3. Where synergy is possible, IT services are shared across organizational boundaries (Share Unless), i.e., design / IT solution selection should proactively consider this.
  4. IT aligns with the business strategy and focuses on realistic next steps based on a roadmap taking into account the maturity of new solutions available on the market (Evolutionary Implementation).
  5. IT services are designed and built as independent service blocks(Independent Service Blocks); IT services can be constructed using different solution building blocks.
  6. IT services must be designed for operations and should be as independent as possible from where they are used and from which geographical place they are delivered. They should be easy to maintain and enable the users to support themselves and maintainable via remote support (Minimize On-Site Support).
  7. IT services must be designed, implemented, and contracted to ensure compliance with architecture, validation, managed operations, and IT security aspects (IT Responsibility).
  8. IT services must be easily transferable to other providers or deployment models, which should be reflected in all contracts with (external) service providers (Transferable Services).
  9. IT services need to be integrated with strong information (security) management practices (Information Oriented).
  10. Data is an asset that has value to DSM and is managed accordingly (Data is an Asset).

This is open data published publicly. It does not mean you can own or use it as you wish. If you want to use this data in any commercial form, you can only do so with the owner's prior written consent. Please get in touch with mark.paauwe@dragon1.com for more information.

Architecting Solutions

DEMO: Concept Mapping Software

How to use Dragon1 EA Tool

Learn to generate architecture diagrams using repositories
DEMO: BPMN Onboarding Process Example

DEMO: BPMN Onboarding Process Diagram - Measure Rules Compliance

Manufacturing, Financial Solutions
DEMO: Enterprise Architecture Blueprint Template

DEMO: Generate an Enterprise Architecture Blueprint to discover and solve RISK

Banking, Logistics, Healthcare
DEMO: Data Mapping Software

DEMO: Generate Application Portfolio Diagram

Automotive, Financial Services, Health Care
DEMO: Strategy Mapping Software

DEMO: Generate Strategy Map on how to INNOVATE with AI

Government, Logistics, Banking
DEMO: Process Application Map

DEMO: Generate Landscape for RPA AUTOMATION

Retail, Agriculture, Energy, Oil & Gas