M3CloudSlam

Master Data · Data Governance Available

Every change to your master data, seen, approved and on record

Choose the M3 tables that matter. M3CloudSlam takes regular snapshots, finds every change field by field, and handles each one according to the level you set: follow it, approve it, or change it only through M3CloudSlam.

Become a founding customerHow the levels work
Data GovernanceAvailable
Dataset · CustomersOCUSMA · daily snapshot · approver: Credit control
Default L1Delivery terms L2Credit limit L3

Snapshot 11 October · 3 changes

  • 10311NameNordic Tools AB → Nordic Tools AB (SE)L1Recorded
  • 10450Delivery termsFOB → DAPL2Needs sign-off
  • 10877Credit limit25,000 → 45,000, changed in M3L3Violation
Approvals inbox · 1 to sign off · 1 violationApproveAcknowledge

Example dataset, records and values.

The core

Three levels: how much control each field gets

Pick a level to see what happens when its field changes: what goes on in M3, and what M3CloudSlam does with it.

L2What happens to a change

For important fields, e.g. delivery terms or an allocation method

  1. 1In M3A user changes it in M3M3 carries on as usual: nothing waits for an approval.
  2. 2In M3CloudSlamThe snapshot finds itThe change gets the status: waiting for sign-off.
  3. 3In M3CloudSlamIn the approver's inboxOnly users with the dataset's approver role can decide.
  4. 4In M3CloudSlamApproved or rejectedSigned off, or rejected and flagged for follow-up. M3CloudSlam never reverts M3.
  • ✓Sign-off afterwards, never blocking
  • ✓One inbox for all datasets
  • ✓Every decision on record

Per dataset, per field

One table, three levels

Each dataset has a default level. Individual fields can be set higher or lower, so a table can simply be followed while a few critical fields are signed off or changed only through M3CloudSlam.

Customers: dataset defaultL1Follow every customer change
Delivery termsL2Steers delivery, so changes are signed off
Credit limitL3Changed only through a proposal

Example dataset. L3 needs a write transaction for the table in M3.

Which level for which field

Control where it pays off

Not every field is equal. What a field does in M3 tells you how much control it deserves.

Steers behaviourCredit limit, allocation method. A wrong value changes what M3 does.L2 or L3
Copied into transactionsDelivery terms, payment terms. Decides again on every new order.L1 or L2
DescriptiveName, search key, phone number. Visible to people, no effect on M3's behaviour.L1

Not sure what a field does? Field-Impact tells you →

Snapshots

Every change, field by field

A governed dataset is an M3 table with its key fields, the fields to track, an approver role and a schedule.

On your schedule

Manual, daily, weekly or monthly. Large tables are read as deltas, with a full run every few snapshots.

Change review

Each snapshot lists what was added, modified and removed, per field or per record, with old and new values.

Any moment in time

Rebuild how a record looked at any snapshot: a point-in-time view of your master data.

Approvals

One inbox for every decision

L2 changes to sign off, L3 proposals to review and violations to acknowledge, across all datasets.

Who decides

Each dataset names an approver role, for example credit control for customer credit. Only users with that role can decide.

Roles that fit your organisation

Built-in viewer, operator and admin roles, plus custom roles, for example a data steward.

Data Governance · Approvals3 open1 violation
L2L2 changeCustomers · 10450 · delivery terms FOB → DAPApprove
L3L3 proposalCustomers · 10450 · credit limit 40,000 → 60,000Review
!ViolationCustomers · 10877 · credit limit changed outside M3CloudSlamAcknowledge
L2L2 changeItem/warehouse · A-2210 · allocation method 1 → 2Approve

Example items.

Proof

Every governed value has a history, ready for the auditor

Customer 10450 · credit limit L3

  1. 2 MarchAdded · 25,000Initial snapshotRecorded
  2. 14 June25,000 → 40,000Proposed, approved by credit control, written back to M3Executed
  3. 30 September40,000 → 55,000Changed directly in M3, found by the daily snapshotViolation
  4. 1 OctoberAcknowledgedCredit control: emergency raise, agreed by phoneAcknowledged
Audit report, as CSV. Filter by period, approver and level: every change with its old and new value, approval, approver, who changed it in M3 and when, and the violations.

Example history.

Overview

86%compliant
Datasets12
Pending7
Violations2
Stale1

Example figures. Stale: no snapshot in 7 days.

Getting started

Start light, tighten where it pays off

Each step is useful on its own, and the next one builds on it.

  1. Step 1FollowPut key master data tables on L1. Every change becomes visible, with no extra work.
  2. Step 2Sign offMove the fields that matter to L2. Their changes are approved afterwards.
  3. Step 3Change through M3CloudSlamCritical fields on L3: proposed, approved and written back.
  4. Step 4Close the side doorRestrict direct maintenance of L3 fields in M3, so M3CloudSlam is the only route. A decision you make in M3.

What it brings you

Master data under control, without slowing M3 down

  1. 1Nothing changes unseenEvery change to the fields that steer M3 is detected and recorded.
  2. 2Control where it mattersStrict levels for the few critical fields, light follow-up for the rest.
  3. 3M3 keeps runningSign-off happens afterwards; M3CloudSlam never blocks, locks or reverts anything in M3.
  4. 4Audit-readyWho changed what, when, and whether it was approved, in a report you can export.

Next in your journey

Data QualityAvailableMeasure how good the data is, not just who changes it.“Where is our master data wrong?” →Data ImportAvailableLoad changes safely, with a backup.“Can I load this safely?” →Field-ImpactAvailableFind out which fields steer M3 and deserve a stricter level.“What does this setting actually do?” →

Coming next Roadmap

Governance that knows what each field does

With the knowledge graph, M3CloudSlam will propose which fields deserve which level, and show on every proposal which processes and open orders the change will touch.

Take control of the master data that steers your 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