Tag Archives: CAD Management

Addendum – Why every AutoCAD CAD Manager should have a copy of BricsCAD – part 1, fixing drawings

2 Replies

This post is an addendum to a post from June, Why every AutoCAD CAD Manager should have a copy of BricsCAD – part 1, fixing drawings. This post provides new information about useful functionality added in V19 of BricsCAD that is useful for any CAD Manager or power user who ever has problem DWG files to deal with. Yes, even if your site is still purely AutoCAD-based.

In this post I’ll describe the (inspector) LISP function. This was added in the V18 cycle but was significantly enhanced in V19. It’s probably the most useful LISP function you’ve never heard of.

Although it’s LISP, that doesn’t mean you have to be a programmer to benefit from it. If you’re a non-programming CAD Manager or power user, you can use it to work out what’s going on within any DWG you’re having problems with. You can use it to discover information about objects in the drawing; not just conventional entities, but also blocks, tables, dictionaries and so on. It even works with custom data.

I gave a brief demonstration of (inspector) in the last BricsCAD Unplugged episode about BLADE. However, you don’t need to use BLADE; just enter (inspector) at the command prompt, select an object and you’ll be presented with a dialog like this:

These dialogs are modeless, and you can have as many displayed as you like; you’re not limited to one. This dialog displays the same data in three different ways. At the top, it’s shown in traditional LISP assoc form, and by playing with the Expand controls you can vary the way in which this is pretty-printed. The bottom left pane shows the data in DXF form, which is probably easiest to read if you’re a non-programmer. If you’re more of an ActiveX person or you prefer to see the properties described with words rather than numbers, you’ll prefer the display on the bottom right, which shows the COM properties for the object.

If you want to select another object to inspect without calling (inspector) again, just use the [ > > ] button.

The grayed-out lines indicate data that is considered read-only. It’s important to note that this doesn’t mean it’s impossible to change the data, merely that the ways in which that data can be changed within a program is restricted. Generally, it means you can’t change the ActiveX properties directly, but there are various other means that can be employed in many cases.

The lists are somewhat interactive; double-click on an entity name and you’ll be given another inspector window for that entity. You can burrow down through the drawing database in this way, looking for the source of your mystery DWG problem. If you’re using it while programming, you can use it to work out what set of circumstances is causing your code to trip up in certain drawings.

The (inspector) function has an optional argument, and what it will accept is very flexible. If you pass an entity name to it, you will get the data for that entity displayed. The same principle applies for various ActiveX objects: pass it a layer table object and the appropriate data will be displayed.

Direct access is provided to various useful things from within BLADE using the pull-down menu Lisp+DCL > Browse DWG Database:

If you pick Browse Text Styles, you’ll see something like this:

Double-click on one of the text style items in the left pane and you will get this:

As you can see, this is very handy for tracking down issues both while programming and when diagnosing DWG problems.

Finally, I should note that there is potential for the inspector to provide even more power in future. Bricsys LISP guru Torsten Moses is investigating the possibility of allowing the inspector to modify data, not just inspect it. There’s potential danger there, but if Torsten can make that work safely then that would be another invaluable tool for any DWG-based CAD Manager.

As I stated in my original post, it’s definitely worth a CAD Manager’s while to do the quick download and install of an evaluation BricsCAD. My experience in dealing with Bricsys is that requests for extensions for evaluation purposes are usually accepted, so you probably won’t have to give up your valuable tool as soon as your 30 days are up.

Why every AutoCAD CAD Manager should have a copy of BricsCAD – part 6, future proofing

2 Replies

This is the sixth and final post in this series where I explain why this statement holds true:

As a CAD Manager looking after AutoCAD users, or a power user looking after yourself, it’s worth your while to have a copy of BricsCAD handy.

This post explains why adding a copy of BricsCAD to your stable of AutoCAD licenses is a good thing for your future and that of your company.

A CAD Management thing I did a few years ago was to examine the options for replacing AutoCAD and other Autodesk products. I was an AutoCAD loyalist (albeit a somewhat critical one) with over a quarter of a century invested in it. I was looking after the deeply entrenched and very heavily customised CAD environment of a major public utility company that had been using AutoCAD as its primary CAD system since the late 1980s. Hundreds of custom commands were in place and providing priceless productivity benefits. Hundreds of thousands of DWG files were on file, with thousands more coming through every month. The inertia behind AutoCAD was very, very strong. Looking outside the cage was a pretty radical step to take. What led me to that point?

  • Autodesk business policy. Autodesk has become increasingly anti-customer over the years in ways that will be familiar to all readers of this blog. I won’t rehash them here. This leads to…
  • Increasing costs. Autodesk software is expensive and getting more so. Autodesk has made no secret of its intention to move to an all-subscription (rental) model. This is an attempt to treble the ongoing income Autodesk receives, in return for doing as little as possible. Which leads to…
  • Lack of progress. It had become clear that the days of AutoCAD seriously improving from release to release were over, never to return. This isn’t because there is no room for improvement, it’s because Autodesk doesn’t want to improve AutoCAD. AutoCAD won’t be permitted to become too capable because that would just eat into sales of Autodesk’s other products. You’re not going to see 3D parametrics or sheet metal capabilities in AutoCAD: buy Inventor instead. You’re not going to see BIM capability: buy Revit. Beyond the internal competition issue, some years ago, Autodesk leadership lost interest in what it perceived to be an old-fashioned dead-end product. The income from AutoCAD customers is being diverted to fund purchase and/or development of more fashionable and interesting products.
  • Frustration with Autodesk’s Beta program. The goings-on within the Autodesk Beta program must remain private, so what I can say here is limited. I can say that I spent many years contributing large numbers of hours to that program in order to attempt to improve the product. As time went on, the positive results that emerged from that effort decreased; that much is no secret because it is apparent in the product. I felt I was fighting against Autodesk to try to improve the product, and losing. There were a few final incidents that persuaded me to stop bashing my head against that particular wall. I wasn’t the only one. I stuck it out for years longer than many very valuable people who had already given up before me.
  • Proxy server issues. Over the years, Autodesk’s habit of attempting to do sneaky things to access the Internet had caused a variety of problems in a secure proxy server environment. This caused several things not to work, and harmed performance severely in some places. As Autodesk’s developers turned over, things that worked in one release would not work in the next. Attempts to get this addressed as a support issue would result in the environment being blamed. These problems increased over the years as Autodesk threw in more and more connectivity-requiring features. There was a non-zero and ever-increasing possibility that one day, Autodesk would screw things up altogether and leave us with non-functioning software. That has already happened for some people, and although the stoppage has generally been temporary, it is important to have redundancy.
  • Poor performance. AutoCAD has been getting bigger and slower. Downloads are huge and Autodesk does its best to make them as difficult as possible. Installations take an age, as do uninstallations. Startup times are terrible and getting worse. My users were complaining – a lot – and there wasn’t much I could do about it.

