The sticker, the spreadsheet, and the hope.

An instrument can appear available at point of use while its calibration, maintenance, cleaning, qualification, configuration, or operator requirements are no longer current. If those facts live in different systems, the execution workflow may discover the problem only after work has begun—or not until review.

Walk through your facility and trace a single instrument's data. Calibration schedules live in an Excel spreadsheet that Katie maintains. She's on vacation this week. Usage logs sit in paper binders that operators sign when they remember. Maintenance records exist in the CMMS, which doesn't talk to anything else. Service contracts are PDFs buried somewhere in SharePoint. Deviation history lives in the QMS, but you have to search by equipment ID manually. And the current calibration status? That's a sticker on the side of the instrument. Whether it's accurate is anyone's guess.

Metrology calibrates the equipment and applies a label with calibrated and due dates. The label is useful at the asset, but it cannot account for a failed as-found result under assessment, a new restriction, an overdue prerequisite, a configuration change, or a status decision made after printing. The sticker is evidence of a prior event—not a live eligibility decision.

An electronic warning still transfers the decision to an operator who may not have the authority or evidence to assess the risk. Seal evaluates the configured eligibility rules before selection. Ineligible assets are blocked. Any permitted exception is a separate, authorized, time-bound decision with defined scope, controls, evidence, and review—not a generic Continue button.

Equipment isn't binary. It moves through states, and those states determine what you can do with it. Every piece of equipment in Seal exists in one of four states. Available means calibration is current, cleaning is verified, and operators can select it for batches and tests. In Use means it's currently assigned to a batch or sample. The system tracks who's using it, for what purpose, and when they started, preventing other operators from selecting it. Cleaning Required means usage is complete but cleaning hasn't been verified yet, so it can't be used again until that's logged. Out of Service means calibration expired, maintenance is overdue, or someone manually took it offline. Equipment in this state cannot be selected for any GMP work, period. The key insight is that state transitions are automatic and enforced. When calibration expires, the equipment moves to Out of Service without anyone lifting a finger. When cleaning is verified, it moves to Available automatically. Operators don't manage states. The system does.

In most organizations, usage logging is a manual process. Operators sign a paper log or fill out a spreadsheet. They forget. They approximate. They backfill at the end of the day. In Seal, usage is logged automatically because equipment selection is part of the workflow. When an operator starts a batch step, the system prompts them to select equipment. They scan a barcode or choose from a list. But only Available equipment appears. The system immediately logs the equipment ID, operator, timestamp, and batch step, linking the usage to both the equipment record and the batch record. When the step completes, the system prompts the operator to release the equipment. They confirm, and the system logs the end timestamp, calculates total usage time, and transitions the equipment to Cleaning Required if that's how you've configured it. No paper logs. No manual data entry. No "I forgot to log that run from yesterday." The equipment record becomes a complete history: every batch it touched, every test it ran, every operator who used it, every cleaning event, total hours of use, and usage trends over time.

Manufacturer, model, serial, internal identifier, system, parent and child components, site, area, location, owner, custodian, intended uses, specifications, criticality, commissioning, qualification, calibration class, maintenance strategy, software and firmware, interfaces, safety class, documents, and lifecycle state define the asset.

Moving, renaming, upgrading, or replacing a component preserves dated relationships. A sensor can be traced through the system and process functions it supports.

The same equipment type may support exploratory work, release testing, process control, monitoring, storage, or safety. Intended use connects the asset to products, methods, recipes, parameters, ranges, accuracy, data needs, environments, operator roles, and regulatory relevance.

Criticality and control requirements follow the actual use, not just the model name.

Calibration in Seal is a managed workflow with enforced schedules and point-of-use status. Each asset or equipment type has an approved plan specifying interval or trigger, procedure, standards, ranges, tolerances, uncertainty where applicable, performer qualification, data, review, and status effect. Approaching work generates assignments and escalation. If the due condition is reached without an approved exception, the asset becomes ineligible for the defined uses. If an as-found result is outside tolerance, the asset remains controlled while impact, adjustment or repair, as-left results, prior-use population, and final disposition are assessed. The outcome may link to a deviation, investigation, or CAPA when the quality process requires it.

