Press hall: five Duplex bays and four Classic positions (balanced at 60 % specials)
Deploy test site / deploy (push) Successful in 44s
Deploy test site / deploy (push) Successful in 44s
User (October 2026): "change the hall layout" after the finding that the 60/40 floor split leaves the Classics about half loaded at 60 %+ specials (specials run only on the Duplex systems). - Press hall now keeps five Duplex bays (four along the visitor corridor, the fifth at the head of the second row) and four Classic positions: 550 + 200 = ~750 m2 of ~870 m2, ~73/27 by floor, 10 to 4 by presses; launch plant fills one of each, growth adds Duplex first. - Full hall: ~2.9 to 4.4M records a year at 60 % specials, Classics ~80 to 100 % loaded (60/40 gave ~2.3 to 3.6M); ~3.2 to 4.4M at ~20 %; fourteen presses as before: ~2.1 to 2.5 t/h steam, up to ~1.8 MW cooling, a utility phase of its own. - pressing-line.md, scale.md, site-candidates.md, crane-workshop-tours.md, roadmap.md, README (FreeCAD model still the earlier layout, not redrawn); calculator preset "Full hall (5 D + 4 C)" and ladder; plant view reserves 5 Duplex bays and 4 Classic positions; business plan draft 0.2 rebuilt. Checks: renderer 720 checks and functional checks pass, calculator regression 0 fails, level checks clean; PDF 47 pages, TOC filled.
This commit is contained in:
1 parent
b3e8e4272b
commit
3f1e4452b8
11 files changed
+69
-66
No files matched your search
+2
-2
@@ -173,5 +173,5 @@ Since October 2026 the plant launches with everything in one capital
|
||||
round (~161M to 292M THB, target ~216M with the levers in
|
||||
[total investment](finance/total-investment.md#launch-plant-october-2026));
|
||||
the gates still come before the round is spent, and the growth options
|
||||
(more Duplex systems first, then Classics, in a press hall laid out 60/40
|
||||
for Duplex) are funded from revenue.
|
||||
(more Duplex systems first, then Classics, in a press hall laid out for
|
||||
five Duplex systems and four Classics) are funded from revenue.
|
||||
Reference in new issue
Block a user