SEO Description: Build an auditable humidity point schedule linking installed sensors, controller channels, units, quality states and BMS tags for project handover.

SEO Keywords: BMS humidity point schedule, humidity sensor tag naming, building automation handover, industrial sensor point mapping

Language Versions: 中文 | Español | Русский | Português | Français | Deutsch | Bahasa Indonesia | ไทย | Tiếng Việt | العربية

A humidity reading can be electrically correct and still be attached to the wrong room, unit or control-system tag. The point schedule is the contract that connects the installed instrument to the information used by operators. It should be controlled alongside the panel drawings and software configuration, not assembled only at handover.

For integrators and engineering contractors, clear point identity prevents ambiguity when a probe is moved, replaced or serviced. This guide describes a project documentation workflow. It does not claim that a Nexisense transmitter automatically provides a particular BMS protocol, cloud service or naming convention.

Application Requirements for System Integrators

A multi-room monitoring project needs a stable association between location, instrument identifier, controller channel and displayed point. A packaged air-handling unit needs a boundary between the OEM tag and the site BMS tag. Assign the responsibility for maintaining that association before interfaces are commissioned.

Avoid using an electrical address as the only physical identity. Addresses and channels can change during maintenance. Conversely, a room label can change without the device changing. The schedule should retain enough information to distinguish equipment identity, measurement location and software mapping.

Nexisense Product Reference

Nexisense publishes the HG803 as a temperature and humidity measurement product. The linked product reference identifies the catalog configuration and the table separates its published information from project checks. Obtain the order-specific drawing and specification before procurement. Related product photos are references, not proof that different probes or housings are interchangeable.

Product specification (English): HG803

Product Parameters and Procurement Checks

Selection Guide

Request the ordered output definition, units, available status information and any register documentation needed for the interface. RS485 is not evidence of a particular building protocol. If a gateway is required, specify its mapping and ownership separately from the sensor purchase.

Agree the site naming convention and required metadata with the operator. Include measurement quantity, unit, location, asset identity, receiving channel, valid range and maintenance owner. Alarm settings and reporting requirements should refer to the same approved point identity.

Integration, Installation and Commissioning

Verify each point from the physical device to the displayed BMS tag using an approved commissioning method. Check that temperature and humidity have not been interchanged and that engineering units and scaling match the supplied interface. Retain a witnessed result for the mapping, not just a screenshot of plausible values.

Document data-quality and maintenance states. A normal-looking number without a reliable identity or validity state is not sufficient for an auditable handover. Where a gateway renames or transforms points, preserve the source mapping and configuration version.

After a device replacement or location change, update the schedule, drawings and interface configuration together. Keep a revision history so historical trends can be interpreted against the location and equipment that existed at the time. Do not silently reuse an abandoned tag for a different quantity.

Illustrative Engineering Application

Illustrative engineering example: a contractor hands over humidity points for a production building. The schedule links each labeled probe to a controller channel and displayed tag, with units and maintenance ownership. A witnessed mapping test resolves an exchanged room label before release. This is a hypothetical documentation workflow, not a reported customer project or measured outcome.

Why Consider Nexisense

Nexisense provides published product references that can support a structured technical discussion. Submit the operating conditions, interface needs and acceptance scope for configuration review. Base purchasing approval on confirmed documentation and the required project evidence, not on photographs or an assumed capability shared by every variant.

Frequently Asked Questions

Q1. Is a controller address a sufficient sensor identity?

Not by itself. Addresses may change, and the physical measurement location must remain traceable. Link asset identity, location, channel and software point in the controlled schedule.

Q2. Does RS485 guarantee a native BMS connection?

No. Confirm the delivered protocol and the BMS interface. A gateway or controller mapping may be needed and should be specified as a separate integration responsibility.

Q3. Should units be written into the point schedule?

Yes. The schedule should identify the quantity and engineering unit, along with the receiving definition. A plausible number is not proof that scaling and quantity mapping are correct.

Q4. Can a screenshot prove point mapping?

A screenshot alone may show only a plausible value. Use an approved test that demonstrates the association from the physical measurement point through the receiving system to the displayed tag.

Q5. Who owns gateway transformations?

The project should assign that responsibility explicitly. Preserve source point names, transformation rules and configuration versions so operators can trace the displayed information.

Q6. Can an old tag be reused for another measurement?

Not silently. Reuse can make historical trends misleading. Follow the site naming and change-control policy and preserve the earlier identity in the record.

Q7. What changes after probe relocation?

Review location, asset association, drawings, software mapping and any affected alarm or reporting assumptions. Keep the revision history so earlier data remains interpretable.

Q8. What is the minimum handover evidence?

Use the project specification to define it. A controlled schedule, interface documentation, mapping test, configuration version and responsible owner form a practical starting point, not a universal compliance claim.

Summary

Treat humidity point identity as a controlled integration deliverable. Link physical location, device, receiving channel, units and displayed tag, then verify that mapping. Preserve quality states and revision history so future maintenance does not undermine the meaning of historical data.

Further Reading: Related product specification (English); Temperature and humidity product range (English)