Estimating Assemblies Building - Offline

We have a diverse amount of experience in our estimating department. Our assemblies have always been high level without a ton of details because we sub out 90% of the work. We have many junior estimators that have worked in the subcontracting world and I'd like to teach them how to build assemblies in SAGE and allow them to build new assemblies they think we need or could use. Or update/ modify existing assemblies to add more detail and depth. However I cant have them playing around with these in our current database. Id like to allow them to do this in a 'Playground' type atmosphere then allow them to present the assemblies to the group and decide if we want to add it to the current database or we can suggest ways to adjust.

For example currently masonry has several line items but No assemblies. We will never self perform masonry but I believe its extremely important the next generation of estimators understand it takes bricks, blocks, mortar, grout, rebar, pencil rod, scaffold, wall ties, caulking, etc. and all the different possible sizes, formats, designs etc. So they know and can price a soldier coarse or herringbone as a more expensive assembly.

I'm hoping others may be willing to share what they do, Best Practices for example. My first and only thought is a separate database but not sure how I would get the newly built assembly from one databases to the other.

  • You are going to want to use the Sage Estimating Management Console and under Tools go ahead and copy your database so you have a playground to work in.  Estimators would just go to File and Open Standard Database to work in the playground.

    As far as getting new assemblies into your working database you would again go to Sage Estimating Management console and under Tools choose the Merge database.   This creates a 3rd database with a new name.  I would strip out of your new assembly database everything except what is related to the new assemblies.  And of course test test test your new 3rd database before making it the one to use.

  • in reply to Mike Orgler

    Thanks Mike.