HOLK Factory
Turning Independent Printers Into Coordinated Production Capacity.
HOLK Factory is the production software. It keeps the job, prepares the file, asks for authorization and records what was transferred. Coordination of many printers is the capability we are building toward.
Private production screens, customer information, device identifiers and credentials are not shown. Where a screenshot would have revealed them, this page uses an illustration of the job instead.
In development
A job is a record with a model, a preparation and a state. The laboratory path runs from intake to a transferred file. It does not yet run through a completed physical print.
In development
An owner pairs a Connect device with a one-time code. The device is then bound to that owner. Pairing is implemented in the Connect service. A fleet of enrolled printers is not in operation.
In development
Heartbeat and printer reports tell the service whether a device and its report are fresh. A report past the freshness window is offline. This rule is in the software. It has not been demonstrated across a running print.
Partly tested
Laboratory jobs have moved through created, preparing, ready to start and transferred. A second request for the same work returns the same job. A queue that schedules many independent printers is planned.
Tested in the laboratory
The laboratory software accepts an STL model and prepares it for the X1 Carbon profile used in the test, including the plate that was confirmed for that job. Preparation is rejected when the slicer result does not match the requested settings.
Tested in the laboratory
OrcaSlicer prepares the machine file. A verified laboratory file used PLA Basic, a 0.4 mm nozzle and a Textured PEI plate on the X1 Carbon. This does not mean every geometry, material or printer profile is supported.
In development
A printer is not opened for work merely because a device is online. Registration, a fresh report and a separate preparation confirmation are different gates. That confirmation does not start a print.
Partly tested
A prepared file has been transferred to the laboratory X1 Carbon. The printer's copy matched the checksum. The command that would start the print has not been sent.
Planned
Confirming that a print finished, and recording that fact from the machine, is a planned capability. No platform-started print has been completed.
Partly tested
Test jobs are stored with their state and their prepared file. The history describes laboratory work. It is not a public catalogue of customers or orders.
Planned
The future step is to treat several independent printers as coordinated capacity: choose a machine, follow the job and keep the record honest when a machine is busy or offline. That coordination is not operational.
The laboratory file
One prepared file for the Bambu Lab X1 Carbon was transferred to the printer. It used PLA Basic, a 0.4 mm nozzle and a Textured PEI plate. The checksum of the copy on the printer matched. The start command was not sent, and the print was not completed.