Spinview, Asset Intelligence for Buildings and Cities

The knowledge leaving problem.

Operations

Every estate has a knowledge leaving problem. The engineer who retires takes thirty years of building history with them. The FM contract that ends takes the operational record with it.

Section 1

What leaves and what stays. When a long-serving engineer leaves, the organisation loses the mental model of the building: which systems are quirky, which assets have a history, which decisions were made for reasons no longer obvious.

Section 2

The FM contract transition problem. A new contractor arrives with no context. The first six months are spent rediscovering what the previous contractor knew.

Section 3

Documentation alone is not enough. Documentation without structure is a filing system, and filing systems are only as useful as the person who knows how to navigate them.

Section 4

Holding knowledge in the building. Spinview holds operational knowledge in the building rather than in the people who work in it. When an engineer leaves, the knowledge stays in the platform.

Section 5

Using the FM tender to protect knowledge. Operational record continuity can be specified as a scored requirement in an FM tender, so the knowledge generated during a contract stays with the building.

Full white paper

The full paper sets out why documentation alone struggles, what a structural record looks like, and how to use an FM tender to make operational knowledge continuity a contractual condition.