Mappings and normalization
How source-specific data becomes one analyzable model.
Every work order system speaks its own language: its own status names, priorities, work types, and trade labels. WorkOrderGuard normalizes all of it into one unified model so analysis behaves consistently across sources.
What gets mapped
- Statuses — source status labels map to a shared work order status vocabulary.
- Priorities — source priority labels map to a shared priority scale.
- Work types — the kind of work requested maps to shared work types.
- Trades — source trade labels map onto your account's canonical trade catalogue.
- Equipment — equipment classes and identifiers map to shared categories.
Who controls the mappings
You do. Each mapping is a reviewed decision in your account, and WorkOrderGuard proposes sensible defaults to start from. Decisions you confirm are remembered and reused for future imports from the same connection, so you should not have to make the same decision twice.
Why it matters
Normalization is what makes findings comparable. When two systems both report a job as "completed - vendor closed", mapping is what lets analysis treat them identically, and what lets estimated impact roll up across all of your data.