That’s what moved me to take a very, very serious look at alternatives. Your motives may differ. Just the desire to have a Plan B in case of disaster might be enough.

If you don’t feel moved to investigate, you may eventually be faced with no option. Sooner or later, the person who holds the purse strings at your company may point to this year’s much bigger Autodesk invoice and ask, “What are we getting for this? How can we reduce our costs?” When that happens, you don’t want to be scrabbling round for answers before that invoice needs to be paid. Look into the options in advance. Are you really wedded to AutoCAD or are you actually tied to DWG?

Days of Future Past

Here’s my suggestion. Examine the available alternatives to AutoCAD and the other Autodesk products you use. Do it sooner rather than later so you get the chance to determine the answers to non-trivial questions like these:

  • Capability. Does the alternative product do everything that AutoCAD does, that your users need it to do? Does it do other stuff that AutoCAD doesn’t that you might find useful? What’s the performance like? How does it work on the hardware you have? Does it have user interface elements that don’t just look good but work productively in practice?
  • Compatibility. You will almost certainly demand extremely good DWG compatibility, but this question goes well beyond that. Will your LISP work? How about DCL? ActiveX support? DOSLib? Other programming languages? Can you carry over your customisation files? Can you make the interface look the same? If you have custom toolbars, or ribbon, or even image menus, do they carry across? Can your users carry across their skills without downtime, extensive training and a productivity hit? Can AutoCAD and the potential replacement coexist without issues? Can you use a common set of custom support files pointed at by both products? Will it work well on your hardware?
  • Add-ons. If you’re using third party products on top of AutoCAD, or if you’re using an AutoCAD-based vertical, is that product or an equivalent available? Does it work well? What do the objects they create look like in plain AutoCAD? Can you round-trip through AutoCAD and back and retain your intelligence? You’re probably going to have to test this with evaluation software and your own data.
  • Licensing options. Is perpetual licensing available? Can you stick on a release for a few years and still purchase upgrades later? Has the company committed to providing you with licensing options or has it made noises about going all-rental? Is network licensing available? Does it coexist problem-free with Autodesk’s network licensing software?
  • Costs. Compare the likely costs for all your options over several years. You’re going to have to make some assumptions. It can be difficult to work out what they should be.
  • Track record. Has the company been around for a while? What reputation does it have? Does it treat its customers with respect? How good is the support?
  • Future prospects. Is the company likely to be around long-term? Is it actively developing the product you’re interested in? Is it innovating? Is it merely following AutoCAD at a distance or charging ahead? Is the product going to be limited by Autodesk-like internal competition?

I went through all of these questions and settled on BricsCAD as the best option in my company’s case. In fact, several aspects made it really the only viable option. The product impressed me with high performance, capabilities well beyond AutoCAD in several important areas, a very high degree of compatibility (particularly LISP but also other customisation files), the availability of perpetual licensing and much lower ongoing costs. The company impressed me with its honesty and attitude toward customers.

Most of all, I was won over because I could see that the product had a future. Subsequent improvements have only strengthened that view.

Obviously, you need to make your own judgement based on your own circumstances. I would suggest looking at all the options, including sticking with AutoCAD permanently, with or without subscription or maintenance. Maybe you can use my investigations as a starting point, but I encourage you to start investigating now rather than when you’re under time pressure and don’t have time to do a thorough job.

It will cost you a few minutes to download and install of an evaluation BricsCAD and start preparing for the possibility of a different future. Maybe it won’t turn out to be part of your company’s future, but it could still be part of your future.

Options are good. Learning is good. Best case scenario, your knowledge is going to save your company money and improve its productivity, and you will end up smelling of roses. Worst case scenario, you’re going to spend some very justifiable time doing something new, different and interesting. I recommend it.

Other posts in the Why every AutoCAD CAD Manager should have a copy of BricsCAD series:

Part 1, fixing drawings
Part 2, 3D operations
Part 3, parts on demand
Part 4, efficiency
Part 5, LISP

Why every AutoCAD CAD Manager should have a copy of BricsCAD – part 5, LISP

5 Replies

This is the fifth post in this series where I explain why this statement holds true:

As a CAD Manager looking after AutoCAD users, or a power user looking after yourself, it’s worth your while to have a copy of BricsCAD handy.

This post is about BricsCAD being better than AutoCAD at the one thing that made AutoCAD win the race against its competitors back in the 80s – LISP. That is, AutoLISP (added fully to AutoCAD in Version 2.18) and Visual LISP (fully integrated with AutoCAD 2000).

If you’re a good AutoCAD CAD Manager, you’ll already know the reasons LISP is an extremely important tool, so I won’t cover them here. I may explain those reasons in a later post, but that would distract us from the main point. Why is having a copy of BricsCAD useful to a CAD Manager?

  • BLADE. I’ve covered the BricsCAD LISP Advanced Development Environment in various posts already, and I intend to go into greater detail in future posts. There are enough advantages over VLIDE to warrant an entire series of posts. This is simply the biggest advance for CAD LISP in 20 years; if you’re doing any reasonably complex development in LISP and you’re not BLADE, you’re wasting time and money.
  • Performance. Because BricsCAD’s LISP engine is much more modern than AutoCAD’s, the performance is much greater. In my experience, it’s about three times as fast. Some function calls are as much as 30 times as fast. If you have a user who’s complaining that your routine is taking an age to process in AutoCAD, try it in BricsCAD instead. I once saved a user half an hour in processing time for one polyline by using BricsCAD. Another aspect that will benefit you when programming and testing is BricsCAD’s generally superior performance. Got nothing running and want to get programming in the next 5 seconds? Fire up BricsCAD. Want to do a complex process on a big drawing that makes AutoCAD run out of RAM? Try it in BricsCAD.
  • Licensing. While you’re developing in BricsCAD, you’re not using up an expensive AutoCAD license. You’re using a cheaper (or even free, while you’re evaluating it) BricsCAD license. Also, it’s a perpetual license so if you ever stop paying, you can keep developing as long as you like. Oh, and it’s not going to flake out on you on those days where Autodesk’s subscription licensing server has a meltdown.
  • Extra functionality. BricsCAD’s LISP has the AutoLISP and Visual LISP functions and then some. Some of the DOSLib functions are available without even needing DOSLib, but if you need the full set of DOSLib functions they can be loaded, as per AutoCAD. A range of extended functions are available with the vle- prefix, and the LISP Developer Support Package documents these and provides the source code so you can also use them in AutoCAD.
  • Platform independence. AutoCAD for Mac has severely restricted LISP capabilities, making it unsuitable for use in a professional, efficient custom environment. BricsCAD for Mac and BricsCAD for Linux both provide practically identical functionality to the Windows version. Yes, BricsCAD for Mac really is significantly more AutoCAD-compatible than AutoCAD for Mac.

I do my LISP development in BricsCAD these days, and can attest that it’s well worth the investment in time to get the hang of BLADE.

