The CloudSuite Industrial evidence base contains no fixed-asset or maintenance content at all, so this domain is run as a location exercise, an opening-balance design and a decision about whether maintenance belongs in the ERP.
The CloudSuite Industrial evidence base contains nothing about fixed assets and nothing about maintenance.
D365 divides the asset domain in a way that is worth understanding before discovery, because it shapes the questions to ask.
The location exercise is the first task, and it has to be run as an active search rather than a request.
Whatever the register turns out to be, the target position is designed the same way, and the design is not negotiable.
The consolidation from per-asset settings to governed profiles is the design decision that needs the most stakeholder handling, and it is worth anticipating.
D365 Asset Management provides maintenance assets, work orders, maintenance plans, requests and job scheduling, integrated with production resources and with cost flowing to the general ledger or to projects.
The final connection is to the Posting Engine crosswalk, and it is easy to miss because assets feel like master data.
The evidence base is silent on assets, and the honest response is to say so and then do the work that the silence makes necessary.