Using Revit as a Team. Use Same Builds.

When using Revit on a project, make sure everyone on the team is using not only the same version, (2011, 2012, etc), but the same build number as well.  The build number can be found by clicking on the question mark pull down in the upper right corner, and click the About button….

From there, you’ll see the splash screen of the version, and the build.  The first 4 numbers in the year the build was released, (2010) The next 2 are the month of the release, (09-September), the next 2 are the day of the release, (03-third).  The last four are the actual build number 2115, and the service pack number is new to the newer versions.  Might not be shown for earlier versions.

 

I’ve seen fatal errors in Revit when teams are using the same version, but different build numbers, and users are syncing their builds local file to the central file, and the central file is receiving updates from multiple builds, when there have been some changes to the software code, and there is a discrepancy  between two items, one new version, one old version, and Revit doesn’t know what to do. 

In order to make sure everyone is using the same build, everyone should be using the latest build.  For 2011, its build 20100903_2115 Web Update 2 Service Pack.  For 2012, it’s build 20110916_2132 Update Release 2.

Project Spark - A future Revit LT?

Project Spark is a technology preview of a new future Revit Architecture (BIM) solution. Using Project Spark, building professionals can create designs efficiently with real-world building objects, produce more reliable documentation faster, and share files with consultants using Revit or AutoCAD-based products.

Project Spark looks like a striped down version of Revit and does not support conceptual design, analysis, rendering, advanced collaboration, and API.  It may turn out to be a Revit LT version of sorts.  I would guess they would come out with all flavors of Revit, but they are only testing the architectural version.  MEP and Structural hopefully would be available when released.
Currently, you cannot open Revit Architecture or Revit MEP 2012 in Project Spark. Files created in Revit are not supported in Project Spark. However, Revit 2012 files can be linked into Project Spark.
You also cannot open Project Spark files in Revit Architecture or in Revit MEP 2012.  Because Project Spark uses a newer Revit file format, it is not currently possible to open files created in Project Spark with Revit 2012.

They're looking for feedback on the overall concept, usability, and learnability of the product.

You can download the preview here.


You can view the tutorial here

Easily share your BIM with eTransmit for Revit

Here is a snippit from Autodesk Lab's website...

With eTransmit for Revit, you can:

• Copy and detach a Revit model and associated files to a single folder for internet transmission. This removes the typical error messages when you copy central files using the operating system.
• Locate dependent files automatically and include them in the transmittal folder, reducing the possibility of error. All dependent files are automatically converted to use relative paths to ensure that the dependent files can be located by the model.
• Choose to include related dependent files such as linked Revit models, CAD files, DWF markups, decal images, and external keynote files. You can transmit any Revit (.rvt) model that has been upgraded to Revit Release 2012.
• Transmit models that are using file-based worksharing or server-based worksharing. eTransmit for Revit will also work with non-workshared Revit models.

Common uses for eTransmit

• Internal archiving
• Sending deliverables to clients
• Model exchange between consultants/partners
• Model cleanup
• Sharing models between disciplines

Availability

The technology preview will operate until December 31, 2011.

More on the Revit Server Extension

To get a better idea about Revit Server, check out this video from the Revit Clinic Blog

http://revitclinic.typepad.com/my_weblog/2010/10/10-things-to-know-about-revit-server.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+typepad%2Ftherevitclinic+%28The+Revit+Clinic%29

The New “Revit Server”

Link to AECbytes "Revit’s New Server Extension" Article (September 28, 2010) by Lachmi Khemlani.  Lachmi Khemlani is founder and editor of AECbytes. She has a Ph.D. in Architecture from UC Berkeley, specializing in intelligent building modeling, and consults and writes on AEC technology. She can be reached at lachmi@aecbytes.com.

The Autodesk® Revit® Server Extension helps geographically dispersed teams more easily collaborate on projects of varying size and complexity. Web-based services help keep teams coordinated as they work on a single project from separate locations.

The Autodesk Revit Server Extension helps you to:

• Work more effectively as a single project team over a distributed wide area network (WAN) with higher performance and efficiency
• Maintain a seamlessly integrated collection of Revit central models on a single server that team members can access from local servers
• Easily manage products on Revit central server using the web-based Revit Server Administrator tools
• Benefit from built-in redundancy in case of WAN connectivity loss

This Subscription Advantage Pack consists of two separate components: an application update, Revit 2011 SAP, and a server component, called Revit Server 2011. An installation of Revit Server may function as a local server or a central server. However this document does not draw any distinction between the two, as the installation and removal requirements are essentially the same for both.

Revit Server 2011

Systems hosting Revit Server 2011 must have:

• Microsoft Windows Server^® 2008, 64 bit (not 2008 R2)
• Microsoft IIS 7.0
• Microsoft .NET 3.5 SP1

Refer to the Revit Sever Installation Guide supplemental documentation for more detail on system prerequisites.

Revit’s New Server Extension 2011 Video

Dependent Views, Matchlines, and View References in Revit: by Reid Addis

Dependent Views, Matchlines, and View References in Revit

Author: Reid Addis, Microsol Resources
Date Published: March 24, 2009

Autodesk University Article Link

Dependent Views were added to Revit in Release 2008. The concept behind Dependent Views is to allow you to maintain consistent annotation and View Scale among the main and dependent views while permitting independent crop regions for each view. A secondary result is that Dependent Views allow you to place different cropped portions of the overall View on different sheets while maintaining consistency of annotation and scale across sheets.

Normally when you simply Duplicate a view with Detailing, all of the annotation (text, dimensions, tags, etc.) become independent from the original view along with the View Scale. Thus if you change the value of the original object (adjust a dimension or edit text or delete a Room Tag) in one view, it has no effect on the duplicated object in the independent duplicated view.

This is not the case with Dependent Views. The annotation and view scale are identical across all the views. Change the view scale in ANY dependent or parent view, and it changes the view scale in ALL the dependent and parent views. In addition, the annotation is identical as well, so a change in ANY view again affects that same object in ALL views.

Using the “Getting Started” tutorial that comes with Revit Architecture 2009, I’ve created some Dependent Views of the Lower Level:

View 1

For clarity, I’ve turned on the Crop Region in the Parent View and added some Filled Regions to show the Dependent View Crop Regions. The “purple” area in the center indicates where these two regions overlap. This is where we will add a Matchline and View References in the Parent View to help coordinate locating these adjacent views when placed on different sheets.

Below are the two Dependent Views with the Matchline displayed that was added in the Parent view from the Drafting rollout of the Design Bar:

View 2

In the Parent View, from the Drafting rollout on the Design Bar, I will place a View Reference on each side of the Matchline.

View 3

Notice that as you place the View Reference, the Option Bar gives you the ability to specify which Dependent View is being referenced. Thus the View Reference placed in the West view will target the East view, and visa versa.

Equally critical is making sure that you actually have a Tag loaded from the View Reference Family. By default, this is set to and thus will fail to work.

View 4

The final step is to place these Dependent Views on Sheets, then watch how the View References update to include this information.

View 5

Notice that the View References now show which View and Sheet number the Matchline adjacent view is on.

View 6

I hope this clears up any confusion you may have had about Dependent Views, Matchlines, and View References.

New Version of Trimble MEP Field Software Enables Faster, Easier and More Accurate Layout of Conduit, Pipe, Duct and Cable Trays

Trimble MEP 2.0 Field Software Introduces Significant New Features to Benefit Mechanical, Electrical, and Plumbing Contractors Working in Building Construction Applications

ORLANDO, Fla. -- Trimble introduced today a new version of Trimble® MEP Field Software for Mechanical, Electrical and Plumbing (MEP) contractors. Trimble MEP 2.0 is the world's first layout solution designed specifically to allow contractors to take digital CAD design file or 3D Building Information Model (BIM) into the field to simplify the layout of conduit, pipe, duct and cable trays. The new version of Trimble MEP Field software can increase the contractor's productivity by reducing rework by facilitating faster, easier and more accurate layout.

The announcement was made today at the AHR Expo 2010, the world's largest show targeting air conditioning, heating and refrigeration contractors.

The Trimble MEP 2.0 field software introduces new, industry-unique functionality to further assist mechanical, electrical and plumbing contractors in bringing rich digital design data directly from the office to the job site. Version 2.0 affirms Trimble's commitment to creating a seamless and more efficient solution for customers. Significant new features in Trimble MEP 2.0 include:

