Assets

If you’re thinking about accessing information from ARDI, you’ll need to know about assets.

Assets represent things of interest in the organisation. Often these are physical pieces of equipment (such as sensors, machines, network switches etc.), but an asset can also represent shifts, crews, departments, people and virtual infrastructure.

Our basic rule-of-thumb is that ‘if it has data and a name, it can be an asset’.

Often, these assets are designed, built and maintained by members of the engineering team.

All assets have several things in common.

Each asset has a name. We encourage people to make sure names are human-readable and easily understood.

We also suggest that asset names should be unique, but this isn't required.

An asset can optionally include a description, detailing what the asset is and what it’s for.

An asset may have one or more Types. These are useful for grouping similar assets together.

Assets can have any number of Properties. These are individual pieces of information about your assets, such as the serial number, status or temperature of a machine.

Assets can have any number of Relationships.

Relationships describe the connections between your assets.

Assets also have media, which are the various types of data file that may be connected to the asset.

These can include drawings, videos, manuals, calibration certificates etc.

Asset Properties