Keeping with this week's theme of everything not related to the ribbon UI, I want to introduce a product enhancement that has been overshadowed by all the talk about the new UI: Autodesk Seek. Seek is a web service that allows designers to search for (and now submit their own) content to be included in their Revit projects. Files are in a variety of formats, depending on the source. Seek was introduced first as an Autodesk Labs project called Content Search (check out the Labs blog for more history) and then "graduated" to a full-fledged service two years ago. It was first integrated into Revit 2009 and has been enhanced in the following ways:
- Most of the old Revit Web Library Content Library material has been migrated to Seek (the old site is on it's way out.)
- You can now search from within Revit from the Insert tab
- You can share your family content with the Seek database by clicking Application Menu > Publish > Share with Autodesk Seek
- Added Omniclass categorization to all Revit Families and provided ability of Revit family creators to add the Omniclass category to their families
A recent thread on AUGI has raised some interesting issues regarding the appropriateness of firms sharing their family content and also if/how the quality of content will be monitored. What are you thoughts on this topic? Would you share content with others on Seek? Do you trust the content you see appearing on Seek? With what criteria would you judge the qaulity of this content? The Seek team is listening, so let them know what you think.
I think Autodesk have put the cart before the horse on this issue.
Rather than thinking about how users can share content, Autodesk should be concentrating more on how users can manage their *own* local content stored on their LAN.
Autodesk needs to apply the same principals and displayed information they have done for Seek (online) and somehow build that into the Autodesk products to search a local folder structure.
Posted by: Chad | April 28, 2009 at 07:11 PM
Ditto
Posted by: David Baldacchino | April 28, 2009 at 09:18 PM
I agree totally.
We have a management problem with keeping various content libraries available. I'm sure others do things differently, but we have 3 possible libraries available for each project - bit of a nightmare for our users to search:
1. Metric library as supplied by Autodesk - this gets totally replaced with each version (but old libraries also kept available as content varies dramatically each year - possibly depends on what is ticked with the content install)
2. company library which we keep separate from the Autodesk supplied library. Our company library only contains families that our BIM managers have vetted or created, and all families follow a strict naming convention and a folder structure like the best Autodesk supplied metric library (v2008 or 9.1 I think. v2009 & 2010 Aus metric library structures are a mess again).
3. We also have project libraries which any user can add to or edit - hence full of stuff of unknown usefullness to others.
I just can't think of a better system that allows us to manage and annually update part of the library without disturbing our company library.
Posted by: Tim Waldock | April 29, 2009 at 07:37 AM
I think the thread on AUGI makes some great points, and i think its commendable that you are all actively seeking out our opinions. I hope they can really implement some of our suggestions!
Posted by: Aaron Maller (twiceroadsfool) | April 29, 2009 at 08:42 AM
It's time for manufacturers to come to the table and start building quality Revit families. And that will require them to be proficient at family building -- just like a lot of CAD blocks out there are crap, families (what with the 3rd dimension) can be awful or fantastic.
We don't use Seek. We've already got products in mind and our efforts on Seek haven't got us what we're needing. So like the others, an in-office content management tool would be awesome.
Posted by: Wes Macaulay | April 29, 2009 at 04:14 PM
Wes, point taken about local content management. Two questions: what "products" were you referring to? And can you say more about your efforts to work with Seek and where in particular did it fall short?
Posted by: Anthony Hauck | April 29, 2009 at 04:23 PM
I think even with manufacturing "quality" content is an issue. Manufacturers generally like very high quality content that may not appeal to many firms. Not only that the symbology and overally look may not be aligned with current company standards. Manufacturered content would need to be built to a strict set of rules worldwise otherwise people will simply grab items shift and shape them, and not bother downloading the latest version of the product as it would require time to upgrade.
Posted by: Adam Sheather | April 29, 2009 at 06:12 PM
"Manufacturers generally like very high quality content that may not appeal to many firms."
I'm not sure if I am reading Adams comment correctly (?), but I can see how manufacturers who produce content will think that having a "highly detailed" family equals "high quality", when this is not necessarily true.
I've seen quite a bit of manufacturers content over the years which is so highly detailed that it has a negative performance on the project. So this then comes back to how external content affects your own projects.
I reckon you would almost see competitions between manufacturers of "my content is better, or more detailed than yours", but in reality they all suck because they are unusable.
Here, we have small housing projects in which we *can* have fairly detailed families because the PCs can handle it, but on the high-rise projects this same content has to be absolutely bare bones information to portray the minimal amount of information, to provide maximum performance.
So while a shared online family might be as accurate as can be, and may even meet company standards, the level of detail that goes into it is still an issue, and still very much company and/or project driven.
Online, shared content will only ever be a starting point, or for limited use. And this is why more focus should be directed towards local content management by Autodesk. Local content management is the place where the rewards will be mostly gained for the customer, not online.
The way I see it, services such as Seek are nothing more than a marketing tool used to encourage misguided manufacturers who don't understand the final consequences their "quality" content has in a production environment.
As a result of these manufacturers producing content, Autodesk now have more leverage to entice new users (who typically don't know any better) over to Autodesk products, by advertising how much "quality" content they have available for users to download.
So it's not really about content for the customers, but rather marketing material via a service for Autodesk.
Posted by: Chad | May 01, 2009 at 12:57 AM
Lack of local content has been a pain for user outside of USA centric CD deliveries by Autodesk. Good work put in years ago (aka v7 and 8) have not been kept up to the point where stuff on the official 2009/2020 cds are obsolete, non code compliant etc such as to turn prospects and users off from buying Revit and if they do, forcing them to have to make families straight away - eek! for a new user.
Turbosquid is doing a good job here providing an alternative delivery method - should be promoted by Autodesk over manufacturer's market driven Seek.
As to the new feature allowing an Omniclass code parameter field - we have lobbied for years to have the Assembly Class product index system opened up/documented/user file specified for other non-USA Geo conventions.
Instead we get yet another hard-wired facility that is not used in our part of the world which is successfully/heavily Revit focused/adopted in the building design industry. We wait again.
Posted by: Rich Sales (Director Salesoft CAD Solutions - Revit developer) | May 06, 2009 at 02:00 AM
I wouldn't trust an online content library that allows uploads by just anybody. As mentioned in the previous posts, the problem is with inconsistent family creation, dissimilar parameters, too much detail built into the file, and unnecessarily heavy files to name a few.
What might be useful for a firm during the early stages of implementation is a simple clean library that is built to strict parameters and keeps the families lean and basic. Beginner firms could use that with confidence, and build on them for their own libraries as they increase their expertise.
Firms that have been using Revit have developed their own standards and an online library is of limited use.
Posted by: Rachel N | May 12, 2009 at 06:48 PM