OFF-HIGHWAY EQUIPMENT SOLUTIONS
ACES Data Built for Off-Highway Equipment
Skid steers, tractors, and combines do not fit the automotive ACES format. OHE DataManager builds a properly structured, validated ACES file for off-highway equipment catalogs, so the data reaches distributors and retailers in the format they expect.
25,981 mappable equipment records
1,239 equipment manufacturers
ACES equipment-based XML
THE CHALLENGE
Automotive ACES Was Not Built for Equipment
Standard automotive ACES organizes every application around a Base Vehicle: a specific year, make, and model. Off-highway equipment does not work that way. A skid steer or track loader comes off a production run that can span several years, and the engine inside it can change partway through that run. Off-highway ACES needs a structure that reflects that reality.
AUTOMOTIVE ACES
Keyed to a Single Year
​Built around Year, Make, Model, and Submodel, with one discrete model year per vehicle record. This is the format DM5 already manages for on-road applications.
OFF-HIGHWAY ACES
Keyed to Equipment and a Year Range
Built around manufacturer, equipment model, and vehicle type, anchored to an Equipment record that covers a full production run instead of a single year. This is what OHE DataManager was built to handle.
A skid steer is not a sedan. Production runs can span years, the engine can change partway through, and vehicle types come from off-highway type groups, never automotive ones.
THE SOURCE DATA
One Live Copy of the Official Off-Highway Database
OHE DataManager keeps a current copy of the Auto Care Association's OHE VCdb, the industry's official reference database for off-highway equipment, and resolves every application through the same chain the standard defines.
Beyond the chain above, each engine also carries aspiration, fuel type, fuel delivery, bore and stroke, and power output. The system enforces two rules everywhere: it always uses the off-highway engine tables, never the automotive ones, and vehicle types are filtered to off-highway groups only, so automotive types can never end up in an off-highway file.
THE OPPORTUNITY
Everything Your Catalog Can Map Against
9
off-highway segments: agriculture, construction, power sport, and more
172
application areas, from tractors and combines to off-highway trucks
25,981
equipment records ready to map, with year ranges included where published
18,227
engine configurations for precise, engine-level fitment
Eligibility lives on the machine, not on the mapping. Map a part to a machine that already carries official equipment identity, and it is automatically included in your ACES file, with no extra bookkeeping per application.
THE WORKFLOW
From Machine to Validated XML in Four Steps
Every step below happens in one workspace, so a part goes from a rough fitment note to a validated ACES file without switching tools. Click any screen to see it full size.
1
Find the Machine
Search the off-highway equipment database by year, vehicle type, make, model, or engine. Filter down from thousands of records to the exact machines a part fits, then select as many as you need at once.
2
Map It Once
Select the matching equipment records and map them to a part in a single step. Because equipment identity lives on the machine itself, every part mapped this way is automatically ready for ACES the moment the mapping is saved.
3
Add Structured Qualifiers
Fill in position, fuel type, and other qualifiers from dropdowns tied to the official reference tables. Free text is still there for the nuance dropdowns cannot capture, but the data that actually ships in the file is structured and consistent.
4
Deliver the File
Pick a catalog and export. The system checks which applications qualify and builds a validated ACES XML file, or a plain CSV version, ready to send to any trading partner.
FITMENT DETAIL
Sixteen ACES Qualifiers, Captured the Right Way
Every fitment note in OHE DataManager carries structured reference IDs, entered once through dropdowns, and turned automatically into the qualifiers an ACES file requires. Free-text notes still travel alongside each fitment for details that IDs alone cannot capture.
.png)
​Position and part terminology (shown in blue) come from the Auto Care PCdb, the industry's official parts reference database, which includes more than 7,600 defined positions. Every other qualifier resolves against the official OHE VCdb tables.
THE PAYOFF
Coverage That Grows Without Extra Work
CATALOG GROWTH
New Machines, Instant Eligibility
When a machine in the catalog gains official VCdb identity, every part you have already mapped to it becomes ACES eligible immediately. No re-mapping or touch-ups required.
AUTO CARE SUBMISSIONS
Closing the Gaps
Machines that are not yet in the VCdb are tracked as equipment requests, complete with the manufacturer's official legal name, ready to submit to Auto Care.
DATA REFRESH
One Sync Keeps Everything Current
When Auto Care publishes an updated off-highway VCdb, a single sync brings in new machines and refreshes identities and names. Applications you have already mapped never need to be touched.
Map to the machine once. The ACES file gets more complete every time the industry catalog grows.
