Mappings
Every data point across projects
The dimensions, objects, and derivations the organization consolidates from every connection, how source values reconcile into them, and where each one comes from.
Where each data point comes from and how they relate: connections feed dimensions and objects, derivations build on them, and automations use the result. Select a node to lay out its tree.
10 source systems7 dimensions10 business objects8 derivations6 automations
Approved / healthyDraft / needs attentionSuggested / runningAction needed
Inputs sit above the node, uses below. Hover any node to see its path to the selected one.
Tree for AP Invoice to Payment
Drag to pan · scroll to move · ⌘ or Ctrl + scroll to zoom
AP Invoice to Payment
Automationattention
Every vendor invoice from intake through extraction, validation, approval, payment, and bank clearing, read from the mailbox, TimberScan, Sage, and the bank.
Built from6
Dimensions
Business objects
Derivations
Feeds0
An automation. It reads the model and writes nothing back.
Details
- Cadence
- Continuous
- Trigger
- New email in ap@eaglerailcar.com or a new TimberScan scan, plus a 15 minute Sage and bank sweep
- Owner
- Priya Raman
Open automation15 upstream · 0 downstream