Monday, June 21, 2010

EXTENTS of a view from a callout, section or elevation

Keep section and detail callouts relatively tight to what is being annotated.

 

Basically –

If the current view’s range ‘touches’ the extents of a tag’s Crop Region that callout/section/detail will show in the view. If MORE space is needed for annotations- turn the annotation crop on and stretch the limits to include the necessary annotations.

 

There are many places where annotations can be turned off but all views should be kept closely cropped to the elements (i.e. curtain wall elevations) referenced.

 

Several comments regarding “CW showing in plan” were due to the section-elevations of the curtain walls extending too far to the plan views below.

Friday, June 18, 2010

The Revit View naming conventions established in the DOD outline correspond with slightly adapted NCS Version 4.0 File naming conventions. There are a few basic reasons for the format and rigidity


If you don't have the luxury of a 100% Revit-BIM Based project you will need to import/export to CAD and subsequently DGN for most DOD / USACE projects.
The  Revit View naming conventions established in the DOD outline correspond with slightly adapted NCS Version 4.0 File naming conventions. There are a few basic reasons for the format and rigidity
1. The view names need to be organized in something other than "DETAIL 1", "CALLOUT OF FLOOR PLAN 1" "ELEVATION 1", etc. from Revit's generic naming conventions.
2. Because the views are exported to PDF and DWG reference especially in Hybrid projects- the best convention we have to follow is based on the current NCS (National Cad Standard currently version 4.0).  Every major player in the US either loosely or strictly follows or will be following this standard; Including U.S.A/C/E, VA, GSA, and DOD. Building Smart Alliance currently oversees the NCS and the NBIMS initiatives.

As NCS is modular it breaks down most of the file naming for the base types from which the USACE and VA have adapted their systems. As Revit appends the view/sheet name to the project name on mass export/print - it is best to use a project and view naming system with these file structures in mind.
3. Familiarity  with a system keeps users in touch otherwise we tend to use it or loose it.
USACE deviates slightly from the NCS (as does the VA). And there are some overlaps where view/file names would otherwise 'overwrite' one another which is where the more detailed overview from which the DOD Template is derived. The more detailed version in the Legend view of the DOD-Revit template file spells these definitions out more explicitly incorporating  previous resolutions to issues already dealt with and strike some solid ground among all these standards.
This standard is young, It is not perfect, and it will evolve and grow.
If you don't use this system and plan on exporting/printing from Revit you will have to rename, by hand, every single file generated every time you export. Sheets, because they basically do follow the standard, do are not as much of an issue but still benefit from this structure.
The Revit View Naming system developed takes the Project numbers (file prefix) and USACE and VA and NCS export issues into account based on ongoing experience with these projects and can be quickly cleaned up by Denis Kozlov's DEN4B ReNamer 5.25  (8 April 2008) with a renaming profile. This should correctly compact the name of the files to meet DOD requirements quickly.

Cad Export Process


Added... "Browse to the export folder." below

Cad Export Process (After bare-bones & Materials are assigned)
Revit Icon> Export> CAD Formats > DWG

















Select set to export (Or Insession)


Select sheets/views to filter in the list. Sort by name to itemize everything by drawing type and its name

Set up CAD Layer naming (If not already set)


This may require selecting one of the read-only layer exports and resaving it under a different Name. Revit ADDS ALL LAYER NAMES from linked drawing files- to prevent this list from becoming too large we made it read only.


Browse to the export folder.

Strip everything off the ‘tail’ of the file name so the project number (and building identifier if necessary) are the only  elements left to use as a prefix. Revit will add a “-“ after this prefix.

  • For standard CAD export - Make sure the [ ] Xref views on sheets is unchecked. This places all elements with the sheet in one file.
  • For “STRIP REFERENCING”  Make sure the [X] Xref views on sheets is checked.

*If files and borders are to be x-refed for continuity- editing in CAD must be done to setup the xbdr files and other base files.

You can then use Re-namer to further clean up and refine the file names (If you have several to do at once)

Mass-renaming of files should only be attempted by those who are certified to use it.

 

FINISH_EXTENTS TAG

