Phone: 925.456.9900 Request for Quote
Manufacturing

Pioneer in Obsolescence Management and Legacy Sustainment for embedded technology

  • Counterfeits  Take To the Road

    Counterfeits Take To the Road

    Those who have been keeping up know the threat counterfeiting poses to the embedded world. To this point, most of our conversations regarding counterfeits have been focused on the damage they can do to projects, the costs incurred to replace them, and the threat they pose to the security of the supply chain. However, there is still the basic, personal way they continue to threaten us—the real and direct danger to us and our families as we go about the day-to-day business of driving from place to place.

    Counterfeit tires are on the road, and they are less safe and of lower quality than the products they pretend to be.

  • Microgrid Death Spiral: The Argument Over “Obsolete” Power Infrastructure

    Microgrid Death Spiral: The Argument Over “Obsolete” Power Infrastructure

    In January of 2013, the Edison Electric Institute released a report titled “Disruptive Challenges: Financial Implications and Strategic Responses to a Changing Retail Electric Business”, which outlined a variety of challenges traditional power utilities will face in the upcoming years. The current power infrastructure in the United States wasn’t constructed with end-user power generation in mind, so the increasing power independence of households and businesses creates threats of “irreparable damages to revenues and growth prospects.” Chief among new technologies are advanced renewable energy sources, including solar, and the growth of grid-independent distributed power generators, aka microgrids.

  • Counterfeit Components Hurt More Than Military Applications

    Counterfeit Components Hurt More Than Military Applications

    When reading the news around counterfeit components, much of the dialogue is driven by the defense industry. When you are dealing with systems that protect our national security and the lives of the people out in the field – you’re not dealing with counterfeits in a bunch of trivial electronics. You’re taking necessary steps to protect the lives of men and women who depend on the systems for their safety. Since 2011 more than 1800 cases of counterfeit components were reported in defense applications, including mission computers operating the THAAD missile system, in the Air Force’s C-27J, in the Navy’s P-8A, and in electromagnetic interference filters on an SH-60B helicopter.

    However, the trouble with counterfeits isn’t limited to the defense industry and the military. They’re just currently the ones driving the conversation and legislation such as the 2012 National Defense Authorization Act, Sec. 818.

  • Obsolescence: Too Soon or Not Soon Enough?

    Obsolescence: Too Soon or Not Soon Enough?

    It is strange how onboarding the concept of legacy sustainment can change the way you look at the world around you. On a recent road trip along one of the nation’s many two-lane highways, I found myself wondering about the thousands upon thousands of wooden utility poles dotting the landscape. How often are they repaired? […]

  • Keys to Successfully Managing DMSMS: Being Proactive

    Keys to Successfully Managing DMSMS: Being Proactive

    “Proactively take timely and effective actions to identify and minimize the DMSMS impact on DoD acquisition and logistics support efforts.” SD-22 DMSMS Guidebook The DMSMS conference is just around the corner. As a conference all about obsolescence management, it tends to be one we look forward to every year. This year, we’re looking to take […]

  • Software Obsolescence: Why Modernization Doesn’t Necessarily Mean “Modern”

    Software Obsolescence: Why Modernization Doesn’t Necessarily Mean “Modern”

    For players in the embedded industry it is easy to forget how large the problem of obsolescence can be, especially beyond the component level. Recently, I was talking to a software engineer who had spent a year doing software modernization, as a result of upgrading a flight navigational system from the original code to Linux.

    The reasoning for the transition certainly made sense—the program was having difficulties finding software engineers who could continue to sustain programming that had been implemented during the early 1980s. While the system was incredibly robust and was considered “bulletproof,” it could no longer be supported the way it had been. Under pressure to upgrade, the program moved to Linux, which has a community that affords an active and growing resource for talent.

Newsletter Signup