Olivier Martin

Temporary reinforcement of the development team to ensure the evolutionary maintenance of the Asset management tool dedicated to claims files.

Technical environment:

PHP 8.2 - Symfony 6, Api Platform

Missions:

TMA aimed at resolving bugs related to the migration of the Asset tool developed in Symfony 3 to version 6.

Ensure the smooth running of production deployments.

Development of a shared draft feature for comments between collaborators on the reminder screen.

Provision of a functionality allowing collaborators to filter entries in the claims file table on the reminder screen, by adding filtering fields to each column, taking into account the intervention lists associated with each claim. Filtering is performed entirely on the client side.

Allow sorting of columns in the claims file list on the reminder screen.

Evolution of the automatic assignment algorithm for incoming emails to claims files by cross-referencing data, including the integration of a mechanism to detect the insured's name, first name, and phone number within the messages. The first phase consisted exclusively of logging the results of these new rules to anticipate the volume of emails requiring manual processing in case of non-assignment to a claim. The second phase involved the effective production deployment of these rules, after a refinement and optimization phase.

Implementation of an email sending simulation form to configure the sender address, subject, and message content, in order to test the new incoming email assignment rules, precisely analyze the treatment applied to each message, and identify potential areas for improvement.

Code review

Writing technical documentation on Confluence

Implementation of unit tests

Migration of functionalities from Tanaris, a tool dedicated to managing claims for household appliances, to their existing solution following the acquisition of the ELECTROREN activity in May 2024 by DYNAREN. It was also necessary to adapt their Dynanet tool so that it could synchronize with the EDI Sinapps dedicated to ELECTROREN files.

Technical environment: PHP 8.2, 7.1, and 5.3, Symfony 3 & 6 Tools: Jira, Gitlab (Git flow workflow), Docker, Mutagen, Confluence

Missions:

- Make the Dynanet tool interoperable with a 2nd SINAPPS IDE dedicated to ELECTROREN files

- Modification of the Dynanet legacy and Symfony 6 tool to automate the retrieval of ELECTROREN files on Asset published by the principals on the dedicated SINAPPS account.

- Modification of the Dynanet legacy and Symfony 6 tool to automate the update of ELECTROREN files on SINAPPS when they are updated from the Asset management application by the business (work managers).

- Integration of the Météociel solution to determine the impact of lightning on the insured's location on the day of the incident

- Allow associating devices with an ELECTROREN file in order to: 1) Generate a PDF report listing the diagnostics of each device 2) Redesign and automate the entire ELECTROREN diagnostic process (generation of estimates, interventions, and invoices for clients and suppliers).

- Creation of an algorithm to calculate the rates to be charged to the end customer (the insurer / principal) based on the number of devices attached to the file and their category (brown, white, grey, or real estate) and the specific flat rates applicable to each insurer.

- Maintenance of the Asset tool which centralizes all DYNAREN and ELECTROREN claims files

- Writing technical documentation on Confluence and production deployment checklists

Team: 6 Fullstack Developers, agile operation

Groupe Revue Fiduciaire is a French publishing group specializing in taxation, human resources, payroll, assets, expert products, and related fields.

Mission Objectives:

The first phase of the mission consisted of optimizing the existing API for the Revue Fiduciaire's CAC e-learning platform, particularly regarding the caching strategy and response times, which were deemed too long. An API redesign was then carried out, along with the addition of new features.

The API then had to handle the delivery of educational content for the EC platform, where 80% of the business logic was managed by the front end. To illustrate the problem, the front end would retrieve the list of categories from Digischool's learning API, then the recorded times from the CAC API, and then reconstruct the hierarchy and aggregate the confirmed times for each category/subcategory.

Main features of the Learning API:

- Track training time to the second.

- Deliver educational content (lessons and quizzes) that GRF clients have access to.

Team:

3 Backend Developers, 4 Front-end Developers, agile operation