Today
In many plants, gauges, tools, complaints and shift logs run in Access databases that someone once built on the side. Nobody knows how many there are, who uses them or what their queries and macros calculate. When the author leaves or the file stops opening after the next update, a process that audits and deliveries depend on comes to a halt.
An example
At Polivo Kunststoffverpackungen, demi finds 46 Access files on drives, NAS and in personal folders. 29 are copies or have not changed in years, 17 are still in use, including the gauge register from 2009 with 1,180 gauges and the tool log for the Ø 38 mm closure molds. The agent describes the macros in plain language and shows that 64 gauges without a calibration interval never come up as due. The head of quality adds the intervals and decides which databases demi takes over and which go to the archive.
Your data, wherever it lives
Gauges, tools and complaints sit in Access databases on drives, NAS boxes and in personal folders, often in several copies, along with old Notes applications for requests and approvals. demi reads, understands and links them with items, machines and customers from the ERP, with your rights. The AI knows within days what each database is for and what its code calculates, and the department decides what happens next.
Where the data lives today
- Databases
- Legacy systems
- Folders & drives
- NAS & hard disks
- ERP
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 drives, NAS, personal folders and the ERP. demi reads every database file in full without changing it: tables, queries, forms, reports, macros and linked tables, plus size, last change and users. The content is linked with items, machines and customers from the ERP.
- 2 · PermitPermission Layer
Content is visible only to people who may open the file today; IT sees the inventory with name, location, size and usage, not the content. Tables with personal data stay with the department in charge. A database is retired only after its department approves, and the approval is recorded.
- 3 · ActIntelligence Layer
The agent recognizes copies of the same database by structure and content and turns queries, macros and code into plain-language rules, each pointing to its place in the code. demi counts records, change dates and users exactly from the files; the language model only explains what it finds there.
How it runs
- 1
demi searches drives, NAS and shared folders for .mdb and .accdb files and records size, last change and users.
- 2
The agent reads tables, queries, forms, reports and macros and groups copies of the same database.
- 3
For each database it describes in plain language what it is for, who uses it and which rules sit in the code.
- 4
The data becomes queryable in demi, linked with items, machines and customers from the ERP.
- 5
The department decides per database: take over, archive or rebuild, and nothing is switched off before approval.
What changes
A complete register of all Access databases with purpose and users
Hidden rules in macros and code become readable and checkable
A clear plan for where each database goes
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
+192 hfreed per year
Assumptions and calculation
demi describes the tables, queries and macros of each database in plain language; the department decides.
10 h → 6 h per case
How we calculate
4 databases × 10 h × 40% × 1.0 (manual) × 12 months = 192 h
Value per year, before demi costs
Freed per year+192 h
Assumption: labor cost of $48.62 per hour in US manufacturing in June 2026 (BLS), plus workplace, IT and overhead.
= Value per year, before demi costs
+$12,480
gained per year
192 h ÷ 1,760 h per role = 0.1 full-time roles
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 someone have to collect the databases first?
No. demi searches every connected drive, NAS and shared folder for .mdb and .accdb files itself, old project folders included. Personal folders are searched only if you allow it, and even then IT sees only name, size and date.
Does demi understand macros and VBA code too?
Yes. The agent reads queries, macros and VBA modules and describes in plain language what they do, for example how a calibration date is calculated or a complaint is forwarded. Each description points to its place in the code so a specialist can check it.
Does this also work for old Notes applications?
Yes. demi reads Notes databases with their views, fields, workflows and reader rights, describes them in plain language and brings the content into the shared data set. The reader rights then apply in demi too, and you see which workflows need to be rebuilt.
Can we keep working while demi reads the databases?
Yes. demi only reads and changes nothing in the files. Whoever works with them today keeps working until the department approves the replacement, and demi reads again regularly so new entries reach the data set too.
