Start with the operating question
A mapping issue is only useful to investigate when it is tied to a decision: plant control, alarm response, billing, reporting, comfort, export limitation or asset performance. Start by naming the operational question the data is supposed to answer.
This avoids a common trap: treating every missing point as equally important. Some points are critical to control or compliance. Others are cosmetic dashboard fields that should not drive remediation spend.
Separate naming, transport and meaning
A point can have a valid address and still be operationally useless. The diagnostic task is to separate communication failure from naming mismatch, unit mismatch, scaling error, stale polling, gateway translation and poor handover documentation.
The evidence pack should include point lists, gateway configuration, poll rates, screenshots, trend exports, alarm logs and a short description of who currently relies on each data set.
Build a trusted data map
The practical output is a map that labels data as trusted, suspect, duplicated, missing or unknown. That gives suppliers and internal teams a shared reference before any reconfiguration or re-procurement begins.
For complex sites, the map should show the route from field device to controller, gateway, BMS, export file, dashboard and business process. That is where hidden ownership gaps usually appear.