Collect close to the source
Place the edge agent on the device network to poll sensor values and prepare data locally.
Services / Hawkeye Ai Subscription
Hawkeye Ai. Data centre and IoT monitoring.
A subscription service for edge monitoring and telemetry in data centre and IoT environments. Connect device data, local processing and central monitoring through an on-premises or cloud architecture.
Field devices Edge agent
MQTT / HTTP
Hawkeye AiEdge monitoring & telemetry
Operational overview On-premises / cloud
Sensor trends
MonitoringDevice configuration Alerts
Collect · Process · Monitor
Illustrative workflow · Example telemetryIntelligence at the edge
Connect your devices to a clearer operational view.
Hawkeye Ai brings sensor acquisition, local transformations and downstream monitoring into one telemetry workflow. The documented platform has been demonstrated through prototype and proof-of-concept work; production scope is agreed for each deployment.
Choose your destination
Route telemetry to on-premises systems or a cloud gateway according to your infrastructure needs.
Support operational action
Use monitoring, alerts and device management to help teams understand and respond to operational conditions.
How it works
From sensor readings to monitoring.
- 1
Connect & configure
Register devices and define communication parameters, then connect the edge gateway to the device network.
- 2
Poll & process
The edge agent polls device readings, processes values, applies transformations and attaches metadata.
- 3
Forward & store
Send telemetry over MQTT or HTTP to the gateway. Store sensor data and device configuration in the corresponding data stores.
- 4
Monitor & manage
Present operational data in the web application, with alerts, configuration and device management.
Platform capabilities
A connected edge monitoring workflow.
Core capabilities and optional integrations described in the product architecture.
Data centre monitoring
Bring operational sensor and device data into a web application for monitoring, alerts and day-to-day visibility.
Modbus device connectivity
Collect device values using Modbus TCP/RTU. Other protocol requirements can be reviewed against the supported integration scope.
Local edge processing
Run the edge agent close to monitored devices to poll values, process readings and prepare telemetry for downstream systems.
Transformations & metadata
Apply transformations to collected values and attach metadata before forwarding the data to the gateway.
On-premises or cloud gateway
Forward telemetry through MQTT or HTTP to an on-premises or cloud gateway, based on the selected architecture.
Time-series data storage
The demonstrated architecture uses InfluxDB for sensor telemetry and MySQL for device configuration.
Device configuration & management
Use the application layer to configure and manage devices alongside monitoring and alerting workflows.
Optional CCTV integration
CCTV streams can form part of an agreed surveillance integration. Device compatibility and video requirements are defined for the project.
Optional actuator integration
Connect actuator control as an optional automation path. Control permissions, safety interlocks and operating requirements need project-specific assessment.
Deployment planning
Shape the platform around your environment.
Review device compatibility, register formats, polling needs and network requirements before defining the production deployment.
Edge hardware options
Raspberry-based and Lenovo-based edge configurations have been demonstrated. Select hardware after assessing your device and processing requirements.
Availability architecture
The documented design presents Rancher Kubernetes for edge high availability. Cluster topology, failover behaviour and recovery objectives require deployment-specific definition.
Automated deployment approach
The platform design includes a DevOps-led deployment approach. Agree the delivery pipeline, release process and rollback requirements with your operations team.
Subscription enquiry
Explore Hawkeye Ai for your environment.
Discuss subscription options for your devices, sensor protocols, monitoring goals and preferred deployment location.
What environments is Hawkeye Ai designed for?
The platform is positioned for data centre monitoring, IoT and edge telemetry, connecting field devices to on-premises or cloud monitoring systems.
Which device protocols are documented?
Modbus TCP/RTU is explicitly documented. Other protocol support must be confirmed against your device list and integration requirements.
What happens at the edge?
The edge agent polls devices, processes readings, applies transformations and adds metadata before forwarding telemetry to the gateway.
Are CCTV and actuator control included in every deployment?
No. They are optional integration paths. Compatibility, control authorisation, safety requirements and surveillance scope are assessed for each project.
What capacity and availability can we expect?
Hardware sizing, polling rates, device capacity, availability targets and support scope need assessment for the intended deployment. Prototype and proof-of-concept results are not a universal capacity or uptime guarantee.
How do we plan a production rollout?
Start with device and protocol assessment, validate register mappings and data formats, then agree security controls, storage, availability, deployment operations and acceptance criteria.
Explore further
Services around Hawkeye Ai.
Discuss your requirements with Benchmark Infotech in Kuala Lumpur, Malaysia, and explore services relevant to your project.