Today
The business depends on things nobody fully knows: nightly exports, scripts on old servers, FTP transfers to customers and suppliers, spreadsheets someone copies every Monday. When something fails, IT spends hours finding where the chain breaks. And every digital project starts with weeks of asking which data exists where.
An example
At Wattaris, demi finds 41 systems and 126 regular data flows, 23 of them nightly exports that appear in no documentation. One sends the test bay data of the 630 kVA transformers to the ERP by FTP every night; the FTP server's log leads to a script on a PC under the test bay manager's desk, with the password in plain text. The head of IT moves the process to a managed server and next tackles the 6 flows that only an outside service provider knows.
Your data, wherever it lives
Who sends which data to whom is scattered across job schedules and scripts on servers, export folders and FTP directories, configuration files, tickets, maintenance contracts and invoices, and some of it lives only in a few colleagues' heads. demi reads, understands and links them, with your rights. The AI draws the map of all systems and data flows in days, where a project would otherwise take months, and the head of IT decides what gets secured first.
Where the data lives today
- Folders & drives
- Databases
- Legacy systems
- Tickets
- PDFs
- E-mails
How demi solves it
Three layers in this order: connect the data first, then the rights, then the AI.
- 1 · ConnectData Layer
The case needs data from servers and job schedules, export folders, FTP directories, the directory service and the ticket system, plus contracts and invoices. demi replaces nothing and records every system, data source and data flow with content, volume, age, owner and cost. The map stays current because demi reads again regularly.
- 2 · PermitPermission Layer
The map shows systems and data flows, not their content; content is visible only to people who may see it today. demi recognises credentials in scripts and configurations and never displays them. Whoever looks after a system confirms its entry, and every change is recorded.
- 3 · ActIntelligence Layer
The agent reads job schedules, scripts and configurations and works out which program moves which file from where to where, and when. Tickets, contracts and invoices add owners and costs, and it flags processes that hang on one person, an old server or an expiring contract. Every connection on the map points to the file it comes from.
How it runs
- 1
demi reads job schedules, scripts, export folders, FTP directories and configurations on the servers.
- 2
The agent works out which system sends which data to whom and when, and draws the map from it.
- 3
Tickets, contracts and invoices add the owner, maintenance and cost of each system.
- 4
The agent flags processes without an owner, on old servers, with a plain-text password or known to only one person.
- 5
Owners confirm their entries, and the head of IT decides what to secure or replace first.
What changes
An overview of all systems, data sources and data flows
Faults found faster, because the chain is visible
Dependence on single people spotted before someone leaves
What does it bring you?
Check it with your own numbers
Every starting value is an assumption you can change. The calculation sits right below, step by step.
Your numbers
Result
+81 hfreed per year
Assumptions and calculation
demi shows the chain from source to target with its owner, instead of IT tracing it again every time.
90 min → 63 min per case
How we calculate
15 interface questions × 90 min × 30% × 1.0 (manual) × 12 months = 4,860 min = 81 h
Value per year, before demi costs
Freed per year+81 h
Assumption: labour cost of €49.50 per hour in German manufacturing in 2025 (Destatis), plus workplace, IT and overheads.
= Value per year, before demi costs
+€5,265
gained per year
An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.
Combine with more cases and get the packageQuestions about this use case
Does IT have to document everything first?
No, demi reads what is already there: job schedules, scripts, configurations, folders, tickets and invoices. Owners only check their entry and add what no file says, such as why an export runs at three in the morning.
What does demi do with passwords in scripts?
demi recognises credentials in scripts and configurations but never displays them. The map only notes that a password sits in plain text at this point, so IT can move it to a secure store.
Does the map also show which data lives where?
Yes. Besides systems and data flows, demi lists every data source from the ERP to the external hard disk with content, volume, age, owner and protection needs. You see where data is duplicated and which questions it can already answer today.
Does the map stay up to date?
demi reads again regularly and reports changes: a new export, a data flow that has not run for days or a maintenance contract that is running out. Whoever looks after the system confirms the change.
