Microsoft Dynamics AX Today and Tomorrow

Creating a System of Engagement with Microsoft Dynamics AX 2012

Brandon George — Tue, 05 Jun 2012 17:56:00 GMT

Today I wanted to focus this column, around the concept of creating a System of Engagement (SoE) with Microsoft Dynamics AX 2012. This focus spans all user types that make use of Microsoft Dynamics AX 2012. From the basic user of Dynamics AX and all the way to the highest C-level executives within an organization, the goal is to engage.

Exactly what does the term mean system of engagement? To start with semantics, per dictionary.com the word engagement means: "the act of engaging or the state of being engaged" How do we create a system, that puts it's users in the state of being engaged? This is achieved through several efforts, including but not limited to how we approach projects, reporting, business intelligence - as well as social and more!

Though is seems like I just crossed the board on a lot of different topics, in reality what we are trying to achieve in these efforts is to truly create a System of Engagement using Microsoft Dynamics AX 2012. This is the evolution and merging of technologies & concepts that been building through the progression of Microsoft Dynamics AX. The idea, simply put, is to engage the end user - so that what was once just a system of record can truly become a system of engagement. That Microsoft Dynamics AX is more than a new transactional system, but it really engages users through all levels of the organization.

Let’s look at what practically makes up such a System of Engagement, with AX 2012. With this, we must start - in my own thoughts - with a focus around Business Intelligence (BI) and reporting. The reason I state we should focus on the end result, which just BI artifacts as reports, Cue, Role Center pages and more - are for an instance of AX, is that this is the touch point mostly used by end users. They understand executing a report, and getting back information.

Model Drive Approach to AX 2012 Reporting

With the creation of Role Centers, and it's use of web parts and specific reporting elements, including KPI's and others, the evolution of engaging the end user was born. I''ve covered the topic of BI to a good extent myself, from Reporting Architecture, Report Development & Design as well as a dive into the personal BI options with PowerPivot. Further a focus on the BI Semantic Model, and it's impacts for Microsoft Dynamics AX now and the future, as well as a focus on the concept of Queries Elements being a re-usable API for AX 2012.

Code Driven Approach to AX 2012 Reporting

The goal, of such building block post has always been how to make the most use of Microsoft Dynamics AX 2012, to truly engage the user base - to help shape and turn the mindset away from being 'just another transactional system' and truly into a real System of Engagement.

This focus, though needed to create a System of Engagement with AX 2012, is not by itself enough. This is just part of the story, or pieces of the narrative - what has to come into focus around this context so that we understand who and what we are trying to engage, is Workloads & Roles. Any functional or technical scope for a Microsoft Dynamics AX 2012 project must have Workloads & Roles at the center of why such scope even exists. Having this as a foundation, helps set forth everything from creating a functional Map for your BI artifacts, through Role Security modeling and solution scope.

This means, of course the focus on reporting, but also further you can truly then shape your Role Tailored Experiences with Role Centers. You can add social feeds that are relevant by the Roles. You can correctly create everything from Cue's to KPI's, and every reporting aspect in-between that helps meet the real functional scope, as defined when looking at a Microsoft Dynamics AX 2012 project.

To close out this thought process, to enable Microsoft Dynamics AX 2012 to truly become a System of Engagement the focus has to be placed on Workload and Role modeling as part of the implementation. Doing this, with an understanding that the end result is just not a new transactional system at go live - but more than that, the end result is to truly create an engaging, role based user experience - that makes use of all the technologies, and points I have mentioned in this post and more! In short, to create a system of engagement, that has to be the goal on the onset of a project. It has to be the focus of what is trying to be achieved.

I will end with this is just the start of such a topic, or conversation. Such a focus deserves real world examples beyond what I've linked to and stated as well as community contribution. So I open the door to any and all on this topic. And further commit, that I will follow this post with a continued focus on examples for using Microsoft Dynamics AX 2012 to truly create a System of Engagement.

Project Success: From the As Is, To Be and on to deployment

Brandon George — Fri, 24 Feb 2012 13:27:14 GMT

With the release of Microsoft Dynamics AX 2012, came a true generational shift in ERP platforms. Having worked with this release from Microsoft for nearly two years now, I can say that marketing tag line is so much more than fluff, or neatly crafted headline. By far with this product we have seen more net functional adds than in any major release of AX, and actually all previously released major versions combined. Beyond the functional net adds, which is the major focus of any such project, the technical depth, integration with the stack, and changes within the data model bring a whole new level of powerful flexibility that frankly did not exist in the past.

AX 2012 Model Driven Layered Architecture

With all of these great functional and technical changes, the process for reducing customers time-to-value, and helping customers understand the larger picture still remains the same. It's very critical, even more so than ever, to have the right mix of project focused resources, pulling together in order to execute well, in turn being able to deliver for the customer a timely solution, that enables their high level value points, of why they are doing such a project in the first place. With this focus in hand, this means, that it's critical for projects, be that new or upgrades, have the same, repeatable process for implementing applied to the execution of such an undertaking.

