Project: ORBIT (phases 1 to 6). This project supports the bank’s Operational Risk Management process and the business brought in an external package to perform this. Phase 1 was implemented by the vendor (SAS) with no in-house technology involvement leading to (expensive) reliance upon third-party support. Later, in-house technical resources were brought in to take on that responsibility and to ensure an understanding for the current and subsequent releases until we finally migrated to a SaaS cloud-based solution in July’19.Technology: Solaris 10, Linux, Windows 64-bit, IIS, IHS, WebSphere (5.1, 6.1 7.0, 8.5), Korn-Shell scripting, Oracle 10/11, IBM RSA, ClearCase, GIT. And numerous background tools.Responsibilities: Take on the technical understanding of how the multi-tiered application is configured, assist in providing continuous support and help in handing that over to Live Support. Provide some of the tools/scripts to enable the application to deployed in multiple environments (some of which were shared). Coordinate the numerous teams involved in deployment and assist the vendor with their deployment issues. Document these processes. Research and document the countless errors we had: liaising with the vendor in their resolution; liaising with Incident Management; liaising with Live Support; etc.; whilst maintaining some ability to problem solve within a culture of partitioned responsibility. Provide support to the others and work with them to enhance the base product so that it would conform to the RBS model for application deployments. Assist in version control. Assisting testers by coordinating and performing the tasks required to reset the test system to a known, consistent state. Write the code to connect RBS sourced information to the cloud provider using a RestAPI, liaising with infrastructure teams to setup/use correct permissioning. Providing tools/data for the reconciliation team to validate the data transfer to the cloud SaaS.

