Station Configuration

ops station configuration

Stations are the core organizational unit of the OPS system. Each station can be configured to control how jobs, machines, and people interact within it.

Configuration Options

Machine-Only Stations

A station can be configured as machine-only, meaning no people can be assigned to work on jobs at that station. This is appropriate for fully automated stages where machines operate without human labor.

• When machine_only = true, the station UI hides person assignment controls
• Time entries from people are not allowed at machine-only stations
• OEE calculations use only machine-hours for actual time at these stations
• Example: An automated CNC machining cell that runs unattended

Concurrent Jobs

A station can be configured to allow multiple jobs running simultaneously:

• When allow_concurrent_jobs = true, multiple jobs can be in in_progress state at the station at the same time
• This affects target OEE calculation — shared resources mean the per-job target may differ from the per-station target
• The process flow visualization must show all concurrent active jobs within the station container
• Example: A QC inspection station where multiple items can be inspected in parallel

Impact on Target OEE

When a station allows concurrent jobs, the target OEE must be adjusted:

• If a station’s target OEE is 90% and it typically runs 2 concurrent jobs, the effective target per job accounts for shared capacity
• The Efficiency Calculation page describes how concurrent work affects efficiency calculations
• Target OEE is set per Product Family per station via Station Product Standards

Station as a Container

Stations encompass three types of entities:

1. Machines — equipment assigned to the station that acts as stages for jobs
2. People — workers assigned to or clocked into the station
3. Jobs — production work orders currently at the station (pending or in_progress)

The process flow diagram renders stations as large rectangles containing their machines, people, and jobs.

Station Connections

Stations connect to other stations to define job routing:

Connection Type	Purpose	Triggers Auto-Advance?
feeds_into	Normal forward production flow	Yes (if exactly 1 connection)
rework	Return path for defective items	No

Connections are stored in ops_station_connections and define the directed graph that the Station Process Flow visualizes.

When a job completes at a station:

1. System checks feeds_into connections from the current station
2. If exactly one next station exists, the job auto-advances to it as pending (idle)
3. If zero or multiple next stations exist, the job is marked completed for manual routing

See Job Auto-Advancement for detailed logic.

Database Columns

Current columns in ops_stations:

Column	Type	Description
id	UUID (PK)	Auto-generated
code	VARCHAR(50)	Short identifier
name	VARCHAR(255)	Display name
site_id	UUID (FK)	References Site
system_id	UUID (FK, nullable)	Optional grouping
is_archived	BOOLEAN	Soft-delete flag

| machine_only | BOOLEAN | If true, only machines can act on jobs (no people) | | allow_concurrent_jobs | BOOLEAN | If true, multiple jobs can be in_progress simultaneously |

See Also

• Station
• Station Process Flow
• Efficiency Calculation
• Station Product Standards