Microsoft Sure Step 2012 is that methodology that sets the correct framework, vocabulary & tools for enabling the execution of such goals, as an AX project is meant to enable for an end customer. This includes for any size customer, be that small or multinational organization, and if new implementation, or upgrading is the focus.

Sure Step 2012 Online Image

What we must understand, from a higher level, still needs to be clear at this point. This is being able to map correctly, with the customer their 'As-Is' story, to help set where they are and how they achieve their current process. Moving from that Analysis / Discovery set of processes, the next step from a business process modeling point of view, is creating the 'To-Be' story. This 'To-Be' story should align with higher level value points, that the customer lays out, from the single question, of: "What exactly are you trying to do?"

In the creation go the 'To-Be' story for a customer, generating those business process models, then drives to true GAP Fit Analysis. This combined with the Functional Design of the configuration and setup of AX 2012, for empowering customers end goals, creates the actual project task. Be that functional or technical. Doing this in a very agile way, with a lot of involvement during the modeling process with the customer fully engaged, and taking ownership early on in the project for data, and processes is key for creating true scope.

These are the critical, from a high level of course, steps that enable a project to at least try to be successful when it comes to executing on the true scope, and creating the overall total solution for a customer. Further to this point, it's more and more the case that Microsoft Dynamics AX is just a part of the total solution for a customer, and why it's important to have a Solutions Architect on your project team that can help shape those bigger picture needs, into project reality. Working with many roles through the life of a specific project.

The above, by far is a high level description of the process that I've seen work over the years of implementing AX for customers. Taking the 'As-Is', crafting the 'To-Be' to target the customers high value points, to create a true plan of execution that will take a customer from project start to deployment and use. There are so many different roles, and parts that have to come together for successful ERP projects, and understanding why a project is being attempted, from the customer to the implementation part is the critical path, to allow a project the chance to succeed.

I hope, for anyone reading this article, that you can take this and either nod your head in agreement, as your well into this thought process, or your able to use this as a launching board to ask those big picture questions, and align yourself correctly to enable true project success. A successful project, is one that meets the customers value points for attempting the project, which is simple terms means you've added value to the customer by completing such journey with them.

Let me end, with this is the first in a series that I plan on continued focus here at the Microsoft Dynamics Community Site. A focus around Project Success, and how this is enabled, executed and repeated. This, by far, I believe is a critical topics, and so each month I will dive deeper and deeper into this area of Project Success. With that, my next focus for this series is around "Learn from the past", which will be a focus on points that we have seen make a project derail and go bad. The idea, is not specific project examples, but common threads, that can help develop early warning signs. It's always been a great learning tool, understanding what does not work, and ERP Project's are no different than any other topic.

Is Microsoft too Late to the Tablet & Mobile Game?

Brandon George — Thu, 12 Jan 2012 01:39:00 GMT

To answer the title of this entry, directly and promptly, from my point-of-view, No! Microsoft is not too late, and in fact I believe that the Win8 Tablets, and the Windows Phone will become a standard in both device types. I realize, that typically I focus on Microsoft Dynamics, and you could then ask, why this article on the Dynamics Community site? Simply put, Mobile ERP already is trending heavily for a topic of focus for most companies, and that will continue in 2012 and beyond. To this fact, it's important to understand what this means for the Dynamics Ecosystem.

Without a doubt, we can't speak to tablets without saying something about the current top player, Apple and it's iPad. I'm a current user myself, and for sure Apple has found a spot among the masses for this device type. Further Apple and Google with it's Android devices, have shifted the smart phone / mobile device landscape, and will for sure continue to be top players in the space. With that said however, Microsoft, the perceived "sleeping giant", in this space, is far from resting in sweet slumber.

To talk to the first point of why I believe Microsoft will come out a dominant force on the mobile front, we need to focus first on the efforts, and focus around Windows 8, and the WinRT platform, as well as the Windows Phone front and the Metro style user experience.

It is without a doubt, a lot of focus has been placed around this new platform, and the vision of "three screens and a cloud" is finally coming to light. With this focus, and the "all in" cloud movement that is sweeping across every single product team for Microsoft, the ability to create applications, and make use of applications via cloud based utility computing from Azure, will empower a massive uptake in the adoption and use of Windows 8 Tables, PC's and Phones for businesses world wide.

With this in mind, how does this play into Dynamics ERP? Simply put, the Mobile ERP movement that will take full focus for this year, and set firm into 2013, will drive the use of Win8 devices, and create the Microsoft Dynamics "Any Device" ERP. Companies that are Microsoft based shops like developing with Microsoft technologies, because they can get what they need, when they need it, without having to worry about the "walled garden" that exist in the Apple ecosystem. The heart of such moves, Microsoft Dynamics AX will be right there, along with technologies like Visual Studio, as well as "LightSwitch" and it's ability to enable companies to create Line-Of-Business (LOB) Apps.

