I am setting up Project Service Automation (PSA). There was a suggestion to make things as simple as possible and only offer a few features until people get accustomed to PSA. We basically are coming from Word, Excel and manual processes for projects and sales. We have Sales prepped to use sales and marketing but they are not in the system yet. We will be starting people mostly in PSA first. We have an external quoting tool but integration will not happen right away.The front running idea is starting our projects with Contracts. Fill out the contract as a Statement of Work using it to work out the details if needed. We then would email the statement of work to sales and get a Quote from the other system. The statement of work then could be reworked if needed.
My concern is contracts are orders in PSA which usually means the sale was closed. Since the sale has not closed it seems like I have the potential for a mess. Eventually, the plan would be to use Dynamics 365 CE as expected(sales, marketing and PSA) and integrate with our quoting tool (QuoteWerks). I can see data integration and migration being a mess.Does anyone see problems that we might experience using the Order/Contract to work out our Statements of Work? I understand there can be areas in PSA that require things done a certain way or you can paint yourself in a corner. Just not sure what all those things are.Thank You,
Hello Sunil,Thank you for your reply. I agree that I think out of the book PSA does not seem right for us. We have not integration with QuoteWerks now. They will still generate a quote for an SoW. The only difference is the word template language. I am leaning toward the Quote being renamed to SoW for our users. Then have them work the details out there. They could attach the other systems Quote to the D365 Quote(our SoW) form. Then have a chance to confirm everything before we make it a Confirmed Contract.We are trying to not renew on another time tracking system. So my boss would like to get something going now. Taking Contract and only adjusting that and Project entity seems appealing. I am worried about all the processes and complications that starting at Contract/Order would make things difficult. We might not even know there was an issue until we start looking at integration. At that point, we might have a big problem to clean up.
Do you have any potential issues that we might experience starting at Contract? That way I can convince him that Quote is a better place to start. If I am wrong on this then I would be happy to know that as well. It just seems that matching PSA settings would be correct in the long run and especially in the short run (considering integration or using the system in full later)
Hi Sunil,Thank you, that makes sense and is what I was worried about. I believe we can create SoW's on Quotes and then move the process forward. SoW and Quotes have the same info so syncing that later should not be a problem(actually the quote is more to track in the quoting system right now anyway). The ad-hoc process to me is starting on Orders with sales that are not done yet. Then it appears once a Contract/Order is confirmed it is not easy if possible to go back and edit.
My Reason to start at Quotes so far:
If you've found this thread useful, dive deeper into User Group community content by role