OEM Gas Analyzers for System Integrators

An OEM engagement starts with a mutual NDA and a requirements brief — target gases, range, matrix, host interface, certification targets, and anticipated volume. Our engineering team evaluates platform fit, flags gaps honestly, and proposes a candidate core. From there, co-design, prototype, pilot, and production are staged deliverables under a co-design agreement rather than a catalogue purchase. Integrators talk directly to application and hardware engineering, not just sales.

The decision turns on three factors. (1) Target gas and range — TDLAS for selective single-line laser absorption against a complex matrix or low-ppm / ppb sensitivity; NDIR for cost-efficient CO / CO₂ / CH₄ at industrial-grade repeatability; GFC for NDIR-class cost envelope with reference-cell rejection of overlapping IR absorbers. (2) Power and packaging — NDIR fits sub-5 W panel and battery duty; TDLAS and GFC are higher-power split-architecture modules. (3) Cross-interference and matrix — flue gas with combustibles, water vapor, or overlapping species pushes the decision toward GFC or TDLAS. Discovery starts with your gas list and matrix; we propose the candidate platform and decline honestly if none fit your application.

A platform core is the sensing front end — laser source or IR optics, reference cell, signal-processing electronics, and core firmware. The integrator owns the housing, sample path, user interface, certification filing, and end-customer relationship. A finished analyzer is a turnkey instrument from the GESHINE catalogue (CEMS systems, in-situ probes, sampling-conditioning skids) that ships ready for plant deployment without integration engineering. If you want a unit to specify and install, look at the catalogue. If you want a sensing core to embed inside your own product line, the OEM program is the entry point.

MOQ depends on the platform and the scope of the co-design. A TDLAS OEM core with custom calibration or firmware typically starts at a small pilot batch (single-digit units) for the prototype phase, with production MOQ aligned to the integrator’s forecast rather than a rigid catalogue number. Lead time from NDA to first prototype is typically 6-12 weeks for a platform match with minor customization; full co-designed variants can run longer. We agree these numbers explicitly during discovery — no blanket promises.

Each unit ships with a per-serial calibration record covering spectral cal and range linearity. NDIR cores typically expose an Auto-Self-Calibration (ASC) routine that learns a fresh-air baseline; for sealed-room or process-line deployments where the module never sees ambient air, we document how to disable or override ASC via Modbus register or firmware option, and we confirm the platform-variant default during discovery so it is never a silent surprise. Verification cadence — bump tests, full re-calibrations, and field-verification intervals — is written into the acceptance test plan against the integrator’s duty rather than published as a generic “X months” headline.

Industrial laser diodes, IR sources, and reference-cell assemblies are designed for continuous-duty operation; the practical service life depends on duty cycle, sample matrix, and ambient temperature at the controller. Rather than a generic year number, we publish the wear-part list (laser diode for TDLAS; broadband IR source for NDIR; reference-cell seals and rotation mechanism for GFC; optical windows where applicable) and an expected maintenance cadence in the program-specific characterization summary. Replacement-part availability and refurbishment routes are a planned part of the LTS commitment, not an afterthought.

Cross-sensitivity is platform- and matrix-specific — a generic interferent table published on a website is more marketing than engineering. During discovery and co-design, we capture your matrix (gas composition, water vapor, particulates, temperature, pressure) and provide a matrix-aware cross-sensitivity disclosure inside the characterization summary. For TDLAS the selectivity story is single-line absorption against a known background; for NDIR it is filter bandwidth plus sample conditioning; for GFC it is reference-cell correlation that isolates the target species from overlapping IR absorbers. We do not make the integrator guess at the bench.

Yes — adapting to an integrator’s existing mechanical envelope, electrical interface, or host protocol is a routine co-design scope. If you already have a sensing module in production and want to qualify a second source for supply-chain risk reduction, we target form / fit / function compatibility under a documented qualification plan. We do not trade on the trademarks or part numbers of other vendors, and we will not publish “drop-in for [Brand X]” claims — but the engineering work to make the integration genuinely second-source viable is a normal program scope.

Default position: GESHINE retains ownership of the platform core (laser source, optical design, reference-cell assembly, core firmware) and licenses it to the integrator for the agreed product scope. Integrator-specific customizations — mechanical housings, application firmware forks, application calibration models, host protocol bridges — are the integrator’s IP. Module identification, firmware banner, host protocol identifier, and packaging can be customized to the integrator’s branding under a private-label arrangement; we do not enforce GESHINE trademark visibility on integrated products. The exact licensing scope and any exclusivity terms are negotiated per engagement and written into the co-design agreement before prototype work begins.

The platform cores are supplied with CE, RoHS, REACH, and FCC documentation on request — these are part of the standard commercial scope. ATEX hazardous-area certification, SIL functional safety, MCERTS / EN 15267 CEMS certification, and regional environmental approvals (US EPA performance specs, China HJ methods) are handled as a co-engineering scope because certification requires testing of the full integrated product, not the platform core alone. We support the integrator’s certification filing with platform-level test data, design documentation, and factory audit access.

Yes, with discipline proportional to the engagement. For active OEM programs, GESHINE issues Product Change Notifications (PCN) with an agreed window before any impacting change to the platform core. Last-Time-Buy (LTB) bridge orders are sized to the integrator’s installed-base service horizon, not a fixed catalogue cliff. End-of-Life (EOL) notice carries a documented migration path to a form / fit / function-equivalent core where one exists. Critical sub-components are reviewed for second-source viability during co-design and tracked in a supply-risk register refreshed at quarterly forecast review. For integrators whose end-customer contracts require longer obsolescence windows (military, regulated environmental, clinical), a multi-year lifecycle commitment is negotiated as part of the co-design agreement, not assumed by default.

After-shipment support is structured around the program rather than a generic SLA poster. Each engagement has a named application engineer for technical questions — first-response window agreed in the co-design contract against the integrator’s downtime tolerance. RMA evaluation, repair-or-replace decision, and return shipment windows are written into the production agreement against your service obligations to the end customer; spare-parts kits are scoped for programs with field-service requirements. We do not publish a one-size-fits-all RMA SLA because the meaningful number depends on whether your unit sits inside a CEMS cabinet at a regulated stack or inside a greenhouse climate panel.