Platform & Coverage

A layer over the systems already in place. 7 places it runs.

nudu does not replace the ERP, the WMS or the planning tool. It operates above them, joins context across channels, and closes the operational loop they were never built to close.

  • 3 operational layers
  • 7 coverage domains
  • Shadow mode before live

How the platform works

Three distinct layers. No proprietary black boxes.

01

Connect

Read first, write on approval

Connects via API, webhooks or mailboxes to the systems already running: ERP (SAP, Oracle, Dynamics, NetSuite), WMS, sensor feeds and the spreadsheets that hold the operation together. Nothing gets ripped out.

  • ERP & WMS read/write connectors
  • Sensor, telemetry and API feeds
  • Spreadsheets, email & WhatsApp channels
02

Decide

Client rules over engine defaults

Thresholds, severities and permitted actions are pure configuration, not code. The engine runs your own playbooks, routing routine exceptions and escalating only when human judgment is needed.

  • Configurable severity thresholds
  • Permitted action matrices per role
  • Accountability roster per shift & site
03

Record & Audit

Evidence by default

No silent automation. Every signal investigated, contact made and action taken is written to an immutable case record with complete root-cause context, timestamps and user sign-offs.

  • Full audit trail of every case
  • Root cause & confidence score
  • Queryable operational telemetry

Operational coverage by domain

The same engine runs across all seven domains with domain-specific signals, rules and action thresholds. Select an area to inspect how exceptions are handled.

01 / 07 · What to buy, and when

Procurement

Typical exception:

An order is confirmed at a price or date that breaks the production or fulfillment plan.

Signals that open a case

  • Confirmation date later than required date
  • Confirmed price outside agreed price band
  • Order acknowledged short against requested quantity
  • No acknowledgement received inside agreed window

Actions nudu is permitted to take

  • Request cause and recovery date from supplier
  • Update expected delivery date in ERP
  • Flag affected production and supply plans
  • Escalate to buyer with full case context attached
Human in the Loop

The same limit applies in all seven domains.

nudu opens the case, identifies the cause, handles the repetitive investigation and logs the trail. Every decision that costs capital or alters vendor contracts remains strictly with the human operations team.

Shadow first, live second.

Nothing goes live on the basis of a demo. Deployment advances when operational data shows nudu's decisions matching the operations team on identical cases.

  1. Week 1–2

    Mapping

    Signals, thresholds and permitted actions are configured alongside your operations leads. Pure business configuration, not software development.

  2. Week 3–6

    Shadow Mode

    nudu monitors live operational data and determines actions, but executes nothing. Decisions are audited against the human team's actions to calibrate accuracy.

  3. Week 7

    Live, Focused

    Go live on one specific process, one severity band, and one facility. Routine notifications resolve automatically; complex exceptions escalate.

  4. Ongoing

    Expansion

    New domains and facilities roll out as configuration on the existing engine. Subsequent rollouts take days because the platform is already in place.

Data governance and enterprise trust

Clear, contractual guarantees on how connected data is handled.

What nudu stores

Only operational case records: signals, joined context, contact logs, classifications, actions and audit timestamps, retained according to your retention policy.

What nudu does not do

Your data is never used to train generalized or shared AI models. Nothing crosses customer boundaries. Pricing, volume and supplier records remain strictly isolated.

Access & Security

Role-based access control (RBAC) with granular site scoping. Every case read or action is logged. Full data export available at any time.

Deployment options

Managed enterprise cloud by default, or deployed directly inside your own AWS, Google Cloud or Azure tenant for strict regulatory compliance.

Start with the process that costs the most hours.

A deployment does not begin with all seven domains. It starts with one process, one severity tier and one facility.