A few variables, rdboyd.
When I'm tasked with helping customers with onsite installs I typically take 4 hours to install the software (I do Sun Solaris installs mostly, I'd think you'll do similar with an SP). Then a couple hours for patch or SP/IDU installs.
Now we have network discovery and this is where most bets are off. :)
I have been in situations where the network was a high-speed campus, very hierarchical, well-known devices and credentials (SNMP comm strings, telnet/SSH login and enable passwords). Maybe a few hours to discover.
Then again, I've been in situations where the network was smaller, not very hierarchical, possibly lots of WAN technology, spaghetti net...a bad mix of devices...nobody knows the SNMP comm strings or the passwords. It could take days to remediate the device logins to a consistent state....
Once we have discovery then I like to spend time building custom device groups - that requires customer input and making decisions (*grin*).
Then you start to configure up the applications. Are you using all of them in the CiscoWorks LMS suite? How about DFM? IPM?
There are special considerations for source/target and operation selections for IPM. With DFM you may want to set up automated actions.
So a lot depends on if it's an 'install and run' or if it's an 'install, discover and customize' scenario.
Again, based on how well, or poorly, engineered the network is you may have a quick or a very long engagement. :)
