Skip to main content

Shop floor

Shop floor provides a station-oriented interface for manufacturing. The content depends on the shop-floor account, registered device, selected work center and assigned published App. Device setup and operational authority are separate: registering a device does not grant every platform action.

Prepare the station​

An administrator sets up the account, permitted work centers, device and App assignment. Follow shop-floor accounts and devices for registration and sign-in. Keep registration credentials under the administrator's control.

At the terminal, confirm the expected account/workspace and work center before starting work. Use the published App assigned to the station or its machine-oriented view. A missing App should be corrected by the workspace administrator; opening another URL does not substitute for assignment.

Execute an order​

  1. Find the intended order in the available order table or cards. Search and filters can hide work.
  2. Open its details and verify material, quantity, priority, instructions and operation/split context.
  3. Select/start the intended work using the configured control. Selecting an App's active order supplies context to its other components; it does not mean every component has already performed its action.
  4. Record actual additional output using the production-progress control. Check the unit and accumulated result.
  5. Complete the App's required inputs, configured placement evidence and other explicit workflow steps.
  6. Complete work using its confirmation dialog and inspect the saved result.

Pause/resume, handover and other controls are App-specific. Use only the actions your published workflow supplies. The production-order lifecycle itself has no paused state. See lifecycle and execution.

Instructions, evidence and exceptions​

Use available text, PDFs, images, videos, models and checklists to carry out the operation. Save the App's inputs through its explicit action; a visible draft is not an accepted business record. Printed labels and reports use the configured template and subject context.

Add relevant notes and permitted attachments when available. Notes marked for an office audience may be absent from shop-floor presentation. Commercial data and Nexus are not required for station execution.

Report malfunctions, scrap or rework using the configured controls. Record planned maintenance in the Factory Calendar when that is the agreed planning workflow. Use Material Flow for output placement and collection; it does not create Warehouse stock bookings.

Embedded Konnie can help within the tools and permissions enabled for that App. Read any proposal and required approval before accepting an action.

Handover and reconnect​

Before handing over, verify the saved output, active order, unresolved malfunction and submitted reports. Leave the next operator the correct station context. On shared terminals, follow your account/session policy instead of sharing an office user's personal session.

When the connection fails, treat unsaved changes and measurements as unconfirmed. Restore connectivity, reopen the same App/order and compare saved quantities and reports before repeating actions. An App retry control should continue its original action. Do not assume offline work will synchronize automatically.

For expired access or a replaced device, ask the administrator to repair account/device assignment using the documented registration workflow. If a terminal shows another station's work, stop input and verify scope and binding. Include device/work-center identity and displayed error in a support request.

See running Apps, App inputs and labels.