Skip to content
Operixon

Operixon Core

Enterprise Decision Infrastructure

From operational data to evidence-based decisions.

Operixon Core is decision infrastructure that models operational context, simulates the actions available and evaluates the economic impact of each option. Where reporting ends, it shows what should be done today, with the reasoning.

At a glance

  • Decisions in money
  • Never writes to your ERP
  • Every number states its status
  • Works with common ERPs
  • First results within weeks
  • On-premises option
Positioning

What Core is not matters as much as what it is.

Core is not

  • A dashboard or reporting tool
  • A replacement for ERP or CRM
  • A general-purpose forecasting product
  • A RAG or chat assistant platform
  • An off-the-shelf automation template

Core is

  • Decision infrastructure that models operational context
  • An engine that simulates and compares actions
  • A provenance chain carrying the reasoning behind each recommendation
  • A memory of decisions taken and outcomes observed
  • A human-in-the-loop layer where people make the call
Components

The six capabilities behind Core

Each component solves a distinct question. Together they answer the one a report cannot: what should I do now?

Context

Operational Context Model

Represents the relationships between orders, products, resources, suppliers and constraints in a single model. Not a table, but a connected operational structure.

Time

Temporal Context Graph

Stores how operational state changes over time. An order's current status is evaluated together with its own history.

Decision

Decision Engine

Produces the set of actions genuinely available in the current context: what can be done today, not what is theoretically possible.

Simulation

Simulation & Optimization Engine

Runs each action forward and compares options under capacity, time and cost constraints.

Evidence

Decision Provenance

Keeps the data, constraints and assumptions behind a recommendation traceable. A recommendation whose reasoning cannot be shown is not produced.

Memory

Decision Memory

Stores the decision taken, the action applied and the outcome observed. Later evaluations use that history as input.

ProductRuns on Operixon Core

Fulfillment Decision Twin

The Core product built for the order-to-delivery chain. It combines order, inventory, production and supply data and shows, in one decision flow, which order will be late, why, and what should be done today.

Decision jobs

At-risk order recovery

Which order will be late, and what should we do today?

Detects orders at risk of delay together with the root cause. Simulates actions such as production priority, partial shipment or alternative supply and compares them by cost. A recommendation that rescues one order never puts another at risk; trade-offs are shown openly.

Date pull-in request

The customer wants the order earlier. What happens if we accept?

Calculates the impact of a pull-in request on capacity, inventory and other orders, and presents whether it should be accepted, with the affected orders and the reasoning.

Four questions answered in every decision job

  1. Detect

    Which orders are at risk of delay?

    Order rhythm, capacity load and supply status are evaluated together to produce a risk signal.

  2. Cause

    Why did this risk arise?

    The source of the risk is traced through the context model: a capacity bottleneck, a supply delay or a planning conflict?

  3. Options

    Which actions are feasible today?

    The set of actions that can actually be carried out under current constraints is identified.

  4. Impact

    What is the expected impact of each action?

    Actions are compared by change in delay, capacity impact and cost.

Fulfillment Decision Twin runs on the Operixon Core infrastructure. The product grows as new decision jobs are added to the same infrastructure.

Why Core

Designed for mid-sized manufacturers and distributors.

Core brings decision support into the language of operations, without the long implementations and budgets of enterprise planning suites.

Decisions in money
Not "risk score 0.83" but "rescuing this order costs TRY 12,000; losing it costs TRY 85,000". Every option comes with its economic impact.
Never writes to your ERP
Core only reads from your ERP. Your team approves and applies the action, which keeps the security surface narrow.
Every number states its status
Whether a value is measured, estimated or assumed is always visible. Missing data is flagged, not hidden.
Works with common ERPs
Designed to work with data from ERPs widely used in Türkiye, such as Logo, Netsis, Canias, IFS and Nebim.
First results within weeks
No full integration needed to begin: it starts from your ERP export, and the first risk and decision report on your own data arrives within weeks. Integration deepens step by step.
On-premises option
For companies that do not want to move ERP data to the cloud, Core can run inside their own infrastructure.
Explainability

Every recommendation is traceable back to its source.

A recommendation that is never acted on has no value. For it to be acted on, its reasoning has to be visible.

Example decision flow: at-risk order evaluation

Risk signal

SO-4471

  • Promised delivery: 14 March
  • 3 lines · 2 production lines
  • Order value: TRY 1.24M

Delay probability 72% · Expected slip 6 working days

Evaluated actions

  • Change production priority

    Priority

    SO-4488 on line 2 moves back one day; capacity goes to this order.

    Delay
    Delay −4 days
    Cost
    Cost +TRY 18,400
    Confidence
    Confidence 81%
  • Ship partially

    The 2 lines that are ready ship ahead on a separate delivery note.

    Delay
    Delay −2 days
    Cost
    Cost +TRY 6,900
    Confidence
    Confidence 74%
  • Switch to an alternative supplier

    The critical component is sourced from the secondary supplier.

    Delay
    Delay −5 days
    Cost
    Cost +TRY 31,200
    Confidence
    Confidence 63%
Based on
  • ERP order record
  • Capacity plan
  • Supply status
  • Historical delivery performance

Representative visualisation. Core does not make the decision; it ranks the feasible options with their reasoning and records the decision taken and the outcome.

  1. Source data

    The order, capacity and supply records feeding the recommendation.

  2. Context state

    The operational state and temporal history at the moment of evaluation.

  3. Constraints & assumptions

    The capacity limits, durations and explicit assumptions taken into account.

  4. Simulation result

    The output produced by running the action forward.

  5. Recommendation & reasoning

    The ranked actions and the chain of reasoning behind each one.

Product direction

One infrastructure, expanding decision surfaces

Core expands into new decision areas on the same infrastructure. The order below shows the direction in which the product family grows.

  1. 01Fulfillment Decision TwinCurrent product
  2. 02Order-to-Fulfillment Decision TwinNext stage
  3. 03Manufacturing Decision TwinLong-term direction
  4. 04Supply Chain Decision TwinLong-term direction
  5. 05Enterprise Decision PlatformLong-term direction

Each new stage builds on the decision models, data mappings and decision memory of the one before.

Frequently asked questions

About Operixon Core

Is Operixon Core an ERP or a BI tool?

No. An ERP keeps records and BI reports what happened. Core calculates, simulates and explains which action should be taken today with the data you already have. It does not replace your ERP or BI tools; it works on top of them.

What data does Core work with?

Order, inventory, production, capacity and supply data. Excel or CSV exports from your ERP are enough to start; for ongoing use a data connection is set up.

Does Core apply decisions automatically?

No. Core recommends and shows the reasoning and impact; your team decides. The decision taken and the actual outcome are recorded, so later evaluations learn from that history.

What is Fulfillment Decision Twin?

It is the Operixon Core product built for the order-to-delivery chain. It covers two decision jobs: at-risk order recovery and date pull-in request evaluation.

Where is our data processed?

Core only reads your ERP data. With the on-premises option, data can be processed without leaving your company's infrastructure.

Contact

Which of your decisions is waiting for evidence? Let's start there.

For Operixon Core, Operixon Compliance or an automation need, let's review your current data, processes and systems together.