Through such technologies, and the need to provide "Any Device ERP", as well as the fact that Microsoft continues to use Microsoft Dynamics AX as it's Locus of Innovation, Microsoft is far from being declared to little to late, instead, the champion of business software will bring the game to a new level, and one that we will see companies welcome, embrace, and in my own words, what companies have been waiting for. There are so many great technologies, that help enable mobile ERP for Dynamics AX, one that I have personally worked with and implemented in DynamicsAnywhere. It's just an example of how even the ISV community, that works within the Dynamics Ecosystem is helping make my prediction, already yesterday's news.

So if your looking for a solid bet on the future, bet on Microsoft, Windows 8, and of course the Microsoft Locus of Innovation, Microsoft Dynamics AX!

To my Brothers & Sisters in Arms

Brandon George — Thu, 08 Dec 2011 16:53:00 GMT

In this months column piece, I thought I would use my time and dedicate this post to all those brave souls out in the big Dynamics Ecosystem of a world, who fight the good fight day in and day out for thier customers.

This is not just limited to the everday Consultants, no this is to all the Great support staff, to the partner organizations, as well as Microsoft, and the top of that list is the customer resources themselves.

We all press towards the mark, working later hours, and long weekends. Analysis, Design, Development, and the like. From Standard Operation Procedures, to being live for many years and focusing on an upgrade path. Each and all of you, are, Brothers and Sisters in Arms. Giving up your own personal time, for a greater tomorrow. Focusing on driving the most value you can, for your customer, or being the customer for your company as a whole.

Few understand, and have braved the challanges of an ERP or CRM project. Over the years, the technology and functionality continues to grow, but the main ingrident of success, that is steady, firm and will always be the case, is the people.

The people that make up these projects, that raise the hard Why's, and the stern No's. They push towards a more connected, and easily adaptable, Dynamic business solution. It's an "all in" mentality, that takes a lot of work, and so much focus, energy, experience, gut and grit.

It's a hard thing, no doubt about it, and it's not the technology that is the hardest aspect. That, you can always trace down, and come to a 1 or a 0, in it's basic form. The grey area, that area in which real life exists, and there are a lot more answers than just 1's and 0's, that is the area of true success, or failure. This is where the people are, and life intersects with business, and technology.

The coming together of ego's, or minds, or persona's. The dive to understand something, that's brand new, and be brave to take on the challange, that might actually change how you think about something, or some process.

To the Social Media "Dukes of Dynamics", you champions of knowledge. For the continued drive to share what you have learned, and doing so expecting only shared knowledge back in return for your time. You help continue the foster of growth, and information that is vital for this Ecosystem itself, to be truly called "Dynamic".

This post, is dedicated to all of you, who make up the Ecosystem. You should all pat yourself on the back and may you be blessed this Holiday seasion, may you spend time with your families and loved ones a little more than planned. May you have a Merry Christmas, and a Happy New Year!

The Value of a Partner

Brandon George — Mon, 03 Oct 2011 10:50:51 GMT

With the release of Microsoft Dynamics AX 2012, there is a lot of excitement around all that it offers. This is a huge leap in ERP technology, and what value it as a business solution can bring to an end customer's business. Out-of-the-box, there are more new net changes than in all the previous major releases of AX combined. With that fact in hand, I think it's important for customers to understand one of the key factors for a successful AX 2012 implementation. A cornerstone, to any such ERP project. What I'm speaking about is the value a partner brings, for such projects.

Dynamics AX 2012 projects are business focused projects, that are enabled by technology. A good partner should not only understand and be experts at the technology that enables this great solution, but more the real value that the partner ecosystem brings is in vertical knowledge. This is the key to driving value out of such projects, and why it's critical that a good partner always be used. It's never recommended a company go at this process alone. There are several reasons why, and a few of those are as follows.

First, as I mentioned above, vertical knowledge, or understanding the business you operate. This means having experience were it counts, within the type of industry you and your company live and work in daily. Someone once said, "if your to close to the problem, it's hard to see the solution." This is even more true, when it comes to such projects as an ERP / SCM project. Time and time again, I've see where working as a part of a VAR, with a great team of consultants, helps drive real value out of these projects. This includes being able to be a second party, compared to the company, and push the company to make real decisions based on value. The asking of why, and the applying of years of experience for processes for driving to the most flexible, dynamic business aspects for an end customer. This vertical knowledge is key and the most important aspect of what makes a good partner, and what helps drive value for such projects.

Second, this concept of an outside party, which in turn enables new eyes, and new ways of thinking about how things can be done, vs. how things are done. You see, ERP projects are akin to marriages, in that there is the courting process, the getting to know you, the digging in, the good arguments that lead to real value, the continued drive to work together for a better tomorrow, and finally the celebration of going live after all that effort and hard work. Having this second party, that can take the technology, that can take vertically specific domain knowledge, along with the customers needs and drive to the best ROI is a very critical part, and very much a part of the value in which a partner brings.

