Workflow
The job explains the month.
An install, a removal, a move, or a conversion is why a floor’s numbers changed. When that job is tracked on its own, the results show up later as a surprise. Someone has to remember that a bank went in on the 12th before the index means anything. The insight arrives only if a person still has the context.
Kept in the same database as the floor, the job is already on the machines and the property. A month can be read with what was placed or pulled, on which cabinets and themes, under which agreement. “Why did this property move” is answered by the work, sitting next to the result.
That is also what makes the other services sharper. Performance is trustworthy because it knows the floor was changed, and when. Maintenance stays cleaner because a floor change is not mixed in with service on a machine that was already there. The customer story includes the jobs that altered their floor, not a deal that froze on the day it was signed.
Your jobs stay on your servers. Why that matters.