As I sat this morning watching the live feed of the oil unleashed by British Petroleum (BP) in the Gulf of Mexico, I wondered about the role of IP communications in the event. Certainly, the reason that I can see the oil gushing out of the earth is because of the Internet. Most of what I read about the tragedy comes via Internet news sites and other IP sources. But, what role on a daily basis does the technology play?
I would be surprised if smartphones were not in use by BP, its contractors, volunteers, state and local officials to schedule daily work activity, document where the oil is approaching shore or creating havoc with various wildlife. Moreover, given BP’s size and financial resources, I am certain that they employ Unified Communications to support their daily business practices and processes. They probably use Skype to make international calls between the US and the UK. They certainly will find it easier to use emails and IM to contact each other and provide updates as to their progress or lack thereof. And I am sure that when escalation is required, transitioning from an email to IM to VoIP is not uncommon.
The role of IP communications in this case is broad based. It is supporting the delivery of information to interested parties such as me. It is supporting the role of those responsible for the cleanup such as BP, its contractors and volunteers. Finally, it is supporting the financial needs of businesses and people who are facing closure and the loss of their jobs. Today, IP communications is applied in nearly every aspect of our lives.
As Broadvox and I push forward the concepts and value propositions associated with VoIP and SIP Trunking, I would be remiss if I did not remind all of you that we use this data-centric technology to accomplish an incredible number of tasks every day. Internet Protocol is not a solution but it enables numerous applications, services, products and processes. At some point, the final solution to shutting off the spill will probably be an action initiated by a command sent over using IP.
b7989d6d-38e2-4e4c-b9e5-f3dba77b71ea|0|.0