
How it works:

Overview
PointVerge Design, Drafting, and Materials Management Transform your Industrial Construction Project Conceptual Design Into a Model that you can Buy and Build from
A Detailed Look
PointVerge introduces Materials Data Management as a single discipline servicing Engineering, Procurement, and Construction project phases.
Materials Data Management is governed by a Materials Execution Plan and supported by the QuBR database tool.
​
Now we can break this process down even further.


Engineering
Let’s peer into the project phases a little deeper.
PointVerge works in the Mechanical
Engineering discipline.
PointVerge builds Engineering Specifications into the 3D Modelling Component Library.
Drafting & Design select parts from this library to assemble the design model. Continuous
Quality Control ensures synchronization with and conformance to Specifications and Standards.
​Procurement
Here we look a little deeper into the Procurement phase. Every Procurement activity relies on some list of parts & labor derived from the BOM.
QuBR provides these lists as customized reports.
QuBR relies on BOM data directly exported from the
design model. Quality control of the component library in Engineering ensures these BOMs are Procurement-ready.
​
Real-world usage data is fed back into QuBR for parts reconciliation and for further use in other systems.


Construction
Here we look a little deeper into the Construction phase. Isometric drawings generated from the model have individual BOMs that are Construction ready thanks
to the Quality Control done in Engineering.
Similar to Procurement, QuBR provides custom BOM parts & labor reports for each Construction activity. Applied factors and calculations are
embedded into QuBR reports.
Real-world usage data is fed back into QuBR for parts
reconciliation and for further use in other systems.
Procurement & Construction
This is how things look without Materials Management. BOMs are exported from the model as simple tabular files and are separately dispersed to various users without document controls.
Each user directly edits data for their own use, breaking the connection with the original and repeating steps taken with previous BOMs. A master file is difficult to impossible to maintain.
Synchronization is impossible without a centralized system; data will leap-frog between users passing modifications forward.