It will cost you a few minutes to download and install of an evaluation BricsCAD and check out the LISP situation for yourself.

Edit: it’s not just LISP. See James Maeding’s comment below about .NET, too.

Why every AutoCAD CAD Manager should have a copy of BricsCAD – part 4, efficiency

2 Replies

This is the fourth post in this series where I explain why this statement holds true:

As a CAD Manager looking after AutoCAD users, or a power user looking after yourself, it’s worth your while to have a copy of BricsCAD handy.

This post is about BricsCAD being more efficient than AutoCAD for some of the things a CAD Manager might need to do. What do I mean?

  • BricsCAD starts up and closes down faster than AutoCAD, much faster in some environments. If your AutoCAD starts up slow (e.g. in some secure proxy server environments), pretty much any job you need to do to a user’s drawing that involves getting in, doing something quick, saving and getting out again is likely to be finished in BricsCAD before AutoCAD is even open.
  • If you perform a more complex operation on behalf of a user that is likely to take a while, there’s a better-than-even chance that BricsCAD will do it quicker than AutoCAD. In some cases it will do it much quicker (e.g. drawing compare).
  • BricsCAD tends to be able to cope with large drawings while using less memory than AutoCAD. If you have a user with a huge drawing who can’t work with it any more in AutoCAD and you need to split, purge or simplify it before it is usable, the very process of doing that in AutoCAD can itself be unworkably slow. Try the same thing in BricsCAD and there’s a good chance you’ll get the job done in a fraction of the time and without the same level of frustration.
  • If you perform a batch process that operaties on a set of drawings, under most circumstances it will be finished in BricsCAD well before the same thing is done in AutoCAD. Maybe this means you can process a set of drawings over lunch rather than wasting all afternoon on them or waiting until home time before setting the batch going. Plus you’re occupying a cheap BricsCAD license rather than an expensive AutoCAD one. Also, because BricsCAD uses much less RAM than AutoCAD while running, you can run your batch processes on that old PC sitting in the corner rather than having your top user sitting around watching your top spec PC grind away.
  • Certain user interface structures in BricsCAD are much more logically arranged and efficient to use than the AutoCAD equivalents. For example, if you have a drawing with an obscure setting that needs changing, unless you have an impeccable memory, you’ll find that setting much more quickly using the BricsCAD Settings command.

As I mentioned in my last post, this series is all based on stuff I’ve done in real life as a CAD Manager for a primarily AutoCAD-using company. Feel free to add your comments with your own experiences, even if they differ from mine.

It will cost you a few minutes to download and install of an evaluation BricsCAD and check out the performance and efficiency for yourself.

Why every AutoCAD CAD Manager should have a copy of BricsCAD – part 3, parts on demand

1 Reply

This is the third post in this series where I explain why this statement holds true:

As a CAD Manager looking after AutoCAD users, or a power user looking after yourself, it’s worth your while to have a copy of BricsCAD handy.

This post is about using BricsCAD as a mechanical and structural parts library for your AutoCAD users. As I mentioned in my last post in this series, I was writing a client-specific AutoCAD 3D training course recently. To demonstrate the concept of revolving profiles, and also to compare and contrast different styles of solid creation, I wanted to use a ball bearing as an example. The easiest way for me to get hold of an accurate example ball bearing model was to fire up BricsCAD (a few seconds) and select the part from the Standard Parts panel (a few more seconds).

It gets inserted as a block. After explosion to reduce it to 3D solids, I could then slice it in either BricsCAD or AutoCAD to form the basis for my example. I could save it at any stage in BricsCAD and open it in AutoCAD to continue to work on it seamlessly. What I can’t do is simply copy and paste from one application to another; you do need to save the DWG. You can then open it in AutoCAD or access the blocks using AutoCAD’s DesignCenter palette; if you’re doing this a lot you might want to point DesignCenter to a scratch DWG you keep handy for this sort of parts exchange.

There are currently 13 sets of standards:

Although you may already have your own parts library, having access to a wider range of international standards may prove useful. Aussie steel sections? Go for your life, mate.

Just how much stuff is available? A lot. Each of the sets of standards has multiple sections, each section has many parts, and many of the parts have many sizes. Depending on the part, other parameters (such as bolt length) may also be available for a given size.

Here’s the full Standard Parts panel in action, in this case selecting a nut.

BricsCAD Pro and Platinum have 3D parametrics built in (and given the minor extra cost I’d suggest going for Platinum), so it’s quite feasible to use it as the basis for your own 3D parts library. If you’ve built up a few 2D dynamic blocks in AutoCAD, you’ll be quite capable of doing the same thing in 3D in BricsCAD. The methods are different but straightforward enough to teach yourself.

As pointed out in a comment by James Maeding, you can set up a network license or two and install BricsCAD on everybody’s PC, giving everybody access to the goodies without excessive cost. Bear in mind that like Autodesk, Bricsys charges a premium for a network license over a standalone one. Unlike rent-or-go-forth Autodesk, Bricsys allows you to have a perpetual license and the total cost of ownership is substantially lower.

By the way, this series isn’t theoretical, it’s all based on stuff I’ve tried out in the real world. For example, the network license software will happily coexist with Autodesk’s network license software on the same license server. The services ignore each other; no clash, no problem. My experience is that it works just fine on a virtual server.

It will cost you a few minutes to download and install of an evaluation BricsCAD and check out the included parts content for yourself.

Why every AutoCAD CAD Manager should have a copy of BricsCAD – part 2, 3D operations

2 Replies

This is the second post in this series where I explain why this statement holds true:

As a CAD Manager looking after AutoCAD users, or a power user looking after yourself, it’s worth your while to have a copy of BricsCAD handy.

This post is about using BricsCAD to do things to help out your AutoCAD users who are having problems with 3D operations. Why would you bother using BricsCAD to mess with AutoCAD 3D models? Because sometimes AutoCAD can’t do stuff with them, and BricsCAD can.

If you have a user who finally asks for help after fighting AutoCAD for ages trying to get an operation to work such as an awkward fillet, a self-intersecting extrusion or a direct edit that doesn’t want to move, you have a couple of options:

  1. fight the same fight yourself in AutoCAD, eventually discover that the user was right, and then construct an excruciatingly awkward workaround; or
  2. fire up BricsCAD and see if you can do it there. There’s a good chance it will. If it does, hand the DWG back to the user with a smug look on your face. If it doesn’t, construct an awkward workaround in BricsCAD, because it will almost certainly be faster than doing the same thing in AutoCAD. Direct editing of 3D solids is more flexible and easier in BricsCAD; the Quad Cursor helps a lot.

I’ve been writing a client-specific AutoCAD 3D training course recently, and going through the exercises I’ve developed has been instructive. I’ve lost count of the number of times I’ve thought, “Man, this would have been so much easier in BricsCAD.” That’s before we get to the 3D parametrics that BricsCAD has had for a while and which AutoCAD never will.

