MBA        Imperial College of Science, Technology and Medicine (University

  of London), Management School, 1992 - 1993.  Master of Business

  Administration and Diploma of the Imperial College, 1994.

BSc (Hons) University of Pennsylvania, Moore School of Electrical

  Engineering, 1979 - 1983.  Bachelor of Science in Engineering,

  Computer Science and Engineering, Magna Cum Laude, 1984.

perl-DBI, -DBD::Sybase, -DBD::Informix

typical Projekt: FrontArena, Sybase, Unix/Solaris, perl, Prime, AEL/python,

SQL, sh, cvs, Windows-Clusters, SQL-Server

* lots of data manipulation and data transformation
* prefer UNIX tools such as python, perl, awk, sh
* can also do plenty with MS Office, particularly MS Access
* rapid rapid-prototyping; proof of concept
* have done some DB Administration and performance tuning and testing
* I'm really a DP jack-of-all-trades, with business knowledge

Banking and Financial Services
Equities, Foreign Exchange and Interest-based Instruments
IT Services
Industry and Trading
Logistics

2010 - Major Bank, Migration Project, Front Arena

 

So far in 2010, worked on two projects for a major bank in Munich. The primary project was the migration of a legacy Front Arena system to Murex, although my work involved only the Front Arena side. My task was the development of a suite of data-extraction programmes which make the full set of data related to live trades in Front Arena available to the Murex team on an ongoing basis as well as on the cutover weekend. Additionally I performed analysis and documentation work for existing interfaces and queries in Front Arena, with an eye towards providing specifications from which the Murex team can work. The secondary project was the design and implementation of a query/interface in Front Arena for the backloading of legacy IRS and OIS swaps from Front Arena to SwapsWire, in accordance with the SwapsWire Backload Cookbook.

 

2009 - Development Bank, Developer, Front Arena

 

Worked as a programmer/analyst on a Front Arena system for a state development bank in Dusseldorf. My work was concentrated on re-working and enhancing two processes, the mark-to-market programme and the market conformance process. The first involved optimisations and bank-specific customisations to the standard MtM-product of the system. The second involved a back-end programme which captured and evaluated trades with respect to market conditions in real-time, and a front-end GUI programme integrated into Prime which the risk managers use to identify, check and sign off on any trades which are not immediately accepted by the configurable tolerance rules. This work involved reverse-engineering of the existing processes, analysis, interfacing with the risk managers, implementation, testing and documentation. A side-task involved a prototype integration of a Fix-protocol engine with an interface to Front Arena.

2007-2008 - Major Bank, Application Manager, Front Arena

Worked as the sole technical and functional system manager and maintainer
for the entire Front Arena installation (which I helped introduce in 2002
and 2003) for a major bank in Munich. My work included testing and
performing numerous upgrades as dictated by the exchanges, maintaining
system stability and compactness despite continually increasing data
volumes, setting up and caring for the various users, diagnosing and
repairing any problems and keeping the interfaces and data clean as
conditions changed. The wide range of my activities required that I know
all parts of the Front Arena system inside out and front to back, and
navigate within the bank's system landscape and change management procedures.

2006-2007 - Major Bank, Project Manager, Front Arena/Heterogeneous Systems

Worked as the project manager for the introduction and initial integration
of a new Front Arena 2.2 platform for a new equity derivatives trading
group at a large German bank in Zurich. Coordinated all aspects of the FA
subproject, from the hardware and software installation and configuration
to accommodating the demands of the traders, middle office, compliance,
business and the vendor. Met the ambitious 'go-live' target date of eight
weeks after my arrival in the project. Normalised the data flows and
operational procedures, including hands-on training of the middle office,
and stabilised the system, in order to make it operable in the long term.

2006 - Major Bank, Control-Programme Developer, Front Arena/Python/Win32Com

In early 2006 I worked as a developer for a major bank in Frankfurt.
The task was to design, implement and document a control programme which
could be used as the framework for carrying out the bank's P&L calculations.
The various job steps to be performed could be combined however necessary
via specification in a configuration file.  The possible job step types
included the following: ASQL-reports, PortfolioSheet-reports, report
upload to Access or Excel, callout of VBA-procedures and mailing of result
files using LotusNotes.  The existing reports were then bound into the
framework as an initial example of how the tool is to be used.  Components
used: Front Arena, AEL/ACM/Python, Tkinter, Win32Com, ASQL, ADFL, cygwin,
cvs, Access, Excel, Lotus Notes Mail.

