Products built for the floor, not the demo table.
Development of industrial products and connected systems, covering rugged electronics, embedded firmware, IoT connectivity, cloud services and AI-enabled features from pilot through deployment.
What “industrial grade” has to mean in practice
The phrase is used loosely. In engineering terms it comes down to a set of decisions that are taken early, because they cannot be added later without redesign.
- Environment. Temperature range, vibration, dust and moisture ingress, condensation, chemical exposure and electrical noise near motors and drives.
- Power. Real supply conditions rather than a clean bench source: brownouts, surges, switching transients and the behaviour expected when power is lost mid-operation.
- Service life. Equipment that stays installed for years, which changes component selection, connector choice and thermal design.
- Serviceability. Whether a technician can diagnose and replace a unit on site without specialist tooling, and whether spares will still exist.
- Supply chain. Part lifecycle and availability, with second sources considered while the design can still accommodate them.
- Documentation. Enough that maintenance does not depend on the original engineer still being reachable.
What we build
- Connected industrial devices. Custom electronics and embedded firmware for monitoring, control and data collection.
- IoT systems. Devices, gateways, connectivity and backend, designed as one system rather than assembled from parts that were never meant to meet. See IoT development.
- Cloud platforms and dashboards. Ingestion, storage, processing and the operational views the people on shift actually use. See cloud and dashboards.
- AI-enabled features. Analysis that turns collected data into something actionable, placed at the edge or in the cloud depending on latency, connectivity and cost. See AI-enabled IoT.
- Retrofit solutions. Adding sensing and intelligence to equipment already installed and running. See AI for industrial machinery.
From pilot to deployment
A pilot proves the concept on a handful of units, usually with the engineers close by. Deployment is a different problem: units installed by people who did not build them, commissioned in varying conditions, and maintained for years.
The work between those two states is mostly unglamorous and mostly decisive. Provisioning and commissioning procedures. Firmware update paths that survive a failed update. Diagnostics that let someone identify a fault without a debugger attached. Manufacturing test that catches assembly faults before units leave the building. Spares and repair strategy. We plan for these while the design can still absorb them.
Planning for the approvals your market requires
Which approvals apply depends on your product, your market and where it is installed. We design with the relevant requirements in view, prepare the documentation a test house will ask for, and support the testing process.
To be explicit: we are an engineering partner, not a certification body. We do not issue certificates or approval numbers, and any claim of compliance comes from accredited testing, not from us. If your application has specific regulatory or functional-safety requirements, raise them at scoping, because they shape architecture rather than decorate it.
Integration with what you already run
Few industrial products arrive into an empty space. Existing PLCs, SCADA systems, historians, ERP and maintenance software usually have to receive the data or supply it. Integration points, data ownership, protocol choice and behaviour when the other system is unavailable are agreed before development, not discovered during commissioning.
After deployment
Equipment in the field needs a route for firmware updates, a way to investigate faults using data rather than guesswork, and someone who understands the design when something unexpected appears. Ongoing support arrangements are agreed per project; see project support.
Start the conversation
Tell us what the product has to do, where it will be installed and what it has to survive. If you are earlier than that, idea to working prototype is the better starting point.
What does the product have to survive?
Tell us what it must do, where it will be installed and the conditions it has to withstand.
What clients ask before starting
What makes a design industrial grade rather than ordinary?
Decisions taken early about operating environment, power quality, service life, serviceability, part availability and documentation. These cannot be added at the end without redesign, which is why they belong in the architecture stage.
Can you certify our product?
No. We are an engineering partner, not a certification body. We design with the relevant requirements in view, prepare the documentation a test house will ask for and support the testing process, but approval comes from accredited testing rather than from us.
Can the product work with our existing PLC or SCADA system?
Yes, where those systems expose a usable interface. Protocol choice, read or write access, and behaviour when the other system is unavailable are agreed at design time rather than discovered during commissioning.
Do you support the move into manufacturing?
Design for manufacture and assembly, manufacturing test, and the documentation a production partner needs are part of the work. The specific division of responsibility is confirmed in the scope.
What happens when a component goes out of production?
Part lifecycle and second sourcing are considered while the design can still accommodate alternatives. Where a part later becomes unavailable, the documented design makes assessing a replacement a contained piece of work.