#IoT
IoT development and equipment connectivity
From the physical device to the business system: IoT development carries measurements, alerts and status from your equipment to your applications and, where appropriate, sends commands back to the device.
From the physical device to the business system
Equipment that does not report its status forces people to collect information manually or wait for someone to visit the installation. A device might already take measurements, but its data may never reach the application that needs them. We study which information exists, what is missing and who should receive it in order to act. An IoT project often combines the device and its firmware, a gateway where needed, telemetry, a cloud platform and integration with your systems; not every project needs all of those pieces.
See equipment status, receive alerts and identify problems without being physically present. We connect devices, platforms and protocols to the systems you already use — ERP, CRM and analysis tools — so data reaches the people who need to act on it. The objective is defined by how information will be used, rather than adding connectivity as an isolated feature.
Design the data path and integrate existing systems
We study which information exists and where it needs to go, design the path — protocol, gateway and server — and integrate with your current applications. To assess the work, we need to understand the equipment and protocols involved, such as Modbus, MQTT, fieldbus or other equipment interfaces, the systems consuming the data and the people who should receive alerts.
Connectivity is chosen for the deployment; in our own devices we have worked with LoRa and 4G/NB-IoT, for example. Actual behaviour depends on the environment, devices and available interfaces; a specification alone does not establish it. We therefore review the complete system before proposing integration and check during testing what happens when information is missing or the connection is interrupted.
Test in your operation and agree the scope
Deliverables may include devices reporting to your systems, configurable alerts and access to information where you need it; remote control may be included where applicable. These are indicative deliverables: scope is agreed per project. Not every device supports the same actions, and not every measurement justifies automation.
We can reuse the AITHA platform when it fits or develop the integration around your systems. You do not need to replace your tools to discuss the project. If other suppliers maintain some parts, we coordinate interfaces and responsibilities so that connectivity belongs to a shared architecture.
We work from Madrid, Spain. Send a description of the equipment, the information you lack and the operating environment. We define what should be tested first and which result will support the next decision.
Related services
Connect your equipment to your systems
Tell us which information you need and where it should go.