An overview of Project Operations | Microsoft Dynamics 365

This week we talk about a Dynamics 365 module we haven't spent much time on in the past - Project Operations! Ashley's been working with it recently so we discuss some cool features, potential limitations, and why you need a lot of data setup to make it work. Leave your thoughts or experiences in the comments!
Be sure to like and subscribe!
Visit www.dynamicshotdish.com for more information.

[@juansimon8737]

Like Antti says Project Operations is one of the most misunderstood modules of Dynamics today. It is a big application like Field Service, so there are tons of things to set for the product to work. Part of it is the element of Project Management/Resource Management. These tools are huge and have lots of dependencies and moving parts that need to work together. The other is the fact that Project Operations was built to generate 'Actuals' for ERP systems, so it has, dare I say it, a bit of an ERP way of thinking in it which adds to the settings and processes that must happen!

[@juansimon8737]

Similar to ERP systems it presents 'some' rigidity (it's basically 3 apps into ONE) in how your process must Flow! So it needs more thought for sure in order to use the main features plus adherence to certain workflows in order to produce the end results. But, once you get the logic of it it actually flows pretty nicely. I have seen PMs loving it after playing with it. Unlike Project Desktop it is easy to start.

[@dynamicshotdish]

This is such a key point - how MS has rolled 3 applications into 1. So it's already going to be complex. I have found that PMs love it as well for the analysis it can provide on project profitability. Thanks for the comment!