Welds

A weld records where two lengths of rail were joined, and how that join was made and verified. Each weld captures the process (the weld type, the conditions at installation, who carried it out) and the outcome, including ultrasonic test results that confirm the join is sound. Welds sit on the rail, so they attach to the assets they relate to and describe the rail strings on either side.

At a glance

• Represents: a rail weld — the join between two rail lengths and how it was made and tested
• Body: a JSON array of weld objects
• Keyed by: id — your external identifier, and the upsert key
• Belongs to: one or more assets, via an assets array (each entry has an assetId)

Tip

The full field list, required vs. optional flags, and a runnable example payload are in the API Reference under Weld Import.

What it represents

A weld captures both how the join was made and whether it is sound. The process fields cover the weld type, joint gap, preheat and tapping times, rail temperature at installation, the welder and machine operator, and the company that did the work. The condition fields cover an ultrasonic test date and result, a condition type, and indicators for special cases such as closure (stress), off-track (field-side), and bow welds.

A weld also describes the rail strings it joins: the rail heading toward the 0 km point (railUp…) and the rail heading away from it (railDown…), along with the rail leg, profile, and rail-height measurements on each side. Removal dates track welds that are temporary or due to be cut out.

Linking to assets

A weld relates to one or more assets through its assets array. Each entry references an asset by the assetId you already imported. It can also carry the shared geolocation concept to pin down exactly where on that asset the weld sits. Because welds reference assets by identifier, import (or define the identifiers for) those assets first — see Assets.

Using it

• Send a non-empty assets array with every weld; each entry must reference a known assetId.
• Keep the weld id stable across imports. Re-importing with an existing id updates the weld in place rather than creating a new one.
• A reference to an assetId the platform doesn’t recognise passes request validation but fails at job time — see Common Errors.