What you can ask

Questions KnowY
answers instantly.

When your project data is structured, specific questions get specific answers — in seconds, not in meetings. These are the questions your team is currently answering the hard way.

Immediate answers No preparation required
Find anything
› query
Who is responsible for instrument FT-2201?
› query
Which components belong to system P-401?
› query
Where does cable C-2217 terminate?
› query
What is the rated pressure of valve V-118?
› query
Which subcontractors have access to this section of the project?
› query
Show me everything tagged to zone B — instrumentation only.
› query
Which components and systems are installed in room B-214?
Change & accountability
› query
What changed in the instrumentation scope this week?
› query
Who last modified this component — and when?
› query
Which items were added to scope after the design freeze?
› query
Show me everything that changed since the last handover package.
› query
Which team member has made the most changes this month?
Interfaces & connections
› query
Which interfaces between our scope and the EPC contractor's are still open?
› query
What does pump P-101 connect to downstream?
› query
Which components have no interface point assigned yet?
› query
How many open interfaces does contractor X currently own?
› query
Where do the electrical and mechanical scopes meet?
› query
List every interface that crosses a contractor boundary.
Lists & quantities
› query
What is the complete bill of quantities for system S-300?
› query
Generate the signal list for control loop L-4412.
› query
How many pressure transmitters of type XT are in this project?
› query
Which components are still missing required specification properties?
› query
Export the interface register for this contractor's scope.
› query
What equipment is planned for delivery in Q3 that has no specification yet?
Across knowledge domains
› products ↔ locations
Which instruments in the product domain have no assigned location?
› products ↔ locations
Show me all equipment installed in a zone flagged as hazardous area — with their Ex ratings.
› products ↔ locations
Does instrument FT-2201 meet the ambient operating temperature requirement for the room it is installed in?
› products ↔ signals
Which instruments have no signal assigned — and which signals have no instrument connected?
› products ↔ signals
For loop L-4412: list every instrument, its signal type, and its control destination in one view.
› products ↔ test protocols
Which instruments in system P-401 have no test protocol linked to them?
› products ↔ test protocols
Which test protocols cover equipment that has been modified since the protocol was created?
› locations ↔ test protocols
For building C: list every room, the equipment in it, and the status of its associated test protocol.
› signals ↔ test protocols
Which signal loops have a completed test protocol — and which still have open deviations?
› products ↔ locations ↔ signals
For each instrument in zone B: its physical location, its signal path, and whether the loop has been tested.
› products ↔ locations ↔ test protocols
Which systems in building A are fully installed, have all test protocols approved, and are ready for handover?
› signals ↔ locations ↔ test protocols
For zone C: list every active signal loop, whether its test protocol is complete, and the physical location of each instrument in the loop.
Advanced analysis

What a well-built model can answer.

These questions go beyond lookup. They require that your project data is complete, consistently structured, and connected. When it is, KnowY can surface answers that would otherwise take days of manual analysis — or would never surface at all.

Requires a structured, connected model
If pump P-101 fails, which other systems in this loop stop working?
Traces the dependency chain through connected components — surfaces everything that depends on P-101, directly or indirectly.
Which parts of this design have no redundancy — a single failure kills the function?
Identifies every component where there is no alternative path. Single points of failure, found before commissioning.
What is the expected availability of this critical loop, based on component specifications?
Calculates uptime probability from the reliability specs already recorded on each component in the loop.
If we change the pressure rating on valve V-234, which connected items need review?
Follows all relationships downstream and upstream from V-234 — shows exactly what the change propagates to.
Which open interfaces are on the critical path to our commissioning date?
Cross-references open interface status with system readiness — highlights the ones that block go-live if they stay unresolved.
Where in the project is the highest concentration of unresolved interface points?
Maps interface density across the project structure — shows where coordination pressure is highest before it becomes a problem.
Which systems will miss their commissioning target if these interfaces stay open?
Connects interface status to system completeness — shows which go-live dates are at risk based on what is unresolved today.
What is the total scope delta since the last contractual milestone — broken down by discipline?
Compares current project state to the snapshot taken at the milestone — exact count of additions, removals, and changes per domain.
If this component is removed from scope, what else is affected — and what becomes unreachable?
Runs a dependency traversal from the removed item — identifies orphaned components, broken connections, and downstream consequences.
Which contractor carries the most interface closure responsibility — and how far behind are they?
Aggregates open interface ownership by contractor, sorted by count and days since assignment.
Are there components in two different systems simultaneously, or gaps where nothing covers a required function?
Detects structural inconsistencies in the model — overlaps and coverage gaps that manual review would take weeks to find.
Which items were marked complete but have had changes applied after the sign-off date?
Compares change timestamps against sign-off records — surfaces items that have quietly drifted from what was formally approved.
Ready to ask your own project?
Sign in to your KnowY workspace, or get in touch and an Ontoteq team member will reach out.
Go to sign in