FABRIX 2.0 - SAMPLE INPUTS AND RESULTS
Captured: 20 November 2026
Staging: https://fabrix.dnjfactory.online

WHAT TO UPLOAD
01-Tekla-10-Connections-Revision-A.json  -> Connection Library > Register & groups > Import Tekla connection export
02-Tekla-10-Connections-Revision-B.json  -> same module; use to demonstrate changed revision and superseding cards
03-IFC4-Mini-Frame.ifc                   -> Model Intelligence > Import IFC model
04-Deck-Weld-Master-Table.csv            -> Deck Job Cards > Import master table
05-Deck-Part-List.csv                    -> Deck Job Cards > Import part list (after master CSV)
06-FABRIX-MTO-Template.csv               -> Model Intelligence > Browse files (or download from CSV template)

WHAT OUTPUT TO EXPECT FROM THESE SAMPLES
The supplied Tekla revision A contains 33 welds grouped to 11 physical connections, including a group of ten matching connections.
The worked card is locally checked, not company-approved.
Fabrication labour: 16.04 hours; machine: 4.14 hours.
Recorded access: 2 hours one-time scaffold setup plus 0.7 x 10 = 7 hours, total 9 hours.
Total illustrative labour including access: 25.04 hours.
Recorded access rate: AED 60/h; extra cost AED 540.
Baseline fabrication cost: AED 991; adjusted illustrative cost: AED 1531.
The deck master CSV has 7959 accepted rows, 8 decks; the matching Part list contains 1421 parts.
A captured reference run displayed 21,000 planned hours after both deck inputs.

RESULT FILES
Example-Connection-Job-Card.pdf   -> generated A4 connection job card
Example-Connection-Register.xlsx  -> generated five-sheet workbook
Example-Connection-Register.csv   -> generated connection card CSV
Example-Deck-JobCards.xlsx        -> generated deck workbook
Example-Deck-JobCard-Print.pdf    -> printed deck job-card PDF
EXAMPLE-RESULTS.json             -> inspectable source calculation object

IMPORTANT
All files are reference fixtures, not from a licensed live Tekla installation.
No source files, wages, rates, client drawings or checks in this ZIP are company-approved.
The web frontend currently persists project state in browser localStorage despite a deployed
company-scoped D1 API. Different browsers/devices are not yet synchronized.
Do not submit customer tender documents from these samples.
