How to track the MIDP/TIDP in Autodesk Forma/ACC
TL;DR — Autodesk ACC (now Autodesk Forma) is an excellent CDE: it stores the files, controls versions, validates naming conventions and coordinates models. What it doesn't have out of the box is an MIDP/TIDP deliverable register: the list of what should be delivered (ISO code, format, responsible party, due date) reconciled against what's actually in the folders. Today that's solved by exporting to Power BI or Excel. MIDP Manager puts that layer on top of ACC, and keeps it up to date on its own.
The gap ACC leaves
ACC answers "what files are there and in what version?" very well. It doesn't answer "what deliverables are missing and which are overdue?". There's no native "delivery plan" object: no list of expected deliverables with date and responsible party, and no planned-vs-actual comparison.
The proof is that the ecosystem itself fills this in from the outside: the usual guide for tracking the MIDP in ACC ends in exporting the data to Power BI or Excel and building a dashboard by hand. On the Autodesk forums there are explicit requests for a native "drawing register" — with status, revision, responsible party and issue date — and the answer is "it's not in ACC yet, use exports or a third-party app".
The three ways to track the MIDP on top of ACC
1. Exported Excel. You download the data and paste it into your spreadsheet.
- Pro: familiar, zero new tools.
- Con: it goes stale instantly; no live link; no alerts.
2. Power BI. You connect the Data Connector and build a dashboard.
- Pro: nice reports for the client.
- Con: it's read-only, not operational; you have to build and maintain it; it doesn't have the coordinator's workflow (mark, reassign, notify).
3. A dedicated layer on top of ACC (MIDP Manager).
- Generates the TIDP from a catalogue or imports it by parsing the file names in your ACC folders.
- Auto-links the first upload (the name matches the drawing code) and flags name/format deviations.
- Ships with the overdue agenda: what's blocking the site, what's due in 7 days, by project and responsible party.
- Respects manual unlinks and keeps the ISO 19650 history (transitions, versions).
How it works with ACC (without writing to your CDE)
MIDP Manager reads your ACC folders with read-only permission (data:read) — it doesn't modify your repository. You link one folder per stage × discipline, and from there the board reflects what's in ACC against what you planned. You connect one or several Autodesk accounts; each project is pinned to an account, so a member without their own account still sees the status.
A note on the first connection: Autodesk requires an account administrator to enable the app once in ACC (Custom Integrations) for the hubs to appear. If it isn't enabled yet, MIDP Manager detects it and shows you the exact steps instead of an empty list.
What if Autodesk builds it?
It's a fair question. ACC left this gap open for years — that's why an ecosystem of tools exists that charge for this layer on top of ACC. Autodesk's focus is models, cost and field, not the governance of the ISO 19650 delivery plan. Meanwhile, the coordinator needs to solve it today.
Who it's for
- Teams standardised on Autodesk Forma/ACC that track the MIDP in Excel or Power BI.
- BIM Coordinators who want status to update itself from ACC.
- Firms under ISO 19650 that need traceability and progress reports with no manual work.
Get started
Connect your Forma/ACC account, import your deliverables from the folders and let the board keep itself up to date.