Why is BricsCAD so much better than AutoCAD at making 3D work well? Because it has to be. When you base your entire product line (including BIM, parametric 3D, sheet metal and a host of other uses covered by 3rd party developers) on a single DWG-based 3D engine, that engine has to be robust, powerful, efficient and fast.

It’s not as if Bricsys can say to somebody struggling with performing 3D operations in BricsCAD that they should be using Inventor or Revit instead. That cop-out is unavailable. It has to just work.

Fortunately, Bricsys has acquired a small group of genius-level experts in this area, and holds on to them rather than dumping them when they get too experienced. It shows. Overwhelmingly, it just works.

It will cost you a few minutes to download and install of an evaluation BricsCAD and confirm this for yourself. It’s well worth it.

There are exceptions, of course. Nothing is perfect, and you will come across the occasional glitch. But those exceptions are definitely rarer than in AutoCAD. My experience also tells me that if you report those exceptions, there’s an extremely good chance that they will be fixed, and quickly. Bricsys ain’t Autodesk.

Why every AutoCAD CAD Manager should have a copy of BricsCAD – part 1, fixing drawings

2 Replies

Here’s a mega-tip with a lot of experience behind it:

As a CAD Manager looking after AutoCAD users, or a power user looking after yourself, it’s worth your while to have a copy of BricsCAD handy.

Why? There are too many reasons to fit in one blog post, so I’m going to do a mini-series. The first post is about using BricsCAD to fix up drawings that are giving your AutoCAD users problems.

One of the things that surprised me most when evaluating BricsCAD as a potential replacement for AutoCAD was that my expectations were wrong when it came to the reliability of opening DWGs. Over the years, I collected a variety of DWGs that gave various releases of AutoCAD some problems. Some of those problems occurred while performing some kind of editing or processing, while others prevented AutoCAD from opening the drawing at all. I was expecting BricsCAD to have all those problems, plus perhaps some additional incompatibilities of its own.

What happened was the opposite. I don’t think I came across a single drawing that AutoCAD could open but BricsCAD couldn’t. On the contrary, BricsCAD was much more forgiving than AutoCAD, breezing through the process of opening drawings that had problems that originated in AutoCAD. Maybe 80-90% of my “problem” drawings were problems for AutoCAD alone. In many cases an AUDIT in BricsCAD and a re-save was enough to make the problem go away in AutoCAD. In other cases I could use BricsCAD to recover the unrecoverable using the traditional methods of WBLOCK, saving as an earlier release, saving as DXF, binary search (I may do a later post on exactly what that means), and so on.

Note that you may be able to obtain similar results using other DWG-based products such as DraftSight, ZWCAD or even the free BricsCAD Shape. However, I don’t have the experience with those products to be able to confirm that. Autodesk’s DWG TrueView, being a cut-down AutoCAD, tends to have the same problems as AutoCAD.

One thing that was particularly pleasant about using BricsCAD to fix problem drawings was the speed at which it could be done, because of BricsCAD’s generally superior performance. Closing and opening AutoCAD is painfully slow these days as the bloat gets worse, so having a product that fires up quickly is very handy.

Also handy is the availability of tools within the product that make it easier to locate and fix problems. Of particular importance is the Drawing Explorer, which provides a consistent and efficient interface that provides access to over 20 different types of aspects of a drawing (e.g. layers, linetypes, text styles, etc.):

One example arose showing how useful this is, when my users were having an intermittent problem with some drawings locking up AutoCAD 2015 on open. Some trial and error made it possible to discover that the trigger for this was the existence of a text style (any text style) with a bigfont attached, where the bigfont SHX file did not exist. It was possible to fix this in an earlier or later AutoCAD release, which the users may or may not have available to them, by opening the drawing, using the STYLE command, then using that dialog box to go through each text style one at a time, looking for bigfonts.

It was much easier to quickly fire up BricsCAD, use the STYLE command which opens the Drawing Explorer in the Text Style section, and see all of the text styles laid out at once (see above). It was very efficient to quickly look for recalcitrant bigfonts and make them go away, or to see instantly that bigfonts weren’t the problem.

Similarly, the consistent, searchable and efficient interface of the BricsCAD Settings dialog makes it easy to check the values of any settings that you suspect may be triggering the problem in AutoCAD:

As a CAD Manager, it’s definitely worth your while to do the quick download and install of an evaluation BricsCAD. My experience in dealing with Bricsys is that requests for extensions for evaluation purposes are usually accepted, so you probably won’t have to give up your valuable tool as soon as your 30 days are up.

Once you’ve determined that it really is an invaluable tool to have around, the cost of entry is low enough to make it relatively easy to justify the investment. You won’t need to recover many drawings to get your money back.

Steve’s BLADE presentation at the BricsCAD New Zealand and Australia Roadshow

3 Replies

Sofoco (Australia) and CAD Concepts (New Zealand) recently ran a series of seminars throughout Australasia demonstrating BricsCAD. I attended the last of these in Brisbane on April 19 and gave a presentation about BricsCAD’s LISP, with reference to AutoCAD compatibility and the tools available to CAD Managers and developers, including BLADE. The talk was aimed at anybody who is writing or maintaining LISP code for AutoCAD or BricsCAD.

I had the just-before-lunch slot, which is never desirable for a presenter. People are dozing off and/or bursting to go to the toilet, and time adjustments have to be made if earlier presentations run over. I started 10 minutes late and therefore had to remove the demonstration part of the presentation on the fly, but I had planned to allow for that eventuality. It’s been a while since I have presented like this before an audience so I was a bit rusty and it wasn’t as free-flowing as I would have liked. Too many ‘erms’!

Steve’s invisible accordion is impressively large

I did manage to keep the whole audience in their seats until the end, though, so that’s something. Maybe the fact that I was waving a sword around had something to do with it.

Here’s my video, which is 21 minutes long. The sound is a bit muffled and my accent is Australian, so you might want to turn on subtitles using the CC option in the YouTube player.

Disclosure: the organisers covered part of my expenses.

The game has changed – Robert Green migrates to BricsCAD

10 Replies

Is anybody left who still thinks BricsCAD isn’t a serious replacement for AutoCAD? If that’s you, perhaps the latest news might make you take it seriously. No, not the Heidi Hewett news. Even more recent news than that!

Robert Green, CAD Management guru, Cadalyst writer and consultant (not to mention a rather good guitarist) has been announced as the first Bricsys Certified Migration Consultant.

Image courtesy of Bricsys

Read all about what Robert has to say on this Bricsys blog post.

Anybody who has been reading this blog for the last few years will be surprised by none of what Robert has to say in that blog post. It’s not merely a repeat of what I’ve been saying for some time now, it’s all factually correct and easily verifiable by any competent CAD Manager.

