SmartView outage when publishing Hierarchies

Summary

Ideas to minimise outage in smartview due to hierarchy changes

Content

Hi

We are a global organization with operations across the globe, this means that we have limited windows of opportunity to update, change or create new hierarchies.  Each time we publish a hierarchy (using the "Process Hierarchy" process) the Essbase cubes are locked for SmartView users preventing them from being able to extract data.  Depending on the changes / adds this could be an hour or more of just processes, during which reporting is "offline".

My question is - how are others in the community governing this, managing the outages - any ideas / best practices - even - quick wins would be appreciated.