Early-Stage Concept

Smarter
decisions for the
mechanical
systems that
keep facilities
running.

Latent is an early-stage idea focused on helping building teams make better decisions about the equipment they rely on every day. By using the information they already have, the goal is to spot repeated problems earlier, understand what needs attention, and support smarter repair-or-replace decisions.

Latent hero image

Asset Priority

Currently 4 high priority assets flagged for review.

4 High Priority
BLD-B-RTU-03

Recurring service calls · replacement review recommended

High
BLD-C-CHWP-02

Repeated issue pattern · prepare planned replacement

High
BLD-A-AHU-02

Service history review needed · assess condition

Medium
The Problem

Critical mechanical systems are still managed with fragmented information and reactive decisions.

Many organizations already have useful maintenance, asset, and operational data, but it often lives across disconnected records, systems, and staff knowledge. The result is slower decisions, weaker prioritization, and less confidence in when to maintain, repair, or begin replacement planning.

Reactive Maintenance

Important action is often triggered by breakdowns, urgent complaints, or visible disruption instead of by a clearer view of asset condition and recurring patterns.

Fragmented Information

Work orders, spreadsheets, BAS data, alarms, inspections, contractor reports, and staff experience often exist separately, making it difficult to form one usable picture of system health.

Weak Repair-vs-Replace Clarity

Even when issues are known, teams can still struggle to decide what deserves immediate maintenance, what should be monitored, and what may be approaching replacement review.

This can lead to higher costs, recurring comfort issues, urgent repairs, and weaker long-term planning.
Inputs

A structured way to move from fragmented information to clearer action.

The concept is to organize what already exists into a simpler decision-support flow for mechanical systems.

Mechanical systems illustration
01

Asset Information

Equipment type, age, location, specifications, and criticality context.

02

Maintenance Information

Work orders, inspections, failures, service history, and parts used.

03

Operational Information

Runtime, alarms, temperature, pressure, airflow, and related system behaviour.

04

Financial Information

Repair costs, maintenance spend, vendor input, and replacement estimates.

05

Comfort / User Information

Complaints, hot or cold zones, odour, humidity, and weak airflow reports.

06

Existing Systems

CMMS, BAS/BMS exports, spreadsheets, and any existing internal records.

Assets

Asset Intelligence Hierarchy

Site / Area
System
Equipment
Components
Example
X-Ray Room
Ventilation
Exhaust Fan
Motor, Grille, Damper, Duct Connection

This structure helps connect where the asset is, what it supports, what condition it may be in, and how important it becomes if it fails.

Signals

What Latent helps surface.

Asset Condition

What has happened recently and whether an asset may be degrading.

Recurring Issues

Which complaints, service calls, or failures keep appearing.

Decision Signals

Patterns in cost, comfort, performance, downtime, or missing information.

Criticality

Which assets matter most based on safety, operations, and downtime risk.

Suggested Review Direction

What should be monitored, inspected, maintained, or reviewed next.

Field Validation

Technician and field input help confirm what the information is suggesting.

Maintenance Types

Not every asset should be managed the same way.

The right maintenance approach depends on asset criticality, condition and history, failure behaviour, and the impact if the asset fails.

Reactive / Corrective

Used when an asset fails or an issue becomes obvious. Best for low-risk, low-cost assets where failure has limited impact.

Preventive

Used on a schedule, usage interval, or inspection cycle. Best for routine service needs or assets with known wear patterns.

Predictive

Used when inspections, alarms, or performance trends show concern. Best for critical assets with measurable warning signs.

Reliability-Centered

Used when the consequence of failure is high. Best for systems affecting safety, operations, compliance, or major cost.

Workflow

From hidden evidence to clearer action.

Collect Inputs
Structured Analytics
Technician Validation
Suggested Review Action

The goal is not to make a final diagnosis or replace field expertise. The goal is to turn scattered information into clearer maintenance directions.

Case Study: Clinic Asset Management

Prioritizing ventilation issues.

A clinic has ventilation-related issues in the X-Ray Room, Reception, and Washroom. The question is not only “what is broken?” It is which issue should be prioritized first when budget, technician time, and clinic operations are limited.
Area Issue Consequence Criticality Action Priority
X-Ray Room Ventilation / air distribution May affect room usability, staff/patient conditions, and imaging workflow High Preventive + condition-based review 1
Reception Ventilation / comfort Impacts waiting-room experience and front-desk working conditions Medium Planned corrective maintenance 2
Washroom Exhaust ventilation Localized odour/exhaust issue; lower-cost and isolated Low-Med Routine inspection or reactive maintenance 3
This is a simplified example. In practice, prioritization becomes far more complex across multiple clinics, buildings, and assets, especially when teams must balance budget, downtime, technician availability, and operational risk.
Vision

A clearer future for the systems people rely on every day.

We believe the teams behind real buildings should be able to move with more confidence, less guesswork, and a clearer sense of what comes next.

Latent icon Latent
Why Latent

Built for the hidden layers of building operations.

Latent is being built around a simple belief: critical mechanical systems deserve a more practical layer that helps teams move beyond raw data, reactive workflows, and generic software.

01

Focused on core building mechanical systems

Focused on the equipment that property and facility teams deal with every day — including HVAC equipment, boilers, pumps, air handling units, rooftop units, heat exchangers, and related systems.

Contact

If this feels relevant, let’s talk.

Whether you're exploring the problem, thinking about a pilot, or simply open to sharing perspective, we'd be glad to hear from you.

Early Feedback

Share what feels true, what feels missing, or what would matter most in practice.

Possible Pilot Fit

Explore whether a focused starting point could make sense for your team.

Industry Perspective

Open to conversations around building systems, maintenance decisions, and what better support could look like.

Get In Touch

Reach out directly — happy to have a conversation.

Currently in the research and prototype stage.