Introducing Amos often benefit of / require a change in work practice/flow and some customized paperwork to go with it.
When FR first went with it, most of the engineers including seniors and director plus all store personell, parts purchasers and tech records went to Basel in 2 batches for a training course with direct access to all the key developers. Key to success was also dedicated IT support and an engineering onsite superuser under Tech Services handling queries and the communication with supplier. Some of the signed paperwork can also be entered into the system after the fact by a Tech Records department, to free up the time of trained engineers.
Amos also often require dedicted computers/devices to avoid slowdown, since the performance of its graphical interface can be affected by funny screensavers and des like. For new installations, if you think its slow complain, since it should be instant but may require additional configuration and backend settings adjustments.
After that it is just a question of practice, practise and more practise until it becomes routine. It may seem cumbersone at first, transacting everything on the system after first doing them in the real world, but gives good oversight and allow for massive expansion.