If you have trouble viewing the videos - Allow all cookies for [*.]google.com
The BOQs are the client requirements - however the items defined by the client may not necessarily correspond to the execution plan to be adopted.
For instance a BOQ item such as excavation maybe defined for the entire project - which in turn may consist of multiple structures, whereas execution will be done structure-wise. Thus the user must break up the BOQ into various sub-items (sub-tasks) - in OMNI these sub-tasks are commonly referred to as Scopes and the hierarchy of these Scopes is called the WBS (Work Breakdown Structure).
OMNI provides a library of pre-existing WBS items that can be used as a Template for the creation of these Scopes. This pre-existing WBS library is called the WBS Template.
Note: Creating a new WBS Item (i.e. Packages, Parent Scope Groups etc.) - should be a rare event. Only if a particular Job calls for a new Activity Type should any change be done to the WBS Template.
From the WBS Template the execution item maybe copied into the Job.
Note: Copying scopes from the WBS can be done once when the Job has been freshly created. Once New Scopes have been added the Copy function is disabled.