{"id":644,"date":"2026-06-09T11:14:12","date_gmt":"2026-06-09T11:14:12","guid":{"rendered":"https:\/\/sinorfi.com\/cas-clients\/suez-archivage-ibm-maximo-ipop\/"},"modified":"2026-06-24T14:21:35","modified_gmt":"2026-06-24T14:21:35","slug":"suez-archivage-ibm-maximo-ipop","status":"publish","type":"cas_client","link":"https:\/\/sinorfi.com\/en\/cas-clients\/suez-archivage-ibm-maximo-ipop\/","title":{"rendered":"SUEZ SA \u2014 Automated IBM Maximo Work Order Archiving (IPOP project)"},"content":{"rendered":"
\"Architecture<\/figure>\n

An IBM Maximo system under data pressure<\/h2>\n

SUEZ SA, a global leader in water and environmental management, relies on IBM Maximo to manage all of its field operations under the IPOP project. After years of operation, the active database tables had accumulated millions of work orders with the \"Archived\" status.<\/p>\n

This gradual overload was degrading search response times, slowing down operational queries, and posing a growing risk to system stability. It had become essential to act \u2014 without sacrificing access to historical data.<\/p>\n

The challenge: archive without interruption, without data loss<\/h2>\n

Automatically move closed work orders to dedicated archive tables, while maintaining service continuity and the integrity of historical data.<\/p><\/blockquote>\n

    \n
  • Large volume of data spread across 6 linked tables (WORKORDER<\/code>, WOSTATUS<\/code>, LABTRANS<\/code>\u2026)<\/li>\n
  • Absolute service continuity \u2014 no network interruption tolerated<\/li>\n
  • Zero performance degradation of Maximo in production<\/li>\n
  • Full traceability and governance of archiving operations<\/li>\n<\/ul>\n

    Solution selection: comparison of the three approaches<\/h2>\n

    Sinorfi analysed three archiving architectures available in the IBM Maximo ecosystem before recommending the optimal solution.<\/p>\n

    \n\n\n\n\n\n\n\n\n\n
    Criterion<\/th>\nSolution 1 \u2014 Native Java<\/th>\nSolution 2 \u2014 Java + SQL<\/th>\nSolution 3 \u2014 Standalone SQL Job<\/th>\n<\/tr>\n<\/thead>\n
    Performance<\/td>\nSlow on large volumes<\/td>\nCorrect but limited execution<\/td>\n\u2713 Runs outside Maximo JVM \u2014 optimal on any volume<\/td>\n<\/tr>\n
    Network outage<\/td>\nProcessing interrupted<\/td>\nProcessing interrupted<\/td>\n\u2713 No impact \u2014 the SQL Job continues independently<\/td>\n<\/tr>\n
    Maximo resources<\/td>\nHigh Java consumption<\/td>\nHigh system utilization<\/td>\n\u2713 No allocation from Maximo<\/td>\n<\/tr>\n
    Application impact<\/td>\nRisk of crash<\/td>\nPossible slowdown<\/td>\n\u2713 No direct impact on Maximo<\/td>\n<\/tr>\n
    Stability<\/td>\nLess reliable<\/td>\nOverload risks<\/td>\n\u2713 Very reliable \u2014 standalone SQL processing<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

    Architecture: a Maximo-decoupled solution driven by SQL Job<\/h2>\n

    The solution is built on a dedicated SQL Server filegroup<\/strong> for archiving, physically separating historical data from active data. This decoupling ensures that no archiving operation consumes Maximo application resources.<\/p>\n

    A Maximo periodic task<\/strong> (INSTANCE) triggers the SQL Job according to the defined schedule. The Job then orchestrates the full cycle autonomously: copying to archive tables, deleting from active tables, and logging operations.<\/p>\n

    Mirror archive tables are synchronised in real time with the structure of the main tables. Any subsequently added attribute only requires a targeted update, ensuring the scalability of the solution.<\/p>\n

    Tech stack:<\/strong> IBM Maximo \u00b7 SQL Server Job \u00b7 Periodic Task \u00b7 Dedicated Filegroup \u00b7 Mirror Tables<\/p>\n

    Two archiving modes adapted to every need<\/h2>\n
      \n
    • 01 \u2014 Isolated Mode \u00b7 Single archiving<\/strong>Processing of an individual work order with all its linked sub-objects (statuses, labour, addresses\u2026). Ideal for targeted corrections and verifying a specific case before a bulk archiving run.<\/li>\n
    • 02 \u2014 Batch Mode \u00b7 Bulk archiving<\/strong>Grouped processing of a set of work orders according to configurable criteria (status, date, group). Designed for large-scale planned purges, maximising the efficiency of maintenance operations.<\/li>\n<\/ul>\n

      A management interface integrated into IBM Maximo<\/h2>\n

      Sinorfi developed and natively integrated into Maximo an application Archiving Configuration<\/strong>, accessible to MAXADMIN administrators, covering the entire lifecycle.<\/p>\n

        \n
      • <\/svg><\/span>Configuration<\/strong>Configuration of main tables, archive tables, archiving groups, execution conditions (Isolated \/ Batch) and associated child tables.<\/li>\n
      • <\/svg><\/span>Planification<\/strong>Scheduling of processing instances with choice of method, frequency and target group. View of the active schedule.<\/li>\n
      • <\/svg><\/span>Historique<\/strong>Full operation tracking: execution status, date, affected table, group, method used and detailed error messages.<\/li>\n
      • <\/svg><\/span>Statistics<\/strong>Visualisation of archived volume evolution by table and year, enabling capacity management and anticipation of future needs.<\/li>\n
      • <\/svg><\/span>Escalade<\/strong>Mechanism for escalating processing anomalies to alert technical teams in the event of a SQL Job failure.<\/li>\n
      • <\/svg><\/span>Liste des archives<\/strong>Centralised browsing of all available archives, with filters by object, period and group to quickly locate historical data.<\/li>\n<\/ul>\n

        Results: concrete, measurable benefits<\/h2>\n
          \n
        • Streamlined active database<\/strong> \u2014 Maximo operational tables now contain only live data. Searches and reports are significantly faster, with a direct reduction in load on the SQL Server engine.<\/li>\n
        • Full service continuity<\/strong> \u2014 Thanks to the standalone SQL Job architecture, archiving operations never impact Maximo users. No slowdown or application interruption has been observed in production.<\/li>\n
        • Preserved access to historical data<\/strong> \u2014 Dedicated archive tables maintain all historical data, accessible at any time from the Maximo interface with no reconstruction delay.<\/li>\n
        • Full governance and traceability<\/strong> \u2014 Every operation is logged: date, table, group, method, status. SUEZ teams have full visibility over the complete archiving history.<\/li>\n
        • Scalable and autonomous solution<\/strong> \u2014 The modular architecture allows archiving to be extended to new Maximo objects without redesign. Administrators manage everything from the native interface, with no dependency on Sinorfi for routine operations.<\/li>\n<\/ul>","protected":false},"excerpt":{"rendered":"

          SUEZ SA runs a high-volume IBM Maximo platform to manage its field operations. Faced with the accumulation of millions of closed work orders, Sinorfi designed and deployed an autonomous and resilient archiving solution, driven by SQL Server Jobs, with zero impact on production.<\/p>","protected":false},"featured_media":698,"template":"","meta":[],"class_list":["post-644","cas_client","type-cas_client","status-publish","has-post-thumbnail","hentry"],"_links":{"self":[{"href":"https:\/\/sinorfi.com\/en\/wp-json\/wp\/v2\/cas_client\/644","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sinorfi.com\/en\/wp-json\/wp\/v2\/cas_client"}],"about":[{"href":"https:\/\/sinorfi.com\/en\/wp-json\/wp\/v2\/types\/cas_client"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/sinorfi.com\/en\/wp-json\/wp\/v2\/media\/698"}],"wp:attachment":[{"href":"https:\/\/sinorfi.com\/en\/wp-json\/wp\/v2\/media?parent=644"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}