Do you use a Reference Architecture?

Are you an architect who uses a reference architecture for your business, product, or application area? I find it to be a helpful tool to explain concepts and capture the "vision" for how components work together. I'd love to hear from others if they use this tool or another for the purposes I list below.

When I need a refresher on why we need to create reference architectures, I find myself going back to a paper I bookmarked a while ago. It is called "The Concept of Reference Architectures", and lists the purposes of a 'reference architecture' as: 

• provide guidance for future broad development efforts
• incorporate the vision and strategy for the future
• provide a reference for the numerous teams related to ongoing developments
• capture the commonalities and essence of the business, system, and technology architectures

The paper also provides a visual as to how it can fit into engineering practices:

In using one, I always like to remind myself (and teams) what a reference architecture is "not". It does not:

• Provide A “How To” guide for developers
• Select Technology
• Capture System Interfaces
• Define Specific Standards

Reference paper: https://wiki.lib.sun.ac.za/images/c/cb/TheConceptOfReferenceArchitectures.pdf

What does one look like in practice? Here's one I created for an Application Modernization program a couple of years ago.

Please respond in the comments if you use a reference architecture, whether industry defined or one you created yourself. When do you find them helpful and when do they seem like overhead? Do you have a favorite?