Ouch!
your reluctance to face accepted investment banking standards and customer requirements wouldn't bode well for you in this environment
Hmmm, well, I have actually been working in IT for merchant banks / securities firms in UK, Europe, US and a little Asia/Pacific/Australasia for more than 17 years now, in development, project management, and domain specialist roles.
The technical team I currently manage has 70+ banking entities in 8 timezones (about 40 distinct banks if you merge the legal entities) currently live, and more in the pipeline.
One of my current products manages real-time cross-bank market exposure for these banks on a continuous basis, yep, with changing time-stamped market pricing and FX rates. The system contains about 300,000 positions, current daily value is just over 735 billion USD in cash, debt and equity instruments (though we peaked in early June at 940 billion - next year we expect to break the trillion USD mark wahey!).
We sit on a number of UK and US industry initiatives, and are often consulted on <buzz>Future State</buzz> initiatives and responses to regulatory changes like the current Basel II and the US ALD and CapAd changes.
Your assertion that saving times in CET is more accord with 'accepted investment banking standards' doesn't gel with my reality - but hey, maybe you have a wider range of experience than I do.
You seem to have already decided that you are going to normaliese your date-times - albeit into CET. I was just recommending that you consider UTC. When you say CET - I assume you are excluding CEST/CEDT (ie Central European Summer / Daylight time) and are going for unaltered CET... watch out for confusion at the changeover. Of course, you may be actually saving CET and CEST date-times... again, watch out for changeover confusion.
Anyway, I only really responded to this because of your other wild assertions that I was posting anonymously - I don't do that.
Jeff
Update:Hue-Bond, points out that CDT should be CEST, post amended. |