Automation Examples
CRAFT automations are deterministic, repeatable sequences that run inside your
CAD host. Each example below shows a realistic engineering task — what it
does, what the Gate checks, and what it produces.
These are illustrative examples of the types of automations CRAFT supports.
Actual available automations depend on published artifacts in your registry
and your seat entitlement. You can create automations by
describing a task or using
a guided form. Once proven, automations can be
promoted to your team's shared library.
Door Schedule Audit
Extract all door family instances from the active Revit model, validate that fire rating, hardware set, and frame type parameters are populated, and generate a summary report.
- Inputs
- Active Revit model, target categories (Doors), required parameters list.
- Preview
- Lists all door instances found, flags elements with missing or blank parameters, shows report output path.
- Gate checks
- Verifies Revit host is available, target categories exist in the model, no egress is required (report is written to local file). Egress disclosure: all false.
- Output
- A local CSV file listing every door instance with parameter status (populated / missing / blank). No model modifications.
- Useful for
- BIM coordinators, project managers preparing for submission.
Layer Name Standards Check
Scan all layers in the active drawing against a naming standard template. Flag non-compliant layers with the specific violation and expected pattern.
- Inputs
- Active Civil 3D drawing, layer naming standard (selected from template library).
- Preview
- Shows number of layers to check, the naming rules that will be applied, and the report output format.
- Gate checks
- Verifies Civil 3D host is available and the drawing is loaded. Read-only operation — no layers are renamed or deleted. Egress disclosure: all false.
- Output
- A structured report listing non-compliant layers, the rule violated, and the expected name pattern. The drawing is not modified.
- Useful for
- CAD managers, design technicians responsible for standards compliance.
Room Parameter Propagation
Read department and finish schedule data from a CSV, match rooms by number, and write parameter values to corresponding Room elements in the Revit model.
- Inputs
- Active Revit model, CSV file path, parameter mapping (CSV column to Revit parameter name).
- Preview
- Shows the full list of rooms that will be updated, the current and proposed parameter values for each, and any rooms in the CSV that have no match in the model.
- Gate checks
- Verifies Revit host is active, CSV file exists and is readable, all mapped parameters exist on Room elements. Blocks if any mapped parameter is read-only. Egress disclosure: all false.
- Output
- Updated parameter values on matched Room elements. Unmatched rooms are logged but not created. A summary shows counts of updated, skipped, and unmatched entries.
- Useful for
- BIM coordinators, interior designers managing finish schedules.
Corridor Station Labeling
Place station and offset labels along a corridor alignment at specified intervals, using the project label style.
- Inputs
- Active drawing, target alignment name, label interval (e.g., 25m), label style name.
- Preview
- Shows the alignment path, proposed label locations along the corridor, and the label style that will be applied.
- Gate checks
- Verifies the alignment exists, the label style is available, and the interval produces a valid label set. Blocks if the alignment has no profile or the label style is missing. Egress disclosure: all false.
- Output
- Station labels placed at the specified intervals along the corridor. Label count and placement coordinates are logged.
- Useful for
- Civil engineers, design technicians working on corridor documentation.
Wall Type Schedule Export
Generate a schedule of all wall types in the model with layer structure, total thickness, and thermal properties. Output as a formatted local file.
- Inputs
- Active Revit model, output format (CSV or JSON), included properties list.
- Preview
- Lists all wall types found, the properties that will be extracted, and the output file path.
- Gate checks
- Verifies Revit host is active, wall types exist in model. Read-only — no model changes. Egress disclosure: all false (output is a local file, not network).
- Output
- A local file containing wall type data with layer structure, thickness, and selected properties. No model modifications.
- Useful for
- Specification writers, energy modelers, BIM coordinators.
IFC Coordination Export
Export selected model categories to IFC format with controlled property mappings and declared network destination for coordination upload.
- Inputs
- Active Revit model, categories to include, IFC schema version, property mapping template, upload destination URL.
- Preview
- Shows selected categories, element counts per category, mapped IFC properties, file size estimate, and the declared upload destination.
- Gate checks
- Verifies all selected categories exist, property mappings are valid, and upload destination is reachable. Egress disclosure: network_egress is true, destination URL is shown. User must acknowledge before proceeding.
- Output
- Local IFC file generated and uploaded to the declared destination. Upload receipt logged locally. No other data leaves the machine.
- Useful for
- BIM coordinators managing multi-discipline coordination.
Anatomy of an Automation Artifact
Every CRAFT automation artifact is a signed zip containing a manifest and
execution steps. It declares its type, required parameters, compatible hosts,
and expected operations.
Content-Addressed
SHA-256 hash of the zip bytes serves as the artifact's identity.
Signed
ES256 signature verified by the client before import using trust anchors.
Immutable
Once published, a version cannot be overwritten. Updates require a new SemVer version.
Every Example Follows the Same Pattern
Create your automation by describing it in plain language or using a guided form.
Review the draft. Validate through the mandatory Gate. Execute locally. Whether the
automation reads model data, writes parameters, or exports files, the same trust
contract applies: you see everything before it runs, and nothing happens that the
Gate did not disclose.
Run One of These in Your Environment
Request early access and try any of these automations in your own Civil 3D or Revit project.