The spectrophotometer in Lab 3 has been "Under observation" for eleven weeks. Three different technicians have logged entries against it. None of them can tell you whether it's still in service, pending parts, or effectively condemned — because each entry went into a separate log, the status was never updated in the equipment register, and nobody with authority to sign a condemnation note was ever formally notified.
That is a calibration audit finding waiting to happen. And it happens routinely in labs that track maintenance events without tracking maintenance state.
The Twelve-State Maintenance Status and Why It Matters
The Maintenance Status choice field carries twelve options, and the ordering is not incidental. It maps a complete equipment lifecycle:
Operational states: Completed/in service, Under warranty, Under observation. Blocked states: Pending spares, Needs to be sent for repairs, Pending quotation (in-house not possible), Sent to dealer. End-of-life states: Beyond repair, Phased out, Not in syllabus — all with "needs to be condemned" appended, plus Condemnation note # as the formal close-out status. The default is "Pending checking by me" — which means every new record enters the queue in a state that signals unreviewed, not operational.
This structure transforms the status field from a label into a workflow. Filter for Sent to dealer for repairs and compare Taken out date to Expected date of return — anything past its return date without Returned on populated is overdue. Filter for Pending spares and sort by Date attended — age of pending spares requests, visible instantly. Filter for Beyond repair — your condemnation queue, waiting for Condemnation note # to be assigned and the formal write-off process to begin.
Components Replaced With Price as the Maintenance Cost Ledger
The Components/parts replaced with price richtext field is the granular cost record per repair event. Total cost of repairs captures the aggregate in INR — the budgeting number. But the components field is the technical record: which part failed, what was used to replace it, what that part cost.
For recurring failures, the components history tells you whether the same part is being replaced repeatedly. A centrifuge that has had its brush assembly replaced three times in eighteen months isn't being maintained — it's being kept artificially alive, and the cumulative parts cost may already exceed replacement cost. That analysis requires the itemized field, not just the total.
Repairs by as a contact field records the specific person or vendor who performed the work. Supplier's Name records who supplied the replacement parts. Both are accountability anchors — when a repair fails within days and the fault description for the follow-up entry describes the same symptom, you have a documented basis for a warranty claim or a supplier dispute.
Calibration as a Parallel Track Within the Same Record
The calibration fields — Calibrated on, Valid till, Calibration procedure, Calibration report No., and Calibration Agency — coexist in the same record as the maintenance log. For laboratories operating under ISO/IEC 17025 or similar metrological frameworks, this integration matters.
An instrument with an upcoming maintenance event and an upcoming calibration expiry should not be returned to service after maintenance without re-calibration. Having both dates in the same record makes that overlap visible. Filter for Maintenance Status = Completed/in service and Valid till within the next 30 days — those are the instruments that need calibration scheduling before the next quarter, not after.
Calibration Agency and Calibration report No. are the traceability fields that an auditor checks during a NABL or equivalent assessment. The agency must be accredited; the report number must reference a traceable certificate. Keeping these in the equipment record, alongside the maintenance history and DBCE Tag, means the instrument's complete metrological and maintenance dossier is in one searchable location.
The DBCE Tag field is the organization's internal asset identifier — the physical tag on the instrument that connects the database record to the physical object. Without this anchor, records get orphaned from assets. The Serial No. cross-checks against manufacturer documentation. Together, they eliminate ambiguity when similar instruments are in the same laboratory.