Systems
Every source system referenced in your SDLC documentation — IT-managed platforms, spreadsheets, reports, third-party feeds — extracted into one structured catalog.
Agents do the extraction. Your team approves what counts.
Systems
1 of 4 Inventories
47
records
31
Approved
12
Pending
4
Manual
Live counts from the agent pipeline
How records get here.
Records land in the inventory two ways — extracted from documents by an agent, or entered by your team. Both paths feed the same approval queue.
System Inventory Agent
AI-powered extraction.
The agent reads classified SDLC documents, identifies every system reference, and creates structured inventory records automatically.
Processes these document types
Batch processing — hundreds of documents in one run.
Human in the loop
Manual entry and review.
Data stewards, contractors, and employees can add systems directly or review and approve agent-extracted records before they're put to work.
Human actions
- Add records manually
- Edit existing data
- Approve pending items
- Remove duplicates
Every AI suggestion requires human approval.
Trust scores, by source.
Every record carries a trust score based on the maturity of the document it came from. Approved technical specifications produce high-trust records. Informal notes produce low-trust ones.
High Trust
From approved specs and signed-off requirements.
Medium Trust
From draft documents and work-in-progress specs.
Low Trust
From informal docs, emails, and early drafts.
Pilot distribution
From pending to production.
Records start as pending. They must be marked use before downstream tools like lineage can pick them up.
Pending
Awaiting review
Use
Ready for lineage
Lineage
Connected to pipelines
The Systems table.
A familiar spreadsheet-like interface with powerful filtering, sorting, and inline editing.
| # | Trust | Action | System ID | System Name | System Type | Business Owner | Source Documentation |
|---|---|---|---|---|---|---|---|
| 1 | Medium | Pending | MOBILE-APP-SYSTEM-UNKNOWN | Digital Mobile and App System | IT_MANAGED_SYSTEM | — | Tech Sys 1 tech req 1.docx |
| 2 | Low | Pending | 1001 | RBCACC | IT_MANAGED_SYSTEM | — | RBCACC Data Pipeline business requirements.docx |
| 3 | Medium | Pending | 850 | KYC System | IT_MANAGED_SYSTEM | — | RBCACC Data Pipeline Technical requirements.docx |
| 4 | Low | Use | SYS-ATM-001 | ATM System | IT_MANAGED_SYSTEM | Operations | Tech Sys 2 biz req 1.docx |
| 5 | High | Use | CRM-001 | Customer Relationship Management | IT_MANAGED_SYSTEM | J. Smith | CRM Technical Specification v2.pdf |
| 6 | High | Use | DWH-001 | Enterprise Data Warehouse | IT_MANAGED_SYSTEM | M. Johnson | Manual entry via UI |
This is a preview — the real interface supports full CRUD operations
Three more inventories.
Systems is one of four. Together they form your end-to-end landscape — from the source system down to the column in the database.
Tools that depend on this inventory.
Systems are the nodes in the lineage graph. Once they're in here, lineage falls out automatically.
Ready to build your Systems inventory?
We'll point IDA at a few of your real documents in a 30-minute call and show you what comes out.
Book a demo