Viewpoint Systems, Inc.
800 West Metro Park
Rochester, NY 14623
Phone: 585.475.9555
Fax: 585.475.9645
Viewpoint Data Management, LLC.
800 West Metro Park
Rochester, NY 14623
Phone: 585.475.9555
Fax: 585.475.9645
Viewpoint News, March 2010
Last month, we discussed platform choices. These decisions are made at the start of the project. However, this month’s topic covers the other end of the timescale, after equipment becomes old and possibly obsolete. Maintenance is not just about the measurement equipment. All test system components age and at different rates. How does maintenance affect platform choices and system design and what can you do to minimize the effects of aging?
Maintenance is traditionally concerned with assuring equipment remains operational. Calibration, lubrication, and replacing worn items were handled on a periodic basis based on how fast the component changes from its baseline.
Perhaps the most critical aspect of these traditional maintenance tasks is planning for downtime of the test system. One of the best ways to minimize downtime is to have spares. For example, have a spare:
Of course, some test systems have costly components (such as an Instron hydraulic tester) that need periodic maintenance overhaul and you won’t be able to afford a spare. But, the goal is still to get the test system operational as quickly as possible, so plan and assure that everything needed for an overhaul is available when you begin.
Last month, in the discussion of platform choices, the length of time that the test system would be used affects the choice of system components. The stability of the component vendor, the use of standards, the PC, and OS all affected the selection of components during the system design. These decisions affect the availability of components after the system is built.
But, even with the best of planning, sometimes the test system is used longer than expected or your system design choices are out of favor faster than you anticipated. You may eventually need replacement components that are no longer manufactured. The fun starts when:
Now what?
Many older instruments, such as an old HP spectrum analyzer, can still be calibrated by calibration companies, of which there are many, rather than the original vendor. So, as long as the equipment is working, it can likely still be calibrated and utilized.
If the instrument is nonfunctional, or you are concerned that it might not be functional in the near future, the four successful methods I’ve seen are:
This situation is classic reverse engineering. Get out your DMM, scope, and tape measures. It’s time to figure out all the components and connections. Mechanical components can be tricky to reproduce due to unknown tolerances. Electrical components at the PCB circuit level can be especially tricky. Talk with us if you have this issue. We are experienced in reverse engineering and our custom instrumentation capabilities might be of use for circuit boards.
This situation has elements of the obsolete instrument and lost documentation because it’s likely that that obsolete component will not have its specifications listed anywhere. In this situation, you have some idea about what to build, but need to find equivalent replacement parts and you don’t know what “equivalent” means.
Finally, parts and components that need calibration and other periodic maintenance should be easily accessible. For example, such components should be put near the exterior of the test system unencumbered by harnesses, mounting plates, power distribution, and so on. Obviously, it’s a bad idea to bolt a PXI chassis right behind a 19” rack patch panel or ATE terminal blocks without an easy way to access the modular instruments inside the chassis for calibration.
Test systems seem to have a way of being used for longer than expected. We see this happen frequently and especially for medical devices and military components. Proper periodic maintenance will prolong test system usage. Design your test system for easy access to the components needing maintenance. Finally, when components become unavailable, I described some methods to keep the test system alive.