Maestro OS · Business operating platform

MES and production coordination in Maestro OS by MASTERPLAST

Maestro OS includes software workflows for production routes, digital travellers, cell queues, work instructions and operation events. These connect manufacturing preparation with identifiable orders and batches. Availability depends on the installation and user permissions. A production plan, an operator event and a command executed by a machine represent different stages.

Production routes and digital travellers

A production route describes the sequence of operations for a job. The inspected services expose route versions, route-operation management and activation, together with digital travellers linked to an order or production batch. A traveller provides the operational reference for the work that moves through production. In a demonstration, start from an identifiable sample order, inspect the selected route and confirm the instructions attached to its operations. The team should agree which revision applies and who may change it. This avoids treating an early planning record as an approved instruction for a different job.

Queues, responsibilities and recorded progress

Production-cell queues organise work for the relevant cell or work centre. Software actions include starting, pausing, resuming, blocking and recording operation progress; some completion and quality actions are explicitly described as previews. Visibility and permissions distinguish viewing work, operating a cell, managing its queue and performing quality checks. A supervisor can therefore evaluate the workflow using the intended roles rather than a single unrestricted account. An event recorded in the application establishes software history. Its relationship to work physically performed must be checked with the operator and the installation’s accepted process.

Instructions, measurements and quality context

The MES interface includes versioned digital work instructions and an approval action for instruction versions. Operation services contain scan, measurement, photo and quality-check workflows, with feature checks for relevant actions. These can support a production record when enabled and used within the assigned company, facility and cell. Review the actual instruction, expected measurement and responsible role before accepting a demonstration result. A photo or completed software step is not, by itself, a certification of product quality. Customer-specific documents and production evidence remain in the authorised workspace rather than becoming public marketing examples.

Cutting handover and machine-execution boundaries

The cutting-to-MES link associates a cutting job with a traveller operation and can place its preview in a cell queue. The inspected handover explicitly identifies preview-only behaviour and indicates that stock issue and operation completion have not been executed by that link. This distinction matters when discussing optimisation, scheduling and machine integration. A generated plan or queue entry does not prove that a saw, controller or other production machine received and executed it. Confirm a specific approved machine interface, release procedure and physical acceptance test before describing automated execution or inventory consumption as available.

Connectivity and an acceptance scenario

Offline event synchronisation includes device registration, duplicate-event checks and synced or rejected results. These are implementation mechanisms; they do not establish that every device or network scenario has passed acceptance. Demonstrate one sample traveller through the intended cell, record an authorised event, inspect the instruction version and verify the resulting history. Where offline work is required, test the selected device, reconnection and duplicate handling. Agree the difference between operator recording, preview completion and released production. This produces a useful installation-specific MES description without exposing private orders, workshop totals, customer files or machine credentials.

Discuss your workflow