Home Mail Login

Latest News

Retailviz - A new paradigm in retail analytics - Plus Free White Paper

Retail – Optimizing revenue efficiency through understanding sales opportunities, product placement, customer preferences, channels and location.

vizbybis2 helps you understand the complexities of your retail business and identify practical ways of improving the profitability of your business. In particular, ask yourself...

Remember all those growth plans you had in 2008?

Remember all those growth plans you had in 2008? These plans relied on a robust economy and business as usual.  Unfortunately, times have changed, and it's time to look for technology advantages.  Click the link above to find out how:

January 28th, Webinar hosted by BIS2

Web Seminar

Is Spatial Data Locked Out of Your Data Warehouse?

Attend this webinar featuring industry expert Richard Hackathorn, Stephen Brobst of Teradata and Andrew Cardno of BIS2 and learn about the key insights that spatial visualizations can provide.

 

You are here: product > The Product

The Product

  • What is the product?
  • What does the product do?
  • What is the product's logical architecture?
  • How does the product actually work?
  • Where will the product be installed?
  • How does a user access the product?
  • How does the product interface with Google MapsTM?
  • What does the GUI look like?
  • Will vizbybis2 run with other BI tools?
  • Which databases will vizbybis2 run against? 

What is the product?

The vizbybis2 product consists of two core parts - the client side, a browser-based application, and the server side application of Java™ components.  The server side design is suitable for installation in organizations ranging from small companies to mega-corporations. The client side can be the vizbybis2 client side Adobe® Flash® application or the organization’s own mashup. 


What does the product do?
 
The server side application makes Visual Documents, typically by constructing a data request to the database and then rendering an image (i.e. a Super Graphic). The client side application (the Graphical User Interface (the “GUI”)) creates a mashup of the rendered image and the context map. The context map can be Google Maps™ or another context map.  Additional context maps will be available in future product releases.


What is the product’s logical architecture?
 
The vizbybis2 logical architecture is divided into components based upon functionality and where each component is run. The following vizbybis2 logical architecture diagram shows the major components within each layer, and identifies the interfaces that are exposed between the layers. 

Key components of the vizbybis2 system:


Client Layer (GUI) – The client layer contains the client components. This includes the HTTP browser (Internet Explorer® 7) and the Adobe® Flash® 9 plug-in application used by the application. This GUI is a mashup, meaning it is responsible for bringing together both the Google Maps™ and the vizbybis² server applications.  The product also supports mashups that access the RESTful services directly.

Presentation Layer (RESTful Server) – The presentation layer consists of a RESTful interface to provide access to the vizbybis2 application and associated resources that drive the content shown to the user. This layer is written in Java™ (J2EE™) and runs as a software service. These services provide the entire interface between the business logic, rendering engine, and the outside world. It has no knowledge of the context map used to display its images. It also has no knowledge, except authorization, of who is calling its features.


Business Layer (Server) – The business layer components represent the core of the vizbybis2 system. These components respond to instructions from the RESTful layer and produce Visual Documents. The components also have the knowledge on how to interface to the backend relational database.


Data Layer (Database) – The data layer is used by the business layer. The business layer is responsible for translating the Visual Document requests (from RESTful) into the data requests written in structured query language, SQL. 


How does the product actually work?

The client side application pulls information from both the vizbybis² server side application and the context map (e.g. Google Maps™). The technical term for this kind of application is mashup.
 
The client side Adobe® Flash® application is provided by vizbybis². However, organizations can write their own applications to draw information from the RESTful server - these applications are also likely to be mashups.  

In the above diagram the client makes an HTTP (web) based request. The RESTful server responds with an XML package. This XML might, for example, be a dataset or a GIF image. In the diagram the mashup effect is shown where the client requests a Google Map™ (or other context map) which responds with the required map.


Where will the product be installed?
 
The vizbybis2 server application is suitable for implementation within an organization's own environment. The client side Adobe® Flash® application runs on a user’s web browser accessing the RESTful server using HTTP. This use of HTTP enables broad deployment, for example it enables support of a virtual private network (VPN).


How does a user access the product?

A user accesses the client side application using the client GUI or an organization may wish to use its own mashup.


How does the product interface with Google Maps™?
 
The Google Maps™ interface is held entirely within the client side application and is provided as a mashup.


What does the GUI look like?
 
Below are examples of the vizbybis2 client side Adobe® Flash® application:

-click image to enlarge-

The GUI functionality includes:

  • Viewing a Visual Document – see the big picture, understand the patterns and meaningful relationships.
  • Searching, saving, printing, and emailing Visual Documents.
  • The ability to quickly see the most recently accessed Visual Documents.
  • Viewing a single Visual Document, or viewing multiple Visual Documents, as an animation.

-click to enlarge-

The GUI functionality includes:

  • Zooming capabilities, with a preset default view.
  • On-line Help.
  • A legend that contains relevant information pertaining to the Visual Document.
  • The data from the database that has been used to create the Visual Document.
  • The ability to view the Structure Query Language (SQL) for the Visual Document.

-click to enlarge-

The GUI functionality includes:

  • The ability to create new Visual Documents from the available Visual Designs.
  • The ability to change dates, restrictions, criteria and other parameters for new Visual Documents.

Will vizbybis2 run with other BI tools?

Yes. vizbybis2 has been designed to work with most other BI tools. The RESTful interface allows the vizbybis2 client side application to call other BI tools and for other BI tools that have an open architecture, to call vizbybis2 via the RESTful interface. Alternatively, an organization may wish to combine another BI tool with vizbybis2 as a mashup.

vizbybis2 has been designed to work with:

  • IBM® Cognos®   
  • BusinessObjects™
  • Oracle®
  • MicroStrategy®

The vizbybis2 RESTful interface allows it to work with other applications in addition to those listed above.


Which database will vizbybis2 run against?

vizbybis2 connects to a database using JDBC and uses ANSI compliant SQL. As such it is designed to work against SQL databases including:

  • Teradata®
  • IBM® DB/2
  • Oracle®
  • Sybase®
  • Microsoft® SQL Server

>>next