Excel Based Model Generator extension. Is it really gone?

[loren_routh]

Just wanted to verify the add-in is no longer available, and if so, why? 

Now more than ever, we need these types of tools.  I currently use Dynamo to create entire buildings from Excel and, while it works, it's slowww.  Any info would be appreciated.  Source code?  This plugin needs to exist!

Here is a blog post about it with some screen shots.

Thanks,

Loren

[RSomppi]

That was a third party Add-In that does not come up with a search of the available apps. Why? is a question for the developers. Seeing that is was subscription based, I'm going to guess that they weren't getting enough sales.

Have you tried searching the web for your need? It seems very specialized and only results in a smattering of results.

[loren_routh]

Hi @RSomppi ,

It was part of a Revit Extension Pack for subscribers of Revit, not 3rd party as far as I can tell.

I have been researching (on the web) for months to learn how to develop an addin that does the same thing as this Excel Based Model Generator, which I randomly stumbled upon.  As you mentioned, there is only a smattering of results. 

But someone developed it and there must be people at Autodesk who have knowledge about why it was discontinued.  I would rather use something existing but may have to code it myself,  a daunting task.

If someone could point me to the developer or any info about the extension, it would be greatly appreciated!

Thanks,

Loren

[RSomppi]

---

@loren_routh wrote:

It was part of a Revit Extension Pack for subscribers of Revit, not 3rd party as far as I can tell.

---

I could be wrong. I assumed it was 3rd party because the blog post said it was only available on the exchange app website.

---

@loren_routh wrote:

But someone developed it and there must be people at Autodesk who have knowledge about why it was discontinued. 

---

Knowing why isn't going to help at all. Almost eight years later, as it seems it was not available after 2014, anyone that knows why it was so short lived may have moved on. Again, not critical knowledge for you goal.

[pendean]

Forgive me for asking, and I'm just curious more than anything since I stumbled on this post, but did you recently moved away from REVIT2014 where you used this add-in all the time?

Or... on a hunt for something faster that your current solution, you stumbled on this add-in in a websearch, then decided it is the solution for all of your woes, and need it without ever experiencing it?

Either way, good luck with your search, look like the developer either vanished or it was an in-house Autodesk tool that is buried deep over there.

[loren_routh]

Thank you @RSomppi and @pendean for your feedback on this subject.  Here is my situation:

The organization I work for has thousands of buildings in their portfolio.  Only a small fraction have BIM models, but they all have CAD files.  Part of my job is to get us into the 21st century, technology-wise.

I have developed a workflow that will translate CAD floor plans into Revit models.  Many people have attempted this, but none are doing it my way.  This is done by processing CAD files in FME, which creates a spreadsheet with everything Revit needs for a LOD 200/300 model, then use Dynamo to interface with the API.    If you are not familiar with FME, I highly recommend checking it out.  

As you can imagine, creating thousands of Revit models manually would take a lifetime and cost millions.  My method has the potential to do it far more quickly, and virtually free.   With FME, not only can you process CAD files, but also Revit files.  This gives you a workaround to the backwards-compatibility issue.  Dynamo is awesome, but has performance issues by nature.  A proper plugin would make things easier for others to use and faster. 

The reason I want to know why it was removed is to understand any issues that were faced.  Maybe they didn't want to spend money supporting it, or it competed with another product?  If I can get in touch with the developer (assuming they are alive), I could see about hiring them or lobbying Autodesk to include the addin again.  Believe it or not, this is possible.  If you are familiar with Revit's Interoperability Tool addin, that was developed through my office and is now part of the standard install.

For the New Year, my goal is to refine/enhance my process and replace Dynamo with a more efficient tool, whether existing plugin or my own creation.  My view is we need to bootstrap our way into BIM with automation and creative use of existing tools.  To address the many problems in the building industry, we need a critical mass of BIM models in order to get there.  The Excel Based Model Generator may be the missing ingredient!

Thanks,

Loren

[RPTHOMAS108]

Was part of the extensions and that was discontinued, I recall it but never really used it.

Do you have a sample Excel file for this input?

In general I would try to avoid Excel COM, it is a bit unnecessary for this task (csv output from Excel would work just as well). You always encounter that 1% that seem to have an incorrectly registered Excel COM server.

[loren_routh]

Hi @RPTHOMAS108 ,

Very interesting,  did not think about Excel COM vs Csv since Dynamo uses both.  I have attached an older file which has been used with a Dynamo script to generate a floors worth of elements.   This can be modified to fit any requirement.  My current version creates strings in Designscript syntax.  In Dynamo, a Python script with Regex creates the geometry (points, lines, arcs).  It streamlines my workflow on both ends!

Since I have never used or seen the add-in beyond a few screenshots, I really can't say it will work.  On the other hand, when you name your plugin "Excel Based Model Generator".....

