Coordination Setups

A Coordination setup is the durable connection between a federated Navisworks model, its property mapping, a ClashWise matrix, and the native search sets/tests generated from that matrix.

Use it when your coordination standard should exist before clash detection and should continue to apply to future publishes from the same federation.

Boundary: a setup creates and reconciles native definitions. It never runs clash detection. Run or update the resulting tests in Navisworks Clash Detective.

Who can create one

Coordination setup automation requires active or trialling Pro, Business, or Enterprise access. Starter, free access, and campaign-only grants are excluded. Matrix viewing and editing still follow the matrix's normal ownership, sharing, and library permissions.

Create a setup from Navisworks

Open the clean federated model.
On the ClashWiseAI ribbon, open Sets and Clashes.
Choose Create from ClashWise matrix.
Name the setup, then choose Create a new matrix or Use an existing matrix.
Confirm every federated source and map its source, class, and optional discipline properties.
Validate the source property required by later cloud analysis.
Scan the model and review distinct raw values, segmentation, counts, and selected class keys.
Create the setup and open its matrix on the web.

The scan uploads compact distinct source/class/discipline tuples with counts, not per-element data. It reports progress, can be cancelled, and stops at 10,000 distinct tuples. Choose a coarser classification property if the ceiling is reached.

Review a setup on the web

Open Coordination setups to see:

setup name, creator, optional project, timestamps, semantic revision, and linked default matrix;
federated source identities and advisory fingerprints;
reusable property mapping;
selected class/discipline inventory and occurrence counts;
matrix/model coverage;
scan freshness and source drift; and
last observed and installed materialization hashes.

Open the linked matrix to review its origin and rules. For every rule, check Active, Detection Type, tolerance, priority, status, contact, and tags.

Coverage

Coverage uses exact (ClassName, MatchDiscipline) keys:

a rule is eligible only when both endpoints exist in the scanned inventory;
matrix endpoints absent from the model are skipped;
model classes absent from the matrix are shown before creation; and
users can proceed with the valid intersection.

For an editable matrix, use Add missing classes. Clone a read-only library matrix before expanding it.

Materialize and reconcile

Return to the plugin and choose Refresh or Continue. Before any native write, ClashWise shows the deterministic definition diff:

Create
Update
Unchanged
Obsolete
Conflict
Unmatched

Only artifacts recorded in the local installation manifest as ClashWise-managed are candidates for updates. They must still match their last installed definition. User-modified and unverifiable artifacts are conflicts and are preserved by default. Obsolete removal is explicit and unchecked. Unrelated native sets/tests are never changed.

Managed search sets live in ClashWise · {setup name}. A rule with two different endpoints creates one A-versus-B test; an identical endpoint creates one self-intersection test. Detection Type and tolerance come from the rule. After applying the diff, run the tests manually.

Federation binding and drift

The local binding is keyed by organization and federation identity. Content changes with the same remembered sources produce a non-blocking rescan warning. Added, removed, renamed, or unmappable sources require review.

If a federation moves and no local binding exists, ClashWise may suggest matching server profiles; the user chooses once. If validation cannot prove the binding, publish explicitly unbound rather than attaching the wrong setup.

A rescan changes the semantic revision only when mapping, selected classes, or exact raw search variants materially change. Fingerprint-only drift is recorded without invalidating the binding.

Default and dedicated matrices

New profile-bound sets use the setup's default matrix. On republish:

ProfileDefault sets adopt the profile's current matrix and mapping.
Explicit sets keep their dedicated matrix and mapping.

Generating a matrix from a clash set creates an Explicit assignment. It always wins over the profile default.

Delete a setup

Deleting a Coordination setup removes the server-side profile. It does not silently delete native search sets/tests or unrelated matrices. Review any local managed artifacts separately in Navisworks.