Asset workspace

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

One physical asset: a machine, vehicle or piece of plant. Its header keeps the system id apart from the name and serial, with type, site, status and the last inspection said in words (a meter reading never stands in for one); limited access, an offline summary and a retired asset are said; an inspection or action opens as a draft with the asset and site filled in. The overview gathers the last known location (place, coordinates and accuracy, when captured and received, from an inspection or a device, drawn on a map base when one is given (the fixes on real streets, the trail between them, the newest with its accuracy ring and place) or against earlier fixes, never a pin at 0,0; stale, unknown and restricted said), the meters with source and age, the maintenance plans by state and recent activity. Activity lists events by day, each with its type (an issue on the danger tone), who, when, the source and a link (no access said), filters by type and range, takes notes beside the events and holds new arrivals until asked. Usage draws use per day by engine hours or distance, a day without readings as a gap and a meter reset marked on its day, with the period's coverage said, a day-by-day table and an export.

Use it for

The page for one physical thing a team looks after: a machine, vehicle, generator, lift or instrument, with where it is, what happened to it and how much it worked.
Anywhere readings and locations must carry their source and time, and missing data must show as missing.

Not for

The due queue and plan setup across many assets (maintenance-plans).
A street map of a whole fleet (geo-map is not a street map).

Anatomy

header: the product's mark, an asset switch, Overview, Activity or Usage
identity: a type tile, name, id · serial · type · site, the status and last inspection on their tones; Start inspection and Open action (a draft with the asset and site filled in, said before it opens)
notices: limited access, offline since, retired
overview: location (with a map base the larger half, down the left: the fixes on the map with the trail, accuracy ring and place, then place, coordinates and accuracy, source, captured and received, stale; without one a locator drawn from the fixes), readings (value, source and age, stale), maintenance (plan and state in words), recent activity
activity: event types as colour toggles, range; new events waiting above the list; events by day with type, title, detail, who, time, source and a link or no access; a note box beside
usage: measure, last 14 or 30 days, Export; the period's total and coverage; a bar per day with gaps hatched and resets marked; legend; day by day

States

asset: in service, in the workshop, retired; full or limited access; offline summary; never inspected
location: from an inspection, from a device, stale, unknown, restricted, asking for a fix
readings: current, stale, none; maintenance unknown or none
activity: filtered, new events waiting, link restricted, no history, note saving, note not saved
usage: no readings, engine hours, distance, partial coverage, meter reset, export preparing and ready
drafts: opening, opened with its ids, refused
loading: shaped skeletons
phone: one column, the identity kept above
right to left: mirrored
reduced motion: through the tokens

Keyboard

Tab through the asset switch, the sections, the identity's actions, the cards' actions, the type toggles (Enter or Space toggles), the note and the usage controls

Motion

Type toggles tint in the fast duration; the day-by-day fold's chevron turns. Nothing runs at rest.

Props

Prop	Type	Default	Description
`assets` (required)	`AssetRecord[]`	—
`defaultAsset`	`string`	—
`defaultTab`	`"activity" \| "overview" \| "usage"`	—
`onStart`	`((q: { kind: "action" \| "inspection"; assetId: string; siteId: string; }) => Promise<{ …`	—	Open a draft inspection or action with the asset and site filled in. Resolve with its id.
`onRefreshLocation`	`((assetId: string) => Promise<LocationFix \| null>)`	—
`map`	`MapBase`	—	A map base the location is drawn on (`@/components/_shared/map-base`); without one the fixes are drawn against each other.
`onAddNote`	`((assetId: string, text: string) => Promise<AssetEvent>)`	—	Add a note beside the events (never replacing one). Resolve with the stored event.
`onOpenLinked`	`((ref: string) => void)`	—
`onExport`	`((assetId: string, measure: UsageMeasure) => Promise<{ file: string; }>)`	—
`now`	`string`	—
`loading`	`boolean`	—
`product`	`string`	—
`className`	`string`	—	Classes on the documented visual root; no override by default.
`ref`	`Ref<HTMLDivElement>`	—	Receives the documented native target or imperative handle; omitted by default.

Built from

Dependencies

lucide-react

Import

import { AssetWorkspace, EVENT_TYPES } from "@beamline/asset-workspace";

Get it

Asset workspace 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

Asset workspaceComplete system · $49

One physical asset: a machine, vehicle or piece of plant.

An asset at a glance

Excavator 14: its id apart from its name and serial, passed with notes five days ago (a reading never counts as an inspection). Its last location came from that inspection, five days old; ask for a fix and the tracker's answer replaces it, source and time together. Start an inspection and it opens with EX-014 and SITE-12 filled in; switch to Excavator 21 and nothing carries over.

0 × 0full

What happened to it

Events by day, issues on the danger tone, each with who, when, where it came from and a link (one issue raised on another contractor's site can't be opened, said). A new issue arrived while reading: it waits above the list until shown. A note sits beside the events and never changes one.

0 × 0full

How much it worked

Engine hours per day for the last 14 days: the weekend the tracker lost signal is a gap, not zero, and the period says how many days it covers. The tracker was replaced on Oct 19, marked on its day; the day counts from after the reset, never negative. The day-by-day table and an export sit under it.

0 × 0full

States

One state at a time, from Example state: an asset seen through a site's permissions with a three-week-old reading; an offline summary; a retired asset; a new asset with no history; a note that didn't save; loading.

0 × 0full

About Asset workspace

← Equipment register Asset packs →

Part of Beamline UI: polished, editable React components and complete screens for custom applications. Build your own style from any look; tokens, fonts, radii, motion; not only colours.

Asset workspace

Use it for

Not for

Anatomy

States

Keyboard

Motion

Props

Built from

Dependencies

Import

Get it

More in Construction