Revit Add-ons: ELLAH-M: A Structural-Production Toolkit

Executive Overview

ELLAH-M is a Revit productivity add-in developed specifically for structural engineers and BIM teams. Its currently published core automates structural-column numbering, foundation and pile numbering, and two-way Excel exchange. Broader tools presented on the developer’s website extend the concept toward project setup, view and sheet creation, opening and recess modeling, and future automated pile layout.

The add-in’s central design idea is continuity across the structural workflow: marks assigned to columns can drive the identification of supporting pile caps and individual piles; selected model data can move to Excel for coordination and return to the correct Revit elements; and office standards can be reused to establish views and sheets in new projects. This makes ELLAH-M less of a general-purpose utility collection and more of a structural-production toolkit centered on numbering, information consistency, and drawing setup.

Product-status distinction: Autodesk Marketplace currently presents column numbering, foundation and pile numbering, and Excel export/import as the principal released capabilities. The developer’s version 1.3.1 website also advertises Project Setup and FastVoid as available in the trial, while some page sections still label FastVoid and automated pile layout as in development. Teams should therefore confirm the exact feature set in the installed Marketplace build before relying on website previews.

Structural Column Numbering

ELLAH-M scans structural columns, sorts them according to the chosen project logic, and writes sequential identifiers directly to Revit’s native Mark parameter. The tool is intended to replace manual renumbering across multiple levels while preserving a predictable relationship between vertically aligned structural members.

Published Capabilities

Multi-level numbering: Columns can be numbered across the full project rather than one level at a time.
Existing-mark continuity: The Marketplace states that the tool can continue from existing manual numbering without overwriting intentional marks.
Preview before commit: Proposed changes can be reviewed before values are written to the model.
Native undo: Changes support Revit’s standard Ctrl+Z undo workflow.
Structural-category targeting: The tool is described as operating on structural columns, limiting accidental edits to unrelated architectural columns or other categories.
Flexible scope: Developer material describes full-project, single-floor, selected-range, and manual numbering modes.
Snake Path: A newer interactive method lets the user move the cursor over columns in the desired sequence without clicking every element. Published controls indicate Space can skip a number and Ctrl can finish the path.
Output choice: Developer demonstration material states that Snake Path can write the sequence to Mark or Comments while maintaining vertical numbering continuity across floors.

Foundation and Pile Numbering

ELLAH-M links substructure identification to the structural column above. If a column is marked 140, the supporting pile cap can receive 140 and the piles beneath it can be labeled 140A, 140B, 140C, and so forth. This preserves a recognizable vertical relationship from superstructure to foundation plan and reduces disconnected manual naming.

Published Capabilities

Column-driven marks: Foundation and pile identifiers derive from the supported column’s mark.
Multiple foundation arrangements: The Marketplace lists support for single piles, grouped piles, and pile caps serving multiple columns.
Office-family support: The developer states that the workflow works with standard Autodesk families and custom office families.
Bilingual family recognition: Published material specifically identifies English and Hebrew family names.
Direct Revit storage: Values are written to the native Mark parameter, allowing them to flow into ordinary tags and schedules.

The method is most valuable when the structural team’s naming standard intentionally ties pile and cap identifiers to column marks. Firms using independent foundation numbering, grid-based codes, or contractor fabrication marks will need to verify whether the built-in logic can match their conventions.

Excel Export and Import

The Excel workflow exports selected Revit information to a structured XLSX workbook, allows users or external collaborators to edit values, and imports updates back into the correct model elements. This supports coordination with office schedules, reviewers, and external structural applications that work more efficiently with tabular data.

Published Workflow

Select an element category and level.
Choose the parameters to include.
Export a styled Excel workbook containing model data.
Edit approved values outside Revit.
Import the workbook and write the changes back to the corresponding elements.

Supported Data

Categories: Columns, walls, beams, doors, and windows are explicitly listed.
Standard fields: Level, Mark, and Type can be included.
Custom parameters: Users can add selected project or shared parameters to the export.
Round-trip coordination: The tool is intended to maintain element correspondence so imported values return to the proper Revit objects.

This is a data-exchange feature, not unrestricted spreadsheet synchronization. Before use, teams should test how the add-in identifies elements, handles deleted or duplicated rows, validates data types, treats read-only, type, and instance parameters, and reports failed imports.

Project Setup and Office Standards

The developer site describes a Project Setup feature that reads a completed office reference project and recreates its production structure in a new job. The stated workflow learns the office’s view series, view templates, browser folders, and sheet organization, then builds structural views and sheets for each floor.

Advertised Functions

View generation: Create recurring structural view sets such as slab plans, top-reinforcement plans, bottom-reinforcement plans, and sections.
Sheet creation and placement: Establish sheets and organize generated views according to the reference project.
Template reuse: Transfer or apply established view templates.
Browser organization: Reproduce office project-browser folder logic.
Existing-view option: Developer posts state that, if views already exist, the tool can focus on arranging sheets to match the reference.
Tag-family transfer: Developer material also describes transferring loaded tag families rather than loading them individually.
Saved settings: Project-setup preferences can reportedly be reused and restored after a new architectural link is loaded.

Project Setup has potentially broad model impact because it can create and organize many views and sheets. Confirm that it is included in the installed version and test naming collisions, duplicate views, template dependencies, browser parameters, title blocks, sheet numbers, crop settings, and linked-model behavior before production use.

FastVoid and Planned Pile Layout

FastVoid

The developer describes FastVoid as a tool for quickly creating recesses or openings inside a structural member on a user-selected face, including recesses in structural columns. Its role is to reduce manual void-family placement and improve opening coordination. However, the developer site contains mixed status language: FastVoid is listed among trial features while another section labels it in development. Its installed availability, supported hosts, family behavior, and limitations should be verified directly.

Automated Pile Layout

An automated pile-layout tool is presented as a future capability that would use soil-report information and basement-slab geometry to develop a pile plan. The website explicitly describes this feature as in development. It should not be included in current purchasing or deployment decisions until it appears in released documentation and can be tested in Revit.

Compatibility, Pricing, and Access

Supported Revit releases: Revit 2024, 2025, 2026, and 2027.
Operating system: 64-bit Windows 10 and Windows 11.
Current version: The developer website identifies version 1.3.1 as live on Autodesk Marketplace.
Trial: A 30-day trial is available through Autodesk Marketplace, with all included features unlocked during the trial.
Subscription: Published pricing is US$8 per month or US$79 per year. Taxes, regional pricing, renewal terms, and future changes should be confirmed at purchase.
Entitlement: Access is managed through the user’s Autodesk account and the Autodesk Entitlement API.
Distribution: The add-in is obtained through Autodesk Marketplace.
Publisher focus: The publisher describes its work as Revit API development and structural workflow automation.

Practical BIM and Structural-Engineering Assessment

Where It Adds Value

Large vertical structures: Multi-level towers and repetitive framed buildings benefit from consistent column numbering across floors.
Foundation coordination: Column-derived pile and cap marks make it easier to trace load-path relationships between plans and schedules.
Reduced transcription: Automatic marks and round-trip Excel exchange reduce repeated manual entry and the associated risk of skipped or duplicated values.
Office-standard deployment: Project Setup could shorten the effort required to recreate view, template, browser, and sheet conventions in each new project.
External coordination: XLSX exchange provides a familiar format for reviewers or analysis workflows that do not operate directly in Revit.
Incremental adoption: Numbering and Excel tools can be piloted independently before broader model-setup or opening-generation functions are introduced.

Best-Fit Users and Projects

ELLAH-M is best suited to structural engineers, Revit modelers, BIM coordinators, and drawing-production teams working on multistory buildings, piled foundations, or office-standardized structural documentation. Its value will be highest where marks drive plans, schedules, details, or downstream coordination. Projects with small element counts or unconventional identification systems may see less benefit.

Limitations and Governance Considerations

Feature descriptions are evolving: The Marketplace listing and developer website do not present an identical scope. Confirm released versus preview functionality in the specific installed build.
Numbering logic must match the standard: Sorting and vertical-continuity rules should be tested against grids, offsets, slanted columns, split columns, transfers, design options, and phased elements.
Marks have downstream consequences: Changes can affect tags, schedules, drawing references, exports, fabrication identifiers, and coordination records.
Existing values require protection: Although the Marketplace states that intentional marks can be preserved, teams should test duplicates, blanks, locked conventions, manual exceptions, and restart behavior.
Foundation relationships can be ambiguous: Multi-column caps, eccentric supports, battered piles, linked geometry, shared foundations, and nonstandard families may challenge automatic association.
Excel round trips require controls: Unvalidated worksheets can introduce incorrect units, invalid values, duplicate marks, type/instance conflicts, or edits to parameters that should be governed in Revit.
Project Setup can create broad changes: View, template, sheet, and browser automation should be tested on a copy and reviewed for duplicate names, dependencies, and office-specific parameters.
FastVoid is not code coordination: Creating a recess does not confirm structural adequacy, reinforcement clearance, fire protection, clash resolution, or approval by the responsible engineer.
Cloud entitlement dependency: Autodesk-account validation means activation and continued access may depend on sign-in, Marketplace entitlement, and network availability.
Limited independent evidence: The product is new, with little independent technical review. Most detailed claims originate from the publisher.

Recommended Evaluation Before Production Deployment

Confirm the installed version, exact included features, supported Revit build, pricing, renewal terms, and Autodesk-account requirements.
Use a detached or copied model containing representative structural columns, levels, grids, piles, pile caps, walls, beams, doors, windows, phases, groups, and design options.
Test full-project, floor, range, manual, and Snake Path numbering; compare the resulting sequence with the firm’s written convention.
Verify behavior for existing marks, skipped numbers, duplicates, stacked columns, transferred columns, and vertically misaligned members.
Test pile and cap numbering on single piles, grouped piles, multi-column caps, custom families, and bilingual family names.
Export each supported category to Excel with standard and custom parameters; edit a controlled sample and verify exact round-trip element matching.
Test malformed, reordered, filtered, duplicated, and partially deleted spreadsheet rows to understand import validation and error reporting.
If Project Setup is present, run it in a blank test project and audit created views, view templates, browser folders, sheets, numbers, title blocks, and tag families.
If FastVoid is present, test supported hosts, faces, rotations, depths, family behavior, structural warnings, and changes to the host element.
Measure time saved, correction effort, model warnings, audit findings, and user training needs against the current manual process.
Define permissions, backups, review ownership, and approval rules before writing bulk marks or importing spreadsheet changes into a central model.
Document which features are approved for production and which remain pilot-only or unavailable.

Sources Consulted

Autodesk Marketplace — “ELLAH-M”
ELLAH-M — “Structural Tools for Revit”
Developer announcement — Snake Path and upcoming tools
ELLAH-M — Excel import/export demonstration
ELLAH-M — floor-range numbering demonstration

Source-quality note: Autodesk Marketplace is the primary source for the released core feature set, compatibility, trial, and subscription model. The developer website and demonstrations provide additional workflow details and roadmap information. Where those sources differ on release status, this summary identifies the uncertainty rather than treating previewed functionality as definitively available.