How to read the FDV building overview

FDV building overview is the compact snapshot of a building: its structure, its systems, its documentation and its operational information, all on one page.

FDV building overview is the compact snapshot of a building: its structure, its systems, its documentation and its operational information, all on one page. It's where you start when getting to know a building you haven't worked on before.

How to open the overview

Go to FDV > Building overview in the sidebar.

What the page holds

Building structure shows the make-up in figures: Sub-buildings/zones, Floors and Rooms.

Building profile shows the building's key details. A field reading Not set means the detail is missing — it's registered under the building's settings. See How to change building settings.

Systems is the list of technical installations in the building. For each system you see:

Field

Contents

System number

the system's number

Sub-building

where the system belongs

System information

details about the system

Components

the components under the system

Delivery date

when it was delivered

Files

documentation attached to the system

Operational information

the notes you've written

Cloud automations from technical schema

cloud automations covering the system

If a system has open tasks, it shows 1 open task or {n} open tasks.

FDV files shows the building's documentation. Without access it says You do not have access to files for this building.

The status markers on systems

Two markers are worth noticing:

  • End of life — the system has passed its expected lifetime
  • Reclaimed — a warranty claim has been raised

Both signal that the system needs a decision, not just maintenance.

How to use the overview

The order that works when you take over a building:

  • Read the Building profile to see what's registered and what's missing.
  • Go through Systems and see which show End of life.
  • Check whether the systems have Operational information — an empty field means the knowledge exists only in people's heads.
  • Check whether the systems have Files. A system without documentation is a risk when something goes wrong.
Note: No data on a system means nothing has been registered there. It doesn't mean the system doesn't exist — only that nobody has filled the details in.

Frequently asked questions

How do I add a description of a system?

Use Add description on the system. See How to add a system description.

How do I add operational information?

Under Operational information on the system. See How to add operational information to a system.

Can I add a system that's missing?

Use Add installation to create one manually. Systems arriving from the building automation come in on their own.

Why does something say Restricted?

You don't have access to that part of the content.

Tip!

Use this page as a handover checklist. A system with no delivery date, no documentation and no operational information isn't a system you can operate — it's something you need details about, and those are far easier to ask for at handover than two years later.