Separate general answers from project commitments
FAQ answers organize initial questions, but device support, performance, price and schedules need confirmation for the version and actual scope. General figures are not acceptance criteria without datasets, methods and operating conditions.
Accuracy means different things across tasks. Correct gauge detection does not prove needle-value accuracy; OCR must verify complete fields including signs and decimal points. Define consequential error types and unreadable cases rather than relying on one overall score.
Standards and protocols describe approaches, not automatic support or certification. Ask about versions, mappings, joint tests and boundaries requiring development.
Questions to prepare before a trial
Prepare instrument types, units, ranges, varied images and observation frequency, with the source of reference answers. If images are unavailable, discuss a survey rather than confirming capability from one attractive example.
Ask about unreadable observations, stale information and connectivity failures, including how users see these states. Message delivery alone is insufficient: verify receiver storage, time, units and review responsibility.
Discuss trials, installation, maintenance and commercial terms separately with an SI partner. Safety and command tasks require specific responsibilities and authorization; ordinary image reading does not replace protective systems.