Mexico Before Industry 4.0: The JUBAP.net GEPLAN Suite Case
- Apr 12
- 4 min read
Updated: May 18
By the mid-2000s, Mexico was not yet speaking the language of “Industry 4.0,” but it was already building a meaningful software and industrial technology base. Official planning documents from the period described a national ICT market expected to grow by around 12%, with software forecast to grow faster, at about 19%, while the sector already employed more than 137,000 people. Mexico had launched PROSOFT in 2002 to strengthen the software industry, and by 2005 had formalized MoProSoft as a national process model for software development and maintenance. By 2006, PROSOFT was already supporting more than 330 projects and thousands of companies, most of them small and medium-sized firms.
This mattered because the country was not relying only on imported enterprise software. Mexico already had a real software ecosystem: large firms such as Softtek, Grupo Tress and Zentrum, but also hundreds of smaller firms building custom solutions for logistics, manufacturing, retail, transport, fuel distribution and industrial operations. States such as Nuevo León, Guadalajara, Monterrey and Baja California were becoming important technology clusters. The country was producing growing numbers of engineers and software developers, while also benefiting from proximity to the United States and the possibility of exporting software and IT services to North America.
It was also a particular moment socially. Before the worst years of the drug war and generalized insecurity, Mexico was seen by many international professionals as an attractive place to live and work remotely, even before the term “digital nomad” became common. Cities and regions such as Veracruz, Mérida, Guadalajara and Mexico City offered a combination of low cost of living, strong local talent, proximity to the United States and a relatively comfortable lifestyle for international freelancers and engineers.
That was also the case for the founders of JUBAP.net and The Integral Management Society SAS. After working in Europe, including at the Nokia R&D center in Barcelona, and spending time in the United States, they eventually established themselves in Veracruz, Mexico. From there, they built systems not only for PEMEX-related logistics, but also for Latin America and the United States, working with Mexican developers and specialists who had experience in medium and large systems for companies such as CSAV and other logistics-intensive organizations.
PEMEX itself was operating in a highly digital and operationally demanding environment. Its 2008 annual report describes telecom modernization, SCADA support, satellite communications, internal logistics and franchise monitoring systems, and even a NASA-supported GEO PEMEX 3D viewer for emergency response and operational maintenance. In the same period, Invensys opened a gas operations center in Reynosa to support PEMEX and described Burgos as the largest SCADA system installed by Invensys in Latin America. So the relevant context is not a “digitally empty” Mexico, but a large industrial landscape where major operators, vendors and local teams were all building serious control, monitoring and integration capabilities.
Within that landscape, the GEPLAN materials are significant because they show a Mexican-built suite that went far beyond a narrow logistics tool. The uploaded catalog presents GEPLAN as an integrated suite for logistics operators, workshops, warehouses, fleet companies and service stations, with modules for inventory and budgeting, vehicle maintenance, logistics planning, fuel-consumption control and volumetric management. It also describes integration into ERP-style environments, remote access, and an architecture based on Delphi, ASP.NET and MySQL.
One particularly notable example was GEPLAN/V, the volumetric control module for service stations. Even by current standards, it was a relatively advanced concept. It could read dispensers from multiple brands such as Wayne and Gilbarco, integrate tank telemetry, monitor opening events, pressure and fuel levels, connect to PEMEX for transport, loading and unloading monitoring, and integrate invoicing with PEMEX franchise workflows. It also supported POS, ticket printing, inventory control and complete service-station management. What made it distinctive was not that each feature was unique by itself, but that all of them were integrated into one practical environment almost two decades before industrial IoT became mainstream.
Another example was the private fleet-control environment developed around GEPLAN. Beyond standard GPS tracking, the platform connected transport companies, dispatch centers, workshops, maintenance, fuel control, drivers, inventory and operational reporting. The PEMEX/TETSA control-center document shows the same logic in live operation: Omnitracs satellite telemetry, data mining, artificial intelligence, alerts, reporting, electronic work orders, secure communications, evidence attachments, operational alerts and linkage to PEMEX estimation workflows. In other words, this was not just fleet monitoring. It was an early operational intelligence layer connecting field execution, communications, compliance and planning.
The broader Chicontepec program, of course, did not meet its original ambitions. The ASF’s 2010 performance audit describes Chicontepec as a strategic response to Cantarell’s decline, representing 40% of the country’s hydrocarbon reserves, with a plan based on drilling 16,000 development wells. The same audit explains that well productivity was very low, around 0.1 to 0.3 thousand barrels per day per well, and concluded that production targets were missed and that the productive return from 2002 to 2008 was only 2.5 centavos for every peso invested. That failure should be stated clearly. But it does not make the associated digital and operational systems irrelevant; if anything, it shows how ambitious the surrounding logistical and decision environment really was.
A fair international reading, then, is this: GEPLAN should not be presented as a unique global first, and it would be exaggerated to frame it that way. But it was also far from a trivial local tool. It was a technically serious, Mexican-built integration layer developed in an environment where the country already had growing software clusters, formal process models, large industrial telecom and SCADA deployments, and domestic firms capable of building custom systems for demanding corporate and industrial use cases. In that sense, GEPLAN belongs to the early wave of practical industrial digitalization in Latin America, before the later vocabulary of IIoT, control towers and Industry 4.0 made those architectures easier to describe.
Here you can explore some 2008 user manuals and JUBAP.net GEPLAN Suite Catalog
Comments