Project: GRDW – Small Enhancements. The continuous project that maintains the banks current business position. It is used to prove the conformance to Basel IITechnology: Oracle, HP UNIX, Korn- & HP standard- Shell, ClearCase.Responsibilities: Maintain and develop the current code base with respect to any new business requests. Analyse any data changes that may be requested (down to data feeds and the downstream effects. Document all changes. Provide support to the business in our analysis role. Provide fast turn arounds,

Project: GRDW – Oracle 10g Migration. This was a cleaning up exercise having had third parties involved in the development.Technology: Oracle, HP UNIX, Korn- & HP standard- Shell, ClearCase.Responsibilities: Testing and modifying Oracle packages with the main emphasis on the speed aspect of the efficiency of the code. Lots of problems with the Oracle statistics. Testing of the Java front-end application. Ensuring that the sources were kept up-to-date in our source-control system (ClearCase) ready for deployment.

Project: UniVaR – Financial Markets VaR System. This is an ongoing project, responsible for maintaining and enhancing the banks’ Value at Risk system Technology: C/C++, SyBase, UNIX, Java, Struts, Spring, Hibernate, Korn- & C- Shell.Responsibilities: Initially I was to investigate and understand the complex C/C++ application that performed the VaR calculations in order to design / develop / test / implement / document the upcoming changes for the next enhancement. On completion, my role was to implement changes to the front-end (Java/Struts) application, giving the team an all-round developer I have written SyBase stored procedures and modified and created shell scripts (Korn- and C- shell) and it was also necessary to be able to understand some Perl.

Project: Basel II Wholesale Programme – Common Customer Identifier. Capture and maintain, through changes to Group Reference Database (GRD) intra-day, End of Day and Online processing, the new Legal Entity data-items and interfaces required by Basel II.Technology: C/C++, SyBase, UNIX, Java, Korn Shell.Responsibilities: My initial role was to investigate and understand the undocumented C/C++ front-end data entry application to the GRD with the explicit intent of modifying the application to handle new fields required by the Basel II Wholesale Programme. Above and beyond this I have expanded my domain to include the back-end stored procedures under SyBase sitting upon UNIX (both of which I’ve had to (re)learn).

Project: Sales & Account Opening – Project to give telephony call centres the ability to have a single customer view, recent history of customers’ requests and integrate sales opportunities.Technology: WebSphere, Java, XML, DHMTL, JavaScript, Chordiant.Responsibilities: As one of the build team I was involved with the code development as well as code validation of the Customer Sales Platform (CSP) application. I also had the responsibilities of unit and integration testing my developed components.As well as the above I was regularly involved in the areas of Problem Analysis and assisted with the Component Architecture & Design which included the development of the Graphical User Interface and the behind the scenes areas of XML Configuration and taskflow development.As with all of the tasks above I also created all the associated documentation

Project Team: Live Support – Provides 3rd level support for live applications.Technology: C/C++, SQL, VB, MS Access, FTP, Java.Responsibilities: I’ve had several roles within this team. I was instrumental in building new servers for the Traveller Project to be moved to Data Centre providing both for live and contingency cover. I’ve provided code level support (including VB, C/C++ and SQL); out-of-hours support; performed on-going maintenance functions on applications supported and taken on the role of support for other systems.

Project: Traveller – Provides the banking mechanism behind the provision of foreign currency and travellers cheques to bank customers.Technology: C/C++, SQL, VB, MS Access.Responsibilities: Provide the analysis, design and implementation for the outsourcing of the physical provision of foreign currency to customers as the only person remaining in the Bank with the appropriate knowledge.

Project Team: NatWest On-Line Banking – Project to upgrade the existing on-line banking demonstration application to include new features.Technology: JavaScript, DHTML, HTML.Responsibilities: The work here involved bringing a HTML demonstration version of the On-line Banking application into line with new enhancements and correcting old problems. This was performed using DHTML.

Project: Lucifer – Part of NatWest’s clearing system. Two Clearing Systems, using complex MS SQL (overnight batch and logon verification), had been running for 9 months, increasing the amount of data stored and getting progressively slower (15mins to 11hrs & 15sec to 15mins respectively).Technology: SQL.Responsibilities: To understand the (undocumented) complex SQL code and rewrite it to bring its performance back to the level of its original design and, if possible, better (which I succeeded in doing).

Project: Traveller – Provides the banking mechanism behind the provision of foreign currency and travellers cheques to bank customers.Technology: C/C++, SQL, VB.Responsibilities: I took over the responsibility for a C/C++ application that provided connectivity between the mainframe system and a MS SQL database. Initially I was involved in migrating undocumented mainframe functionality and I was later involved in several smaller developments using C/C++, VB and MS SQL. I also got involved in implementation and live support.

APPLICATION DEVELOPER. National Westminster Bank.Project: Managing Your Local Market – Project to update current portion of their website.Technology: HTTL, JavaScript.Responsibilities: Redevelop the current static website into something more dynamic.

Project: Transmission Decision Support System (TDSS) Technology: C/C++, SQL.Responsibilities: My roll was to develop a series of DLLs (in C/C++) that interfaced with a MS SQL database (using native C calls to DBLibrary) to perform various searches, housekeeping and daily download updates, alerting the ops people appropriately.

Project: An Image Viewer for Scanned Documents. Rewrite an existing DOS/ WINDOWS application to take full advantage of WINDOWS and a new version of the HyperFax III API. The final product required was a DLL that could be called from within a VB Document Imaging and Storage System.

Project: GCSE tutoring and information system. Design and implementation of a DMBS system suitable for storing examination questions an model answers (including images). Design and implementation of the front-end interface (using VB) and a real-time animator that used both sound and graphical imagery (using VC) all running on WINDOWS 3.1X technology.

Project: Integrate HyperFax III file format reader into a German OCR product. This company had an OCR product that they wished to integrate with a better graphics package for scanning their images

Project: Database Management System. Design and implement (in FoxProW for Windows 2•5a) a Database Management System for the control of Information Technology solutions sold to clients.

Project: Tag Image File Format (TIFF) viewer. Design and implement (in Microsoft* C/C++ 7.00) a utility to display either the complete or a portion of a graphical image stored in the Tag Image File Format (TIFF). This involved the decoding of TIFF files and a visual compression technique to condense a large image in order to display it on a VGA/SVGA monitor. This condensing mechanism I had to design.