Code review and production deployment of Visual Time for Orígenes Seguros

Visual Time is the core system where Orígenes Seguros holds its products, policies and issuance. A solution had been built on top of it, and the company was about to rest its digital operation on it.

Leaning on a solution nobody has verified is making a decision on an assumption: it works until you have to change it, and that is when whatever was never examined shows up.

And there was a second question underneath, the one that matters long term.

• Unknown code state: nobody had reviewed how the thing meant to carry sales was built.
• Outdated database: without bringing it to its latest version, any evolution drags the problem along.
• Deployment dependency: if the IT team cannot build and install on its own, every change depends on a third party.

For an insurer that last point is not convenience: it is being able to respond when the business asks.

We ran a bounded 120 hour solution architect engagement with a double goal: know what state it was in, and leave the client able to run it alone.

It was executed in May 2020, coordinated by a technical lead.

Reviewing the real state

• Review of the Visual Time solution code and detection of coding issues.
• Technical recommendations report for the evolution of the solution.

Production deployment on their own infrastructure

• Application deployed on the Orígenes servers, not a vendor's.
• Database brought up to its latest version.

Autonomy, the underlying deliverable

• Step by step documentation to compile the solution and deploy it on the client infrastructure.
• The IT team is left able to redeploy without depending on third parties.
• It is the deliverable that outlives the project: reviewed code ages, the ability to deploy it does not.

Architecture and technology

• Solution on Visual Time, installed on the insurer own servers.
• Bounded engagement in hours, with scope defined upfront and documentary deliverables.
• A solution architect on the technical assessment, coordinated by a technical lead.
• Deliverables: recommendations report, deployed application and build documentation.

Learn more about software development.

The company stopped relying on an assumption and came to know the state of what carries its operation.

Starting point

• Unreviewed solution, about to carry digital sales.
• Database behind its latest version.
• No documentation to build or deploy from the internal team.

Results

• Full code review in 120 hours, in May 2020.
• Application deployed on the client own servers.
• Database updated to its latest version.
• Build and deployment documentation handed to the IT team.

Strategic impact

• The recommendations report turns the review into a plan rather than a standalone diagnosis.
• Building and deploying stop depending on a third party, which is what allows responding when the business asks.