Finally, we have the technology aspect, and I hope the point is clear this is listed last in line. It's very, important this point - no doubt about it. However this is less the critical path, than the vertical knowledge and years of such project experience that a partner brings. To often I've seen companies try to approach an ERP project, from a technical point of view. There are technical needs, however the project should be driven from a business requirements, and therefore business aspect needs. Still, with that stated, technology is what enables this solution. Therefore it is critical that a good partner understand the technology that is used, so that when the real business requirements ate finally meet, then the technology can be used in such a manner that further drives value, with the least amount of modifications. Understanding the technology, can also lend to helping understanding options of further value, or possibilities that did not previously exists, that come with the new technology. Such things as looking at BI in a different fashion, and being able to quickly and with much more degree of flexibility have true interop between the solution and the outside world around it.

A good partner, is key to the success of a Dynamics AX project, and this will always be the case, no matter how the technology changes, or what it might can enable. These are business projects, vertical knowledge is required to understand and drive the most value for a customer. There is so much more that I could talk to know about the value a partner brings, however I think the above helps introduce, at a high level, why it's important today, as well as it will be important tomorrow in using partners to have successful Microsoft Dynamics AX implementations.

That's all for now, till next month!

Master Data Management & Microsoft Dynamics AX 2012

Brandon George — Mon, 29 Aug 2011 17:15:00 GMT

One of the more interesting concepts that has really gotten a boost, with native support in Microsoft Dynamics AX 2012, is around the Master Data Mangement (MDM). This is not a new business domain issue, it's been around for sometime, however there are some great new features about Microsoft Dynamics AX 2012, that enable native master data management concepts within the application itself.

Some of these area's include Product Data Management (PDM) / Product Information Management (PIM), Chart of Accounts, Number Sequences, etc. These have elements to them now, where data lives at the instance level, vs. just at the legal entity, or company level.

Because of this fact, now within AX 2012, exists the ability to Manage global product data including very nice hierarchies. These products can then be released into a specific legal entity or company for use to buy, sale and make for the given products / items. The term item, is actually replaced at the product information management module, with 'Released Products'.

These product information concepts are covered very well, in the following series of post, located here:

-Product Management with Microsoft Dynamics AX 2012 - Part I

-Product Management with Microsoft Dynamics AX 2012 - Part II

-Product Management with Microsoft Dynamics AX 2012 - Part III

-Product Management with Microsoft Dynamics AX 2012 - Part IV

With this information, one would ask then about the use of Microsoft SQL Server - Master Data Services, and AX 2012. This is a valid line of thought, as it's a new technical solution, to help possible resolve business domain issues around management of master data.

We have to take a step back however, at this point, and why I think it's important to understand the nature of Microsoft Dynamics AX 2012 projects, in that they are business projects, and not technical projects. I will refer back to my previous article of this column, "Just because you can, doesn't mean you should".

So, in order to understand where a technology like Master Data Services fits into a possible Microsoft Dynamics AX 2012 project, we need to look at value, and then context. What do I mean by these terms? Well if you are taking, and the end result is a company wide, single instance of Microsoft Dynamics AX 2012, replacing alot of your companies current line of business (LOB) applications, then adding the complexity that can come with an MDS deployment looses a lot of value. The reason this is relates to the second point about context.

The context for this given example, is AX 2012 is the System of Record and System of Entry for your Master data elements. Since that is the case, there is very little business value for adding a layer of complexity to your overall solution, with a technology like Master Data Services. AX 2012 can handle all of your Master Data Management (MDM) needs, and so that sets our context for the value in this example.

Moving forward, what if we say Microsoft Dynamics AX 2012 is going to exists in a tiered, or two tier environment? Where, AX 2012 is then used as a divison level, or does not exists within a single instance, but multiple instance level. This then means, that there is a not a single instance of AX 2012 that is acting truly as the System of Record for master data. Since that is our context, we can look to the possible use of Master Data Services, as it's potential for adding value has increased.

In this example, AX 2012 is a spoke, in the hub-and-spoke concept, or again tiered concept, where as a company is having to manage, as part of their total solution, multiple line of business applications, that Microsoft Dynamics AX 2012 is a part of. When this is the case, then we still have to look at where the System of Entry for each type of Master Data entity will be, and truly what is meant to be the System of Record.

So we still need to define further context, to determine the value of adding Master Data Services to resolve business domain issues, relating to having a single Master, for say Products, that all subscribers work from. The arguement, still, can be made that AX 2012 have the capability of being that System of Record, with it's rich new features around Master Data Management concepts.

However, again, when the business requirements define, that a single System of record needs to exists, for all line of business applications, and we have the context of the hub and spoke, or tiered environment, again the value of Master Data Services, and what it offers rises as a possible solution.

I will caution, that when the context and value point to using a solution, like Master Data Services is reached, that type of project, the Master Data Management project, can be massive in itself. There is a lot to agree upon, understand, map and translate to, data stewards, data owners and governing business rules to decide upon. All of which affects publishers and subscribers within this given part of a solution.

