Thank you both for your replies.
@JaredCroft: I see your point, it sounds rational and I understand the concern about having information spread over many places for one and the same thing. I am wondering though how one can achieve a good process overview both internally and also for an external viewer without having a short visual overview combined with a detailed description containing all the “deep” information. I have seen many flow charts containing some of the information needed to gain some overview but not enough to really understand the process.
In my view there should be some sort of document which allows to get a full overview of the process, its products, CPPs, CQAs, documents, equipment, etc which helps to understand the process and therefore serves as a good basis for risk management / analysis.
Would it be a suitable approach for both, good process overview and minimising redundancy, to just combine the two documents into one ?
So for example first few pages containing the flow chart overview followed by detailed description of each step.