<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/838777ebbffb4736a42ef07543ff5d34&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/838777ebbffb4736a42ef07543ff5d34-bfa6cdb80146f542.gif</thumbnail_url><duration>998.658</duration><title>Linking ZZ Quantities into Bidbow</title><description>I walked through a workflow we are setting up with Bidbo to link quantities from ZZ, using a resource list that matches Bidbo resource descriptions, and an export from ZZ to Excel that we import into Bidbo with an ID column renamed to match. In Bidbo, I use a description column, units, and measurement 1 and the hierarchy to build base items like my slab on grade and footings, with variables and resources flowing into the estimate. Pricing then pulls from the Bidbo library using the ZZ quantities, including options for measured quantity versus waste included quantity. I also discussed a fork in the road on whether ZZ quantities with resource codes should come in as fixed resources or as variables for further math. I am looking for your thoughts if this is a good workflow or if we should tweak it.</description></oembed>