What is a BMS points list?
Requirements come first. The points list names every value, state, alarm and command exchanged with the system; it records units, read or write access, update behaviour and the responsible equipment package.

Jaipur · Automation
Architecture of building automation system Jaipur is the focus of this local planning guide. Building Automation planning through SmartR Spaces (Pannadhaya Circle) starts with the property stage and the documents already available. For this scope, the first survey brief should identify BMS, Lighting control and Handover; each item is then tied to a room, user action or operating outcome. The branch address establishes where the enquiry is coordinated, not what the building needs. A proposal follows only after drawings, existing equipment and installation access are checked for that Jaipur address.
Concise canonical answer
Interfaces need proof. A building automation system reads sensors and equipment status, applies control logic, sends commands and presents alarms or trends to operators. BACnet can carry data between compatible systems, but a protocol name does not prove that a required point is exposed or writable.
This technical material is generated from the canonical Building Automation page. Editing that source updates every city spoke on the next build.
Shared technical source
Requirements come first. The points list names every value, state, alarm and command exchanged with the system; it records units, read or write access, update behaviour and the responsible equipment package.
Failure needs a tested path. Field controllers should continue their essential sequences when the supervisory interface is unavailable, subject to the equipment design; operator workstations, servers and gateways sit above that local…
Requirements come first. BACnet defines messages and objects for building controls; the project still needs a device-specific point list and conformance information because two BACnet products may expose different capabilities.
Requirements come first. An alarm needs a condition, delay, priority, recipient, acknowledgement rule and return-to-normal state; flooding an operator with repeated low-value alerts is a design failure, even if every alert is…
These modules are rendered directly from the canonical Building Automation record. A verified technical edit there propagates to every city version on the next build.
Technical relationships
These service-specific diagrams come from the canonical technical record; they do not depict a completed local project.
Decision aid
| Layer | Primary job | Failure question |
|---|---|---|
| Field device | Measure or act | Can it be read or operated locally? |
| Controller | Run local logic | Which sequences continue alone? |
| Supervisory layer | Graphics, trends and coordination | How is it restored from backup? |
City-specific planning layer
Branch facts are verified. Community observations, when present, are anecdotal and address-specific; they are not presented as citywide facts.
Evidence scope: The same discussion shows strong area-to-area variation, so the page must not describe outages as universal across Jaipur.
What this service can and cannot address: SmartR Spaces can plan manual fallback, restart behaviour, protected low-voltage supplies and UPS runtime for selected systems. It cannot improve the electricity utility's supply.
Evidence scope: The discussion is brief, gives no verified utility diagnosis and shows that interruption duration differs even within the broader area.
What this service can and cannot address: SmartR Spaces can define critical loads, UPS runtime, restart order, local control and recovery tests for selected low-voltage systems. It cannot prevent grid interruptions or validate the cause asserted in a Reddit reply.
Evidence scope: Replies offered several possible explanations, including accumulated readings and meter error, but none was verified in the thread. The utility meter and bill remain JVVNL's responsibility.
What this service can and cannot address: Where the electrical design permits it, SmartR Spaces can integrate supported submeter data or trends to help a facilities team compare internal loads over time. It cannot certify the revenue meter, adjudicate a bill, diagnose wiring remotely or replace a licensed electrical and utility inspection.
Evidence scope: Replies proposed several unverified causes. The later reading supports a placement issue for that display, not a diagnosis of the AC or a Jaipur-wide cooling condition.
What this service can and cannot address: SmartR Spaces can coordinate representative sensor placement, compare readings with a calibrated reference, document the approved HVAC interface and test occupied-zone behaviour with the mechanical contractor. Automation cannot compensate for an undersized or faulty AC, poor envelope performance or an unverified sensor.
Local planning questions
Start with the rooms or operating zones, the people using them and the outcome required from BMS, Lighting control and Handover. Drawings and existing-equipment details help turn that brief into survey checks.
A survey is needed before the proposal depends on unverified cable routes, mounting positions, power, network reach or interfaces. SmartR Spaces (Pannadhaya Circle) first confirms the address and what must be inspected.
The written scope should list included rooms, selected functions, interface responsibilities, exclusions and the acceptance test for each promised outcome. Product names alone are not an approval record.
Give BMS, Field devices, Points lists, HVAC interfaces, Lighting control, Metering their own drawing note, schedule row or decision reference where they affect the installation. The record should show the intended location, control or connection, responsible trade and unresolved dependency before ordering begins.
Installation context
Representative photography supports planning; it is not presented as a completed SmartR Spaces project in Jaipur.


Verified branch
Confirm availability before visiting.
Continue planning