Autodesk University 2022 – The Good, The Bad and The Ugly

Autodesk University 2022 is a wrap. First live event since 2019. This year, it moved from Las Vegas to New Orleans. Folks had a lot of mixed feelings about this event. Including victimization of some attendees. I won’t rehash what someone else has done so for a good review of how the “Event” went, give this 20 minute recap a watch. Neil Cross does a bang up job recapping this poorly organized event. https://www.youtube.com/watch?v=StEtDbUxHV0


New Orleans – The City

I’ve been to New Orleans before. Stayed at the same hotel in fact. New Orleans Hilton Riverside. It was about a decade ago. Really enjoyed the city so I was looking forward to going back.

Honestly, I really like the city….much more so than Las Vegas. The Architecture is amazing. Neighborhoods rich with character and culture. Great music and most of all, some of the most amazing food I’ve ever had. I find the people in general are warm and kind. I think my ride from the airport was the the best Lyft ride I’ve had of any city. Linsey was a pleasure to converse with during the trip.

While my Monday arrival was warm, the weather the remainder of the week was pleasant. A result of Hurricane Ian pulling cooler air from the north. I think we lucked out that it wasn’t hotter and more humid.

Now while I personally like the city, it is well known as a corrupt and violent city. If you listened to the video link above, you’ll know this crime affected several attendees. People drugged and mugged. Robbed at gunpoint and knifepoint. One attendee was stabbed. Even the legendary God Father of Autodesk Fabrication CADmep had someone try to pick pocket him. You can see his post here.

Knowing all this, I would go back to New Orleans…the city. Perhaps I’d view it differently if it happened to me. But while I grew up very rural, I did grow up with a lot of violent crime. By the time I graduated high-school I’d had over a dozen connections with people being killed. While I don’t make excuses, I do have an understanding of the effects of poverty. Perhaps that’s why I still felt comfortable in New Orleans. I grew up around people like this. The good and the bad. Frankly, I felt WAY more safe walking around in New Orleans than I do in Seattle. For me, New Orleans is an upgrade. Your mileage may vary.


New Orleans – The Convention Center

The New Orleans Convention is the 6th largest in the US. Despite that, I don’t think it was built to host a single large event…rather multiple smaller events at the same time. Halls were narrow leading to over crowding. 20 minute line to get up the escalator the first day. Remaining days people seemed to self adjust.

But the convention center is LONG and narrow. Not stacked like in Las Vegas. Took forever to get anywhere. With room attendants not letting people in early, it led to even more crowded halls.

Even the rooms themselves were typically smaller. Much harder to “Sneak” in or out if the class wasn’t what you wanted. A more frequent even this year than most.

While convention center food is never top notch, even in Las Vegas, it was particularly low quality here. A surprise considering the quality of feed elsewhere in the city. One morning, the breakfast burritos were so starchy it made a McDonalds seem like a Michelin 5-Star Restaurant.

Bottom line, if they continue to have AU at this convention center as it’s rumored to be, it’ll have limited success. This just is NOT the venue to host Autodesk University IMO. The facility and services are just not up to par.


Expo Hall

Expo hall was what you’d expect. I’d venture to say half the space was utilized by Autodesk. Mostly wasted IMO. There’s only a couple places where I’d typically go to meet the product teams. The rest is of no value to me. Taking meaningless surveys or other low value activities Autodesk marketing thinks are worth while. Letting users think they’re impacting direction while nothing meaningful changes. Nothing that’s going to improve your professional life IMO.

Expo hall ran out of food within the first 30 minutes of lunch on the first day. No refills of the buffet tables like you see in Vegas. As lunch started 1/2 hour before the General Keynote ended, everyone came out to an empty food line. This means the remaining days people left the Keynotes early to ensure they were fed.

One disappointing thing was finding the UA’s Trade Exhibit was micro managed. They wouldn’t let them operate much of it. GTP’s Stratus booth was right down the row. Both with people walking by not quite getting the connection unless you were from the MEP Trades yourself. Not sure if this was the Convention Center Legal or Autodesk Legal but it was a missed opportunity in my estimation. Especially considering a few years back Titan’s of CNC were throwing chips from their CNC equipment. Had they showed the Tigerstop running from Stratus and hearing the buzz of copper or PVC cutting….it would have drawn people to the back where they were stuffed and really connected the dots IMO.

For the most part, any booth worth seeing was hard to see as they were very busy. I tried going to DiRoot’s both multiple times only to find them overwhelmed with interest. Other booths seemed pretty slow. I stopped by one booth from a vendor from Finland. After 15 minutes of a demo and them talking, I still didn’t know what they hell they did or what he was saying. Ironic considering I grew up in a part of the Michigan listening to Suomi Kutsuu (Finland Calling) on Sunday morning television as a kid. The US’s only Finnish language programming.


Classes / Sessions

Sessions this year were absolutely abysmal IMO. That said, the speakers were generally high quality and presented well. It was just the topic selections were utter rubbish. To the point I almost didn’t bother attending AU at all. Ultimately, I remembered that its the networking and face time w/Autodesk product managers not the classes that have me coming back.

Still, every AU there’s some good classes. This year, anything worth taking was full. As one long time Autodesk University speaker told me, they’ve never had their sessions repeated before. Their take was there was nothing worth taking so everyone signed up for theirs.

Another former coworker texted me…

“I felt Tuesday sessions were sub-par so went on a walking food tour of the city instead”

I ended up either skipping or walking out of all but 4 of the sessions I had scheduled not counting the panel I was on.

In years past, a group of industry insiders would help select sessions. This year, I’m told it was Autodesk Marketing. This meant that most sessions were beginner or sales focus. As Neil Cross put it…”Thought grandstanding”. Even the descriptions were misleading on many. This is the type of tone many set…

“As a company, it’s our mission to help solve the global climate crisis…..” followed by a lot of nonsense and the last sentence being something like “Learn how we use Autodesk Docs”.

Part of the problem is also the session “voting” after the original RFP’s. Those self promoting their sessions with a large LinkedIn network get voted up vs. voting merely based on merit. I was added to an Autodesk Panel at the last minute this year. None of my proposals were selected. I’m ok with that. I actually don’t like “teaching” the sessions. I do it as I feel it’s important to give back to an industry who’s helped me. If others don’t feel my content is worth while, I’m ok not teaching. But the way some instructors self-promote…they’re clearly in it for their ego in teaching at AU and less for the attendees. I think this contributes to a decline in session quality. You really want someone’s session selected because their Grandma voted it up?

If you look at many of the sessions, clearly the San Francisco Bay area “Woke” crowd and Autodesk Sales Idealism was who and what Autodesk Marketing was targeting. Here’s some of the key phrases you saw littered about the titles and descriptions….

Evolution of Roles” – “Remote Collaboration” – “Sustainable Mfg” – “Saving the Planet” – “ESG” – “Multiverse” – “Carbon Impacts” – “Digital Transformation” – “Society First/Social Value” – “Happiness” – “Leadership” – “Women in BIM” – “Gender, Diversity” – “Inclusion” – “Belonging” – “Global Environmental Challenge” – “Net Zero” – “Strategic Workforce” – “Decarbonization” – “Omniverse” – “Business Models” – “Convergence Customers” – “Talent Trends” – “Productivity Crisis” – “Digital Future of Work” – “Onboarding” – “Upskilling” – “Climate Footprint” – “Reconfiguring for the Future” – “Hybrid Workforce” – “No Planet B” – “Growth” – “Metaverse” – “Enabling Nations” – “Satisfying Places” – “Greenwashing” – …etc…

Not that these aren’t good topics….but this is a Tech conference is it not? It’s now primarily a “Beginner” and “Sales” conference. Very little on how to actually do things. A session of how the software/services can fall short and what to do about it is clearly not on the table any longer.

And lets get real…after 2-1/2 years…we’ve all figured out how to remote work or we’re likely out of business. We don’t need another class on Remote F’ing Work.

All I can say is that if you attended half of this crap, you were are guaranteed to be well prepared to solve everything from World Peace to Feline Leukemia this next year.

Oh, and not to mention, there were no computer labs. Given they handed all registrants a Covid tests to self-report, I can only assume the lawyers shut down the hands on labs.


Reviewing My 4 Good Classes….

As I said, there were 4 sessions I didn’t walk out of. I’ll review them here….

FAB502677 | Design, Develop, Deploy: Create Revit Content from Inventor Designs

This session was presented by Mark Flayler of IMAGINiT. Mark did a fantastic job explaining the options for Revit and Inventor interoperability and how it’s changed over the releases. If you’re working on toward industrialized construction or manufacturing for construction, this session is a must.

