Verified EngineeringBook a call

Data schema

What an ML engineer needs to judge fit: the structure of the reasoning record and validation report that come with each model.

The structures below are illustrative. Field names and formats are agreed with each client at the start of a program.

Reasoning record

One record per decision: a feature, a fit, a tolerance or a datum choice. Records link to the feature IDs in the native model and to the PMI in the AP242 file.

{
  "model_id": "S-0142",
  "standard": "ISO",
  "decisions": [
    {
      "feature_id": "Hole1",
      "feature": "bore",
      "decision": "Ø25 H7",
      "why": "sliding fit with a Ø25 g6 shaft",
      "reference": "ISO 286-2",
      "dfm": "drill and ream; H7 holds on a lathe",
      "datum_role": "primary axis A"
    },
    {
      "feature_id": "Pattern1",
      "feature": "4 × Ø6.6 holes",
      "decision": "position Ø0.05 to A",
      "why": "M6 clearance holes locating on a mating flange",
      "reference": "ISO 1101",
      "dfm": "standard drilling tolerance is sufficient"
    }
  ]
}

Validation report

Every check has a pass or fail result and the value measured, so failures can be filtered out or used as negative examples.

{
  "model_id": "S-0142",
  "checks": [
    { "check": "geometry_vs_reference", "result": "pass" },
    { "check": "pmi_attached_to_features", "result": "pass", "count": 9 },
    { "check": "interference_with_mates", "result": "pass" },
    { "check": "drawing_views_complete", "result": "pass" }
  ],
  "reviewed_by": "second engineer",
  "status": "accepted"
}

Want the real thing?

We share full sample files on a walkthrough call: native model, AP242, drawing, reasoning record, macro and validation report.