M3CloudSlam

Understand · Flow Viewer Available

See how an M3 process really works

Every M3 process as a flow: its steps and statuses, the decisions in between, and the screens, API calls and jobs that move it on. Replay one of your own orders on top, step by step.

Become a founding customerAll features
Flow Viewer · landscape
SALES & DELIVERYSUPPLYSTOCKFINANCEDelivery / shipment14 statusesCustomer order8 statusesOpen ›Picking9 statusesCustomer invoice10 statusesPurchase order14 statusesManufacturing order8 statusesDistribution order14 statusesRequisition order14 statusesStock on handbalances, no statusesStock move order13 statusesCustomer payments6 statusesGeneral ledger5 statusesreceiptallocates
Click a process to open it.Available

Why it matters

Today

  1. 1Ask the colleague who knows the process
  2. 2Dig through old blueprints and process documents
  3. 3Try it in a test environment to see what happens
  4. 4Piece it together from program names and status codes

Days of searching, and an answer nobody is quite sure of.

With Flow Viewer

  1. 1Open the process in the Flow Viewer
  2. 2See every status, decision and what moves it on
  3. 3Replay one of your own orders on top

The whole process, in your configuration, in minutes.

How it works

From the whole landscape to one real order

  1. 1 / 5

    Start from the landscape

    Every M3 process, grouped by domain, each with its row of statuses. The lines show how processes connect, for example through stock.

    Flow Viewer · landscape
    SALES & DELIVERYSUPPLYSTOCKFINANCEDelivery / shipment14 statusesCustomer order8 statusesOpen ›Picking9 statusesCustomer invoice10 statusesPurchase order14 statusesManufacturing order8 statusesDistribution order14 statusesRequisition order14 statusesStock on handbalances, no statusesStock move order13 statusesCustomer payments6 statusesGeneral ledger5 statusesreceiptallocates
    Click a process to open it.Available
  2. 2 / 5

    Open a process

    Click a process to see its statuses in order, the way M3 moves an order through them: from preliminary to closed.

    › Customer order › Process flow
    STATUSPreliminarySTATUSCreatedSTATUSAllocatedSTATUSOn picklistSTATUSDeliveredSTATUSInvoicedSTATUSClosed
    Statuses and doors as drawn from the knowledge graph.Available
  3. 3 / 5

    See what moves it on

    Above each status: the screen, API call or job that takes the order there. Below: the decisions where it can go another way, such as a failed credit check.

    › Customer order › Process flow
    APIOIS100MI AddOrderLineJOBAllocationSCREENRelease for pickingAPIMWS420MI ConfirmJOBInvoicingSTATUSPreliminarySTATUSCreatedSTATUSAllocatedSTATUSOn picklistSTATUSDeliveredSTATUSInvoicedSTATUSClosedcredit check failsCredit-blocked
    Statuses and doors as drawn from the knowledge graph.Available
  4. 4 / 5

    Replay one of your own orders

    Lay a real order over the flow and follow the way it actually went, step by step, up to where it is now.

    › Customer order › Process flow
    APIOIS100MI AddOrderLineJOBAllocationSCREENRelease for pickingAPIMWS420MI ConfirmJOBInvoicingSTATUSPreliminarySTATUSCreatedSTATUSAllocatedSTATUSOn picklistSTATUSDeliveredSTATUSInvoicedSTATUSClosedcredit check failsCredit-blockedReplay · order 1000234 5 steps in 2 days, now Invoiced
    Example order. Statuses and doors as drawn from the knowledge graph.Available
  5. 5 / 5

    Zoom into one step

    Open a single door, such as the receipt of a manufacturing order by API: every decision with the field it reads, every action with the records it writes, the refusals, and for each step how sure M3CloudSlam is: proven, observed, predicted or can't tell.

    › Manufacturing order › Receipt (API) › Process flow
    yesnoyesyesnononoSTARTReceipt reportedPMS050MI RptReceipt◆ DECISIONPROVENChecks pass?◆ DECISIONPROVENItem inventory-accounted?MITMAS.STCD◆ DECISIONOBSERVEDMO made for acustomer order?MWOHED.RORCACTIONPROVENPost stock andallocate CO linewrites lot, planningREFUSED WHEN11 refusalseach with its M3 messageACTIONPROVENPost stock(make-to-stock)STATUSPROVENCustomer orderline allocated◆ DECISIONPREDICTEDItem inspected?MITMAS.QACD◆ DECISIONPREDICTEDAutomaticmaterial issue?issue methodENDCAN'T TELLReceipt doneFLOW VARIANTReceipt for an order-initiated MO+ 10 more variantsPROVENOBSERVEDPREDICTEDCAN'T TELL
    One door in detail, with how sure each step is. Example.Available
On your own M3. Answers come from one knowledge graph of how M3 behaves, applied to your configuration and data. When something can’t be known, M3CloudSlam says so.

What it brings you

Understand your processes the way M3 runs them

  1. 1“You don’t need a consultant for that anymore”Key users see how a process runs in their own configuration, without booking someone to explain it.
  2. 2Minutes, not daysUnderstand a process in your own configuration, without searching documents or asking around.
  3. 3Your reality, not a blueprintReplay real orders and see the paths your company actually takes.
  4. 4A head start on every changeKnow how a process really runs before a migration, an upgrade or a redesign.

Next in your journey

PredictorPreviewSee what M3 will do with an order before you press enter.“What happens if I press this?” →Field-ImpactAvailableFind out what a setting along the way actually does.“What does this setting actually do?” →Process VisualizerAvailableZoom out to how all processes connect.“What depends on what?” →

See Flow Viewer on your own M3

We are onboarding a small group of founding customers. You get the newest features first, a direct line to the team, and founding pricing.

Become a founding customer
  • Preview features firstPredictor, Debugger, Release Toggle Impact and Value Provenance
  • Shape the roadmapYour M3 questions decide what we build next
  • Founding pricing, locked inYour rate stays as the product grows