Case studies

2 problems we worked on.

A synchronization problem and a critical process rebuilt on governed data. Two fairly different situations, running on the same Filiament architecture underneath.

CASE 01 · ERP <-> ACCOUNTING

Seventeen ERP instances, seventy accounting instances

2 ERPs · 17instances on the operations side
70accounting instances
15,000invoices wrongly flagged as new
50 to 60people raising tickets

Situation

A multi-entity company ran operations on two legacy ERPs spread over 17 instances. Its accounting ran on 70 instances of another system, one per entity. The sync between them had become unreliable, and 50 to 60 people opened tickets whenever records disagreed. Some invoices never reached accounting, so they were never collected.

Problem

The data did not mean the same thing on both sides. A single invoice on one side could show up twice on the other, with a different amount or a different customer. Each gap was patched by hand, one case at a time. Nobody could say which rule had produced a given difference. At one point, 15,000 existing invoices were flagged as new.

What Filiament did

Filiament connected both sides to a shared ontology. Master sources feed the model. Each transformation is explicit and can be replayed. Records are checked against the rules before they are written back. Sync runs both ways: customer invoices go to accounting, while payments and supplier invoices come back to the ERP.

Outcome

  • Invoices created in the ERPs reach accounting.
  • The ticket flow has dried up.
  • Identifier, currency, VAT and duplicate anomalies are caught and logged. They no longer spread silently.
  • The same layer now carries the migration to the group's next ERP.
Legacy ERP ~70 accounting instances changed identifiers · currencies · VAT · duplicates FILIAMENT shared semantic model · explicit, replayable transformations Clean records written back to both sides

The next system plugs into the model once. It does not have to be wired to each of the others.

Case 02 · Cash collection forecast

A critical cash forecast running on disconnected spreadsheets

4types of data brought into one model
1shared model behind the plan and the reporting
Real timealerts on what is billed and collected

Situation

A construction group steered its billing and cash-in forecast in spreadsheets. Each forecast relied on information held in several systems: signed quotes, staff, invoices already issued and payments received. Nobody had all of it in one place, so the forecast was only as reliable as the last manual copy.

Problem

To automate the forecast, the workload plan first needed up-to-date data from each of those systems. Copying it by hand was slow, and the copies were never fully current. The forecast always lagged behind reality.

What Filiament did

Filiament keeps the workload plan in sync with the source systems. Staff, quotes, issued invoices and payments flow into one shared model. Reporting is built on that same model, and alerts fire in real time when something is wrong.

Outcome

  • Billing and cash-in forecasts are now produced in a tool, not in spreadsheets.
  • No more manual copying between systems.
  • Real-time reporting and alerts on what has been billed and collected.
SOURCE SYSTEMS Signed quotes Staff Issued invoices Payments received always in sync FILIAMENT one shared model · sold, billed, paid Workload plan Reporting Real-time alerts billing and cash-in forecasts, produced in a tool

The plan reads what has really been sold, billed and paid.

Start with one operational problem.

We pick a problem that crosses a few systems, model only the context it needs, and leave something the next scope can build on.

Request a demo