Aug 11, 2026Services & Support
Technical Alignment for Custom OEM Sensor Projects
A practical framework for defining application conditions, interfaces, prototypes and verification before approving a custom sensor configuration.
Direct answer
A custom sensor project should convert the application need into an approved technical specification before production. The specification should define process conditions, mechanical and electrical interfaces, required performance, evidence, responsibilities and change control. Customization does not guarantee suitability; the selected configuration must be verified against the actual application.
Define the application
Provide the measured variable, medium, range, process and ambient temperatures, pressure or level conditions, installation, output, power and environmental constraints. Explain how the measurement will be used and what happens if it is unavailable or incorrect.
Avoid broad descriptions such as “high precision,” “corrosive,” “high temperature” or “harsh.” Replace them with measurable conditions and applicable standards.
Establish the interface specification
Document:
- mechanical dimensions and mounting;
- process connection and sealing;
- wetted materials;
- probe, cable or enclosure configuration;
- electrical connector and pinout;
- supply, output and communication;
- scaling, units and update behavior;
- labels, documentation and packaging;
- required tests and records.
Protocol registers, scaling or connector changes should be controlled as configuration items. Do not assume that a requested interface is available until feasibility is confirmed.
Review feasibility and risk
Identify requirements met by an existing configuration, requirements needing modification and unresolved items. Review material compatibility, temperature influence, structural limits, sealing, certification and manufacturing capability where relevant.
Certification or hazardous-area use cannot be extended to a modified product without applicable evidence and approval. A custom change may affect existing ratings or test coverage.
Prototype and verify
Use drawings, samples or a prototype when the design or interface requires validation. Define acceptance criteria before testing. Verification may include dimensions, wiring, output, configuration, functional response and agreed environmental or process-related checks.
A prototype result applies to the tested configuration and conditions. Record deviations and confirm whether further validation is needed before production.
Control production and changes
Use an approved bill of materials, drawings, configuration and inspection plan. Identify critical characteristics and required records. Changes to materials, components, firmware, dimensions or suppliers should follow the agreed notification and approval process.
Define how nonconforming items, rework and deviations will be documented. “Equivalent” substitutions should not be accepted without technical review.
Plan commissioning and support
Provide installation, wiring and configuration information suitable for the project. Assign responsibility for site checks, regulatory compliance, commissioning and maintenance.
Remote support can help clarify drawings, wiring and operating data, but it does not replace qualified site engineering. Support availability and response arrangements should be agreed rather than assumed.
Practical questions
Which fields can be customized?
Availability varies by product family. Connections, dimensions, cable, enclosure, output or display may be reviewable, subject to feasibility, quantity, validation and schedule.
Does a custom model require new testing?
Possibly. It depends on what changed and which requirements apply. Define the verification plan during feasibility review.
How are materials confirmed?
Use the approved specification, configuration identification and applicable supplier or batch records. Evidence requirements should be agreed before production.
Who approves the final configuration?
The project should identify customer and supplier approvers. Approval should reference the exact revision of drawings and specifications.
Next step
Prepare an application and interface specification. HRT can review available standard and custom options, identify unresolved requirements and propose a verification path. Final approval should reference the exact model/configuration.
