It started on a Tuesday in March 2024, on the receiving dock of our integration shop. A pallet of blue cable showed up for a palletizer upgrade. The electrician had ordered 'network cable' to replace the damaged run between a barcode scanner and the PLC. The reel said Cat5e. The cable it was supposed to replace said LAPP. Two different worlds wearing the same color jacket.
I'm a quality inspector for a mid-sized automation company. I review every cable delivery before it reaches the floor—roughly 200 unique part numbers a year. In 2024, I rejected about 9% of first deliveries. Not because the suppliers are careless. Because cable specs are hard to trust from memory.
This is the question that should be asked before anyone buys anything. In an office, a network cable is usually a fixed, unshielded cable that never moves after installation. In a machine, a network cable might flex every cycle, share a tray with motor drives, and get sprayed with coolant. Same RJ45 plug, same protocol, but not the same cable.
An office cable is usually unshielded. A machine cable often needs braided shielding because it sits next to variable frequency drives. Same protocol, but not the same electrical environment. In our shop, we see three kinds of network cable orders. One is a fixed link between cabinets; a standard data cable is fine. Another is a connection in a moving cable track; that one needs a flex rating. And a third is a feedback cable for a servo drive, with individually shielded pairs. All of them look like network cable. None of them are interchangeable.
What most people don't realize is that 'equivalent' cable is not equivalent. A spec sheet can say Cat5e, but the construction detail—stranded vs solid, copper vs copper-clad aluminum, PVC vs PUR jacket, braided vs foil shielding—decides where that cable can live. I learned that the hard way.
The 'cable is cable' idea comes from the world of wiring closets and dropped ceilings. It was true enough twenty years ago when cable was installed once and left alone. Today, an industrial network cable often lives in a moving track. The old rules don't apply.
On the bill of materials, the original run was listed as a LAPP 220804. I want to say 220804, but don't quote me on the exact digits—I'm better with specs than catalog numbers. What I remember clearly is the construction. The old cable had finely stranded conductors, a flexible outer jacket, and shielding that held up to movement. According to the manufacturer's datasheet, that part was rated for continuous flex. The replacement was solid-conductor PVC cable rated for fixed installation.
I asked the electrician: 'Is this run in the moving track or in a fixed conduit?' He shrugged. 'Fixed conduit, mostly.' I checked the drawing. The cable went through a track that moved about 14 inches every cycle. Not a fixed environment.
Real talk: the label said Cat5e, but not all Cat5e is born equal. Look, I'm not against generic cable. Use a fixed PVC cable in a wall and it will work until the building is demolished. But in a moving track, solid conductors work-harden and snap. Foil shielding cracks. The jacket gets stiff in the cold. The problem isn't digital vs analog; it's copper being copper.
So we rejected the reel. Not ideal, but workable. Cost us a day of receiving time and a $90 rush charge for the correct part. The electrician said we were overthinking it. But a week later, the original damaged cable was replaced, the scanner was fixed, and the line ran clean.
A year earlier, I had approved a budget 'equivalent' for a small sensor drop. Saved $180 on the roll. The cable went bad on a night shift. The emergency callout cost $1,800. I've never made that substitution again. In my first year, I made the classic spec error: I compared AWG numbers and ignored the strand count. That little mistake cost us $600. The lesson was always the same: check the construction, not just the label.
Five minutes of verification beats five days of correction.
That quote sounds like a slogan. It became real after a $22,000 redo on another project where the cable was installed without checking the IP rating. A cable inside a wet washdown area had the wrong seal. Water got into the connectors. A whole production line stopped for two days. The cable itself was fine—the environment was not.
Here's something vendors won't tell you: the part number is the spec. LAPP 220804 is shorthand for a particular conductor count, a particular flex rate, a particular jacket material, and a set of test results. When someone substitutes a 'network cable' without a datasheet, they are not simplifying your life. They are asking you to trust the word 'equivalent.'
For motor and control circuits, we standardize on LAPP ÖLFLEX. Not because it's the most expensive choice, but because the construction is documented and traceable. For data links in moving machines, LAPP's ETHERLINE family is the same discipline: tested, documented, verified before release. What I mean is that the total cost of a cable is not the price per foot—it's the price per foot plus the technician's time, plus the probability of an unplanned stop, plus the cost of explaining to a plant manager why the network goes down twice a week.
A cable is a promise. It promises to carry a signal from one point to another under a set of conditions. If the conditions change—temperature, motion, oil, moisture—the promise breaks. Networks notice. Then the plant knows.
After that first substitution mistake, I built a 12-point checklist for incoming cable. It covers part number, datasheet, conductor type, jacket, flex rating, environment. The checklist has saved us an estimated $8,000 in potential rework—just by making the verification obvious.
If you've ever had to pull a failed cable out of a moving track while a machine is down, you know exactly what I mean. Trust me on this one: when a machine builder writes a specific LAPP part number, they are not being fussy. They are handing you the proof that the cable was tested under the conditions that matter. Don't trade that proof for a lower price.
And if you're ever tempted to ask what is a network cable, don't ask the cable. Ask the datasheet.