BOQ Annotation
ProjectVIEW ERP employs a hierarchical annotation system that uses asterisk-based level indicators and code-to-letter mapping to define item levels and relationships within the BOQ.
Visual Walkthrough
In ProjectVIEW ERP's workflow, we utilize Column A to define a pseudo serial number (SI No.) that mirrors the structure of the original BOQ serial number. This pseudo SI No. is annotated in a specific format to ensure compatibility with our ERP system's data import requirements, facilitating seamless integration and accurate item mapping during the upload process.
*Refers to lvl 1
A, B ,C D, refer to level 2 if under level 1
** Refer to lvl 2
A B,C, D refer to level 3 if under level 2
*** refer to level 3
**** refer to level 4
To standardize BOQ structuring and ensure compatibility with our ERP system, we use a dual-referencing system that combines an asterisk-based level indicator with a code-to-letter mapping convention. This approach supports clear hierarchical organization and smooth data integration.
Asterisk-Based Level Indicators
Each item is assigned a hierarchical level using asterisk notation, as follows:
*→ Level 1 – Main categories or disciplines of work.**→ Level 2 – Subcategories under Level 1.***→ Level 3 – Further breakdown under Level 2.****→ Level 4 – Detailed line items under Level 3.
This asterisk system provides a visual and structural guide to the depth of each item in the BOQ hierarchy.
Code-Based Sub-Item Mapping
In parallel, we apply a numeric coding structure (e.g., 01, 01.01, 01.02, etc.) which corresponds to alphabetic annotations for use in ERP-upload formatting. This mapping functions as follows:
01*→ Level 1 item01.01= A → First Level 2 item under0101.02= B → Second Level 2 item01.03= C, and so on.
If deeper levels are required (e.g., under 01.01), further codes like 01.01.01 could map to Level 3, and would be represented using the next set of letters or numeric subcodes depending on the formatting logic.
Purpose and Advantages
This system ensures:
Clear and consistent hierarchy throughout the BOQ.
ERP-friendly annotation that enables automated parsing and mapping.
Scalability, allowing for flexible multi-tiered breakdowns.
Ease of cross-referencing between the source BOQ and ERP records.
Video Walkthrough
Last updated