Skip to main content

Henrob blow feed riveting documentation

The Henrob blow feed riveting system presented a unique docs engineering challenge at Atlas Copco. This was energy-efficient technology - achieving just 7Wh per rivet while delivering setting forces up to 85,000 N. The engineering was impressive, but making it accessible to production teams required a completely different approach.

Understanding the technology first​

Before I could write a single word, I needed to understand why blow feed was different from tape feed systems. The magazine rivet feed mechanism was more complex than it appeared - pneumatic systems controlling rivet selection, positioning, and the actual riveting process all had to work in perfect synchronization.

I spent weeks with the engineering team, not just learning what each component did, but understanding the decisions behind the design. Why this pneumatic approach instead of mechanical feed? How did the energy efficiency improvements actually work? These weren't just technical details - they were the story I needed to tell.

Connecting to broader Atlas Copco experience​

This project built directly on the self-pierce riveting work I had already completed. The fundamental joining technology was similar, but the delivery method changed everything about how operators would interact with the system. I could reference the foundation I had built in the main riveting documentation while highlighting what made blow feed special.

Like the webhooks security documentation I later wrote at Ably, this required explaining complex interactions between multiple systems. The blow feed mechanism, the riveting head, the control system, and the quality monitoring all had to work together seamlessly.

Addressing multiple audiences​

Production managers cared about the 7Wh energy efficiency and what that meant for operating costs. Technicians needed to understand the magazine loading procedures and troubleshooting steps. Quality engineers wanted to know about the 85,000 N force capability and how to monitor joint integrity.

I structured the documentation with clear paths for each audience, similar to how I later organized the developer journey mapping at Ably. Different users had different entry points and different goals, but they all needed to understand how their work connected to the overall system performance.

Safety and reliability focus​

Blow feed systems operate at much higher forces than most manufacturing equipment. The 85,000 N setting force could cause serious injury if safety protocols weren't followed correctly. Every procedure had to start with safety considerations, and I had to make those warnings clear without being overwhelming.

I developed a layered safety approach - immediate safety warnings for dangerous operations, general safety guidelines for each section, and comprehensive safety training materials for new operators. This mirrors the contextual approach I used in troubleshooting guides at Ably, where different situations required different levels of detail.

Process optimization documentation​

The most interesting part of this project was documenting how to optimize the blow feed process for different production requirements. The energy efficiency wasn't just a marketing feature - it had real implications for production planning and facility requirements.

I worked with applications engineers to understand how different rivet materials, joint configurations, and production speeds affected energy consumption and cycle times. This became some of the most valuable content for production engineers planning new installations.

Quality and monitoring integration​

Blow feed systems generate different force and energy signatures than other riveting methods. I had to create documentation that helped quality teams understand what these signatures meant and how to use them for process control.

This connected to the broader troubleshooting approach I had developed for Atlas Copco - systematic diagnostic procedures that helped operators identify issues quickly and accurately. The energy efficiency meant smaller margins for error, so the monitoring and response procedures had to be more precise.

Global manufacturing considerations​

These systems were shipping to automotive plants worldwide, each with different quality standards, safety regulations, and operator skill levels. The documentation had to work equally well for a highly automated German plant and a more manual facility in Mexico.

I created modular documentation that could be adapted for different markets while maintaining technical consistency. This experience later influenced how I approached content restructuring at Ably - different markets and user types needed different presentations of the same core information.

Integration with broader joining solutions​

Blow feed riveting didn't exist in isolation - it was part of Atlas Copco's complete joining portfolio. I made sure the documentation clearly explained when blow feed was the right choice versus tape feed or other methods.

This systems thinking became central to how I approached docs engineering throughout my career. Individual technologies are just components in larger solutions, and documentation needs to help users understand those connections.

Results and continuous improvement​

The blow feed documentation became a reference for other product lines because of its clear structure and practical focus. More importantly, it helped reduce the implementation time for new installations and improved troubleshooting efficiency when production issues occurred.

The feedback from field applications helped identify areas where the documentation could be clearer, leading to continuous improvements that benefited everyone using these systems. This user feedback approach became a cornerstone of how I approached documentation projects at every subsequent company.