For commissioning providers
See what is actually on the network before you sign for it.
Every point you discover, verify and label is a decision somebody will rely on for thirty years — and today it leaves the site as a PDF. Indagate starts as a read-only day on one live project, and ends as the record the owner runs the building on.
One project. Read-only. One day.
The gateway goes on the network and listens. It discovers every BACnet device that answers, enumerates the objects on each one, and flags which points are writable. You get what is actually there — every device, every point, every name the installer gave it — beside what the drawings say should be there.
That is the list you were going to build by hand over the next three weeks. It is also the first version of the asset model the building will run on, because the names you fix now are the names the record uses from then on.
Read-only means read-only. Nothing in this mode issues a write. The comparison against the design point list is work you do with us, not a report the software generates yet.
Why it is you and not the owner.
You cannot hire. Roughly six in ten operators cannot find a qualified commissioning engineer, and a facility cannot go live without your signature. You are turning down work, and every hour a principal spends walking a point list is an hour off a schedule someone is paying for by the day.
The owner holds the bigger budget and the slower cycle. You hold the acute problem and can decide in a week. So the first project is yours — and the handover package it produces is addressed to the owner, which is what earns the second conversation.
Network access is the question, not interest.
- Read-only by construction in this mode — no write path is enabled
- The gateway publishes over mutual TLS; what leaves the site is configurable before it leaves
- Life-safety priorities 1 and 2 are refused at the gateway even where writes are later granted
- If IT will not permit a live connection at first, a BACnet capture file you produce yourself is a supported starting point
A firm that will not grant read-only access on any project is not an early customer. That is a useful thing to learn in one conversation instead of three months.
What the first project looks like.
- Day 1
- Gateway on the network, read-only. Discovery runs. You have the as-found device and point list by the end of the day.
- Week 1
- As-found beside the drawings. Everything on the network the drawings never mentioned, everything in the drawings that is not on the network, everything mislabelled — worked with your engineer, on your punch list.
- Handover
- The asset model and the verification record go to the owner on a documented schema. Not a binder. The record their operations team starts from instead of rediscovering for three months.
Specifics
- Discovers
- BACnet/IP devices via Who-Is / I-Am; objects and present values via ReadProperty; writable points identified
- Does not
- Write, in this mode. Reconcile against a design list automatically — that is done with you. Touch anything safety-related
- Exports
- Devices, points, names and the verification record on a documented schema, to the owner
Common questions
Will it write to anything during discovery?
No. Discovery is read-only by construction; the write path is not enabled in this mode. Where an owner later grants supervisory writes, priorities 1 and 2 remain refused at the gateway regardless.
Who owns the record at handover?
The owner. It exports on a documented schema while the platform runs and on the way out if it ever stops. You are replacing a binder nobody opens, not creating a new dependency.
Start with one project.
Tell us the project, the controller vendors on it, and whether a live connection is possible. We come back with what day one looks like on that network.