Seamless OBM ServiceNow Integration at ANZ: A ZigiOps Case Study

What Is OBM-ServiceNow Integration?

OBM-ServiceNow integration connects Operations Bridge Manager, a real-time IT event monitoring platform, with ServiceNow's ITSM incident management system, so that events detected in one platform automatically create and update records in the other. Done well, it eliminates the manual handoffs between NOC teams and service desks, replacing them with a continuous, bi-directional feedback loop between monitoring and service management.

This is the exact gap ANZ Banking Group needed closed, and the case study below walks through how they closed it.

Modern Financial Operations Require Seamless IT Synchronization

In the digital-first banking environment, robust IT operations are critical to delivering secure, uninterrupted financial services. For ANZ Banking Group Ltd, a leading financial institution with global operations, this means ensuring full alignment between monitoring systems and service management tools.

Prior to adopting ZigiOps, ANZ faced significant challenges coordinating incident lifecycles across Operations Bridge Manager (OBM) and ServiceNow. Fragmented monitoring and ITSM toolchains are a well-documented cause of extended mean time to repair (MTTR) in enterprise environments [CITATION NEEDED: confirm the specific Gartner report this references before publishing]. The manual and semi-automated processes ANZ had in place introduced inefficiencies and blind spots that directly impacted IT responsiveness. ZigiOps provided the intelligent, bi-directional integration needed to close these gaps and enhance operational agility.

Customer Overview

ANZ Banking Group Ltd (ANZ) is one of the largest banks in the Asia-Pacific region. With operations in over 30 markets, ANZ provides banking, investment, and financial services to millions of customers worldwide. Its infrastructure supports a vast digital banking ecosystem with strict compliance and service level expectations.

Business Environment

• Global banking operations with high transaction volumes and 24/7 uptime requirements

• Complex infrastructure with thousands of interconnected systems and services

• Centralized IT Operations team overseeing incident detection and resolution across diverse platforms

Technology Stack

The Problem: Fragmented Incident Workflows and Manual Event Processing

While ANZ leveraged both OBM and ServiceNow effectively in isolation, the lack of deep, automated integration between the two systems created real operational pain. Incidents were detected in OBM but had to travel through human hands before reaching ServiceNow, introducing delays and inconsistency at every step.

Key Challenges

• Manual Ticketing: OBM events were manually or rule-based forwarded to ServiceNow, leading to delays and inconsistent incident creation.

• One-Way Communication: Once an incident was created in ServiceNow, updates were not reflected back in OBM, breaking the visibility loop for NOC teams.

• Limited Automation Logic: ServiceNow logic transformed OBM-generated incidents into alerts, but without proper synchronization back, critical context was lost.

• Duplicate and Disjointed Records: Without a reliable correlation key, incident updates and OBM events often existed as disconnected entries across systems.

Integration Pain Points and Attempted Workarounds

ANZ explored initial solutions through custom scripts and basic API connections. However, these faced common technical hurdles:

• Lack of Retry Logic: Scripts failed silently, and error handling was minimal.

• Incompatible Data Models: OBM's complex, nested event data did not map cleanly to ServiceNow's incident format.

• No Bi-Directional Sync: Changes in ServiceNow (state updates, comments) were never pushed back to OBM, leaving operators uninformed.

• High Operational Overhead: Maintaining scripts and middleware required constant effort and troubleshooting, a hidden cost that adds up fast.

This is a pattern ZigiWave sees frequently across enterprise environments. If you recognize it in your own stack, see how ZigiOps solves OBM-ServiceNow integrations or explore the full ZigiOps integration library.

The ZigiOps Solution: Intelligent, Bi-Directional Integration

ANZ selected ZigiOps for its enterprise-grade capabilities tailored for OBM to ServiceNow integration. ZigiOps enabled a fully automated and reliable two-way synchronization process with minimal configuration effort, no developers required.

ANZ selected ZigiOps for its enterprise-grade capabilities tailored for OBM to ServiceNow integration. ZigiOps enabled a fully automated and reliable two-way synchronization process with minimal configuration effort, no developers required.

ZigiOps Key Differentiators

• 100% Code-Free: The entire integration is configured through ZigiOps' guided UI, no scripting, no middleware, no custom code.

• No Data Storage: ZigiOps transfers data between systems without ever storing it, keeping ANZ's sensitive incident data fully within its own infrastructure.