I’ve been there and done that. I’ve gone through the process of taking a very complex custom AutoCAD environment, applying it to BricsCAD and giving it to my users. They loved it. No training was required to work as usual. Most things happened quicker, more conveniently, or both, starting right from the speedy installation. Once the product is in place and established, training can then be applied to take advantage of the places where BricsCAD is ahead of AutoCAD.

If you’re a CAD Manager where AutoCAD is used and you haven’t checked out BricsCAD yet, it’s about time you did.

This might come as a shock to those who see Autodesk domination of DWG CAD as a permanent fact of life, but the game has changed. AutoCAD’s stagnation and comments by senior figures show that the former flagship is clearly unloved by the powers within Autodesk. AutoCAD LT, even more so. An unimpressive AutoCAD 2019 shows that major improvements can no longer be expected in exchange for your ever-increasing annual payments, and with large numbers of people having been offloaded from the research and development teams, who would do it anyway? Meanwhile, BricsCAD development shoots ahead.

Thanks to decades of hostility towards customers that has only accelerated in recent years, Autodesk can’t even rely on customer loyalty for survival. When there’s a serious competitor that offers an easy migration path, the inertia that has kept Autodesk alive so far in the DWG space is no longer enough. The feeling among industry observers I meet is that Autodesk is in a decline of its own making. The only debate is whether that decline is temporary or terminal.

Back to Robert et al. Autodesk has lost many good people, and Bricsys is gaining them. The momentum is clearly with the Belgian company. Anybody want to run bets on who the next big name defector will be?

Steve at the BricsCAD New Zealand and Australia Roadshow

Leave a reply

Sofoco (Australia) and CAD Concepts (New Zealand) are currently running a series of seminars throughout Australasia demonstrating BricsCAD.

Here are the dates and locations:

Auckland – 9 April 2018, Jet Park Hotel and Conference Centre
Christchurch – 11 April 2018, Christchurch Community House
Melbourne – 17 April 2018, Airport Motel and Convention Centre
Sydney – 18 April 2018, Stamford Plaza Sydney Airport
Brisbane – 19 April 2018, Royal on the Park

Each seminar is in two parts. The morning session is for leaders and decision makers and the the afternoon is less structured and goes into more details, with informal discussions, questions and answers and one-on-one sessions. There will be many short presentations from various presenters to demonstrate the different things that BricsCAD is capable of, with or without third party add-ons.

I’ll be travelling to the Brisbane show. I’ll be there for the whole day but will be doing a brief presentation about BricsCAD’s LISP, with reference to AutoCAD compatibility and the tools available to CAD Managers and developers, including BLADE.

I have experience not only in developing using LISP in AutoCAD and BricsCAD, but also in transitioning from one to the other in a comprehensively modified custom environment. I hope to be of some assistance to CAD Managers and users who are considering such a move. I believe there are still seats available.

Disclosure: the organisers will be covering part of my expenses.

Autodesk removes ability to control products and updates by device

1 Reply

If you’re a CAD Manager controlling Autodesk software through Autodesk Account, make sure you don’t ignore this little notice near the top:

Full details can be found on the page Device Management Discontinued in Autodesk Account, but in short another level of control and flexibility will be removed from you in a month or so.

I hope you’re sincerely grateful for Autodesk improving and simplifying the user management experience.

This only applies if you allow Autodesk desktop app to be installed, which I’ve always advised against. Of course, if you’re in a secure proxy environment there’s a good chance that Autodesk desktop app doesn’t work anyway, so the point is moot.

Rock on, Robert Green!

1 Reply

I’d like to offer my congratulations to Robert Green on his landmark of 400 issues of the CAD Manager’s Newsletter. There’s a interview with Robert here.

As a fellow CAD Manager and Cadalyst contributor, I’ve admired Robert’s work for many years. I finally got to meet Robert last year at the Bricsys Conference 2017 in Paris, and it was a pleasure.

Legends on stage – Robert being interviewed by Don Strimbu at Bricsys 2017
Robert, R.K. McSwain and Steve enjoy lunch at the Carrousel du Louvre
No pictures! R.K. McSwain, Nancy Johnson and Robert
Robert rocks out

Some of you will already be aware that Robert is a seriously good guitarist, and he did not disappoint at the after-conference party. I look forward to seeing Robert again, and to reading many more of his insightful articles.

CAD Panacea tip – startup files in BricsCAD

3 Replies

One of the things that might initially baffle a CAD Manager or power user when investigating switching from AutoCAD to BricsCAD is how to set up the startup routines. Head over to CAD Panacea for R.K. McSwain’s concise, handy description of how to do it.

Due to BricsCAD’s high level of compatibility, you can maintain a common folder or set of folders containing LISP and other custom files for both applications. That way, you don’t need to do double maintenance during the transition period. I’ve done this successfully in a highly complex custom environment. Some code and other adjustments were required in places, but all but a handful of my hundreds of AutoCAD LISP files worked as-is in BricsCAD with zero effort.

Having added your AutoCAD custom folder(s) to BricsCAD’s search path, I suggest you make a common startup LISP file (e.g. rename your old acaddoc.lsp to something like CADStartupDoc.lsp) and have tiny stub startup LISP files for each application (acaddoc.lsp and on_doc_load.lsp) that each loads the common startup file.

acaddoc.lsp contents:
(load "CADStartupDoc")

on_doc_load.lsp contents:
(load "CADStartupDoc")

You can add error checking and messaging if you like, but if you have control of your environment you probably won’t even need that. If you find you do need any application-specific code, you can just add it or load it from the acaddoc.lsp or on_doc_load.lsp stubs as appropriate.

How to sign your LISP files

Leave a reply

This post follows on from Why digitally sign your LISP files? and How to obtain a digital signature to sign your LISP files.

In the first post, I explained why you might want to digitally sign your LISP files. In the second, I explained how to obtain and install a digital signature. This third and final post in the series assumes you have done all that and now want to sign your files. There are two methods available to you, using a dialog box or command-line interface.

Signing LISP using the AcSignApply.exe dialog box

Autodesk has provided a utility called Attach Digital Signatures for years. This was provided to sign drawings, zip files, etc., but the ability to sign LISP files was added in AutoCAD 2016. Don’t go using the 2015 version or you’ll have a very frustrating time! You can invoke this utility using the Windows Start Menu:

You can also make your own desktop shortcut if you like. The executable is stored at (XXXX is your AutoCAD release number):

C:\Program Files\Autodesk\AutoCAD XXXX\AcSignApply.exe

AutoCAD doesn’t need to be running when you start the application. Here’s the interface:

Half way down, there is a list of code signing certificates that you can use. You should see the one you obtained and installed earlier in this list. If you don’t see it listed it may not have been installed correctly. It’s possible to install a public key version of a certificate and see it listed in the Windows Certificate Manager, but that won’t help you sign code. You need to install the private key version in order to be able to sign things. If you do the wrong kind of export from your browser, or if you use the wrong browser to obtain and export the certificate, you may have installed the public key version. In such a case, you will need to contact the certificate provider for help. I have found that the online chat help provided by Comodo is excellent in such cases. Yes, I know this because I got it wrong the first time!

