Map the records
Operations Data Model is about understanding how the core records that run a tenant relate to one another. In AWRA, that means the team treats tenants, users, roles, locations, items, vendors, customers, and transactions as connected operating records instead of isolated screens.
The practical value is visibility. Users can see who owns the record, where the work happened, which item or party was involved, and which transaction changed the balance before they commit stock, money, access, or a customer promise.
In practice, a purchase order belongs to a tenant, references a supplier, uses item lines, affects receiving, and eventually feeds stock and finance reporting. The record map below shows the minimum chain a manager should understand before asking for a report or correction.
Core record chain
Tenant
The account boundary for users, settings, records, and reports.
Users and roles
Define who can create, approve, edit, or review work.
Locations
Show where stock, sales, counters, and branch activity happen.
Master data
Items, vendors, and customers give transactions reliable references.
Transactions
Requests, orders, receipts, sales, payments, and adjustments create history.
Model rules
- A tenant is the boundary for operational records.
- Users and roles explain who was allowed to act.
- Locations explain where operational impact happened.
- Transactions connect master data to reports.