Wednesday, December 1, 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
|  |                       Typical View Type (PLAN, DETAIL, GENERAL, DRAFT)
|  |                       (*NOTE Can be applied to other view types)
|  |
|  +----------------------rough sequential order in set
|
+-------------------------View Sheet prefix association:

##=PARTIAL, 00=general, 01=plans, 02=elevs, 03=sections
04=large scale views, 05=details,
06=schedules & diagrams (& door glaze details)
07=user, 08=user,
09=3d representations (Including perspectives)


*FOLDER_0 = view template name

 

Applying view templates applies folder1 and folder 2 which organizes  views in Project Browser.

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 counterproductive in the long run. 
We are currently implementing coarse view patterns for fire walls- and have many permutations of wall types representing walls with tile, special finishes, impact resistant finishes, etc. and combinations thereof. I suspect the answer lies in a combination of what the VA is proposing and spliced parameters including the Fire Rating parameter.

In the meantime- anyone have some good solid ways of categorizing those wall types or how do you separate they wall types and categories? 

Filters?  Display representations? What elements do you use to drive these things?

Ron

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 be generated and left on the sheet just as the VA indicated on their sheets. Note also  the VA Doesn't appear to have a graphic wall legend.  Instead we could utilize the schedule and general details which would save a lot of space and follow the current trend Tony seems to be headed for.

DOOR AND WINDOW SCHEDULES
Ideally the head/jamb/sills are called out in the schedules-
Callouts cannot go in legend views. Callouts can go into drafting views.  So a drafting view of a typical window with 'width see schedule' and 'height see schedule' should cover most types.

Dummy tags or text typically gets overlooked. General notes or schedules would be preferred over the dummy tags is possible- with the callouts being the most ideal.


Shortly before each critical printing the schedules and the partition types should be looked over.

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.





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

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 and inconsistent visibility across views!

Visibility & Graphics 102 – View templates and object settings
Many of our graphics for plans, sections, elevations, finish and furniture plans are already refined by the object styles in the DOD template. The graphic detail levels (which automatically correspond with certain scales), line weights and cut weights have been set and associated with view templates to keep the graphics readable and consistent from view to view.

Visibility and graphics 201 manual checklist for missing objects
In visibility/graphics- verify the object's category is visible, verify no filters are hiding the object, and the object is within the view's View Range (Cut, Bottom and items 'beyond' in the view depth). If working with Worksets make sure the workset is visible in the view and loaded and no filters are interfering with the visibility of the workset.

Worksets 101- Speeding up Revit

When working with large worksets in Revit, there are several ways to get Revit moving faster. One way is to limit the number of worksets that are loaded by either unloading worksets or limiting worksets when opening the file. By loading some, rather than all of the worksets, Revit has less overhead and runs/saves a little faster.

Worksets 102- or "Hey- where did my objects go?"
If you have missing objects from a view Don't Panic! 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 for visible/loaded worksets.

If you still don't see what you are looking for- the workset may be unloaded.

Make sure the workset is on, visible in the view and loaded. To load/unload a workset- use the collaboration tab and Worksets - select the respective workset and OPEN.


Worksets 103- Filters and worksets
Work set's graphics can be controlled with Filters. If you have all objects on a particular workset, i.e. equipment or consultant drawings, filters can be used to half-tone or highlight in red the entire workset-

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.




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's work shared elements.


Really Dr. Seuss'ish eh? But if they keep heading in this direction – I believe it may also eliminate the scalability issues Bentley has virtually solved.


Free with subscription pack.

Seems the best option for large projects in general – Autodesk should consider this approach for Revit in general... this may be where they are already heading. With this approach linked files would be virtually transparent either over the LAN or the WAN.

This hasn't been tested in virtual servers and the could yet- but that too may prove to be promising. A typical added cost could come in the form of a redundant 'Revit server' which mirrors the main server in the even the main goes down. If the server goes down – everything stops.

Once they establish a more distributed model- where there are redundant communication avenues between machines as well as the WAN-central I believe they will have nailed the next big hurdle.