Library / WI-215

WI-215 CMM Program Release and Revision Control

WI-215 CMM Program Release and Revision Control

Revision B · Effective 2026-05-18

1 Purpose

This instruction controls how CMM programs are named, stored, proved out, released and revised so that every measurement made on CMM-01 and CMM-02 uses a known, approved program.

2 Scope

Applies to all part programs run on the Bay 4 CMMs, whether written by Tallgrass Quality staff or by a contract CMM programmer. Measurement of first articles with a released program is covered by WI-210.

3 Definitions

  • Program status: every program is in one of four states: Draft, Prove-out, Released or Obsolete.
  • Released: a program that has been proved out on a first article and approved by a Quality Engineer. Only Released programs may be used for FAI or production acceptance.
  • Program name: <PartNumber>_<DrawingRev>_OP<op>_v<n>, for example 48210-3_C_OP20_v2.

4 Responsibilities

  • CMM programmer (Quality Technician or contractor): writes and edits programs, performs prove-out, logs changes on F-215-01.
  • Quality Engineer: reviews prove-out results, approves release, and sets the program to read-only.
  • Contractors: may write and prove out programs but may not approve release. Contractor access to the library requires a Tallgrass account with a sponsor per IT-04.
  • IT Lead: maintains the library permissions requested by the Quality Engineer.

5 Procedure

5.1 Naming

  1. Name every program <PartNumber>_<DrawingRev>_OP<op>_v<n>. The drawing revision is the customer drawing revision letter; OP is the operation number from the traveler at which the inspection is performed; v<n> starts at v1 and increases by one for each change.
  2. A new drawing revision always starts a new program name at v1, even if the program content is copied from the previous revision.

5.2 Storage

  1. All programs are stored in the SharePoint Quality site "CMM Programs" library, in a folder per part number.
  2. Programs may be copied to the CMM PC only for execution. Local copies are deleted at the end of the job; the library copy is the master.
  3. Released programs are set to read-only in the library. Only the Quality Engineer can change a program's status.

5.3 Prove-out

  1. Run the Draft program on a first article that has been soaked per WI-210.
  2. Review the probe path in slow mode for collisions before running at full speed.
  3. Compare at least three characteristics against an independent method (height gage, micrometer or optical comparator). Differences greater than 10% of the tolerance must be investigated before release.
  4. Record prove-out results and the comparison on F-215-01 and set status to Prove-out.

5.4 Release

  1. The Quality Engineer reviews the program against the ballooned drawing, confirms every ballooned characteristic the CMM measures is in the program, and reviews the prove-out record.
  2. On approval, the Quality Engineer signs F-215-01, sets the status to Released and sets the file to read-only.
  3. A program is not Released until both prove-out and Quality Engineer approval are complete.

5.5 Revising a released program

  1. Do not edit a Released program in place. Copy it, increment the version (v2, v3...), and work on the copy as Draft.
  2. Log every change on F-215-01: date, version, description of change, reason, author, and approval.
  3. Repeat prove-out and release per 5.3 and 5.4. The Quality Engineer decides whether the change affects previously reported results and whether re-measurement of any completed FAI is needed.
  4. On release of the new version, set the previous version to Obsolete and move it to the part number's "Obsolete" subfolder. Obsolete programs are not deleted.

5.6 Program errors found in use

If a Released program is found to measure a characteristic incorrectly, stop using it, notify the Quality Engineer, and set it back to Draft. Parts accepted with that program are evaluated by the Quality Engineer; suspect product is held per WI-610.

6 Records

F-215-01 CMM Program Revision Log and Obsolete program versions are quality records retained 10 years from creation (QP-4.2).

7 Revision history

Rev Date Change Approved by
A 2024-09-09 Initial release Ruth Okafor
B 2026-05-18 Program storage moved to SharePoint "CMM Programs" library; added Draft/Prove-out/Released/Obsolete status; contractors may not approve release Ruth Okafor