I get many questions about the usage, pervasiveness, and adaption of mobile BI applications. What's a mobile BI application? Beyond a simple delivery of alerts, URLs, or actual reports via email - functionality that has existed for years - here are a few newer approaches to deliver BI on a mobile device:
The no brainer. In theory any mobile device equipped with a browser can access web based, thin client, HTML only BI applications. Yes, these BI apps will be mostly static, not interactive reports and dashboards. Navigation (scrolling, zooming, etc) will be quite awkward. But, this approach indeed requires no additional effort to deploy.
Customization. The next step up is to render each (or all) reports and dashboards to a format suitable to any mobile device in terms of screen size, usage of screen real estate, and mobile device specific navigation instrumentation. A variation of this approach is to create device specific navigation controls (thumb wheel or thumb button for Blackberries, up/down/left/right arrows for Palms, gestural manipulation for iPhone, etc). This obviously requires more development effort, but still no additional software.
Our latest featured podcast is Bill Band's "The Top 19 Customer Management Technologies To Watch".
In this podcast, BP&A Vice President and Principal Analyst Bill Band describes what technologies comprise the customer management applications ecosystem, and which ones offer the most value based on Forrester’s most recent research.
We look forward to your questions and comments.
Subscribe to Business Process & Applications podcasts through iTunes.
I'd like to drill into some more details on my BI SaaS blog from September 2009. A key critical point to "what differentiates one BI SaaS vendor from another" discussion is what really constitutes multi-tenant architecture. Here are some initiall thoughts to stimulate the discussion:
DBMS. There's got to be back end, DBMS architecture that allows for one of the following:
Automatically generate a separate DBMS instance for each client
Use same DBMS instance for multiple clients, but automatically generate a set of unique tables for each client
Use same DBMS instance and tables for multiple clients, but automatically assign unique keys to to each client so that they can only update and retrieve their own rows
Application. Similar functionality has to exist in the application tier:
Automatically connect to the appropriate, client specific DBMS instance, or
Automatically use views that only point to client specific tables, or
Append "where" clause to each SQL statement to only retrieve client specific rows
past Tuesday Autodesk conducted its annual Manufacturing Analyst Day event in
Lake Oswego, Oregon, and I had the opportunity to catch up with executive
leaders across the company’s spectrum of product brands (i.e. Alias for
conceptual design, AutoCAD and Inventor for engineering design, and, more
recent acquisition additions, MoldFlow and Algor for simulation). Contrary to
my original perception that Autodesk offers affordable, no-frills product design
tools to lots of smaller, mom-and-pop companies, I learned that their business
is significantly shifting to include more direct sales to large,
enterprise-level manufacturers like Intel, Nestle, and Parker Hannifin. In
fact, approximately a quarter of Autodesk’s manufacturing business now comes from
customers with over $2 billion in annual revenues, and it’s their fastest
growing segment within this vertical.