Docs
Assets
A name, a place, and the checks on it. Add assets when a route touches them, not before.
An asset is a thing you stop at. A valve, a trap, a hood, a pole, a drain, a substation. It has a name, a place in words, and the checks that belong to it.
Use the name that is already on the tag or in the crew’s mouth. Do not invent a Tidep code beside a code that is stamped in the metal. If the stamped code is unreadable, say so in the place line and use the name people use, then fix the tag in the real world. The register will not repair a tag.
What you can see
Open an asset and you get the last three readings on each check, the open deficiencies, and the routes that include it. Three readings are enough to see whether today is new. They are not a trend report. If you need the year, export the route. See exports.
What not to import
Do not import the whole plant, the whole pole file, or the whole campus on the first day. Names will be wrong, duplicates will be embarrassing, and the route will become a search box. East Ward deleted a pole sample for this reason and went back to adding poles as the cycle reached them. St. Brice started with the traps in one notebook.
An asset that is on no route is allowed, briefly, while you build the route. If it is still on no route a month later, it is clutter. Remove it or put it on a route. The register is not a parking lot for a drawing extract.
Retiring
Retire an asset when it is gone or when you will not check it again. Retirement keeps the history and takes it off routes. Deleting is for a duplicate you created by mistake and have not yet recorded against. If a reading exists, retire. Do not delete history because the name was ugly. Rename it.