Press fleet: two Newbilt Duplex systems with an extruder per press, plus a Classic
The current plan (user decision, October 2026) replaces the 50/50 target (two semi-automatic presses and two Pheenix AD12s) with an all-Newbilt fleet of five presses: two Duplex systems in Newbilt's two-extruder configuration (two HRP 12 presses, an extruder each, one hydraulic unit) and one Classic fully automatic press. - pressing-line.md: new "Current plan" section (fleet table, what it means, phasing from the Single 2.1 as the first half of system 1, re-quote questions); site requirements per Duplex system. - scale.md: capacity table and basis (368 to 448 records/h, ~1.06 to 1.5M a year on two shifts, same range as before); pressing electrical row; steam and cooling flagged, not re-based: five presses draw ~750 to 900 kg/h of steam and up to ~625 kW of cooling at Newbilt's per-press figures, against the 400 kg/h / 250 kW sized for one Duplex. - total-investment.md: fleet change as an added-scope row (system 2 ~230k-300k and the Classic ~290k-460k, estimates; -60k / -160k against the two blocks it replaces); headline unchanged until the re-base. - roadmap items 4, 5 and 24, revenue model mature row, crane doc (the Classic's weight now decides 5 t or 3.2 t), vendor landscape (AD12 is the comparison for the Classic), README. The business plan docx is not regenerated.
This commit is contained in:
1 parent
f1334f4756
commit
c50417668b
8 files changed
+128
-48
No files matched your search
@@ -99,7 +99,7 @@ as output.
|
||||
| ResurRec, assuming one shift over 300 days | ~275k – 355k |
|
||||
| **CNX launch** (1 semi-auto, 1 shift) | **90k – 135k** |
|
||||
| CNX Duplex (2 semi-auto, 1–2 shifts) | ~175k – 540k |
|
||||
| CNX mature (2 semi + 2 automated, 2 shifts) | 1.0M – 1.5M |
|
||||
| CNX mature (4 semi + 1 automated, 2 shifts) | 1.0M – 1.5M |
|
||||
|
||||
All rows are on the same 300-day basis so they can be compared. CNX does
|
||||
not overtake them on installed capability until the Duplex expansion, and
|
||||
|
||||
Reference in new issue
Block a user