I will finish with this fact, that for any Master Data Management project, that involves ERP related business data, the solution is only 20%, and human workflow is still 80%. Someone has to take and make a business decision. Trying to write endless rules, that make an attempt to streamline this, seems to only add to the complexity of such a project, when the end true value could have been an alert to the right party, so a decision by the data owner and data stewards can be made.

If your interested in understand Master Data Services better, I actually started a LinkedIn group on this topic last year, that is gaining in it's members, who have shared with the group some great stories in which they have used Master Data Services, to enable value add to their companies or respective clients. You can find out more about that group here: SQL Server Master Data Services Group on LinkedIn

Well that's all for now, till next month!

Just because you can, doesn't mean you should

Brandon George — Fri, 29 Jul 2011 16:20:00 GMT

With the release of Microsoft Dynamics AX 2012 coming very soon, there is a lot of great new technical abilities that will exist. There is a slew of articles, blog post, etc. that cover some of these topics, from Services, to Reporting, to the Model Driven Layered Architecture (MDLA), and so on.

With this, and being a techie at heart, I'm super excited about all the great possibilities that exists. This includes, with all the great features, and choices even within X++ and the use of Eventing, as well as the choice in development with what can now be done with .Net / C#. This represents new ways to solve business domain issues, and opens the door to implement some great, in theory, new features and practices. Now with this said, we have to take a step back, take a deep breath, and realize, that we are still working in the ERP / SCM domain.

The goal then, for such software, is always to solve business domain issues for companies, and the underlying driving factor is to drive value. This is the only reason we should ever do something, to drive business value. So as the post title states "Just because you can, doesn't mean you should", really has to be applied to implementations. This has always been the case really, and still will be the case for AX 2012. I think its easy to get caught up in making technical decisions, that might be very elegant solutions, that in the end though, does not drive true, best value and ROI for the cost of doing such designs.

One story, that I know most any ERP or CRM consultant tells, and has been through if they have been in the game long enough, is around replacing older, legacy systems. In this process, there is always requirements gathering, and GAP analysis that takes place. During that, we as the partners and consultants run into the 'Well in our old system, we only had to press one button to do 'X', and in AX you have to press, in this example for simplicity sake, two buttons to achieve the same end result.'

Now, if there is truly a valid business case, that AX should be customized to have that easy button, and weighted ROI can be shown, then fine, that's what should drive such custom scope. However, most likely the cost in real dollars to create the new custom scope, for enabling such an easy button, and then the weight of having that as 'just one more thing' to maintain, does not typically justify the ROI for such an effort. And in reality, the process might be better suited, as designed, without moving forward with the customization. If this is true, then the correct action, is to update the companies process, and have the persons role no longer have an easy button. Instead have two easy clicks, from our point!

Obvious this is very simple, in comparison to what a lot of scope looks like. The idea is the point, not the example. The idea, and the vision, and driving force behind any scope of any project relating to Microsoft Dynamics AX 2012, should always be driven by functional design, and true business requirements, that drive bottom line value to the company that will be using AX.

So, it's exciting that we are on the verge of such a great new release of Microsoft Dynamics AX, and there is such much to look forward too. Microsoft has really done a great job, still the burden of correct use, correct implementation, falls upon the shoulders of the Partner Ecosystem, and the Customer, in a joint effort to deliver true value for it's use.

I will end, with something I start a lot of project kick offs with, one of the greatest things about Microsoft Dynamics AX is that you can change almost anything about it. This happens enable one of the worst things about Dynamics AX at the same time, you can change almost anything about it! Not to say I think there is anything bad at all with Microsoft Dynamics AX. It's meant to be Dynamic, as the name implies. It's also not to say it cant be done, for whatever 'it' may be. Heck I can integrate Dynamics AX into anything, including to working your business lights, with the right automation tools, development time and dollars. But does it make sense to do so? Or is the better value, is to still allow your employee's to use the good old light switch to perform this action?

I hope the point is made, step back to look at the problem or, business domain issue, at hand to see why that may exists, before jumping right into a solution, that might not be needed. That's all for now, till next month!

Making the most of Microsoft Dynamics Convergence 2011

Brandon George — Thu, 07 Apr 2011 18:55:10 GMT

Convergence will kick off in just a few days time, and a lot of people are getting ready. This is the great Microsoft Dynamics "Yearly Ball", in which a parade of people, vendors, customers and Microsoft themselves come together to share and connect, driven by all things Microsoft Dynamics.

There is going to be a lot of news, as Microsoft Dynamics as a whole is seeing a lot of product launches this year, including Microsoft Dynamics AX 2012. As part of this coverage, there will also be plenty of talk around Microsoft Dynamics Cloud ERP, how it exists now, how it will exists, and what it will end up looking like. By far this Convergence is set to be one of the biggest yet, with the most impact, and most changes taking place in the Ecosystem.