While Inventor and Fusion 360 don’t have the user base programs like Solidworks have, you’re just not going to be able to touch the functionality Inventor has with Revit interoperability. You need to reference Revit inside Inventor to design something going into a building? It’s there. Want to export what you designed in Inventor to use in Revit? It’s there.

If you’re doing fabrication or manufacturing drawings and models outside of Revit for construction, you need to review this material. That said, Fabrication Parts in Revit don’t import worth a shit inside Inventor. That wasn’t discussed in this session rather that’s my contribution. But for everything else, it should work great.

AS502502 | Autodesk Forge Data APIs: Standardized Granular Data Extraction to Reduce Code Base

This session was presented by Robert Manna of dRofus and James Mazza of Stantec. If you read up on any of Autodesk’s big announcements regarding their rebranding Forge to Autodesk Platform Services, this session was a good preview of the direction Autodesk is headed regarding your design data. Robert and James gave a great overview of how you’d go about using the Data API’s.

Not a coder? No worries. This session wasn’t full of syntax and code snippets. It was higher level discussion how you would use the API’s not demonstrating actually coding them. If you’re not a coder, there was still a lot of value here IMO.

IM502087 | Model-Based Definition: A Key Value Driver for Future Product Development

This session was presented by Eugen Taranov and Melanie Thilo both of Autodesk. It covered the topic of Model Based Definition. As Manufacturing typically leads a lot of trends you see in AEC by 2-3 decades, I’m always game for a good Manufacturing session.

If you’re new to MBD (Model Based Definition), it’s about embedding the manufacturing data within a model so that it can be fabricated without a human needing to read a drawing.

What interested me about this session is that I’ve long stated that I thick AEC is headed the wrong direction be jamming every piece of data within a 3d model. Revit is not SQL server after all. You can read one of my prior posts here about this. MBD seems to contradict my view of where AEC is headed. As such, it created a dilemma in thinking that I wanted to sort out.

Having sat through the session, I now have a more firm view of MBD and I don’t see any conflict with my thinking. MDB isn’t about embedding ALL data within a model, rather manufacturing specific information that needs to be communicated. My view that AEC is placing TOO much data within models is not in conflict with MBD in my eyes.

One realization I came to is that MEP is already doing “Lite” versions of MBD with tools like Stratus, M-Suite, Allied BIM and Connect2Fab. I say “Lite” because MEP doesn’t need high-precision tolerancing descriptions like GDT or finish information communicated the same way manufacturing does. None the less, it’s important to realize it is a form of MBD which is a validation on the direction we’re headed. The only real disappointing part is Autodesk themselves is not enabling Digital Fabrication for MEP. They’ve done their best to fragment the workflows and it’s 3rd parties providing these services. Most of the fabrication data Autodesk creates for MEP is not even accessible in Revit and is completely ignored in the Construction Cloud let alone their Industrialized Construction initiatives.

BES502491 | Beyond Fabrication: Using Revit Fabrication Parts for Spec-Driven Design

This session was presented by Claudia Calderon Quintero and Josh Churchill both of SSOE. This was literally the ONLY session at AU that covered anything related to Autodesk Fabrication. I wasn’t expecting much. Autodesk Fabrication has a pretty tight knit community of experts who’ve known each other for decades. Anyone speaking on Autodesk Fabrication that isn’t a known name is highly suspect.

That said, I was very surprised at this session. From an A&E perspective, they covered the topic very well. I’ve listened to Autodesk Fabrication presentations over the years with a lot of partial or incorrect information. But Claudia and Josh had a really rock solid presentation. Everything I heard was detailed, accurate and presented very well. I’m really impressed as well in their ability to get up to speed with Fabrication Parts as it’s not an easy thing to learn on your own when there’s not a lot of resources.

The essence of their presentation was using Fabrication Parts to create a “Specification” for industrial or process piping. As they said, anyone can make a “fabrication” level model with Revit Families…but anyone can also mess with those families. By using Fabrication Parts in Services, it get’s Revit a lot closer to a “Spec” driven design like you’d typically see in industrial piping with Plant3d with the content a little more protected from incorrect manipulation.

The key learning point here for me was the value of Fabrication Parts for a firm who’s NOT actually fabricating. I’ve struggled to see the value of Fabrication Parts for an Engineering only firm. Claudia and Josh easily explained this value to me. Something that having my head stuck in the actual “fabrication” and “construction” prevented me from seeing. Great job and great class.


Things We Can’t Do

Despite all Autodesk’s self proclamations of greatness and the legions of fans, there’s more holes in Autodesk’s strategy than a block of swiss cheese if your an MEP contractor. Here’s a few highlights of my observations from an MEP Contractor’s perspective….some will apply more broadly to other trades/domains.

Industrialized Construction, Inventor and Revit

One of my highlights of Autodesk University is to see the “Manufacturing Informed Design” team at Autodesk in the Expo Hall. I’ve spent 30 years straddling Construction and Manufacturing asking for this. It’s finally coming. Everything Autodesk has done to date seems to have been “Design” focused….pushing unbuildable design to Fabrication, Construction and Manufacturing. The Manufacturing Informed Design group flips that around…putting the PRODUCT front and center. This allows the Manufacturer or Fabricator to control how their product is used in Design….the way it always should have been.

Sure you can make a Revit family that represents a product. But anyone and everyone can mess with the RFA. You’ve can’t receive this model back and have any sense of reliability that’s it’s something you can manufacture from. What the Manufacturing Informed Design team does, is to make sure nobody in Revit can mess with your product. If your product is configurable, the consumer (Designer) is directed back to Autodesk’s web portal where they can control ONLY the aspects of the product the Manufacturer allows.

While the initial release will focus on Products produced in Inventor, there are plans to expand the “authoring” to other platforms like Fusion 360, Revit…perhaps even Solidworks and others. They want to make the logic authoring agnostic using code blocks similar to Inventor’s iLogic for configuration. In my opinion, this is the single most important step they could make toward “Productization” in construction.

So what’s the catch? Beta is estimated to be next year. That likely means 2024 Revit will be the first version (if not later…or even at all) that will have this capability. Except that means we’ll realistically be able to use this about 2027/2028. This industry loves to stay on old Revit versions and Autodesk now allows use up to 5 versions back. This means it’ll be 2028 by the time you find defects or functional limitations of 2024 versions. Except they won’t fix 2024 four years later…those fixes will come in 2029/2030 versions which you’ll start using about 2033/2034. That’s a 10 year development/feedback cycle. It’s just not sustainable. Keep this in mind when they tell you the industry is going to completely transform to products within a few short years. The tools just aren’t there to facilitate this in a wide scale manner.

Industrialized Construction and Fabrication Parts

As you can tell from the Inventor/Revit interoperability class I reported on earlier and the Manufacturing Informed Design group’s initiatives…Inventor is a key part of Autodesk’s Industrialized Construction Strategy.

Except that the vast majority of large MEP Fabricators are using Fabrication Parts. Fabrication Parts can be exported and brought into Inventor….except they look like shit and are unusable for manufacturing in the Inventor environment. Inventor and Fusion 360 are Solid Modelers. Fabrication Parts are NOT Solids…they’re surfaces. Poor quality surfaces at that. That was intentional…to keep AutoCAD/CADmep performant. Because Fabrication Parts know what they are (Pipe, Elbow, Tee, Valve, etc.) they have the proper data to fabricate from and don’t need heavy detailed graphics. You can place 10x more Fabrication Parts in Revit than RFA’s before seeing the same performance impact.

Until Autodesk bolts Fabrication Parts into Inventor (and I have no knowledge they’re even considering this) you’ll have to wait for the Manufacturing Informed Design team to allow Revit Authoring of Product. Who knows when that will be and when it does happen…what are the chances they even know how to manipulate a Fabrication Part? Most of Autodesk’s own Revit experts don’t even know what a Fabrication Part is let alone comprehend their value. Of the hundreds of data points Fabrication Parts hold…even their own Construction Cloud knows virtually nothing of the data. In short, the firms who have digitally fabricated from 3d models for nearly 30 years (MEP Contractors) are largely shut out of all Autodesk’s Industrialized Construction technology strategy.

Speaking of Fabrication Parts…

I asked about the MEP Fabrication Data Manager Sync. The Technical Preview of Autodesk’s Cloud based Fabrication configuration manager. A 7+ year initiative that’s still not usable in any practical capacity. I asked when it would be “Done”.

“Who’s to say it’ll ever be done. Perhaps it keeps evolving.”

Fair enough. So I followed up…When will it evolve enough that MEP contractors will willing use it?

“Who’s to say it’s even going to be for that type of customer?”

