# How are people handling gage families?

**URL:** <https://forum.cybermetrics.com/t/how-are-people-handling-gage-families/290>\
**Category:** GAGEtrak\
**Tags:** gagetrak\
**Created:** [July 30, 2026, 11:44am UTC](https://forum.cybermetrics.com/t/how-are-people-handling-gage-families/290 "2026-07-30T11:44:01Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![cawatton](https://yyz2.discourse-cdn.com/flex008/user_avatar/forum.cybermetrics.com/cawatton/32/165_2.png) [@cawatton](https://forum.cybermetrics.com/u/cawatton)\
**Post date:** [July 30, 2026, 11:44am UTC](https://forum.cybermetrics.com/t/how-are-people-handling-gage-families/290/1 "2026-07-30T11:44:01Z")

</div>

How are people handling gage families in GageTrak?

Here’s some context: We perform MSA on a schedule; not by individual gage, but by gage families. I want GageTrak to remind me when an MSA study is due for each gage family. For example, we have 30+ calipers that all belong to the gage family calipers. We are only required to do MSA every 6 months on any 1 of these calipers.

How would I set this up in GageTrak?

I already have a plan on how to do this, but I want to see what the forum says first before I share my idea.

---

<div class="post-metadata">

**Author:** ![DaveM](https://yyz2.discourse-cdn.com/flex008/user_avatar/forum.cybermetrics.com/davem/32/136_2.png) [@DaveM](https://forum.cybermetrics.com/u/DaveM)\
**Post date:** [July 30, 2026, 11:59am UTC](https://forum.cybermetrics.com/t/how-are-people-handling-gage-families/290/2 "2026-07-30T11:59:08Z")

</div>

I have ours set up like a gage, so it has a due date that comes up on the calibrations due list.

---

<div class="post-metadata">

**Author:** ![cawatton](https://yyz2.discourse-cdn.com/flex008/user_avatar/forum.cybermetrics.com/cawatton/32/165_2.png) [@cawatton](https://forum.cybermetrics.com/u/cawatton)\
**Post date:** [July 30, 2026, 12:05pm UTC](https://forum.cybermetrics.com/t/how-are-people-handling-gage-families/290/3 "2026-07-30T12:05:31Z")

</div>

So this was my idea too. But with 1 other part.

I plan on making a custom field called gage families and assign each gage to a family. Then creating a new gage for each gage family called something like “Caliper Family MSA”. When I see that in our calibration list, I’ll know to do an MSA study on calipers.

But I’m still willing to hear other people ideas.

---

<div class="post-metadata">

**Author:** ![Angela](https://yyz2.discourse-cdn.com/flex008/user_avatar/forum.cybermetrics.com/angela/32/34_2.png) [@Angela](https://forum.cybermetrics.com/u/Angela)\
**Post date:** [July 30, 2026, 12:22pm UTC](https://forum.cybermetrics.com/t/how-are-people-handling-gage-families/290/4 "2026-07-30T12:22:41Z")

</div>

That is what we do as well for all types of gages. All of our CMM’s are done yearly but I still have a “family of” for auditing purposes.

 ![image](https://canada1.discourse-cdn.com/flex008/uploads/cybermetrics/original/1X/4dadf675e86e56f0e8c345155884612c79a63db0.png)

---

<div class="post-metadata">

**Author:** ![Jeremy\_Dressler](https://avatars.discourse-cdn.com/v4/letter/j/278dde/32.png) [@Jeremy\_Dressler](https://forum.cybermetrics.com/u/Jeremy_Dressler)\
**Post date:** [July 30, 2026, 12:49pm UTC](https://forum.cybermetrics.com/t/how-are-people-handling-gage-families/290/5 "2026-07-30T12:49:27Z")

</div>

We don’t currently do MSA at our facility, however, I would do a phantom gage. The other field you could also use called “Gage Type” to set up gage families like “Caliper” instead of making a custom field. Operating range field in Specifications would let you specify the size of the caliper like 6", 8" etc.