Architectural Revit SEED Process for establishing origins with consultants

The 'seed' process requires Architecture to create a base minimum shell model of slab, grids & floor levels for each building. These seeds are distributed to the consultants to ensure each trade within a building links to the same coordinate system.
Sample seeding process:
·         Architectural creates a shell model of slab, grids & floor levels for the buildings- establishing the XYZ 0,0,0 point- typically at a grid intersection (A1)
o    If a good CAD File has been created and can be used they should be brought in at 0,0,0 and followed as a basis of organization so CAD and Revit will overlay properly
o    If no reliable CAD files exist origins can be located by turning on the "Reveal Hidden Elements" light bulb located at the bottom-left of the modeling view
·         Enables work sharing
·         Saves the file with correct naming (per project requirements)
·         Depending on which is the most logical discipline to control the grids & levels:
o   If Architectural is charged with controlling the model- structural references/copy/monitors the Architectural model.
o   If Structural is charged with controlling the model(need more immediate access for structural analysis, etc.):
§  Architectural sends the seed to structural.
§  Structural takes over the Grids, Levels, Columns and structural walls in their model.
§  Structural sends the model back to architectural.
§  Architectural removes the temporary structural grids from the architectural model- Links structural in & uses their grids & Levels. As a precaution – a copy/monitor operation is typically used so if the structural team should lag behind- architectural can update the model's structural components.
·         Once established the 'seed' model is sent to the remaining consultants.
·         The consultants then copy/monitor the levels and if necessary the grids, walls, floors from structural or architectural.
·         An 'architectural' Revit site plan will be used to locate all buildings on the site.
·         'Progress model' Exchanges are made on a weekly basis at the end of the week(Friday-Sunday)  so that disciplines are always within 1 week of one another. These are not finished products. These can also be made 'on demand' as necessary.
·         'progress models' are copied to archive folders on upload or download for future reference.
·         Alternatives like the riverbed appliance or script automation could keep files updated on an hourly or semi daily or daily basis.


Popular posts from this blog

Revit area plans adding new types and references (Gross and rentable)

Organization and management of data in Revit across omniclass, Masterformat, Uniclass, and Uniformat