Print scheduler

A React block (a whole screen) in Beamline's Manufacturing app.

A print shop's production schedule. The week by station: each station's day holds its runs, with a load bar and minutes used against the station's minutes a day (capacity in minutes, never pieces), runs without an estimate counted apart instead of as zero, and over capacity said and marked; runs with no day, no station or neither wait in a tray saying what they do have. Run cards show the fields of the saved view in its order (customer, pieces, estimate, production due, status in its colour). A run opens its imprint beside the schedule: the job (opened elsewhere, a failure said), production due and customer due kept apart, sizes and total, and its runs: each with pieces, an estimate (empty is no estimate), a day, a station of the right kind and a status; the pieces must add up to the job's before saving (short or over said as you type), a day's capacity is checked as runs are placed, removing a run first says how many pieces the rest keep, and all runs save together, a save someone beat keeping the edits until Reload; notes and files by audience (shop only or customer can see), files the viewer can't see counted, never shown; closing returns focus to the run. Saved views: the cards' fields chosen and ordered, the work shown, an unsaved layout said, shared with the team only when allowed, and deleting staged until saved. Stations and statuses: minutes a day with the hours beside them and whole-minute validation, archiving a station with runs on it refused with the count; each work type's statuses with a label and colour, moved up and down, and archiving one with runs in it refused with the count.

Use it for

Scheduling jobs onto machines or stations by day against capacity in minutes, with runs split across days and stations.
Setting up stations' daily capacity and the statuses work moves through.

Not for

Monthly stock planning (production-plan).
One workstation's queue on the floor (shop-floor).
Staff shifts (shift-planner).

Anatomy

head: Schedule or Stations and statuses; saved view, work shown, Save view, Delete view
schedule: the tray of runs not placed; days across, stations down, each cell's runs and load
imprint: job and Open job, the two dues, sizes, runs (pieces, estimate, day, station, status, remove), the allocation, notes and files by audience, Save runs
views dialog: name, who sees it, fields with move buttons
setup: stations (name, work, minutes a day, archive); statuses per work type (label, colour, moves, archive)

States

runs: no day and no station, station only, day only, placed, no estimate, over capacity
imprint: runs balanced, short, over; remove preview; saving, saved, conflict, failed; no mockup; files hidden; job unavailable
views: unsaved layout, personal, team, team not allowed, delete staged, saved
setup: invalid minutes, archive refused, archived, unsaved, saved

Keyboard

Every run is a button; placing a run is done with labelled fields in its imprint instead of dragging
Fields in a view and statuses move with Move up and Move down buttons naming them

Motion

Load bars grow to their new share. Nothing runs at rest.

Props

Prop	Type	Default	Description
`imprints` (required)	`Imprint[]`	—
`stations` (required)	`Station[]`	—
`workTypes` (required)	`WorkType[]`	—
`days` (required)	`string[]`	—	The days shown (ISO dates), usually a work week.
`views`	`SavedView[]`	—
`canShareTeam`	`boolean`	—	Whether this person may share views with the whole team.
`onSaveRuns`	`((imprintId: string, splits: Split[]) => Promise<unknown>)`	—	Saves one imprint's runs together; reject with ScheduleConflict if they changed meanwhile.
`onReloadImprints`	`(() => Imprint[])`	—	The imprints as saved now, after a conflict.
`onOpenJob`	`((jobId: string) => Promise<unknown>)`	—
`onSaveView`	`((v: SavedView) => Promise<unknown>)`	—
`onDeleteView`	`((id: string) => Promise<unknown>)`	—
`onSaveStations`	`((s: Station[]) => Promise<unknown>)`	—
`onSaveWorkTypes`	`((t: WorkType[]) => Promise<unknown>)`	—
`defaultView`	`PrintSchedulerView`	—
`defaultActiveView`	`string \| null`	—
`defaultOpen`	`{ imprintId: string; splitId?: string \| undefined; } \| null`	—	Initial open state when uncontrolled; defaults to false.
`locale`	`string`	—
`className`	`string`	—	Classes on the documented visual root; no override by default.
`style`	`CSSProperties`	—	Inline styles on the documented visual root; no overrides by default.
`ref`	`Ref<HTMLDivElement>`	—	Receives the documented native target or imperative handle; omitted by default.

Built from

segmented-control
select
multi-select
number-field
input
checkbox
radio-group
dialog
sheet
button

Dependencies

lucide-react

Import

import { PrintScheduler } from "@beamline/print-scheduler";

Get it

Print scheduler is part of Beamline UI. Install the parts you need in your React app as compiled packages or editable source. Get Beamline · Connect your agent

Print schedulerComplete system · $49

A print shop's production schedule.

Inkwell Press Co. · production

Capacity is minutes, not pieces: Auto press 1 is over on Tuesday, and a run with no estimate is counted apart instead of as zero. Runs missing a day or a station wait in their own tray.

0 × 0full

States

Each state as it first appears; the first action in each shows how it resolves.