FoundryNet / Fields / program_name
Canonical field reference

program_name

The identifier of the part program currently loaded or executing. Carries the join key for almost every downstream analysis: without it, cycle times and load traces cannot be attributed to a part number. Controllers expose it as a filename, an O-number, a comment field, or all three under different tags, and some pad or truncate it.

21OEMs / profiles mapped
43distinct raw spellings
118corpus source tags
1.00match confidence
Get an API key All canonical fields

Vendor tag table

How 21 vendors spell program_name

Each of these is a real tag as the device or controller emits it, taken from the Forge mapping corpus. This is the table that does not exist anywhere else — the reason cross-vendor telemetry is hard is visible in a single column.

OEM / profileRaw tag as the device emits itConfidence
FanucMAINPRG
ONUMBER
PRGNAME
PROGRAM
MAIN PRG
MAIN_PRG
+4 more spellings
1.00
HaasPROGNAME
PROG NAME
Prog_Name
1.00
SiemensPROGRAMM
ACTIVEPROGRAMNAME
1.00
Bridgeportactive_prog1.00
Brotheractive_prog1.00
DMG MoriNCProgram1.00
Doosanactive_prog1.00
HeidenhainactiveProgram1.00
Hitachi Seikiactive_prog1.00
Hurcoactive_prog1.00
Kitamuraactive_prog1.00
Komatsu NTCactive_prog1.00
Makinonc_prog1.00
Matsuuraactive_prog1.00
Mazakmain_program1.00
Mikronactive_prog1.00
Mitsubishiactive_prog1.00
OkumaMainPrg1.00
Siemens SinumerikprogName1.00
Tongtaiactive_prog1.00
Tormachactive_prog1.00
Trumpfactive_prog1.00

Every row above is an exact match — a deterministic pack entry or a confirmed corpus mapping — so all of them carry confidence 1.00. That is not a rounding: these are the two exact-match layers, and a tag that resolves here never reaches the embedding or LLM layers. Mappings resolved by the LLM layer do carry sub-1.0 confidence, but those are per-tenant and are not published here.


Unit contract

What Forge guarantees about the value

The canonical field is not just a name. It is a contract about units, sign convention and plausible range, enforced on the way in and re-checked at read time.

SI / canonical unitunitless (identifier or enumeration)
Measurement typeinstantaneous
Distinct source tags in the corpus118

Normalization

Raw tag in, canonical field out

# Fanuc emits its own spelling; Forge returns the canonical field
curl -s -X POST https://forge.foundrynet.io/v1/normalize \
-H "Authorization: Bearer $FORGE_KEY" \
-H "Content-Type: application/json" \
-d '{"data": {"MAINPRG": 0}, "oem": "fanuc"}'
{ "normalized": { "program_name": 0 }, "match_type": "deterministic", "confidence": 1.0 }

No mapping table to maintain, and no per-vendor branch in your code. The same request shape works for every OEM in the table above.

# Same thing with no key and no account — the sandbox ships the packs
docker run -p 8000:8000 ghcr.io/foundrynet/forge-sandbox

Where this field appears

Protocols

Transports this field is carried on in the corpus.

MTConnect OPC UA

OEMs that map this field

Fanuc Haas Siemens Sinumerik DMG Mori Mazak Okuma Heidenhain Makino Mitsubishi Brother Hurco Doosan Trumpf Bridgeport Hitachi Seiki Kitamura Komatsu NTC Matsuura Mikron Tongtai Tormach
Every one of these tag names is someone’s integration project. The Machine Agent, weekly. Read it →
Get the thesis behind this infrastructure — The Machine Agent, weekly.