Contextual user guide

What FABRIX actually does

Honest status by capability, a complete sample walkthrough and a short management summary. Nothing here is a formal engineering approval.

Working verified functionality

Implemented, reachable from the UI and covered by automated tests. Engineering formulas, imports (where stated) and exports in this category are exercised by the test suite.

  • CSV/JSON MTO import with rejection reasons and duplicate quarantining
  • Tekla contract fixtures → welded connection recognition with per-weld specifications
  • Fabrication calculation, resource-aware schedule, job-card revisions and PDF/Excel output
  • IFC quantity takeoff from IfcElementQuantity in Model Intelligence
Demonstration / sample data

Real code paths running on clearly labelled sample values. The numbers are not company rates, time studies or client data.

  • Sample projects, section profiles, connection templates and demo connection register
  • Crew size, shift length, handling and lifting allowances
  • Every rate in the Rates library unless replaced by a released company sheet
  • Workbook-transcribed rates from '3026001-JB-001 — Master file — Sample.xlsx'
Requires company validation

The mechanism works, but an authorised engineer, planner or commercial manager has not confirmed the values or the rule for production use.

  • Every local check recorded in this browser — it is not a formal approval
  • Workbook reconciliation discrepancies left in the validation tracker
  • Groove preparation formulas and deposition rates
  • Access/scaffolding allowances, even when recorded
Unsupported or future integration

No claim is made that these work. Running the app does not enable them, and no placeholder is presented as analysed data.

  • PDF/DWG drawing takeoff and OCR — reference attachments only
  • STEP/IGES geometry takeoff
  • Live Tekla Open API connection from the browser (the .NET companion is a separate Windows tool)
  • Shared cloud storage, real authentication and server-side approval until the Cloudflare backend is deployed and migrated

Sample project walkthrough

Open workspace
  1. 1
    Import engineering data

    Open the Import tab and drop the Tekla batch fixture or an MTO. Review parsed/rejected counts, duplicates and reconciliation.

    Import →
  2. 2
    Identify ten identical connections

    The register groups identical welded configurations by engineering fingerprint. Three welds on one joint are one connection, not three.

    Connections →
  3. 3
    Calculate once

    Calculate the ten-occurrence configuration. The other occurrence set stays separate because its plate differs.

    Calculations →
  4. 4
    Review man-hours and duration

    Man-hours, machine hours and scheduled elapsed time are shown separately. A machine-bound cut cannot be shortened by adding fitters.

    Open calculations →
  5. 5
    Record a check

    A named engineer records the local check. This is traceable and explicit, but it is not an authenticated company approval.

    Verification →
  6. 6
    Generate the job-card package

    Issue connection, assembly or batch cards. Shared setup, access and lifting allowances are counted once per card, never per connection.

    Generate cards →
  7. 7
    Revise one connection

    Import revision B. The changed fingerprint produces a new draft revision; the previous card is superseded and stays printable with a historical banner.

    Revision workflow →

The walkthrough is self-contained and needs no Tekla installation: the demo register and the committed batch fixtures exercise the same code path as a real export. A licensed Tekla export has not been compared with a Tekla report.

Management summary

Project
FX-TDR-2611-001
Steel tonnage
21.6 t
Tender price
AED 360,780
Connections
14
Configurations
5
Checked cards
0
Deck datasets
0
Current calculations
1
Locally checked
1
  • One workflow. Project → data → connections → calculations → cost & duration → cards → verification → reports.
  • One calculation per configuration. Ten identical connections are calculated once; shared allowances are counted once.
  • No invented quantities. Missing data blocks the step and is listed with its owner-facing reason; access is excluded unless recorded.
  • Data is local today. The D1 schema and API are prepared in the repository but not deployed; multi-device operation requires that deployment and a local-backup migration.

Where to find things

Local demonstration record: a named person reviewed the calculation inside this browser. It is not an authenticated company engineering approval.