For Dynamics GP:
Product Development Themes:
- Features: MS Connect tool is the primary way MS decides on new features.
- Technology: Focused almost entirely on ease of hosting
- Companion Apps: Windows 8 apps that allow you to access GP data. Very role centric and incorporate all form factors for devices. Will go beyond windows phone to other device platforms.
- Release schedule: Full client available via browser by end of year. Every half year after that, doing new features with a major release every 24 to 30 months. Business Analyzer rewrite in Q4 2013 including complete rewrite in HTML5 and JS and ability to include MR reports in the Analyzer. With next service pack, can go off domain.
Rapid Start gets a big upgrade with the ability to extract setups from an installation then redeploy the same setting elsewhere. That actually makes the tool useful provided the other bugs are fixed.
For Dynamics SL:
Same product development themes as GP, but very focused on projects, as one would expect, and therefore oriented to mobile. SL will also have a Windows 8 Analyzer style product. They’ll stay on a 2 year release cycle with a mid-cycle Feature Pack release. BA is coming in Q4 2013. UI for mobile (time entry, expense, approvals) in 2013 with web services (Approvals, delegations, resource assignments) in same time frame. CRM Project Connection, Project Multi-Company and Multi-Currency coming in H12014 with SL9 along with Resource Management.
Overall, the roadmap is a bit of a yawner. Not MS’s fault – the products are very mature, very stable and don’t need tons of new stuff. But, after seeing the keynote, these roadmaps seem quaintly retro.
I recently attended an ERP cloud strategy update from MS in which they outlined their next few years of ERP activity vis-à-vis the cloud. Here’s what I heard:
SL: No comments. No surprises there.
NAV2013 is in a TAP program on Azure with several partners and will be the first cloud ERP delivery expected to release in Q1CY2013. This will run on Azure, but the IAAS portion of Azure (in other words, it will be using virtual SQL Servers and Application Servers). It is NOT running on SQL Azure. They will also be releasing the web client which will work either with the Azure release OR with an on-premise release. They are also releasing a Rapid Start tool that uses QA interfaces to do initial configuration – clearly this is a method for making the provisioning as fast as possible. Any customer, regardless of licensing, can move to Azure but would have to pay the cost of the hosting (proc time and storage).
GP 2013 releases Dec 2012 and will be deployed on Azure exactly the same way that NAV is. However, they have done two things to make managing the environment a little easier. First, they have allowed the Dynamics system database to be named anything – this will allow a partner to host multiple versions of GP on a single SQL server. Also, they have developed a web based management console for GP that they say allows easier multi-tenant management. They did not show it but said it was available with the general release. I’ve looked at the Beta release of both the Web Client and the Management console. Rough and not ready for a high volume shop just yet. However, I’ve seen lots of cycle releases on the web client before BETA so I think it will improve fast.
AX is the biggest release change for the cloud. v.next AX moves to the cloud 2014/2015 and will release on Azure BEFORE it releases on-premise. They intend v.next to be delivered exactly like CRM Online (a true multi-tenant app I guess is what they mean by this) and will also offer a Windows 8 native interface. The entire client will be rewritten under HTML5 and JScript so it is platform independent, but will have an app wrapper so it can be delivered in the various app store marketplaces. They also intend to take advantage of tablet features (like camera and GPS).
For lifecycle management, they intend to deliver tools that will allow easier movement of code and data between TEST and PROD. Such will be workflow based so that approval events move data and code rather than people having to do it manually. In addition, they plan to manage data moves (like copying live to test) so that less manual involvement is needed (copy prod to test and eliminate any private data while, at the same time, stop any automatic emails, as an example).
They also intend for upgrades to be far more automatic with customer selecting the timing of the upgrade and allowing customer to automatically upgrade a test environment so they can do their own testing. In addition, they will do upgrades to reduce or eliminate downtime by upgrading snapshots and looking at production differential which, in turn, gets upgraded.
Convergence will be where most of this is announced in more detail and they may try to find early adopter customers at Convergence.
Apparently we will be hearing more Dynamics related messages integrated to the classic Microsoft stack as we go forward. Below is their vision of how this works followed by a stack slide showing where everything fits.
I love the above two messages. I think they are will thought out and definitely position the entire stack more cleanly.
One last note: during QA some people asked questions about ISV support in NAV and GP. The answer was very unclear and was something like “Azure is more vanilla so, if they need lots of ISV’s, they may want to go to a hosting partner”. I can’t interpret that at all, so I’ll keep my ears open.
In an effort not to lose my product chops, I’ve been sticking my nose into a couple of projects (both AX and GP). A couple of posts came out of it that you can find at the IBIS Dynamics Care site or here and here.