Discuss your project
← All use cases

Use case · Production

A bottleneck.
A new plan.
A clear decision.

We start from your planning rules, machine capacities and typical disruptions. Together with production planning, manufacturing and IT we clarify which data is needed, who may change plans and when planning decides. The result is your workflow for rescheduling around bottlenecks.

CORAProcess assistant

Your team

“Use our planning rules, changeover times and delivery commitments. Create a workflow that proposes a new production plan after a machine failure, material shortage or rush order: read orders, capacities and material stock. Calculate variants that keep delivery dates wherever possible. Explain which orders move and why. The plan is only applied in the system after approval by production planning.”

CORA is drafting the process …

The description becomes the workflow

Describe once.
Run every time.

Your description becomes a workflow for every disruption: from the event on the shop floor to an approved new plan.

CORA builds the process. Your team reviews the test cases and approves it. Only then does it run for every matching event – with your permissions.

Spot bottleneck · Calculate variants · Approve plan

  1. Disruption
  2. Read situation
  3. Calculate variants
  4. Reasoned proposal
  5. Approval
Discuss your project

One run in detail

How CORA reschedules after a failure.

A disruption on the shop floor: from the line failure to the new sequence in the ERP.

All names, numbers and values in this example are fictitious.

  1. TriggerLine 3 reports a failure of about six hours.
  2. IntegrationRead situation

    Read: nine affected orders, free capacity on lines 1, 2 and 4, material stock and setup states.

  3. CodeCalculate variants
    VariantDates keptExtra effort
    A: move to line 28 of 945 min changeover
    B: extend late shift9 of 92 h overtime
    C: swap sequence7 of 920 min changeover
  4. RuleCheck limits

    Order AU-5512 has a firm delivery commitment. Variant C breaks it and is discarded.

  5. AIExplain proposal
    Variant A keeps all dates except AU-5530, which moves by one day; the customer has buffer until Friday. Variant B keeps all dates but needs an extended late shift. Recommendation: A if no overtime is possible.
  6. HumanDecide

    After talking to the shift lead, production planning chooses variant B.

  7. IntegrationApply

    New sequence applied in the ERP; shift lead and sales receive a notice.

From existing documents to a tested workflow

From existing documents
to a tested workflow

1Your documents and example cases

DocumentPlanning rules
  • Priorities
  • Changeover sequences
ExampleLine 3 failure (fictitious)
  • Duration
  • Affected orders
DocumentShift model
  • Capacities

2Business systems and data

SystemERP
  • Orders
  • Delivery dates
  • Material
SystemManufacturing execution
  • Machine status
  • Confirmations
RuleFirm delivery commitment
  • Must not be moved

3People, roles and rights

Role cardProduction planning
Approve plan
Role cardShift lead
Own lines
Machine controlBlocked
No access
  1. Build process
  2. Test
  3. Approve

Running process

  1. Disruption reported
  2. Read situation
Buffer suffices
  1. Adjust sequence
  2. Planning approval
Date at risk
  1. Compare variants
  2. Planning approval
No solution
  1. Align with sales

Process steps in detail

What AI does – and what rules, code and integrations handle.

CORA uses AI where language, context or unstructured information needs to be understood. Calculations run as tested code, limits and responsibilities as rules, system access through defined integrations. Approvals stay with people.

  • AILanguage model: understands, summarises, drafts1×
  • RuleFixed conditions, thresholds, responsibilities1×
  • CodeCalculations and models, versioned and testable1×
  • IntegrationRead and write access via MCP servers or interfaces3×
  • HumanReview, approval and decision1×
  1. 01

    Detect disruption

    A failure, shortage or rush order triggers the workflow.

    Integration

    Implementation: Event from manufacturing execution or report by the shift lead

  2. 02

    Read situation

    CORA reads affected orders, capacities, setup states and material stock.

    Integration

    Implementation: MCP servers for ERP and warehouse, read-only

  3. 03

    Calculate variants

    Several feasible plans are calculated and rated by schedule adherence and changeover effort.

    Code

    Implementation: Optimisation model with your planning rules

  4. 04

    Check hard limits

    Variants that break firm commitments are discarded.

    Rule

    Implementation: Delivery commitments, shift limits, material availability

  5. 05

    Explain proposal

    The AI describes how the variants differ and which orders move – clearly for planning and sales.

    AI

    Implementation: Language model with the variant comparison

  6. 06

    Approve

    Planning selects a variant, adjusts it if needed and approves it.

    Human

    Implementation: Production planning

  7. 07

    Apply plan and notify

    The approved plan is applied; those affected receive a notice.

    Integration

    Implementation: Write access to the sequence in the ERP, message to shift lead and sales

Connected systems

  • ERPreads orders and delivery dates, writes the approved sequencevia MCP server
  • Manufacturing executionreads machine status and confirmationsvia interface
  • Warehouse managementreads stockvia MCP server
  • Email or chatsends approved noticesvia interface (API)
  • Company sign-inchecks identity and rolevia single sign-on

How we work

We start with your
actual work.

  1. 01

    Understand existing documents

    Planning rules, changeover matrices, shift models and past reschedulings show us how decisions are made today. From them we derive goals, hard limits and priorities. We capture unwritten rules together with planning.

  2. 02

    Connect data and business systems

    With your IT we connect ERP, manufacturing execution and warehouse. Order number, work centre and material number link the data. We define where data is read and where plan proposals are stored.

  3. 03

    Assign identities, rights and roles

    Identity comes from your company sign-in. Production planning may change plans, shift leads see their lines, sales sees delivery dates. The AI acts on behalf of the responsible person and only writes after approval.

  4. 04

    Test together and go live

    From the description, documents and clarified system access, CORA drafts the process. Together with your business unit we select test cases and expected results. Testing runs without write access. Example tests: Machine failure for one shift, material shortage, rush order, conflicting delivery commitments.

Your team decides on rules, AI steps and approvals. We activate the tested workflow, compare effort and results and practise the next changes in the skill workshop. Integrations, knowledge and reusable building blocks remain as the foundation for further processes.

Discuss your project

How the case
runs

With every disruption, CORA reads orders, capacities and stock, calculates feasible plan variants and checks hard limits such as delivery commitments. Planning receives a reasoned proposal and approves the new plan.

What it
produces

Rated plan variants, a reasoned proposal listing affected orders, the approved plan in the ERP and notices to shift leads and sales.

Where your team
decides

Production planning selects and approves the variant. CORA does not control machines. If delivery dates cannot be kept, planning aligns with sales.

More use cases

We show you where AI can take work off your hands right away.

Discuss your project