Showing posts with label Collaboration. Show all posts
Showing posts with label Collaboration. Show all posts

May 10, 2012

BIM Coordinator

Autodesk Labs have a new product to assist with coordinating Revit with Civil 3D.  This new add-in tool will allow the coordinates inside of Civil 3D be saved out as an external file, that can be imported into Revit to acquire the Shared Coordinates.  This process appears to work without having to import the actual Civil file.  A quicker, simpler way to make sure you Revit model has the correct coordinates.


The add-in app is written for release 2012, but I copied it to my 2013 version and it appears to work correctly.

Check it out!



February 20, 2012

BIM vs. U.S. Army Corps of Engineers?

BIM, to most of us designers, has seemed to be a very slippery slope when dealing with the USACE.  Many of our clients have had the same conversation with us (repeatedly) when trying to respond to an RFP.  They are continually faced with the frustration of wanting to use Revit, but falling into the trap of still having to deliver the final product in "native Bentley format," as is written in many of those packages.  Yet sometimes, just sometimes, we find one or two where Autodesk Products are acceptable, or even mandatory.  But most of the time, the conversation always ends with, "Well, what do you think we should do?  Is there anyone to appeal to?"  No. . . And yes.  Let me explain.

The USACE is NOT against BIM; so this isn't an "us vs. them" or "them vs. BIM" situation at all.  The fact is that they completely understand the need for it; but need to be very clear as to where it is important, and what flavor of BIM, or CAD, is needed in certain situations.  They also have standards that must be adhered to so that FM functionality can be maintained throughout their vast portfolio of buildings. The standards are really based on two primary things: the project type and the 'client.' You see, the USACE handles two major clients for which they procure the buildings and provide FM services: The Air Force (USAF) and the Army.  There are also some sub-components that modify how flexible the client may be to the format of the final delivery - regardless of what the designers or the end user (tenant) may want.

There are two major rules of thumb (and a couple of sub-rules) to follow based on the above.
  1. If it is an Army project, you can be 90% sure it will be done in Bentley.
    • If it is one of the Centers of Standardization (COS) building types, shown in the image below, you can be almost 100% certain it will be delivered in Bentley.
    • If it is not one of the COS building types there will be room for Revit or other applications. These include projects such at VA Buildings and various others.
    • Regardless of whether the local base managers in California (or wherever) REALLY want Revit on a project, they still must answer to the lead district that controls the COS.
  2. If it is a USAF project, you can be 90% sure, or greater, that it will be done with an Autodesk product because that is what they have as their standard.
There is also a third rule:

     3.  The RFP is final.  The USACE know what they want and know where they are willing to        compromise.  If there is "wiggle room" for Revit, it will be in the RFP.  PERIOD.

There are 41 COS products divided between 8 USACE Regions.  Each Region is the controller of that particular COS and each "Tenant" must answer to the Region that controls it.

That's it.  Pretty straightforward and easy to understand, if you ask me. In the end, it is up to you if you want to try to use Revit and then convert the files to Bentley, or if you even want to respond to the RFP.
The USACE has always supplied a vast amount of work for the AEC world, and will continue to do so.  Hopefully these rules of engagement will allow you to make better decisions in pursuing USACE work and, in the end, how to work better with them.

Pete Zyskowski

January 16, 2012

Design Review Mobile App

There was a time when I can remember preparing for a meeting or even going to the plant to discuss design and engineering issues with multiple detailed drawings in my hands and needing someone to aid me in opening doors. However, with today's technology, the burden of lugging around loads of documentation is becoming a thing of the past. With more and more people starting to make the move to mobile devices and discovering the vast world of apps available, I would like to point out one specifically which allows you to view, markup, and annotate 2D and 3D DWF files from your Autodesk Cloud account. It is the Design Review mobile app by Autodesk, Inc. and it is available for the following devices: iPhone 3GS or higher, iPad 1 or 2, iPod Touch 3rd generation or higher, with a minimum operating system of the Apple iOS 3.2.




Links for Referenced Material:

 
-Jason Miles

January 5, 2012

Why BIM? . . . Again?

I was recently asked by one of my sales people to craft a quick overview of BIM trends that would make someone want to use it.  I had a couple of gut reactions and some realizations:

