Project data

Quality gate

Required Attributes

Equipment must carry the right data before you raise work — inherited keys, a completeness view, and an optional raise gate. Guidance by default, not a silent block.

Completions work is only as good as the tag it sits on. Required attributes let you declare the keys an equipment type must carry — serial, duty, voltage, whatever the procedure needs — on the hierarchy, then inherit that set down to every linked tag.

Missing or wrong-type values show in the tag editor and on the Tags dashboard completeness view. Import and save still work; the optional project toggle is what blocks activity raise until the required set is complete. The gate is visible, not a surprise.

Declare the keys on the hierarchy

Put the required set on the equipment type or other hierarchy node. Every tag linked to that node inherits the keys. Closest or deepest type hint wins when more than one parent speaks, and conflicts are shown rather than hidden.

Equipment type — required keys inherit from the parent hierarchy.

See completeness, then decide whether to gate raise

The Tags dashboard completeness view is a current snapshot per hierarchy type. When the project enables the raise gate, create and raise against an incomplete tag is blocked on desktop and field. Hierarchy and document targets are not gated — this is a tag-data rule.

Tags dashboard — completeness by hierarchy type.

What it does

  • Define required attribute keys, with optional type hints, on any equipment hierarchy
  • Tags inherit the union of required keys from the hierarchies they belong to
  • See missing values, wrong types, and type conflicts in the tag editor and info panel
  • Required rows appear in the attribute editor and cannot be removed by accident
  • Tags dashboard shows completeness percentage per hierarchy type
  • Optionally block activity raise against a tag until required data is complete
  • The raise gate is a project setting — off by default, enforced in the API when on
  • Works offline on desktop and field with the same domain rules
  • Does not block import or tag save, so onboarding is not frozen for missing fields
  • Keep free labels and extra attributes alongside the required set

Highlights

  • Required keys inherit from equipment type down to the tag
  • Completeness is visible before work is raised
  • Raise gate is optional, not a silent block
  • Six value types: text, number, URL, date, email, phone

Demo

Demo video coming soon

See the rest of the platform, or talk to us about a demo.