Before Digital Transformation Had a Name JUBAP.Net GEPLAN and the Hidden Logistics Lab Behind PEMEX

JUBAP.Net GEPLAN and the Hidden Logistics Lab Behind PEMEX Operations

When executives speak today about “digital transformation,” they usually refer to programs with formal roadmaps, dedicated offices, and carefully branded initiatives. In the late 2000s, the JUBAP.Net GEPLAN program around PEMEX and its transport contractor TETSA was something very different: a practical, field-driven, and quietly radical transformation that never used the term, yet achieved exactly what many programs still claim to pursue.

At the time, we operated as Corbera Networks, within the broader Integral Management lineage that later evolved into JUBAP.Net. The team engaged in a logistics and planning system for one of the most complex oil projects in Latin America, Chicontepec, where thousands of wells, irregular production, rugged terrain, and scattered communities made coordination extraordinarily difficult. Over time, it evolved into a proto-ERP with modules for logistics, fleet maintenance (CMMS), warehouse management, purchasing, finance, HR, and administration, becoming the digital backbone of transport operations serving PEMEX in central and northern Mexico.

This operational environment became an early example of Mission-Critical Infrastructure operating at industrial scale under highly fragmented field conditions.

From Firefighting IT to Structured Reengineering

In its early phase, the JUBAP.Net GEPLAN team spent most of its time putting out fires: solving urgent incidents, dealing with real and invented system errors, and facing any pretext that operators could find to disconnect the system. Behind many of those interruptions, they began to detect patterns: fuel theft from trucks, unregistered entries and exits from fluid plants, overweight trips, and “side” operations for third parties.

This led to a strategic insight: to make JUBAP.Net GEPLAN sustainable, it was not enough to improve the software. The operation itself had to be reengineered and fully standardized, so that processes were documented, auditable, and protected. Digitalization could not survive without governance.

What emerged was an early model of Enterprise Systems Integration, where software, field processes, logistics discipline, and governance became inseparable.

Hubs, ISO and Governance Before “Digital”

From that point, the program expanded beyond pure technology into an integrated organizational transformation. Multiple transport operations that previously functioned as independent, poorly coordinated units were unified into three logistics control centers, or hubs, where information flowed, orders were issued, and full traceability was ensured. These hubs became the visible face of a deeper redesign of roles, procedures, and decision flows.

In parallel, the team documented every job profile and procedure from scratch and adopted ISO 9001 as the backbone for standardizing the operation. The first certification had an immediate signaling effect: the news spread in the region, and more than twenty companies eventually requested similar services to formalize and improve their own processes. Later came ISO 14001 for environmental management and OHSAS 18001 for health and safety, consolidating a comprehensive governance framework around an operation that had previously been almost entirely analog.

External audits played a crucial role. Beyond checking compliance, auditors’ presence helped anchor discipline and seriousness in departments that had long functioned on unwritten habits and informal power structures. That cultural shift was what finally allowed JUBAP.Net GEPLAN to stop being “just an IT system” and become the axis of PEMEX’s logistics process in the region.

Designing for Non-Digital Users

One of the most striking aspects of the JUBAP.Net GEPLAN experience is that its users were not “digital natives” or early adopters. Many had almost no prior exposure to information systems and came from environments where Excel, if present, already represented a significant technological leap. This forced the design of ultra-intuitive interfaces, inspired in part by usability principles learned at Nokia but adapted to the local reality: large, clear, color-coded buttons, visual cues reminiscent of early Apple simplicity, and workflows aligned with how people actually worked in the field.

The environment was not only analog; it was politically and socially complex. Different departments, working cultures, organizational micro-powers, and high institutional pressure coexisted in the same ecosystem. System outputs were not harmless reports: they influenced payments, bonuses for hundreds of workers, and the viability of many contractors. In that context, any misinterpreted number could become a crisis.

To survive in this environment, the platform gradually evolved toward characteristics associated with resilient Mission-Critical Infrastructure, even though much of the surrounding ecosystem remained manual and paper-based.

A Hidden System-Country Interface

As the transformation advanced, JUBAP.Net GEPLAN began to play a role that went far beyond a vendor’s internal system. With just a few input data and specific algorithms, it was possible to infer critical information from other parts of the PEMEX system that were not yet digitalized: real-time production estimates for wells, tank volumes, and even maintenance conditions for valves, turbocompressors, or separation batteries. In practice, the system offered more visibility and reliability than the large army of supervisors traveling the fields in trucks taking notes by hand.

PEMEX started using JUBAP.Net GEPLAN’s reports as a reference source, even if integration remained almost comically manual: spreadsheets generated from JUBAP.Net GEPLAN were copied cell by cell into identical spreadsheets in other departments, sometimes passing through up to eleven areas where teams of clerks transcribed the same data without ever seeing the original system. Many of those people depended on JUBAP.Net GEPLAN without knowing it.

A Prototype for Operational AI Integrity

Looking back, GEPLAN can be seen as a laboratory of digital transformation before the label existed: a combination of reengineering, ISO-based standardization, logistics hubs, progressive digitalization, and interface design for non-digital users in a politically sensitive environment. It demonstrated that a critical system can function and endure in an analog, fragmented, and socially complex context if it is anchored in governance and real processes, not just technology.

For JUBAP.Net, that experience became the foundation of its current focus on Operational AI Integrity and early warning regime change detection. The same principles that once allowed a logistics system to infer hidden behaviors and resist sabotage now inform a broader mission: to design intelligent systems that understand how complex operations behave under pressure, not in theory, but in the real world.

Viewed today, the GEPLAN experience represents an early convergence of Enterprise Systems Integration, resilient Mission-Critical Infrastructure, and large-scale industrial coordination through JUBAP.Net GEPLAN inside one of the most difficult industrial environments in Latin America.