Tip Jar

Change is good

Tip Jar

A word from our sponsors...

June 06, 2006

eBay and Lobbying

As you may be aware by now, I think the relationship between manufacturing companies and CAD companies looks more parasitic than symbiotic.  I advocate that the manufacturing companies join forces to lobby for reform of the software industry.

In the blog post  Grassroots Support Helps eBay Lobbying Efforts, the author points out that eBay has shown success in lobbying various state legislatures for laws that help them.  One law they shot down was a Louisiana law requiring sellers to pay $300 for an auctioneer license.  The author also points out that other tech companies have lagged in their use of lobbying as a business tool.

June 05, 2006

Delphi Webcast on Improved Manufacturing Collaboration

ImageBand_TechTransfer

Sorry for the last minute post.  Delphi is sponsoring a free webcast tomorrow about their uniform approach to creating CAD geometry among their designers. 

Join Delphi executive David Lien, senior designer Kevin Marseilles and CAD industry expert David Prawel for this complimentary Webinar as they discuss the importance of standardizing design methodology and demonstrate its impact on global collaboration, efficiency and time-to-market. Learn how "Design Anywhere, Engineer Anywhere, Manufacture Anywhere" can become a reality in your company.  Link.

As I understand it, one of the problems in data translation is that there are so many ways to create similarly shaped geometry that it often ends up being easier for a designer to entirely re-create geometry than figure out how to use the existing data.  A related problem comes up in setting parameters for batched translation jobs.  Thus, Delphi limits the space of potential downstream geometry problems by limiting the ways geometry can be created.

As you may know, David Prawel ran the SME data exchange conference in Chicago two weeks ago.  So I am sure this conference is relevant and useful.

Shortly after you register, you will receive a confirmation email.  Information about access to the webcast is emailed to the registered participants on the day of the webcast. 

May 30, 2006

A three hour tour, a three hour tour

Shipwreck

Neil McAllister wrote "Why Redmond is so threatened by ODF."  He brings up an interesting point:

Thee celebrity tabloids cover Angelina Jolie’s love life as extensively as the IT trade press tracks the progress of ODF. The question is: why? How did something so completely mundane and uninteresting as an office document file format get to be the subject of so much press coverage?

The answer, of course, is Microsoft. As ODF has progressed, Microsoft’s mouthpieces have been there each step of the way, to give the company’s own contrarian spin on the topic. The ODF camp should probably thank the folks in Redmond for helping to make OpenDocument a household word — assuming, that is, that they hold with the popular wisdom that there’s no such thing as bad publicity. Because, if you’ve been paying attention, one fact becomes clear: Microsoft really has it in for ODF.

At the SME Data Exchange conference last week, a couple of the CAD vendors discussed how they believed user data belonged to users and proceeded to explain why they thought it was best to maintain two CAD data formats. None of the audience members bought the reasoning and I think it made the vendors looked a little desperate.  In fact, one of the vendor reps said he hoped that in a few years there would be no more need for interoperability conferences.  Yeah, I bet he does.

The CAD vendors would be wise to consider the fact that a rising tide lifts all boats.  Well, the rising tide lifts all the boats that have not already sunk.  The big CAD vendors are slowly sinking and some are just sitting on the bottom.  Sooner or later, the tide will come in and wash the rotten hulls away.  At least Gilligan and the Skipper tried to make the island comfortable.

 

Opensource Legos

legobot

As if there was not enough for my kids to get into, now Lego is encouraging them to make microbots.  <Link>  It is a bit more interesting than trains.

Unreliable software

lock and key black

CNet posted an article about a speech given by Oracle's Chief Security Officer Mary Ann Davidson at WWW2006 last week.  She was specifically criticizing the "patch" mentality of software and made an analogy to civil engineering, "What if civil engineers built bridges the way developers write code?"  The problem with such an analogy is that there are many PC manufacturers out there, requiring various patches, but the laws of physics are equally accessible to everyone.  In another sense, design engineers are frequently hindered by vendor lock-in and proprietary data formats.

I entirely agree with Ms. Davidson's point that bad software is becoming a nationality security issue.  Ms. Davidson and I may disagree on the scope of what constitutes bad software, though.  Ms. Davidson appears to have centered on hacking.  I would expand the scope to include anti-competitive business practices such as vendor lock-in. 

I can see this as an issue in the CAD industry in at least three areas.  First, it is a matter of sovereignty when a nation to allows its data to be stored in proprietary data formats.  Data subject to national security laws should not be secondarily subject to the dictates of a commercial software vendor.  Second, the data created at taxpayer expense should generally be considered a public good and available to the public in non-commercial data formats.  The exception, of course, is data important to national security but even this eventually passes into the public domain.  Third, once a CAD vendor stops functioning as a business or dissolves entirely, the availability of user data stored in that vendor's proprietary format depends on a number of factors that the user may have no control over such as the affordability of licenses for extinct packages, availability of equipment to run the old software, availability of operators with the expertise to run the dead CAD package, etc.  Military airplanes (thankfully) are now around for generations so the design data should not be subject to the format de jure.

Ms. Davidson also discussed the possibility of the regulation of the software industry.  I found this point somewhat disturbing.  When the government begins regulating industries the unstated goal of the corporate parties is to hinder future competition by setting high regulatory hurdles for new comers.  In the case of an industry involving critical dangers, such as nuclear power, the regulations are no doubt a good thing.  In other industries, like telecommunications, it probably not good for the public to have the industry very regulated.  So where does online banking fall along the continuum?

I am sure customers want there data secure from hackers, but I am equally sure that customers do not want to prop up a banking monopoly through software regulation.  For this point, I point to the growing P2P lending business which is nothing more than individuals exercising their right to contract.  Ms. Davidson's position within Oracle makes me suspicious of her motive behind these statements.  She may be correct, but I am suspicious of self-interest when her company grew under the very conditions she now advocates regulating away.

Why, then, should I advocate a difference in the CAD industry?  I think a root of the problem CAD interoperability problem stems from the political necessity of the sharing the benefits of multi-billion dollar contracts over many jurisdictions.  Thus, interoperability should be addressed as a political problem not just as a technical problem. 

Recent Reading

Blog Roll

Blog powered by TypePad

Sponsors

  •  View My Public Stats on MyBlogLog.com