We planning our installations for use of RTC, QM and DOORS NG into our organization and would like to know what functionality if any impose the use of "thick clients".

To elaborate, our env is divided into 2 separate domains in that users typically have 2 hosts
- that provided our corporate IM group - a locked down image (users don't have admin writes) used mainly for email and MS Office products, etc..
-  and dev hosts - used for development purposes where users typically have have full capabilities.

For corporate hosts, our IM group needs to create installation bundles, etc. for each app that needs to be installed onto their controlled hosts whereas on the dev side users can do basically what they want. Needless to say its cumbersome to get stuff installed on corporate hosts.

In our JTS setup we'll have RTC, QM, DOORS NG and RRDI. We are also getting Rational RPE for reporting.
Based on the the above, at this point I know their is a DNG client and the Eclipse RTC client. Are there any other "thick" clients required say for RRDI or RPE? (I am not familiar with these two apps.)

For DOORS NG  - is there any functional differences between the web and thick client useage? To clarify, is is there any functionality that would necessitate the use of the thick client that the web if is not capable of doing?  I'm not really interested in what the web i/f provides (e.g modify attributes) but what it lacks that forces the use of the thick client.

For RTC use on corp hosts, basically all they are doing is documentation checkin/updates. Do they need the RTC client for this or can it be done via the web or other means?

The end result of this is that I need to define what clients are needed on corporate hosts.