During customer migrations from IBM Netcool to IBM Concert Operate, one of the most frequently identified functional gaps is the absence of native Maintenance Window Management.
In traditional Netcool environments, planned maintenance activities could be centrally managed, allowing operations teams to prevent expected alerts from generating operational noise while maintaining full visibility and traceability of the maintenance activity.
Today, organizations adopting Concert Operate must implement custom integrations or configure maintenance independently in each monitoring tool, increasing operational complexity and reducing governance.
Current Situation
IBM Concert Operate receives events from multiple observability platforms and applies AI-driven correlation and incident analysis. However, it currently does not provide a centralized mechanism to determine whether an incoming event belongs to an approved maintenance window before it is processed.
As a result:
- Planned maintenance events generate unnecessary operational noise.
- AI correlation processes analyze events that are expected and non-actionable.
- NOC operators spend time reviewing alerts that should have been automatically identified as maintenance-related.
- Each monitoring platform must implement its own maintenance logic, creating inconsistent operational behavior across the enterprise.
Proposed Enhancement
Introduce a native Maintenance Window Management capability within IBM Concert Operate that allows customers to centrally define and manage maintenance schedules independently of the monitoring source.
The capability should support:
- One-time and recurring maintenance windows.
- Maintenance calendars.
- Association by:
- Application
- Business Service
- Configuration Item (CI)
- Resource
- Tags
- Topology groups
- API-based management.
- Integration with Change Management platforms (IBM Maximo, ServiceNow, etc.).
- Role-based administration.
- Audit trail of all maintenance activities.
Event Processing Actions
When a maintenance window is active, administrators should be able to configure the desired behavior for matching events, including:
- Suppress event processing.
- Mark events as "Under Maintenance".
- Lower event severity.
- Exclude events from AI correlation.
- Prevent incident creation.
- Prevent notification generation.
- Store events for historical analysis without operational impact.
These actions should be configurable through policies, allowing organizations to adapt the behavior to their operational model.
Benefits
Adding this capability would provide significant operational and business value:
Operational Benefits
- Centralized maintenance administration.
- Significant reduction of alert noise.
- Higher accuracy in AI correlation and root cause analysis.
- Reduced operator workload.
- Consistent behavior across all monitoring technologies.
Business Benefits
- Simplifies migration from IBM Netcool environments.
- Eliminates the need for custom developments.
- Improves governance of planned changes.
- Increases customer adoption of IBM Concert Operate.
- Reduces implementation time and operational costs.
Architectural Alignment
Unlike the Netcool implementation, this capability does not require an ObjectServer or IBM Netcool Impact.
Instead, the maintenance evaluation could be integrated into the Concert Operate event ingestion and policy engine, leveraging the platform's existing capabilities, including:
- Topology model.
- Configuration Items (CIs).
- Business Services.
- Labels and metadata.
- Event enrichment.
- AI processing pipeline.
This approach aligns with the cloud-native architecture of Concert Operate while delivering functionality that enterprise customers consider essential for day-to-day operations.
Customer Impact
This enhancement is particularly valuable for customers operating:
- Enterprise NOCs
- Financial institutions
- Telecommunications providers
- Managed Service Providers (MSPs)
- Critical infrastructure environments
where thousands of alerts may be generated during planned maintenance activities.
Reference
IBM Netcool Impact previously provided this capability through Maintenance Window Management (MWM) integrated with the ObjectServer.
IBM Documentation:
https://www.ibm.com/docs/en/tivoli-netcoolimpact/7.1.1?topic=solutions-configuring-maintenance-window-management
This enhancement would modernize that capability within the cloud-native architecture of IBM Concert Operate, providing equivalent operational value without relying on legacy Netcool components.
