Scorecard Marketplace – A Reference Model to Deliver Dashboards on Tablets
Using this model, scorecards are easily published and subscribed to by enterprise users, partners and business divisions
Aug. 11, 2013 01:21 PM
Business always needs the ability to deliver real-time analytics on-demand for better information visibility and decision making anytime anywhere. Delivering dashboards on mobile devices or tablets has become a very popular use case for executives. The use case has more relevancy now than ever with Bring Your Own Device (BYOD) gaining momentum across organizations.
Organizations around the world are realizing that the need for a full spectrum of dashboards on mobiles is challenging. Especially in utilizing existing investment, providing rich user experience, and simplifying mobile enablement. This article details a reference model, i.e., Scorecard Marketplace, which is useful for pushing the existing reports and analytics to mobiles and tablets with minimal extension by addressing the above challenges. The model uses the popular Marketplace concept and can be published internally to the organization (on-premise) or it can sit on (public) cloud.
Most of the big players and ISVs provide end-to-end enterprise solutions for scorecards by covering these major activities, but they have yet to:
This need within enterprises has led us to the idea of a Scorecard Marketplace, which really simplifies and expedites mobile enablement and provides a very rich user experience.
Scorecard Marketplace: a marketplace for digital scorecards
Easy to adopt
Data Anytime, Anywhere, on Any Device
Native/Rich User Experience
In a nutshell, the Scorecard Marketplace simplifies the Business Intelligence work within enterprises and enables these scorecards on mobile devices and tablets with minimal extension work.
Platform typically does the heavy lifting needed for a marketplace including data handling and security. It mainly exposes standardized Publishing and Subscribing interfaces to the external world. This can be hosted either on premise within an enterprise or on a public cloud.
Enterprise systems publish scorecards to a marketplace via the platform publishing interface. (Details below)
Enterprise users subscribe to authorized scorecards by directly consuming a Subscribing interface into their own applications or via a readily available Dashboard app (native or web), which in turn accesses the marketplace via the platform subscribing interface.
Conceptual architecture for Scorecard Marketplace
Major Components of the Architecture
Scorecard Marketplace Platform is a server component that hosts the scorecard marketplace. Interaction with the platform is simplified through Publishing and Subscribing APIs, mostly RESTful, through which scorecards are published and subscribed from anywhere, anytime on any device in a secure way. These APIs can just be an extension of existing enterprise implementations. The platform can also perform periodic data synchronization with enterprise systems to get real-time data for scorecards. Data synchronization information is updated to the platform along with publishing data. Synchronization can follow the standards available in the market.
The Dashboard App is typically a readily available native application that can be separately built for each channel. A web version of the same can be provided for web access but with limited user experience. The app provides subscription access to the scorecard marketplace and contains prebuilt UI templates to render data into charts, documents, media files, etc., so that user experience is uniform across mobiles and tablets. Internally, the app consumes subscribing API exposed by the platform. Some of the technical features the app can include are:
Access to the scorecards is really made simple by using the Platform and Dashboard App.
Publishing API Internals
Typical Scorecard.zip Structure
container.xml is the key file, a starting point of the package holding information about scorecards to be uploaded to a marketplace.
mimetype just holds the mime type of the package. In this case it is "application/zip" value.
package.xml is a scorecards file that holds metadata and manifest information.
o Publisher identity
o Configuration details such as security, data synchronization, etc.
§ snapshot.data holds snapshot data that is viewed in scorecards
§ security.policy holds information on user access and other restrictions
ui.template holds custom templates (typically XSLT) that are used to render data while displaying scorecards.
Typical steps in publishing
Subscribing API Internals
Typical steps in subscribing from tablets or mobiles
Reader Feedback: Page 1 of 1
Latest Cloud Developer Stories
Subscribe to the World's Most Powerful Newsletters
Subscribe to Our Rss Feeds & Get Your SYS-CON News Live!
SYS-CON Featured Whitepapers
Most Read This Week