Having implemented models that use ALM and models that stay directly deployed, the level of testing and control that you can do with ALM probably outweighs the benefit of being able to do hotfixes instantly. I think there are a few things that are worth considering as you move to implement ALM: Ways of Implementing Model Changes Rolling back a model is required because changes since the last deployed revision tag should not be deployed in the model while in development. What if the changes can be deployed, and therefore you do not need to roll back the model? There are many ways to achieve this, such as: not linking the new build to existing build by formula until they are ready; using a boolean as a switch, and only turning on the new calculation / methodology when you are ready; hiding new dashboards / modules / line items through user access controls UX vs Classic dashboard We are only starting the use the UX, but the flexibility to have titles and texts that are different to the line items are refreshing, as @andrewtye mentioned. Plan ahead If there any settings that needs to be changed on a regular basis, and they are structural in nature, such as role-based access to version, you can plan ahead and create all upcoming changes as revision tags before you start the significant build that would require rollbacks. An example of this is creating revision tags that update access to the Current Version from write to read, then from read to write again. Having said that, with version switchover and current period settings now production data, and the possibility of using Dynamic Cell Access (DCA) as access control, this should no longer be a big issue. Customer Expectation When we first implemented our models we effectively trained our users that all fixes are near instantaneous. The fact that ALM introduces a necessary time delay provide you an opportunity to introduce a Service Level Agreement (SLA) type expectation that is more in line with a complex model. You can of course aim to exceed and delight your customer by delivering quicker that your SLA. I'm sure there will be other considers that are more specific to your situation, and I hope the above helps you to devise a delivery governance structure that works for you.
... View more
