ProductVision is a standard Windows^® MDI (Multiple Document Interface) application.  That is, the program has a “desk-top” on which you can open multiple documents.  This is the same type of interface used by other Windows applications like Microsoft Word^®, Excel^®, and PowerPoint^®.  This shortens the learning curve for users already familiar with these programs.  And it happens to be an ideal interface for rapid formula development.

ProductVision allows you to open multiple formulas, raw materials, and other items simultaneously, allowing copying and dragging of information between items.  For example, you may open an existing formula and drag entire sections to a new formula.  This is much faster than having to add each component individually and reduces formulation time dramatically.

ProductVision utilizes “client-server” technology to manipulate and store application information (formulas, properties, MSDSs, etc.).  Client-server technology was originally developed in the 1980s to improve operability and scalability of applications written for mini- and microcomputers.   As such, it is a now a robust, mature technology that is used by thousands of computing applications.  In a client-server application, the user’s machine (client) handles the user interface and data request duties.  Another machine, a server, is connected to the client and responds to query requests for information. 

For smaller applications (less than 50 users), you can implement ProductVision as a 2-Tier application.  That is, the client machine runs the ProductVision application (screens, calculations, etc) and accesses information on the database server.  The database server, in turn, executes the database application software, which may be Oracle or Microsoft SQL Server^®.  As a 2-Tier application, a separate copy of ProductVision and the database connectivity software (ODBC drivers) must be installed on each client PC. 

For enterprise computing with a large number of users, we recommend implementing ProductVision with a 3-Tier architecture utilizing Windows Terminal Server and optionally, Citrix Metaframe™.  Using this technology, the ProductVision client is installed on a single (or small number) of application server(s) with the need to set up only a single connection to the database server.  The application may be accessed with an Internet browser from the user’s machine.  This architecture greatly increases the scalability of the system and dramatically reduces maintenance and implementation costs.  Rollout of the system utilizing this approach is as simple as installing Microsoft Internet Explorer^® on each workstation, which probably already exists.

Implementation of ProductVision with a 3-Tier architecture provides all of the advantages of a “native” browser-based application without its inherent disadvantages.  Specifically, native browser-based applications work well for applications where a user is querying for specific information or filling in forms, but the technology is currently very limiting for sophisticated interactive applications like formula development.   Rapid formula development requires immediate access to information at all points in the process.   Native thin-client applications cannot communicate complicated field-level logic like ProductVision can.  With a browser-based product, you would need to wait until you pressed the “Save” button to know whether the formula meets your allowable criteria.  Given the limited bandwidth available, a native thin-client application has to compromise “intelligence” on the client to have a usable product.   And native thin client applications lose multi-formula “drag-and-drop” and other rapid formula development features.  ProductVision does not have to compromise on functionality to deliver a web-accessible, enterprise-wide solution to meet your product development requirements.

For more information about enterprise computing using Windows Terminal Server and Citix Metaframe, download our white paper on Using ProductVision In a Metaframe Environment.