Archive for the ‘Specs & Standards’ Category

Battery Safety — It’s Just Not Fair

May 29, 2010

I picked up the LA Times and once more read that HP has announced yet again another laptop battery recall. Our firm uses this brand, and once more our personnel are being exposed to volatile battery pack angst.

I am intimately aware of the possible consequences of ignoring my responsibility as a consumer responding to a battery recall, because the risks of battery fire or explosion are real. I know it, yet I resent it.

Here’s why:

  • MarkeTech’s involvement in the mobile computing industry’s safety efforts with the SMBus (Smart Battery Bus) battery specifications and standards. I attended the presentations (and even made a few) that invariably included videos and photos of battery fires and explosions.
    • I resent the outcomes of my and others’ work. Except for a rare few, the battery and battery-powered device manufacturers didn’t fully implement the SMBus standard. Too expensive.
  • I patented a number of battery-safety solutions that not only solved the problem for future battery packs, but also improved the safety of legacy batteries already in use. No takers for new technology that would have added less than a dollar to the retail price (usually, over $100) of a laptop battery pack. Too expensive.
  • I spent an inordinate amount of time traveling the globe to include battery-safety provisions in the commercial aviation industry specifications for passenger devices.
    •  After an onboard computer-device fire, a major conflagration at LAX involving pallets of L-Ion batteries, recalls of battery packs in the laptops pilots and crew were bringing aboard, and letters from the battery industry…these weren’t enough evidence of the safety risks. Instead, the safety issue was put to rest by an FAA safety officer “proving” that laptop battery packs didn’t combust or explode by using his backyard barbeque as a test lab! Oh, yes, let’s not forget – especially in commercial aviation, implementing safety is too expensive.

Today, I am responding to this second recall. Once again I’m spending time collecting battery pack serial numbers, logging on to the HP website, hunting down the exact product model (is this a zv5000 or zx5000?), then scanning an extensive list of battery serial numbers, blah…blah…blah. I resent it.

Yes, this reads like I’m venting. But, it’s supposed to be the darned battery that vents when it’s in a pre-failure mode, instead of me having to help clean up avoidable outcomes by responding to yet another recall.

I think I did more than my part to help avoid, or at least minimize, these recalls. Recalls are certainly the least expensive route, but…it’s just not fair.

 #     #     #

 Other Relevant Blogs

The Benefits of Specs and Standards Marketing
David v. Goliath:  Specifications and Standards
Code Word “Interoperability:”  Danger Will Rogers!

 Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to TwitterAdd to TechnoratiAdd to Yahoo BuzzAdd to Newsvine

The Benefits of Specs and Standards Marketing

May 21, 2010

I grew up in a technical environment. My Dad, a mechanical engineer, VP of Manufacturing for ITT Europe, and disciple of William Edwards Deming, was always reminding me about the importance of science and technology. (That’s probably why I wound up working in high tech and then founding MarkeTech.) Many years ago he sent me the following.

“How Specs Live Forever (author unknown)

“The U.S. Standard railroad gauge (distance between the rails) is 4 feet, 8.5 inches. That’s an exceedingly odd number. Why was that gauge used? Because that’s the way they built them in England, and the U.S. railroads were built by English expatriates.

“Why did the English people build them like that? Because the first rail lines were built by the same people who built the pre-railroad tramways, and that’s the gauge they used.

“Why did ‘they’ use that gauge then? Because the people who built the tramways used the same jigs and tools that they used for building wagons, which used that wheel spacing.

“Okay! Why did the wagons use that odd wheel spacing? Well, if they tried to use any other spacing the wagons would break on some of the old, long distance roads, because that’s the spacing of the old wheel ruts. 

“So who built these old rutted roads? The first long distance roads in Europe were built by Imperial Rome for the benefit of their legions. The roads have been used ever since. And the ruts?

(more…)

David v. Goliath: Specifications and Standards

March 30, 2010

BYBM3WGN9NH7

The underdog applies a little friendly guerrilla marketing.

I just put the finishing touches on a press release announcing one of our firm’s clients throwing its hat into the ring as a supporter of the federal government’s Virtual USA program. Writing the release was fraught with memories of one of my other involvements in getting a client’s technology into a government-mandated specification and global standard.

Those memories include traipsing all over the world from one spec meeting to another. Being up most of the night not because of jet lag, but putting the final touches on a specification document, updating a PowerPoint presentation, or lobbying spec leaders in a hotel bar.

The specification subject matter focused on global standards for passenger use of laptops on commercial aircraft. Virtual USA has similar implications, as a program that will standardize agency emergency response databases at all levels, from the local police and fire departments up to the FEMA and Department of Homeland Security level. Both specifications address issues of safety…ways to prevent an exploding laptop battery at 30,000 feet being analogous to emergency first responders having access to national databases via GIS (Geographic Information Systems) mapping software.

Another analog is that both clients are comparatively small fish, and both have IP and products that are (more…)

Code Word “Interoperability:” Danger Will Rogers!

March 13, 2010

It’s Saturday, and I’m preparing for Monday’s conference call with a GIS client. The topic is the government’s Virtual USA (vUSA) initiative, specifically a press release about the client’s mapping software as a viable end-user application in vUSA.

I’m conflicted as to how to counsel my client.

On the one hand, the vUSA information appears to be focused almost exclusively on data interoperability, with limited statements about the app layer (See my comment at Directions Magazine). The Technologies Working Group is working integrating data with different (read “legacy”) applications that agencies already he in place. The apps are going to be open-source, it seems. That’s may not necessarily be good for my client., because it infers the possibility of having to surrender the company’s strong IP.

On the other hand, my firm has considerable domain expertise in specs and standards. Hands on in key WINtel and the Mobile Advisory Council (MAC) specs and standards as players in Marketing SIGs. Our firm was a lead player in drafting government (FAA) specs/standards for mobile device software, hardware, and infrastructure for use on commercial aircraft. I hold 14 patents on those high-tech mobile devices.

In this situation with my client, I feel like the man who knows too much about how government agency specs/standards usually get created. Our firm marketed its mobile device client to success in accepting its interoperability requirements at the standard’s gray cover stage. Over a year and a half, our marketing/PR campaign hobbled the alleged incumbent, paralyzing that company’s already sizeable installed customer base.

Why couldn’t the AEEC (Airlines Electronic Engineering Committee), ARINC (Aeronautical Radio Incorporated), and other agencies accept both companies’ requirements? Because, even though government specs/standards are supposed to be open sourced, and are supposed to allow for “interoperability” performance from more than one vendor, the reality was that the spec process was only to give an 800-pound gorilla exclusive rights to monopolize the commercial aviation industry. We were also able to successfully resolve our client’s potential surrender of its IP rights…a common issue in some agency specs/standards.

By comparison, the firm’s experiences in the high-tech specs/standards bodies were not met with such interoperability issues. Any company, including our client, was able to bring its requirements into the standards. Our firm was able to leverage our client’s alliances that we created with Intel, Microsoft, and IBM to join the client in its government specs battle.

Our client believes in and wants to contribute to the success of the vUSA initiative but, if what that other client experienced happens here, I guess at least this client will have the benefit of how our firm engaged in the art of war with government specs/standards.

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to TwitterAdd to TechnoratiAdd to Yahoo BuzzAdd to Newsvine


%d bloggers like this: