A common question I have found especially during mobility deployment project is how support of the mobile devices will be managed and especially how to link up the device provider and its external support framework with an expected rate of device turnover from software failure, broken hardware or shelling. This in turn lead to extensive discussions on guaranteed SLAs for device repair or replacement by the provider and what levels of spare devices should be held and especially by whom - the provider or the customer organization. Finally this whole story is written down within a mobile device support model, including a view of the customer and provider responsibilities and of course one or several contracts detailing out the finances and items like guaranteed time windows when a particular version of a device must be available for shipment.
Showing posts with label ruggedized. Show all posts
Showing posts with label ruggedized. Show all posts
Saturday, 21 June 2014
Halt mobile device turnover rate by placing trust in the individual
A common question I have found especially during mobility deployment project is how support of the mobile devices will be managed and especially how to link up the device provider and its external support framework with an expected rate of device turnover from software failure, broken hardware or shelling. This in turn lead to extensive discussions on guaranteed SLAs for device repair or replacement by the provider and what levels of spare devices should be held and especially by whom - the provider or the customer organization. Finally this whole story is written down within a mobile device support model, including a view of the customer and provider responsibilities and of course one or several contracts detailing out the finances and items like guaranteed time windows when a particular version of a device must be available for shipment. 
Subscribe to:
Posts (Atom)