Devices & gateways
MQTT · HTTP · TCP / UDP · DLMS / COSEM
+971-58-537-4661Pi IOT HUB / CONNECTED DEVICE OPERATIONS
Add data services to your connectivity offering. Bring multi-vendor device data into branded dashboards, alarms and workflows for enterprise customers.
Pi IoT Hub is developed and supported by Tadam. Explore the Pi product family.
01 / WHY IOT HUB
Equipment suppliers often bring separate platforms, data formats and asset identifiers. A customer with several suppliers needs to relate their readings to the same sites and business records. IoT Hub provides the processing layer for that shared view, for customer services or your own operations.
YOUR EXISTING SOURCES
MQTT · HTTP · TCP / UDP · DLMS / COSEM
Data through supported interfaces
Non-IP data and device events
Asset registers, locations and rollout plans
INDEPENDENT OF EQUIPMENT VENDORS
SERVICES FOR YOUR CUSTOMERS
Asset status and telemetry in context
Act on missing data and configured events
Share processed data with external systems
IN PRACTICE / UTILITIES DIGITALIZATION
Give utility customers a reporting service across equipment vendors. Combine rollout plans and asset registers with incoming readings. Build a country map and regional dashboards that compare targets with actual reporting for an agreed period.
Use the program’s planning records to define the target assets and territories.
Calculate which assets provide current readings and how complete their data is over the selected period.
Keep connectivity, reporting and installation acceptance distinct. Show missing or delayed data so teams can investigate gaps.
An example solution configured around your sources, program targets and agreed indicators.
02 / WHAT YOU CAN DO
Separate tenants, organizations and access rights within one installation. Support customer hierarchies with child organizations and their own administrators, organizing devices by organization and location.
Explore devices on a map, in an object tree or as a list. Associate telemetry with locations and assets to build a view across sites and regions.
Build dashboards, explore historical metrics and configure alarms with severity levels and activation delays. Use forecasting and anomaly detection for device data.
Use protocol connectors and a built-in data description language for binary formats. Integrate vendor systems through available interfaces and maintain versioned device profiles for each supported device type.
03 / BUILT TO BE OPERATED
Create transformation and integration scenarios with access to reference data and adjacent enterprise systems.
Create NIDD configurations and MONTE subscriptions through IoT Hub.
Present the service under your brand or a customer brand with white labeling.
04 / A CLOSER LOOK
Define the devices and data sources, customer access, required dashboards, alarms and business integrations. Your commercial offer sets pricing and service commitments; the implementation scope determines which integrations and configurations are delivered.
They can remain and supply data through available interfaces. The integration design determines which readings come directly from devices and which come from existing platforms. New formats or device types may require integration work.
No. Devices and vendor platforms can connect through the other supported protocols and interfaces. SCEF is used when the solution needs supported cellular network capabilities such as NIDD. It provides network access; IoT Hub processes device data and operational workflows.
Firmware and software updates, as well as remote commands, depend on the technical capabilities of the device and its integration. They are not available for every device by default.
Tadam assesses your requirements, integrates Pi IoT Hub with your systems and prepares the solution for production. We support its integrations and configuration, with 8×5 or 24/7 coverage by agreement.
FZCO IFZA Business Park, DDP, Dubai, United Arab Emirates