IoT that answers a question you already have.

With a question rather than a sensor. "Which cold room went out of range last month", "what are we still running at two in the morning", "where did that trolley go". Each of those implies a different sensor in a different place, and answering one properly is worth more than instrumenting the whole building and reading none of it. Tell us the decision you want to make and we will work backwards to the smallest installation that answers it.

Yes, and it is the main reason this sits under manufacturing rather than under IT. The tags and cards are made and encoded here, so the tag, the reader and the numbering are specified together instead of being bought from three places and reconciled afterwards. If you already run cards from us for doors or attendance, asset tracking can reuse the same numbering rather than starting a second scheme. The chip side of that is covered on RFID and NFC card manufacturing.

The gateway keeps logging locally and backfills when the link returns, so you get a gap in the dashboard rather than a hole in the record. This matters more than it sounds: the sites that most need monitoring are often the ones with the least reliable connectivity, and a system that silently stops recording during an outage is worse than no system, because you only discover it when somebody asks for the very period that is missing.

Where you run it, yes. Readings and asset movements can land in Vybe ERP so there is one place to look rather than another login and another password. Where you run something else, we can export to it or simply hand you CSV and an API and let your team do the joining. What we try to avoid is leaving you with a dashboard nobody opens because it lives somewhere separate from the system people already have open all day.

You do, and you can export all of it at any time in a format that is useful rather than deliberately awkward. We will tell you plainly where it is stored before anything is installed. If your policy requires it to stay on your own hardware, that is a reasonable policy and the gateway can be configured to keep it there, but it changes the quote and it is better raised at the start than discovered at handover.

It is treated as an event rather than as silence. A sensor that stops reporting raises the same kind of alert as one reporting a bad number, because the failure mode that actually hurts is a dead sensor sitting unnoticed for six weeks while everybody assumes the cold room is fine. Batteries are reported before they die rather than after. Spares are quoted with the installation so a replacement is a swap rather than a procurement exercise.

Quoted, and the site drives it more than the sensor count does. A single cold room is a small job; six buildings with poor connectivity and an energy meter on every panel is not. The survey is where the real number comes from, because cable runs, mounting and how far the gateway sits from the sensors move the price more than the hardware list does. Tell us the site and the question you want answered at sales@vybe.net.in and a figure comes back.