That speaks volumes. Add to that the ONLY session at Autodesk University on Fabrication Parts in Revit was from an A/E firm that doesn’t build or fabricate, it’s another data point suggesting Autodesk doesn’t have a plan for MEP Contractors. Or they simply think they’ll all cease to exist in a “Productized / Industrialized” construction economy. Certainly MEP Contractor’s will need to evolve…but we’re not going away. Great opportunity for someone else to enter the market IMO.

Data Exchanges

Another focus of Autodesk is Cloud Enabled Data Exchanges. You don’t download or export a spreadsheet to order from Amazon.Com or to book a flight. This makes a lot of sense in many if not most ways. It’s the first step of breaking down those old obsolete concepts and barriers like “files” which have long outlived their usefulness. With so much work to do in this area, it’s unlikely Autodesk will make Fabrication Parts part of these data exchanges anytime soon….if ever. Products like GTP’s Stratus jump through huge hoops to mine the data they do. These exchanges aren’t anywhere close to possible in Autodesk’s Platform Solutions today. It’s my hope that these Cloud based data exchanges evolve enough to start breaking down those “version incompatibility” walls between Revit versions which will shorten that 10-year development cycle. At least that’s my hope….if I were to have any.

A Bridge to Nowhere

One of the Autodesk Construction Cloud (ACC) highlights is it’s “Bridge” functionality. It allows you to link/sync multiple ACC Accounts between customers. Except that it only works on “published” models in Docs. It doesn’t work on “Live” models with BIM360 Collaborate Pro like it needs to. It also doesn’t work on the “Data”, just the “files”. This limits the effectiveness of ACC which is why most BIM360/ACC projects I see are complete train wrecks in terms of their use of existing functionality and configuration. People using Desktop Connector to access non-collaborated models or host Central Workshared models that aren’t in Collaboration.

Rumor has it Autodesk is reworking Desktop Connector. I’m sure that’ll inject just as many problems as it solves. Autodesk simply doesn’t have robust feature sets in their products any longer. Merely enough features to keep you on the hook as they have guaranteed annual revenue now.


Future Speculation

Given everything I’ve seen and heard….and 30 years of observing the industry and correctly predicting much of what has really transpired, I have a few predications…

  1. Autodesk’s Cloud enabled Exchanges will eventually be monetized. You’ll pay for everything eventually. Pay to author…pay to report…pay to export.
  2. Autodesk will become the “Facebook” (Meta) of Design/Construction/Manufacturing data. That means everything you think of when you think Facebook….the good and bad.
  3. An API first strategy is NOT in the cards. Data Exchanges will always be limited compared to what Autodesk can do with them. This will allow them to control and maintain their market position limiting what others can do or and controlling how much they must pay.
  4. Old school data exchanges will eventually go away and everything will be required to use the Cloud to facilitate data exchanges. I don’t like it on principal but it makes sense and needs to happen.
  5. 3rd party developers traditionally thought of as Autodesk competitors will some day be customers to facilitate their interoperability with Autodesk.
  6. Industrialized Construction will not be as wide spread or come as quickly as Autodesk says. Autodesk will be the biggest limiting factor in this due to products suffering a drought of features and depth.

No need to cover the positive predictions….I touched on them earlier and Autodesk does a good job promoting them all on their own. They don’t need my help. My value is providing a more realistic perspective and timeline….IMO. Let’s hope I’m wrong on many of my predications.

ESTmep Underlays – Auto vs Individual Placement

Do use use PDF Underlays in your ESTmep takeoff? Do the Pages come in all at once on separate tabs and layers? Or do you have to place them individually and make the tabs/layers yourself?

Maybe it worked one way for you and all of the sudden it seems to change to the other way for no reason. And despite looking, you can’t find a setting that changes this behavior.

What controls Auto Sheet Placement vs Individual is very easy to control, but it is hidden. Let’s take a look.

Individual vs. Automatic PDF Sheet Placement

This images shows a 7 page PDF with each page imported as an Underlay separately. Notice they are not on separate tabs and they’re all on one layer.

This next images shows what Automatic PDF placement looks like. Notice all sheets evenly placed in a row, each on a separate tab and layer.

So what’s the difference? What’s the magic setting? It all depends on how you select the “of type” dropdown when you select the PDF. This next image should explain it…

Let’s Look at Each Process

Place Sheets Individually One at a Time (of type = *.*)

Place Sheets Automatically All at Once (of type = *.pdf)

Desktop Connector + Revit Cloud Models = Bad Idea

I’ve been seeing a recent trend in project teams. An increasing use of Autodesk Desktop Connector to link Revit Cloud Models. While it can and does work (sometimes), it’s a real bad idea and should be avoided unless absolutely needed. The reasons are subtle and nuanced. But those nuances are a make or break in terms of success.

I’ll try to explain as best I can. I’ll even give you steps you can do to reproduce this issue yourself. But first, let’s go over why Desktop Connector exists in the first place.

A Brief Desktop Connector History

Autodesk’s first attempt at a proper Cloud workflow for Revit was called Collaboration for Revit. It later became BIM360 Design and today is called BIM360 Collaborate Pro. Same idea…take a Revit model and manage it in the Cloud from Sync’d local data. Practically speaking, it’s a cloud version of Revit Server.

Back in those early days, you could link to other Revit cloud models. But Revit supports other types of links besides RVT files. So people would link to file servers. But in a collaborate environment, other teams didn’t have the same file servers or folder structures. Those other linked files linked DWG’s or IFC’s would break. So like the good technologist’s they are, BIM Managers started using services like Dropbox across the product team. Those non-Revit files were linked from there so the links would be common across of team members.

As a result, Autodesk later acknowledged the value in doing this and released it’s own ‘sync’d drive’ tool called Autodesk Desktop Connector. So that’s why it’s there. It’s intended to link non-Revit files or Revit files that are NOT cloud models.

