Application notes, standards updates, and cable engineering best practices from the Nexans Cables engineering team.
A procurement manager breaks down the numbers on Nexans products and services, sharing a real cost comparison that changed how we evaluate vendors. Includes specifics on Nexans Olex, Todd Pepsi compatibility, 2660 flip, and vSRX integration.
A practical, step-by-step quality checklist for telecom cable procurement, based on real-world inspection experience. Includes common pitfalls and how to avoid them.
A procurement manager for a mid-sized telecom firm shares a costly mistake involving Nexans Halden cables and a Cisco switch comparison. This is a story about why understanding product specs, not just brand trust, can save your job.
A purchasing specialist shares costly mistakes with Nexans fiber optic cables and how to avoid them by understanding specifications, testing tools, and supplier nuance.
An office administrator shares a practical, experience-based review of ordering from Nexans for telecom and cable supplies, focusing on invoicing, reliability, and when to choose alternatives.
A cost controller breaks down the real cost of Nexans cabling solutions, comparing the TopTherm and DuraXV Extreme ranges based on over 6 years of procurement data. This is not a spec sheet review; it's a deep dive into total cost of ownership, hidden fees, and why a "cheaper" cable is often the most expensive mistake.
A procurement manager’s perspective on choosing Nexans vs. budget alternatives. Focus on TCO, hidden costs, and real-world contract experience.
A practical, step-by-step checklist for procurement professionals and engineers who need to source Nexans connectors under urgent or high-stakes conditions, with a focus on total cost of ownership.
A procurement veteran explains why choosing Nexans connectors over cheaper alternatives saved his team $20k+ annually, based on hard-won experience with hidden costs and performance failures.
A firsthand account of a costly cable specification error, how a simple multimeter test could have prevented it, and the pre-check checklist that saved my team from repeating the same mistake.