Skip to main content
GullySystem
Manufacturing

Business solutions for Sensor manufacturers

Explore software for work such as “Pressure sensors and transmitters”. Review each business function below, including when it fits and what to check before implementation.

Sensor manufacturers

How the business operates.

A pressure, temperature, proximity or gas sensor is bought for its accuracy. Customers rarely open the housing. They trust what the label and certificate say, and an auditor will ask to see what stands behind both. That trust rests on records made during calibration. Today they live on the test station or in an engineer’s folder.

Sensor models and variant codes

Hold each family with its valid ranges, outputs and connections, along with the cable lengths and labels that customers are allowed to choose. Sales picks only combinations that engineering has released. Surprises stop.

Sensing element lot control

Receive elements by lot with the readings taken on incoming samples, and issue them to builds in the order the stores should use them. A finished unit shows the element lot it carries.

Calibration runs and coefficients

Record chamber or controller runs, readings at each calibration point and the coefficients written to the unit, along with the technician and the soak time that applied to that run. Out-of-limit units go to rework. None ship.

Reference instrument register

List every master gauge and thermometer with its own certificate and due date. A calibration cannot be saved against an expired instrument.

Certificates and final test

Print the calibration certificate from stored readings, with the instrument used and the date. The final accuracy and ingress test is attached to the serial number.

Field returns and drift analysis

Book a returned sensor against its serial number and record the finding as a coded fault. Then group faults by element lot, potting batch and housing supplier to see where a pattern begins.

Orders and OEM custom builds

Take orders by model code, with custom cable lengths, labels or firmware for OEM buyers. Open orders show the stage each unit has reached.

Environmental chamber booking

Schedules the temperature and humidity chamber by unit batch, profile and run time. Calibration technicians see free slots on the booking board. A chamber out for service blocks bookings.

Firmware and compensation versions

Holds each firmware build and compensation table loaded into a unit, with the date and the engineer. Support reads it when a field unit drifts. Old versions stay on record.

Repair and recalibration jobs

Tracks units returned for repair or fresh calibration, with the fault found, parts changed and new coefficients. Customers get a revised certificate. Warranty cover is checked on receipt.

The records that hold the operation together.

  • Families and variant rules. Hold every family with its valid ranges, outputs, connections and cable lengths, so a custom OEM variant is released once by engineering and then quoted freely. Quotes stay inside released codes.
  • Sensing element lots. Receive elements by lot, record incoming readings against the datasheet limits and hold failing lots, so each build shows the exact lots it consumed. Lookups run both ways.
  • Bills of materials and builds. List elements, boards, housings, seals, potting compound and cable for each model, and let build orders issue the parts while recording the operator and the bench. Parts issue against the bill.
  • Calibration runs and coefficients. Store readings at every calibration point, the coefficients written to the unit and the chamber or pressure controller used, and route units outside limits to rework or scrap. Each run keeps its record.
  • Reference instrument register. List master gauges, reference thermometers and dead-weight testers with their certificates and due dates, and block expired instruments from new calibrations. No one keeps it in their head.
  • Final test and ingress checks. Record accuracy, hysteresis, insulation resistance and IP ingress results per unit with the tester’s name and date, and hold a failed unit back from the packing bench. Failures stay on the bench.
  • Certificates and labels. Print certificates from stored readings, with labels carrying model code, range and serial number, so a reprint three years later matches the original. Each reprint is logged by customer.
  • Field returns and drift study. Book returns by serial number, record the coded finding, and compare the stored coefficients against the new bench reading, so faults group by lot, batch and supplier. Drift becomes a pattern.

Operational bottlenecks to check

Calibration data leaves with the engineer

Readings sit in a file on the calibration station. Two years after shipment a customer asks for a certificate, and the lab must find proof of what the bench measured on that day. The station has been replaced. The file is on a disk nobody can find.

Reference instruments fall out of date

The master gauge or reference thermometer has a calibration due date. Without a register, units are calibrated against an instrument whose own certificate has lapsed, and the work of a whole week has to be repeated from the first point.

Element lots are not tied to finished units

The supplier of the sensing element quietly changes how it etches or bonds the die, and afterwards finished units start to behave differently from the lots shipped before. Some units drift more than others. Why? Nobody can list which finished sensors used which element lot.

Variant codes grow out of control

