The customers goal is to have a simple RMA process. If a device goes bad... Step 1 - RMA the device. Step 2 - When new device arrives at their processing center (HQs), use existing backup to restore config on new device (SIC, Mgmt IP, Mgmt Server). Step 3 - ship device to remote location and plug into the network (local engineer should not have to log in or access the device at all). Step 4 - confirm connectivity, SIC, policy, traffic passing, etc...
While I realize a ROBO device has the majority of the config (interfaces, routes, etc...) in Smart-Console / Smart-Provisioning ultimately the customer is trying to make the RMA process as seamless as possible. If you have a better solution / process in mind I would appreciate the assist.
Thanks.