FoundryNet / Fields / operating_hours
Canonical field reference

operating_hours

Cumulative powered or running hours. The denominator for almost every reliability metric, and cumulative, so it carries the same reset semantics as part_count. Sources disagree about whether it counts power-on time or spindle-running time; where the distinction is visible the corpus keeps both.

3OEMs / profiles mapped
81distinct raw spellings
227corpus source tags
1.00match confidence
Get an API key All canonical fields

Vendor tag table

How 3 vendors spell operating_hours

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
FanucRUNTIME_h
RUN TIME_h
CUTTIME (h)
CUTTIME_hrs
CUTTIME(min)
Cut Time (h)
+43 more spellings
1.00
HaasTOTAL_HOURS_h
TOTALHOURS(hrs)
TOTAL_HOURS (h)
TOTAL_HOURS [h]
Total Hours (h)
Total Hours [h]
+12 more spellings
1.00
SiemensBetriebsstunden
BETRIEBSSTUNDEN(min)
BETRIEBSSTUNDEN [min]
Betriebsstunden (min)
BETRIEBSSTUNDEN(hours)
BETRIEBSSTUNDEN_minutes
+2 more spellings
1.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 unith
Accepted input unitsdays h min ms s
Converted on ingestdays min ms s → h
Physics bounds0.0 to 1000000000.0 h
Measurement typecumulative — resets are expected; a decrease is a counter reset, not a negative reading
Distinct source tags in the corpus227

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": {"RUNTIME_h": 0}, "oem": "fanuc"}'
{ "normalized": { "operating_hours": 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.

Related fields

Read alongside this one.

spindle_speed_rpm spindle_load_pct program_name part_count feed_rate
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.