Data is everywhere.
Access shouldn't be complicated.
SPIDEX simplifies the path from physical data sources to enterprise applications through a device-agnostic, industry-agnostic technology stack.
The world doesn't have a data problem.
It has a data access problem.
The data already exists. Reaching it is what costs — and the cost does not amortise.
Between you and one sensor's reading
- 01Custom driver
- 02Protocol conversion
- 03Vendor SDK
- 04Gateway integration
- 05Data transformation
- 06Cloud connector
- 07Device management
- 08Maintenance
Now do all eight again for the next source.
And again for the one after that.
No matter where the data comes from.
Integrated by hand, every one of these is its own piece of work — a device type, on a transport, in a sector, for an application. Stop counting device types at 13 and transports at 9, well short of either real figure, and across 5 sectors that is already 585 of them.
One block per sector · 9 transports across × 13 device types down
One path through all of them.
SPIDEX · acquire · normalise · deliver- 01No matter the deviceany product type
- 02No matter the protocolany transport
- 03No matter the sensorany payload
- 04No matter the vendorany manufacturer
- 05No matter the industry5 sectors
- 06No matter the applicationany consumer
Democracy
of data.
Data should not be privileged by the circumstances of its own creation. A reading from a thirty-year-old controller is not worth less than one from a device shipped last quarter — it is only harder to reach.
Data should not be privileged based on
- ·Which vendor generated it
- ·Which hardware produced it
- ·Which protocol transported it
- ·Which industry owns the equipment
- ·Which generation of technology produced it
- ·Which application eventually consumes it
Democratising access to data acrossdevices, systems and industries.
A layered technology stack for the physical world.
What the data was for
- Analytics
- Automation
- AI / ML
- Dashboards
- Enterprise
- Custom
Device and platform operations
- Provisioning
- Monitoring
- Configuration
- OTA
- Diagnostics
- APIs
Where difference stops mattering
- Normalisation
- Common models
- Events
- Metadata
- Device state
- Context
Common communication & control
- Communication
- Control
- Abstraction
- Telemetry
- Diagnostics
- Security
- Lifecycle
Where acquisition happens
- Gateway
- Protocol translation
- Edge compute
- Local rules
- Buffering
However it already talks
- BLE
- Ethernet
- Wi-Fi
- Cellular
- RS485
- UART
- CAN
- MQTT
- OPC-UA
The physical world
- Sensor
- Machine
- PLC
- Vehicle
- Meter
- Camera
- RFID
- Asset
- Facility
- Legacy
Layer by layer
Data sources
The physical world
- Sensors
- Machines
- Devices
- Vehicles
- Assets
- Infrastructure
- Legacy systems
Connectivity
However it already talks
- BLE
- Ethernet
- Wi-Fi
- Cellular
- RS485
- UART
- CAN
- MQTT
- OPC-UA
Device & edge
Where acquisition happens
- SPIDEX devices
- Gateways
- Edge computing
- Protocol translation
- Local processing
- Communication
- Control
- Device abstraction
- Telemetry
- Diagnostics
- Security
- Lifecycle
Data
Where difference stops mattering
Built by SPIDEX- Normalisation
- Common models
- Telemetry
- Events
- Metadata
- Device state
- Context
- Management
- Monitoring
- Configuration
- OTA
- Diagnostics
- Security
- APIs
Applications
What the data was for
- Enterprise systems
- Analytics
- Automation
- AI/ML
- Dashboards
- Custom applications
SPIDEX separates the complexity of data acquisitionfrom the applications that need the data.
From physical signal
to usable enterprise data.
One reading, tracked the whole way. Watch what it carries at each stage — the complexity does not disappear, it moves into the platform.
- ·ADC 0x0A3F
- ·raw · 12-bit
- ·no timestamp
- ·no identity
Illustrative payload · shapes shown, not live data
Industrial data,
without industrial complexity.
A plant, a warehouse or a facility already produces everything needed to run it better. It produces it in six incompatible ways, on equipment installed two decades apart. Pick a source and follow what it becomes.
PLC · Modbus TCP
A SPIGWAY gateway running C3F polls the holding registers over Modbus TCP. The PLC program is not modified and no vendor SDK is involved.
Equipment already on the floor
- PLC · Modbus TCP
- SCADA · OPC-UA
- Energy meter · Modbus RTU · RS485
- Rack sensors · BLE
- Forklift · CAN · cellular
- Legacy panel · Dry contacts · serial
Common communication & control framework
Runs on the device and gateway
Normalise · contextualise · deliver
What operations actually uses
- Insights
- Dashboards
- Alerts
- Work orders
- ERP / MES
Pick a source
Holding registers 40001–40012 · counts, state word, fault bits
cycle.count · line.state · fault.code, typed and timestamped
Cycle time drifting 4% slower across the shift
Maintenance work order raised against the sealing head
Illustrative journeys · shapes shown, not measured figures
Connect what already exists.
Build what comes next.
Complexity belongs in the platform. Not in every application.
SPIDEX does not eliminate the physical diversity of the world — nothing can. It absorbs that diversity, once, so that every project above it does not have to.
Rebuilt per project
- 01Device
- 02Custom driver
- 03Custom gateway
- 04Custom data format
- 05Custom cloud
- 06Custom application
Six stages · repeated for every source
Built once
- 01Device
- 02SPIDEX
- 03Unified data
- 04Application
Four stages · reused for every source
Absorbed by the platform
- Protocol differences
- Hardware differences
- Communication differences
- Device lifecycle
- Connectivity
- Data normalisation
- Device management
- Security
- Remote operations
Every item here is work an application team would otherwise carry themselves, on every project, for the lifetime of the deployment.
The data source shouldn't dictate the architecture.
SPIDEX hardware is part of the ecosystem, not a precondition for it. The platform is designed to absorb differences in hardware, vendor, gateway, sensor and generation of equipment.
- ·SPIDEX hardware
- ·Third-party hardware
- ·Existing equipment
- ·Custom devices
- ·Legacy systems
- ·Mixed estates
Use what you have. Build what you need.
Connect what comes next.
Different worlds. Same problem underneath.
The equipment changes completely from one sector to the next. The work of reaching its data barely changes at all.
See the sectors in detail →Devices are how the platform
reaches the physical world.
SPIDEX hardware exists to open a path to data that would otherwise stay shut. Each family is a different way into the same stack — not a separate product line with its own architecture.
SPIGWAY
L03 · Device & edgeIndustrial and enterprise gateways. They aggregate devices at a site, convert protocols, run edge logic and hold the secure link back to SPIEngine.
- Acquires
- Site equipment over industrial and wireless interfaces
- Delivers
- Aggregated, protocol-converted site data
BLEPSI
L01 · Data sourceBattery-operated BLE sensing and proximity devices for environments where running cable is not an option.
- Acquires
- Environmental and proximity readings where cable cannot run
- Delivers
- Battery-operated telemetry over BLE
LiNT
L03 · Device & edgeBridges that bring existing industrial equipment onto the platform without replacing it — Modbus, RFID and sensor interfaces that speak C3F on the platform side.
- Acquires
- Equipment that predates the platform — Modbus, RFID, sensors
- Delivers
- Brownfield assets speaking C3F
TiTA
L01 · Data sourceConnected telemetry and tracking units for assets and vehicles that move, including direct vehicle-bus telemetry.
- Acquires
- Position, movement and vehicle-bus telemetry
- Delivers
- Location and asset state from things that move
Timing & Specialised Systems
L03 · Device & edgeNetwork timing and specialised systems built on the same SPIDEX foundation, for environments where accuracy and reliability are the requirement.
- Acquires
- Network time and specialised system state
- Delivers
- Precision timing across the estate
Once the data is accessible,
everything above it becomes easier.
The path, not the product category
- 01AcquireConnect to physical data sources, whatever they are.
- 02NormaliseConvert heterogeneous device data into a common representation.
- 03UnderstandAdd device, asset and contextual information.
- 04OperateMonitor and control devices across the estate.
- 05IntegrateExpose the data to enterprise systems.
- 06BuildCreate applications on top of one unified data layer.
What teams build on it
- Analytics
- Automation
- Digital twins
- Predictive maintenance
- Asset intelligence
- Remote operations
- Business intelligence
- AI and ML
SPIDEX does not ship these. It removes the reason they are hard to start — the months of acquisition and integration work that sit between an idea and the first useful reading.
The physical world is diverse.
Your data architecture isn't.
SPIDEX provides a flexible, device-agnostic and industry-agnostic technology stack for acquiring, normalising, managing and delivering data from the physical world to the applications that depend on it.