Design Assist Methodology

We realize the design is not complete at this time. The goal of this proposal is to thoroughly define what we believe to be missing or unquantifiable so an allowance can be carried by others. It is also our desire to positively influence the cost of construction as the design matures. Rather than attempting to distinguish between Value Engineering, Constructability and Coordination during preconstruction, our philosophy as a design-assist partner is to methodically work from generic to specific. We consider cost control to be a by-product of our efforts, not an activity.

From our perspective, generic is considered the selection of the Lateral Force Resisting System (LFRS) type, LFRS locations within the structure, gravity framing orientation, and the diaphragms and chords that transfer forces between the two systems. The type, size and grade of materials are also tackled in these early stages of interaction with the design team to ensure we are efficient, but also working with materials that are readily available.

Conversely we view specific as the detailing of individual connections and the direct interface with trade partners who rely on accurate models to ensure a fully coordinated building information model.

Constructability consists of connections that are efficient and reliable in real world applications. A coordinated model linked to a primavera schedule is sometimes required to demonstrate the viability of practices that offer the promise of efficiency yet carry the risk associated with employing a new technique method. When beneficial, our team utilizes 4D modeling to confirm the sequence, access, and safety of high risk operations.

Cost control is the by-product of innovation, enhancing efficiency, and building reliability by anticipating, quantifying and mitigating risk. Only expertise, experience and timely engagement can guarantee a fully coordinated building information model. To this end our team has developed a scope matrix to ensure coverage and eliminate doubling up on scope. An example is included, but a brain storming session is required to tailor the scope matrix to a specific project.