2005 - Major Bank, Interface Developer, Front Arena/Python/Sybase

During 2005 I served in the team "Front-Arena" of a major public
bank in Munich. Many diverse tasks were asked of me; new development,
programme changes, improvements and optimisations, error detection
and analysis and, particularly, performance issues. A major theme for
me has been data volume and database size management; aggregation,
archiving and deletion. Components used: Front Arena, Sybase, OOP,
AEL/Python, SQL, sh, cvs, SUN Solaris.

2004 - Major Bank, Interface Developer, Front Arena/Python/Tkinter/Sybase

In 2004, I worked performing design, implementation and
documentation of two data import/export interfaces to the Front
Arena financial information system for a major bank in Frankfurt.
These involved a price/volatility interface for the mark-to-market
process and a trade interface for reverse convertibles.  The MtM
data is ordered using a GUI (Python/Tkinter) or in batch.  Both
trade and price data are delivered via Mercator to the AMB, picked
up, and processed in an AMBA/AEL/Python hook before flowing into
Front Arena.  Replys are generated in a hook and passed back to
Mercator.  Interesting here was the integration of Tkinter with
AEL, enabling custom GUIs to be developed and then served from
within Arena.  Also, I created object classes and a wrapper for
the easy development of further AEL hooks.  Components used:
Front Arena, Sybase, OOP, AEL/Python, Tkinter, SQL, sh, cvs,
ClearCase, SUN Solaris, Excel.

2002-2003 - Major Bank, Integrator/Developer, Front Arena/Sybase/Perl/Solaris

My primary project in 2002-2003 was integration work in a team
performing the introduction of the trading and positioning
system Front Arena for equity risk management for a large bank
in Munich.  I also served as the project's cvs-administrator.
I was responsible for: design, implementation, maintenance and
documentation of batch programmes and external data interfaces,
problem analysis and correction, performance testing, analysis
and improvement at the application and database levels, and
software repository and version administration.  We used the
following components: Front Arena, Sybase, Unix, perl, python,
SQL, sh, cvs, SUN Solaris.

2003 - Cable Infrastruktur, Developer, Informix/Perl DBI/Solaris

A minor project in 2003 was for a provider of cable infrastructure
and consisted of two parts.  1) the introduction of cvs, including
importing the existing application from sccs; for repository access,
I configured two GUIs, WinCVS and tkcvs (based on Cygwin/XFree86)
and made them generally available.  2) design and implementation
of a subsystem for asynchronous, distrubted updates of standing
data tables, including the automatic updating of foreign key values,
using perl with DBI/DBD::Informix, triggers, stored-procedures and
SQL on an Informix DB on a Solaris machine.  Also configured several
RAID devices for Informix.

2001 - Major Bank, Upgrade-Analyst/Developer, Kondor+/Sybase/Solaris

My previous primary project in 2001 was adapting and upgrading a
complex interface software package between the front-end Kondor+
system and a bank-internal treasury back-end software for a large
bank in Munich.  The bank was migrating from Kondor+ 1.9 to 2.0,
which brought many new features and semantic differences in the
data model which had to be accommodated.  The software was used to
transmit money-market and foreign exchanged deals entered by the
traders from Kondor+ to the bank's back-end interface, both in real
time and again as a batch in the evening.  The following components
were used: Kondor+, Sybase, Unix, C, SQL, sh, cvs, Solaris.

2000-2003 Cirrus Logic, CRM-Development/Maintenance, Access/NT

My secondary project in 2000 to 2003 was the care and maintenance
of a CRM application for the european offices of a US-american
chip manufacturer.  In 2000, I took over and fully re-engineered
the application which had been implemented by an amateur in his
free time.  It was based on MS Access and consisted of separate
programme and data parts, with the data tables being replicated
over the company's intranet from a centralised NT-Server.  I had
to struggle plenty with various Windows and Office upgrades during
those four years.  The main data were product, prices, customers,
distributors, projects, forecasts, users and events.  All Data were
entered using forms, VBA modules performed validation and steered
the user's navigation.  The user had many reports to choose from,
which were automatically exported to Excel and formatted.  One
interesting forecast report allowed external partners to change
the data in the Excel spreadsheet, which would then be re-imported
into the application.

