The exchange of the corresponding master and transaction data objects (assets, orders, notifications, etc.) between the individual systems and applications forms the data framework of SAP Asset Manager for the effective use of the mobile solution. This way, employees can access orders and notifications via a worklist and process them accordingly.
It is also possible to view the complete structure of technical assets while moving, in case additional information on adjacent objects is of interest. This frees employees from having to go to stationary devices to find relevant information or carry around a large number of documents or work instructions in paper form.
At the same time, mobile access to documents and job progress also increases the quality and efficiency of asset management since, for example, changed or already completed processes can be viewed. Of course, the functionalities are not limited to accessing orders, notifications, and documents but also include the option of recording measurement information and time confirmations and attaching additional documents from the end device (e.g., a photo of the damage) to the relevant objects and transferring them to the back end. In this way, employees can be informed about pending jobs.
The control of employees for completing individual tasks can be carried out via special roles and the use of Crew Management (optional), whereby the deployment of people and other resources, such as vehicles, can be planned and displayed. With the help of push messages, employees can be provided directly with task-oriented information or instructions. In addition, through integration with the SAP Geo Enablement Framework, map information regarding future deployment locations can also be accessed in the worklist.
A particular highlight of the SAP Asset Manager is certainly its use in offline operation. If performing employees are in locations without sufficient coverage for direct communication to the backend, data can be preloaded so that employees can still perform their tasks. Subsequently, confirmations are synchronized at appropriate intervals when reconnecting to the backend to update data.