OEM Dependence Cycle
In the past, telephone systems were required to pass rigorous testing of both software and hardware before being released for general availability. But in recent years, OEMs have adopted a methodology similar to software manufacturers.
Rather than wait through lengthy “alpha” and “beta” test cycles to ensure product reliability, OEMs have shifted the testing burden to their customers in order to more quickly bring their products to market, causing consumers to bear the burden of relatively untested products.
New product releases often contain software glitches or “bugs” that can create a wide array of problems for end-users. Patches are then required from the OEM to repair the software defects. Today, most OEMs require customers to purchase costly software support in order to receive patches required to repair software defects. And, in order to purchase software support the customer must maintain a software release that is considered by the manufacturer to be current. This often requires the customer to purchase an upgrade. The required upgrade is often costly and, not surprisingly, contains new glitches or “bugs” resulting in a potentially endless cycle of dependence on the OEM.
Continuant can help you break free from the OEM Dependence Cycle.