-- The ability for users to create points directly from a DXF file into Trimble MEP running on the Trimble Nomad® Controller. Previously, points had to be created on a PC or via other methods. This critical new function enables mechanical, electrical and plumbing contractors to respond to situations on the job as they arise without having to return to the office, which can provide significant time savings and increased efficiency.
-- The Direct Reflex (DR) Layout feature makes locating points on a deck or overhead fast and efficient because users do not need to know elevation in order to achieve an accurate location--Trimble MEP determines the elevation automatically and turns the total station to the correct position. Enhanced DR Layout in version 2.0 extends this capability to walls: regardless of the orientation or design of a wall, Trimble MEP 2.0 will calculate the correct location for piping, duct and other wall penetrations. By eliminating the need for manual calculations and multiple instrument setups, Trimble MEP 2.0 can deliver greater efficiency. In addition, the DR range of the total stations has been significantly increased, allowing contractors to reach further on the jobsite.

These and additional new features in Trimble MEP 2.0 Field Software are designed to meet the needs of mechanical, electrical and plumbing contractors, to deliver streamlined data flow from field to office.

Trimble MEP Field Software version 2.0 is available now through select dealers in Trimble's North American Building Construction distribution network.

About Trimble's Building Construction Business

Trimble's Building Construction Division is a leading innovator of productivity solutions for the building construction contractor. Trimble's solutions target site prep, general, concrete, mechanical, electrical and plumbing contractors on large and small commercial, industrial and residential jobsites. Trimble is focused on delivering solutions that tightly link office based process and information with the field crew--including taking Building Information Models (BIM) and other design data to the field for highly accurate positioning and layout of foundations and mechanical, electrical and plumbing systems. Trimble solutions provide a high-level of process and workflow integration from the design phase through to the finished project--delivering significant improvements in productivity throughout the building construction lifecycle.

About Trimble

Trimble applies technology to make field and mobile workers in businesses and government significantly more productive. Solutions are focused on applications requiring position or location--including surveying, construction, agriculture, fleet and asset management, public safety and mapping. In addition to utilizing positioning technologies, such as GPS, lasers and optics, Trimble solutions may include software content specific to the needs of the user. Wireless technologies are utilized to deliver the solution to the user and to ensure a tight coupling of the field and the back office. Founded in 1978, Trimble is headquartered in Sunnyvale, Calif.

For more information Trimble's Web site at www.trimble.com.

CONTACT: Willa McManmon, Investors, +1-408-481-7838, willa_mcmanmon@trimble.com, or Lea Ann McNabb, Media, +1-408-481-7808, leaann_mcnabb@trimble.com; both of Trimble

You don't need Navisworks to create Navisworks NWC files from your AutoCAD or Revit models.

The distributable NWC file exporter program enables project teams using Autodesk Naviswork software to generate whole-project models for simulation and analysis. Project team members can generate the optimized NWC file directly from their design applications. This capability is provided without necessitating a licensed seat of Autodesk Navisworks 2010 software on the same machine. The NWC exporter works with a range of products, including the AutoCAD-based and Revit-based Autodesk products, as well as Autodesk 3ds Max, Bentley MicroStation, and Graphisoft ArchiCAD software. The NWC file format supports transfer of both object geometry and associated metadata from the design applications into Autodesk Navisworks 2010 software.

Click here to download the exporter program


Using NWC File Exporter Pack

The NWC file exporter pack enables project team members generate the optimized NWC files directly from their design applications.

The NWC file enables transfer of both object geometry and associated metadata (such as object properties and materials) from the design applications into Autodesk Navisworks 2010.

The NWC exporter pack works with a range of products including AutoCAD-based applications, Revit-based applications, 3DS MAX and Viz, Microstation, and ArchiCAD.

You can distribute link to a download page for the NWC exporter pack to any project team member.

To export an NWC file from an AutoCAD-based application

1. To export an NWC file, type NWCOUT at the command line in the design application.
2. Press Return.
3. In the Save As dialog box, enter the name for the file, and browse to the desired storage location.
4. Click OK to export the file, or Cancel to return to the application without exporting it.
   

To export an NWC file from a Revit-based application

1. In the design application, click Tools ➤ External Tools ➤ Navisworks 2010.
   NOTE This option is not available in Demo/Viewer mode. If you are not in demo mode, but do not have access to the Navisworks menu, check if editing view is set to normal, and the modify tool is selected (Edit ➤ Modify).
2. In the Export Scene As dialog box, enter the name for the file, and browse to the desired storage location.
3. Click Save to export the file, or Cancel to return to the application without exporting it.
   

To export an NWC file from 3DS MAX or Viz

1. Click File ➤ Export.
2. In the Select File to Export dialog box, select Navisworks 7 Cache (*.NWC) in the Save as Type field.
3. Enter the name for the file, and browse to the desired storage location.
4. Click Save to export the file, or Cancel to return to the application without exporting it.