The name is a shorthand: Know Why. Every decision, connection, and change — documented so the reasoning is never lost.
KnowY is where your project's knowledge lives. Not files — knowledge. What each part is, what it connects to, who is responsible, what changed and why. Structured, searchable, and available to anyone on your team with the right access — from the first day of the project to the final handover.
KnowY does not use artificial intelligence. There is no language model processing your data, no inference engine guessing at answers, and no third-party AI service receiving your project information. Every result you see in KnowY comes directly from structured data your team has entered.
That means no hallucinations, no statistically plausible but wrong answers, and no exposure risk from sensitive project data leaving your organisation. When KnowY shows you a tag number, a connection, or a responsible party — it is because someone on your project recorded it. Not because a model estimated it.
In regulated industries, that distinction is not a feature. It is a requirement.
| Tool | What it does | How KnowY fits alongside it |
|---|---|---|
| SharePoint · ProjectWise | Stores and organises your files | KnowY structures the knowledge inside your project — not the files. You can search an item, not a document. |
| Revit · Navisworks | 3D spatial and geometric design | KnowY handles what the 3D model does not: signals, systems, instruments, and how everything connects logically. |
| SAP PM · Maximo | Maintenance work orders and asset records | KnowY is the project model that feeds your maintenance system — complementary, not competing. |
| Aconex · Procore | RFIs, submittals, drawing workflows | KnowY is not about managing process. It is about structured knowledge — what exists, how it connects, who is responsible. |
| Spreadsheets · shared drives | Everything you are currently doing manually | KnowY replaces this with a searchable, navigable model — at a fraction of the time cost and without the version confusion. |
For discipline engineers managing a single domain — when your signal list, your P&ID, and your cabinet schedule all call the same component something different. One name, one reference code, one truth.
For project leads coordinating two or more knowledge domains — when your electrical contractor needs to see the location model, or your mechanical engineer needs to trace a signal to its destination. Every knowledge domain in one shared model.
For programme managers and interface coordinators on large projects — when a change at system level cascades through instruments, cables, and terminations, and you only discover the full extent at commissioning. Make that chain visible before it becomes rework.
| Structure | Insight | Lifecycle In dev | |
|---|---|---|---|
| Naming & structure | |||
| One authoritative list of every component | ✓ | ✓ | ✓ |
| Reference codes — auto-updated when a component moves | ✓ | ✓ | ✓ |
| Structured project tree (single knowledge domain) | ✓ | ✓ | ✓ |
| Multiple knowledge domains in one shared model | — | ✓ | ✓ |
| Record and edit properties on each component | ✓ | ✓ | ✓ |
| Create, edit, and delete relations between components | ✓ | ✓ | ✓ |
| Full reference model documentation, generated automatically | ✓ | ✓ | ✓ |
| Navigation & sharing | |||
| Search across all components instantly | ✓ | ✓ | ✓ |
| Permanent shareable link to any item | ✓ | ✓ | ✓ |
| Visual diagram of all components and connections | — | ✓ | ✓ |
| Navigate from one knowledge domain into another | — | ✓ | ✓ |
| Interfaces | |||
| Automatic interface detection within a knowledge domain | ✓ | ✓ | ✓ |
| Automatic interface detection across knowledge domains | — | ✓ | ✓ |
| Track each interface from identification to formal closure | — | ✓ | ✓ |
| See what is affected before making a change | — | ✓ | ✓ |
| Collaboration | |||
| Notify a colleague about a specific item | ✓ | ✓ | ✓ |
| Notify all relevant stakeholders at once | ✓ | ✓ | ✓ |
| Control who can see which parts of the project | ✓ | ✓ | ✓ |
| Log of who changed what and when | — | ✓ | ✓ |
| Export & handover | |||
| Import and export from spreadsheet | ✓ | ✓ | ✓ |
| Quantity lists and component schedule exports | ✓ | ✓ | ✓ |
| Point-in-time snapshot for contractual handover | — | — | planned |
| Connect to your other systems (REST API, API key) | — | — | ✓ |
A Danish team combining deep software architecture expertise with 25 years of hands-on experience from mechanical and electrical engineering projects. We built KnowY because we knew the problem first-hand.
"Critical project knowledge scattered across spreadsheets, inboxes, and the heads of people who may not be there next year."
We typically respond within one business day. The more you tell us, the more useful our first conversation will be.
An Ontoteq team member will read your message and be in touch — typically within one business day.