In my previous post I introduced the concept of Customer Power Outages and, at a high level, introduced how Outage Management Systems work. The key take away from that blog post is that important, event driven data is passing through BizTalk and there is an opportunity use this information to provide better Customer and Employee engagement through Service Bus Notification Hubs. Think about, conceptually how different is it from BAM Alerts? The idea behind BAM Alerts is data is moving through BizTalk, Tracking Profiles pick it up and send it to subscribers who are interested in it via email (oversimplified…I know). The process of collecting this information for Notification Hubs is different but now we can reach an audience that we may never had access to before.
In this post we will take a closer look into how we could actually implement a Power Outage system and include notifications to both customers and employees by using Service Bus Notification Hubs.
Note: In some areas I have over-simplified the process in order to focus on some of the key technical aspects of Notification Hubs.
In the diagram below I have laid out the series of events that make up the architecture:
Conclusion Hopefully this post has described in more detail how Service Bus Notifications can improve customer and employee engagement. I promise that the next post in the series will have some code. I just felt that if I could build a story, it would provide some worthwhile context that truly demonstrates why this Notification Hub technology is important.