TEOMIX / Coordination note 01

Find the conflict.
Keep the context.

A calm, evidence-led way to coordinate engineering models—from first detection to verified resolution.

See the method
Coordination sheet08 / CL-018

ISSUED FOR REVIEW
20.09.2026

FindingSupply duct / transfer beam
EvidenceMEP_R24 ↔ STR_R11
StatusDecision required
Revision 04Source-linkedOwner: MEP lead
01

Traceable by design. Every issue retains its geometry, source revision, rule and decision history.

One issue.
One line of evidence.

TEOMIX makes coordination legible. Instead of surrounding the team with another dense interface, it presents the exact information needed for the next engineering decision.

DESIGN INTENT

Clarity is not decoration. It is the shortest route from a detected condition to an accountable resolution.

01

Detect

Identify the spatial condition
02

Explain

Reveal objects, rules and revisions
03

Decide

Assign ownership and approve intent
04

Verify

Confirm the changed model resolves it

Coordination
without the noise.

Four connected instruments. Each one reduces ambiguity at a specific point in the review.

A—01

Clash Core

Detect what matters.

Group related conditions and keep each result tied to the exact model revision.

A—02

Evidence Graph

See why it happened.

Inspect source objects, rules, tolerances and spatial context in one readable record.

A—03

Resolution Room

Make the next decision.

Assign ownership, compare proposals and preserve the approved engineering intent.

A—04

Model Reconciliation

Prove the fix.

Re-check changed geometry against the original condition and close the evidence loop.

A controlled path
from model to decision.

STEP 01 / 04

Connect models

Bring approved discipline models into a controlled coordination set without losing source identity.

IFCBCFRVTNWC

Review one coordination question.

Choose a sample issue, inspect its affected elements and move it through a temporary review sequence. This interface demonstration does not detect clashes, load IFC files or store project data.

Affected elements / synthetic plan

Selected synthetic coordination example A simplified coordination diagram. The selected example is highlighted. TRANSFER BEAM / STR-R11SUPPLY DUCT / MEP-R24 PLANTROOM / ARCH-A12AHU-03 CORE WALL / STR-C04SERVICE RUN / MEP-S09

CL-018

Open

Supply duct intersects transfer beam

Disciplines
MEP / Structural
Description
A synthetic supply duct crosses a synthetic transfer beam at Level 08.
Impact
The proposed route cannot be issued for coordination review.
Owner
MEP lead
Next step
Compare a raised route with a local beam adjustment.
OpenIn reviewResolved

Status changes are temporary for this browser session. They do not prove a construction conflict is resolved.

    Quiet on screen.
    Rigorous underneath.

    P—01

    Evidence first

    No finding without source objects, revision and rule context.

    P—02

    Human authority

    Automation organizes and recommends. Qualified people approve.

    P—03

    Open exchange

    Project information remains portable across established workflows.

    P—04

    Calm operation

    Priority, state and next action stay understandable at a glance.

    See the issue.
    Decide with confidence.

    Bring one coordination case. We will show how TEOMIX turns it into a clear, source-linked decision record.

    Private review

    See TEOMIX in your project context.

    Tell us where to reply and what you are coordinating. We will prepare an email to info@teomix.com for you to review and send from your email app.

    What happens next

    1. Prepare an email draft or copy the request.
    2. Review the details and choose whether to send it yourself.
    3. TEOMIX can reply to your work email about a private review.
    Use an address where we can reply about your review.
    This is added only to the email draft or copied request; TEOMIX does not store it on this site.
    Preparing or copying this request does not send it. You choose whether to send an email.