<?xml version="1.0" encoding="UTF-8"?>
<!--Generated by Squarespace Site Server v5.9.2 (http://www.squarespace.com/) on Wed, 17 Mar 2010 21:34:32 GMT--><rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rss="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:cc="http://web.resource.org/cc/"><rss:channel rdf:about="http://www.evanyares.com/the-cad-industry/"><rss:title>The CAD Industry</rss:title><rss:link>http://www.evanyares.com/the-cad-industry/</rss:link><rss:description>Evan Yares on the CAD Industry</rss:description><dc:language>en-US</dc:language><dc:date>2010-03-17T21:34:33Z</dc:date><admin:generatorAgent rdf:resource="http://www.squarespace.com/">Squarespace Site Server v5.9.2 (http://www.squarespace.com/)</admin:generatorAgent><rss:items><rdf:Seq><rdf:li rdf:resource="http://www.evanyares.com/the-cad-industry/2009/10/28/how-to-repair-a-bridge.html"/><rdf:li rdf:resource="http://www.evanyares.com/the-cad-industry/2009/10/27/why-did-you-click-accept.html"/><rdf:li rdf:resource="http://www.evanyares.com/the-cad-industry/2009/10/26/thinking-about-engineering-and-design.html"/><rdf:li rdf:resource="http://www.evanyares.com/the-cad-industry/2009/10/12/medusa4-personal-free-2d-cad-software.html"/><rdf:li rdf:resource="http://www.evanyares.com/the-cad-industry/2009/10/10/cad-and-antitrust.html"/><rdf:li rdf:resource="http://www.evanyares.com/the-cad-industry/2009/10/1/judgment-for-vernor.html"/><rdf:li rdf:resource="http://www.evanyares.com/the-cad-industry/2009/9/29/the-fuzzy-verge.html"/><rdf:li rdf:resource="http://www.evanyares.com/the-cad-industry/2009/9/29/which-cad-program-would-you-recommend.html"/><rdf:li rdf:resource="http://www.evanyares.com/the-cad-industry/2009/9/18/before-there-was-sketchup.html"/><rdf:li rdf:resource="http://www.evanyares.com/the-cad-industry/2009/9/17/pushpulldragdrop-deelip.html"/></rdf:Seq></rss:items></rss:channel><rss:item rdf:about="http://www.evanyares.com/the-cad-industry/2009/10/28/how-to-repair-a-bridge.html"><rss:title>How to Repair a Bridge</rss:title><rss:link>http://www.evanyares.com/the-cad-industry/2009/10/28/how-to-repair-a-bridge.html</rss:link><dc:creator>Evan Yares</dc:creator><dc:date>2009-10-29T01:01:54Z</dc:date><dc:subject>Bridge CAD FEA The CAD Industry</dc:subject><content:encoded><![CDATA[<p><span class="full-image-float-right ssNonEditable"><img src="http://www.evanyares.com/storage/bridgeoops.jpg?__SQUARESPACE_CACHEVERSION=1256785380892" alt="" /></span>If you lived in the San Francisco Bay area, I wouldn't need to tell you that  the Bay Bridge is closed.&nbsp; A&nbsp; tie rod in a repair brace failed dramatically, dropping a several thousand pound steel saddle, with tie rods still attached, onto the bridge deck, hitting several cars (though, fortunately, no one seems to have been seriously injured.)<br /><br /><span style="font-size: 150%;">The Labor Day repair. </span></p>
<p>This is a story is about how the Bay Bridge was repaired last Labor Day weekend.&nbsp; It is based on interviews of several people directly involved in the repair of the bridge.&nbsp; I spoke to these people literally hours after the bridge was reopened.<br /><br />The back story is that the Bay Bridge is due to be replaced with a new bridge.&nbsp; While the construction of the new bridge won't be finished for quite some time, preparations for that construction have already started.&nbsp; <br /><br />One of the first steps in that preparation was the installation of a bypass section at the East end of the existing bridge.&nbsp; The plan was to close the Bay Bridge for four days, over the Labor Day weekend, and literally cut out an existing section, float-in the replacement section, and bolt it into place.&nbsp; This planned closure was to be the longest in recent history for the bridge, and Caltrans (the California Department of Transportation, which is responsible for the bridge) planned a biennial structural inspection of the bridge to coincide with the closure.<br /><br />Though the previous structural inspection revealed no problems, this inspection was different.&nbsp; A large crack was discovered in the end of a eye-bar.&nbsp; The Bay Bridge is largely structural steel, and uses tension links, each made up of four eye-bars, attached to pins at each end.&nbsp; These links are similar to the links you'd find in a bicycle or motorcycle drive chain&mdash;but a lot bigger.&nbsp; The eye-bars are cut out of thick plate steel, with holes at each end for the pins.<br /><br />The failed eye-bar discovered on Labor Day weekend had a crack running from the outside edge, nearly through to the pin.&nbsp; Caltrans said, at the time, that they suspected the crack was caused by corrosion.&nbsp; If you look at pictures of the failed link, it seems pretty clear that the crack started from a stress riser.&nbsp; Whether that stress riser was caused by corrosion, or by a steel worker pounding on the eye-bar with a sledgehammer when it was installed 73 years ago probably isn't important.<br /><br />When Caltrans found the bad eye-bar, there was good news, and not so good news.&nbsp; The good news was that the bridge was already closed, and several of the companies they would have otherwise called to help fix it were already there&mdash;working on installing the bypass section.&nbsp; The not so good news was that none of those companies could afford to endanger their contractual commitments to finish the bypass section on-time, and it was Labor Day weekend&mdash;so it wasn't like Caltrans could call up a steel fabricator, and have anyone actually answer the phone.<br /><br />Caltrans put one of their most senior bridge engineers in charge of getting the bridge opened up by Tuesday morning, at the end of the holiday weekend.&nbsp; Working with him were a team of people from C.C. Myers, Inc. (a construction company known for its ability to handle emergency bridge repairs), Danny's Construction (steel erection specialists), and T.Y. Lin, International (bridge engineers).<br /><br />The first step was to come up with a conceptual design for the repair.&nbsp; Since the repair would only need to last until the replacement bridge is built, it didn't need to be elegant.&nbsp; Caltrans' engineer drew a sketch of what he had in mind:&nbsp; A brace, consisting of two saddles, connected by tie rods.&nbsp; The next step was to figure out who could build the parts for the the brace.&nbsp; And that's an interesting story in its own right.</p>
<p><span style="font-size: 150%;">A history of success.</span></p>
<p>In 2007, a gasoline tanker truck overturned in the MacArthur Maze, a freeway interchange in Oakland.&nbsp; The resulting inferno was so hot that it melted the steel in the roadway deck above the tanker, resulting in its collapse.&nbsp; C.C. Myers was hired to repair the Maze, and managed to get the job done just 26 days after the collapse, beating the deadline by over a month.&nbsp; This feat was significant enough that it was not only memorialized in<a href="http://en.wikipedia.org/wiki/MacArthur_Maze#Rebuilding"> Wikipedia</a>, it was the subject of a <a href="http://www.amazingmaze.com">television special</a>.&nbsp; C.C. Myers gives a lot of credit&nbsp; to Stinger Welding, in Coolidge Arizona, for fabricating and delivering replacement girders for the job in just nine days.<span class="full-image-block ssNonEditable"><span><img src="http://www.evanyares.com/storage/Stinger1.jpg?__SQUARESPACE_CACHEVERSION=1256792453871" alt="" /></span><span class="thumbnail-caption" style="width: 480px;">Girders for the MacArthur Maze. The truck actually had a blowout on the way.</span></span></p>
<p><span style="font-size: 150%;">A call to the wild.</span></p>
<p><span class="full-image-float-right ssNonEditable"><img src="http://www.evanyares.com/storage/ccmyers.jpg?__SQUARESPACE_CACHEVERSION=1256786518572" alt="" /><span class="thumbnail-caption" style="width: 240px;">The legendary C.C.Myers (L), talking with Carl Douglas</span></span>Last Labor Day weekend, when the failed eye-bar was discovered, Carl Douglas, president of Stinger Welding, was in the wilds of Montana on a fishing trip.&nbsp; Where he was, there was no email, and no cell phone service.&nbsp; About 1:00 on Saturday afternoon, he headed into town (where there was cell phone coverage) to get some supplies.&nbsp; And coincidentally, that's the moment that his phone rang.<br /><br />On the other end of the line was a person saying they had an emergency, and needed some parts fabricated right away.&nbsp; Initially, Douglas thought it was a joke. But the words "C.C. Myers" and "Bay Bridge" got his attention.<br /><br />After hearing what was needed, Douglas got on the phone immediately, to track down the employees he needed to do the job.&nbsp; It was not easy.&nbsp; His shop foreman, for example, was on vacation in Utah, and had to turn-around, and head back to Arizona.&nbsp; By mid-afternoon, Douglas had managed to assemble a 15 person crew.&nbsp; He had his people go into the steel yard, and take an inventory to send to the Caltrans team, so they could adapt the design of the saddles to the materials on hand.&nbsp;&nbsp; <br />&nbsp;<br />Douglas then took on the task of trying to find a plane that was big enough to fly ten tons of steel from Coolidge to Oakland.&nbsp; Fortunately, he knew people in the air-cargo industry.&nbsp; Unfortunately, being the holiday weekend, no one was around to answer his phone calls.&nbsp; Just as a passing notion, he thought to call FedEx.&nbsp; They not only answered his call, they offered three different planes which could handle the load, and deliver it on time. (If Stinger Welding ever needs to do something like this in the future, it's good to know that FedEx can even charter an Antonov An-124, with a maximum payload of 330,000 pounds.)&nbsp;&nbsp; With the people and transportation in place, Douglas flew back to Coolidge, arriving at the shop at 11:30 PM, Saturday night. <br />&nbsp;<br />While Douglas and his crew were working in Arizona, the Caltrans team were working in California, taking measurements and refining the design of the saddles.&nbsp; The two teams communicated back and forth until about 3:00 AM, Sunday&mdash;at which point the Stinger Welding crew started cutting and welding.<br />&nbsp;<br />By 9:00 AM Sunday, 18,000 pounds of steel saddles (and Carl Douglas himself) were being loaded onto a FedEx charter plane, which would fly directly to Oakland, where a flatbed truck and a California Highway Patrol escort awaited. <br />&nbsp;<br />While the saddles fabricated by Stinger were critical to the repair, the work could not be completed without the high-tension steel tie rods.&nbsp; For these, C.C. Myers called on AVAR Construction Systems, a major supplier of post-tensioning systems for bridges and stadiums.&nbsp; The rods were much  easier to fabricate than the saddles, as they only had to be cut to length.&nbsp; Since AVAR is based in Fremont, transportation was not an issue. <br />&nbsp;<br />With the saddles and tie rods delivered, the steel erection crew got to work.&nbsp; Hoisting the first saddle up, they found that it fit perfectly.&nbsp; Except no one had anticipated that the tie rods, if installed directly on the saddles, would interfere with the eye-bars.&nbsp; What was needed were spreaders, to move the tie rods so they wouldn't interfere.&nbsp; <br /><br />Ultimately, American Bridge Fluor, Inc., which had been working on the bridge bypass, was able to fabricate the spreaders in their Oakland yard, and deliver them to the bridge Monday night.&nbsp; They were quickly installed, and the tie rods were carefully brought up to tension. <br />&nbsp;<br />With no time to spare, Caltrans got all the construction debris cleaned up, and started contacting toll booth operators, to get them to come to work.&nbsp; After a hastily called 6:00 AM press conference, the bridge was reopened at 6:38 AM, Tuesday morning&mdash;just 1-1/2 hours after the originally planned opening.</p>
<p><span style="font-size: 150%;">The failure of the repair</span>.<br /><br />It's only been 7 weeks since the Bay Bridge was repaired.&nbsp; The question arises, why did the repair brace fail?<br /><br />Caltrans' initial statement is that the failure was likely due to a fatigue crack in a tie rod, exacerbated by high winds. But the brace, properly designed and installed, should have been able to handle hurricane force winds without a problem.&nbsp; There shouldn't have been a fatigue crack in a nearly new tie rod.<br /><br />So, I'm going to speculate, and tell you why I think it failed. (Since I'm not  a P.E., you should take this with a grain of salt.)<br /><br />The basic design of the brace was very robust.&nbsp; The saddles and spreaders were far stronger than they needed to be.&nbsp; The only critically stressed components were the tie rods.&nbsp; <br /><br />If the brace had been installed across one tension link, the calculation for sizing the tie rods would have been pretty simple.&nbsp; But the brace wasn't installed across one tension link.&nbsp; It was was bolted to the top and bottom pins of two separate links, which are joined at a central fixed pin that's part of large fixed girder. Take a look at the picture, and try and wrap your head around the force vectors in this configuration. The brace itself absorbs the load that was previously born by the three girders that converge at the point labled "joint" in the photo below. Rather than reinforcing the weak link, the brace, as installed, has created complex multi-bar linkage.&nbsp; If you consider statics, dynamics, and kinematics, this makes for an "interesting" system. <br /><br /><span class="full-image-block ssNonEditable"><img src="http://www.evanyares.com/storage/bridgerepairfailure.png?__SQUARESPACE_CACHEVERSION=1256784468679" alt="" /></span>When I saw a picture of the actual installed configuration of the brace, my first thought was that it&nbsp; probably made the design calculations a lot more complicated.&nbsp; (Acutally, my very first thought was "Kansas City." If you happen to be a structural engineer, and would like to explain to the readers what that means, please post a comment.)</p>
<p>Since this blog is about engineering software, you probably know I'm going to tell you how straightforward it would have been  to design and analyze the brace, using Tekla Structures, Ansys/CivilFEM, STAAD.Pro, or SAP2000 (among others.)&nbsp;</p>
<p>So, here's the question:&nbsp; Was any computer-based analysis run to optimize the design of the brace?</p>
<p><span class="full-image-float-right ssNonEditable"><img src="http://www.evanyares.com/storage/saddle.jpg?__SQUARESPACE_CACHEVERSION=1256784365703" alt="" /></span>What I've found out so far is that the steel erection people made measurements for the brace by cutting&nbsp; foamcore patterns to fit.&nbsp; (This isn't a bad way to do it, but it's not  as accurate as using a laser scanner.)&nbsp; Design information and dimensions for the saddles were sent back and forth from California to Arizona via fax.&nbsp; And, finally, the images provided by Caltrans that show the saddles are not 3D models, but are rather photoshopped pictures that don't even accurately represent the design.&nbsp;</p>
<p>All of these things, taken together, lend credence to the possibility that the brace was designed without the benefit of engineering software.</p>
<p>Though it's too early to know for certain, today's newspaper articles hint that  the modified/repaired brace now being installed on the bridge hasn't been analyzed with engineering software either.</p>
<p><span style="font-size: 150%;">Is there a moral to the story?</span></p>
<p>It's easy to be a Monday morning quarterback.&nbsp; Overall, I think everyone involved in the Labor Day weekend repair deserves tremendous credit for working their asses off to get the bridge opened on time.&nbsp;</p>
<p>Yet, I think the original decision to design the brace using the &ldquo;back of an envelope&rdquo; method was short-sighted.</p>
<p>It's pretty likely that either Caltrans or T.Y. Lin has a structural model of the Bay Bridge already.&nbsp; I'm making an assumption here, but given the retrofits done to the bridge since the Loma Prieta earthquake in '89, I think it's a reasonable one.&nbsp; So, why not use that model?</p>
<p><span class="full-image-float-right ssNonEditable"><img src="http://www.evanyares.com/storage/uglybrace.jpg?__SQUARESPACE_CACHEVERSION=1256787195372" alt="" /><span class="thumbnail-caption" style="width: 312px;">Not pretty, is it?</span></span>It's probably old-school thinking.&nbsp; Not that many years ago, the software tools for doing this kind of work were a bit, ahem, user-hostile.&nbsp; Faced with the need to design, fabricate, and install a brace within an impossibly short deadline, and having had some experience with the vagaries of engineering software, a reasonable manager might say &ldquo;to hell with using computers.&rdquo;</p>
<p>Looking at the progression of events over the Labor Day weekend (for example, discovering the need for the spreaders late in the process), and the failure of the brace yesterday (which will have a major economic impact on the bay area, despite the likelihood that the Federal Highway Administration will pay for the actual repair), the notion of using CAD and CAE, even given the tight deadlines, seems, in retrospect, a lot more interesting.</p>
<p><span style="font-size: 150%;">What can engineering software vendors do better?</span></p>
<p>I'd like to see companies in the engineering software industry put some skin in the game.&nbsp; All too often, it is their customers who are left holding the bag when software problems result in missed deadlines and failed projects.&nbsp; While I recognize that engineering software companies can't jump every time a customer has a short deadline and doesn't know how to read the manual, I do think it's reasonable for the major players to have emergency response plans&mdash;If only to give their customers the confidence that, when failure is not an option, someone's got their back.</p>
<p>I can't help but wonder if this story would have turned out differently if the engineers responsible for the job had more confidence in their engineering software&mdash;and in their engineering software vendors?</p>
<!-- 		@page { margin: 0.79in } 		P { margin-bottom: 0.08in } 		H2 { margin-bottom: 0.08in } 		H2.western { font-family: "Nimbus Sans L", sans-serif; font-size: 14pt; font-style: italic } 		H2.cjk { font-size: 14pt; font-style: italic } 		H2.ctl { font-size: 14pt; font-style: italic } 		A:link { so-language: zxx } -->]]></content:encoded></rss:item><rss:item rdf:about="http://www.evanyares.com/the-cad-industry/2009/10/27/why-did-you-click-accept.html"><rss:title>Why did you click "accept"?</rss:title><rss:link>http://www.evanyares.com/the-cad-industry/2009/10/27/why-did-you-click-accept.html</rss:link><dc:creator>Evan Yares</dc:creator><dc:date>2009-10-27T13:01:26Z</dc:date><dc:subject>CAD EULA Licensing The CAD Industry</dc:subject><content:encoded><![CDATA[<p>There is a demo version of a CAD program that I'd like to take a look at.&nbsp; It fits into a category that I'm very enthusiastic about:&nbsp; Tools that empower non-CAD-gurus.&nbsp; I wanted to talk about it here, in my blog.<br /><br />Yet, I can't install it.</p>
<p>It's not because my computer is incompatible. It's because, after having read the license agreement, I can't, in good conscience, click "accept".</p>
<p>It sucks, because this program looks really interesting.</p>
<p>At first, It occurred to me to "out" the vendor, and tell everyone why the license agreement is so egregious. But, after some thought, I figured I'd rather ask you some questions, about how you respond to license agreements.</p>
<p>So, let's assume that you recently installed a demo version of a CAD program:</p>
<ul>
<li>Did you read the license agreement?</li>
<li>If you didn't, why not? (seriously.) 
<ul>
<li>Were you just being lazy?</li>
<li>Did you even scan it a little bit?</li>
<li>Did you think it's not an enforceable contract?</li>
<li>Did you think it's full of meaningless boilerplate?</li>
<li>Did you think the vendor would never actually enforce its terms?</li>
</ul>
</li>
<li>If you did read it, 
<ul>
<li>Did you understand it?</li>
<li>Did you grasp its implications?</li>
<li>If you showed it to your lawyer, what would he say?</li>
</ul>
</li>
<li>Why did you click "accept?"</li>
</ul>]]></content:encoded></rss:item><rss:item rdf:about="http://www.evanyares.com/the-cad-industry/2009/10/26/thinking-about-engineering-and-design.html"><rss:title>Thinking about engineering and design</rss:title><rss:link>http://www.evanyares.com/the-cad-industry/2009/10/26/thinking-about-engineering-and-design.html</rss:link><dc:creator>Evan Yares</dc:creator><dc:date>2009-10-26T21:12:11Z</dc:date><dc:subject>Engineering Software Interoperability Russia The CAD Industry</dc:subject><content:encoded><![CDATA[<!-- 		@page { margin: 0.79in } 		P { margin-bottom: 0.08in } 		A:link { so-language: zxx } -->
<p>For the last seven weeks, Ralph Grabowski has been writing in<a href="http://www.upfrontezine.com/2009/upf-620.htm"> upFront.eZine</a> about CAD companies he met up with in his recent tour through Russia.<br /><br /><span class="full-image-float-right ssNonEditable"><span><img src="http://www.evanyares.com/storage/truboprovod_clip_image002.jpg?__SQUARESPACE_CACHEVERSION=1256593179085" alt="" /></span></span>This week, he writes about <a href="http://www.truboprovod.ru/en/about/truboprovod.shtml">NTP Truboprovod</a>.&nbsp; As he explains, in Russian, Truboprovod means "piping systems."&nbsp; If you're interested in tools for piping systems engineering,<a href="http://www.upfrontezine.com/2009/upf-620.htm#a"> you should read his article</a>.&nbsp;&nbsp; Actually, if you're interested in how engineering software will affect the business of engineering, you should read the entire series of articles.<br /><br />Here are some thoughts I had when reading this week's installment:<br /><br />The disciplines of engineering and design have often been thought of as being inextricably linked.&nbsp; In practice, what we call &ldquo;engineering software&rdquo; is often better described as &ldquo;design software.&rdquo; &nbsp;<br /><br />Yet, what happens when this software matures to the point where engineering and design functions, while still intertwined, are logically separable?&nbsp; It introduces interesting possibilities, and opens up even more interesting questions.&nbsp; Such as: For a large US or European engineering firm, is engineering or design the more core (sustainable and profitable) competency?<br /><br />Rephrasing a bit, in the context of Ralph's article:&nbsp; If it's possible to do engineering in house, yet outsource detail design to Russian engineers using Russian design software for &frac14; the cost, why not consider it?<br /><br />Let me give you a related example:&nbsp; I recently talked to the owner of a steel fabrication company that builds parts for bridges. (I'll tell you more about him in a later post.&nbsp; He's an interesting fellow.)&nbsp; In his company, there are three important competencies: project management, steel detailing, and fabrication.&nbsp;&nbsp; He employs about 200 people, including project managers and welders, at his main facility.&nbsp; Yet, he has steel detailing work done at a subsidiary in India.<br /><br />If you think about this kind of outsourcing, it makes a lot of sense.&nbsp; The company is an AISC certified major bridge fabricator, with fracture-critical endorsement.&nbsp; For reasons of accountability, it simply can't outsource its welding, and off-shoring it, even to a wholly owned subsidiary, would create insurmountable traceability and scheduling problems.&nbsp; Yet, by using best-in-class software (Tekla Structures, in this case), it can do steel detailing anywhere in the world.&nbsp; India, with its large pool of mechanical engineering graduates and English as a primary language, is a natural choice. &nbsp;<br /><br />It's not my intention to get into a detailed discussion of software functionality here.&nbsp; Whether we're talking about structural design software from Tekla, or piping systems software from Autodesk, Rebis, Intergraph, Bentley, Coade, or NTP Truboprovod is not important. &nbsp;<br /><br />What is important is whether the software tools used by engineering firms support the distinction between engineering and design--both logically, and through open interoperability.</p>
<p>By the way, if you think this issue has any merit, I'd be interested in hearing your thoughts.</p>]]></content:encoded></rss:item><rss:item rdf:about="http://www.evanyares.com/the-cad-industry/2009/10/12/medusa4-personal-free-2d-cad-software.html"><rss:title>Medusa4 Personal: free 2D CAD software</rss:title><rss:link>http://www.evanyares.com/the-cad-industry/2009/10/12/medusa4-personal-free-2d-cad-software.html</rss:link><dc:creator>Evan Yares</dc:creator><dc:date>2009-10-12T22:23:59Z</dc:date><dc:subject>Medusa CAD Schroer The CAD Industry</dc:subject><content:encoded><![CDATA[<p>I read <a href="http://worldcadaccess.typepad.com/blog/2009/10/installing-medusa4-on-linux.html">Ralph Grabowski's blog</a> regularly.&nbsp; A few days ago, he mentioned <a href="http://www.cad-schroer.com/index.php?&amp;ziel=Products-MEDUSA-M4Personal&amp;land=com&amp;scr=1.6">Medusa4 Personal, from CAD Schroer</a>. Actually, he mentioned that it is free for personal use, runs on Linux (and WIndows), and that he had an installation problem with it.</p>
<p>I double checked, and indeed, CAD Schroer's installation guide for Medusa 4 Personal doesn't mention that you might have to use the "sudo" command when installing the program.&nbsp; You have to type "sudo sh medusa4_v3_1_1_linux_personal.sh" at the command line to install it.&nbsp; No big deal.</p>
<p>I was able to install Medusa4 Personal on Ubuntu 9.04 Jaunty, with no difficulty.&nbsp; The program runs just fine.</p>
<p>Here's a little history of Medusa, from <a href="http://www.toddspraker.com/Medusa-info.htm">Todd Spraker</a>:</p>
<ul>
<li> 1980 - Medusa was developed by CIS (Cambridge Interactive Systems) in the UK getting the name CIS Medusa. It ran mostly on Unix based computers namely the DEC (Digital Equipment Company) VAX minicomputers. </li>
<li>1981 - Prime Computer Co. acquired exclusive rights to market Medusa outside of Europe. Medusa was developed to run on Prime computers and became the start of Prime Medusa which eventually got up to revision 5 </li>
<li>1983 - Computervision buys CIS Medusa and continued to develop the software, eventually taking CIS Medusa up to revision 7. </li>
<li>1984 - Prime gets joint ownership of Medusa which allows them to market Prime Medusa worldwide </li>
<li>1988 - Prime buys Computervision taking full control of Medusa. Prime develops Medusa-12 by combining CIS Medusa-7 with Prime Medusa-5 to run on the UNIX based workstations which were taking a growing position in the computer market. Medusa-13 was eventually developed with a very different user interface from rev-12.  MEDEA electrical was also developed to offer an additional wiring capability</li>
<li>1998 - Parametric Technology Corporation (now just PTC) buys Computervision and Medusa. </li>
<li>2002 - CAD Schroer (a German company) buys Medusa from PTC </li>
</ul>
<p>Medusa has always been a highly regarded 2D mechanical drafting system.&nbsp; In the same league as <a href="http://www.cadam.com">Cadam</a> and <a href="http://www.anvil1000md.com/index.html">Anvil-1000MD</a>.&nbsp; (When AutoCAD was released, and Autodesk talked about it providing 80% of the capabilities for 20% of the price, they were comparing it with products such as these. It took many years for Autodesk to catch up.)</p>
<p>If you decide to check out Medusa4 Personal,  remember that it's not an AutoCAD clone or work-alike. If you're an AutoCAD guru, it might take you a while to get used to Medusa4.&nbsp;</p>
<p>If you're not looking for an AutoCAD clone, but rather are trying to find a  productive and professional mechanical drafting tool that you can learn to use without taking a bunch of classes, you might really like Medusa4 Personal.</p>]]></content:encoded></rss:item><rss:item rdf:about="http://www.evanyares.com/the-cad-industry/2009/10/10/cad-and-antitrust.html"><rss:title>CAD and antitrust?</rss:title><rss:link>http://www.evanyares.com/the-cad-industry/2009/10/10/cad-and-antitrust.html</rss:link><dc:creator>Evan Yares</dc:creator><dc:date>2009-10-10T18:32:10Z</dc:date><dc:subject>CAD Antitrust Interoperability The CAD Industry</dc:subject><content:encoded><![CDATA[<p>Ralph Grabowski asks the question in his blog "Does CAD face antitrust under Obama?"</p>
<p>It's an excellent question.</p>
<p>All major CAD vendors have "market power" in certain relevant markets.&nbsp; Lock-ins from restrictive licensing and poor interoperability sometimes leave CAD consumers with little meaningful choice.</p>
<p>It's well-known among antitrust experts that dominant companies will often push the boundaries of anticompetitive behavior, as the cost of sanctions is less than potential gains in revenue.<br /><br />This is just a fact of life.&nbsp; It doesn't make those companies evil.</p>
<p>The challenge is to figure out what to do.&nbsp; How to promote the kind of competition that results in more and better choices for consumers?&nbsp; It's a question I've pondered for well over a decade.</p>
<p>I think, to the extent that government antitrust scrutiny might cause the major CAD vendors to pause and rethink their strategies, it would be a good thing.&nbsp; Yet, the most effective actions I've seen from the government in the past have come in its role as a consumer of CAD data, where it has been able to command attention with its checkbook.</p>
<p>It may be that the DOD and GSA are as important as the FTC and DOJ when it comes to promoting competition in the CAD industry.</p>]]></content:encoded></rss:item><rss:item rdf:about="http://www.evanyares.com/the-cad-industry/2009/10/1/judgment-for-vernor.html"><rss:title>Judgment for Vernor</rss:title><rss:link>http://www.evanyares.com/the-cad-industry/2009/10/1/judgment-for-vernor.html</rss:link><dc:creator>Evan Yares</dc:creator><dc:date>2009-10-01T22:23:20Z</dc:date><dc:subject>Licensing The CAD Industry Vernor Autodesk AutoCAD License</dc:subject><content:encoded><![CDATA[<p>Two years ago, Tim Vernor tried to sell some copies of AutoCAD on eBay. Autodesk cancelled the auctions, claiming copyright infringement.&nbsp; Vernor then sued Autodesk.</p>
<p>Vernor v. Autodesk became an important suit, because it asked whether the owner of a particular copy of software had the right to resell that copy.&nbsp; Autodesk's position was that AutoCAD is licensed, not sold, and that its license agreement prohibits  resale.&nbsp; Vernor's position was that he never entered into any license agreement with Autodesk (he bought the copies at a garage sale), so he had the right to sell them, under the "first sale" doctrine of US copyright law.</p>
<p>The case was essentially decided in May, 2008, with the Court holding in favor of Vernor.&nbsp; Yet, because of some unresolved issues, no judgment was entered for Vernor.</p>
<p>Autodesk got another bite at the apple on Monday, with a hearing on cross motions for summary judgment. This hearing took 4 months to happen after the last paperwork had been filed, so I was pretty much ready to wait another several months to see what the Court had to say.</p>
<p>Was I ever surprised.&nbsp; The Court's opinion was issued yesterday evening.&nbsp; Judgment was entered for Vernor this morning.&nbsp; You can read both at <a href="http://www.cadcourt.com">www.cadcourt.com</a>.</p>
<p>Taking into consideration the relevant developments over the last year, the Court revisited its May, 2008 holding.&nbsp; In a 26 page opinion, the court carefully laid out the rationale for its decision, paying particular attention to the conflicting case law relevant to the matter.&nbsp; The only good news for Autodesk was that the Court did not take up the issue of "copyright misuse" (which would have opened up a pandora's box of problems.)</p>
<p>The judgment says:</p>
<p style="padding-left: 30px;">The court declares that Plaintiff&rsquo;s sales of Defendant&rsquo;s copyrighted AutoCAD software do not violate the Copyright Act to the extent Plaintiff acquired them in the manner described in the order. Defendant is hereby enjoined from asserting its rights under the Copyright Act as a basis for preventing or otherwise hindering Plaintiff&rsquo;s sales of AutoCAD software.</p>
<p>While Autodesk was the defendant in this case, It wasn't really about AutoCAD.&nbsp; Vernor was represented by <a href="http://www.publiccitizen.org">Public Citizen</a>, a national non-profit public interest organization, whose goal was to clarify the case law regarding software licenses and the first sale doctrine.&nbsp;&nbsp; The result of this case affects Autodesk, but it also affects most other vendors of commercial off-the-shelf software.</p>
<p>I'm hoping that Autodesk will appeal the decision.&nbsp; Not because I think they're right or wrong, but because I believe that resolving the legal uncertainties now inherent in software licensing would benefit both suppliers and consumers of software.</p>
<p>I'd recommend that you read the opinion in this matter, if for no other reason than to give you an appreciation for the complex legal quagmire you wade into the moment you blithly press the "I agree" button when installing not just AutoCAD, but any software application.</p>
<p>&nbsp;</p>]]></content:encoded></rss:item><rss:item rdf:about="http://www.evanyares.com/the-cad-industry/2009/9/29/the-fuzzy-verge.html"><rss:title>The fuzzy verge</rss:title><rss:link>http://www.evanyares.com/the-cad-industry/2009/9/29/the-fuzzy-verge.html</rss:link><dc:creator>Evan Yares</dc:creator><dc:date>2009-09-29T13:31:22Z</dc:date><dc:subject></dc:subject><content:encoded><![CDATA[<p>The <a href="http://www.pdma.org">Product Development and Management Association</a> looks at the innovation process as having three distinct phases: the <span style="text-decoration: line-through;">fuzzy</span> front end,  the new product development process, and commercialization.</p>
<p>&nbsp;</p>
<p><a href="http://www.stevens.edu/cce/NEW/PDFs/FEIEffectiveMethodstoolWorkshop.pdf"><span class="full-image-block ssNonEditable"><span><img src="http://www.evanyares.com/storage/fuzzy front end2.png?__SQUARESPACE_CACHEVERSION=1254236544844" alt="" /></span></span></a></p>
<p>Here are a couple of&nbsp; questions for you to ponder:</p>
<ul>
<li>At which phase of the innovation process are most  engineering software tools targeted?</li>
</ul>
<ul>
<li>Which phase offers the greatest opportunities for improvement of the overall innovation<br />process?</li>
</ul>
<p>If the answers to these questions are important to you, and you are either a supplier or consumer of engineering software, I'd like to have a short private conversation with you.&nbsp; No, not to sell you anything, but rather to get your perspective on a some research work I'm doing.&nbsp; You can reach me at evan@yares.com</p>]]></content:encoded></rss:item><rss:item rdf:about="http://www.evanyares.com/the-cad-industry/2009/9/29/which-cad-program-would-you-recommend.html"><rss:title>Which CAD program would you recommend?</rss:title><rss:link>http://www.evanyares.com/the-cad-industry/2009/9/29/which-cad-program-would-you-recommend.html</rss:link><dc:creator>Evan Yares</dc:creator><dc:date>2009-09-29T11:31:55Z</dc:date><dc:subject>CAD The CAD Industry</dc:subject><content:encoded><![CDATA[<p>I recently received an email, asking me to recommend a CAD program.</p>
<p>I thought it would be interesting to post a copy of the email here, and ask what you think.</p>
<blockquote>
<p>I am looking for a new 3D CAD program that is easy and intuitive to use like a Tool driven direct modeler that can also produce accurately dimensioned 2D drawings to be plotted with title blocks and BOM lists and all for fabrication and construction.&nbsp; I generally work by myself and don&rsquo;t have CAD projects often but occasionally need to work with other engineers and Naval Architects on projects.&nbsp; It seems we all use different CAD programs so the program would need to be able to import and export the various standard file exchange formats.<br /><br />I mostly design small Submersibles and underwater equipment and do some Naval Architectural work.&nbsp; I also like to design furniture and house and shop additions.&nbsp;&nbsp; &nbsp;<br /><br />I made the switch from the drafting board making engineering drawings using AutoCAD V 1 on a Wang with a 12&rdquo; monochrome monitor.&nbsp; I upgraded through all the versions to AutoCAD 2000 which I still use to produce 3D models to get the 2D dimensioned views.&nbsp; Due to the complexity of this method I can&rsquo;t find others that still work like this to consult with.&nbsp; I would like something easier to use.&nbsp; I just purchased [redacted], which I don&rsquo;t like.&nbsp; I am also just getting started with Google Sketchup Pro which is fast and intuitive but I am having problems with accuracy.&nbsp; I also don&rsquo;t know yet how the BOM and 2D layouts will work.&nbsp; Can I plot out professional looking 2D drawings?<br /><br />Talking to all the individual sales reps is not helping me come to a fast decision as to the best way to proceed.&nbsp; I could use some unbiased advice.</p>
</blockquote>
<p>Which  CAD program would you recommend for this person?&nbsp; And why?</p>]]></content:encoded></rss:item><rss:item rdf:about="http://www.evanyares.com/the-cad-industry/2009/9/18/before-there-was-sketchup.html"><rss:title>Before there was SketchUp</rss:title><rss:link>http://www.evanyares.com/the-cad-industry/2009/9/18/before-there-was-sketchup.html</rss:link><dc:creator>Evan Yares</dc:creator><dc:date>2009-09-18T14:00:00Z</dc:date><dc:subject>SketchUp Alias The CAD Industry</dc:subject><content:encoded><![CDATA[<p><a href="http://sketchup.google.com/">SketchUp</a> is an amazing tool for doing conceptual design of buildings.  It's one of only a handful of CAD tools capable of inspiring passion among even casual users.</p>
<p>But what came before SketchUp?</p>
<p>Check out  this demo tape of Alias Upfront, circa 1991.</p>
<p><object width="425" height="344"><param name="movie" value="http://www.youtube.com/v/Ihisz51Qiew&hl=en&fs=1&rel=0&color1=0x006699&color2=0x54abd6"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/Ihisz51Qiew&hl=en&fs=1&rel=0&color1=0x006699&color2=0x54abd6" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="425" height="344"></embed></object></p>]]></content:encoded></rss:item><rss:item rdf:about="http://www.evanyares.com/the-cad-industry/2009/9/17/pushpulldragdrop-deelip.html"><rss:title>Push/Pull/Drag/Drop Deelip</rss:title><rss:link>http://www.evanyares.com/the-cad-industry/2009/9/17/pushpulldragdrop-deelip.html</rss:link><dc:creator>Evan Yares</dc:creator><dc:date>2009-09-17T21:23:55Z</dc:date><dc:subject>Deelip SpaceClaim Spatial Kubotek Trispectives The CAD Industry</dc:subject><content:encoded><![CDATA[<p><em>Update:&nbsp; In this post, I'm trying to point out that disagreement isn't a bad thing, as it can lead to discussion. &nbsp; I'm also providing a little history, to show that not everything new is unprecedented.&nbsp; Apparently my sense of parody is a bit obscure, because some folks thought I was picking on Deelip with this post.&nbsp; I think I need to make this  even clearer than I thought I made it originally: I like and respect Deelip, and my ribbing him is entirely good natured.</em></p>
<p>A few days ago, after I poked <a href="http://www.deelip.com/?p=512">Deelip Menezes</a> pretty good in a comment to one of his blog articles, he wrote me, saying "people like you and me were designed to disagree. However, I don't think either of us wants to entertain the world when doing so."<br /><br />I responded, "the fact that we disagree is not a bad thing.&nbsp; It gives a basis for discussion.&nbsp;&nbsp; And, if it entertains the world -- that's OK." &nbsp;<br /><br />It all comes down to motive.&nbsp; I think Deelip's motives are generally pretty good.&nbsp; He's an enthusiastic developer of CAD utility software, who has an interesting, and occasionally fresh, perspective on things.&nbsp; (Not to say that he doesn't get things wrong sometimes.&nbsp; Still, he's got a lot of catching up to match my record in that realm.)<br /><br />Today, I was reading his post, <a href="http://www.deelip.com/?p=515">How SpaceClaim Did It Differently</a>.&nbsp; I can't resist adding some perspective, and disagreement, of my own.<br /><br />Fourteen years ago, I wrote about Trispectives (a new CAD product) for CADalyst magazine, saying it could end up being "the Pro/E killer."<br /><br />The people at Trispectives liked what I said so much that they quoted me in their advertising, and on their product packaging.&nbsp; Years later, I learned that Buzz Kross, the VP of Autodesk's Mechanical CAD division, saw that quotation, and came to the conclusion that I was nuts.&nbsp; Or an idiot.&nbsp; Or something similar.<br /><br />Buzz had a good point, since Trispectives ended up killing nothing, especially Pro/E.&nbsp; Over the course of years, as we got a chance to talk every year at COFES, I think Buzz came to understand that I wasn't an idiot.&nbsp; And, I got to explain that the context of the quote was important:&nbsp; I wasn't suggesting that Trispectives was going to beat Pro/E in a feature-by-feature faceoff, but that it brought a new approach to CAD that made it usable for people who weren't gurus. &nbsp;<br /><br />Rather than using the parametric feature-based modeling process typical of the day, Trispectives let users model by starting with basic building blocks, then push, pull, drag, and drop them into the final form.&nbsp; This process involves directly selecting and manipulating features in a model, and has sometimes been called  "direct modeling."&nbsp; I prefer the term "direct feature modeling", to distinguish from  direct face modeling, a somewhat different technology.<br /><br />Trispectives was the first mechanical CAD product to implement direct feature modeling.&nbsp; It was rolled out to the CAD industry at the <a href="http://www.daratech.com/">Daratech</a> CAD conference in 1995--the same conference where SolidWorks was unveiled. (Charles Foundyller of Daratech deserves credit for the tremendous impact his conferences had on the growth of the CAD industry in the 1990's.)&nbsp; &nbsp;<br /><br />I remember sitting and chatting with Mike Payne, of SolidWorks, at that conference.&nbsp; Mike was quite familiar with Trispectives, but was of the opinion that the market really needed (or wanted) a product that, rather than redefining how CAD worked, simply built on the parametric feature-based modeling method used by the standard of the day: Pro/E.&nbsp; Given that Mike was also one of the founders of PTC, and had been responsible for much of the development of Pro/E, his opinion was worth listening to with care -- though, at the time, I thought he was just biased, because of his background.<br /><br />Turns out, of course, Mike was right.&nbsp; SolidWorks was a big hit.&nbsp; It was the first of a new wave of mainstream CAD products, which included (after a false start) Solid Edge, and (after rushing to avoid missing the wave) Inventor.<br /><br />Unfortunately, Trispectives was a market failure.&nbsp; It never delivered on the initial spark of promise it showed.&nbsp; Possibly because the time was not yet right, but more likely, because its technology wasn't yet ready for prime time.&nbsp; Still, just because it failed commercially, doesn't mean it had no impact on the market.<br /><br />Today, SpaceClaim is a shining example of what can be done with direct feature modeling.&nbsp; It was born out of a deep understanding of Pro/E and the other mainstream CAD products, and a desire to build a CAD system to  overcome the limitations inherent in the parametric feature-based modeling approach which those systems used.<br /><br />It could be a coincidence, but it turns out that Mike Payne, the same person I chatted with about Trispectives at the Daratech conference 14 years ago, was the founding CEO of SpaceClaim.<br /><br />SpaceClaim is by no means the only company to recognize that, possibly, Trispectives was onto something way back when. &nbsp;<br /><br />Siemens PLM has Synchronous Technology, which is the engine that enables direct feature modeling in both their Solid Edge and NX products.&nbsp; CoCreate, now a part of PTC,  never jumped on the parametric feature-based modeling bandwagon, but over time added direct feature modeling capabilities to their eponymous CAD product.&nbsp; Kubotek  pioneered direct feature modeling of dumb (e.g., IGES or STEP) models through feature inference.<br /><br />Deelip, in his blog post today, said:</p>
<p style="padding-left: 30px;">"[T]hey [other CAD vendors] have been offering direct modeling much before SpaceClaim, but what they did not offer (and some still don&rsquo;t) is the dynamic push-pull user interface that make SpaceClaim so easy and intuitive to use."</p>
<p>Deelip is right, with respect to some vendors, but, in general, he's wrong, as the example of Trispectives shows.</p>
<p>(Did you hear that Deelip?&nbsp;<em><strong> You're Wrong!!!</strong></em>)<br /><br />It's OK... I'm only picking on Deelip to provide some entertainment for the CAD world.&nbsp; I'm certain he'll return the favor.</p>
<p>Since I'm at it, let me pull a couple of more excerpts from Deelip's article:</p>
<p style="padding-left: 30px;">[I]f another MCAD vendor whose solution is built upon ACIS (for example Kubotek) wishes to add push-pull direct modeling capabilities to their software, they need to spend some more &ldquo;quality&rdquo; time with Spatial and learn some new moves themselves. . . .</p>
<p style="padding-left: 30px;">I believe what SpaceClaim did was really commendable. Its founders had a vision of an easy to use MCAD software and challenged the kernel developers to do things differently. Spatial took up the challenge and delivered. There is a word for that. Its called innovation and it needs to be appreciated. . . .</p>
<p style="padding-left: 30px;">SpaceClaim may have got some recognition for its innovation. However, I am not sure Spatial ever got any. For whatever its worth, I dedicate this post to Spatial and its brilliant programmers that helped make SpaceClaim happen.</p>
<p>Deelip has some good points here.&nbsp; The programmers at Spatial <em>do</em> deserve recognition for their work.&nbsp;</p>
<p>While there are many who are due credit, one name comes immediately to mind--Spatial Technical Fellow, principal author of the ACIS <a href="http://www.google.com/patents?vid=USPAT6941251">Space Warping</a> patent, and the leader of the team that developed the core ACIS technology that helped make SpaceClaim happen:&nbsp; Dr. Paul Stallings.<br /><br />As to Deelip's point about MCAD vendors (for example Kubotek) needing to spend some more quality time with Spatial:&nbsp; I think it's a great idea to talk to the people who are actually responsible for developing a technology.&nbsp;</p>
<p>I've had some very interesting conversations with Dr. Stallings at <a href="http://www.cofes.com">COFES</a>.&nbsp; He has tremendous technical insight into what it takes to do push-pull direct modeling--from his experience developing deformable modeling as a team leader Spatial, to his pioneering work in feature inference as VP of Development at <a href="http://www.kubotekusa.com/company/executive_team.html">Kubotek</a>.<br /><br />Oops.&nbsp; Well, maybe Kubotek already took Deelip's advice.&nbsp; But, instead of just talking to one of the brilliant programmers at Spatial, they hired him. <br /><br />(Incidentally, Kubotek KeyCreator doesn't support SpaceClaim-style push-pull direct modeling--but it's not for lack of knowledge of how to do so.&nbsp; Keycreator uses direct modification of inferred parameters.&nbsp; This method seems to work better for Kubotek's customer base, who often use KeyCreator for modifying or repairing third-party models.)<br /><br /><br /></p>]]></content:encoded></rss:item></rdf:RDF>