# NC programs

NC program file attachments on jobs — supported formats, parsing behavior, and what is extracted.

Source: https://support.toolingmetrics.com/en/engineering/reference/nc-programs/
Updated: 2026-10-29

**NC Programs** are the CAM-generated machine code files attached to a job. They represent the programming output that will run on the machine. Tooling Metrics can parse attached NC program files to automatically build the job's operations from the T-codes, operation names, and comments found in the file.

NC programs are stored as file attachments on the **Job** — not as standalone documents. Multiple files can be attached to one job (one per setup variation, or one per machine if the job spans multiple programs).

## Supported formats

NC programs are read as plain text. The parser supports standard G-code conventions used by most CAM systems:

- T-code blocks that assign tool numbers (e.g., `T01`, `T1 M6`)
- Operation name comments in standard CAM comment formats (e.g., `;` line comments, `(` block comments `)`)

Proprietary post-processor formats may require mapping before parsing produces correct results.

## Parse NC program

When a file is attached and **Parse Operations from NC Programs** is opened on the job, Tooling Metrics reads the file and extracts:

| Extracted value | How it is used |
|---|---|
| **T-codes** | Populates the **Tool No.** field on a newly built operation row. |
| **Operation names** | Populates the **Name** field on the operation row. Drawn from the comment block preceding the T-code in the NC file. |
| **Comments** | Populates the **Comment** field on the operation row — useful for identifying which Tool Assembly to assign. |

Every parse run builds brand-new operation rows from the file — there is no matching or updating of existing operations by tool number. After parsing, the engineer reviews the generated rows and, for each one, selects the correct **Tool Assembly** and enters the **Est. Cycle Time** (the Tool No. can also be adjusted). No cutting data is assigned during this review; cutting data is configured on the Tool Assembly/Library side, not on the operation.

## Commands

| Command | Description |
|---|---|
| **Attach** | Upload one or more NC program files to the job. Attached through the job's edit form. |
| **Parse Operations from NC Programs** | Open the parse form for an attached NC program and build new operations from its T-codes, names, and comments. Repeat per NC program. |
| **Purge NC Program** | Remove all attached NC program files from the job. |

## Notes

- NC program files are informational attachments — they are not executed or validated by Tooling Metrics.
- Parsing is destructive by default: the **Clear existing operations** toggle on the parse form is checked by default, which removes all of the job's existing operations when you save. Uncheck it if you want the newly parsed operations added alongside the existing ones instead of replacing them.
- Tool numbers assigned by the parser match the T-codes in the NC file. Use **Renumber** on the job's **Tool List** tab if the tool numbering scheme needs adjustment after parsing.
- NC program files are not included in the printed setup sheet.