Service Manager > OMi. When you create a downtime RFC (request for change) in Service Manager, the RFC includes the CI that is under change and a start and end date/time of the downtime. If you do not want to waste effort with false alarms in your operations center, and do not want to have these times included in service availability reports, you can set up the integration so that these RFCs are translated to downtimes in OMi.
In this scenario, you install and set up a downtime adapter on your CMDB (whether you are working with a UCMDB, central CMS, or with RTSM). The RFC creates a planned downtime CI in the CMDB, and the adapter sends the planned downtime CI to OMi to create a downtime.
OMi > Service Manager. When you define downtimes using OMi (for example, every Monday and Saturday from 8:30 PM-9:30 PM), in order to proactively support end users, the help desk should be aware of such operational downtimes. After you set up the integration, downtimes in OMi trigger events that create corresponding incidents in Service Manager.
In this scenario, when a downtime starts, OMi generates an event. Using the event forwarding mechanism, the event generates an incident in Service Manager. When the downtime ends, an event is sent to close the downtime incident.
|Operations Bridge Manager (OMi)|