Capacity terrain
A React component in Beamline's Data & tables category.
A schedule that stands on a terrain of capacity: under each station's lane of jobs, every day's load rises to its capacity line and an overload is a cliff above it that says how far over, with every overloaded day said in the head. Drag a job (from To schedule or the board), or pick it and aim it with the keys, and the start days where it fits for its whole length light as valleys while a dashed ghost and the terrain preview it in place and a line says where it fits; drop anywhere, an overload said. Required staff against the rota run as a lane beneath, a short day marked.
Use it for
- Fitting a new job into a week of stations, crews or chairs with daily capacity: print and sign shops, workshops, salons, production lines, field crews.
- The host owns the stations' capacity, the jobs (days, hours a day, crew) and the rota; the part shows load against capacity and where a job fits, and reports placements.
Not for
- Dependencies and critical paths between tasks → gantt-chart or tension-timeline.
- Booking times inside a day → availability-layers or event-calendar.
Anatomy
- head: the label and every overloaded day in words (Press A is over on Fri 7 Nov by 6 h), or Every station fits its week
- fit line: while a job is in hand, where it fits on the station under it, and where starting there goes over
- board: the days across; per station a lane of job bars (name, hours a day; overlapping jobs stack) and its terrain (each day's load rising to the dashed capacity line, an overload a cliff above it with over N h); while aiming, valleys light on the lane and a dashed ghost shows where it lands (green where it fits)
- staff (with assigned): per day Required and Assigned, a short day marked short N
- To schedule: jobs not placed yet (days, hours a day, crew), or Everything is placed
States
- at rest
- an overloaded day
- a job in hand (valleys, ghost, preview)
- fits nowhere
- placed
- placed over capacity
- staff short
- every station fits
- nothing to schedule
Keyboard
- Each job is a button named by its name, length, station, first day and hours a day: Enter picks it; Left and Right move its start, Up and Down its station (keeping the day where it fits there, else the nearest day that does); Enter places it; Delete sends it to To schedule; Escape puts it back where it was
- Each terrain day is named by its station, day, load and capacity; placing is said once (a polite status), with the days it goes over
Motion
The terrain rises and falls on transforms as a job is aimed or placed; the job in hand's hours stack on it as a striped layer; the room under the capacity line lights where it fits; placed jobs glide (the shared FLIP). Nothing runs at rest; reduced motion places everything.
Props
| Prop | Type | Default | Description |
|---|---|---|---|
label (required) | string | — | What the board plans: "Production, week of 3 Nov". |
days (required) | TerrainDay[] | — | |
stations (required) | TerrainStation[] | — | |
jobs (required) | TerrainJob[] | — | |
value | TerrainPlan | — | Placements by job id; default the jobs' own station and start. |
defaultValue | TerrainPlan | — | Initial selection when uncontrolled; omitted by default. |
onValueChange | ((plan: TerrainPlan) => void) | — | Reports the selected value after a change; no callback by default. |
assigned | readonly number[] | — | People on the rota per day; with it, Required and Assigned lanes run under the stations. |
unit | string | — | The unit of capacity and hours. Default "h". |
className | string | — | Classes on the documented visual root; no override by default. |
classNames | Partial<Record<"root" | "board" | "lane" | "terrain" | "job" | "tray", string>> | — | Classes for the named visual parts; no overrides 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. |
defaultAim | { job: string; station?: string | undefined; } | — | Open with a job already in hand (a rush order to fit, a draft): picked and aimed at a station, its valleys lit, without taking the page's focus. Omitted by default. |
Import
import { CapacityTerrain } from "@beamline/capacity-terrain";
Get it
Capacity terrain 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
More in Data & tables
- Living table: A table that shows as much as fits on both axes: width decides which columns show (the rest ride in the name line, moving there rather than vanishing)…
- Availability layers: A week of bookable start times whose closed times explain themselves: every availability rule (hours, time off, bookings, buffers, rooms, lead time…
- Domino move: A room board where one move shows its chain: drag a booking (or pick it and aim it with the keys) onto a taken room and the bookings it would push appear…
- Match board: Month-end matching as one picture: bank lines and books entries side by side with threads between them — solid for matched, dashed with the host's reason…
- Split anything: One splitter for money, quantities and time: a bar of the whole shows every target's part and what is not split yet; items are dragged onto targets…
- Approval route: A policy you can read by trying it: an amount on a log scale with the thresholds as marks (the arrows stop just under, at and just over each), the…
- Proposal twin: A proposal edited beside the client's exact page, the two linked both ways: a field in focus lights its twin on the page, scrolls it into view and joins…
- Quantity river: The life of one order line's quantity: at rest a bar of its real split ("5 delivered · 1 back in stock · 1 damaged · 5 cancelled"), unfolding into a…
- Stock horizon: Projected stock per item over the coming weeks: a strip of weeks with the safety line, weeks under safety in warn and short in danger, every dip said in…
- Ageing queue: Tickets that visibly age: each ticket's ring fills toward its own service target and steps from on time to late to very late, the words say when it is…
- Import lens: A messy import made fixable by kind: rows stream through the checks once with live counts; problems gather into groups that say what is wrong in words…
- Duplicate guard: A new record that watches for the one that already exists: as you type, the likely duplicates slide in beside the form with the fields that match lit and…
- Scan flow: A pick list that takes scans: each scan flies from the scan field into its row and fills that row's quantity ring, and the prompt moves to the next bin…
- Pack planner: The packing bench: the order's items sit in box outlines drawn to scale, each box filling to its padding line, weighing against its limit and naming the…
- Provenance lens: Hold Alt (or press Lens) over any number on the page and see what makes it: hairline threads draw from the number to the rows, cards and documents on…
- Record time machine: The record itself, rewound in place: a slim track of every change (a tick per change in its person's colour, hollow for automation, named moments as…
- Tension timeline: A plan where slack is something you see: every dependency is a string from one task's end to the next one's start, sagging with the days it has to spare…
- Replay bar: Rewind for anything live: pause a stream, scrub back to the moment you missed (markers for the ones that matter), step one update at a time, replay at a…
- Event calendar: A schedule of events by day, week or month: events that overlap sit side by side, drag one to another time or day or pull its bottom edge to change its…
- Kanban board: Work as cards in columns by stage: drag a card (or lift it with Space and walk it with the arrows) to another column or place, the cards around it make…
- Data grid: Virtualised local or server-driven grid: stable row IDs, manual sort and filters, pages or infinite loading, retry without losing rows, inline editing…
- Pivot table: Records summed up by the fields people choose: rows grouped by one or more fields that fold open level by level, columns split by another, one or more…
- Query builder: Conditions people build by hand to pick out records: each rule is a field, an operator that fits the field (contains, between, in the last N days, is any…
- Sort order: Several sort keys in order. Each key says its rank in words ("Sort by Plan, A to Z", "then by Size, largest first") with its order named for the field's…
- Metric rules: Ordered rules that colour a dashboard number. Each rule has a name for what its colour means ("At risk", not just red) and a tone (good, watch, act…
- Log viewer: Log lines as they stream: it follows the newest line until you scroll up, then counts what arrived and brings you back in one click; filter by level with…
- JSON viewer: A JSON value as a tree you can read and walk: branches open and close (one level, or all at once), closed ones preview what they hold, every value reads…
- JSON diff viewer: Two versions of a JSON value compared as one tree: added keys marked +, removed ones struck through with −, changed values read old → new, unchanged keys…
- Import mapping: Map the columns of a file to the fields of one record type, see what every value becomes, then run the import and get an outcome for each row…
- Diff table: Proposed edits to a table before they happen: new rows green, removals struck through, changed cells old → new; each change can be left out and Apply…
- Filter toolbar: The filters on a list kept in view: chips that remove themselves, Add filter with fields and their values, Clear all, and room for search or view controls.
- Table: A native HTML table for small datasets, composed with children or driven by records; shared server paging, sorting, filters, search, stable-ID selection…