Asset Impact: Overview
What the Asset Impact tab does, and why it is the only reliable way to close an amenity for work.
Last updated
When work takes an amenity out of service, two things have to happen: nobody new should be able to book it, and the people who already booked it need to be told. The Asset Impact tab on a service ticket does both, tied to the dates of the work itself.
What it is for
Asset Impact links the amenities affected by a ticket to that ticket, and closes them for the period of the work. A closure created here is enforced by the booking rules, so residents and staff are actually prevented from booking during the window rather than merely asked not to.
Why not just tell people
Because a notice does not stop a booking. A resident booking the party room three weeks out has no idea the elevator work will overrun into it, and staff taking a booking over the counter have no reason to remember. A closure is a rule; a notice is a hope.
What it can do to existing bookings
When you confirm a closure, Kore checks for bookings that overlap the window and gives you a choice: cancel them all, notifying the affected residents and refunding paid bookings automatically, or leave them alone and merely block new ones. That choice is covered in Cancel Bookings or Block New Ones.
It needs a schedule first
The tab will not let you link amenities until the ticket has a scheduled start and end date. That is deliberate, since a closure with no dates is meaningless. If you see Schedule Required, set the schedule on the ticket first and come back.
The one thing that catches everyone
Adding an amenity to the tab does not close it. The closure sits as Pending until somebody confirms it, and a pending closure blocks nothing at all. The tab says so in as many words, and it is still the most common way a closure fails to happen. See Confirming a Closure.