Skip to main content

Operational work centers

A work center is a production resource. Its definition in Operations Studio controls reusable configuration; its operational screens show assigned work and current information. An available machine, a scheduled split and an active App order are different facts.

Find the resource​

Select the correct site/environment and open Operations Studio → Workcenters to find the resource by name/code or its group in the explorer. Open its definition to inspect configuration. For station work, use the assigned published App or configured shop-floor machine view.

Older work-center bookmarks redirect to the current Studio definition; an old order-detail bookmark redirects to Production Orders. The former standalone work-center list and its table-view controls are no longer the entry point.

Check the resource's code, group and current status before acting. Reading the station does not automatically grant editing, progress reporting or malfunction permissions. Change reusable settings in Operations Studio; plan assignments in Planning.

Inspect its work​

The machine-oriented station view can provide orders, history, malfunctions and maintenance context. Open an order to inspect its planned/produced quantity, priority, dates, component relationships, notes and available instructions. A narrow screen can show cards instead of a table.

  1. Confirm the station and active workspace.
  2. Find the intended queued or active work and open its details.
  3. Check order number and, in a split-based workflow, the operation/split.
  4. Follow the configured execution action or open the station's assigned App.
  5. Report output and complete work using lifecycle and execution.

Instructions can include text, images, PDFs, videos, models or checklists, depending on the configured content and access. A missing attachment is not proof that no instruction exists; check the source assignment and file permissions.

Status, quantities and history​

A malfunction alert identifies an active station problem and its start time. Resolve it through the malfunction workflow. Operational indicates the application's current status; independently verify the physical machine before operating it.

Produced quantity is recorded output. Current machine signals and KPI widgets depend on configured data sources and calculation periods. Do not infer good output, inventory or complete downtime coverage from a single counter. Use Edge Runtime when investigating machine connectivity.

History lists retained activity available for this resource. Order reports belong to their order or subject. Nexus helps inspect relationships and sources without changing production.

Recovery​

For an empty order list, clear filters and verify that work is assigned to this resource in the current site/environment. For stale status, check connection, refresh, and compare with current source data before reporting again. If a file fails to open, check its assignment, upload completion and access. After a lost progress response, inspect the saved quantity first. Provide work-center code, order/split, workspace and approximate time to support.

See shop floor, Factory Calendar and reports.