Vivensis: legacy system evolution and security for a field technical operation
Fteam supported Vivensis in maintaining and improving a legacy system, in the technical decisions needed to evolve the app used by field technicians during service calls and installations, and in a security consulting engagement focused on reducing fraud carried out with emulators.
Technology connected to the service and installation routine
Operations with technical teams in the field depend on applications capable of logging service calls, supporting installations, and connecting work done outside the office to the company’s systems.
When this technology grows on top of a legacy foundation, new needs must coexist with decisions accumulated over time.
The challenge becomes even greater when the operation also needs to distinguish legitimate behavior from fraud attempts.
How do you evolve a legacy system and respond to a fraud risk at the same time?
Vivensis had a technology already up and running and needed to keep evolving it without interrupting its operation.
Beyond maintenance and improvements, a specific security problem emerged: fake installations carried out using emulators capable of simulating the device’s location.
It was necessary to act on two different but connected dimensions: system continuity and greater reliability of the information used by the operation.
Maintenance, technical decisions, and security protocols
Fteam carried out maintenance of the legacy system and developed the improvements needed for the solution’s continuity.
It also supported the Vivensis team on technical decisions related to the evolution of the app used by technicians during service calls and installations.
On the security front, Fteam analyzed the scenario of fake installations carried out through emulators that simulated location and developed protocols to increase the operation’s protection.
A consulting engagement connected to execution
Legacy system
Maintenance and improvements on top of an existing technology.
App evolution
Support to the team on technical decisions for new needs of the field operation.
Fraud analysis
Understanding the behavior of emulators used to simulate legitimate conditions.
Security protocols
Creation of additional mechanisms to raise the operation’s reliability.
Technical continuity
Decisions oriented to preserve functioning while the product evolves.
More security without abandoning the existing technology
The case shows that modernizing and protecting a system doesn’t necessarily mean rebuilding everything from scratch.
Fteam worked on Vivensis’ existing reality, keeping the operation running, evolving the technology, and creating specific protocols for a risk identified in real-world use.
Technical consulting needs to understand the problem before prescribing the solution
In legacy systems, similar symptoms can have different causes. That’s why evolution and security decisions need to consider architecture, operations, and real user behavior.
Fteam can work alongside the internal team to analyze scenarios, guide decisions and, when needed, also take part in implementing the improvements.
When does this type of consulting make sense?
- When a legacy system needs to keep running while it is being improved.
- When the team faces difficult technical decisions and needs specialized support.
- When there is fraud or behavior that needs to be addressed at the technology layer.
- When the company needs to increase security without interrupting a critical operation.
Related skills and solutions
This case connects mainly to the following Fteam service areas:
Does your legacy system still support an important operation?
Fteam can analyze risks, support technical decisions, and structure improvements so the technology keeps running and evolving with more security.