Assuming your certificate is visible, click on that line to select it. You can add files to the pane at the top left using the buttons on the right side or by simply dragging and dropping files onto the pane from Explorer. But wait! Before you do that, make sure you have a safe unsigned copy of all your files. Applying the signatures is a modification process; you are left with only the signed version of the files.

LISP files with the LSP, MNL, FAS, or VLX file extensions can be selected and dragged into the pane. As mentioned in the first post, there’s a bug in the original iterations of AutoCAD 2016 and AutoCAD 2018 that prevents signed VLX files from working, so I would advise against creating them. If you need to distribute signed DCL-based code and don’t want the LISP source visible, you will need to provide a signed FAS instead, along with a DCL file that’s either provided alongside the FAS or created on the fly by your code. Yes, this is a pain.

Note that at the time of writing, you can’t sign CUI, CUIx, DVB, JS, PGP and SCR files.

Once you have selected the certificate to use and the files to sign, select a source for the time stamp and enter a description in the Comment box (optional). Pick the Sign Files button and you’re done.

Signing LISP using the AcSignTool.exe command-line utility

This utility isn’t provided with AutoCAD, but you can download it here. It doesn’t require AutoCAD, which means you can sign LISP files even if you don’t have a copy of AutoCAD 2016 or later.

Once you have downloaded and unzipped the file, place the files somewhere handy. If you make a shortcut to cmd.exe that starts in that location, you can run this command to see all the options:

acsigntool.exe /?

Usage is usually as follows:

AcSignTool -sign /file:[inputfile] /cert:[certificate] /time:[timestamp] /comment:[description]

Here’s an example:

AcSignTool -sign /file:"X:\ToSign\MyCode.lsp" /cert:abcdef1234567890 /time:1 /comment:Hello

The resultant file should be the same as with the dialog box interface. If it’s a raw LISP file, a large comment like this will be placed at the bottom of the file:

;;;-----BEGIN-SIGNATURE-----
;;; /gcAADCCB/oGCSqGSIb3DQEHAqCCB+swggfnAgEBMQ8wDQYJKoZIhvcNAQELBQAw
;;; IE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBD
;;; CwYJKoZIhvcNAQcBoIIFQzCCBT8wggQnoAMCAQICEQCyNMZT2aa05avqeC3j+F3p
;;; YQBuAGQAYQByAGQAcwAgAGEAbgBkACAAVABlAGMAaABuAG8AbABvAGcAeQAgACgA
;;; MA0GCSqGSIb3DQEBCwUAMH0xCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVy
;;; QSBMaW1pdGVkMSMwIQYDVQQDExpDT01PRE8gUlNBIENvZGUgU2lnbmluZyBDQTAe
;;; bnB31gkc9o/M8YjPdGVjQG0VS96RVf/WtkmGugV2n1Fv4wWXBLA7n410yglqSZh9
;;; NOK2Ya1KFx4trccIHV1oAFN+BCKzSf6J/HdVkmCcy4TEPcrxSzZsi//slm2o9EHl
;;; mwdm6Quhw1wMT8+iRmJNO4ofwuKfBwyE28ZIK4q+zorJPNwiK2o43CmNJViU5SQD
;;; M9ImVtHTTtdAR1Iln+wEtg/4xgwj5KWuxoUJ22OJ/K0A8IcnxqGBujCBtwYDVR0O
;;; Fw0xNzEwMDQwMDAwMDBaFw0yMTEwMDQyMzU5NTlaMIGAMQswCQYDVQQGEwJBVTEN
;;; MAsGA1UEEQwENjE1NTELMAkGA1UECAwCV0ExEjAQBgNVBAcMCVdpbGxldHRvbjEV
;;; A1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwuY29tb2RvY2EuY29tL0NPTU9ET1JT
;;; QUNvZGVTaWduaW5nQ0EuY3JsMHQGCCsGAQUFBwEBBGgwZjA+BggrBgEFBQcwAoYy
;;; aHR0cDovL2NydC5jb21vZG9jYS5jb20vQ09NT0RPUlNBQ29kZVNpZ25pbmdDQS5j
;;; MYGvBIGsOAAyADsAMgAvADEAMAAvADIAMAAxADgALwA4AC8AMgA2AC8AMQA3AC8A
;;; TgBhAHQAaQBvAG4AYQBsACAASQBuAHMAdABpAHQAdQB0AGUAIABvAGYAIABTAHQA
;;; dABpAG0AZQAtAGEALgBuAGkAcwB0AC4AZwBvAHYAKQAAAA==
;;; -----END-SIGNATURE-----

Because it’s a comment, it will be ignored by AutoCAD releases prior to 2016, and by other AutoLISP-compatible CAD applications such as BricsCAD and ZWCAD.

References:
Signing your application modules for AutoCAD 2016 – Part 1 – Kean Walmsley
Signing your application modules for AutoCAD 2016 – Part 2 – including various other references
To Digitally Sign an AutoLISP File – Autodesk Knowledgebase article

How to obtain a digital signature to sign your LISP files

2 Replies

In an earlier post, I explained why you might want to digitally sign your LISP files. If you decide to go ahead with that, then this post explains how you can obtain and install the digital signature you will need to sign your files. This is the most difficult part of the process and it involves spending money.

Getting a digital signature

Although you can make your own digital signature (there’s an Autodesk Knowledgebase article describing the process), there’s little point in doing this. You can sign your files, sure, but that signature won’t be seen as trusted by software that checks for it. Anybody can create a signature like that, including one that impersonates you, and it doesn’t prove anything. The only purpose for such a home-made signature would be to test the methods you’ll be using to apply a proper trusted signature later.

Edit: if you do want to make your own signature, BlackBox informs me that the MakeCert tool in the Windows SDK mentioned in the Knowledgebase article is deprecated. He suggests using this PowerShell Cmdlet instead.

You’re going to need a signature that is trusted. That means you’re going to have to pay somebody trustworthy to trust you. There are a set of certifying authorities, trusted by Microsoft, Autodesk, etc. who can issue code signing certificates to companies and people. You need to prove who you are to one of those authorities and pay them to certify that you are who you say you are. So before you start, make sure you or your business are visible in terms of directory listings, publicly visible phone numbers, etc. If you are representing a company asking for a certificate, you can expect to be asked to produce evidence that you really represent that company. You can expect to confirm that your email and phone number are really under your control.

You only need to do this once a year, or even once every several years if you pay in advance. You might find that the evidence you need to provide changes at renewal time; for example a Yellow Pages listing that was OK in 2015 was no longer accepted when I renewed in 2017, so I had to register my business with another listing.

In my search for a certifying authority, I found that K Software, a reseller for Comodo, was the cheapest source for a code signing certificate, see here. An OV certificate will be fine for signing LISP.

