Product variants

The right procedure for the right variant, every time.

In high-mix production, the risk is not choosing the next order. It is making sure the right action happens, in the right place, for the variant currently on the workbench. Arkite connects MES variant data directly to the operator.

Last updated

The problem

Every changeover is an execution risk

Customer-specific configurations, optional parts and frequent engineering changes multiply the number of product variants at each workstation. Similar variants often share most of their steps and differ in one component, one fastening sequence or one quality check.

When variant information is spread across paper travelers, PDFs, static screens and memory, operators spend time checking part numbers and filtering what applies. Errors appear exactly at the moment of changeover, and every new variant adds training effort.

Root causes of variant errors

01

Manual variant selection

The operator selects or confirms the variant by hand, and a similar previous job leads to the wrong assumption.

02

One document per variant

Paper and PDF instructions multiply with each variant, and outdated versions stay in circulation.

03

Late engineering changes

An updated step does not reach every workstation in time, so lines run on different versions.

The Arkite approach

Variant-aware execution, driven by your MES

Arkite manages variants through jobs, job options and job variants. Job options are properties for which the steps differ, such as color, size or optional parts. Shared steps are defined once, and variant-specific steps run only when they apply.

Through MES integration, the workstation receives the correct job and product variant automatically when the operator logs in or the order arrives. The variant can also be selected by scanning a barcode or on the operator screen.

  • No practical limit on the number of variants in a project
  • Variants imported from and exported to CSV files
  • Current variant and expected cycle time shown on the operator screen
  • Changes published centrally and available on every workstation
  • New jobs, job options and steps generated with AI from a written description, reviewed by the engineer
Arkite operator screen showing the step list, the current variant and variant code, and cycle time against expected cycle time

How a variant reaches the operator

  1. 01

    MES creates the job

    Job orders and product variants are pushed to the Arkite server through the REST API.

  2. 02

    Engineers adapt the instructions

    Process engineers make the steps practical for the physical workstation in the no-code editor.

  3. 03

    The workstation loads the variant

    At login or order start, the correct job and variant are retrieved automatically, removing manual selection errors.

  4. 04

    Execution is validated

    With VALIDATE, the 3D sensor confirms that the variant-specific parts and locations were used.

Data that proves the improvement

  • Cycle times per job and per variant
  • Expected versus actual cycle time per variant
  • Errors per variant and per step
  • Job output per variant per hour, day or week
  • Step durations after each changeover
  • Completion status reported back to MES

Frequently asked questions

How does Arkite handle product variants?

Through jobs, job options and job variants. Shared steps are defined once and variant-specific steps run only when they apply. There is no practical limit on the number of variants in a project.

Can the variant be selected automatically from the MES?

Yes. Jobs are created in the MES and pushed to the Arkite server. When the operator logs in, the workstation retrieves the correct job and variant automatically. Barcode scanning and manual selection are also supported.

Can AI speed up job creation for new products and variants?

Yes. Since software version 2026.2, engineers can generate a job with AI. Based on a written description of the assembly, the software generates the job, job options, materials, detections and job steps, and the engineer reviews and finalizes the result. The integration is optional, disabled by default and uses OpenAI or Anthropic with your own key.

Does Arkite replace our MES?

No. ERP decides what to build and MES decides when. Arkite connects them to the operator layer and tells operators how to build each variant.

How are instruction changes rolled out?

Projects are versioned and stored on the central Arkite server. Once released to production, updates are immediately available on every connected workstation.

Bring your most complex product family

We show how Arkite structures your variants and connects them to your MES.