Shamelessly indulged the inner INTP this week ...
and she produced a project proposal containing:
EXPECTED BENEFITS: ELIMINATE ARCHIVE (APPROX 2,500 GIGABYTES)
That should get someone's attention, ya think? :)
It's another one of my classic HASSLs - which stands for *HA*irbrained *S*cheme*S* hatched over *L*unch by *S* {me}. Elegant in simplicity, "WTF???? Nowai!?" on the surface and "damn that's so OBVIOUS" in the details. Now to see how well it holds up to having holes poked in it by people who have far superior technical and current-system-knowledge than I.
$boss is NOT going to begrudge me billing for the extra hour of chart-it-out and poke-holes-in-it and writing-it-up time. Even if someone finds a deal-breaking hole, or it can't be started until well after my contract is up ... the payback will be there for the company. One of my previous HASSLS years ago saved them $15-$20 million USD a year. So I'm hoping the rep-mojo will ensure that this doesn't get immediately dismissed as puffery. At the very least, the reasoning behind why I think we can now eliminate this huge 1,600# gorilla known as the history tables will lead other people to analyze how they use the table, and whether they could get what they need from other systems.
And in other news, I'm giddy with joy because at the last fillup, Goldie got 38.2 mpg in CITY driving, even considering the couple of days of AC use.
Gods, I'm easily pleased at times. :) Saving $5 off my petrol bill is as joyous an occasion as coming up with a plan that will save a client millions?
And I've really, really missed dealing with credit systems. It wasn't until this afternoon I started to feel the physical strain of being on a creative and productive binge high for 12-15 hours a day, five straight days. Logistics arena kicks ass, and I'm seriously good at it, but credit/financial systems and compliance is *Home*.
EXPECTED BENEFITS: ELIMINATE ARCHIVE (APPROX 2,500 GIGABYTES)
That should get someone's attention, ya think? :)
It's another one of my classic HASSLs - which stands for *HA*irbrained *S*cheme*S* hatched over *L*unch by *S* {me}. Elegant in simplicity, "WTF???? Nowai!?" on the surface and "damn that's so OBVIOUS" in the details. Now to see how well it holds up to having holes poked in it by people who have far superior technical and current-system-knowledge than I.
$boss is NOT going to begrudge me billing for the extra hour of chart-it-out and poke-holes-in-it and writing-it-up time. Even if someone finds a deal-breaking hole, or it can't be started until well after my contract is up ... the payback will be there for the company. One of my previous HASSLS years ago saved them $15-$20 million USD a year. So I'm hoping the rep-mojo will ensure that this doesn't get immediately dismissed as puffery. At the very least, the reasoning behind why I think we can now eliminate this huge 1,600# gorilla known as the history tables will lead other people to analyze how they use the table, and whether they could get what they need from other systems.
And in other news, I'm giddy with joy because at the last fillup, Goldie got 38.2 mpg in CITY driving, even considering the couple of days of AC use.
Gods, I'm easily pleased at times. :) Saving $5 off my petrol bill is as joyous an occasion as coming up with a plan that will save a client millions?
And I've really, really missed dealing with credit systems. It wasn't until this afternoon I started to feel the physical strain of being on a creative and productive binge high for 12-15 hours a day, five straight days. Logistics arena kicks ass, and I'm seriously good at it, but credit/financial systems and compliance is *Home*.