Book a demo
Open navigation

What AxiFloor
does today

Seven areas, each on a real screen from a demo system running SAP S/4HANA® Cloud Public Edition. What is not built yet is on the roadmap.

Plan

Planning starts from your ERP’s own orders: the load on each work centre, each week sequenced inside the shifts, and the orders that are ready to release.

AxiFloor’s Production Order Calendar for work centre BK-PAINT, plant 3510, 2 to 8 November 2026, after Optimize: 22 powder-coat operations laid one after another inside the shifts, a draft of 22 unsaved operations with Save Plan.
  • Production Order CalendarEach work centre’s operations by day, week or month; Optimize lays them inside the shifts as a draft until Save Plan.
  • Capacity BoardLoad against capacity per work centre and day, from SAP S/4HANA’s own capacity requirements.
  • Plan to ProduceWhich planned orders can be converted and released, checked before anything is posted.
  • Missing PartsStock and confirmed incoming supply against what each order still needs.

Execute

Operators work from the station, on a tablet at the line; supervisors see each order whole. For discrete and process orders.

AxiFloor’s Operator Station at work centre BK-WELD: order 1002110, Road bike Aero 700C, operation 0010 Weld frame with 5 PC to confirm, Start, the materials to issue inside the operation, and Record Confirmation, Scan, Report Breakdown and Report Defect.
  • Operator StationThe work centre’s queue; the operator’s Start and Stop time the job, and that time is booked with the quantity.
  • Order CockpitOne order on one page: materials, execution, quality and goods receipt, each with what its verdict is based on.
  • Materials per operationBackflushed ones post with the confirmation; manual ones are consumed from the station.
  • Breakdowns and defectsReported by the operator at the station, on the order they belong to.

Verify

In-process quality on the same order as the work, so an out-of-spec result is seen at the line, not at the end.

AxiFloor’s Inspection Workspace for lot 30000000841 of order 1002111, BIKE-KIDS: frame temperature 21.5 °C (18 to 25 °C) and brake lever force 32.5 N (20 to 40 N) in spec in green; handlebar clamp torque 13.1 Nm (8 to 12 Nm) out of spec in red.
  • Quality WorklistPending, overdue and failed inspections: the inspector’s day in one list.
  • Results per characteristicRecorded against their limits; out of spec shows in red first.
  • DefectsRecorded on the lot or the order, with their code and quantity.
  • Usage decisionTaken on the same lot once every characteristic is closed.

Act

Every issue at the plant, ranked, each with its cause, its impact and one next step. The Manufacturing Overview refreshes every five minutes while it is open.

AxiFloor’s Manufacturing Overview for plant 3510: Needs attention now, 3 items (order 1002105 short of GROUPSET-MTB, order 1002110 late by 1 day, BK-WELD over capacity today), each with its cause, impact and one action; below, Next steps for orders 1002141, 1002142 and 1002143.
  • Needs attention nowLate orders, shortages, lots without a decision and overloaded work centres, ranked by urgency.
  • Next stepsEach order’s routine next action, with the app where it is done.
  • Coming upKnown conditions that will hit work planned in the next 24, 48 and 72 hours.
  • Exceptions InboxEvery order’s exceptions, filed by reason, with what to do about each.

Order closing

Each delivered order checked against its plan before it is closed, operation by operation, so a deviation is explained while it is still fresh.

AxiFloor’s Order Closing for production order 1002142, BIKE-ROAD, plant 3510, 2 PC confirmed and delivered: operations 0010 to 0040 planned against actual, operation 0030 Assemble bike flagged with its time over plan, and Set TECO.
  • Planned against actualOperations, consumption, goods receipt and quality, each row with its deviation and status.
  • Deviations to explainSet TECO asks for a note on each deviation before the order is closed.
  • Closing deviationsThe notes written at closing, newest first, with who closed the order and when.
  • Did not postGoods movements the ERP did not post are listed with what to do in SAP S/4HANA.

Master data

The manufacturing master data behind each order, read from SAP S/4HANA and laid out for the plant: one material, its structure, its routings and recipes.

AxiFloor’s Production Structure for BIKE-ROAD, Road bike Aero 700C, plant 3510: two levels and seven materials; BOM 00000285 with production version 0001 and routing 50000008, operations 10 Weld frame at BK-WELD, 20 Powder coat frame at BK-PAINT, 30 Assemble bike at BK-ASSY and 40 Final test and pack at BK-TEST; then its components TUBESET-ROAD and PAINT-POWDER.
  • MaterialAll the manufacturing master data for one material at one plant, on one page.
  • Production StructureThe bill of materials level by level, with each made material’s routing or recipe and its work centres.
  • Master Data ReadinessChecks per material whether it can be planned, with what to fix.
  • Where-used and comparisonThe bills of materials that use a component, or two of them side by side.

Insights

What actually happened, after the fact: one batch across orders, one work centre, or the whole plant week by week.

AxiFloor’s Batch History for batch 0000001008 of BIKE-ROAD at plant 3510: produced by order 1002143, 4 of 4 PC received and delivered on 28 October 2026, one inspection lot decided, no defects; what happened to the batch: inspection lot 30000000851 created, results for characteristics 10, 20 and 30 accepted, usage decision A, and the goods receipt of 4 PC.
  • Batch HistoryEverything that touched one batch, across orders: produced by, consumed by, inspection lots and defects.
  • Batch TraceWhere a batch came from and where it went, several levels deep.
  • Work Centre HistoryWhat actually ran on a work centre, beside what was scheduled there.
  • Production TrendsYield, scrap, deliveries and quality week by week, across both order families.

See it on your process

AxiFloor works through the standard released SAP S/4HANA APIs, with the ERP as the system of record. Book a demo and see it on a real system.

Book a demo