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.
One configuration per data point: how each source's fields, values, records, and folder conventions reconcile into it. See how sure Eagle is about each treatment and why, tell it how the sources should reconcile, edit a treatment by hand, and preview how selected sources merge. Locations is the clearest place to start.
How each system names a facility, and how those names become the six canonical locations.
312 RailcarRX job codes and four Sage revenue accounts collapse to seven service types.
AAR mechanical designations and the ops database car family map to seven car type families.
Dates from each system aligned to one fiscal calendar and one week boundary.
The customer named on a signed SharePoint contract matched to a Salesforce account, strongest signal first: tax ID, then customer number, then domain, address, and contact email.
Vendor ids from six Sage databases, email sender domains, and TimberScan captures keyed together on tax ID.
Bank feed nicknames and Sage bank ids matched to eight accounts, with internal clearing accounts kept as members that never expect a statement line.
Which RailcarRX and Sage work order states count as open backlog, which are storage or released, and how a Sage job joins its work order.
How released work orders and ops database cycles become one counted car cycle, and when a return is rework.
Which Sage accounts and invoice types are operating revenue, credits, or pass-through, and how the billing repair card links a line to its car.
AboutTime cost codes and approval flags sorted into direct, indirect, and training hours, with ADP and Sage joined for identity and checks.
ADP pay and Sage job cost kept as actual and standard cost, with the burden rate and the timesheet tying pay to work orders.
RailcarRX status history and ops database gate, move, and inspection records normalised to six event types, sensor timestamps winning.
Sage invoices and receipts, bank lockbox lines, and customer email sorted into one activity history. Sage owns the balance; everything else adds history.
An invoice's stage from the email it arrived in, through TimberScan capture and approval, to the Sage payment and the bank debit that clears it.
BAI2 type codes and file handling for the one connection that feeds this object: what is a transaction, what is a balance, and what is a duplicate.
Which SharePoint files are agreements, which role each plays, and how a signed document reconciles to the Salesforce contract it governs.
Which revenue lines and released cycles feed the numerator and denominator, and how the existing spreadsheet and dashboard figures compare.
Which approved hours count, how they match a cycle, and why the shop scoreboard runs high.
Which events open and close a span, which holds come off it, and which cycles cannot be measured.
What counts as completed work, what closes it, and which work never invoices and should not be chased.
Actual and standard cost per released car, kept side by side, with the burden and Ashdown questions still open.
What puts an invoice in the queue, what holds it, and what closes it.
The match rules for each transaction kind, what becomes a composite match, and what is an exception with an owner.
What is ready for the run, what is held and why, and how a paid item is cleared by the bank.