K Software takes your money (USD $67 to $84 a year depending on the length of time you need), gets Comodo to provide the certificate, and provides a handy tool (KSign) that allows you to simply apply the certificate to various files without some of the messing about that’s otherwise required. It’s not useful for LISP files, though. Comodo also provides the support, and I’m happy to report that in my experience their customer service is excellent.

Note: it’s important that you pay close attention to the instructions when applying for your certificate. For example, the browser you use to apply for the certificate is vital. Choose one that’s suggested (e.g. Firefox) and which you expect to use later to obtain the certificate.

Installing a digital signature

Once your evidence is accepted and your payment has gone through, you will be sent an email with a special code, allowing you to obtain the certificate. It’s important that you’re using the same browser on the same computer that you used when applying for the certificate.

Once you click the link and obtain the certificate, you’ll want to export it. In Firefox 58.0, use Options > Privacy & Security and scroll to the bottom to see View Certificates. Select the certificate and pick Export. This will create a .P12 file that you can back up and install on this or another computer. To install the certificate, double-click the .P12 file and follow the prompts to assign it to the current user in the default location (Personal).

That’s it. You should now have a certificate installed that you will be able to use to sign LISP and other files. To check this, start the Windows Certificate Manager (C:\Windows\System32\certmgr.msc). Have a look in Current User > Personal > Certificates and you should find your newly installed certificate.

The next post in this series will explain how to apply this digital signature to your LISP files. That’s the easy bit.

Why digitally sign your LISP files?

4 Replies

After I mentioned in an earlier post that I had digitally signed the sample LISP file I had provided, this generated some interest. In this post, I’ll explain why you might want to sign your LISP files. In a later post, I’ll explain how to do it.

These days it is standard practice for developers to digitally sign their code. Operating systems and applications are displaying increasingly scary warnings when coming across unsigned code. Here is an example of the sort of message you get when you load an unsigned LISP file into AutoCAD from a location that has not been explicitly configured as a trusted location:

If you’re a CAD Manager dealing with your own internal code, it’s not too onerous to configure AutoCAD in Options > Files such that a folder is trusted by AutoCAD and place your code in there. The folder should be read-only; if it isn’t, AutoCAD warns you when you try to configure it. If you do this, the scary warnings don’t appear to bother and confuse your users, even if your code is unsigned.

Another way a CAD Manager can avoid the warnings is to set the SECURELOAD system variable to 0. That’s generally not recommended because it turns off AutoCAD’s security features. While you’ll probably get away with this, there’s always a chance that a user will load some malware and then you’ll have to explain yourself to management.

If you’re not just using your code internally and it’s going to be used by other parties, then you’re not going to have that level of control over the user environment. In recent AutoCADs it’s possible to set up the installation deployment such that users can’t turn off the security settings. If the CAD Manager at the location using your code has done this, your potential users are going to be presented with unprofessional-looking scary warnings.

If you sign your code, users might still get a warning, but it’s less scary. It identifies you as the verified source of the code so they will have more confidence in picking the Always Load button. Once they’ve done this, other signed code of yours will be automatically trusted.

There’s another important reason you might want to sign your code, and that’s protection against other people’s modification of your code. If somebody edits your LSP file and then gives it to someone who tries to load it, the user is presented with an even scarier warning:

Note that this warning no longer has your name on it. This means it’s possible to protect yourself from people (internal or external) who well-meaningly hack about with your code and then try to blame you when it goes wrong. It also gives a level of protection against your code being infected by malware.

Note that all of the above only applies to AutoCAD 2016 and later. AutoCAD 2014 introduced some LISP loading security measures, but the signature stuff came a couple of releases later. Earlier AutoCAD releases, along with compatibles such as BricsCAD and ZWCAD, will just ignore the digital signature. It’s just a comment in the code as far as they’re concerned.

LISP files with the LSP, MNL, FAS, or VLX file extensions can be digitally signed. There’s a bug in the original iterations of AutoCAD 2016 and AutoCAD 2018 that prevents signed VLX files from working. This was patched later in both releases (2016 SP1 and 2018.0.2), but if you’re distributing your code externally there’s always a chance that your VLX might end up in the hands of somebody using a broken release. Also, VLX files that are digitally signed cannot be loaded into AutoCAD 2015 and earlier, broken or not. You should bear that in mind before distributing signed VLX files. I don’t do it and would advise against it. Thanks, Autodesk.

Given this information, if you decide that signing your LISP is a good idea, watch this space for information on how to do it.

Simplifying CAD Management the Autodesk way

7 Replies

According to Autodesk, one of the benefits of subscription (rental) is simplified administration. To prove it, Autodesk has provided a simple guide for CAD Managers called The Software Administrator’s Guide to Autodesk Subscriptions – How to Set Up, Install, and Manage Your Software and Users.

It’s 18.7 MB and 78 pages long.

Don’t worry though, this simple guide helpfully includes a simple guide on how to read it.

Among other things, this eBook provides handy hints on how subscription’s simplified administration regime for standalone licenses requires you to pre-emptively name all your users, set them all up with Autodesk accounts and define what software each is allowed to use. There’s a note to say that your Internet connection needs to be working at the time of installation (obviously) and also every 30 days (less obvious) or you won’t be able to use the software.

The guide describes how you can simply go online to Autodesk Accounts (assuming it’s up), and switch those permissions around when Bert is away on site and Ernie needs to hop on his PC at 6 PM to make a quick change before a drawing goes out. It mentions how Ernie will be sent an email with a link to follow so they can sign up before using the product. The CAD Manager is encouraged to check with Ernie to make sure it all worked, and check online to ensure Ernie’s sign-in went according to plan.

Make sure you get in early tomorrow morning before Bert’s shift starts so you can switch the user permissions back again. What? You planned to have the day off? Don’t you understand that your job has been redefined by Autodesk? I dub thee “not a team player”.

Don’t complain, because the new procedure is clearly much more simple than the old-fashioned perpetual license method. You know, the one which involved the far more complex procedure of Ernie logging on to Bert’s PC and using the software, then Bert logging on and using it the next day. How did we ever cope before Autodesk’s magnificent management enhancement?

If the huge job efficiency boost provided by this simplified new method doesn’t have CAD Managers throwing their perpetual licenses at Autodesk in a subscription-hungry frenzy, I don’t know what will.

Simplifying CAD Management is alive at Autodesk.

Autodesk updates Design Review

1 Reply

Despite the previously announced end-of-active-life for Design Review (Autodesk’s DWF viewer), there is now a new release available. This wasn’t supposed to happen, because we should all now be using cloud-based solutions.

A new version of DWG TrueView was needed to deal with the new DWG 2018 format, and one knock-on effect is that a new Design Review was needed to be compatible with DWG TrueView 2018.  It’s still only 32-bit, so it appears to be a matter of Autodesk just touching it up enough to keep it compatible.

