Metalya · Adaptive Manufacturing Platform

A stable manufacturing core.An adaptive application layer.

Run production and planning on a governed MES + APS foundation. Adapt dashboards, forms, workflows and factory mini-apps around the way your people actually work — with AI, without building a second system.

MES
Execution, quality, materials, maintenance
APS
Finite-capacity planning on the same data
Studio AI
The adaptive layer, composed with AI
Painting station · PNT-02Adaptive edge
Current work stage WorkStageWO-4812 · 20Painting · Housing AX-90
Drawing DocumentDRW-19281 · rev B
Remaining WorkStage248 pcs402 of 650 declared
Declare quantityDeclare scrapStart downtimeActions ProductionHistory · Reason
Output vs plan ProductionHistory1,840 / 2,100
Scrap rate1.6%
Machines Machine
  • PNT-01 Running
  • PNT-02 Setup
  • PNT-03 Down 14 min
  • PNT-04 Running
Open downtime ReasonPNT-03 Colour changeOVN-01 Waiting material
Lot BatchL-24-0917Housing AX-90 · 650 pcs
Characteristics QualityOrderCoating thickness 82 µm70–95Gloss 88 GU≥ 80Adhesion grid test pending
Thickness trend
Record defectPlace on holdActions ProductionDefect
Finishing · 06:00–22:00 WorkStage · Machine
On time SalesOrder94%
At risk3 orders
Compare with v13Release planPlanner decision
Metalya Core · governed model, actions, history stays the same
  • WorkOrder
  • WorkStage
  • Product
  • Document
  • Machine
  • Operator
  • Reason
  • ProductionHistory
  • Batch
  • QualityOrder
  • ProductionDefect
  • SalesOrder
  • Calendar

Same core, different edge. Each role gets its own experience; every view reads and writes the same governed objects.

The platform, at a glance

One core. Every module.
Adapted by AI.

Metalya Core contains every module of the manufacturing system. Metalya Studio surrounds it: the layer that adapts the platform to your context — with AI.

Metalya Studio

Adapts every module to your context — screens, workflows and mini-apps — with AI.

Metalya Core

All the modules of the manufacturing system, on one governed model.

Click a module to open its page.

AI inside Metalya Studio

Describe it. Metalya AI composes it.
AI doesn’t replace the manufacturing system. It makes it fast to adapt.

Compose with words

Describe a screen, form or dashboard; Metalya AI proposes it from the widget palette, bound to the right data.

Understands your model

AI suggests which governed entities a request refers to — orders, stages, lots, machines, reasons.

Ask your data

Questions in natural language become charts you can pin to dashboards.

Drafts widgets and queries

Custom widgets and queries drafted by AI, reviewed by your experts.

Metalya Studio AI

Describe what you need.
Make it part of Metalya.

Pick a request and press “Compose with AI”. Watch Metalya AI read it, map every word to governed objects and existing actions, and compose a real screen — published only when you approve it.

Metalya Studio AI

Simulated demo
Your request

Create a tablet application for the painting department. Show the current order, drawing and remaining quantity. Let the operator declare scrap and downtime.

Metalya AI is ready. Pick a request and press “Compose with AI”.

  1. 01Describe
  2. 02AI interprets
  3. 03Map to the core
  4. 04AI composes
  5. 05You approve

Mapped to governed objects

Metalya AI will map each phrase to an entity, a derived value or an existing action.

  • painting department Department · WorkCenterContext Scopes the app to the painting work centre and its machines
  • current order WorkOrder → WorkStageEntity The work stage active on the operator’s machine
  • drawing Document (Product)Entity Released revision linked to the product
  • remaining quantity WorkStage.Quantity − OutputQuantityDerived Derived from declarations, never typed in
  • operator Operator · SysUserContext Shop-floor user; actions are recorded against them
  • scrap declare_quantity → ProductionHistoryAction Scrap quantity with a ProductionDefect reason
  • downtime start_downtime → ProductionHistoryAction Downtime record with a Reason
Flow painting_station
Painting stationRunningPNT-02 · M. Rossi
Current orderWO-4812 · stage 20Housing AX-90 · Painting RAL 7016
DrawingDRW-19281 · rev B
Remaining248 pcs
Progress402 of 650 · scrap 6

Events written to Metalya Core

  • Publish the experience, then use it.

AI proposal 1 flow · 1 tab · 5 widget types · 2 existing actions

Menu Shop floor › Painting · Actions declare_quantity start_downtime

Discover Metalya Studio

Metalya APS

Production plans meet reality.

Plans break the moment a machine stops, an order jumps the queue or material arrives late. Because planning runs on the same data as execution, the impact is visible at once — and the planner decides what to release.

Choose a disruption
Simulated demo · illustrative data

Released plan for today: 8 orders across 5 machines. Pick a disruption to see how the plan reacts.

Late orders0±0
Machine utilization44%±0
Estimated completion20:35±0
Capacity impact0 hno change
Order-by-order view
Orders, due times and estimated completion for the current phase
OrderProductDueCompletionStatus
WO-4803Frame FR-3011:3009:15On time
WO-4807Cover CV-1815:0010:10On time
WO-4801Bracket BR-1216:0013:45On time
WO-4802Cabinet door CD-419:0015:25On time
WO-4804Base plate BP-720:3018:40On time
WO-4805Housing AX-9022:0016:50On time
WO-4806Support arm SA-222:3019:20On time
WO-4808Panel PN-5500:0020:35On time

The demonstration uses a simplified scheduler. Metalya APS schedules with your calendars, setups, constraints, crews and material availability. Explore Metalya APS

Build / Buy / Adapt?

Three ways to run a MES.
Three ways to handle change.

A factory never stands still. The real difference isn’t just who builds the software — it’s where you start from, and what happens when production needs to change.

  1. 01 / BuildCustom software

    Build

    You develop your own MES — from scratch.

    You build it.

    You start from zero: data model, routings, traceability, integrations, security and upgrades. Every decision and every line of code is yours to write — and to maintain for as long as the factory runs on it.

    1. Design
    2. Code
    3. Maintain
    MES foundation
    None — built from zero
    Change approach
    New development work
    Dependency
    Internal IT & resources
  2. 02 / BuyProject-led MES

    Traditional MES

    You purchase and implement a MES.

    You request it.

    The core exists, but significant adaptations are typically scoped, planned and delivered as supplier projects.

    1. Request
    2. Scope
    3. Deliver
    MES foundation
    Provided by the vendor
    Change approach
    Change request / project
    Dependency
    Supplier delivery cycles
  3. 03 / AdaptAdaptive MES platform

    Metalya

    A ready-to-use MES core, made to evolve.

    You adapt it.

    The platform provides the foundation — model, traceability, planning, integrations, security. Your team evolves supported screens and processes with no-code tools and AI assistance.

    1. Configure
    2. Validate
    3. Evolve
    MES foundation
    Provided by Metalya
    Change approach
    No-code + AI assistance*
    Dependency
    More autonomy for your team

The moment that matters

Tomorrow, your production workflow changes. What happens?

Same need. Three very different paths.

  1. Build

    Your team writes new software.

    Development → Testing → Deployment

  2. Traditional MES

    You start a change project.

    Specification → Quotation → Delivery

  3. Metalya

    You configure and keep moving.

    No-code tools → AI assistance → Iteration*

* AI assistance works on supported screens and flows; every change is validated and approved by your team before it is published.

Read the full comparison

Industries

Where the model fits best.

Discrete and process manufacturers with real routings, real constraints and real traceability requirements.

Explore more industries

Buy the foundation. Adapt the experience.

See Metalya on your own production scenario: your routings, your constraints, the screens your people need.