• ISO 27001 Certified: Enterprise-grade security compliance, meeting the strict standards expected in financial services environments.

• Out-of-the-Box OBM and ServiceNow Support: Pre-built integration templates enable quick deployment without starting from scratch.

• CLIP-Based Bi-Directional Synchronization: Events and incidents remain in sync in real time across both platforms.

• Support for ServiceNow Alert Logic: Seamlessly transforms incoming OBM events into Alerts, then Incidents, while maintaining backsync integrity.

• Custom Correlation Logic: Ensures every OBM event remains tied to its corresponding ServiceNow incident for full lifecycle tracking.

• Unlimited Transactions: No caps on the number of events or incidents processed, supporting ANZ's high-volume operational environment.

• Standalone Application: ZigiOps is not a plugin or add-on. It operates as an independent platform, avoiding version dependency conflicts with either system.

• High Availability Architecture: Built for enterprise resilience and scalability from day one.

For technical teams evaluating this integration, ServiceNow's official OBM connector documentation provides helpful context on how the platform handles incoming event data and alert promotion workflows, and OpenText's Operations Bridge Integration for ServiceNow overview describes the native connector ZigiOps was chosen to replace.

Native OBM-ServiceNow Connector vs. ZigiOps

For teams evaluating their options, here is how the native connector approach compares to ZigiOps on the criteria that mattered most to ANZ:

Use Case in Detail: OBM to ServiceNow Integration Flow

Modern IT operations require seamless communication between monitoring tools and ITSM platforms to ensure rapid response to incidents, efficient root cause analysis, and improved service reliability. The ANZ integration consists of two core workflows that together create a continuous, automated feedback loop.

Workflow 1: OBM to ServiceNow — Event Detection and Incident Creation

This workflow captures new events from OBM and automatically opens the corresponding ServiceNow incident, populated with severity, CI, and metadata, with no manual triage step.

Workflow 2: ServiceNow to OBM — Bi-Directional Backsync

The second workflow ensures that changes made in ServiceNow are reflected back in OBM, maintaining alignment between monitoring and service management:

• Update monitoring: Continuously monitors ServiceNow for changes to existing incidents, status updates, reassignments, and resolution notes, so NOC teams always see the current incident state without leaving OBM.

• Lifecycle state sync: Pushes incident state changes back to OBM (Acknowledged, In Progress, Closed), keeping OBM events aligned with the incident's real-world progress.

• Custom attribute mapping: Attaches the ServiceNow Incident ID to the originating OBM event, providing a clear, persistent reference linking every event to its incident.

• Event comment sync: Appends ServiceNow notes and updates as comments on the OBM event, for full traceability and operational visibility without platform switching.

• Custom key synchronization: Uses a dedicated correlation field to reliably link OBM events to ServiceNow incidents, preventing duplicate records and ensuring no incident is orphaned between systems.

Before and After ZigiOps

Results and Business Benefits

Results at a Glance

Operational Impact

• Streamlined Workflows: Incident creation and updates are now fully automated, reducing manual intervention to near zero.

• Real-Time Feedback: NOC teams gain full visibility into incident progress directly within OBM, without toggling between tools.

• Improved MTTR: Quicker detection-to-resolution cycles thanks to synchronized, always-current incident data across both systems.

Who This Case Study Is For

This deployment pattern applies most directly to IT Operations and NOC teams running OBM alongside ServiceNow ITSM in regulated, high-volume environments, banking and financial services, insurance, and other sectors where audit traceability and data residency are non-negotiable. Service Managers and ITOM Engineers evaluating a replacement for fragile custom scripts will recognize the same before-state ANZ described.

Conclusion

The ANZ ServiceNow OBM integration is a textbook example of what bi-directional, enterprise-grade integration can achieve when it replaces fragile scripts and manual processes. By deploying ZigiOps, ANZ Banking Group transformed its incident management workflow from a reactive, siloed operation into a synchronized, always-current feedback loop between monitoring and service management.

The result: fewer manual handoffs, faster resolution cycles, full audit traceability, and an integration architecture that scales with the bank's operations, not against them.

ZigiOps delivered this outcome with zero custom code, no stored data, and full ISO 27001-compliant security. For operations teams still wrestling with disconnected OBM and ServiceNow environments, the path forward is clear.

Learn more about ZigiOps OBM-ServiceNow integrations and how other enterprise teams have solved the same challenge.