Each component must currently be registered as a sub-asset. But not every switch, not every cable, not every viewing window of e.g. a control center is a 'sub-asset'.
Yes, you can define a customized subgrid with system components. But these are then missing in the work order, e.g. throughout the service process.
To replace an battery, a viewing window, an air-filter, and so on should also be charged. If you register all of these components as sub-assets, the customerasset is a confusing bundle of ods and ends.
Comments
@sven, have you checked out the asset properties feature for tracking chemicals? I think it is what you are looking for - https://docs.microsoft.com/en-us/dynamics365/field-service/asset-properties
To the original idea @josef, the way we differenciate is if the asset record has a parent asset, we know it is a sub asset. Can you share some user flows today which could be better with a clearer differentiator of asset and sub asset?
Category: Customer Asset
Perhaps an addition to this idea:
Would it be possible to add an option for GHS related information to the customer assets? I'm thinking about a lot of different chemicals our field service technicians may be exposed at our customers. Maybe linking to a chemicals database and the possibility to allocate the relevant chemicals to the assets and have these information available in the asset view. A combination of up to 25 different chemicals should be possible per asset.
Category: Customer Asset