Skip to main content
GullySystem
Manufacturing

Fixed Asset Register for Sensor manufacturers

Keep owned assets identifiable by value, location and custodian.

Assets and Fleet

Does this function belong in your operation?

Use when equipment, vehicles or other fixed assets need ownership and custody records.

An asset is acquired, transferred or disposed of.

Pressure controllers, reference gauges, temperature baths and chambers are recorded with calibration due dates and traceability certificates. A calibration run using a lapsed reference is blocked. Location is tracked.

Bring the records the workflow depends on.

  • Asset identifiers and purchase records
  • Locations and custodians
  • Accounting and disposal rules

Outputs to check

  • Asset and custody register
  • Movement and physical-check history
  • Accountant-ready acquisition and disposal schedule

Follow the fixed asset register workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Register acquisition

    Record the asset, purchase reference and approved value.

  2. 2. Assign custody

    Set the tag, location and responsible person.

  3. 3. Track movement

    Retain transfers and handover acknowledgements.

  4. 4. Verify physically

    Compare the register with actual assets and investigate differences.

  5. 5. Approve disposal

    Record the authorised retirement and pass financial adjustments to accounts.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Accounts assistant

Adds assets from purchase bills and gives the accountant the schedule they want.

Office or admin manager

Issues equipment to people and moves it between branches without losing track.

Owner

Sees what was bought this year and what has quietly disappeared.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Asset cannot be found

Record the discrepancy and investigation owner before any write-off.

Shared asset changes custodian

Capture the handover and effective location without creating another asset.

Disposal requested

Hold retirement until authorised and retain the supporting financial or physical evidence.

Can this work independently?

An asset register can operate independently from accounting with approved purchase values and identifiers. Purchasing supplies acquisition evidence; maintenance tracks service; accounting determines depreciation and disposal entries. A physical transfer changes custody, not necessarily ownership or accounting value.

Systems and records it connects with

  • Asset AMC tracking: Asset coverage dates, service visits and renewal status.
  • Purchase orders: Authorised supplier commitments and open line balances.
  • Finance and accounting reporting: Ledger-based period totals and reconciliation outputs.
  • Vendor management: Approved supplier identities, terms and sensitive-change controls.

Configure, test and introduce the workflow.

  • We start from a walk around your premises. You provide purchase bills and any old list, and get a draft register to correct.
  • Asset classes, depreciation methods and rates are set as your accountant directs. Their written sign-off is requested. Tags are printed in batches. Staff stick them on, and unmatched tags are traced.
  • Cost and accumulated depreciation come from your books. A trial schedule is printed. Compare it with last year’s. Purchases and transfers are entered as they happen. Practice for the accounts team comes before the next closing.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Assets have unique identifiers.
  • Transfers retain the old and new custodian.
  • Disposals reconcile with approved accounting entries.
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.

See the full industry workflow, reports and implementation plan →

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.

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.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  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.

Industry reports to connect with

  • 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

Questions before implementation.

When should sensor manufacturers consider fixed asset register?

Use when equipment, vehicles or other fixed assets need ownership and custody records. An asset is acquired, transferred or disposed of.

What should we bring to the requirements discussion?

Bring anonymised examples of Asset identifiers and purchase records; Locations and custodians; Accounting and disposal rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Keep owned assets identifiable by value, location and custodian. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Valuation, depreciation policy and tax treatment remain with your accountant.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Assets have unique identifiers. Use this check when reviewing the first working version.

Talk to us

Discuss fixed asset register for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

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