Diagnostic readiness checklist
What to gather before a review: system maps, exports, alarms, asset registers, access details. Speeds up scoping and reduces cost.
Resources
Start with the white paper on digital-building evidence chains, then use the guides and checklists to prepare for supplier conversations, technical reviews and spend decisions.
Evidence library
The digital-building paper sets the frame: connectivity is not assurance until the evidence chain holds. This library gives that thinking somewhere to live as new papers, resources and approved case studies are added.
Paper / White paper
A North Current white paper on why connected buildings can still lack operational truth, and how evidence chains break between assets, data, support contracts and commercial decisions.
Resource / Guide collection
Short diagnostic guides for mapping faults, PV and BESS reporting gaps, and energy bill evidence problems.
Resource / Checklist set
Preparation prompts for evidence packs, integration details and operational handover checks before a review starts.
Resource / Reference collection
Reference points for commissioning, metering, maintenance, alarms, golden-thread information, analytics and field reliability.
Case study / Anonymised case note
A home for anonymised diagnostic examples where small site faults distorted reports, supplier ownership or spending decisions.
Problem guides
01 · GUIDE
A practical guide to diagnosing missing values, duplicated points, stale data and unclear ownership in BACnet or Modbus integrations.
Read guide02 · GUIDE
How to review inverter, battery, meter, gateway and BMS evidence before assuming a solar or storage asset has failed.
Read guide03 · GUIDE
A practical route for reconciling commercial bills, meters, sub-meter exports, BMS data and site operating behaviour.
Read guide04 · GUIDE
Five cabling errors found on a single site, how they created unstable comms, data loss and incorrect billing, and what to verify before accepting an RS485 installation.
Read guideBefore you start
The quality of a systems review improves significantly when the right evidence is available from the start. These tools help you get there faster.
What to gather before a review: system maps, exports, alarms, asset registers, access details. Speeds up scoping and reduces cost.
How to document integration details, protocol maps, vendor responsibilities and export constraints so an independent reviewer can assess them quickly.
Questions that test whether a newly commissioned system is actually usable, not just installed and connected.
FAQ
Useful evidence includes system maps, screenshots, point lists, data exports, alarm logs, trend data, tariff context, known integrations, vendor contacts and a short summary of the operational impact.
No. Our role is independent advisory support. We clarify the evidence, issues, ownership and action plan so internal teams and suppliers can work from a cleaner brief.
Yes. Integration review can include point naming, mapping, polling behaviour, missing values, duplicated points, data freshness and the practical impact on operations or reporting.
Yes. A current-state map and acceptance criteria reduces ambiguity before tender, retrofit design, vendor selection or commissioning, and protects you from scoping gaps that emerge later.
No. We're not a SaaS platform or OEM-aligned installer. Recommendations may include software, configuration, process or supplier actions where the evidence supports them.
Depth and terms are agreed through the enquiry process. The first conversation is free: no scope pitch, no obligation. We recommend the right depth for your situation, not the most comprehensive option by default.
Describe what you're dealing with in a few lines. We'll tell you honestly whether an independent review would help.
No obligation · Vendor-neutral · First conversation is about scope, not a sale