Tag Archives: Third-Party Developers

The big Bricsys interview 9 – treading on developers

5 Replies

This is one of a series of posts covering an extensive interview with Bricsys CEO Erik De Keyser and COO Mark Van Den Bergh. Erik explains that Bricsys won’t trample over its application partners in Autodesk-like fashion, except…

Steve: Autodesk is known for treading on its third-party developers and replacing their market. Can you tell us about your attitude to doing that?

Erik: We have always said that we are not stepping into any application market. We will not do it.

There’s only one exception, that’s where there is no [other] possibility. There was no sheet metal. There is no viable [third-party] DWG sheet metal product in the market today for sheet metal. Then we do it, of course.

For BIM, there are. There is a German product. We have talked to those guys, but the problem is, for BIM the way we do it, it’s so deep in the core, the direct modeling engine that we have build… there’s no way that we could expect, of all the partners that are working on AEC, that one would have the strength and the force to bring the product where it is today. We have worked with maybe 30, 40 people for three, four years to do that. I don’t know of any application partner that has more than ten employees. And then those ten employees do everything.

Mark: Except for Intergraph, of course!

Erik: Except Intergraph! Except Intergraph! In the AEC space, I mean. When it comes to making an architectural modeler, there was no other possibility but to do it ourselves. Then we do it. But what we do then is provide all the APIs so the rest of the AEC community can profit off it. Otherwise, I think we would have lost the AEC space. If we didn’t do that, with what we have shown you today on BIM, we would lose the AEC space completely. That could not happen.

This is the complete set of links to this interview series:

The big Bricsys interview 7 – the applications ecosystem

1 Reply

This is one of a series of posts covering an extensive interview with Bricsys CEO Erik De Keyser and COO Mark Van Den Bergh.

In this post, Erik discusses the Bricsys efforts to work with and assist third-party developers. He does this without being prompted by a question – it’s obviously very important to him.

Erik: For our future growth it’s very important, the ecosystem of the applications we have now. We have talked a lot about what we are doing and about our own products, but we should maybe have spent more time on the importance of the ecosystem. The worst thing we could do is forget the application market for us.

We will not, and we are not able, to develop another HVAC system or a [inaudible] system. We are limited in our resources and focused too much in our development. We believe that if there are five or ten HVAC packages, one in Germany, one in France, one in the US and one in Australia, all those guys understand their local markets and it’s very difficult to take an HVAC package made in America and sell it in Germany. The last thing we want to do is destroy that diversity of the application market. On the contrary, we’re going to encourage it. Therefore we will continuously provide APIs to the application market and invite and encourage them to become more professional. This support is so important. That’s where we can make a difference with many of our colleagues, and we should bring the application market to the same level of professionalism. That’s where we are investing as well. They can use all our systems for free.

It would be a great and a wonderful world if you as a customer if you come to our website or you go to an application website and finds the same systems and buys something, and communicates… if there’s a problem, it’s our problem. He can tell us, the application partner can tell us, if it’s an application problem we will tell them or the customer will tell them. But that kind of trio between the customer, us and the application market is so important. We need that.

We need those kind of applications working with our system. And they are there! For over ten years they have wonderful applications. The point is, they lacked, for the moment, the technology to grow into IFC and the BIM market. That’s what we are developing for them now. Right now we need the apps, and we’re delivering to them. But it’s a very important thing for us, that ecosystem. And again I think that’s another difference between us and many, er, alternatives (laughs).

Steve: Not saying “the A word” there…

Erik/Mark: (laughs)

Steve: It’s something I’ve noticed for years, actually, that you guys look after the third-party developers whereas Autodesk sees them as a revenue source.

Erik: Absolutely. We are convinced we need them. They have to say they need us as well. That’s a very good symbiosis. And the top of that is Intergraph. For us, it’s an application partner, right? There’s scalability a bit more than before.  If Intergraph takes this step, let us invite every other application developer to do the same.

This is the complete set of links to this interview series:

Where have all the developers gone?

4 Replies

I noticed in Ralph Grabowski’s latest upFront.eZine that Autodesk has announced that 100 developers have 200 add-ons working with its 2009 series of software. I hope I’m not supposed to be impressed by those numbers. I remember when Autodesk boasted about having over 3500 third-party developers. What happened to the other 3400-odd? This is a serious question; if anybody knows where they all went, and why, I’d love to know.

Of those two hundred 2009-ready applications, how many of them take advantage of 2009’s Big New Feature, the Ribbon? My guess would be close to zero. Why? Because the AutoCAD 2009 CUI architecture is all wrong. Adding custom stuff to the Ribbon is simply a lot more trouble than it’s worth. Even Autodesk’s own vertical teams have shunned it.