Dave Shea Dispatcher

My current process has me creating 4 work orders each representing a milestone within a project. This works to replicate progress invoicing within Field Service at the cost of losing insight at the higher level in a single view.

Would it not be possible to set up a parent work order logic similar to the incident type logic is Primary (is parent); and then tie in the child work orders in the entire process. I couldn't find information from Microsoft on the intended purpose of those fields but found some from IBM which seems to I think make my idea seem reasonable?...

https://www.ibm.com/support/pages/when-use-child-work-orders-tasks-and-multi-asset-location-table-work-orders

What you could then do is have a Parent work Order be completed only when all children are completed (if dependent), but it would also allow me to submit one quote to the client and have 4 child work orders spawn from it, see the profitability of the Parent Work Order (project as a whole), instead of only the milestones.

I understand that I'm currently using field service instead of project operations but as of now there is a minimum license requirement for project operations which is the root cause.

RSO respects requirements. Could it not also have the ability to scan a manually created schedule for these same requirements and highlight those that don`t comply? example: predecessor successor logic not being respected.