How ZEN runs a federation
From registry to batch execution to audit trail.
ZEN converts project governance into a repeatable execution workflow: define the model registry, define the link matrix, run the ACC Gate engine, execute the batch, and review per-model reports.
Workflow structure
Five stages turn project rules into governed execution.
The process is intentionally structured. ZEN is not just a shortcut for linking. It uses reviewable project data, applies repeatable logic, and produces a usable record of what happened in the batch.
Model Registry
Region, Project GUID, and Model GUID are collected into a structured source listing every cloud-hosted model involved in the project.
Cloud Link Matrix
Host/link rules, worksets, coordinates, room bounding, and attachment logic are defined before execution begins.
ACC Gate
ZEN opens cloud models by GUID and runs governed model operations directly in Revit — without relying on Desktop Connector paths.
Batch Run
Links are created or repaired, setup is normalized, workset logic is applied, models are saved, and execution continues automatically through the queue.
Reports
Per-model logs capture exceptions, outcomes, and processed items — creating an audit trail for what was executed and corrected.
Why this matters
Repeatability, visibility, and project-scale control.
Why the workflow matters
Large federated projects fail when linking logic lives only in local habits. ZEN shifts that logic into project-controlled sources that can be reviewed, updated, and executed consistently.
What the reports provide
- Per-model outcome tracking
- Error visibility for failed items
- Audit trail for execution review
- Repeatable reruns when project conditions change
See the full platform
Ready to explore the full ZEN workflow?
Move back to the main ZEN page, or start a conversation about how cloud linking, federation governance, and automation can support your delivery environment.