Logical
The business terms and definitions your organisation uses to describe data — extracted from dictionaries, glossaries, and prose definitions in your specs.
Logical elements give physical columns their meaning. Without them, lineage is just plumbing.
Logical Elements
3 of 4 Inventories
216
records
142
Approved
58
Pending
16
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.
Logical Inventory Agent
AI-powered extraction.
The agent reads data dictionaries and glossaries, extracting business terms with definitions, data types, and domain classifications.
Processes these document types
Understands tables, lists, and prose definitions interchangeably.
Human in the loop
Manual entry and review.
Business analysts and data stewards can add terms directly or refine and approve agent-extracted definitions.
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 Logical Elements table.
Manage business terms with definitions, data types, and domain classifications — ready for semantic matching.
| # | Trust | Action | Element ID | Element Name | Definition | Data Type | Domain | Source Documentation |
|---|---|---|---|---|---|---|---|---|
| 1 | High | Use | LDE-CUST-001 | Customer ID | Unique identifier assigned to each customer in the system | String | Customer | Customer Data Dictionary v3.xlsx |
| 2 | High | Use | LDE-ACCT-001 | Account Balance | Current monetary balance of the customer account | Decimal | Finance | Financial Terms Glossary.pdf |
| 3 | Medium | Use | LDE-TXN-001 | Transaction Date | Date and time when the transaction was processed | DateTime | Transaction | Transaction Processing Requirements.docx |
| 4 | Medium | Pending | LDE-PROD-001 | Product Name | Official name of the financial product or service | String | Product | Product Catalog Data Model.xlsx |
| 5 | Low | Pending | LDE-RISK-001 | Risk Score | Calculated risk assessment value for credit decisions | Integer | Risk | Risk Assessment Business Req.docx |
| 6 | Low | Pending | LDE-ADDR-001 | Address Line 1 | Primary street address component for customer location | String | Customer | Manual entry via UI |
This is a preview — the real interface supports full CRUD operations
Three more inventories.
Logical 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.
Logical elements are one half of every glossary match. Approved matches feed the Business Glossary, then roll up into the Global Glossary.
Ready to catalogue your business terms?
We'll point IDA at your dictionaries and glossaries in a 30-minute call and show you the populated terminology that comes out.
Book a demo