Capabilities

Research & Development

In plain words: we find out whether something can be built - and how - before it is built for real.

The background is a map of DNT's six areas and the connections between them. Digital Products is connected to Software & AI. Software & AI is connected to Digital Products, Connected Systems, Automation & CTS and R&D. Connected Systems is connected to Software & AI, Automation & CTS and Hardware & Machines. Automation & CTS is connected to Software & AI, Connected Systems and Hardware & Machines. Hardware & Machines is connected to Connected Systems, Automation & CTS and R&D. R&D is connected to Software & AI and Hardware & Machines. This page belongs to R&D.

The problem

When nobody knows yet if it can be done

An idea is promising, but the technology is uncertain, there is no proof that it works, and nobody wants to invest in a full build on a guess.

At a glance

Overview

R&D is how we reduce uncertainty step by step: a concept, small experiments, a prototype, validation against real conditions, and finally a product that can be built and maintained.

We say it clearly when an experiment shows that something does not work - that is a result too.

Where it fits

R&D can start in any of the other areas, and often leads into Hardware & Machines or Digital Products.

R&D

What we build

  1. Concept

    Describing the idea and what must be true for it to work.

  2. Experiment

    Small tests of the riskiest assumptions first.

  3. Prototype

    A working model that shows it can be done.

  4. Validation

    Testing against real conditions and requirements.

  5. Productization

    Turning a proven prototype into something that can be built and maintained.

Systems

Typical system combinations

  1. Concept
  2. Experiment
  3. Prototype
  4. Validation
  5. Product

Illustrative example

Honestly

Is it the right choice?

A good fit when

  • The technology or approach is uncertain
  • Proof is needed before a larger investment
  • A new product is being explored

Probably not the right choice when

  • The solution is already known and proven
  • There is no room to learn from a failed experiment
Technical view

Experiments are documented with setup, data and result, so what was learned stays usable - also when the answer is no.

  • Test setups and measurement
  • Prototypes
  • Documented results

Have an idea that needs proving?

Start a Project