Should the WBS include the project manager's work (e.g., EVM) as well?

For the WBS, should the staff and management be included (what’s under the structural QA inspector ) for the subprojects?

Can I leave lower-level tasks combined (since I cannot fit all the details into 60 lower-level tasks)? (Image attached)

Do we need to include technical goals under the goal section

1. The construction can withstand XX Wind Load

Are we restricted to only 3 levels in the WBS, or is it acceptable to extend the structure to a 4th level if needed for clarity and task distribution?

Is it acceptable to have multiple level 1 items, or should we move the 2 main projects to level 2 under a top-level title? (image attached)

Can we have a same team for 2 main projects, as the tasks are similar (image attached)

For sub-project, is it legit to classify with different specialization instead of functional unit?

For instance:

Level 2: Mech / Elec / Automation

or

Level 2: Dosing Unit, Intake Unit ...

The rubrics stated that we have to specify milestone in WBS. However in the FAQ recently, milestone were stated to be in table format. I guess we could just have a WBS chart and a standalone milestone table?

Do we need to estimate the duration of each task in M2 and include this in our report&presentation?

The WBS and precedence diagram is too complex to be visually appealing if we attached it in our report. Could we provide a hyperlink to the original image instead? Or if there were any other ways recommended?