Fire door survey: how entry door assets and leaseholder notices work

Function Overview / Purpose

There is now a statutory requirement to inspect entry doors of apartments. There is an automated cSite survey that will allow a site inspector to complete the inspection, and when sync’ed from the surveying device will automatically send to each leaseholder to inform them of the status of their entry door.  It will also create a Request that will show any remedial actions to repair/make compliant the door.

When a Fire Door Survey is published it will automatically -

• Send a one page Entry Door Survey to each leaseholder
• Send normally by email for active users
• Send via your print provider to all others 

You can view the list of surveys from the Content > Building Surveys page

Door Entry Group and Door Entry asset types

Each block asset could have a group of doors. This means one asset where the linked entity type is “Door group”. And each group of doors asset, will contain multiple individual doors. These are assets where the linked entity type is “Door Entry”.

To generate the door group with all the doors for one or multiple units go to the Compliance → Assets → List menu:

Where there is a button, “Create entry doors”

Which allows to generate the tree of assets for either one or all the units of a block or blocks.

• Create all remaining entry doors hides the unit name, so that based on the regex of the blocks, ALL the units gets their door assets created. Answers can be pinned for those doors.
• The building (organisation table) must previously contain a root asset of entity linked type “Building”.
• The structure of the assets created is as follows. Building Root Asset → Block root asset → Entry Door group Asset → Entry Door asset. 
  Where the entry door asset is related to the unit (unit_asset table)

• Each asset will be related to a unit, and the pinned answers from the Questions related to the Entry Door asset type will be cloned into the unit’s entry door asset.