With all the headline coverages, there is also important items that should be understood, and as my President, John Pence, of Sunrise Technologies, Inc. (www.sunriseconsult.com) pointed out, Self-Service BI is a topic that should be understood, followed, and that might not get the highlights as other hot topics, but one that customers need to make sure they check into. The reason this is, is that self-service BI offers a true business value add for a customer inevested into Microsoft Dynamics ERP.

Some of the Microsoft Dynamics AX 2012 coverage will show off this, with the sessions on Microsoft PowerPivot and it use with Microsoft Dynamics AX 2012. I having been writing about this specifically for a little while now, with my latest article found here.: Microsoft Dynamics AX 2012 and the importance of PowerPivot This mixed with Report Builder v3.0 from SQL Server 2008 R2, along with other BI ISV offerings, means true self-service BI is a reality, today with Microsoft Dynamics AX.

There are also other topics that should be considered important, if your a customer, making sure you connect with your VAR, as well as any other ISV products you make use of. Attend AXUG birds of a feather sessions, and connect with fellow peers, in similar businesses and verticals. Make sure to take time, and booth hop, checking out the different offerings that exists from so many different Microsoft Partners, that could help you maximize your Dynamics ROI. Finally, make sure to have fun, and enjoy connecting with people, share, laugh and smile!

For sure Microsoft Dynamics Convergence 2011 is going to be jamed packed with all kinds of information, and really to much for one person to take in everything. Make sure, as a customer, you have a game plan of areas that are a must for you, and then leave room for ad-hoc sessions to join, or meetings to take place. Also make sure to keep an eye on the twitter hash tag: #CONV11 as there will be plenty of coverage for this event, following through the social site, along with blogs alike. Post convergence, take the time to sift through all those business cards, and follow up emails, and prioritize the area's in which you and your company want, or need to focus on.

I did a small social expertiment on twitter, and asked for those excited to say one word about what they are most excited about. The majority of people stated: Connecting! That's the whole point of Convegerence, so make sure you take the time, connect, and enjoy! I hope to see you there!

To Upgrade or Not To Upgrade. Is that the Question?

Brandon George — Wed, 23 Feb 2011 19:44:00 GMT

I hope that I have set the mood correctly for this month’s article, in that the focus will be upgrading. And not from the technical aspects of upgrading, what it takes to perform an upgrade. No this is more on the focus of upgrading for Microsoft Dynamics AX, and what path should be taken in regard to Microsoft Dynamics AX 2009 vs. Microsoft Dynamics AX 2012.

When we think of upgrading, a lot of time we can easily get lost in the technical aspects of what all specific planning, and new technologies that come along with an upgrade choice. This is looking at AX as if it were any other piece of technology or software.

However, we can not look at ERP / SCM / CRM software through technology colored eyes. We never upgrade for technologies sake, unless that technology enables the addressing of a business process, or business domain issue for a company.

See that is the real upgrade driver is business domain issues for a given client. To this end, we must then look at the two options that exists for current customers of Microsoft Dynamics AX.

With all technical pre-requisites aside, let us look at what each version solves from a functional and therefore business domain level. This is how you must decide on if upgrading now to Microsoft Dynamics AX 2009 is the right choice, or waiting until Microsoft Dynamics AX 2012 is released close to the latter part of this year.

Looking at this, each company would have a different correct and right answer in question of upgrading. For a company that needs AX for Retail now, would like to have their Dynamics CRM Online investment integrated with AX, and also the functional gaps that exist today are mostly addressed with AX 2009 stable offering, then what’s the right answer? Microsoft Dynamics AX 2009.

However, if a client is in, say the public sector and in their current investment of AX there is a lot of custom code, that could be replaced with out-of-the-box functionality from what we have been publicly told will exist in Microsoft Dynamics AX 2012, then what’s the right answer? Investigate further Microsoft Dynamics AX 2012, and then most likely that is your correct answer.

To sum this point up, there is no cookie cutter, fits all, if a then AX 2009 else if b then AX 2012. That’s not the nature of Microsoft Dynamics AX anyway. No, the correct answer, for you and your company can only been seen when looking at the business domain issues that exists for you, and how those fit with what can currently be done with the stable version of Microsoft Dynamics AX 2009, or what is currently known to exists in the to be released Microsoft Dynamics AX 2012.

Being a technologist, it’s sometimes easy to get carried away with all the cool and neat things that come with the latest and greatest. However, being a ERP / SCM / CRM / PLM focused Architect, I must keep in front of me the real reason we are deploying Microsoft Dynamics AX for any customer. That reason is, to drive value through improved management of data and processes.

So what’s the right answer for you? Need help deciding? Get involved with looking at this now, talk with your Partner. Have them help you with looking and this, and leading to the right choice so that you can maximize your Microsoft Dynamics AX investment.

That’s all for now, till next time!

When to introduce Convergence, AXUG & MSDW Decisions to a new Client

Brandon George — Mon, 17 Jan 2011 19:13:42 GMT

One of the first things I try to do, when starting a new Microsoft Dynamics AX project for a client, is to introduce them to Convergence as well as AXUG membership. A lot might have already heard of these, and might have attended a Convergence. However, it seems that once the project starts, or the project is over, the value of continued investment into attending events like Convergence, AXUG Summit, AXUG Regional Chapters seems to get lost in the shuffle of being live with a customers new implementation.

