Assets
Use a familiar asset tree as an operational model of the physical world around work, ownership, scope, and control.
More than an asset register.
Most industrial systems treat assets as equipment records. Vinkey uses the familiar asset tree as a broader operational model of the physical world around work, from sites, areas, and equipment to vehicles, containers, batches, and inventory.
Familiar tree structure
Start with the asset tree people already understand, but use it to structure the wider physical operation
Asset ownership
Keep every asset anchored to the operational group responsible for it
Asset classes
Use asset classes to model very different physical objects without forcing them into one equipment template
Physical context
Use table, map, and CAD-linked context where exact physical location or scope changes the work
Physical world model
A brief view of how a familiar asset tree becomes an operational model of physical scope, ownership, and context in Vinkey.
Step 01
Model
Use one operational hierarchy to represent sites, equipment, vehicles, containers, batches, and other physical objects.
Step 02
Classify
Use asset classes so different kinds of physical objects behave correctly inside the same model.
Step 03
Assign
Keep each asset anchored to the responsible group so ownership is visible before work starts.
Step 04
Position
Add map or CAD coordinates where teams need to understand the exact physical boundary or location.
Step 05
Scope
Use exact asset or under-this-asset scope to define where work, permits, hazards, and issues apply.
Why this model is different.
Most systems treat asset context as background data. Vinkey uses it as a control layer that defines what exists, who owns it, and exactly where work and supporting controls apply.
Benefit
Keep the familiar tree, expand what it controls
Start from the tree structure teams already understand instead of inventing a new concept
Use the same model for equipment, vehicles, containers, batches, inventory, and other physical objects
Avoid splitting different physical object types across separate masters
Benefit
Turn physical scope into operational control
Link work, permits, deviations, and observations to the exact asset they affect
Filter by the selected asset or everything under it when physical scope matters
Reduce ambiguity when work spans an area, line, vehicle, or nested equipment structure
Benefit
Use classes, ownership, and location as one model
Use hierarchical asset classes to keep very different physical objects structured in one system
Keep ownership visible so every asset stays anchored to the right operational group
Support map, CAD, and future asset status in the same model around the work
Connected around the same work.
These domains are often used together because they operate around the same execution flow.
Go deeper from this product
Relevant articles that connect this product to the wider operational context, evaluation criteria, and practical execution.