White papers and published research

Levaru·August 2026

The Continuity Audit: A Facility Manager's Framework for Measuring and Closing Located-Knowledge Risk Before Retirements, Contract Changes and Reorganizations

Nikolai Hanov

Facility organizations run on located knowledge — operational knowledge tied to specific places and assets, almost never written down — and it leaves through three foreseeable doors: retirements, contract changes and reorganizations. This paper defines the Continuity Audit: a governed, repeatable assessment that inventories that knowledge, scores each item for criticality and documentation coverage, and converts the result into an owned, prioritized closure plan. It supplies the Handoff Test, an inventory method, the Criticality–Coverage Matrix, closure mechanisms, a maturity model, baseline-first metrics and the governance that keeps an audit of knowledge from becoming an audit of people.

Levaru·July 2026

The Visual Asset Register: How 360-Degree Documentation Improves Work Orders, Inspections and Staff Handoffs

Nikolai Hanov

Facility teams lose located knowledge one retirement, contract change and undocumented repair at a time, because the record of most buildings is scattered across CMMS fields, shared drives, O&M binders and staff memory — none of it spatial. This paper defines the Visual Asset Register: a spatially indexed, time-stamped set of 360-degree captures, linked to asset records and maintained on a defined re-capture cadence under documented governance. It shows how a maintained register improves work orders, inspections and staff handoffs, and supplies a vendor-neutral framework, a metrics model, a five-level maturity model and the governance to run one responsibly.

Levaru·June 2026

Minimum Viable Digital Twin for Existing Buildings: A Facility Manager's Practical Framework for 360° Reality Capture, Structured Asset Data and Operational Integration

Nikolai Hanov

Digital-twin guidance is written largely for new construction, yet facility managers of buildings that are decades old start from incomplete drawings, an uncertain asset register and knowledge held by a few long-serving technicians. This paper defines a minimum viable digital twin — the least connected spatial, asset and workflow information that measurably improves one operational outcome, is synchronized with the building at a stated frequency and fidelity, and can be governed and audited. It sets out six minimum requirements, a six-stage maturity ladder, a vendor-neutral comparison of eight capture methods, a bounded pilot roadmap and transparent business-case formulas.

Levaru·May 2026

The Closure Note: A Facility Manager's Framework for Capturing the Diagnosis, the Fix and the Exception Before the Technician Leaves the Room

Nikolai Hanov

Facility operations produce knowledge continuously and record it almost never: every completed work order closes at the moment the fault is understood, usually with a status and a single word. This paper defines the closure note — a five-line record of what was found, what caused it, what was done, what was learned and what comes next, written at the asset — and closure discipline as the practice that produces it: capture mechanisms matched to real technicians, a sampled Closure-Quality Audit scored on the Recurrence–Recoverability Matrix, and the Re-Fix Test as the headline measure of whether the archive can answer the building's next fault without a phone call.

Levaru·April 2026

The Handover File: A Facility Manager's Framework for Specifying, Verifying and Taking Delivery of the Operational Record Before the Project Team Leaves

Nikolai Hanov

Every completed project ends in two deliveries: a physical asset and an information asset — and the second delivery routinely fails, at a measured cost of US$15.8 billion a year in United States capital facilities, two-thirds of it borne by owners and operators. This paper defines the Handover File: a specified, verified, operations-ready information deliverable — demanded in the contract at project outset, delivered progressively, structured to load the owner's systems of record, and acceptance-tested before the project team is released. It supplies the Day-One Test, the Operational Data Requirements Schedule, the Demand–Structure Matrix and a vendor-neutral menu of acceptance mechanisms.