Range, output, thread and cable options multiply into hundreds of codes. Sales quotes one that engineering has never built. The order stalls.

Returned units show no fault pattern

Returned sensors are tested one at a time. Drift, zero shift and water ingress are recorded in free text. Patterns by element lot, potting batch or housing never emerge from notes written in a hurry.

Follow the work across teams.

This is a planning flow. Confirm the steps, owners and approval rules against your actual operation.

  1. 1. Enquiry and variant check

    The buyer names a range, an output such as 4 to 20 mA and a process thread, then the model code is checked against released variants before quoting. An unbuilt combination stops here.

  2. 2. Element receipt and incoming test

    Sensing elements arrive in lots with supplier readings, incoming samples are measured against the datasheet, and a lot that fails is held. Nothing from it reaches the bench.

  3. 3. Assembly and sealing

    Elements are bonded to boards, housed in stainless bodies and then potted or laser welded, and operators log the adhesive or potting compound batch used with each build. Every build names its bench.

  4. 4. Calibration

    Units go into a temperature chamber or onto a pressure controller, readings at each point are stored, coefficients are written, and the master instrument is recorded against the run. Failures go to rework.

  5. 5. Final test and certificate

    Accuracy, hysteresis and ingress checks are done and attached to the serial number, then a certificate prints from the stored readings. A reprint matches the original.

  6. 6. Shipment and field feedback

    Units ship with labels and certificates, and later returns and drift reports are booked against the serial number and grouped by cause for the design team. Patterns show up.

Roles and responsibility boundaries.

For owners and managing directors

See orders due, units in calibration, master gauges overdue and returns by cause, all without ringing the lab. One page covers it.

For design and product engineers

Release variants, study drift against element lots and potting batches, and revise the coefficient rules for a family. Rules are yours to set.

For calibration technicians

Run the chamber, save readings, write coefficients and see which reference instrument to use for the range in hand. The screen lists valid masters only.

For quality and the lab manager

Keep the instrument register current, sign certificates and review returns by element lot and housing supplier. Expiry dates stay visible.

For sales and customer support

Quote only released variants and look up a serial number to answer a customer’s query about its range, certificate or ship date. The lab is not disturbed.

Reports your managers need.

  • Units calibrated by day, station and technician
  • Master gauges and thermometers due or overdue
  • Element lots with failing incoming readings
  • Hysteresis and ingress failures by model and cause
  • Field returns by element lot, potting batch and housing supplier
  • OEM orders open, with stage reached
  • Certificate reprints requested, by customer

Connections to scope

  • Calibration station files
  • Barcode and label printers
  • Email
  • SMS or WhatsApp
  • Accounting export

Confirm data access, record ownership and the exchange method for each connection. Inclusion here does not mean every connection is available in a standard package.

Setup decisions and adoption risks.

Use these requirements to plan phases, data migration and user training. Agree the release sequence after reviewing your current systems.

Variant rules

Ranges, outputs, process threads, cable lengths and the combinations that are released are entered with your product engineers, family by family. Unbuilt ones stay blocked.

Calibration points and limits

Points per range, soak times, accuracy limits and coefficient rules for each family are agreed with your lab staff and tried on a sample unit first. Nothing goes live untried.

Certificate layout

The certificate carries the wording, units, tolerance table and signatures your customers and your own quality staff expect. Layouts are drawn up with a real sample.

Existing records migrated

Lot receipts, serial history, customer files and the list of master gauges are keyed in from the workbooks your lab keeps now, then checked against a few old certificates.

Limitations to settle before implementation

  • A distributor that resells sensors made elsewhere can work with simple stock and billing records.
  • Makers of general control gear will find Industrial Electronics Manufacturer Management Software closer.

Modules to consider first.

These functions connect to the operating model above. Confirm each one against the work your business actually runs.

Choose the operation you want to improve.

Use these activities to explain your scope. Your business does not need every function in the directory.

  • Pressure sensors and transmitters
  • Temperature sensors and RTDs
  • Proximity and photoelectric sensors
  • Level sensors
  • Load cells
  • Gas sensors
  • Custom OEM sensors
  • Sensor modules with signal conditioning
  • Calibration services
Talk to us

Start with the problem your team can describe.

Bring a sample record and show where information is copied, missed or waiting for approval. Scope the first useful change from there.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements