Skip to main content

Henrob tape feed riveting documentation

When I started working on the Henrob tape feed riveting documentation at Atlas Copco, I knew I was dealing with something special. This wasn't just another joining technology - it was a servo-driven system capable of setting rivets in just 1.2 seconds for high-volume automotive production.

Writing process and approach​

I began by spending time on the factory floor watching these machines work. The tape feed system was fascinating - rivets loaded from continuous tape, positioned with servo precision, and set at incredible speeds. But explaining that in a way that made sense to engineers, technicians, and production managers required a completely different approach.

The challenge was translating the complex mechanics of servo technology and rivet formation into something actionable. I worked closely with the engineering team to understand not just what the system did, but why design decisions were made and how different settings affected outcomes.

Connecting technical depth with practical needs​

Much like the server-sent events documentation I created at Ably, this project required bridging the gap between complex technical concepts and real-world implementation. The tape feed system had dozens of parameters that could be adjusted, but operators needed to know which ones mattered for their specific applications.

I developed a layered approach to the documentation. Quick reference guides for day-to-day operation, deeper technical sections for setup and troubleshooting, and comprehensive theory sections for engineers designing production systems. This mirrors how I structured the troubleshooting guides at Ably - different users needed different levels of detail at different times.

Industry-specific writing challenges​

Automotive manufacturing documentation is different from software documentation in critical ways. Safety is paramount - a mistake doesn't just cause a system error, it can shut down an entire production line or cause safety issues. Every procedure had to include proper lockout/tagout protocols and safety warnings.

I also had to consider the global nature of Atlas Copco's customer base. These systems were shipping to factories in Germany, Mexico, China, and dozens of other countries. The documentation needed to work across different languages, safety standards, and manufacturing cultures.

Process optimization through documentation​

The most rewarding part of this project was seeing how good documentation could actually improve the technology itself. As I worked through different use cases and edge conditions, I discovered scenarios the engineering team hadn't fully considered. This feedback loop between documentation and product development made both better.

I documented not just the current capabilities, but also pushed the team to clarify limitations and specify operating boundaries. This prevented customer applications outside the system's design parameters and reduced support calls.

Integration with existing documentation systems​

This work connected directly to the broader self-pierce riveting documentation I was developing. Both systems served the automotive lightweighting market, but for different applications and production volumes. I made sure the documentation clearly explained when to use tape feed versus other joining methods.

Similar to how I restructured information architecture at Ably, I organized this documentation around user workflows rather than technical features. Production engineers didn't care about servo motor specifications - they cared about cycle times, quality metrics, and changeover procedures.

Results and impact​

The tape feed documentation became a model for other Atlas Copco product lines. The modular structure made it easy to adapt for different markets and applications. More importantly, it reduced the learning curve for new installations and improved troubleshooting efficiency when production issues arose.

This project taught me that industrial documentation requires the same user-centered thinking as software documentation, but with much higher stakes. The principles I learned here - clarity, safety-first thinking, and global accessibility - influenced how I approached every subsequent docs engineering project.