planeus isn’t just a scheduler. It’s a modular solution that brings planning, execution, and data management together on a synergetic platform.

Unlike traditional systems that separate planning from execution:

That’s where the Workbench comes in.

Workbench is a lightweight, in-system execution module to capture real-time operation data fed directly by your shop floor employees.

It makes workers to enter feedback and time data easily, helping keep your plan and reality perfectly in sync.

Workbench offers two types of interfaces:

Both systems share the same data structure, which means you can use them side by side without conflict.

Here’s what you can do in the Workbench to record what’s happening on the shop floor:

Sometimes things don’t go as planned.

If your shop floor uses barcodes, you can integrate it into Workbench using this feature.

You can:

If you want to enter the barcode number manually, you can

Once you enter or scan the barcode:

Sometimes you need to add more than just numbers. And in Workbench, you can take a photo or upload a file directly when providing feedback or updating progress.

You can see the uploaded photos and document in History.

Custom fields let you add extra input fields in the Workbench (Classic and Terminal). This makes it easy to capture additional production-specific information as part of feedback.

This feature requires a license. Access also depends on user roles. To analyze custom field data in reports, you also need reporting licenses.

In Workbench Classic, you can find custom fields under the Custom fields tab in the header of the open Work Step.

In Workbench Terminal, you first open the details of the Work Step. If custom fields are available, planeus shows an orange dot on the icon.

You define custom fields under: Configuration → Custom fields

There you decide:

In the field definition, you set the field name. This is a free-text label that describes the purpose of the field.

Under Area, you choose where planeus should show the field in the Workbench.

Available areas:

planeus supports these field types:

The default value pre-fills the field in the Workbench.

The order defines where the field appears when you use multiple custom fields.

The required field toggle makes the field mandatory in the Workbench.

Users cannot complete the Work step until they fill in that field.

The show field in history toggle makes the field visible in the Work step history.



You can control field visibility with conditions.

Available options:

If you enable selected resources or resource groups, planeus adds two dropdown lists. There you can choose the relevant resources or resource groups. You can select more than one.

Custom fields follow the standard planeus permissions model.

To fill in custom fields, a user needs the permission:

Workbench Work steps write

After the user saves the values, they cannot change them without additional rights.

To correct values later, a user needs:

Feedback / correct status ‘Completed’

If a user does not have the required permission, existing values stay visible but cannot be edited.

If a user only has read access and no entries exist yet, planeus hides the entire Custom fields section in the Workbench.

planeus shows custom field data in these reports:

To see these fields in reporting, enable Show custom fields.

You can do this through the gear icon in the upper-right corner of the reporting view.

You can adjust how the Workbench behaves under Administration → Settings → Workbench

If this setting is enabled, when you complete a Work Step, it will automatically complete any earlier steps.

This feature helps keep your data accurate.

For Work Steps:

While entering data, you’ll also see the quantity recorded in the previous step.

If Work Steps overlap, the Work Steps and its following Work Steps can be started — regardless of the quantities already reported.

Quantity reporting: Even with overlapping Work Steps, the quantity is still taken only from the direct predecessor. This means you can only report the quantity that has already been reported for the direct predecessor.

Plausibility checks also work for Processes, even though they don’t have quantities.

For Assemblies:

Partial quantity checks only apply within the same Production Order.

You can use the “Show not plausible” switch to hide or show any Work Steps that are not ready to start yet.

You can make certain fields mandatory for users:

You can tailor the Workbench to fit your team’s language and preferences:

This setting makes sure that every step in production follows the actual yield from the Work Step before.

This setting is helpful when: