Robotic Arm FCC Integration
Budget: $750 – $1,500 SGD
I need purpose-built software that will let our Fire Command Centre’s robotic arm monitor and report fires in real time, while acting as the brains that ties every critical life-safety subsystem together and streams updates back to headquarters.
Core behaviours
The application must drive the arm’s patrol sequence, capture video/thermal data, analyse potential incidents, and automatically flag fire events. Its decisions should be based on both the arm’s own sensors and the status of the building systems listed below.
System integrations (must be bi-directional where possible)
• Fire alarm systems
• Emergency lighting systems
• Smoke control systems
• Lift supervisory panel
• Ventilation system
• Public-address (PA) system
• CCTV system
• Sprinkler pump system
Remote HQ updates
HQ requires three data streams: 1) continuous status of the arm (position, task, faults), 2) instant alerts for any detected or confirmed fire, and 3) regular system-health/diagnostic packets. Push methods can be MQTT, REST, or another secure protocol you recommend, but latency must stay under five seconds for alerts.
Acceptance checklist
• Robotic arm completes a full patrol loop and logs data without manual input
• Any subsystem alarm triggers an immediate HQ alert and on-screen confirmation locally and remotely
• Manual override from HQ pauses the patrol instantly and returns control cleanly
• All integrations pass fail-safe tests (power loss, comms drop, sensor fault)
Please build with maintainability in mind—clear code comments, modular structure, and a deployment guide that lets my in-house team replicate the setup in a lab environment before we roll it onto the live FCC floor.
Core behaviours
The application must drive the arm’s patrol sequence, capture video/thermal data, analyse potential incidents, and automatically flag fire events. Its decisions should be based on both the arm’s own sensors and the status of the building systems listed below.
System integrations (must be bi-directional where possible)
• Fire alarm systems
• Emergency lighting systems
• Smoke control systems
• Lift supervisory panel
• Ventilation system
• Public-address (PA) system
• CCTV system
• Sprinkler pump system
Remote HQ updates
HQ requires three data streams: 1) continuous status of the arm (position, task, faults), 2) instant alerts for any detected or confirmed fire, and 3) regular system-health/diagnostic packets. Push methods can be MQTT, REST, or another secure protocol you recommend, but latency must stay under five seconds for alerts.
Acceptance checklist
• Robotic arm completes a full patrol loop and logs data without manual input
• Any subsystem alarm triggers an immediate HQ alert and on-screen confirmation locally and remotely
• Manual override from HQ pauses the patrol instantly and returns control cleanly
• All integrations pass fail-safe tests (power loss, comms drop, sensor fault)
Please build with maintainability in mind—clear code comments, modular structure, and a deployment guide that lets my in-house team replicate the setup in a lab environment before we roll it onto the live FCC floor.