One could argue that Autodesk should have just made Collaboration for Revit work with those other files types. I agree and it’s a nice thought. But it’s likely not the case because the Revit files you see on BIM360 Docs (now Autodesk Docs) are NOT the same files as are used by Revit’s Cloud collaboration tools. You can read more about that here (https://www.darrenjyoung.com/2022/03/29/the-2-sides-of-bim360-acc-docs/)

The False Alure of Desktop Connector

When I see Desktop Connector misused, the reason I’m given is usually the same. “We don’t want to Live Link models“. That’s to say, they don’t want to see daily changes from the other project teams in real time.

So that sounds reasonable. But if people would use BIM Collaborate Pro ‘properly’ this actually solves this problem and in a much more flexible way. BIM Collaborate Pro when setup and used properly allows 3 separate workflows or a combination of any of them….

  • Link to Live Models
  • Link to “Shared” copies of Models (only updates when the model owner chooses to share)
  • Link to “Consumed” copies of Models (only update when you consume a shared copy)

Yup. That’s it. Complete flexibility on how you link to other Revit Cloud Models. In short, if you’re linking to get away from updates you don’t control, it’s because you’re not using the BIM Collaborate Pro properly. More accurately, whoever is hosting the project did not set it up properly and you’re a mere casualty caught in the cross fire. Something most sub-contractors are very familiar with.

The True Appeal of Desktop Connector

There’s really another reason people use Desktop Connector for Revit Cloud models. A result of Autodesk’s flawed logic that everyone on the project should be on the same platform, same project and same account. While it makes sense at a high level, it also means all other project teams who aren’t the hosting company are limited to the willingness and/or capabilities of the hosting company.

Taking that into account, one aspect of Desktop Connector is that you can link ‘between’ BIM360 or ACC (Autodesk Construction Cloud) accounts. That is, you can link files in your account, to project files in another team’s account. This cross account linking is NOT available in BIM Collaborate Pro with Cloud models or Cloud Workshared models but it is in the Desktop Connector.

When you put this all together, this means companies can link to files from other companies but still control their own models on their own account. And they’re not live linked either. This is why we’re seeing a proliferation in Desktop Connector usage with Revit Cloud Models.

The new Autodesk Construction Cloud has some “Bridge” functionality designed to facilitate this. I tested the Bridge functionality when it first came out. It didn’t work as required, expected or as advertised IMO. It may or may not have improved since then but that’s not the point of this article. The point of this article is about linking to Revit Cloud models from Desktop Connector. Why it’s problematic, not a recommended best practice and why it should be avoided.

The Desktop Connector Problem

To demonstrate the problem, we’ll use two separate sets of 3 Revit files each linked to each other within the set like the following…

  • Set 1 (problem set)
    • Test – 1.rvt (Link to Test – 2.rvt & Test – 3.rvt)
    • Test – 2.rvt (Link to Test – 1.rvt & Test – 3.rvt)
    • Test – 3.rvt (Link to Test – 1.rvt & Test – 2.rvt)
  • Set 2 (working set)
    • Test – A.rvt (Link to Test – B.rvt & Test – C.rvt)
    • Test – B.rvt (Link to Test – A.rvt & Test – C.rvt)
    • Test – C.rvt (Link to Test – A.rvt & Test – B.rvt)

Each Revit model is a Cloud Workshared Model. (a standard Cloud Model would function the same for this issue). You can tell they’re Cloud Models be viewing them in Revit’s interface like shown in the following image…

If any of the Revit files were not Cloud Models, they wouldn’t appear here in Revit but would appear from the BIM360 or ACC web interface. You can see in the following image, those same files are listed in the web interface. They were all published so the version in Autodesk Docs displays the same contents as is available in BIM Collaborate Pro.

So far, all seems fine. The files you see in the BIM360 or ACC interface are the same ones that are available in Desktop Connector. Now here’s where the issues starts to manifest itself.

Take a look at what happens when we try to download the Revit Models from the web interface. Set 1, the numerical set download as ZIP files. Set 2 on the other hand, that alphabetic models download as Revit files.

Perhaps you’ve seen this before. I know many users who assume that the ZIP file downloads are there because the Revit files contain links. Because a non-linked model always downloads as an RVT. Other users think it’s part of the whole “Share/Consume” workflow of BIM Collaborate Pro. Both explanations are technically incorrect.

The following image shows the files and their downloaded names. Keep in mind that each set is a model collaborated in the Cloud the exact same way and linked the exact same way. In fact, they themselves are not linked from the Desktop Connector either. They’re linked properly through the “External Resources”. Aside from the files names, they are identical in every way.

Further Proof – RVT Doesn’t Mean RVT

To further complicate matters, Desktop Connector displays all the files as RVT files even though some are ZIP files. Here’s how to test that out. First, we’ll use Windows File Explorer to select and copy all the files to the desktop. You can see the first hints of something being wrong in the following image…

Notice that all the files are named RVT just like was displayed in the Web Interface of BIM360 / ACC. However you can also see the icons are different between the two sets of files. The Revit files display their preview. The others display the icon because if the RVT extension because it can’t find a Revit preview. So let’s test our theory that some of these are actually ZIP files named wrong.

We’ll rename all the files to the ZIP extension and attempt to open them. The following images shows the renamed files. It also shows happens when you attempt to open the ZIP for one of files from Set 1 (Test – 1.rvt, Test – 2.rvt & Test – 3.rvt).

You can see when attempting to open the file TEST – 1.rvt.zip (remember we renamed to a ZIP) it shows the contents. It contains the Revit file and the links that Revit file uses.

Now let’s try the same thing with another file. This time. we’ll use the file Test – A.rvt.zip from Set 2.

You can see that despite renaming the file as a ZIP file, Test – A.rv.zip will not open and displays no contents. That’s because it is indeed not a ZIP file.

Summary of the Desktop Conector Problem

To summarize what we just saw, the web interface to BIM360 / ACC as well as Desktop Connector showed that all the files were RVT files. But upon testing with 2 different methods (web download & copy/rename from Desktop Connector) we can see that the two sets of files are not the same.

Set 1 is comprised of ZIP files despite showing their name as RVT and Set 2 are actual RVT files.

We can perform one further test to see if this is the case, We can start a new Revit file and try to link one of each set from the Desktop Connector. The following images shows just that…

You can see we were able to successfully link Test – A.rvt (from Set 2) using the Desktop Connector. But when we try to link Test – 1.rvt (from Set 1) we get an error, Failed to open document.

Again, this is because despite what you see (the RVT file extension), the file is actually a ZIP file. This is the root of the problem with using Desktop Connector to link Cloud Models. Linking non-cloud Revit models is not a problem. More in that in the next section when we cover “How” and “Why” this happens.

The How and Why

The issue of when BIM360 / ACC is using a ZIP file vs. a RVT file behind the scenes is actually quite predictable and a little controllable. So let’s take a look. It might be a little difficult to understand but we’ll try explain anyway. We’ll then follow-up with the steps to do it yourself.

At the root of the issue is that the Cloud model Revit uses is a separate file that the one you see in BIM360 / ACC Docs and Desktop Connector. You choose when to “publish” the one that shows up in BIM360 / ACC. And here’s where it starts to get complicated. We’ll use the names of the samples models to make it a little more clear.

If you have cloud model Test – 1.rvt open, and you link to cloud model Test – 2.rvt, if cloud model Test – 2.rvt has changes that are unpublished to BIM360 / ACC Docs when you publish Test – 1.rvt to BIM360 / ACC Docs, Test – 1.rvt will be a ZIP file.

On the other hand, if you link to cloud model Test – 2.rvt and it’s latest version is published to BIM360 / ACC Docs then when you publish Test – 1.rvt and download it, it will be a RVT file.

Did you catch that? Whether a Cloud model ends up as a ZIP vs. a RVT depends on the Publish Status of the Cloud models it links when you publish it.

Let’s look at that visually. The below image shows the 3 models from Set 1. Notice how none of them have the current version published. When you publish one of these, or even all three of these you’ll end up with a ZIP file.

Again, the issue is that you linked a cloud model in Revit when that cloud model had unpublished changes. Even if you published all of the models now, you’ll still get ZIP files with downloads and Desktop Connector. That’s because when they were published, there were unpublished changes which made them ZIP files. Further publishes will always make more ZIP files because they now reference Cloud models who’s Published versions are ZIP files not RVT. Yea…that’s a bit complicated. Just know that once you start getting ZIP Downloads, they’ll stay that way. From here on out, there’s only one way to fix it which we’ll get to momentarily.

How Not to get a ZIP

Now here’s where the process get’s slightly different if you want a RVT. The difference here is when you go to link the Cloud model, you need to make sure the file(s) you’re linking don’t have unpublish changes when you publish it. So when you have Test – A.rvt open, make sure Test – B.rvt doesn’t have unpublished changes, if it does, Test – B.rvt needs to be published before Test – A.rvt. Then when you then publish Test – A.rvt it will download as an RVT and Desktop Connector will be a ‘real’ RVT file.

So that sounds simple. Just make sure when you link the cloud model that’s it’s most recent version is published. But it’s not that simple. At any point in the future if one of the linked files is not published when you publish the model, you’re back to the ZIP file again and it stays that way. Until you fix it.

Unzipping the ZIP

If you ever link a cloud model that has unpublished changes you’ll end up with ZIP files. Further more, if at any point you publish you model, any one of the linked cloud models has unpublished changes, you’ll get a ZIP file again. And it won’t get fixed again easily.

This is why you should NOT link to cloud models from Desktop Connector. Because you’re relying on the author to understand this and know what to do. In fact, in the course of a real project, it’s damn near impossible to make sure you’re not going to get a ZIP. You can’t control when the project teams make changes and publish.

However, if you do want to fix the ZIP problem, here’s the process.

  1. Open your Revit model and “unload” (not remove) and cloud model links. Save/Sync and publish the model.
  2. Repeat Step 2 for all of the linked Cloud model. Make sure none have the links loaded.
  3. Once all models have their links unloaded, republish them all.
  4. Reopen one of the models and reload the links. Save/Sync the model. One model only.
  5. Now Publish the model and wait for publish to complete before doing any more models.
  6. Repeat steps 4 and 5 for the remaining models.

So that’s the process to “fix” the issue. Each model needs to be republished with none of the cloud model links loaded. You then open one, sync and publish each model. If you do save/sync more than one model before publishing again, you’re back to the ZIP files.

Try It Yourself

This issue is a bit nuanced…what makes a ZIP files vs a RVT. An even when its a ZIP, The web site and Desktop Connector misleadingly tell you it’s an RVT. And if you do have it working, it’s still fragile and breaks easily. Which is why it’s recommended to NOT use Desktop Connector to link to Revit Cloud Models.

If you really want to understand the issue, it’s best to try it yourself. You can do it with just 2 files. Here’s how. Follow these steps exactly.

  • Step 1 – Create file A in Revit and save as a Cloud model or Cloud Workshared model.
  • Step 2 – Close file A.
  • Step 3 – Create file B in Revit and save as a Cloud model or Cloud Workshared model.
  • Step 4 – Close file B.
  • Step 6 – Open file A and link file B using the “External Resources” (not Desktop Connector)
  • Step 7 – Save/Sync file A and close.
  • Step 8 – Open file B and link file A using the “External Resources” (not Desktop Connector)
  • Step 9 – Save/Sync file B and close.
  • Step 10 – Publish both files so their latest version appear in BIM360 / ACC Docs.
  • Step 11 – Try downloading with model from the web and you’ll see they’re zip files.
  • – – You’ve now recreated the process which makes the ZIP files – –
  • Step 12 – Open file A and unload the link to file B.
  • Step 13 – Save/Sync and Close file A
  • Step 14 – Open file B and unload the link to file A.
  • Step 15 – Save/Sync and Close file B.
  • Step 16 – Publish both models. (when you publish doesn’t matter with links unloaded)
  • – – Both models are now published with no Cloud model Links. This clears the ZIP issue. – –
  • Step 17 – Open file A and reload the links to file B.
  • Step 18 – Save/Sync and Close file A.
  • Step 19 – Publish file A and wait for it to complete before continuing. This is important. It’s linked to a file B. While file B has no links loaded, it has all it’s changes published (the critical step)
  • Step 20 – Open file B and reload the links to file A.
  • Step 21 – Save/Sync and Close file B.
  • Step 22 – Publish file B and wait for it to complete before continuing. This file is linked to file A which does have links, but it also has all of it’s changes published too.
  • Step 23 – Try downloading the models now. You should get a RVT file instead of a ZIP.
  • – – Both models are now published but are now accessible from Desktop Connector or downloadable as RVT files – –

It sounds like a lot of steps but it’s fairly quick to do. Perform these steps and you’ll get a better idea how the issue. Any time you have changes in multiple models before you publish, you’ll see the ZIP show up. If you change and publish a single model at a time, you’ll have RVT files. But also note, once you get the ZIP files, you’ll need to unload the links on all the files, republish and then open, reload and publish one at a time to clear the issue.

Summary

So that’s it. If you understand the issue, you’ll see how easy it is to have the ZIP issue show up. And that’s when linking from Desktop Connector breaks. And in the course of a project, it’s easy for others doing what I’ve explained above to break YOUR link to THEIR model when you use Desktop Connector.

So don’t use it to link Revit Cloud models if at all possible. If you’d like further reading on this, check out these Autodesk Knowledge Base articles…

“Failed to open document” when adding links to a Revit model through Desktop Connector.

Application Development & System Integration – No Coder Required

As many of our IT systems have moved to the Cloud, the promise of a “Single Source of Truth” seems further away that it ever has. Our data was always generated by multiple applications. But it was still stored on your servers. And related data was often in the same folder structure.

With Cloud based systems, you’re data is now locked in another company’s servers. Or is it?


Anyone Can Code – But They Don’t Need To

One of the great things about the technology landscape today is there’s a lot of solutions that allow non-programmers to create applications and integrate systems. If you can create a flow chart and have some logical thinking skills, you can built an app. You can build and integration. All without writing code.

I tend to think of these systems in 4 different groups. Those are No-Code, Low-Code, RPA (Robotic Process Automation) and Integration platforms. It’s often hard to draw lines between them because they have many of the same attributes and often overlap in functionality.

I’m not a technical purist or a trained IT professional despite a career in tech. So here’s my “unofficial” stab at how I define those classes of software.


No-Code

No-Code platforms are just what the names implies. A system that allows you to built an application, or database with forms and a workflow or even a website without any coding skills. They typically have drag & drop controls or widgets that can be configured to do what you need. Even to pull or push data to other systems.

Low-Code

Low-Code platforms are a little more misleading. The name implies you need to code….maybe. It’s not always the case. They often allow a lot of the same aspects of a No-Code platform but extend functionality with the optional ability to use code. But again, not always. Some of the Low-Code platforms do require coding. That “Low-Code” can very from simple syntax to more comlpex or even complicated. It could be based on an existing language or may even proprietary to the platform. Do you research carefully. But don’t let it deter you from using a Low-Code platform. It’s a lot lighter lift that hard core software development.

RPA (Robotic Process Automation)

RPA platforms are what the name implies….software robots. However don’t get too excited. Many people hear “Robot” and they think all finds of complex amazing workflows and interactions. That’s not the case…each RPA application is a little more narrowly focused. Think of an automotive assembly plant. Lot of robots. But each does a very limited set of tasks. A robot doesn’t make an assembly plant….an assembly plant is made of many robots, manual tasks and other technologies. RPA is similar….more task, data or workflow specific. Often mining data or running AI/ML analysis on those data sets.

Integration Platforms

Integration Platforms, sometimes called iPaaS (Integration Platform as a Service) are platforms designed exclusively for the purpose of integrating other systems. Many No-Code/Low-Code platforms even include iPaaS functionality. They may have built it themselves into their product or they just may incorporate another technology to serve that purpose for them. As an example, TrackVia is a No/Low-Code platform. They also offer integrations but use Workato for that purpose.

Integration platforms usually offer a number of “pre-built” connectors that aid in connecting to other systems. Those connectors eliminate your need to know how to code to connect to another system.

Using those connectors, you build your logic based flow, often visually to define how those systems interact. As an example, if you wanted a Slack notification everytime someone posts a file to DropBox, you’d use a Connector for Slack and Dropbox and configure their interation yourself. If there’s not a pre-built connector, they can typically be built as long as the system you want to connect to has an API. If you don’t have a coder, no worries. These Connectors are fairly easy to contract out to a developer.


Platform Selection

Unfortunately, it’s hard to offer blanket guidance on how to pick the platform you need. It may even require multiple applications. But here’s some rules of thumb….

If you want an Application, something that has a more complex user interface or workflows, No/Low-Code is likely were you want to look. If you have simple, repeditive or data heavy tasks RPA bots may be a good option. And if you want to connect other existing systems, an Integration platform is what you’re looking for.

Licensing is another area of concern. You may need to pay “Per Application” or “Per User” or “Per Integration” or “Per Task”. Your license may even be a combination of these factors and more. Ask lots of questions and think of every loophole you can think. Does your integration generate PDF’s? Is there a cost per page? Per file? Is there a limit to the amount of data the PDF can print? Questions like these will be bery helpful in determining your overall cost. It’s rare someone buys into a solution and it costs less than they think. It’s usually more. There’s nothing wrong with that if it’s providing more value than you expected. But plan accordingly.

Selection can also be daunting. Especially if you look at my list below. How the hell do you parse through that? Especilly when I tell you I’ve left a lot off the list? More niche platforms designed around only an industry or two.

It’s really not that hard. Look at the list. I’m sure some names will pop out at you. Do a search for “Low-Code” or “No-Code”. See what names keep popping up. Do a search on a specific platform and a serch engine will aften list “Ads” for their compeditors. If there’s no Ads taken out against them, that may be a smaller player. Crunchbase can also tell you a bit about the company….how much funding they’ve recieved…number of eplmoyees, etc. But with a landscape this large, expect some to disapear…maybe go out of business or perhaps be aquired. SAP in particular seems to be snappnig up a lot of them.

So with that in mind, here’s a list to get you started. I make no claims to it’s accuracy. Do you due dillegence.


List of Solutions

PlatformURLNo
Code
Low
Code
RPA iPaaS
8basehttps://www.8base.com/ X  
Airtablehttps://www.airtable.com/XX (x)
Adalohttps://www.adalo.com/X   
Agentyhttps://agenty.com/  X 
Alphabotshttps://www.alphabots.de/  X 
Alvariahttps://www.alvaria.com/  X 
AntWorkshttps://www.ant.works/  X 
Appy Piehttps://www.appypie.com/X   
App Engine (Service Now)https://www.servicenow.com/ X  
AppGyver (SAP)https://www.appgyver.com/X   
AppSheet (Google)https://appsheet.com/X  X
Appianhttps://appian.com/ XX 
Argoshttps://www.argos-labs.com/ XX 
AssistEdgehttps://www.edgeverve.com/  X 
Atoshttps://atos.net/  X 
Automaihttps://www.automai.com/  X 
Automatehttps://www.helpsystems.com/  X 
Automation Anywherehttps://www.automationanywhere.com/  X 
AutomationEdgehttps://automationedge.com/  X 
Ayehuhttps://proxima-software.com/  X 
Betty Blockshttps://www.bettyblocks.com/X   
Bildrhttps://www.bildr.com/X   
BiznessAppshttps://www.biznessapps.com/ X  
Blue Prismhttps://www.blueprism.com/  X 
Boomihttps://boomi.com/   X
Bubblehttps://bubble.io/X   
Build Firehttps://buildfire.com/ X  
Camundahttps://camunda.com/  XX
Carrdhttps://carrd.co/X   
Caspiohttps://www.caspio.com/ X  
Celonishttps://www.celonis.com/  X 
Choiceworxhttps://www.choiceworx.com/  X 
Claris FileMakerhttps://www.claris.com/filemaker/XX  
Claris Connecthttps://www.claris.com/connect/   X
Cloudstormhttps://www.cloudstorm.io/  X 
Cognifirmhttps://cognifirm.com/  X 
Cortexhttps://www.cortex-ia.com/  X 
Creatiohttps://www.creatio.com/X   
Dataflixhttps://www.dataflix.com/  X 
DWKithttps://dwkit.com/X   
Epiancehttps://www.epiplex500.com/  X 
electroNeekhttps://electroneek.com/X X 
Emmahttps://www.wianco.com/  X 
Flowdohhttps://www.enadoc.com/  X 
GeneXushttps://www.genexus.com/ X  
G1anthttps://g1ant.com/  X 
Gibotshttps://gibots.com/  X 
Glidehttps://www.glideapps.com/X   
HoneyCode (AWS)https://www.honeycode.aws/X   
Hylandhttps://www.hyland.com/  X 
.Internalhttps://www.internal.io/XX  
JitterBithttps://www.jitterbit.com/   X
Kissflowhttps://kissflow.com/XX  
Kofaxhttps://www.kofax.com/  X 
Lansahttps://lansa.com/ X  
Makehttps://www.make.com/X  X
Mendixhttps://www.mendix.com/ X  
Meta:prochttps://www.metaproc.com/  X 
MicroGenisishttps://mgtechsoft.com/  X 
Mulesoft (Salesforce)https://www.mulesoft.com/   X
Netbotixhttps://www.nexbotix.com/  X 
Nicehttps://www.nice.com/  X 
Nintexhttps://www.nintex.com/XXXX
Nividoushttps://nividous.com/  X 
Olive.Aihttps://oliveai.com/  X 
OpenRPAhttps://www.openrpa.dk/  X 
Orchestrahttps://www.onvisource.com/  X 
Outsystemshttps://www.outsystems.com/ X X
Pegahttps://www.pega.com/ XX 
Perpetuuitihttps://perpetuuiti.com/  X 
Pineapplehttps://pineapple.build/X   
Power Apps (Microsoft)https://powerapps.microsoft.com/ X  
Power Automate (Microsoft)https://powerautomate.microsoft.com/  XX
Pulse (IMAGINiT)https://www.imaginit.com/   X
QuickBasehttps://www.quickbase.com/ X X
Quixyhttps://quixy.com/X   
RapBothttps://rapidautomation.ai/  X 
Redwoodhttps://www.redwood.com/ XX 
Retoolhttps://retool.com/ X  
Robocoder (Rintagi)https://www.rintagi.com/XX  
Roboosthttp://roboost.info/  X 
Salesforce Platformhttps://www.salesforce.com/products/platform/overview/ X X
SAP Process Automationhttps://www.sap.com/  X 
Scoop Roboticshttps://www.scooprobotix.com/  X 
Sisensehttps://www.sisense.com/X  X
Skan.aihttps://www.skan.ai/  X 
Skyvehttps://skyve.org/XX X
SIB Visionshttps://www.sibvisions.com/ X  
Softrhttps://www.softr.io/X   
Stackerhttps://www.stackerhq.com/X   
Symphonyhttps://www.symphonyhq.com/  X 
TagUIhttps://tagui.readthedocs.io/  X 
Thunkablehttps://thunkable.com/X   
TrackViahttps://trackvia.com/
Tray.iohttps://tray.io/   X
Trubothttps://www.datamatics.com/  X 
UI Bakeryhttps://uibakery.io/ X  
UiPathhttps://www.uipath.com/  X 
Verinthttps://www.verint.com/  X 
Vinyl (Zudy)https://zudy.com/X   
VisualCronhttps://www.visualcron.com/  X 
vOnehttps://www.yourvone.com/X   
Uniphorehttps://www.uniphore.com/  X 
WinActorhttps://winactor.biz/en/  X 
Winwaihttps://www.win-wai.com/  X 
Workatohttps://www.workato.com/   X
Workfusionhttps://www.workfusion.com/  X 
Wrkhttps://wrk.com/  X 
Xalt (Hexagon)https://hexagonxalt.com/    
Xpertrulehttps://xpertrule.com/  X 
Zapierhttps://zapier.com/X  X
Zaptesthttps://www.zaptest.com/  X 
Zoho Creatorhttps://www.zoho.com/ X  

ESTmep – Troubleshooting Duct Area & Weight

ESTmep seems like it should be easy to calculate things like Area and Weight. A couple of the major factors in cost. But this couldn’t be further from the truth. It’s difficult to understand “Where” numbers are coming from. Here’s a few tips for troubleshooting.


Eliminate Wastage and Costing Adjustments

Make sure Normalization is turned off for costing. You can do that here…

Next, eliminate any Wastage factors. Here’s what that might look like…


Create a Neutral Takeoff

There’s so many adjustments and factors that reporting properties it’s hard to tell what all makes up a number. The best way to find out what makes up a number is to make a Takeoff that eliminates as much of the factors as possible so you start with the core properties.

You can do this by adding Duct with simple numbers…12″ x 12″ x 12″. Duct with no connectors and no seams to eliminate allowances and sealant. Sizes that either don’t use stiffening or a purpose built specification that eliminates stiffening.

In my test, I created 20 pieces of Straight Rectangular Duct, You can do other fittings or Round/Oval too but start with the simplest and once you get dialed in and understood, you can expand to Round Straight or Fittings, etc.

  • Qty of 1
    • 12″ Width x 12″ Depth
      • 12″ Length
      • 24″ Length
      • 36″ Length
      • 48″ Length
      • 60″ Length
    • 24″ Width x 24″ Depth
      • 12″ Length
      • 24″ Length
      • 36″ Length
      • 48″ Length
      • 60″ Length
  • Qty of 2
    • 12″ Width x 12″ Depth
      • 12″ Length
      • 24″ Length
      • 36″ Length
      • 48″ Length
      • 60″ Length
    • 24″ Width x 24″ Depth
      • 12″ Length
      • 24″ Length
      • 36″ Length
      • 48″ Length
      • 60″ Length

Customize Takeoff

Takeoff in ESTmep can sometimes list “Many” properties for Area and Weight or Quantity. When you add them, they typically just list “Area” or “Weight” making them unclear what they are. You can customize the takeoff Description to reflect which property it maps to. This way you can add them all and see the differences.


Test Various Quantity Units

Each Property in Takeoff also has the ability to change the Qty Units. Here’s the 3 settings you have can reflect what Area and Weight is displayed. Here’s what those settings look like…

Here’s the results of those settings on my sample duct…

Per Item Quantity

Per Item Rate

Total Item (extn)

You can see “Per ITem Qty” gives you likely the closest to what you want. Exept it doesn’t take into account the Quantity of fittings. Quantity of 1 vs 2 is the same Area/Weight for the respective sizes.

“Per Item Rate” seems to be furthest from what you’d think. It’s really a ‘Per Ft’ value.

Lastly, the “Total Item (extn)” gives you most likely what you want and also taking into account the quanities of fittings.

Validate Data

Now that you have sample data and simple numbers, you can start doing the math. Look at the material and gauge and find the weight or area and see how your numbers respond.

Once you get comfortable that the numers are correct, start by adding in Seams or Connectors and see if the ancillary weights get added as you expect. Note that you’re numbers may be a little “off” based on Seam or Connector allowances and notching. Try adding only one thing at a time.

If you want to test how Wastage or Costing methods apply, you’ll want to go back to simple duct…No Seams…Connectors….Stiffeners, etc.

Keep things simple. Experiment. Check the numbers. Remove one of the factors and add another and try again. Then combine factor and verify your data is adding up properly.

Unfortunately there is no easy path or roadmap. But by starting with simple datasets and incrementally testing added features or factors, you can start to get a better picture of where your values are coming from.

ESTmep/CAMduct – Area/Weight Missing

In ESTmep and CAMduct, if you use the 3d View and stretch duct to add pieces, you end up with duct that has zero Area & Weight. This also means you have zero cost for that material.

This is a confirmed issue that’s been around forever. I’ve tested from 2016 thru 2023 and can reproduce in all versions.

Here’s what that looks like…

The Fix

The good news is, there’s a quick fix (workaround) you can deploy to update the weight and area. Using Notepad, you can make a quick COD script that updates the ITM’s. Below is what your script should look like…

Once you create the COD script, it’s recommended you put it in the SCRIPTS folder of your Fabrication Configuration. From there, you can make a process that calls the script which will update all the ITM’s to their proper Area and Weight. The display on the Item Takeoff may not refresh. If so, just browse to another tab and back. Here’s what that looks like….

So, which this doesn’t “Fix” the issue, it does work around it fairly easily. Just run the process before running and reports or data exports.

Field Ordering Ductwork

Want to Field order ductwork electronically? There’s several options that I’m aware of.

Autodesk Remote Entry

Autodesk’s Remote Entry can be installed on any number of computers without cost just as long as you have at least a single license of Fabrication CAMduct (~$1000/yr). You can read about Remote Entry’s licensing details here. Remote Entry is only of value if you’re shop or your duct manufacturer uses Autodesk’s Fabrication CAMduct to drive fabrication.

Note, like most of Autodesk’s Fabrication software…this is a stagnant product. Works only on Windows (no Andriod or IoS). Unless you’re already using CAMduct in your shop, there’s littererly very little reason to ever implement this software.

BuildCentrix

BuildCentrix started out as Webduct. They’ve since expended beyond ductwork and gone as far as having capabilities to integrate with a number of ERP systems. This is likely the best “Enterprise Class” tool focusedon ductwork at this time.

FieldOrderZ

One of the newer players in the market, it’s a project partnered with GTP. However you don’t need to be a GTP Stratus user to leverage FieldOrderZ. It can serve your needs even if you’re not a Stratus customer. It can also facilitate more than just Ductwork. Works best for Autodesk Fabrication users but I’d encourage you to reach out to them to see what they can do if you’re not an Autodesk Fabricatino customer. Likely one of the easiest tools for your Field staff to sketch what they need without being an AutocAD or Revit savvy detailer.

SiteTrace

SiteTrace is another newcomer I’ve just become aware of. CAD Content agnostic, it’ll help digitize your field ordering of Duct and related accessories saving you time and errors from traditional processes. They don’t integrate with any CAM software or Machine tools at this time making it the perfect fit for those smaller shops that get overlooked by the larger software companies.

Trimble FabShop

This is the old Vulcan software, one of the long timer CAM platforms for Duct fabricators. Their current platform has mobile capabilities that allow Field ordering of duct and processing within Trimble’s Shop Fabrication software.

Vicon Vi-Call

Most pepole know Vicon as a builder of Duct fabrication machinery. But they also offer a varierty of software tools. One of which facilities ordering of ductwork from your field staff to the shop into their managment platform.


If you’re aware of other field ordering tools for Sheetmetal ductwork, drop me a note and I’ll get them added to the list.

Construction’s Misguided ‘Model Based’ Ideology

Paraphrasing Country singer Johnny Paycheck, “Take this Model and Shove It.”

Yes. You heard me correctly. But just to be sure, let me rephrase it another way….”F_ck the Model“.

There. That should do it.

That may seem a bit of an odd thing to say. Especially for someone like me. After all, I’ve spent most of my career working with technology in Manufacturing and Construction. It’s been good to my family and I. But like many things, it can go too far. And it has. It’s time someone stands up and says something.

Why Do You Oppose 3d Models?

Why am I opposed to 3d models? Simply put, I’m not.

I’m opposed to idealistic visions of a utopia where everything can be solved with a 3d model. That may be the case one day, but it won’t be in my lifetime. Technology moves fast. But we’re also a long way off from promises made even a mere decade ago. The value of creating many 3d models does not overcome the cost to generate them (or maintain them).

There’s a lot of reasons NOT to model things. I won’t elaborate too deeply here. You’ll either get it or you won’t. But to summarize, here’s some of the major reasons to NOT 3d model something…

  • No time / schedule
  • No resources / staff
  • Lacking tools / technology
  • Less efficient / takes longer
  • No value / creates waste

If you disagree and think we should 3d model everything…like right now today, consider you might be part of the problem.

The 3d Model Vision

There’s a lot of folks who tell you how things “should be”. Digital Twin this and that. Everything will have a perfectly pristine working digital clone. Identical in every detail.

For the most part, I agree with them. However there’s an economic ecosystem at play. It’s beyond the control of a mere few wishful thinkers and prognosticators. It takes a while to turn around an industrial complex the size of constructon. So until modeling everything adds value offsetting it’s cost, some things (many things) should never be modeled. Ever.

Some will say this is because the industry full of laggards. Those reluctant to change. But look around. The skyscrapers, the roads and bridges, the dams and monuments. Do they look like they were constructed by laggards? Next time you’re in a big city, walk up to a construction worker and call them a laggard. See how that goes for you.

It’s also important to keep in mind how things “are” didn’t just happen in an ignorance vacuum. Things evolved for a reason. And until those reasons go away, we’re left with what “is” not “what should be”. And if things haven’t changed as you expected, consider the problem might by more complex than you give it credit. Those ‘laggards’ as they’re called, just might know something you don’t.

Resistance to Overboard

3d Modeling in manufacturing preceded common use in construction by about two decades. Same with concepts like PLM which is manufacturing’s ‘BIM’. Lean? Started in manufacturing (Just like me).

I pushed hard for 3d modeling back in one of my old companies. Endured the eye rolls and comments about how “3d is for boxes, not complex things like the warped surfaces” which they were doing in 2d AutoCAD. I also promoted Revit for a manufacturer of construction materials before Autodesk acquired the technology.

In each of those cases, when they finally saw what I was trying to convey, they over reacted and went too far. Complete abandonment of all 2d even where it made sense and 3d had no added value. They even attempted to do manufactured piece part modeling in Revit where Inventor or Solidworks was better suited. What was need was nuance and a blended approach. Instead the result was a binary shift. Classic throwing the baby out with the bath water. Lessons learned the hard way.

Sometimes when you apply too much force to a seemingly immovable or stuck object, it’ll eventually break free and go beyond it’s acceptable tolerance. If you’ve ever busted a knuckle trying to remove a stuck bolt while working on your car, you know what I mean.

3d Modeling has went that same way. Gone too far. If you ask me, as an industry are suffering from bruised, broken and bleeding knuckles.

The Problem With 3d Models

So what’s wrong with the current 3d modeling approach? Absolutely Everything.

No, not THAT ‘Everything’. There’s a lot of 3d modeling that creates incredible value and eliminates waste. It greatly exposes risk before cost is incured. In those cases we should do more not less.

The ‘Everything’ I’m talking about is that we’ve somehow moved into this unattainable, low intellect thinking that 3d modeling is the answer for….well, just about EVERYTHING. Revit projects have become nothing more than an erotic orgy of data vomit.

Oh look…corn. I don’t remember having corn. Is that a piece of baked potato? A date dump from a 3d model often results in forensics to even determine what the hell it is.

  • Need data? Add it to the model.
  • Nothing modeled? Model it.
  • Data changed? Open the Model and edit it.

Somehow the 3d Model turned into not only the single-source of truth but the ONLY source of truth. Merit for what to put in a model is typically controlled by somone with limited perspective. Can the computer can open it, navigate efficenetly and display/print sheets in an asthetically pleasing way? That’s the benchmark used today. There’s not a shred of data lifecycle cost or maintenance perspective let alone the cost and impact of those decisions up and down stream from the model.

This is absolutely flawed thinking. When you look at the data required for the built environment, there literally is no commercially available applications on the market today to help you manage this data. Hardly at the project level, and certainly not at the enterprise level. None. They’re all focused on the project model at it’s core….not project data. And certainly not enterprise data.

Yes, there are applications that help you manage portions of data or small genres of data. But nothing exists today which allows a company to manage their AEC ‘Data’ and leverage it across the enterprise. Once again I repeat, NOTHING.

Baseless Claim or Reality?

I’ve been thinking along these lines for some time. Years perhaps. I’ve been in User Groups and Meetups. Vendor Webinars. Industry Conferences. Hallway conversations. Far too many times I’ve heard “Model it” or ‘Add it to the Model”. No debate. No discussion. Just an accepted fact without any hint of value focused thought.

There’s a lot of examples in other industries that suggest alternate thinking. One is Manufacturing which typically leads trends in constriction by a couple decades. Manufacturing has Data Management systems and PLM (Product Lifecycle Management) systems. These are database systems that manage not only models but the data about the models. The key is that the data is associated to the model from an external database. They typically contain a lot of data that isn’t modeled. Anyone model Grease or Paint? A well implemented PLM system will tell you exactly how much you need and where to procure it all without a model of it.

Another notable example is GIS (Geographic Information Systems). A database is at it’s core, not CAD data. CAD data is merely just a small subset of data in a GIS system. Imagine a home changes owners. How does someone at the County get their GIS system updated? They update a database. What aren’t they doing? Opening CAD…Editing a graphical polygon with the owner information and saving the CAD file.

In both of these cases, external databases are linked to and help manage graphical models. The models don’t contain all of the data. And the databases usually contain MORE than just data for the models themselves. Unlike construction where we try to embed every conceivable piece of information right into the model itself.

I’m Not Alone…Anymore

As I said earlier, I’ve been thinking about this for a while. I frequently question my own sanity. Perhaps not as much as those who know me. But I do none the less. So imgine my surprise when I recently came across a couple articles that reaffirmed my thoughts.

This first is this article from AEC Magazine. ‘BIM is Bust’.

https://aecmag.com/opinion/bim-is-bust-how-should-aec-data-work-hok/

The next is the ‘Data Centric Manifesto’. You can read that here…

http://datacentricmanifesto.org/need/

To summarize, enterprise data is locked inside applications (and models). It’s created there and those applications serve as the gate keeper. Yes there’s Cloud services with API’s. But the data they host and control is still application/model centric. It doesn’t integrate with your data. If you want the data, you have to integrate with it. As such, it’s application/model centric. Not enterprise centric.

How Should We Use Models?

By examining how modeling tools came to be, we can understand how those tools should be used,

That start was as a drafting and documentation tool. At it’s core, creating drawings is the act of working out design decisions and documenting them. That documentation is then used to physically build whatever it is you were designing.

As tools progressed, they offered some natural enhancements. 3d helped us visualize not just during the design process but for others who weren’t skilled at visualizing in 3d from a 2d document. Parametric functionality also helped us build smart objects which helped us quickly make derivative designs. These functions also helped increase efficiency in the design process. We lessened the need to calculate small details and merely used smart objects to help build a design. They’re really ‘Digital Pre-Fabrication’.

Here’s one example: The following image is a conveyor support. It’s top and bottom width are variable. So is it’s height and the number of cross bracing panels.

Now look at the holes on the half circular mounting plate. Look also at the holes where the cross-bracing meets. It’s not in the center. What’s the length of that steel angle anyway?

Imagine trying to calculate all of this information from purely numerical data and no geometry. It’s no small task. The number of right-triangles and trigonometry required is quite complex.

If you need to build a few of these, 3d modeling is the perfect fit. The smart objects have made it a digital measuring tool. But what if you fabricated thousands of these? All different. Copying design files and making derivatives with new sizes gets to be time consuming. And the same 5 or 6 inputs drive all of them. And eventually, some of the parts will likely be duplicate as parts from one design just “happen” to match another. And what if the design needs to change? All those models as opposed to just regenerating them.

If you wanted to build a manufacturing system around this, you need a configurator and move data OUTSIDE the model. In this case, that’s what was done.

The assembly is 100% parametrically controlled from a spreadsheet. ALL data driving the model is driven from Excel from 6 inputs. From the length of the angle and position of holes. Even the size and shape of the structural steel shapes is driven from Excel. Here’s the formula for just the length of the selected cross-brace…

So what type of software tools do we have to manage this data at the enterprise level? Sure there’s product configurators but what about you parts library? Historical models and drawings? Common reference data defining shapes and configurations? Vendors and pricing? That’s where you implement data management or PLM systems in manufacturing.

What do we do with that data in Construction? Embed it in a model. Editable only by a Revit/AutoCAD/Microstation user. Locked up and application/model centric.

If you ask me, the solution was obvious. Or so I thought.

The Solution Should be Obvious

One of our technology vendors was pushed hard from many customers like us. The ask was to handle non-model based workflows and data. Their solution? A tool to model data in the field. They built some cool tech that will be helpful in cases, it’s not what was needed or asked. The data wasn’t modeled for a reason. So we didn’t need another tool to model it.

The real solution is to build a tool that can help us manufacture and build from data. No model required. Cutting of linear materials requires very little data as an example. Other operations like purchasing or assembly can be accomplished without a model too. Which means we can procure, manage pricing and labor, and even manufacture vast amounts of parts and data all without a model. None.

If we had tools that let us build WITHOUT a model, then where a model IS required it’s very simple to generate a model and/or link a model to that data. The manufacturing and construction process would have 100% coverage because it’s based on data, not a model.

When you use a model based system, you have partial coverage. You miss all non-modeled work and introduce a second workflow and processes. Also lost are analytics to view your entire operation.

One company I know literally publishes purchased items like buckets of adhesive as generic models. This is done so they can have all work go through their “model based” system and link to an ERP. Is that really what you want? It’s yet another workaround to compensate for lacking tools.

To summarize…

If you build tools that work only with models, they’ll only work with a model.

If you build tools that work with only data, they can also use models because a model is a shortut to data.

Now all we need is someone to start building “Data” centric tools.

Fabrication References – 2023 Update

Fabrication 2023 is out. I’ve updated all the reference information to include 2023 formats. As has been the trend the last few years, little has changed. Summary below…

The 2 Sides of BIM360/Autodesk Construction Cloud

I see a lot of people confused about how BIM360 Docs / Autodesk Docs works when used with BIM360 Design or BIM Collaborate Pro and Revit. It doesn’t help any that Autodesk repeatedly refers to ‘Single Source of Truth‘ as one of the benefits. While BIM360/ACC does help provide a ‘Single Source of Truth‘, it’s not quite as simple as it seems.

There’s 2 Models…Not 1.

Yes, you heard me right. There’s actually 2 models and a virtual ‘Fence‘ between them. One used by BIM360 Design / BIM Collaborate Pro and another completely separate model by BIM360 Docs / Autodesk Docs. This graphics might explain it a little better…

How Things Really Work

Before anyone creates anything, Docs has no files. The following images show BIM360 Docs on the feft and Autodesk Construction Cloud on the right. This will help you see subtle differences however things really work the same.

Next, you model something in Revit and Initiate Collaboration…

Once Collaboration to the Cloud is Complete, if you look at BIM360 Docs / Autodesk Docs quickly you’ll see the file shows up as Version 1 (v1). At this point, you can’t click on the file to view it. Autodesk’s system is merely creating a placeholder while it continues to process the model in the background.

If you wait long enough, you’ll see that the files then update as Version 2 (v2). Once they’re listed as v2, they can be clicked and viewed in the Cloud. Despite saying v2, you really only initiated collaborate once from Revit. v1 was the initial file placeholder and v2 is the finished model that’s processed.

One reason for the confusion is that this v2 model shows up automatically. The common assumption is that it’s the same model as the one you opened in Revit. But that is NOT the case. The v2 model is actually a ‘Processed Copy‘ of the model you had open in Revit. That’s why it took a little while for the v2 model to show up in Docs.

The next time you open the models in Revit, you can see that it shows the models as ‘Latest Published‘. Note that you should be opening the models through BIM360 Design / BIM Collaborate Pro and NOT from the Desktop Connector. More about that later. For now, you can see the models listed when you try to open them in Revit.

If you open these models, they would look exactly the same as those viewed from Docs on the Web. The next thing that happens is people change the model and Sync to Central. This will continue for the entire development of the model. Pretty normal stuff.

Despite syncing changes to the cloud, if you view the models from the web interface of Docs, they’ll still say v2 and show the original published model.

In fact, if you were to close and then try to reopen the model from Revit, you might notice that it now says there’s an ‘Update Available‘. Note: You might need to click the ‘Refresh the current project‘ icon in the upper right to refresh the status. If you haven’t browsed to a different folder/project or restarted Revit the project status cache might be stale and need the refresh.

When an update is available, YOU as the model author can choose when to push those changes to BIM360 Docs / Autodesk Docs. This is why there’s really ‘two sides‘ to models in BIM360. It’s intentionally this way to put you in control. You can control IF and/or WHEN to release your changes to the rest of your team for viewing. After all, you don’t want them to view your partial updates while you’re still working through issues.

You can choose to update the models right from that same interface. Click the ellipsis button to the right of the file entry and select ‘Publish Latest‘.

Once you select to publish the latest version, you’ll be prompted for a confirmation with some added details. You’ll then see the interface in Revit show it’s processing. Once it’s finished processing, you’ll be able to open the model again in Revit. If you look back at BIM360 Docs / Autodesk Docs once processing is done, you’ll see the file(s) there are now listed as Version 3 (v3)

At this point, your web view of the model in BIM360 Docs / Autodesk Docs is the same as when you open it in Revit. That is, until you make more changes and Sync to Central again. Once you have new sync’d changes, you’ll have to publish to Docs again. But only when you’re ready for the rest of the team to view the model.

BIM360 / Autodesk Desktop Connector Warning

It should be noted that the Desktop Connector displays what’s in BIM360 Docs / Autodesk Docs. It does NOT give you access to what you’re currently modeling in Revit with BIM360 Design / BIM Collaborate Pro. This may be perfectly well what you want when linking in a model from another team. But if you want their Live updates, you’ll want to Link from BIM360 Design / BIM Collaborate Pro.

Note that Design Collaboration does have advanced features for collaboration. It’s beyond the scope of this post but highly recommended you look into it.

I hope this helps you understand a little better about how BIM360 Docs / Autodesk Docs does and doesn’t relate to BIM360 Design / BIM Collaborate Pro. Just remember, it’s NOT the same model, it’s a published copy. The only time it shows up automatically in BIM360 Docs / Autodesk Docs is when you initiate collaboration for the first time in Revit. All other Sync to Central updates won’t show up in Docs without an intentional Publish by you or another team member.