Commentary

Mitch Irsfeld
 

Mobilization By The Dashboard Light

I was chatting today with Paul Fulton, CEO of Orative, a maker of enterprise mobile telephony software, and he said something that got me thinking once again about this whole notion of presence and the intersection of enterprise applications and mobile voice and messaging technology. Fulton mentioned the old separation-of-church-and-state that has kept mobile devices from truly integrating with enterprise communications and data systems: Consumers own the devices; carriers own the networks; and enterprises own the data. Now Orative and a handful of other vendors are starting to nibble away at that barrier without treading too heavily on the carriers' toes, and one suspects that the heavy shoes have yet to fall. Once they do, we'll notice a suspicious amount of Northwest soil stuck to the bottoms of those stompers, but that's another topic. What players like Orative have hit on is that employees are just consumers that go to work in the morning, and those cool little consumer handsets have the potential to deliver much more value if you could bolt their mobile capabilities to the enterprise voice and data applications that are housed behind the firewalls. They're right, and some of the presence capabilities they are already providing are delivering dividends in applications like field sales, investment banking and other professional services where immediate decisions are critical.

I was chatting today with Paul Fulton, CEO of Orative, a maker of enterprise mobile telephony software, and he said something that got me thinking once again about this whole notion of presence and the intersection of enterprise applications and mobile voice and messaging technology. Fulton mentioned the old separation-of-church-and-state that has kept mobile devices from truly integrating with enterprise communications and data systems: Consumers own the devices; carriers own the networks; and enterprises own the data.

Now Orative and a handful of other vendors are starting to nibble away at that barrier without treading too heavily on the carriers' toes, and one suspects that the heavy shoes have yet to fall. Once they do, we'll notice a suspicious amount of Northwest soil stuck to the bottoms of those stompers, but that's another topic.


More Telecom Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

What players like Orative have hit on is that employees are just consumers that go to work in the morning, and those cool little consumer handsets have the potential to deliver much more value if you could bolt their mobile capabilities to the enterprise voice and data applications that are housed behind the firewalls. They're right, and some of the presence capabilities they are already providing are delivering dividends in applications like field sales, investment banking and other professional services where immediate decisions are critical.But the opportunity runs much deeper, as our friends in Redmond are starting to show us. One area that intrigues me is the "dashboarding" of data, where we are able to filter out relevant information from many different applications and receive reports and alerts, monitor critical operations, and share the information with other stakeholders. These dashboard interfaces seem tailor-made for mobilization. And combining that with the presence capabilities that continue to evolve makes that a pretty powerful decision-making tool.

Now, whenever I mention these little what-if scenarios, I receive messages from companies claiming to have already accomplished whatever strange feat I've noodled over, and I welcome them because sometimes they are way ahead of me. So illuminate, who's doing something like this, and if not what will it take to get 'er done?


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links