Brasil TecPar case banner
← Back to Cases
Brasil TecPar

Case: Brasil TecPar

Brasil TecPar is a Group whose purpose is to consolidate the Internet, Technology, and Telecommunications market in Brazil. As a result of more than two decades, Brasil TecPar brings connectivity to thousands of people across the most diverse regions and markets.

Come and see how we became part of this story of constant evolution through the words of Roberto Rosenfeld.

Brasil TecPar

We made years of progress in terms of technology. From the tools we adopted to the levels of layering and governance. The internal team even found new opportunities to enrich our data lake with external data.

Roberto Rosenfeld

Head of Systems

The project

Laying the foundations for digital transformation

First, we performed an assessment (a complete and comprehensive evaluation of the customer's technology landscape) covering different aspects related to data, infrastructure, governance, and the community involved. As the structure for these foundations, we used a few key points that can be considered in an assessment of this kind:

01

Project goals

We assessed whether the project goals were clearly defined and aligned with the needs of users and the broader community, taking into account the technical capability of the internal team.

02

Data quality

We worked with the customer to understand the quality of the data available in the project — verifying whether it was accurate, complete, current, and reliable — so we could identify potential data-quality issues and recommend improvements.

03

Infrastructure and technology

We performed a deep technology infrastructure analysis, including the data architecture, the tools used, and system scalability. We identified opportunities for infrastructure improvements to make it robust enough to handle large volumes of data and meet user needs.

04

Data governance

We analyzed how to implement data governance in the project. We checked for clear data management policies, decision-making processes, and defined responsibilities. We also assessed whether privacy and security guidelines were being followed appropriately.

05

Community and collaboration

From the start of the project, we had the participation and collaboration of the customer's technical community. Communication flowed efficiently; we ran discussion forums and provided support resources for the team. The technical team was actively involved in the development and continuous improvement of the project.

06

Documentation and resources

Starting at the assessment phase, we created clear and comprehensive documentation explaining how to use the data, the project's features, and best practices. We also evaluated whether additional resources existed, like tutorials, usage examples, and success stories.

07

Licensing and legality

We presented the customer with three different reference architectures for different scenarios and, based on the trade-offs, decided to go ahead with the data project using open-source tools that complied with applicable licenses and regulations.

08

Sustainability and continuity

The customer's internal community was very active throughout the project's execution, so the internal team was able to take on the project's long-term sustainment, ensuring the project can continue to evolve and support its users.

The partnership model we used was very satisfying. Initially we considered hiring a consultancy that would build the entire project — which would be expensive and wouldn't give the team room to grow. I see Datatchê as a company that allowed us to adapt a working model by bringing technical and architectural expertise that my team didn't have, so we could move past the starting point and build skills. It's great to be able to count on this kind of technical specialization without needing a large staffing engagement, simply with a focus on giving us direction in the architectural strategy.

Roberto Rosenfeld

Head of Systems

Strategy

Choosing an open-source environment

There are several reasons people and organizations choose open-source tools, and it's important to consider that selecting open-source tools also requires a careful evaluation to ensure they meet the specific requirements of your project or organization. Factors like support, documentation, project maturity, and compatibility with existing systems must be considered.

And the main points that led to this choice are strongly tied to:

01Freedom and transparency
02Customization and flexibility
03Active community and collaboration
04Cost and savings
05Security and reliability
06Innovation and rapid evolution
Impact

Benefits and partnership

One of the main goals we sought to achieve throughout the project was the creation of a reference architecture based on Data Lakehouse, providing a robust environment and a data governance structure — through which, by delivering value to the customer, we were able to understand how many end users (business) we impacted with the goals we achieved:

Our company has more than 2,000 employees and their goals are tied to the proper use of data.

Roberto Rosenfeld

Head of Systems

Based on all the value deliveries cited in this case, the customer was able to perform an internal evaluation that confirmed we had a strong impact not only for the business but also for the technical team.

Datatchê supported us on a strategic project for our operation: building a new data structure with more modern tools that could keep up with the data volume growth our organization is seeing. We cut our data lake build time in half even with the data growth that occurred in the period, and we now have higher velocity to generate new queries and views for the business area.

Roberto Rosenfeld

Head of Systems

screenshot.png
Roberto

Want results like these?

Talk to our specialists and find out how we can transform your data environment.

Talk to us
Talk to us!
WhatsAppChat on
WhatsApp