AX7 in only 10 weeks

Microsoft solutions are popular in Denmark, and the use of Microsoft Dynamics AX (Operations in Dynamics 365) is widespread among Fortune 500 companies. On a Nordic level, we can also witness a widespread use of Microsoft’s ERP solutions.

Most of the solutions are based on the companies’ own IT-infrastructure. This is because they can maintain and run a locally installed solution and therefore live up to the motto “we need to be able to do a lot of it ourselves.”

Now, with Microsoft having released its Cloud- based version of AX; ”The New Microsoft Dynamics AX” (more popularly known as AX7, and from 1st of November 2016: Dynamics 365 for Operations), companies must begin to think differently in relation to the procuring and implementation of a new ERP-platform on this basis.Read More

Most companies follow the traditional approach to getting a new ERP-system. They are typically assisted by external consultants who swear by the importance of knowing requirements and processes, carefully selecting a platform and finding a partner to implement it.

The traditional approach also includes the methods for operation, maintenance and customisation/new features.

The big question is, however, if you should follow the traditional approach when you are to build a business infrastructure that can run and develop the company where it is required to be agile and adaptable, and where the demands for effective processes are ever-growing.

How can you think outside the box?

Most decision makers in companies are familiar with the concept ”Pay- as-you-go” from Apple iTunes, and they have no problem with using their credit card and acquiring an app which makes their daily lives more efficient. The same decision makers might have a basic idea of what they could need an app for, and they accept what the app can and cannot do. In return, they expect an on-going development of new features, and they replace the app with another if it no longer meets their needs.

However, when it comes to a company’s ERP-system, it is a different story.

Microsoft’s new cloud-based AX challenges many of the traditional IT organisations that are based on locally installed solutions with one large annual update or release. The features which are missing in the standard package are often built into the platform based on what tools are available. The same companies are sitting on solutions customised for the requirements of the past, but which find it difficult to keep pace with the constant innovation we see in the market today. Thus, the companies miss out on the opportunity to take advantage of the kind of development that Microsoft provides across its platforms, where new features are continually released 6-12 times per year.Read More

One of our clients in Norway was faced with a challenge: The company’s senior management had made the decision to start a new business concept in order to test it on the market. The requirements were quite simple – to be able to buy and manage inventory and sell it through a POS-system and to be able to receive payments and pay suppliers.

The company had the choice of going with the traditional approach and expanding its current Dynamics AX 2009 platform to meet the requirements of the new business concept. This would mean, however, that the company would quickly find itself having to deal with existing processes that were designed for another kind of business.

As one of the IT department employees put it: ”I’ve been here for so long that I no longer know what is standard AX 2009 and what is our own customisations.” Many IT specialists presumably have the same problem, and will sometimes have to say no to the company’s requested changes, because it would mean fundamental alterations to the IT infrastructure which has been created over a long period of time.
Instead, the company chose an approach where they set a deadline for when the new concept would go live. The processes were based on what a standard cloud-based Microsoft Dynamics AX could provide for an integrated retail solution, covering everything from purchasing, supply chain management, marketing and financial reporting.

When a supplier of IT solutions is faced with such a task, it is important that targets and expectations are agreed upon beforehand. It is also important that, as a customer, one is aiming to ensure that the core processes are supported and not burdened by unnecessary complexity.

Microsoft’s cloud-based solution is different in a number of technical areas, but the major difference is that Microsoft owns the operations part of the product platform and that configuration and installation is delivered through data packages to the production environment.

Also, as you do not have access to the SQL-datase in Azure or access rights to code small scripts that correct faulty data in the system, you need to plan and not at least test the processes and configurations thoroughly, before data is deployed to the production environment.

It is therefore important to test the deployment processes of the data multiple times and to make sure that the test cases clearly reveal that the solution is working as intended. The lack of access to the SQL- database on the supplier and client side prevents using a simple ”backup and restore” between the environments. It therefore must be part of the planning process that such operations are now done through opening a support ticket with Microsoft. Depending on what kind of service level agreement the company has with Microsoft, the backup will be completed within 48 hours or less.

One of the primary pillars of Microsoft’s cloud-based solution and Microsoft’s strategy of ‘cloud first’ across platforms is to ensure an agile environment for the customers, particularly when it comes to new functions and opportunities being more frequently released.

The standard solution offers a lot more today than it used to, and the things which are missing are presumably going to be provided within 3-6 months, as Microsoft continues releasing new features for the platform. This forces companies to think more in terms of solution governance and support and release management, rather than having the internal IT capacity to customise the ERP-platform.

Whereas previously the IT organisation had to make sure that the ERP-platform was stable, that backups were taken and that the infrastructure worked, now it is more a matter of making sure that one has effective ITIL and support ticket processes.

Known bugs and defects in the standard product must now to a much greater extent be reported to Microsoft; this ensures that errors are solved by the supplier of the product and not, as it is now, where many issues are solved by the IT department and thereby potentially bypassing the opportunity to get a fix from Microsoft installed.

Integrated IT is becoming increasingly important for the ability of companies to run an efficient business with LEAN processes. The process owners must to a far greater extent come up with more effective processes using IT, but they are continually provided with information and inspiration for new approaches concurrently with new features being added to the platform.

What might be a burdensome process right now is perhaps solved in a new release 2 months down the road when the ”monthly update” on the AX is released from Microsoft. Release-planning of new features and opportunities therefore become an important part of the process owners’ work.

How did we achieve our goal?

Implementing a new system in 10 weeks is an accomplishment in itself, but it also requires that – as a company – one has the necessary capacity to drive the process forwards, and not least, be ready to accept change.

In the case at hand, the company had the courage to test a new business concept in interior design and housing accessories. The concept was closely related to the existing business model selling furniture, but was markedly different in that one was not dealing with private customer orders, but instead a more traditional cash and carry model.Read More

The implementation itself was kept to a small team consisting of consultants from AlfaPeople who were specialists in retail and standard AX, in addition to a small team from the client’s side with IT architects and infrastructure specialists.

A large part of the effort involved getting a firm grip on the master data, where we had to ensure that we built a structure which solved the immediate requirements, but at the same time, did not limit the opportunity to move the rest of the business over to the new platform.

In the end, it was all about including only the necessary features and finding workarounds for the problems which presented themselves during the course of the project.

One of our key objectives was to carry out the implementation without any adaptations to the system at all, but instead focus on integration and data migrations.

This objective proved itself to be an important factor in reaching our goal. We avoided adding unnecessary complexity during the test and deployment phase during implementation, as this could have contributed to the project not being completed on schedule.

What did we gain from it?

It has definitely been an advantage being able to test the new solution in a small scale setup where we have been through the core processes driving the company. It has also been an advantage that we could carry out this implementation in a standard setup. This again proves what the standard solution is capable of if you are willing to adapt to the specifications. Furthermore, it has made the dialogue with Microsoft Support easier when dealing with the software issues we have had to overcome, since we have not made any customisations that had to be explained to the support staff.Read More

We have certainly gained valuable insights into Microsoft Lifecycle Services, which is the key player in the deployment of solutions and hotfixes for the product. There is no doubt that in the long run, Microsoft is on to something here which compels customers to think in terms of standard solutions and processes. We have been surprised, however, at how much you must consider during the planning stage when you are not directly responsible for the production environments. It adds a bit to the project time estimates, so it is critical that you plan the testing rounds carefully and reserves capacity with Microsoft ahead of time. When doing that, however, everything seems to work just fine.