Finish extents tag-  to show extents of finish along wall in plan. 
This 'tag' is actually a  DETAIL COMPONENT that you can use to tag walls/extents of finishes to show the extent of finishes in plan (Interiors old-school).
It can be taken one step further- By incorporating this detail component into a generic wall hosted family- it can force to snap to walls and will show wherever the instance is cut. These families would actually map the extent of the wall finish as a wall-hosted object which then would show the tags when cut. This can be done but would take some reconstruction of the family to keep it under control (Like the ADA graphics- it would likely need to be a generic subcategory and/or locked down to a specific workset)
MARK and DESCRIPTION are the parameters for the text/graphics. These are designated by type.
FINISH_EXTENTS.rfa

CEILING PLANS

 

To show the ceiling plans correctly, the RCPs will be cut at a height of 7’6”

 

All the drop soffit areas lower than this will need to have plan regions added to them to drop the RCP cut plane in these regions to 6’9” to display and register correctly.

 

 

 

A SINGLE SKETCH in the PRIMARY VIEWS with all the plan regions indicated can be used to lower the view across all drop soffit areas that are below the 7’6” mark similar to below. Try to keep relatively tight to the

 

Without a ceiling to tag, no height information or graphics stippling/representations will show (The elevation targets will disappear).

 

 

 

 

Wednesday, June 16, 2010

Windows Azure... ((CLOUDS HERE!))

Autodesk likely destined for the clouds... So' Private and Public' (MS 'Dedicated VS Standard') versions are already being run in the clouds... HUGE application implications for work-sharing applications like REVIT!

http://labs.autodesk.com/technologies/trials/

 try it

OVERVIEW

Welcome to Project Twitch! This project is testing remote delivery of our applications over the Internet. The goal of project Twitch is to enable you to test and try the latest versions of AutoCAD, Revit, Inventor, and Maya without having to install or download the applications. These applications run remotely on our servers and are delivered to you over the Internet.

 

 

 

 

 

View References

View references

 – there are two types of VIEW REFERENCES

 – opposite and adjacent.

 

View References ONLY show in PRIMARY<>Dependant view relationships. They are not visible in standard views. It is best to find the extents of the dependent views from the primary view and place the view reference tags there- use the dependant view extents (Dashed in view/annotation crop regions in the primary view) to place the tags.

 

BOTH Opposite and Adjacent tags should be used as they ‘grow’ from opposite sides of the match line-

The invisible aligning line (Below in purple) should align with the match line. Each must point to the corresponding dependant views- adjustable from the options bar or element properties.

 

NOTE:

·         In the primary view reference ALL view reference tags show.

·         In the dependant views- ONLY the view tags unrelated to the view show. In the example graphic above- match line 1/AE111-B will not show in dependant view AE111-B, however it will show in dependant view AE111-A as well as the primary view.

·         Hopefully in future Revit versions- a single tag placed in an overlapping region will point to the adjacent view.

 

Important to note these are the same tags shared between PRIMARY and DEPENDANT views. If more than 1 / 2 of the tag is off the crop region or annotation crop region it will not be visible in the dependant view- so keep that in mind when laying out the tags.

Thursday, June 3, 2010

CAD Export processes updated 2010-06-03 v1_0

This document outlines the processes of cross-platform collaboration between Revit and AutoCAD. Version 2010-06-03-1.0


Basically the steps involved in Exporting from Revit to CAD (and back) are as follows:


  • Creating reference in Revit (Discipline and type-specific, plan, section, elevation, Callout or detail) Naming the callout view name correctly.
  • Creating sheets in Revit (Setting up the details on the sheets in Revit)
  • Exporting Revit to CAD
  • Matching Revit output in CAD
  • Detailing in CAD
  • STRIP REFERENCING (For re-importing to Revit)
  • Re-Importing the enhanced information back into Revit.


NOTE:   Elements shown in RED are behaviors that need to be verified with each upgrade/update to Revit or CAD editing program. Each update can cause its own unique set of issues and should be tested on a case-by-case basis. This should probably be done with a single detail/sheet export/import from Revit to CAD before full export to CAD is assumed to be working correctly.


There are a number of cleanup VBA utilities that can be used to refine the Revit CAD Exports to align the Fonts, dimension styles, etc.


Exporting to CAD should only be attempted as a last resort as the process is time consuming and lengthy.


·         Create callouts/details in Revit
·         IMPORTANT: Rename the views in Revit to the view-naming protocol for the project. See the drafting view area for references to the view-naming conventions.
·         Create the sheets in Revit by dragging and organizing the details on the sheets. IMPORTANT: name the sheets per the sheet naming protocol for the project.
·         Assign base materials and callouts in the views on the sheets. This is the door/window/material callouts relevant to the type of view being exported. This is the "bare bones" basis for the AutoCAD information.
·         After bare-bones & Materials are assigned export the file(s) by using Revit Icon> Export> CAD Formats > DWG


Select the set to export (Or In session)
Select sheets/views to filter in the list. Sort by name to itemize everything by drawing type and its name
Set up CAD Layer naming (If not already set). Once set for a file Revit retains this information on a per file basis.


This may require selecting one of the read-only layer exports and resaving it under a different Name. Revit ADDS ALL LAYER NAMES from linked drawing files- to prevent this list from becoming too large we made it read only.


Browse to the export folder.


Strip everything off the 'tail' of the file name so the project number (and building identifier if necessary) is the only element left to use as a prefix. Revit will add a "-" after this prefix.


  • For standard CAD export (ONE-WAY to CAD) - Make sure the [ ] Xref views on sheets is unchecked. This places all elements with the sheet in one file.
  • For "STRIP REFERENCING"  (TO CAD and back into Revit) Make sure the [X] Xref views on sheets is checked.


NOTE:   If files and borders are to be x-refed for continuity- editing in CAD must be done to setup the xbdr files and other base files.


NOTE:   Renaming software can refine file names but will break x-ref naming associations. A preset for Bay Pines exists here:
               S:\Healthcare\3683a-00 VA Bay Pines\2.0 Drawings\2.4 Revit\4.0 Publish\4.3 DWG\4.3.1Renamer_Presets\03683a-00-VA_BAY_PINES-new.rnp
              
               *Mass-renaming of files should only be attempted certified users. If you have any questions or need someone else to clean up the DWG file names contact Ron Allen (Apsis0215@gmail.com) and we can go over the use of this software.



When exporting to CAD Revit creates PCP files containing pen weight information. As there are a number of customizations that occur in Revit between differently scaled views. This needs verification in a real-world test. Each new version of Revit/CAD can cause issues in exporting making it difficult to maintain visual fidelity between CAD and Revit drawings. It may be beneficial to use the exported PCP file for the sheet layout. Adjustments to the layer-export file may be necessary.

STRIP REFERENCING
One way to minimize the graphic impact of CAD & Revit sheets in a set is to create the bare-bones details and sheets in Revit, export the sheets to CAD, embellish the details in CAD via a 3rd file then link just the embellishments back into Revit for printing. We will call this strip referencing as each step in the information chain is stripped out from the previous one minimizing file sizes an the information therein.

On exporting from Revit [  ] Xref views on sheets should be selected to create separate drawing files to reference back into Revit.


Detailing in cad is intended to enhance the elements in those files using the elements as markers and locators when Revit resources are not available and CAD is the only resource available or is an only option.


Under no circumstances should the original location or base points in the drawing file be changed or the elements relocated in the file. The base points should ensure critical for re-referencing will match when the CAD files are brought back into Revit. This needs to be verified- there are some import issues when dealing with CAD in Revit Details. Real-world tests need to be run on a case-by-case basis to verify origin-to-origin match ups in Revit details.


Once the views/sheets have been exported to begin detailing in CAD:
  • Open an individual detail file
  • Save the file back out appending "-CAD" to the end of the file name. (IE "03683 - IDT3‑1G-301T - CASEWORK-CAD.DWG"
  • Move all the line work and hatching from the file away from the original location- this will be used for quick reference and eventually deleted.
  • XREF the original detail file (i.e. "03683-IDT3‑1G-301T-CASEWORK.DWG") back into the drawing as an overlay at 0,0,0.


Detail over the elements using:
  • The layers exported by Revit
  • The line types exported by Revit
  • The hatch patterns exported by Revit


Avoid the use of:
  • Masking regions
  • AEC Objects
  • Objects requiring proxy elements in earlier versions of AutoCAD. Proxy objects don't always translate. Keep it simple.
  • Match text styles, heights and dimension styles if possible


The "–CAD" version of the file should x-reference back into the CAD sheets at the same origin point in model space.


The -CAD version of the file should also reference back into the Revit drawing detail as origin-to-origin. This will bring in the additional detailing from CAD over the Revit detail. Because the views were exported as x-refs from Revit- the titles of the CAD files should match the view titles in Revit.