# FaciliWorks 8i Calibration — How Gage Management Actually Works

**URL:** <https://forum.cybermetrics.com/t/faciliworks-8i-calibration-how-gage-management-actually-works/109>\
**Category:** Faciliworks 8i\
**Created:** [January 28, 2026, 5:20pm UTC](https://forum.cybermetrics.com/t/faciliworks-8i-calibration-how-gage-management-actually-works/109 "2026-01-28T17:20:01Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![aavila](https://avatars.discourse-cdn.com/v4/letter/a/a6a055/32.png) [@aavila](https://forum.cybermetrics.com/u/aavila)\
**Post date:** [January 28, 2026, 5:20pm UTC](https://forum.cybermetrics.com/t/faciliworks-8i-calibration-how-gage-management-actually-works/109/1 "2026-01-28T17:20:01Z")

</div>

If you’re using **FaciliWorks 8i with Calibration** , you’re not running two systems—you’re running **one asset platform** that treats _facility assets and metrology assets as first-class citizens_.

Here’s how it works in practical terms

* * *

**One Asset System, Two Worlds**

FaciliWorks 8i expands the **Asset module** to include:

- Facility equipment and

- **Gages / measurement instruments**

Every asset can have a **calibration option** , which means:

- No siloed calibration software

- Shared data, shared history, shared reporting

* * *

**The Gages Sub-Tab (Think “Asset Info, But for Metrology”)**

The **Gages sub-tab** functions just like the standard Asset _Information_ tab—but tailored for calibration.

Creating a gage record is intentionally fast:

- You’re not retyping common data

- You’re selecting from a structured database

This design is what enables **rapid, repeatable calibration entry**.

* * *

**Database First, Calibration Second (This Part Matters)**

FaciliWorks 8i is built on a **shared data model**.  
That means **key components must exist before calibration records are created**.

**Recommended data to enter _first_:**

- **Suppliers** (labs, vendors, OEMs)

- **Staff** (internal techs, external providers)

- **Procedures** (internal SOPs, ISO methods, OEM instructions)

- **Standards** (NIST-traceable reference instruments)

- **Gage components** (ranges, resolution, tolerances)

Why this matters:

- Data is reused across multiple gages

- Consistent terminology = cleaner audits

- Faster calibration entry with fewer errors

* * *

**Standards Management (Calibration Backbone)**

Calibration **standards** are entered into the database once and then:

- Assigned to multiple gages

- Referenced during calibration events

- Tracked for traceability and due dates

This supports:

- NIST traceability

- ISO 17025 / ISO 9001 alignment

- Clean audit trails without manual cross-referencing

* * *

**Why This Design Works in the Real World**

- Facility teams don’t need to “learn calibration software”

- Calibration teams don’t lose asset context

- Shared suppliers, staff, and procedures reduce duplication

- Reporting spans **maintenance + calibration** in one system

In short:  
**Good database structure = fast calibrations + clean compliance**

* * *

**Field Question for the Group**

- Do you manage gages inside your CMMS or in a separate system?

- What’s the most painful part of calibration audits for you—traceability, paperwork, or overdue gages?

Drop your experience below.  
Next post: **Calibration Events vs. Work Orders — why FaciliWorks separates them and why that’s a good thing.**