Scopes & WBS
BOQ items are client requirements, but they may not correspond to the execution plan. For example, a BOQ for "excavation" might cover an entire project, but execution happens structure-by-structure. You must break BOQs into sub-items called Scopes, organized in a WBS (Work Breakdown Structure).
WBS Hierarchy
The Work Breakdown Structure follows a four-level hierarchy from broadest to most specific:
| Level | Name | Description |
|---|---|---|
| 1 | Package | Top-level grouping of related work (e.g., "Civil Works", "MEP") |
| 2 | Parent Scope Group | Major category within a package (e.g., "Structural", "Finishing") |
| 3 | Scope Group | Specific grouping of related activities (e.g., "Concrete Work") |
| 4 | Scope | Individual execution activity (e.g., "M25 Grade Concrete") |
Scope Master Fields
Each scope item in the WBS template is stored in omni_scope_master (10 columns):
| Field | DB Column | Type | Description |
|---|---|---|---|
| Code | scope_code | varchar(50) | Unique scope identifier within the template |
| Description | scope_description | varchar(max) | Full description of the execution activity |
| Scope Group | scope_group_id | int (FK) | Parent group in the WBS hierarchy |
| UOM | uom_id | int (FK) | Default unit of measure for this scope |
| Rate | rate | money | Default rate (can be overridden per job) |
| CPV Code | CPVCode | varchar(30) | Common Procurement Vocabulary code (EU classification) |
Job Scope Fields
When scopes are copied to a job, they become Job Scopes stored in omni_job_scope (23 columns) with job-specific data:
| Field | DB Column | Type | Description |
|---|---|---|---|
| Code | job_scope_code | varchar(max) | Scope code within this job |
| Description | job_scope_description | varchar(max) | Job-specific description (can differ from template) |
| Quantity | quantity | money | Planned quantity for this job |
| UOM | uom_id | int (FK) | Unit of measure (inherited or overridden) |
| Rate | rate | money | Rate for this scope in this job |
| Value | value | money | Calculated: quantity × rate |
| Planned Start | planned_start | datetime | Scheduled start date |
| Planned Finish | planned_finish | datetime | Scheduled completion date |
| Actual Start | actual_start | datetime | When work actually began |
| Actual Finish | actual_finish | datetime | When work was actually completed |
| As-built Qty | actual_final_asbuilt_qty | float | Final measured quantity after execution |
| BOQ Link | boq_id | int (FK) | Linked BOQ item (set when linking scopes to BOQ) |
| IDC | IDC_id | int (FK) | Indirect Cost category assignment |
WBS Template Library
JobNext provides a library of pre-existing WBS items (the WBS Template) that can be copied into a Job as execution scopes. This template contains standardized activities that organizations use across projects. The template is a shared organizational asset — additions should be carefully considered.
How to Copy Scopes from WBS
- Navigate to the Job and open it
- Click Scopes in the horizontal menu tabs
- Click Copy from WBS button
- Browse the WBS template tree — expand Packages, Parent Scope Groups, and Scope Groups
- Check the boxes next to the scope items you need for this job
- Click Copy Selected to import them as Job Scopes
- After copying, set the quantity, rate, planned dates, and notes for each scope
Important Rules
Linking Scopes to BOQs
After scopes are copied, they must be linked to BOQ items to establish the cost and schedule relationship:
- BOQ Items are client deliverables
- Scopes are execution items
- To deliver a BOQ Item, one or more Scopes need to be executed
- Linking establishes which scopes contribute to which BOQ deliverables
Linking Parameters
| Parameter | Description |
|---|---|
| BOQ Conversion Factor | Converts scope quantity to the equivalent BOQ quantity |
| Stage % | Percentage of the BOQ rate applied to each stage (for stage-wise BOQs) |