Glossary
The basics, in plain words
Short answers to the questions behind the work we do — no jargon, no pitch. Each one links to a deeper guide if you want it.
- What is a CMMS migration?
- A CMMS migration is the move from one computerised maintenance management system to another — carrying the asset records, work-order history, and PM schedules across so nothing is lost. More →
- What is basis-of-design (and why does it drift)?
- Basis-of-design is the document that records the criteria and assumptions an engineering design is built on — loads, redundancy, code references, setpoints — so everything downstream rests on a stated foundation. More →
- What is institutional knowledge — and what does losing it cost?
- Institutional knowledge is the unwritten understanding a team builds over time — a client's preferences, a facility's history, the reasons behind past decisions — that usually lives in people's heads rather than any system. More →
- What is human-in-the-loop AI?
- Human-in-the-loop AI means a person reviews, can meaningfully change, and owns the result before it takes effect — the tool does the legwork, but a human makes and is accountable for the decision. More →
- What is data residency, and why does "stays in Canada" matter?
- Data residency is where your data is physically stored and processed, and which country's laws govern it — often a more important and more durable decision than which AI model you use. More →
- What does it mean to scope a custom build?
- Scoping a build is defining the smallest, clearest version of a tool that solves one real problem — what it will and won't do — before any code is written, so the project stays tight and ships working. More →
Want the longer version?
The guides go deeper on each of these — and if you’d rather just talk it through, that’s what the first call is for.