Custom Research and Development
Some technical problems do not have a ready-made solution.
The requirement may involve adapting existing technology, combining products in an unusual way, investigating undocumented behaviour, or proving that an idea is technically possible before committing to a larger project.
WDWD Industries provides technical research and development for unusual software, hardware and systems-integration problems.
When custom R&D is useful
Research and development can be useful when:
- an off-the-shelf product almost meets the requirement but not quite;
- several existing technologies need to be combined in a new way;
- equipment needs to perform a function it was not originally designed to provide;
- a vendor does not expose the interface required;
- technical documentation is incomplete;
- an idea needs to be validated before significant investment;
- a prototype is required to understand the practical constraints;
- the organisation needs to know whether something is possible before deciding what to build.
The first deliverable is often understanding rather than a finished product.
Research before implementation
For unusual problems, starting development immediately can be expensive.
A focused research phase can answer questions such as:
- What interfaces are available?
- What data can be accessed?
- What behaviour can be controlled?
- Are there undocumented protocols or constraints?
- What security restrictions exist?
- What would need to be modified?
- What can be achieved without changing the original equipment?
- What are the technical and commercial risks?
This information can prevent a project from being based on assumptions that later prove incorrect.
Working beyond the intended use
Products and systems are normally designed around a particular intended use.
In some projects, the useful solution comes from understanding the underlying technology well enough to use it differently.
This may involve:
- communicating with an undocumented interface;
- extracting useful data from an existing device;
- creating an adapter around a closed system;
- combining several independent products;
- controlling a device through an alternative interface;
- building a bridge between incompatible systems.
The goal is not modification for its own sake.
The goal is to achieve a practical outcome for the people using the system.
Prototyping
A prototype is useful when the important question is:
> Can this actually work?
A prototype can deliberately ignore some production concerns while proving the core technical idea.
It may demonstrate:
- communication between devices;
- access to required data;
- control of an existing system;
- a new user interaction;
- integration with a backend service;
- feasibility of a particular architecture.
A successful prototype creates evidence that can inform the next stage of the project.
From prototype to usable system
A working technical demonstration is not automatically a production solution.
Further work may be required around:
- reliability;
- security;
- deployment;
- diagnostics;
- maintainability;
- user experience;
- repeatability;
- support;
- scale.
An R&D project should make these distinctions clear so that a successful experiment is not mistaken for a finished product.
Reverse engineering and technical investigation
Some projects require understanding a system where formal documentation is unavailable.
Investigation may include:
- observing network communication;
- inspecting available software interfaces;
- testing device behaviour;
- analysing data formats;
- experimenting with commands;
- comparing behaviour under controlled conditions;
- documenting findings.
Where this work is appropriate, it should be carried out within the legal, contractual and security constraints of the project.
Combining hardware and software
Custom R&D frequently crosses technical boundaries.
A single project may involve:
- electronics;
- embedded devices;
- networking;
- protocols;
- backend software;
- APIs;
- mobile or web interfaces;
- cloud infrastructure.
The difficulty is often not any individual technology but making the complete system behave coherently.
Designing around users
An unconventional technical solution is only useful if it improves the experience of the people who need it.
This may mean adapting technology to fit:
- an established workflow;
- a physical environment;
- an accessibility requirement;
- an operational constraint;
- an existing piece of equipment;
- a user interaction that conventional products do not support.
The technology should serve the requirement rather than defining it.
Example R&D scenarios
Examples include:
- proving that data can be extracted from an existing device;
- creating a custom interface around a specialist piece of equipment;
- adapting consumer or commercial hardware for a different operational use;
- connecting a new user interface to an existing system;
- investigating whether an undocumented protocol can support a required workflow;
- combining several existing technologies into a new purpose-built solution.
What a useful R&D engagement should produce
Depending on the project, the result may include:
- documented findings;
- a proof of concept;
- a prototype;
- an integration method;
- a technical risk assessment;
- architecture recommendations;
- a working implementation;
- a clear explanation of what is and is not feasible.
A negative result can also be valuable if it prevents a larger investment in an approach that cannot meet the requirement.
How WDWD Industries can help
WDWD Industries works on technical problems where the solution is uncertain, unconventional or crosses several disciplines.
Typical work includes:
- feasibility research;
- technical investigation;
- prototyping;
- protocol investigation;
- hardware/software integration;
- custom adapters;
- proof-of-concept development;
- architecture;
- transition from prototype to production.
If you have a technical requirement that does not appear to have an obvious off-the-shelf solution, contact WDWD Industries at https://wdwd.industries/enquiries.