Start with a representative family
Choose a defined product family and record its models, configurations, suppliers, and the people who own its evidence. Agree which destination schema the work needs to support.
Inventory what already exists
List specifications, BOMs, declarations, certificates, test summaries, and carbon reports. Keep original filenames, dates, revisions, supplier identities, and product references. Do not replace an original with a normalized copy.
Connect each value to a source
For every candidate field, capture the document, page or row, excerpt, unit, and normalization note. Distinguish a source being present from its accuracy being independently verified.
Separate gaps from conflicts
Missing evidence needs a specific supplier request. Conflicting evidence needs a decision about source meaning, revision, or applicability. Keep both sources until the conflict has been resolved.
Make human review actionable
Assign a responsible owner, record the question, retain candidate values, and preserve the reason for any approved decision. A confidence score alone does not establish evidence validity.
Prepare the handoff
Deliver normalized records alongside source lineage, review notes, and the outstanding-action register. Validate field names, units, access classifications, and the agreed platform import schema.