There are two primary reasons for investing in QlikView Publisher
Allows the back-end reload Tasks to run on a separate server to the front-end QlikView Server machine. This means the interactive user sessions are not impacted if you have to reload QVWs during business hours.
The QlikView Publisher license unlocks the advanced scheduling features meaning you can have more than one reload task per QVW and you have Supporting Tasks which allow automation of other aspects of your solution that are not reloading a QVW.
There is a document available from Qlik called "Why QlikView Publisher" - it is very useful, I could not find it in the community.
-reloading the qlikview models --> Nprinting can do that but only one task/file at a time, right?
-alerting administrators when there is error in loading process --> What kind of alerts can publisher raise?
-distributing the models to other servers --> Nprinting cannot distribute .qvw files?
-managing the qlikview users who can see which model --> I dont get that. I think that security is either handled by windows (group a cannot access folder A) or through Qliview server (group A cannot see dimension member A).