Equipment Calibration: Every Instrument Cleared or Quarantined on Its Own Record

Four dozen instruments, three classes and due dates a day apart

Every month the quality team decides which instruments stay in service. Each gauge, torque wrench and pressure transducer has a class, a calibration interval and a grace window, and its status depends on its own due date and on whether the outside lab's certificate has arrived. Several instruments come due within a day or two of each other, which is exactly where a status gets copied from the wrong row.

The inputs live in different places. The instrument register is an Airtable base, class thresholds sit on a SharePoint procedures list, certificates arrive in the quality mailbox in Outlook, and the second plant, which joined last year, still sends its technicians' notes from Gmail. The coordinator's monthly report is a document in Google Drive, written from all four and checked against none of them.

Who works in the room

The quality team runs one calibration room for both plants. Myco is the default agent, so a message that names no one, such as a supervisor's Slack report of a dropped height gauge, lands with Myco. Questions about visit dates go to Ryan, who owns the lab schedule. When a set of dispositions is approved, Myco opens a thread for Ryan whose first message lists the instruments that need the lab, with their classes and locations, and Ryan leads that thread from there.

A month of calibration decisions, in order

The policy and the allocation rules sit in the cycle folder and in the room guidelines, so all three agents work from the same version. Each step ends with a person.

When the lab moves a date or a reference standard fails

Changes reach the room as email and chat. The lab's scheduler asks to move a visit by three days. A technician recalibrates a bore gauge in-house and sends the result. A correction memo says one calibration record carried the wrong as-found reading. Myco re-runs only the instruments named, writes a one-line note on each record saying what changed, and proposes canceling any lab visit that an in-house recalibration or a fresh certificate has made unnecessary.

A failed reference standard reaches further. When the lab reports that the master set one of its technicians used failed its own recheck, every calibration done with that set is in doubt. Myco lists those records, voids them once the quality manager approves, and sends each instrument back through the policy as if no certificate existed, which usually means quarantine until it is recalibrated. Ryan drafts the single reply the quality manager asked for, with the count and the instrument ids, and the run history keeps every step for the next audit.

What the checks catch

• Two instruments due a day apart, each judged on its own class and due date, never on the row above it
• No reply when a request asks for none, and exactly one reply, on the named thread, when it asks for one
• Voided calibration records followed by a fresh pass through the policy for every instrument they covered
• A lab visit still booked for an instrument that has since been recalibrated in-house
• Close-out counts per class taken from the current table, not from the first pass of the month

What stays with people

• Approving each status and quarantine reason before Airtable changes
• Sending every reply to the lab, which Ryan prepares as an Outlook or Gmail draft
• Deciding what a voided calibration means for parts already made with that instrument
• Signing the monthly compliance summary

Integrations in this workflow

Kylon is not a calibration management system and does not replace one. It sits across the tools the quality team already runs and keeps the coordination between them in one place. The SharePoint and Airtable connections are a lasting grant the quality manager approved for this room, while Ryan drafts mail through the coordinator's own account, checked on every call.

• Airtable
• Gmail
• Google Drive
• Outlook
• SharePoint
• Slack

• Airtable holds the instruments table, the calibration records and the monthly summary rows
• SharePoint keeps the procedures list with each class's interval, grace window and tolerance
• Outlook receives the lab's certificates and carries the visit calendar and the lab's scheduling thread
• Gmail carries the second plant's technician notes, including in-house recalibration results
• Google Drive holds the cycle folder: policy, allocation rules, the draft report and correction memos
• Slack is where line supervisors report a dropped or damaged instrument

Where to start

Pick one plant's instruments and one month. Connect the Airtable base that holds your register, give Myco the SharePoint procedures list, and add an automation that flags any instrument the day its due date passes. Then write the rule that matters most into the room guidelines: agents propose statuses, quarantines and visit dates, and the quality manager approves each one before anything is written or booked.

“Each instrument is judged on its own row, and the lab hears from us once, on the thread that asked.”

Set it up with your agent

Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it.