Gut Reaction 1:  I am over it.  Do we still have to have this discussion?  It's a five-year-old question.

Gut Reaction 2:  The industry is past it.  The talking heads are now arguing about what is after BIM and are coming up with ridiculous things like "BIM 2.0" and 7D, 8D, 9D and XD models.  (How many dimensions can there be?  This isn't quantum physics, people.  I'm going to create a String-BIM theory just for my own amusement.)

Realization 1:  The industry is NOT past it.  While we now have the talking heads dithering about "BIM 3.0" and 99D models, we still have parts of the country and world where BIM is VERY NEW.  We still have owners that have no idea why they should (or should not) be using it.  There is no NEXT BIM.  There is only refining it and building upon the idea to make it better.

Realization 2:  I am NOT over it.  I am over BIM, the singular, "solve anything" application.  But not over BIM as a team based, data rich set of processes that can help solve many relevant industry problems. While my frosted side wants to dance and splash in new discoveries and uses for BIM data, my crunchy, wheat-y side realizes that we still need to evangelize, but differently than we used to talk about it; with more understanding, foresight and relevance.

The following is my initial response to this request.  It needs some additional word-smithing, and doesn't go very deep at all, but I think this is the basis of what the next generation of BIM adopters needs to understand to get on board and quickly catch up or even innovate upon current understanding.  Based on what we have seen, each new wave of adoption is better than the last.  We shouldn't dismiss these later waves of BIM adopters, but realize that their new energy in learning applications that have had immense amounts of additional development could make them better than early adopters whose skills and BIM usage may have hit a plateau.  These later waves also have something that the early adopters didn't have - the backing and desire of a more educated client to do better:

"BIM isn't the trend anymore.  To be quite frank, we are past that.  The real drivers towards BIM adoption now are synergistic uses that go above and beyond simply having a 3D model of a building that we can collide.  The current BIM catchwords are really focused on modern operational and economic issues that are the true underlying issues that BIM can help to solve. 
  • Efficiency:  Let's be honest: The economy is still in the dumper.  There are some bright spots, but let's not get too excited because it will never be the same.  The construction industry loses a massive amount of money every year to wasted effort and time, not to mention materials.  Some estimates are as high as 40% of profits are lost to lack of efficiency.  This is unforgivable – even in the best of times.  BIM, due to the nature of being able to view, quantify, and share helps eliminate over-purchasing and rework in all phases of the building life cycle.  Additional ability to visualize construction sequencing helps ensure timely and safe construction of the building.
  • Sustainability / Energy Analysis:  Green design is about data – Calculations, weights, locations, volumes, etc.  BIM, with its ability to tie that information to 3D geometry (which is just now really being harnessed by design teams) can provide a powerful synergistic relationship for providing sustainable design and analysis.  This data can also be used further downstream by owners (See FM / O&M).
  • Partnering/Integrated Processes:  The ability to share project data and design concepts is not new to CAD software, but the ability to more clearly see design decisions, data and analyze their effects is compelling in many ways.  From the designers to fabricators to owners, the entire project team can be involved in ways that are heretofore unprecedented.
  • Facility Management / Operations & Maintenance:  If an owner has a clear understanding of Facility needs, the BIM can be the backbone of a strong FM / O&M initiative.  What better place to tie the data to than a virtual model of a building or campus?  Things such as manuals, maintenance schedules, real time energy monitoring, asset management, space allocation can all be tied to a BIM and vice versa.  The industry is just now beginning to really see the need for "portals" to tie all of this data together for greater operational efficiency and knowledge.  This is the stuff of science fiction that is happening now.  
  • Standardization:   BIM has the capability to standardize . . . . everything.  Several large companies from Starbucks to Target are standardizing on BIM.  Giving them an edge over competition with some of the FM uses above, but also the ability to visualize remodeling, signage, displays, etc.  The industry as a whole would benefit from manufacturers creating standardized BIM models of everything from tables to pumps to furniture that will contain all the data needed for purchasing, quantities, LEED and much more.
