Reference · built on requestOperator by FibricProduction & maintenance

Calibration Due

Finds every instrument due by date or use count and proposes the calibration work order and a swap-in before the station needs it.

Request accessPricing ↗

About

Calibration Due is an operator for instruments that must be calibrated on a date or after a number of uses. It reads the instrument register in IBM Maximo Manage, Fiix, MaintainX, or a sheet, the use counters on the line over OPC UA, and the production schedule from Plex.

For each instrument that is due, it proposes a calibration work order in a window when the station is idle and names the spare from the register to swap in. Where a CMMS meter drives the interval, it proposes the meter reading from the counter it read. You approve each proposal, and each one leaves a receipt.

This is a reference listing. It documents what Fibric would read from Calibration Due and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • The instrument register: Maximo measuring and test equipment assets with owner and status, Fiix Asset records with strSerialNumber and strModel, or a Google Sheets range
  • Use counts from the line: cycle or shot counters read as OPC UA nodes with a sourceTimestamp, or posted as MaintainX or Fiix meter readings
  • Calibration work already scheduled: Fiix ScheduledMaintenance jobs, MaintainX meter triggers and their work order templates, Maximo calibration work orders
  • The production schedule from Plex jobs and job operations, so a calibration is proposed for a window when the instrument is idle
  • As Found and As Left data recorded on Maximo calibration work orders, which Maximo uses to analyze calibration frequency
  • Spare instruments of the same model and range in the register, for a swap-in

Proposed actions

  • Target capability: propose a calibration work order for each instrument due, through Maximo mxapiwodetail, a Fiix AddRequest, or MaintainX POST /workorders
  • Target capability: propose the swap-in: the spare named in the register, the station it goes to, and a status change on both instrument records
  • Target capability: propose a Fiix or MaintainX meter reading on the instrument's asset from the counter it read, so the due date moves with use
  • Target capability: propose a due list per site: instruments past due, due inside the scheduling horizon, and those with no last-calibration date on record

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Open Maximo calibration work orders by use count

    Cycle counters read over OPC UA are compared with each instrument's use limit. For each one due, the operator proposes a work order on mxapiwodetail and a swap-in from the measuring and test equipment register.

    With OPC UA, IBM Maximo Manage

  • Move Fiix due dates with real counts

    The operator proposes a Fiix MeterReading per instrument from the line's counter, so ScheduledMaintenance triggers fire on use, and proposes the work order and a swap when a trigger is reached.

    With OPC UA, Fiix

  • Fit calibrations into the Plex schedule

    Instruments due inside the horizon are matched against Plex jobs at their workcenter. The operator proposes a MaintainX work order timed for a gap between jobs, with the spare named for the swap.

    With Plex, MaintainX

  • Run from a sheet register

    A Google Sheets range holds instrument, model, range, last calibration, and interval. The operator proposes the due list, a MaintainX work order for each, and an appended row when a calibration is recorded.

    With Google Sheets, MaintainX

Requirements

  • A CMMS with instrument records: IBM Maximo Manage, Fiix, or MaintainX, or a register in Google Sheets or Microsoft Excel
  • A use count per instrument where calibration is by use: an OPC UA node, a KEPServerEX tag, or a meter in the CMMS
  • A production schedule source such as Plex jobs, or a calendar you keep in a sheet
  • A calibration interval or use limit per instrument, on the register row or the CMMS record
Authentication
Registers, counters, and schedules are read, and work orders proposed, with the access each connector already holds; no separate account is created for the operator.

Limits

  • A due date is only as good as the last-calibration date on record. An instrument calibrated by a vendor and not updated reads as due
  • MaintainX caps manual meter readings at 10 requests per 24 hours and automated readings at 100 per 60 seconds, so counter posts are batched
  • It does not perform or grade a calibration. As Found and As Left values are entered by the technician on the work order
  • Fiix documents no webhooks, so a completed calibration is seen on the next poll of its work orders

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Calibration Due ↗

Questions and answers

What does the planner approve?
Each work order and each swap. You see the instrument, why it is due (the date or the use count and the reading it came from), the proposed window, and the spare. Approve, change the window or the spare, or dismiss. The CMMS and the register change only after that.
What does the receipt contain?
The work order as the CMMS created it, the counter reading and register row the due call rests on, the swap with both instrument records, who approved it and when, and how to reverse each write.
Does it calibrate or pass an instrument?
No. It schedules. Calibration is done by a technician or a vendor, and the As Found and As Left results are recorded on the work order by the person who did it. The operator reads that record afterwards to reset the due date.
Ask about Calibration Due

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy