Bad inputs stop at the gate.
We validate every discipline model before coordination begins. Coordinates, naming, content and model health must be right before any clash result can be trusted.
A clash test is only as reliable as its source models.
Model creation and validation establish whether each discipline file is ready to enter the coordination environment. We inspect its geometry, shared coordinates, levels, grids, naming and agreed level of development against the project requirements.
Skipping this gate allows basic modelling faults to masquerade as coordination problems. A shifted origin can produce thousands of false clashes, while incomplete geometry or inconsistent LOD can hide conflicts that will surface later on site.
CNE treats validation as an engineering control, not a file-opening exercise. We record exceptions, return clear actions to the originating discipline and admit the model only when it is suitable for federation.
What we check and hand over
Project base points, survey points, shared coordinates, grids and levels are tested against the agreed project reference.
File names, model breakdown, worksets, classifications and object naming are checked for consistency across the delivery team.
Model elements are reviewed against the required LOD and coordination purpose, with missing or over-modelled content identified.
Files are audited and purged where appropriate, with warnings, duplicate objects, broken links and unnecessary data flagged.
Each model receives a recorded status, issue list and required actions, giving the team a traceable basis for acceptance.
Accepted native or IFC files are prepared with the correct references, revisions and identifiers for controlled federation.
We test the model before testing the design.
We distinguish harmless authoring quirks from defects that could distort coordination or conceal a buildability issue.
Readiness is measured against agreed project requirements, not a vague impression that the file looks complete.
Every accepted file has a known revision, validation record and accountable source before it enters the clash cycle.
Start with models the team can trust.
Send us your discipline files and coordination requirements. We will identify what is ready, what needs correction and what should not enter federation yet.