Regardless, the fact that it existed lets me know it was a priority, however short-lived.   I'm sure Autodesk had its reasons.   All this talk about automation with people still slogging away, translating 2D drawings into Revit by hand.  Not if I can help it!  

[RPTHOMAS108]

That is not how I remember it to be honest. If it was about generating Revit elements from a spreadsheet then why is the data in such an inconvenient form for Revit input?

For example regarding vertical/slanted columns (two level based family instances) all you need is:

Family, Type, Level, Level, XY, XY, Offset1, Offset2, Orientation(XY)

Instead of this you have:

(1)Floor_ID, (2)Column Family, (3)Column Diameter, (4)Column Type, (5)COLUMN_CTR, (6)Length, (7)Width, (8)SQUARE_COLUMN

Column 4 would alone establish (3),(6) & (7),

Column 8 appears to be a bounding box but not sure why it has five points with the last the same as the first? Again you don't really need this column since type would cover size and therefore bounding box.

Not 100% on understanding the WALLS tab, would wonder what the curve types represented by the various 2D point sets in Wall_Lines relates to?

Can't see much that would allow me to know the height of the Walls/Columns etc.?

On the GRID tab there is the FLOOR_ID column which again seems odd for Revit (where grids are not level based).

I think instead of this I would look to think about how a Revit model is built-up e.g.

Grids, Levels, Columns, Primary Beams, Division of primary beams for secondary beams (fixed number, max spacing etc.). Build relationships in a way that allows the model to be grown.

Similar to analytical models you may prefer to define nodes and then members between such nodes. That approach ensures better connectivity as two members with the same end node id have the same end point regardless of dimensional imperfections in how the nodes were defined i.e. why define the same point ten times or more? Define the thing, give it an id and refer to it elsewhere.

[RSomppi]

---

@loren_routh wrote:

The organization I work for has thousands of buildings in their portfolio.  Only a small fraction have BIM models, but they all have CAD files.

I have developed a workflow that will translate CAD floor plans into Revit models. 

---

Why? Are all of the buildings in need of BIM models? What is driving this need?

[loren_routh]

As I stated in my reply, the spreadsheet can be formatted to fit the add-in
requirements. Don’t worry about what column is where

The point is that I am able to synthesize accurate coordinates, wall
thicknesses and other info into a spreadsheet, which can be used to create
a Revit model. The spreadsheet I attached works perfectly when used in a
specific Dynamo script.

It’s becoming obvious to me that there isn’t something existing I can use,
so I am slowly learning to make my own. See you in the Revit API forum!

[loren_routh]

Why? Because Revit.

[RSomppi]

---

@loren_routh wrote:
Why? Because Revit.

---

Where's the value? Do you have upcoming projects for all of these buildings or is this just an exercise for the sake of updating archived projects?

Sorry but I don't get updating 1000s of buildings just for the sake of it.

[syman2000]

Autodesk is notorious for killing extension apps. I remember Timber plugin was great but Autodesk end it since 2019. So I would look at 3rd party like Diroots sheetlinks

https://diroots.com/revit-plugins/revit-to-excel-sheetlink/

[loren_routh]

Yep, that sounds like AutoDesk. I looked at the Diroots plug-in and it
only creates rooms and spaces.

The journey continues…

[loren_routh]

All of these buildings either have projects currently or will in the
future. That’s how buildings work, but that’s not the point. When you
have systems in place that rely on outdated technology (ie CAD, paper) it
is very hard to make a change unless you find a way to transition that
isn’t cost-prohibitive and also provides tangible benefits. The
architecture and construction industry have embraced BIM but we are behind
the curve. BIM will not only make projects more cost effective but provide
better info to building managers, O&M, and portfolio managers. That’s the
plan, anyways.

[RSomppi]

---

@loren_routh wrote:
All of these buildings either have projects currently or will in the
future. That’s how buildings work, but that’s not the point.

---

Actually, it is the point. If the buildings are ongoing projects that need/want to be done in Revit, then they MIGHT need to be converted. Arbitrarily doing so "because Revit" to archived projects is a huge waste of resources with nothing gained.

[loren_routh]

Putting aside whether a building “needs” a Revit model, the System needs
to change, and is changing. One way to accelerate this change is to find
ways to generate models in a cost-effective, quick, and accurate way. It’s
a feedback loop where the more models are available, the more they will be
used, and the systems will adapt to the new requirements. It is also a
culture change which is the most difficult part. I have found that if you
don’t make a big deal about it and just start doing it, people will come
around and in some cases, not even notice anything changed. There are
plenty of naysayers out there, so my task is to “build it and they will
come”.

I am literally one plug-in away from accomplishing this! Instead of
spending $100k+ in A/E fees and several months time per building, we can
use our existing software to generate a model with enough detail to be used
not only in projects, but as a way to connect other stakeholders with info
that is normally hard to get.

The models are the beginning, not the end.

Thank you for the questions, it helps me articulate what I am trying to
do. You are definitely not the first person to ask why!