Continued interaction, and attendance at Convergence, AXUG and the MSDW Decisions Virtual Conferences is very much an investment in time and resources, that help extend and squeeze the most ROI for a given customers choice of deploying Microsoft Dynamics AX.

As I sit here, on the heels of the kick off for #DAXCONF 2011, it very clear that there is so much to be gained from theses events. Having attending several different events now, spanning the aboved mentioned and the face to face interactions that take place, exchanging of ideas over breakfest, gaining insight into product depth and area's that maybe a person did not know AX was used in a given fashion. All of this builds into getting the most out of a customers Microsoft Dynamics AX investment.

So, as the title states, you should tell the client about these great resources during the sales cycle, as well as the project starts. And continue to reference them as sources throughout the project. Point them to the Official Microsoft Dynamics Community site, in which this article is being hosted on. Talk to them about the value of joining AXUG, and becoming an active member in the regional and national events. These help the company grow in knowledge and in AX strength, given the company the ability to get the most for what they are investing.

That's all for now, I will actually have another article this month on my column, coming out of this weeks #DAXCONF, so keep an eye out for it, and keep pushing the gears that help the Dynamics Community and Ecosystem grow: Convergence, AXUG, MSDynamicsWorld.com and the Official Dynamics Community Site!

The Value of Upgrading

Brandon George — Fri, 19 Nov 2010 14:33:00 GMT

When looking at an investment, like the one you took when you chose to go with Microsoft Dynamics AX as your ERP / SCM platform. You want to see ways to increase the ROI that you have placed into this technology.

As a company you have spent dollars, man hours, time training, maybe changing your culture even to adapt to new ways of doing business. So to say the least, you have a lot into this thing. With the investment that has been made, it is then a top priority for you and your company to get the most out of it!

When you target things, there is always short term as well as long term goals. Being that the majority of ERP choices last a company on average Ten years, it would make sense that long term returns on the cost would be targeted. Sometimes however, as part of this long term focus, to many times I see companies not actively targeting upgrades as part of that return.

A lot of times, it's seen as a static hit, vs something that is actually very dynamic. And in staying up on the correct upgrade cycle, well help your company take full advantage of what all comes as part of the choice of hainvg Dynamics AX.

As we approach the new year with AX 6 on the horizon, and looking at two years being out of RTM for AX 2009, it's time to look at this long term on-going return for your companies choice in Dynamics AX. In looking at upgrades, you get a lot from staying on a good cycle. Take a look at the following list.:

Latest Bug Fixes
Performance Improvements
Functionality / Enablement

These are the three real buckets I classify upgrade ROI in. I put functionality and enablement together in the same bucket on purposes. Reason being, you take AX 2009 with SP1, RU5, and KB article 2278963. Mouth full I know, but with this, AX 2009 is then certified to work with MOSS 2010. This is an enablement, that offers new funtionality through enabling technology to be used with AX 2009.

You can read more details about the benefits of MOSS 2010 and AX 2009, by going here.: MSDW: Dynamics AX Team Announces Microsoft SharePoint 2010 Compatibiltiy with AX 2009 SP1

Speaking of Functionality adds, these could be things from localizations, to specific functions within a give module inside Dynamics AX. Though typically maJor adds of functionality sit at the major release cycles, some do take place during service packs and release candidates.

So what is a good upgrade cycle?

Every other Major Release
Latest Service Pack
Latest RU, when issues are being faced

Simple right? You would think so, but to often companies don't have this as part of their monthly and qaurterly updates. If these were part of those updates, then proper planning of resources, and budget could be done that would help pull the most return out of a given Dynamics AX install base for a company. The whole idea of ROI on this front is getting the most, out of the lifespan of your Dynamics AX instance. This includes many, many factors that help update the core of AX, and also help enable and extend AX through the rest of your Enterprise.

In the end, if looked at correctly, a greater ROI can be had from staying current and keeping up to date. The cost to continue to be dynamic as a company is reduced drastically, and your ability to be dynamic is ever increased when doing so. I will add one last thing, in that there might be a solid reason for a company that is on the latest major to upgrade to the next released major version of AX. There should be however calculated return for doing so. There should be known returns, that will help the company increase in performance, scale, ability or function.

Make sure to keep an eye out for more details starting next year about Microsoft Dynamics AX '6'. A lot of great information will be coming out of the Dynamics AX Technical Conference 2011!

AXUG Summit was a huge hit!

Brandon George — Tue, 26 Oct 2010 17:32:10 GMT

Well I am back at home, back to normal work life after attending a great AXUG Summit down in Orlando. There was so many great sessions, topics, connections and sharing. It seemed as those this years theme for AXUG was "Get the most out of AX, Extend AX and the Future version on the horizon".

