Do you start low, and increase these values if users have valid complaints about not being able to complete tasks? What values do you start with? The only one that makes sense is CPU/Call, where you can limit the amount of CPU time consumed per call to say, 30 seconds, be setting this to 3000.
Yes ... You can get connect and idle times from v$session ... For some of my clients, I limit the connect time (users that wont log off ...) etc ... Here's a little script to monitor session idle time ...
col sid format 999
col username format a10 truncated
col status format a1 truncated
col logon format a17
col idle format a9
col program format a30 truncated
to_char(logon_time,'dd-mm-yy hh:mi:ss') "LOGON",
order by last_call_et;
As far as I can see the only reason for setting up the 4 parameters that you mentioned is to limit a heavy user or users (e.g. by rationing how much CPU they can use either in a call or in a session) - I have yet to meet a user that I disliked so much as to set these up in his profile (though I have been tempted a few times!)
As Gregg said, idle times & connect times are a more 'user friendly' way of monitoring the users.
90% of users' problems can be resolved by punching them - the other 10% by switching off their PCs.