{"graphSha256":"f29d7b1eedeb88387238d2abda347f810d2179c5fdbead47c3ef48507ab20ca5","node":{"id":"N1267","type":"ficha","title":"JubAp.Net Distributed Tiger Team Model – origins –","url":"https://dakleyer.github.io/perspective-beyond/sources/jubap-net-distributed-tiger-team-model-origins-n1267/","original":"https://jubap.net/jubap-net-distributed-tiger-team-model-origins/","aliases":[],"clusters":["net"],"tags":["decision","empresa","experimentacion","memoria-territorio","transformacion"],"summary":"","commit":null,"sourcePath":null,"commitUrl":null,"documentId":"doc-253ed7736f47ec1d73","tagWeights":{"decision":0.2593,"empresa":0.2592,"experimentacion":0.1852,"memoria-territorio":0.0741,"transformacion":0.2222},"reading":"The GEPLAN record supplies an early setting for the distributed engineering lineage. Identify how field observations reached design decisions and how those decisions returned to operation. Preserve the tools, constraints and responsibility arrangements of the period rather than explaining them only through later remote-work terminology.\n\nThe GEPLAN lineage shows how distributed engineering, field proximity and operational intelligence were combined before Industry 4.0 became mainstream language. The model emerged from practice rather than retrospective branding.\n\nWhen the JubAp.Net GEPLAN suite was developed between 2002 and 2008, terms such as Industry 4.0, Industrial IoT, digital twins and operational AI had not yet entered mainstream business language.\n\nYet Mexico already possessed many of the core ingredients needed to build advanced industrial software systems — and a small group of field-embedded engineers, architects and operators was quietly assembling them into something that would anticipate those concepts by nearly a decade.\n\nThe organization behind GEPLAN, JubAp.Net, is today a complex systems intelligence center specialized in Operational AI Integrity. At the time, it operated through two entities: The Integral Management Society in the United States and Corbera Networks in Mexico.","readingSource":{"url":"https://jubap.net/jubap-net-distributed-tiger-team-model-origins/","section":"Opening paragraphs","observed":"2026-11-04","sourceSha256":"2059b99588230f1d2e8e77f47a0e9923f3ca65268b2577aeb25c2e9f7f76581b"},"readingSummary":"The GEPLAN record supplies an early setting for the distributed engineering lineage.","contextTokens":342},"relations":[["apoyo:N1267:C10","N1267","C10","documenta el concepto","",null,"apoyo",""],["apoyo:N1267:C79","N1267","C79","documenta el concepto","",null,"apoyo",""],["apoyo:N1267:G25","N1267","G25","documenta el concepto","",null,"apoyo",""],["apoyo:N1267:G41","N1267","G41","documenta el concepto","",null,"apoyo",""],["documento:F052","N1267","T1484","analogy only","Embedded field architecture can shorten corrective feedback between the operational flow and the representation used to change it.",null,"documento","La presencia en campo no da observabilidad total ni demuestra por sí sola causalidad o eliminación de fricción."],["documento:R082","N1258","N1267","editorial comparison","For a complementary reading, see [The field origins of the Tiger Team model](https://jubap.net/jubap-net-distributed-tiger-team-model-origins/).",null,"documento",""],["documento:R123","N1261","N1267","editorial comparison","For a complementary reading, see [The field-embedded origins of the model](https://jubap.net/jubap-net-distributed-tiger-team-model-origins/).",null,"documento",""],["documento:R124","N1267","N1295","editorial comparison","For a complementary reading, see [The consolidated Tiger Team operating model](https://jubap.net/jupap-net-tiger-team-model/).",null,"documento",""]]}