These things are synergistically tied to each other as well.  Solving one issue tends to solve the others. BIM is not THE THING, but a tool that helps foster greater understanding and solutions to the real problems listed above and more.  In our own experience we are training BIM tools at a 4:1 rate over traditional CAD applications.  The classes are getting more specific and targeted on a weekly basis.  Additionally, we are now working with owners in commercial, educational, and government spaces helping them craft their own BIM requirements and corporate BIM Execution Plans – which is possibly the real trend.  BIM isn't about marketing brochures or colliding 3D pieces anymore.  Owners are starting to understand how it can help them generate efficiency, design sustainably, foster partnering, standardize data, trim operational costs and reveal new understanding about how they use their spaces.  Now that I think about it, that's not a trend, that's finally getting it right." 

-Pete Zyskowski

December 21, 2011

eTransmit for AutoCAD

Ok, so I saw Pete write a blog about eTransmit for Revit. As an old AutoCAD user, I felt the need to write about eTransmit for AutoCAD; the original eTransmit. And before that, Pack-n-Go.

I want to write about a feature few people use but is still very POWERFUL. You should feel and hear a deep dark voice as you read the word POWERFUL.

You can use eTransmit to not only automatically compress all your AutoCAD drawings into a .zip file or a self executible .exe file, BUT AT THE SAME TIME you can use e-Transmit to AUTOMATICALLY save your AutoCAD drawings to an older DWG version within the .zip or .exe file. Your orginal DWG files on your computer or on your server are not saved back to an older version, only the copies made part of the zip file are converted. So when do you think that will be a feature in Revit's eTransmit?
Mark Petrucci

December 19, 2011

eTransmit for Revit

While we haven't experimented with this yet, this may be worth checking out.  Autodesk Labs has released an update for Revit eTransmit.  Everyone gets nasty messages from a workshared Revit model when you are the one that is getting a file from a consultant. Hopefully, this makes sending (and receiving) the Revit file a bit easier - and makes sure that everyone is getting the right info.

From Autodesk:
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, helping to reduce the possibility of error. All dependent files are automatically converted to use relative paths so 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 beenupgraded to be compatible with a 2012 Revit software product.
  • Transmit models that are using file-based worksharing or server-based worksharing. eTransmit for Revit will also work with non-workshared Revit models.
View of the eTransmit dialog.





















-Pete Zyskowski

December 15, 2011

PLM for the masses, courtesy of Autodesk 360 Nexus

Every company, whether manufacturing a product, designing a building or providing a service (IT, consulting, etc.) has a concept, a plan, process or design reviews, and procedures related to the startup, production, management and pass-off or completion of their product, building or service. And all aspects of that lifecycle ideally should be documented and accessible (at various permission levels) throughout the entire organization.

Some of the traditional objections to implementing PLM have been the massive infrastructure and investment in costly programming needed to link disparate and non-communicative technologies. Try connecting Vaulted Inventor assembly data to an ERP system based on a "home grown" AS400 platform for example...it works about as well as Monty Python's Hungarian at the Tobacconist using an English phrase book. And if you don't know how that sketch ended, look it up on YouTube - not pretty!
This is where Autodesk 360 Nexus appears to have an ingenious way of clearing the hurdle mentioned above - by keeping the data inside the firewall and providing a Cloud based, zero infrastructure investment model whereby anyone collaborating or doing business with a company can view data about various stages of the lifecycle, from virtually anywhere.

When considering Autodesk’s diversification and continued gains in the markets as a software provider to the AEC, manufacturing and M&E (media and entertainment) segments, tight integration of Nexus 360 with their mature Vault and Buzzsaw product lines is a given.

So when you start hearing the term PLM, don't think that it's limited to manufacturing companies, or only Product Lifecycle Management. It is about to become whatever you need it to be...

Learn more at http://usa.autodesk.com/360-lifecycle-management-software/plm/, and sign up at the top right of the page for information as this exciting new offering from Autodesk takes shape.

December 12, 2011

Autodesk's 360 Nexus PLM solution - Changing the landscape for the SMB market


