Supporting fabrication customers
This is the internal playbook for helping customers who use ForgeFab and Beacon to spool, track, and install fabrication work. It mirrors the customer help center, from the side of the person answering the question.
The product map
Momentum SaaS
Revit time tracking. The account, billing, and seat home. Staff manage it in the Ops console.
ForgeFab Revit addin
Models and spools fabrication in Revit, then exports packages to Beacon.
Beacon fab web app
Where packages, labels, the 3D model, labor, and install tracking live. Field and shop facing.
BeaconFVR field VR
Walk the model in the field or VR. Separate from Beacon fab.
The fab flow, end to end
- Model and export. In Revit, ForgeFab groups untagged duct into packages and runs Export to Beacon. Hand-spooled work is never touched.
- Packages and pills. A Duct Prefab Package is 2 to 3 connected parts with a package number like
EA-L1-03. Every part also gets a pill likeEA1-42. Diffusers, grilles, and dampers are kitted, not welded in. - Labels. Each package prints a QR and barcode from a project's Labels tab. Scanning opens the package in Beacon.
- Master model. All packages stitch into one 3D view colored by system. Shift-click parts to multi-select, then Add to package to regroup. Reassigned parts recolor to their package.
- Install. In install mode, tapping a part marks it installed (green vs amber). Progress is shared across the crew live.
- Status back to Revit. When a package is Approved or beyond, the addin's Sync from Beacon grays and pins those parts so approved work can't drift.
Numbering, for quick reference
EA1-42 | Part pill. System + level prefix (Exhaust, Level 1), then a sequence 1 to 999 per level. Never collides across floors. |
EA-L1-03 | Package number. System, level, sequence. This is what a QR label resolves to. |
EA-L1-KIT | Kit. Loose terminals and dampers for a zone, shipped with the run but not welded in. |
Common questions and fixes
A scanned QR opens a
.web.app address.Old labels printed before the domain fix. New links point to getmomentum.studio, and
.web.app visits now bounce there automatically. Reprint any label printed before mid-July 2026.A label won't scan or shows "not found".
The label predates the current export. Reprint from the project's Labels tab after a fresh Export to Beacon.
Parts or pills aren't showing in Beacon.
The model needs a re-export with the current addin so it carries the package and pill parameters.
Export to Beacon errors out.
If it mentions a connector or "PhysicalConn", they're on an old addin build. Have them update ForgeFab and retry on a scratch model.
A field worker hits "sign in required" when scanning.
Beacon package pages currently need a Momentum sign-in. A public field-scan view is a pending decision; escalate if a customer needs no-login scanning.
Escalation and links
Customer chat routes here once wired. For now, customers email support and it reaches the team. Account actions (billing, seats, resets) live in the Ops console.