Interestingly, the new Design Review is not called 2018. Here’s where to find it:

On the bloatware theme, if there’s a particular reason this download (421 MB) is over eight times the size of its predecessor (49 MB), it’s not readily apparent.  The installed application is 212 MB, so it’s all a bit mysterious.

The downloaded executable is a WinZip self-extractor. If you’re a CAD Manager, there’s no point in having the unzip happen 100 times for 100 users when it could happen just once, so you’ll want to grab the extracted files and install from those. This installer makes that difficult, but not impossible. If you want to do that, read on. If you’re just installing it once, skip the next two paragraphs.

Running SetupDesignReview.exe (note the lack of version information), the extraction started but I couldn’t find out where it was extracting to. I eventually found it in the folder %Temp%\XXX.tmp, where XXX is a random name, e.g. _AID0D9. This folder gets automatically erased on completion or cancel, so what you need to do is run SetupDesignReview.exe once, wait for the unzipping to finish but don’t go ahead with the install, copy the %Temp%\XXX.tmp folder elsewhere, then cancel the initial installation. You can then run as many installations as you like using the extracted files.

It would be useful to have these things documented. The Installation Help, System Requirements and Readme links in the installer all rather unhelpfully point to a generic Knowledge Network search.

The install proper will uninstall Design Review 2013 without asking, which is antisocial. For example, if you wanted to keep using HP Instant Printing (not supported in the new release), this installation would mess you up. In my case it also threw up an error during that uninstall, although it still seemed to go through with it.

Note there’s no sign of a release number. The only versioning I can find is in Help > About, with a build version of 14.0.0.177. When you run it, you’ll notice that it hasn’t had the UI of Doom treatment, so it looks like a cut-down AutoCAD from a few releases ago. Not a bad thing.

How about the product itself? Seems to work OK. If you go to open something, it will show you DWG files as well as DWF(x) files. What happens if you try to open a DWG file? This.

Everybody familiar with versioning knows you never put “the latest version” on anything because it’s meaningless. I was once told about a Head Drafter in the early CAD days who had special stamps made up to stamp paper plots with THIS IS THE LATEST VERSION OF THIS DRAWING. The above message is about that smart.

What happens when you pick the Learn More button? Nothing. So I learned nothing.

Anything else? Well, on my system, it takes about twice as long to start up this simple DWF viewer than it does to start up a full-blown CAD application. Want to take a guess at which application I mean?

Can’t complain too much. This product is free, Autodesk is still providing it and still making efforts to keep it up to date. Props for that much, at least.

Cloud concerns – tie-in

4 Replies

One of the major attractions of the Cloud for vendors is that it ties in customers, providing a reasonably consistent revenue stream. It is an effective anti-competitive strategy. There are various technical and other methods that can be used to ensure that it’s difficult or even impossible for customers to jump ship. While that’s all very nice for vendors, it’s not such a wonderful thing for customers.

Let’s say you’re a CAD Manager who persuades your company to use a great new SaaS service and Cloud storage. Let’s assume it performs well, is secure, has 100% uptime and offers functionality that is not available with standalone software. Your company is pleased with all this and uses it increasingly over several years, eventually moving completely into the Cloud. A good news story, right?

Well, maybe. There are a few things that could go wrong. Very wrong. Wrong enough to get you fired. Most of these things have multiple precedents, some of them quite recent. They are realistic concerns and it’s not really plausible for anyone with any knowledge of the past to argue that they won’t happen in the future. I have grouped these concerns into five categories:

  1. Impermanence. The vendor stops providing the service. There are many possible reasons for this happening. Computing is full of product failures and withdrawals. Autodesk alone has such a long history of dead products and orphaned customers, that it would be a major undertaking just to document them all. If the product’s not making money, it’s unlikely to have a future. The vendor itself could go down the tubes. Computing history is littered with the corpses of once-dominant companies. Because there is a chain of dependencies in a typical Cloud solution, there are several potential points of corporate failure. Maybe Autodesk doesn’t go down, but Amazon does, or Citrix. One day, your software just isn’t there any more. What now?
  2. Price ramping. Once you and enough of your fellow customers are tied in, there is nothing to prevent the vendor from racking up the prices. Autodesk has already done this kind of thing with upgrade pricing and Subscription, so it’s not as if it’s an unlikely scenario. If the boil-a-frog-slowly approach is used and you’re the frog being boiled, you’re better off not being tied down when you decide it’s time to get out of the water.
  3. Unwelcome terms and conditions. The terms and conditions under which you operate are often in the Cloud themselves and can be changed by the vendor without you having any say in the matter. What if one day your company lawyer spots a clause has been added that is totally outrageous (even more than normal, I mean) and there is no way your company can possibly continue to operate under those conditions? Good luck trying to negotiate your way out of that one from a position of weakness.
  4. Unwelcome technical changes. I intend to cover the issue of as-you-go upgrades more fully later, but let’s say the vendor introduces a new feature that seriously impacts your ability to use the software productively. No off switch is provided. Sound familiar? It happens to standalone software. It will happen to your SaaS choice, too.
  5. Ignoreware. Your once-fashionable product stops being The New Black. The vendor decides to concentrate its resources in other areas to attract new customers rather than the ones it has already tied up. While your SaaS product continues to be provided, it is put into maintenance mode and nothing useful is added to it. As the rest of the computing world moves on, your SaaS product does not. Holes start to appear that make your life difficult or impossible. Again, Autodesk history is replete with examples of this kind of thing.

If you’re using standalone software and any of the above occurs, it’s probably a pretty big deal, but you can work around it in the short term by simply continuing to use the product that works. You can keep doing this into the medium term, perhaps for several years. Sure, if Autodesk goes down you’ll find that you can no longer authorise new installations or transfer software from one computer to another. But you’ll have some breathing space. You’ll still have all your data, bang up to date. You’ll be able to continue working productively while you look around for an alternative.

If you’ve deeply committed your company to a Cloud solution and the SaaS hits the fan, it’s more than a big deal. It’s a disaster. It could kill your company. It could kill your career. As a computer once asked me, “Do you really want to do this?”

AutoCAD 2009 Update 3

6 Replies

Update (nee Service Pack) 3 for AutoCAD 2009 is now available. See Between the Lines for full details. As always, read the readme first. Here are the links:

Readme
AutoCAD 2009
AutoCAD LT 2009
AutoCAD 2009 for Revit Architecture
AutoCAD 2009 for Revit Structure

No word yet about related updates for the vertical products.

While I’m not convinced by some aspects of the recently introduced multiple-update-per-release regime, I do approve of Autodesk continuing to maintain 2009 after 2010 has been released. People have complained about this not being done in the past, and on this score at least, I have to say that Autodesk has listened.

What do you think about these updates? Do you use them? What about CAD Managers using deployments; do you deploy the updates? Is it too disruptive? Does it cause problems with the deployment no longer matching the installation, for example when attempting a repair install? Any other issues?