Solution
The main objective of the project, in addition to regulatory compliance, was to keep the integration interface of the New MiFID Engine in line with that of the Old Engine as much as possible, with the aim of inducing the least possible impact on all the Bank's systems integrated with it and guaranteeing a non-regression test phase on device processes that was as secure and robust as possible.
To achieve this purpose, Technology Reply took care of the implementation aspects of a back-end business service (realised through J2EE, EJB, Oracle Database, Oracle OSB 12c and JMS code technologies), invoked by all the Bank's channels, which was entrusted with the task of enriching the input received with all the information necessary for the new suitability model (thus bridging the gap with the old model), which was ultimately realised through the integration of market-leading third-part solutions. This enrichment concerned the client's personal details, the relative Personal Profile derived from the completion of the MiFID questionnaire, the portfolio and the financial instruments handled with relative management costs (entry, exit and running costs).
Furthermore, this back-end service also implemented a mechanism for managing error messages in the event of a negative outcome of MiFID checks that is fully configurable, scalable and modifiable without the need for application releases, so as to normalize the messaging displayed to the end customer and centralize its management.
Lastly, Technology Reply also dealt with the implementation of all the components that carry out the periodic massive MiFID audit performed on all the Bank's clients to verify the suitability of their consolidated portfolios and produce, quarterly, half-yearly and yearly, the statements and reports required by the current European MiFID II regulations.
The project lasted about two years, and since this MiFID engine is core and invoked for every transaction executed by the Bank's customers from any channel, the related ROLLOUT in Production phase initially involved a small subset of the Bank's end customers, which gradually increased until it was opened to the entire customer base, in compliance with the timeframe shared with CONSOB for the adaptation of its suitability model to the European MiFID II regulation.
Moreover, the progressive rollout of the initiative was organized in the following 3 phases (managed through a customer-side profiling mechanism on the back-end services side):
- The first phase in which the invocation to the new suitability verification service was redirected to the old MiFID engine, returning the relevant outcome, so as to verify the correct integration of all channels with respect to the new service interface in terms of request and response.
- The second phase in which the call to the new suitability verification service was redirected to the old MiFID engine, returning the relative result, and in parallel and in asynchronous mode, by means of a JMS queuing mechanism, the suitability verification operation was also submitted to the New MiFID Engine, so that, by means of extractions of the respective databases, business users could compare the checks performed and the relative results of the two engines to verify and adapt the metrics of the New MiFID Engine.
- The third phase in which the call to the new suitability verification service was redirected directly to the New MiFID Engine, returning the relevant outcome (pilot phase).