While en route to the first of 4 Innovation Forums at Autodesk University this year, there were 2 buzzwords that I knew I'd hear many times during the conference: "Cloud", and "PLM". And while the former certainly has multiple definitions, the latter has traditionally been defined as Product Lifecycle Management. However, with the launch of Autodesk 360 Nexus, PLM may soon be democratized and more accessible to SMB (small to medium sized businesses) than ever.

First, let's distinguish the differences between PDM and PLM. At it's core, PDM focuses on the data involved in the design and manufacture of a product, and therefore, is most important to those divisions of an organization. In more progressive firms, the data is shared with sales, marketing and ERP, though frequently as a non-collaborative, one way push. Many clients of ours have a PDM system courtesy of the Autodesk Vault, which is an engineering centric tool for data management.

But PDM, through Vault, DBWorks or even Windows Explorer (yikes) is merely one component of PLM, which focuses on the lifecycle of a product, from concept to retirement. With PLM, each division of a firm is a participant in the product, including
documenting its origin
  • versioning its iterations 
  • releasing the manufacturable content for build 
  • itemizing the purchased and manufactured parts for accounting 
  • creating service manuals, sales and marketing content 
  • And finally, maintaining the product once sold in the field, until ultimately being withdrawn or replaced with a newer product line.
If you're in a manufacturing company that fits the criteria above, then the traditional PLM acronym certainly applies. But given that the "L" stands for lifecycle, if we consider the functions of non-manufacturing firms in relation to my laymans definition of PLM,, then why couldn't the "P" stand for "people", "project" or even "process"?

If this concept can gain traction in non-manufacturing firms, THIS is where Autodesk may revolutionize the PLM market.

Next time - "PLM for the masses, courtesy of Autodesk"

November 29, 2011

Revit Server Between Different Companies? It's Do-able!

Revit Server.  Let's review quickly what it was meant to do and the problems that it solves.  Then we'll take it to the next level.

Revit Server was designed to help a SINGLE company with distributed, satellite offices work on a single model.  In that scenario, everyone is on the same wide area network with no worries about security or other IT issues to get the server up and running.  In the traditional model to the left, we are using some sort of VPN for synchronization, or an FTP site to share a model that has been sliced into pieces so that each office can work on their piece of the project.  This can work, but only if the pieces of the puzzle are cleanly delineated, which is very rare on a project of the size and magnitude that would require

November 17, 2011

Navisworks Batch Utility

The Batch Utility can be used to automate importing and conversion processes that are common tasks within Navisworks. There are four areas that the batch utility can assist: getting a list of design files used in a current NWF/NWD, build a new NWF/NWD with selected design files, export out NWDs for each design file listed, and accessing the Windows Scheduler to run the batches. As an example, I will select various NWCs to build a new NWF.


The Batch Utility is accessed from the Home Tab:













First, in the Input section of the dialog, I will select a specific NWC file that contains all the architectural models using the Add Files button:





November 15, 2011

T.O.S. vs. F.F.E. – What’s your pleasure?



Top of Steel (T.O.S.) or Finished Floor Elevations (F.F.E.) Why do you ask? A recent debate has been going on with architects and engineers on what is the typical datum level to reference from.

There are pros and cons potentially to setting up levels at FFE vs TOS. The first would be coordination and the chance for human errors. Also depending if you are an in the architectural discipline as an Architect vs. the structural industry as a Structural Engineer.

What is the industry standard?
An architect would say FFE. This however does not include carpeting, tile, etc. This is the floor to floor heights.

An engineer would say TOS. This is what is usually built first and erected in the field. Even if the steel is sloping, the TOS reference datum plane is still established.

So how can we, from a technology, computer BIM application benefit, or should I say coordinate this industry dividing quandary? Constraints are a wonderful option when looking at Revit (Architecture, Structure, and MEP) for a solution.

Using Existing data
What if we are using the other discipline's file and linking them in the model, and the levels are already established? Linking and Copy Monitor tool. Copy monitor allows users of different disciplines to do just what the name implies “copy” the existing levels, and then allowing the user to move/offset the level to their specific location, for their needs. The levels can then be constrained so if there is movement from either disciplines, a notification will be presented.
Which ever method you choose, Revit has the tools built-in to help you accomplish you needs and coordinate other level references, allowing you to focus on your project.

BIM floor level datum lines should be: