Posts

Showing posts from December, 2010

Kinect touch free controls for Windows 7

Templating nomenclature & Updated browser settings for project browser(VIEWS)

04.AI-IN-PLANS (1/8"/FT) 04.AI-IN-PLANS (1/4"/FT) Added- for interior floor plans (Intended for AE451 series – needs some coordination with interiors- Steph & Michelle can we meet tomorrow morning?)                to show casework and interior elevations (& Details?)
Project browser settings:

Browser- (Default) Browser
*UNUSED VIEWS filters out showing all unplaced views in the set- except dependant/primary views *USED VIEWS isolates views placed on sheets.
*NOTE: for USED / UNUSED - With the exception of PRIMARY/DEPENDANT Views… Primary views are never placed on sheets… so they show as unused even though the dependant views ARE on sheets. Unused dependant views show under the primary view status.

View templating nomenclature:

00.01-DETAILS-GENERAL(1-1/2"/FT) |  |  |       |      | |  |  |       |      +----(SCALE SPECIFIED IN TEMPLATE-IF SPECIFIED) |  |  |       | |  |  |       +-----------EXTENDED DESCRIPTION |  |  | |  |  +-------------------2x Discipline designator or | …

DRAWING CLEANUPS... Elevation marker cleanups

For elevations on the plans that exist within a callout- 1. Go to the callout (Or verify the scale of the callout) 2. Select the point of the elevation 3. Match the HIDE AT SCALES COARSER THAN properties of the elevation to the callouts scale. If the callout is 1/2"/ft then the Elevation marks within that should be hidden at scales coarser than 1/2"/ft. IMPORTANT: If for some reasons callouts are being deleted - YOU MUST OPEN THE CALLOUT TO SEE IF THERE ARE ANY ELEVATIONS IN THE CALLOUT and change them back to 1/8"/ft. If this step is not followed the elevations will be invisible in every view. NOTE: SIM views are view-specific and do not have a hide at scales coarser than. This could be handled programmatically- search through every view defaulting the hide at scales coarser than for the finest scale visible. Filters for tags and limit for hide at scales coarser than and [ ]only views on sheets (REGEX filter) should be considered.

FW: 03683 Partition schedules

There are a lot of reasons for including interior finishes included with wall types including accounting  for material thicknesses and elevational information, fire & Smoke ratings, etc .
Ways of managing the wall partition schedule that meets the BIM nature of projects (Including finishes) are being devised. Some of the wall types should be inseparable like heavy stone finishes on a load bearing partition while others can be additive- like the wood finish panel systems in corridors. Having placeholders for elements like these in critical wall types or UL Specific wall types should be the basis for categorization.
The VA Is heading to a process similar to this (<>).
I disagree with the approach of creating 'general' partitions with generalized notes (I.e. Cementitious board at all wet areas, Impact resistant board at all corridors and only one A1 wall type) and I disagree with reverting to a generalist approach to the Revit BIM model- its ends up being counterproducti…

Partition schedules

For the wall legends the underpinning data needs to be the basis for tagging- and from best accounts in my research and discussions with other BIM Managers- modular systems seem the best way to go.
One possible combination a wall class (Existing, Concrete, Masonry, H=Shaft, S=Steel Stud, W=wood) + (Nominal size of the wall assembly rounded to the nearest quarter i.e. 4 for four inches, More definitive would be eights expressed as 1 2 3 4 5 6 7 8 so 4-1/2" would be 42, 7-5/8" would be 75. This could be brought back to 1/4" increments- and should be noted in the schedule general notes.
Additionally for more interior-intense finish jobs I have seen systems similar to above over a list of modifiers for interior-exterior in a compound tag.
The finishes won't be of particular note to the wall tags- Unless there is a specific UL that calls it out or requires it... Or if a specific assembly is required for structural support as in the stone.
A schedule of wall types should also …

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) oIf 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 oIf 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: oIf Architectural is charged with controlling the mod…

translate process (Details 1-1/2"/ft and finer)

Image
Focusing on one typical detail the following process evolved - the results match the Revit detail very closely... We will have to see if successive exports have any glitches in them. Since Revit is exporting in a CAD layer format much like the NCS- the following was translated down to Dustin's template (Fewer layers....) for this project. #1 Export from Revit (Using the NCS3.0 APPX template and Override objects: #2 Open in AutoCAD and cleanup using DWG_CLEANUP VBA (I have here locally - we can set to redistribute if needed) #3 LayerTrans using the attached template: NOTE_ Not all line weights are there- BUT most are... We can adapt further and re-examine if later exports vary too much:

More of a what we can use Revit for…

More of a what we can use Revit for…
Revit can be used in a very limited fashion to leverage CAD drawings. ·Link the CAD file in (Verifying the origins line up) to the current view only, and origin to origin. ·Use Room separation lines (at the centerline of the CAD walls) to set the limits of the room. ·Furniture will then schedule according to the rooms. ·Color keyed schedules can be quickly created and labeled. ·For more accurate square footages, use generic wall types to approximate wall thicknesses.
Visibility and graphics 101 checklist for missing objects- Start with the light bulb tool in the lower-left hand corner of the 'Drawing area' in the rightmost side of the 'View Control Bar'- click it and it will show all hidden objects loaded in the drawing. To restore an element's category- select it, right click it and unhide category. And remember NEVER use the hide element, override graphics for element! It is a slippery slope quickly leading to inconsistent drawings…

Revit Server (New fall 2010)

Found this from an AU2010 class- The Revit Server Extension may prove helpful if we need to work over the WAN.

http://download.autodesk.com/us/subscription/sap_2011/videos/revit_server_extention/aec-sub-adv-pack-revit-server-ext.html

From what I gather it adds an intermediary  between the actual central file and what the end-users perceive as the central file.

Typically for use if users on a project must collaborate across the WAN.

A central server (over the WAN) maintains what I will call the WAN-CENTRAL file The local server communicates with the WAN-CENTRAL to maintain updates on what I will call the LAN-CENTRAL during STCs The end-users STC on their system syncs with the LAN-CENTRAL copy. This is supposed to eliminate the (potentially deadly) Wide Area Network lag- so users perceive a STC that is as fast as a LAN STC and no issues arise from the lag not syncing across systems.

All this appears to be handled with my SQL- so true locks can be established with pieces and parts of the file&#…