RnD for problems without an obvious solution
We test technical feasibility and build prototypes and custom software for computational tasks, measurements and industrial data.
Core RnD directions
Five directions — from research and prototypes to low-level optimisation and applied computing.
Research and feasibility
Feasibility studies, benchmarks, technology comparison, finding the limits, and prototypes.
Experimental software engineering
Custom libraries, prototypes, computational algorithms, plugins, integrations and experimental components.
Industrial and equipment software
Equipment APIs and SDKs, telemetry, protocols, drivers, edge software, Modbus, CAN and OPC UA.
Low-level and performance engineering
C, C++ and Rust: concurrency, memory, CPU and I/O optimisation, cross-platform libraries.
Scientific and applied computing
Measurement processing, modelling, computational algorithms, scientific software and research problems in computer vision and ML.
Test first, then scale
R&D is needed where the technology, architecture or expected result cannot honestly be defined without research and experiment. We fix the hypothesis, criteria and constraints, compare approaches, build a PoC and form a technical conclusion.
We test whether an idea is technically feasible
We compare approaches and technologies
We build prototypes
We develop custom software
We work with industrial data and equipment at the software level
Low-level development and optimisation in C, C++ and Rust
Scientific and applied computing
We build software around equipment
The client provides the equipment, access to it and its technical documentation. NDDev is responsible for the software layer and integrations.
NDDev / Software
The software layer
APIs, SDKs, telemetry, protocols, drivers, edge software and integrations.
- NDDev’s responsibility
Client / Hardware
Equipment and access
The client provides the hardware, access to it and the technical documentation.
- An external project dependency
From hypothesis to technical conclusion
The order of the checks keeps the context of the original signal and the limits of the equipment.
Context and constraints
We record the task, data, environment, equipment, criteria and risks.
Research plan
We define hypotheses, test methods, metrics and success criteria.
Benchmark and experiment
We build a test setup and compare technologies under real constraints.
PoC or prototype
We implement the minimal system that is enough to test the solution.
Conclusion and next step
We hand over the code, measurement results, conclusions, limitations and recommendations.
Completed projects
NDDev’s research and engineering work around equipment data.
HarvesterLib
A C++20 library for timber harvester measurements: parsing, validation, alignment and extrapolation of the data.
Tell us about the task, hypothesis or equipment
Describe the context, data, constraints and expected result. We will make an initial analysis and propose the next step.
We reply within 24 h
Discuss a project
This form needs JavaScript. Write to us at danil@nddev.it.com.