Asset Supervisors

The Asset Supervisor is the primary person responsible for an asset. Asset Supervisors are a very important concept in AssetChief, as they determine how the workflow functions when entering requests.

For regular assets, the Asset Supervisor will be the one who is sent any tasks for work orders that are raised on an asset.

For locations, the Asset Supervisor will be the one who will grant authorization to access the location.

You set the Asset Supervisor in the asset record itself:

You also have to keep in mind the hierarchy of the assets. If an asset is inside an asset group, then the asset itself doesn't need to have a supervisor set. Instead it will take the supervisor defined on the parent group.

Also, if an asset is a sub-item of a location, and the location is set to require authorization to access, then a work order for that asset will create 2 tasks - one to have the location access authorized, and the other the actual task to work on the asset.

The other place that the asset supervisor can be defined is on the Asset Type. If the asset has an Asset Type selected, and it doesn't have a supervisor defined itself, then it will use the Asset Supervisor defined on the Asset Type instead.

Finally, the Asset Supervisor is just one worker you can define. If more are required, you can put those into the Other Workers list under the asset:

For a location, ALL of the users listed in Other Workers (in addition to the Asset Supervisor) will be asked to authorize access. For an asset, the work will be sent to all of the workers to complete. However, this can be limited based on the particular request type. If there's a worker that's set for a particular request type (eg. a work order) then that user (or users) will be chosen to complete the work - and not the Asset Supervisor.