{"graphSha256":"f29d7b1eedeb88387238d2abda347f810d2179c5fdbead47c3ef48507ab20ca5","node":{"id":"N1263","type":"ficha","title":"JubAp.Net 2019 Suite: From Embedded Suites to Operational AI Integrity","url":"https://dakleyer.github.io/perspective-beyond/sources/jubap-net-2019-suite-from-embedded-suites-to-operational-ai-integrity-n1263/","original":"https://jubap.net/jubap-net-geplan-suite-from-embedded-suites-to-operational-ai-integrity/","aliases":[],"clusters":["net"],"tags":["cambio-regimen","empresa","experimentacion","integridad-ia","movilidad"],"summary":"","commit":null,"sourcePath":null,"commitUrl":null,"documentId":"doc-ba2a029a0dfb8d143c","tagWeights":{"cambio-regimen":0.1429,"empresa":0.2,"experimentacion":0.2,"integridad-ia":0.2571,"movilidad":0.2},"reading":"JubAp.Net, the organization behind the GEPLAN suite, is today a complex-systems intelligence centre focused on Operational AI Integrity and early-warning regime-change detection. Its origins lie in the early 2000s — in a Mexico that was not yet speaking the language of “Industry 4.0,” but was already building a serious software and industrial-technology base.\n\nBy 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 formalised 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.\n\nThis 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, producing growing numbers of engineers and software developers while benefiting from proximity to the United States.\n\nIt was also a particular moment socially. Before the worst years of the drug war and generalised 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. 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 who had experience in medium and large systems for companies such as CSAV and other logistics-intensive organisations.\n\nPEMEX itself was operating in a highly digital and operationally demanding environment. Its 2008 annual report describes telecom modernisation, 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 centre in Reynosa to support PEMEX and described Burgos as the largest SCADA system it had installed in Latin America. The relevant context is therefore 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.","readingSource":{"url":"https://jubap.net/jubap-net-geplan-suite-from-embedded-suites-to-operational-ai-integrity/","section":"Opening paragraphs","observed":"2026-11-04","sourceSha256":"60d17aae7b4c3b049918f170ff868cfa4e92d97d546949d2c18d3dd86848182d"},"readingSummary":"JubAp.Net, the organization behind the GEPLAN suite, is today a complex-systems intelligence centre focused on Operational AI Integrity and early-warning regime-change detection.","contextTokens":739},"relations":[["apoyo:N1263:C20","N1263","C20","documenta el concepto","",null,"apoyo",""],["apoyo:N1263:C49","N1263","C49","documenta el concepto","",null,"apoyo",""],["apoyo:N1263:C51","N1263","C51","documenta el concepto","",null,"apoyo",""],["apoyo:N1263:C52","N1263","C52","documenta el concepto","",null,"apoyo",""],["documento:M009","N1263","T897","analogy only","A multi-module suite and fragmented tools are different architectures; application count alone cannot establish capability fragmentation or coordination burden.",null,"documento","No se dispone aquí de una comparación causal de carga humana antes y después de GEPLAN."],["documento:A011","U1494","N1263","analogy only","The extensible onboard node and the later enterprise suite illustrate a shared architectural question: which investment can host additional capabilities without recreating the operating foundation?",null,"documento","Es comparación de decisiones de plataforma, no identidad de producto, código o cronología entre ambos casos."],["documento:G050","GH050","N1263","candidate transfer","A suite capability can be reused across domains while its decision boundary, new constraints and evidence obligations are re-established for each extension.",null,"documento","Aplicación metodológica posterior; los usos históricos de GEPLAN no constituyen pruebas de A25 ni heredan una garantía global."],["documento:R078","N864","N1263","editorial comparison","For a complementary reading, see [From GEPLAN to the enterprise suite](https://jubap.net/jubap-net-geplan-suite-from-embedded-suites-to-operational-ai-integrity/).",null,"documento",""],["documento:R083","N1263","N1265","editorial comparison","For a complementary reading, see [The pre-cloud engineering context](https://jubap.net/engineering-value-creation-before-the-cloud-jubap-nets-geplan-case-before-saas-and-iot-revolutions/).",null,"documento",""],["documento:R084","N1263","T874","editorial comparison","For a complementary reading, see [Human Intelligence Debt and the single-capture principle](https://tegrity.ai/human-intelligence-debt/).",null,"documento",""]]}