| Original Message |
hj
Posted Jul 2, 2009 2:50 PM
I have a client where their current production lockdown is moving from 3 months to 5 months. Anyone out there have a longer lock down duration for Essbase?
That leaves roughly 7 months whereby essbase can be modified to meet the users budgeting / allocation / reporting requirements. I guess that's still at least half a year where production changes can be made. I just need to line up my customers by when their lock down periods are open.
I've battled sox auditors in the past and prevailed.
Battling IT is a different story.
What other outlandish IT rules have you seen applied to Essbase that all but make it unusable?
I had one IT manager try to tell me they would need a 5 hour overnight window to backup 10 gig........ That would have left me with 2 hours for my nightly processing.
The stuff business guys do to derail a project can't really be categorized other than to say they keep changing their mind....
hj |
|
|