Equipment cleanliness can depend on product, material, cleaning procedure and version, method, agent lots, parameters, dirty and clean hold times, inspection, samples, results, campaign, and next intended use.

Clean, dirty, cleaning in progress, awaiting result, restricted, and expired-clean states are evaluated alongside calibration and qualification. A current calibration never makes unclean equipment eligible.

Equipment needs more than calibration. It needs preventive maintenance, corrective repairs, and vendor service. Preventive maintenance schedules can be time-based, usage-based, condition-based, or whichever trigger occurs first. Work orders preserve the approved procedure, actual tasks, parts, people, time, observations, test results, exceptions, and signatures. Service contracts, vendor visits, reports, purchase references, and renewal dates remain linked to the asset.

URS, design, installation, operational and performance qualification, protocols, tests, deviations, reports, requirements coverage, accepted ranges, limitations, requalification triggers, periodic review, and release state remain linked to the asset version.

Software, firmware, recipe interface, configurable parameters, alarm and interlock set points, drawings, parts, and connected systems form the controlled configuration baseline. Changes cannot bypass impact and verification.

For a selected date, Seal can show status and location; intended and actual use; configuration; qualification; calibrations; maintenance; cleaning; alarms; batches, samples and results; operator eligibility; deviations; changes; contracts; and retirement state. Every entry is timestamped, attributed, versioned, and linked to its source.

Before a batch step, laboratory test, monitoring event, or other regulated use, Seal evaluates intended use, asset state, location, reservation, qualification, calibration, maintenance, cleaning, configuration, environmental conditions, operator qualification, method or recipe compatibility, restrictions, and effective time.

The decision returns eligible, conditionally eligible, or blocked with the exact rule and evidence. The execution record preserves the decision used at that moment.

Equipment management doesn't exist in isolation. A batch or test can select only assets eligible for the exact intended use; usage links to the execution record; a state change during work becomes an event; and deviations can evaluate the asset history and actual use population. Required operator qualifications are evaluated at selection time rather than reconstructed afterward.

Possible failure onset, measurement function, range and direction, uncertainty, asset use log, samples, results, batches, processes, alarms, products, releases, calibrations, standards, and maintenance history derive a potential population.

Technical evaluation and quality disposition remain distinct. Recalibration of the asset does not itself resolve the effect on prior data or product.

Relocation, component replacement, software or firmware change, repair, range change, new intended use, utility change, interface, method, alarm, supplier, or retirement can trigger qualification, calibration, validation, cleaning, training, document, process, and regulatory assessments.

The approved change defines work, testing, cutover, rollback, release, and verification against the asset's new configuration.

Decontamination, data and record retention, active methods and recipes, spare and component disposition, labels, software and credentials, interfaces, contracts, samples or materials, replacement, removal, destruction, sale or transfer, and final approval form retirement.

Historical usage, state, qualification, calibration, maintenance, deviations, and changes remain retrievable after the physical asset leaves the facility.

Equipment control owns asset identity, intended use, qualification, calibration, cleaning, configuration, usage and point-of-use eligibility. CMMS owns requests, planning, work orders, labor, parts, contractors, breakdown response, return to service, cost and reliability.

Seal can operate both or integrate with an existing maintenance system while retaining one authoritative eligibility decision at execution.

Manufacturer manuals, datasheets, calibration certificates, service records, and legacy inventories can be ingested into proposed equipment attributes, tasks, intervals, specifications, ranges, and history. Every proposed value retains its source location and confidence.

Qualified owners review the changeset, resolve conflicts, and approve the applicable configuration. AI accelerates extraction; it does not establish a calibration interval, tolerance, criticality, or approved maintenance strategy on its own.

Equipment repositories can store specifications, certificates, and schedules. Seal also connects current asset state to the work that wants to use it. That is what prevents an expired, unqualified, unclean, restricted, wrongly configured, reserved, or operator-incompatible asset from becoming part of a regulated record without an accountable decision.