That engagement is the reason the evidence rule exists.

Service contracts were priced by hand. Technical and commercial data for more than 1 500 industrial devices was enriched with the first version of what became inRecipe, and the new features made the pricing model about 50 % more accurate.

Mika AhoProfessional Enricher
Ask Mika about this story →
1 500+

industrial devices brought into one register

About 50 %

more accurate service-contract pricing model

Situation

Service contracts were priced by hand, in a spreadsheet, on the judgement of a few senior people. That made quotes slow, hard to standardise and hard to teach. The device data underneath was fragmented: inconsistent component names, missing specifications.

Before
  • Contracts priced by hand, in a spreadsheet
  • Inconsistent component names, missing specifications
After
  • A pricing model that explains each estimate
  • More than 1 500 devices in one register

What was done

  1. Technical and commercial data for the device fleet was enriched and standardised with the first version of what became inRecipe, before source-verified reading existed. The resulting fields fed a pricing model that could explain each estimate rather than assert it.

Result

  • More than 1 500 industrial devices brought into one register.
  • About 50 % more accurate service-contract pricing model, from the newly enriched device data.
What did not work

Fast, plausible and impossible to check.

1

Nothing to check against

That engagement is the reason the evidence rule exists. The first version filled fields from what the model already knew, which is fast and plausible and impossible to check. Everything inRecipe does now, the document, the page, the refusal to write a value with no source, is the answer to what that run could not prove.

Rule nowNo value is written without a document and page.

One device, then

Illustrative, not the customer’s data. The values were plausible and well-formatted, and none of them said where it came from. That gap is what the current inRecipe was built to close.

RowDeviceName as recordedCategoryManufacturerPowerPressure
As recordedD-20417KOMPR RUUVI 30KW SARJA 2————
First version, no sourcesD-20417KOMPR RUUVI 30KW SARJA 2Oil-injected screw compressor no sourceMaker A no source30 kW no source10 bar no source

Device data behind a pricing model?

  1. 1Send a slice of the device register, 100 to 200 rows as they are today.
  2. 2Within days you see which specifications can be proven from the makers’ documents, and which cannot.
  3. 3One hour to walk it through together.
Book a Start

Your ERP, PDM or PIM stays where it is. A file export is enough to start.

Spare parts and aftermarket →

The recipes in this story

More customer stories