See what's happening across your factory.
Collect electricity, water and operational telemetry at the edge. Preserve it during connectivity interruptions and structure it consistently across individual equipment and multiple sites.
Start with the questions you can't currently answer.
Telemetry only matters when it helps explain what is happening in the factory. Utility monitoring is the starting point, not the destination.
Start without another factory-network integration project.
The current prototype uses LoRaWAN sensors with an independent cellular backhaul, allowing the first telemetry deployment to operate independently of existing production IT and OT networks.
Useful data can start flowing before requesting access to PLCs, historians, databases, or production systems. Those conversations can happen later, when there is a reason for them.
Telemetry Fabric is not tied to LoRaWAN. The edge uses general-purpose compute, so additional protocols and software integrations can be developed as requirements become clear.
Flexible by design.Start with a focused measurement problem. Explore production context and further data sources only where they would make the information more useful.
The factory doesn't stop when the internet does.
Data is collected and persisted at the edge, so a temporary loss of connectivity does not create a gap in the operational record.
Make the data understandable before making it clever.
Measurements are organised within an industrial context so that equipment, areas and sites can be understood consistently. The model is built for a single factory first, with the structure already in place to compare equivalent data across multiple sites as deployments grow.
The sensor data is only the beginning.
Once useful telemetry is available, the next question is which existing production or process information could provide context.
Electricity or water data can show that something changed. Production context can help explain what was running at the time — a product or batch, line state, cleaning cycle, changeover or other site-specific activity. That information may live in PLCs, databases, historians, MES, APIs or something entirely site-specific.
Machine state, counts, alarms and process values where accessible.
Operational information already being captured elsewhere.
Potential production context where interfaces and permissions allow it.
Integrations driven by useful data rather than a fixed protocol checklist.
Built to be extended.
The edge and central services are built on modern Microsoft .NET and run on Linux and containerised infrastructure. General-purpose edge compute leaves room for site-specific integrations as real requirements emerge.
Telemetry Fabric is a software platform, not a fixed hardware appliance. The working prototype runs in a purpose-built edge cabinet. The architecture also leaves room to explore deployment on industrial PCs or other suitable site infrastructure as requirements develop; those alternatives have not yet been validated.
The next capabilities will be shaped by real operational needs identified during manufacturing trials, rather than by a fixed checklist of speculative integrations.
MQTT · REST · TimescaleDB
Integration experience first.
Telemetry Fabric is being developed by a software architect with around 25 years' experience in distributed systems, operational software and systems integration, including NHS clinical messaging integration and message-driven distributed systems in automotive technology. The prototype's electrical design has been reviewed by qualified electrical engineering expertise.
Why build it this way?
Electricity and water are a practical place to start because they can be measured without interfering with production systems. Once the platform is running on-site, other sources such as PLC, production, or batch data can be explored where they provide useful context.
The first cabinet is now running outdoors.
It is collecting test pulses continuously while exposed to normal outdoor conditions. The pulses follow a known hourly pattern, which allows the system to detect if one is missing or received twice. During the trial, the internet connection is deliberately cut. Readings collected during the outage must then reach the central system when the connection returns, with their original timestamps preserved.
Help shape the next stage of Telemetry Fabric.
Telemetry Fabric is a working engineering prototype. Its core edge-to-cloud data collection and recovery mechanisms have been demonstrated, while outdoor environmental validation continues.
We're looking to work with a small number of manufacturing partners to explore practical applications and let real operational challenges guide what comes next.
- Start with a small number of targeted electricity or water measurement points.
- Agree a defined scope, success criteria and trial period with the site.
- Carry out installations in accordance with the site's normal electrical safety and isolation procedures.
- Review the measurements together and identify what they reveal — and what additional production context could explain.
The factory helps shape the next stage. That could mean understanding off-hours consumption, comparing equipment or sites, or exploring production context to interpret the measurements. Additional capabilities would be agreed and scoped rather than assumed to be included in the trial.
Looking for manufacturing pilot partners.
We're looking for manufacturing sites interested in exploring an early trial of independent, resilient industrial telemetry.
Start with a useful monitoring question, agree a limited trial and evaluate the results together. The purpose is to discover where trustworthy measurements and production context can deliver practical value — and use those findings to guide the platform's development.