Customization of ERPNext for EPCM Market

Checkout List of Module Volunteers if you find any similarities.

May be related issue.

Briefly,

Bill of Quantities (BOQ) will be mapped as

  • Project / Task Tree for recording time and description part of BOQ
  • “Work Order” will be linked to this Project / Tasks and BOM based production for any task/work order will be re-used
  • Tasks can record Timesheet / Worker or Employee payments based on timesheet

I don’t think above issue covers everything what you have explained in the topic.

You are welcome to send PR of what you’ve already developed (if there is anything).

For DocType Names.

  • Avoid Short Forms “WBS”, in some domain it may mean something else.
  • What is Sub Project? Checkout NestedSet / Tree view feature of frappe framework, Task is NestedSet already. Task Tree can be made. If required Project can be made NestedSet, but why task and project both need to be nestedset?
  • In general avoid generic names - example: Room DocType exists in education. We needed Hotel Room recently, with that logic Education needs Lecture Room or Class Room not just “Room

If you feel you need to discuss functionality, data, design, naming conventions open an Issue.