The whole thing started off with a keynote speech from Major General Visot. HOOAH! It was a great speech, and what a wonderful person to meet. It will always stand out to me, one of the beliefs he lives by is that every human being we meet has value. This is a thought, a phrase, that every single one of us should carry around and keep with us at all times.

After the keynote is when AXUG Summit kicked into high gear. There were all kinds, of great sessions, and during that next time block, I attended a great AX performance tips and tricks session. This session made sure to really touch on where performance lives in an AX implementation, and that is around SQL Server, and AX interacting with the SQL Relational Database. After that, I actually headed up a session, EXE02 - "Cloud computing, what is it and is my company ready?"

This session was well attended, and geared at the executive level dive into what cloud computing is today, what's not cloud computing, and getting companies to think about if their company is ready for cloud computing or not. The details of this session will be a part of a webinar soon from AXUG, and also you can get the presentation I created at the AXUG.com site. The high level, I broke the cloud into the four real segments.: SaaS, IaaS, PaaS and Personal Cloud Services (PCS). Some great comments, questions, and good to see the interest level in this.

After this there was time at the Expo, and myself working the Sunrise booth some, meeting with our existing customers and some prospects to become Sunrise customers. This lead right into drinks and Sunrise Customer event. We actually had a lot of customers attend AXUG and also the customer dinner at Trade winds. If your down at Sea World, it's a great place to eat. The service was great, and all the customers had a great time. At this point, we basically concluded Tues. I will mention though, and this is one of the things that makes AXUG great, is that I was walking back to my room. In doing so, I had to cross the central bar area, and plenty of AXUG people were attending. I sat with Kris and others from Dent Supply, and went over the presentation he was doing the next day on Role Centers with AX 2009. Having the chance to randomally meet, share and talk is what makes AXUG such a great event.

Of course, there is always plenty of ways to meet without taking a chance with the random encounter. Still goes to show the value of being there, and interacting, which is still a great value!

So next we had Wed at AXUG, and after breakfeast, I had an early session, TECH05 - "The Technical side of cloud computing". It took a little bit to get everyone awake, but after doing so that also turned into a great session. There is for sure real interest in cloud computing, a lot around the formely called Microsoft BPOS, which is not called Office 365. Also some interest in Azure Development, though most companies were still roughly 12 months out of doing anything with it. One of the points I made in this presentation, and ther EXE02 one, is the fact that American companies have a culture issue around not trusting the cloud. it's a false reality, that their data is more safe in their data center, than the datacenters that Microsoft has built and is building for Azure. Companies will come around, most just don't like being first.

After this session, it was time to listen in on an Upgrade Tips and Tricks for AX 2009. This was well attended by some of our customers, and actually one that most likely I will be helping them with their upgrade. It was a good session, had good questions, and mostly open actually. I think most everyone that walked into that session, walked away with knowledge and information to help them out. One thing I did notice, is that most companies were on AX 4, and wondering if they should wait until AX 6.

This was covered good, but the reality is ROI for the company. That is what should be used to determine if AX 2009 or AX 6 (wait) is the best for them. People have to keep in mind tha AX 2009 is a mature product, with service packs, and many bugs fixed. Were as AX 6 is still a beta level. This is a big consideration, even more so now that the new came out AX 6 RTM date has been pushed offically into Q3.

After this session, I lead another session, in the same room on AX and the iPad. This was actually the biggest session I had, with the room totally packed out, and some standing. I covered the iPad and why business' are wanting to use it. Form factor, ease of use, battery life. I also got into RDP access to a Dynamics AX instance, from the iPad. Most everyone in the room that had an iPad was already doing this. Then I showed off Sunrise axPad Sales app. This is an iPad application wrote in Objective-C, native to the iPad that connects and extends Dyanmics AX through SOA approach. After showing this off and fielding questions, we also talked on HTML5, and using web applications for iPad, iPhone and even Driod based devices.

This ended as a great session, with a lot of interest in native apps running on the iPad and connecting / extending Dynamics AX with. Finally it was off to more expo time, and spending time with customers and ISV. We actually spent a good amount of Time with DynamcisAnywhere. I have interviewed and posted about them before on my blog, dynamics-ax.blogspot.com. They are an ISV that works specifically with VAR Partners to help solve the mobile warehouse needs of customers, with a framework that lives and is configured with Dynamics AX itself.

Finally, I did have to say good bye to everyone and head back home to get back to real work and real life. It was a great summit, and I highly recommend anyone that is not a part of AXUG, or have not attending an AXUG summit, that next year you make sure to. It will be in Las Vegas at the Ceaser Palace! Should be lots of fun, and hopefully I will see some of you there!

I will end with this, it was great seeing the Dynamics Community team there, helping spread the word on what a great resource this site is. The new 2.0 version brings so much to make this the portal Dynamics Customers, Partners and even Microsoft should be making use of. Also, Catherine McDade and others from the Microsoft support team were on site, and attending. I was so glad to see that kind of support from Microsoft!

That's all for right now. Check back, as next month I will continue my posting here on my guest column.

-Brandon