Project Operations is a project management tool from Microsoft that offers various deployment options to cater to some narrow requirements. Microsoft offers three deployment types for Project Operations: 1) Lite; 2) Resource/non-stocked; or 3) Stocked/production, each with unique capabilities and drawbacks.
To determine the most suitable deployment, you need to first determine which type fits your business the best. Be sure to choose wisely, as it is not easy to reverse course once you make a selection and start implementing the solution. You must choose one of the following deployment types:
Dynamics 365 Project Operations Lite deployment type
This deployment type includes the following features:- Sales process for projects that extends Dynamics 365 Sales application experiences
- Project planning using Microsoft Project for the Web
- Multi-dimensional pricing
- Unified resource management
- Time tracking
- Basic expense
- Proforma invoicing for Project manager’s review and edits
Dynamics 365 Project Operations for resource/non-stocked scenarios
This deployment type includes the following features:
- Sales process for projects that extends the Dynamics 365 Sales application
- Project planning using Microsoft Project for the Web
- Multi-dimensional pricing
- Unified resource management
- Time tracking
- Basic expense
- Full expense
- Receipt OCR
- Proforma and customer-facing invoicing
- Revenue recognition for projects
Dynamics 365 Project Operations for stocked/production order scenarios
This deployment type includes the following features:
- Project planning using WBS
- Resource management
- Time tracking
- Full expense
- Receipt OCR
- Full invoicing
- Revenue recognition
- Production orders
- Stocked materials support with inventory
With these deployment options, Project Operations tries to show flexibility and customization to meet your specific needs. However, most customers are confused over these options and what they really mean. Moreover, as you can tell by the descriptions, the functionality seems rather limited for many types of project-driven companies.
The functionality you receive from Project Operations depends wholly on how it is deployed. Also, once you make that choice, you cannot go back. For example, much of the functionality contained in the ERP with Project Operations goes away once you select one of the first two options.
Additionally, the functionality of the solution lives in different places depending on your deployment choice. For example, project scheduling and resourcing may occur in your CRM while cost tracking happens in your ERP. That means if you have the same role covering both functions, they will be managing their projects in two different systems.
Other Options for Dynamics
If you are strongly considering Project Operations for your company, first understand if you are a project business, meaning a company whose primary driver of business is projects, then you may want to learn more before you make a final decision.
If you are looking to solve serious problems in your project business, such as problems with cost control, project scheduling and resource planning, risk management, project estimation for large and/or complex projects, Project Operations likely will not meet your needs and you should consider a project business system like Adeaca Project Business Automation (PBA).
Adeaca PBA is a complete project business solution, seamlessly integrated into Dynamics 365. PBA combines one of strongest cloud ERP platforms (D365) with the strongest enterprise project business platform.
Download this Quick Guide: Microsoft Dynamics 365 Project Operations vs Adeaca Project Business Automation to gain a detailed understanding of the capabilities of both systems and how your business can benefit.
