Quantbit's BMS connector for ERPNext CFMSX reads operational data from BACnet, Modbus, or MQTT-enabled building management systems — HVAC status, equipment run-hours, energy consumption, water flow readings, and access control events. This data triggers maintenance work orders in ERPNext automatically when equipment crosses service thresholds, updates asset run-hour logs, and generates energy consumption records for utility billing. Facility managers get live building data inside ERPNext without needing to switch to a separate BMS dashboard for routine checks.
Yes. Quantbit's GPS connector for ERPNext ConstruX integrates with GPS tracking devices installed on JCBs, cranes, transit mixers, and other construction equipment. Location, movement history, ignition status, and idle time are pulled into ERPNext and linked to the construction project and equipment asset record. Geofence alerts fire in ERPNext and via WhatsApp when equipment leaves the designated site boundary. Fuel consumption and engine hours are tracked against work orders for accurate project cost allocation.
Connect building management systems, GPS-tracked equipment, IoT sensors, and access control systems to ERPNext ConstruX and CFMSX. Site progress, asset health, and maintenance needs update in real time — not on the next site visit.
Construction and facility management generate enormous amounts of field data — from GPS coordinates to HVAC sensor readings. Our connectors bring that data into ERPNext so decisions are made on facts, not on what someone remembered to report.
Building Management Systems control and monitor HVAC, lighting, fire, and utility systems. Our connector reads BMS data and converts operational events into ERPNext maintenance records, asset logs, and energy entries.
Construction equipment — cranes, excavators, concrete mixers, generators — is expensive and mobile. GPS tracking connected to ERPNext gives you visibility into where your equipment is, how hard it is working, and when it needs service.
Modern construction sites and managed facilities deploy IoT sensors to monitor conditions that affect safety, quality, and compliance. Our connector brings sensor readings into ERPNext where they belong — linked to the asset or location they describe.
Who entered which building, which floor, and at what time — this data is crucial for security compliance, contractor billing, and COVID-style occupancy management. Our connector links access control events to ERPNext visitor, employee, and contractor records.
For construction companies using BIM or project management platforms, our connector links milestone completion, material usage, and subcontractor progress reports to ERPNext project and billing records.
For LEED-certified buildings, government-mandated energy reporting, or simply for controlling utility costs in large facilities, energy meter data from smart meters and sub-meters feeds into ERPNext CFMSX automatically.
The integrations look similar on the surface — GPS, IoT, sensors — but the ERPNext documents they create, and the workflows they automate, are quite different for a construction company versus a facility management company.
For developers, contractors, and EPC companies — integration is about tracking what is happening on site and ensuring that site-level data flows into project costing, billing, and procurement in ERPNext without delays.
For FM companies managing commercial, industrial, or residential properties — integration is about knowing the state of every asset and every system, and turning that knowledge into proactive maintenance before failures occur.
Construction and facility management are industries where decisions are made in the field but recorded in the office — often hours or days later, often incompletely. These stories are about closing that gap.
A facility management company in Muscat manages HVAC systems across 28 commercial buildings under a performance-based FM contract. Their contract specified maximum downtime per cooling unit. When a chiller fails in the peak of Oman's summer — when outdoor temperatures are above 45 degrees — a response in hours rather than days is the difference between keeping the contract and losing it. Before BMS integration, the way they knew a chiller had a problem was when a building occupant called to complain about the temperature. By that point, the chiller had typically been in an abnormal state for one to four hours. After the BMS integration connected each building's Johnson Controls system to ERPNext CFMSX, any equipment fault or out-of-range parameter generates an ERPNext maintenance work order immediately — and a WhatsApp alert goes to the assigned technician and the FM supervisor within two minutes. The technician is dispatched before the building occupant even notices the temperature change. In one incident during August, a compressor fault was flagged at 2:14 AM. A technician was on-site by 3:40 AM and the unit was back to normal by 5:20 AM. The building occupants arriving at 8 AM noticed nothing. Under the old process, the same fault would have resulted in a six-hour outage and a contract penalty clause being triggered.
A mid-sized construction company in Pune was running four concurrent projects across the city — two residential towers, one commercial complex, and a road widening project. They owned a fleet of seven JCBs, three transit mixers, and two cranes. Equipment deployment was managed by a dispatcher over phone calls. By the end of the month, when the accounts team tried to allocate equipment costs to the right projects for billing purposes, the records were a mess. One JCB had been on loan between projects three times in a month and nobody had updated the dispatch register accurately. Equipment cost allocation was essentially guesswork — and since these costs went into the billing to clients, incorrect allocation meant either overcharging one client or undercharging another. After GPS devices were installed on all heavy equipment and integrated with ERPNext ConstruX, location data is pulled every fifteen minutes and matched to the geofence of each project site. Equipment cost allocation happens automatically — if the JCB was at the commercial site for six hours and the residential site for two hours, ERPNext allocates 75% of the day's cost to the commercial project and 25% to the residential. No dispatcher records to reconcile, no arguments with clients about equipment deployment, no month-end guesswork.
A property developer in Mumbai managing a partially occupied commercial tower during construction finishing work had two diesel generators — one for the construction team's tools and temporary systems, and one dedicated for the server room and security systems. The construction generator ran out of fuel during a Saturday afternoon, which in itself was manageable. The problem was that someone had already switched the server room generator to the construction circuit the previous day to handle a load test, and had not switched it back. When the construction generator died, the server room lost power too. By the time anyone figured out what had happened, the CCTV system, the access control panels, and the fire alarm monitoring system had all gone offline for four hours on a weekend. The building's insurance required continuous monitoring, and the outage triggered an incident report. After IoT fuel level sensors were integrated with ERPNext CFMSX, fuel levels below 25% trigger an automatic purchase order for diesel refilling and a WhatsApp alert to the facilities coordinator. The generators now get refueled before they reach critical levels — and the fuel level history in ERPNext provides an audit trail for insurance purposes.
A facility management company in Bangalore was managing a large IT campus under a manpower supply model — they provided cleaning, security, and technical maintenance staff whose billing was based on attendance. The billing department was receiving attendance registers from site supervisors by WhatsApp every evening — handwritten sheets, photographed, and sent. The accounts team would count the names manually and raise a monthly invoice. The client — a major IT firm — was beginning to query the attendance numbers because their own building access control system showed lower numbers than what the FM company was billing. An audit revealed that the site supervisors were inflating attendance by five to eight percent on average. After access control integration was deployed at all campus entry points, attendance is captured automatically by the access control system and flows directly into ERPNext as the basis for subcontractor billing. The attendance register WhatsApp photos are no longer accepted as billing documentation. Billing became verifiable, the client disputes stopped, and — unexpectedly — the FM company discovered they were actually deploying more staff than they were billing for on two days of the week, which they were able to correct and recover revenue from.
A residential developer in Kolhapur was experiencing inconsistent concrete quality across floors of a building — some floor slabs showed minor surface cracking that their structural engineer attributed to inadequate curing under high-temperature conditions. Concrete needs to be kept moist and at a controlled temperature for seven to fourteen days after pouring to reach its design strength. Whether curing was being done correctly depended entirely on the site supervisor remembering to instruct the labour and checking visually. There was no record, no measurement, and no accountability. After IoT temperature and humidity sensors were installed at concrete pour locations and integrated with ERPNext ConstruX, readings are logged every thirty minutes against the work order for each pour. If temperature exceeds 32 degrees or humidity drops below 80%, an alert goes to the site supervisor via WhatsApp from ERPNext. The curing record is automatically documented in the work order, providing evidence for quality certification. The structural engineer signed off on the curing protocol in the first building where it was used and noted that it was the most systematic curing documentation they had seen on a mid-market residential project.
A facility management company in the GCC was responsible for lift and escalator maintenance across twelve commercial properties. Lifts in the UAE and Oman require periodic statutory inspections by approved inspection authorities — typically every six months. Managing inspection schedules across forty-two lifts in twelve buildings, each with a different last-inspection date, was handled through a shared Excel calendar maintained by the compliance coordinator. She did her best, but with annual leave, sick days, and competing priorities, a lift in one building slipped through — its inspection was six weeks overdue before a routine audit caught it. The building owner received a notice from the regulatory authority. After integration connected lift run-cycle counters from the BMS to ERPNext CFMSX, each lift's maintenance and inspection schedule is tracked automatically. ERPNext generates a maintenance work order sixty days before the statutory inspection due date, escalates it at thirty days, and sends a daily reminder at seven days. The compliance coordinator now manages exceptions rather than the entire schedule. In the twelve months since go-live, no statutory inspection has been missed across any of the forty-two lifts.
Construction sites lose connectivity. BMS controllers crash and restart. GPS devices lose signal in underground car parks. Our connector architecture is built for these realities — not ideal conditions.
Tell us about your properties — how many buildings, what BMS systems, what equipment you track. We will design an integration that fits your operational reality, not a textbook scenario.
Book a Free Site Integration Assessment →