Sites hierarchy - stopping midway down.

Question

Hi - long time user, first time poster…

My site hierarchy is setup as: Country > State > City > Building > Floor.

I've lots of inspections that relate down the ‘hierarchy’ to the floor of a building. I now need to record a new template that is done for the whole building instead of a floor. The automated ‘site’ function in the inspection however forces me down to the bottom of the hierarchy to a floor and wont let me stop halfway.

Any suggestions on how I can stop halfway down at the building name rather than a floor within it? or perhaps the preloaded ‘site’ function isn't the right thing to use to capture my inspections?

Part B to this would be scheduling against this mid-point. Currently you can select the building name but it will assign the inspection to all the ‘floors’ beneath it which isn't required.

I need to run analytics from this template in the future so assume it needs to be connected to the base-data set, such as ‘site’ for this to work (this prevents using the free-text field).

The only thing i can think of is to include a new floor in every building called ‘whole building’ or the similar, to differentiate the data (but i will then need to exclude this from all the existing analytics & dashboards that are tracking completion rates across all existing floors).

Emily-Rose · Accepted Answer

Hey Rob,Currently, you’ve rightly pointed out, that it’s only possible to tie an inspection/schedule/action etc to the lowest level in the hierarchy, i.e your floors. Even if you choose a level above in scheduling, this is a way of grouping and bulk assigning directly to any of the bottom levels below. A way around this if you’d like to use sites for smaller areas of the building is to have an all encompassing site “whole” building as you mention.However, we are currently looking into the Sites feature and the needs of the future, including meta data on a site and the concept of locations vs specific areas within the location itself.Keen to hear your thoughts on should they all be in one hierarchy!Or would you prefer to build and manage it in a different way? What is the difference for example in the data you’re collecting at floor level vs building?Thanks!

Rob Rio T · Answer

Thanks for the response.To answer your question ref differences between levels in the hierarchy, an example for me would be that I've a team doing inspections of floors of a building (i.e. presentation check), but i also might have an inspection that's relevant to the whole building - perhaps an over arching inspection or assessment. (i.e. insurance inspection).A work-around would be to createan asset within that module that's called ‘whole building’ or something and then schedule against the asset instead of a part of the location hierarchy.Due to time constraints, I've created a whole new hierarchy separatelyfor whole buildings & inspections which don't have any levels so it will suffice for now but as my usage increasesFrom a development POV - being able to confirm each level of the hierarchy as ‘anchorable’ with the same functions as the bottom level would be useful.

Sites hierarchy - stopping midway down.

Reply

Cookie policy

Cookie settings

Reply

Sign up

Single sign-on

Log in

Single sign-on

Scanning file for viruses.

This file cannot be downloaded

Cookie policy

Cookie settings