It all depends on the business and how the adoption of QlikView goes. We have a number of manufacturing clients and they are each different. A couple of these clients run everything off a single QlikView document which pulls in all kinds of different information and tries to show it all in one place. On the flip side, other clients have a different QlikView app put together for each part of the business and each different audience. One particular customer has apps that cover:
- Sales performance
- Forecast variance
- Transport costs
- Customer complaints
- Budget adherence
- Production Line Planning
- Stock Availability and Movement
- Maintenance Spend
- Tooling Changes
- Operations KPIs
- Production Volume per Headcount
Over all of that there are then applications that look after systems and QlikView itself, such as the standard QlikView Operations Monitor, QlikView CAL monitor, Active Directory Group monitor, QlikView Status Dashboard.
In my experience there is always a significant advantage in having more smaller applications covering a specific part of the business. Each application can be built quicker, tested easier and can be tailored exactly to the audience. Where there is a single QlikView app that tries to do everything this is generally a symptom of a business trying to squeeze as much as they can from their Document CALs - but this can be a false economy as development and maintenance time can be much higher.
Regarding sheets, having more sheets will not cause a performance issue - but it can make things more difficult to find. Having more tables and joins in your data model to bring more information into one place, on the other hand, can cause serious performance issues.
Hope that helps give you a better picture.
- Steve