1999 - Epcos, EDI/Warehouse-Stock Control-Development, Access/NT

My prior project at Epcos was the design and implementation of a
stock control application for a consignment warehouse, based on an
MS-Access database.  The application accepted EDI-inputs from the
trading partners, computed the current stock levels, made intelligent
re-stocking order suggestions and generated the corresponding EDI
messages to submit the orders.  There were also plenty of reports
to be generated.

1999 - Epcos, EDI-Specification Author, EDIFACT

My previous project for Epcos was the specification of many, many
EDI-translations between various customers' EDIFACT versions and
the in-house version, for several EDI message types.  Then, I oversaw
the implementation and controlled that the customer connections and
dataflows were brought successfully into production.

1997-1999 - Siemens/SBS - Development/Partner Interface/Operations, EDI

My main work at SBS was in a team concerned with the ongoing care and
support of external EDI trading partners.  Every day we received many
error reports about erroneous EDI messages sent by the trading partners.
Only through extensive contact with the partners were we able to iron
out their problems.  We were also responsible for bringing new external
partners into the system and the entire teaching effort that involved.

An associated project was a BS-2000 and PC-based application to
transform indecipherable internal EDI-error reports for the external
trading partners into an understandable, actionable form.  The reports
were then sent automatically to the partners via e-mail.  To make
this workable, I also had to implement an extremely user-friendly
Windows GUI for the support personnel.

Related projects at SBS were concerned with DB data manipulations
to make EDI partner and message-type information useful for their
support personnel; data mining of sorts.

1994-1996 - Own Company, Development, C/Windows/DLL/Driver

For my own company I designed and developed a specialised, Windows-
based product, which enabled a simple, but generic, EDI-capability
for small customers of large distributors.  The development environment
consisted of Windows driver and DLL programming in C with Visual C++.

1992 - Large Bank, Interface Developer, Sybase/Informix/ESQL/C

For a software house (Siemens-Nixdorf) for a large bank (Dresdner),
I developed an ESQL/C emulation layer to implement a subset of the
Sybase ESQL/C interface on the basis of the Informix ESQL/C interface.
In doing so I configured and administered the necessary Sybase and
Informix servers.

1990-1992 - Bank Software House, DB-Developer/Admin, Sybase/ESQL/C

For a software house (Infosoft) who served several banks, I worked
in 1990 to 1992 as a database developer, programmer and administrator.
We designed and developed a dynamic-update API for inhouse-applications
using the Sybase-ESQL-C interface, stored procedures and triggers.  I
also installed and administered several Sybase databases on various
Unix PCs and for which I wrote an extensive set of administrative
software tools.

1985-1989 - Court Administration, Programmer/Analyst, Unify/C/Unix

In 1985 to 1989 I worked at the Federal Judicial Center in Washington
as a programmer/analyst.  We developed a system to modernise the
administration of cases for the federal appeals courts on the basis
of the Unify DB, C and various Unix platforms.  I learned a lot there
by doing some of everything, including application and database design,
implementation, testing, installation, data-conversion, optimisation
and application security.

1984 - NASA, Programmer, COBOL/MVS/JCL

A long, long time ago I was also a COBOL maintenance programmer
(IBM 370/MVS/JCL) at NASA.  As a summer intern during my university
years, I served as a programmer's assistant for the US Air Force.

* Where my work has been concentrated:
So far my work has generally been concerned with the manipulation of
current business data in databases; acceptance of such data from
external interfaces, storage of the data, transmission of the data
and analysis of the collected data.  Examples are trade data, prices,
orders, invoices and also standing data.

Usually my work takes place in the back-office and server areas,
although there have been exceptions.

* My work channel:
I work exclusively via my one-man GmbH-company, which can not be
named here.  I am the head of the company and sole owner, so there's
no danger of my being construed as a principal's pseudo-employee.