The purchasing decision
Request interface documentation, sample logs and exact firmware/hardware identities. Separate experimental integration from production suitability. Preserve the configuration that produced a dataset so replacements can be evaluated on the same basis.
Keep these records
- Required data access.
- Configuration and revision record.
- Repeatability acceptance plan.
Give each record an owner and a revision or date. If a supplier proposes a different part or test condition, record it as an exception for review before treating the quotation as equivalent.
Turn the review into a sourcing request
Start with the linked component checklist, add the actual platform and part identity, and state quantity, destination and timing. List unresolved requirements explicitly so the first discussion can focus on those gaps.
IMU modules — requirement checklist