Wonderware. SuiteVoyager Deployment Guide. Invensys Systems, Inc. Revision A Last Revision: 5/23/02

Transcription

1 Wonderware SuiteVoyager Deployment Guide Revision A Last Revision: 5/23/02 Invensys Systems, Inc.

2 All rights reserved. No part of this documentation shall be reproduced, stored in a retrieval system, or transmitted by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of the Invensys Systems, Inc. No copyright or patent liability is assumed with respect to the use of the information contained herein. Although every precaution has been taken in the preparation of this documentation, the publisher and the author assume no responsibility for errors or omissions. Neither is any liability assumed for damages resulting from the use of the information contained herein. The information in this documentation is subject to change without notice and does not represent a commitment on the part of Invensys Systems, Inc. The software described in this documentation is furnished under a license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of these agreements Invensys Systems, Inc. All Rights Reserved. Invensys Systems, Inc. 33 Commercial Street Foxboro, MA (949) Trademarks All terms mentioned in this book that are known to be trademarks or service marks have been appropriately capitalized. Invensys Systems, Inc. cannot attest to the accuracy of this information. Use of a term in this book should not be regarded as affecting the validity of any trademark or service mark. Alarm Logger, ActiveFactory, ArchestrA, Avantis, DBDump, DBLoad, DTAnalyst, FactoryFocus, FactoryOffice, FactorySuite, hotlinks, InBatch, InControl, IndustrialRAD, IndustrialSQL Server, InTouch, InTrack, MaintenanceSuite, MuniSuite, QI Analyst, SCADAlarm, SCADASuite, SuiteLink, SuiteVoyager, WindowMaker, WindowViewer, Wonderware, and Wonderware Logger are trademarks of Invensys plc, its subsidiaries and affiliates. All other brands may be trademarks of their respective owners.

3 Contents 3 Contents Before You Begin...5 About This Book... 5 SuiteVoyager Documentation... 5 Document Conventions... 6 CHAPTER 1: Introduction to SuiteVoyager...7 Why Use a SuiteVoyager Portal?... 7 About the SuiteVoyager Portal... 8 Features for Portal Users... 8 Browser-Based InTouch Windows... 9 Factory Alarms... 9 Historical Data... 9 MultiViews... 9 Search Capabilities... 9 Portal Administration Features Portal Customization Application Management MultiView Management Security Administration...11 Access Panels...11 License Administration Data Source Configuration Win-XML Exporter for InTouch Localization Support CHAPTER 2: Project Planning...15 About Deployment Project Planning A Planning and Implementation Model for Deployment Identify Key Personnel Profiling the Client Users Identifying the Portal Administrator Define Vision, Scope, and Business Drivers Assess Risks Document Your Current Environment Survey the Existing Control Network Determine Internet/Intranet Use Determine General Portal Use Migration Considerations Document Client Expectations and Current Level of Functionality 26 Create a Functional Specification Create and Approve the Physical Design... 27

4 4 Contents Build the Master Project Plan...27 Deploy a Pilot SuiteVoyager Portal...28 Make Modifications Based on Pilot Results...29 Deploy SuiteVoyager Throughout the Organization...29 SuiteVoyager and Large Domains...30 Client User Training...32 Assess the Complete Deployment...33 Perform Maintenance and Support...33 CHAPTER 3: Networking Considerations...35 General Architecture...36 Required Bandwidth for Data Access...36 Maximum Number of Concurrent Clients Supported...39 Tested Performance Metrics...40 LAN Access of Browser-Based Windows...40 LAN Access of MultiViews...41 Dial-Up Access of Browser-Based Windows...42 Dial-Up Access of MultiViews...43 Deploying SuiteVoyager over the Internet...43 Deploying SuiteVoyager over an Intranet...45 Using Multiple Web Servers for Browser-Based Windows...45 Glossary...47 Glossary of Terms...47

5 Before You Begin 5 Before You Begin About This Book This guide provides information on deploying SuiteVoyager in your company, including project planning and networking options. The SuiteVoyager Portal builds on existing Wonderware Internet technologies and is tightly integrated with Microsoft Internet Information Server. It is assumed that you have working knowledge of basic Internet technologies, Microsoft Internet Information Server, Microsoft SQL Server, and the Windows 2000 Server operating system. For more information on Internet Information Server, Microsoft SQL Server, or your Microsoft Windows 2000 Server operating system, see your Microsoft documentation. SuiteVoyager Documentation The SuiteVoyager documentation set includes the following guides:. This guide provides information on deploying SuiteVoyager, including project planning and networking options. SuiteVoyager Installation Guide. This guide provides information on installing SuiteVoyager, including hardware and software requirements and migration instructions. SuiteVoyager Portal Administration Guide. This guide describes how to administer and maintain an installed SuiteVoyager Portal, such as configuring data sources, managing security, and performing customizations. SuiteVoyager Portal User Guide. This guide describes how to access factory information over the Internet/intranet via the SuiteVoyager Portal. SuiteVoyager Win-XML Exporter Guide. This guide describes how to use the SuiteVoyager Win-XML Exporter to convert InTouch application windows to web pages and publish them to the SuiteVoyager Portal. This guide also describes how to best design InTouch windows so that they can be successfully converted. SuiteVoyager Toolkit Guide. This guide describes how to create custom applications and data providers for use with the SuiteVoyager Portal. This guide is only available with the SuiteVoyager Developer Edition. All of these guides are provided in PDF form and can be printed. Also, information included in these guides is provided in browser-based online Help, which can be accessed from the SuiteVoyager Portal.

6 6 Before You Begin Document Conventions This documentation uses the following conventions: Convention UPPERCASE Initial Capitals Bold Italic Monospace Used for Transact-SQL keywords and SQL elements Paths and filenames Database names, table names, column names, stored procedures, command-prompt utilities, menus, commands, dialog box options, programming elements, and text that must be typed exactly as shown. User-supplied variables, relationships, and phrasings. Code samples, examples, display text, and error messages.

7 Introduction to SuiteVoyager 7 C H A P T E R 1 Introduction to SuiteVoyager Wonderware SuiteVoyager is a manufacturing information portal that enables access and control to plant floor data sources via the Internet or intranet. Contents Why Use a SuiteVoyager Portal? About the SuiteVoyager Portal Features for Portal Users Portal Administration Features Why Use a SuiteVoyager Portal? The industrial visualization or HMI market for supervisory control has undergone significant changes in the last several years. Business today is faster and more competitive necessitating products that are more flexible and dynamic. At the same time globalization and the formation of virtual supplier networks further complicate the production and distribution of products. Businesses today are under tremendous pressure to adjust to dynamically changing products, improve the efficiency of the production process, manage costs, and maximize revenues. All of these factors have combined to demand more functionality from supervisory control products. Not only must they support the needs of the factory floor operators and supervisors, but also summary, analysis, and realtime status information must be made available to a new level of "casual" users. Casual users need immediate access to critical manufacturing or process information that is pertinent to them. They need this information on-demand and for a short duration. Internet technology is driving these major changes and these changes are as significant as the move to client-server computing was over a decade ago. Companies should look at systems that allow them to take advantage of Internet technology, as opposed to merely layering browsers on top of legacy applications. Only then will they be able to manage complexity better, and allow for maximum scalability and extensibility as needs grow. The HMI market for supervisory control must now address the needs of these "casual" browser-based clients in desktops environments as well as the emerging "mobile" clients on untethered platforms.

8 8 Chapter 1 SuiteVoyager offers an integrated solution in that it consolidates all of this information together in an easy-to-use format. In addition, SuiteVoyager provides an integrated set of visualization tools for leveraging information from the PC workstation environment, to the browser environment, to the mobile or embedded environments. The SuiteVoyager Portal will allow customers to take a "voyage" into a new era of information at their fingertips. Using the SuiteVoyager Portal, you can deliver factory-floor information to all decision makers in your organization, from senior executives and production line workers to sales forces and branch offices. You could even provide this access to customers, suppliers, and partners. People at any level of an organization can view information pertinent to them, understand its origins, and improve the way it is managed. About the SuiteVoyager Portal The SuiteVoyager Portal can be used in the following two modes. The mode is assigned based on the rights of the user when he/she logs into the portal. User mode. A user can navigate to all client options in the portal site, such as FactorySuite applications and custom links set up by the portal administrator. Unless a user has administrative privileges, that user will not even see the administrative areas of the portal. For more information, see "Features for Portal Users" on page 8. Administration mode. An administrator is given access to special areas for customizing the portal, managing licenses, configuring data sources, and assigning role-based privileges to other portal users. For more information, see "Portal Administration Features" on page 10. Features for Portal Users SuiteVoyager allows you to visualize and interact with plant floor information coming from Wonderware InTouch systems, InTouch alarm providers, I/O Servers, InControl, and IndustrialSQL Server over the intranet/internet using nothing more than the Microsoft Internet Explorer browser. Using the SuiteVoyager Portal, run-time and historical data access is extended to computers beyond the boundaries of the secured process network. The portal provides enterprise-wide viewing and supervisory control to all of this plant floor information. For example, the portal allows for ad-hoc investigation and reporting of all information relevant to particular tags as defined in InTouch or IndustrialSQL Server, such as current and historical tag values, real-time trends, alarm states and historical records, and graphics. The portal interface provides a secure framework, common navigation method, and a user-friendly graphical user interface (GUI) for delivering access to converted InTouch windows, reports, documents, alarms, historical, and realtime information. The portal also incorporates a single login mechanism and a portal-wide search capability. For information on using any of these features, see the SuiteVoyager Portal User Guide or online Help.

9 Introduction to SuiteVoyager 9 Browser-Based InTouch Windows Using only a browser, you can view and interact with InTouch application windows that have been converted and published to the portal. These windows can run within a browser and do not require InTouch installed on the client computer. These windows will show all graphics and animation with real-time links to the factory floor, just as they do in InTouch WindowViewer. These windows are dynamically scalable and feature two navigation choices: standard InTouch methods (including pop-up windows) or menu-bar web style navigation. Windows can be grouped into WindowSets, which are are ususally retrieving data from the same data source. However, each window can possibly have many data sources, depending on how the window was constructed in WindowMaker (remote tags). Factory Alarms Historical Data MultiViews SuiteVoyager can display current and historical alarms from the InTouch 7.11 Distributed Alarm System and InTouch 7.1 AlarmSuite. If enabled by the administrator, you can view alarm displays that access data in each of these types of databases. You can view current alarms, view alarm history, and configure the alarm display. You can generate trends and reports from history data stored in an IndustrialSQL Server (versions 7.1 and 8.0). You can retrieve data for an unlimited number of tags of a single type, either analog, discrete, or string (memory message) tags. An IndustrialSQL Server report can include sections such as general tag information, historical data, graphs, and event data. The information is configurable to specific times, dates, and resolutions. MultiViews allow for multiple areas of completely independant and varying content to be displayed together on a single browser window. For example, a single window can display an InTouch graphic, InTouch 7.11 historical alarms, and an IndustrialSQL Server report. Information can be arranged in an intelligent manner for the user to enable them to better analyze the information they want to see. Search Capabilities The SuiteVoyager Portal incorporates smart search capabilities to locate keywords or tagnames that are used in the following applications: Process graphics (tagname search only) Any custom application that has been integrated into the portal and includes search capabilities You can also search for tagnames within an IndustrialSQL Server database.

10 10 Chapter 1 Portal Administration Features The SuiteVoyager architecture has been designed for centralized administration. From the administrative section of the portal interface, the administrator can configure all aspects of the portal, including security, access panels, licensing, data sources, write-back parameters. The administrator can also make certain customizations to the portal interface itself. For information on using any of these features, see the SuiteVoyager Portal Administration Guide or online Help. Portal Customization The portal administrator can completely customize the look and feel of the SuiteVoyager Portal home page, such as: Adding a custom logo or replacing the portal banner. Replacing the default home page content. Creating links to published reports, documents, other web sites, or resources. All of this is accomplished through a series of easy-to-use menus, without leaving the SuiteVoyager Portal. Users will see the changes when they refresh the current portal page. Application Management Using SuiteVoyager, you can install and configure additional applications to enhance the functionality of the portal. Applications are available from Wonderware and third-party partners. After an application has been integrated, the portal administrator can change the configuration for the application, if a configuration page was provided by the application developer. Two custom applications are currently available for purchase from Wonderware. Charting Application. The charting application can be used to query any SQL-compliant database through the SuiteVoyager SQLPROVIDER web service and display the results into a variety of charts. Data Table Application. The data table application can be used to build and execute a SQL query against any SQL-compliant database through the SuiteVoyager SQLPROVIDER web service. The results are displayed in a table format with customizable and sortable columns. MultiView Management You can configure web displays, called MultiViews, that contain one or more Web Parts and then save these displays on the portal. You can easily add or remove Web Parts to and from a MultiView, and modify the layout of the included Web Parts via a drag-and-drop interface.

11 Introduction to SuiteVoyager 11 A Web Part is a component that contains web-based content, such as HTML pages, scripts, or Extensible Markup Language (XML) code. Web Parts are similar to ActiveX controls in that they are stand-alone components, and can be reused in multiple web browser displays. Web Parts are built to a Microsoft Web Part standard or are wrapped with a Web Part compliant shell so they can be used in any Web Part compliant container, such as SuiteVoyager. Thus, you can use any standard Web Part within SuiteVoyager, whether it be a Web Part available from Wonderware or from a third-party company. Security Administration Security concerns should be considered before deploying SuiteVoyager. You want to make sure the people that need the information have access to it, while limiting or completely denying others access to certain information. SuiteVoyager can be deployed in an Internet environment. Since this connects sensitive industrial information to the Internet and allows for the enabling of write-back to plant controllers, the need for tight security is paramount. SuiteVoyager controls access to plant floor information at the portal and user levels. The first level of security is access to the SuiteVoyager Portal web server itself. Access to the SuiteVoyager Portal is achieved by tight integration with Microsoft Windows security (Kerberos) and the security mechanisms employed by Internet Information Services. For additional security, the SuiteVoyager Portal also supports Secure Sockets Layer (SSL), password authentication, digital certificates, and Windows login dialog boxes. SuiteVoyager is installed in a "safe state." This means that the user who installs SuiteVoyager will be the only person with privileges on SuiteVoyager. This user will have administrative privileges and can add additional users. However, the "Everyone" Windows group (all authenticated users from the same domain as the portal) is given "Read-Only" access. The second level of security determines what casual users (or groups of users) will be able to do once they access the portal. The portal administrator can grant specific users (or groups) privileges by assigning them to pre-configured security roles. The third level of security is for write-back capability for factory data sources, such as those used for InTouch browser-based windows. WARNING! Enabling write-back will allow users to change the state of plantfloor devices, with potentially life-threatening consequences. Access Panels SuiteVoyager provides a new feature, access panels, which enables a high level of flexibilty when configuring which information a user or a group of users is able to view in the portal.

12 12 Chapter 1 An access panel is a logical grouping of navigation nodes (folders) and links that is only accessible to particular users assigned to it. Access panels allow you to segregate portal objects (for example, converted InTouch windows, alarm displays, and history reports) into groups of related information. Then, each access panel can be configured to allow access by specific Windows users and user groups (for example, plant maintenance personnel, operators, or managers), so that each user or group will see only the portal objects that are pertinent to their area of the plant or their user group. For example, an Operators access panel might show InTouch graphics and charts for a particular portion of the plant floor to just the plant operators assigned to that panel. A Maintenance access panel might show only historical trends of plant equipment tags to plant maintenance personnel. License Administration The SuiteVoyager Portal supports concurrent, session-based licensing; that is, the licensing policy located on the portal server determines how many browsers can access information at any given time. No license control software is required on the client. All of the license information is managed by a dedicated license management component. When a client attempts to access SuiteVoyager through Internet Explorer, the license manager checks to see if a session license is available and grants or denies access to the client depending on license availability. You will need enough client licenses for the amount of users that will be concurrently accessing the licensable areas of the portal site. Client access to these areas is on a first-come, first-served basis. For example, if the SuiteVoyager Portal is licensed for ten concurrent clients and an eleventh client attempts to access the server, a message will appear at the client stating that there are no additional licenses available. However, if the eleventh client is a portal administrator, then he/she will be allowed to access only the administrative areas, with the exception of the MultiView Manager. A session is created when a client user accesses the SuiteVoyager Portal home page, and a license is issued for the use of the core SuiteVoyager applications, such as Process Graphics, Factory Alarms, and Historical Data. A user can access these and all custom areas and still only use one license. Add-on applications that support licensing will burn a license for that application the first time the user accesses the application link. All licenses are released for the user's session when the user clicks Log Off on the main menu bar. If a user closes the browser without logging off, the current license session will time out after a certain length of time. By default, this is set to 20 minutes and can be changed by the web server administrator for the SuiteVoyager application using the Internet Information Services console application. The license management feature allows you to monitor activity and usage on the portal. Licensing information is displayed in text format to allow analysis of peak portal usage times and personnel. Note SuiteVoyager Portal does not manage the licensing of third-party ActiveX controls.

13 Introduction to SuiteVoyager 13 Finally, you can create as many connections as you want to the default InTouch alarm databases (WWALMDB and AlarmSuite) and IndustrialSQL Server database (Runtime) without having a license for additional connection strings. However, connections to other data sources require a license. One license is included with the portal. For example, you want to connect to an InTrack database, an Oracle database, and a SQL Server database. The connection to the InTrack database can use the connection license included with the portal, but the connections to the Oracle and SQL Server databases will require the purchase of two additional connection licenses. The licensing is enforced when you attempt to create the connection string, not when it is used. Once you have defined the connection string, it may be used an unlimited number of times throughout the portal. For more information on licensing, see the SuiteVoyager Portal Administration Guide. Data Source Configuration SuiteVoyager stores configuration information in a Microsoft SQL Server database. In addition, SuiteVoyager can use the following applications as data sources, also known as data providers, out of the box: InTouch WindowViewer I/O Servers InControl IndustrialSQL Server (7.1 and 8.0) InTouch Distributed Alarm Subsystem AlarmSuite Any data source that communicates using an ADO connection string. For example, an Oracle, SQL Server, or Access database. Note Custom data providers can be created using the SuiteVoyager Data Provider Toolkit. In previous architectures, client tools would have been required to be loaded and maintained on each client computer. A benefit of the portal concept is that it centralizes all of the tools and data; everything can be maintained from the portal. Also, there is less duplication of data, and users have a common interface for accessing all types of information. Win-XML Exporter for InTouch SuiteVoyager includes an XML graphic exporter utility for use with FactorySuite InTouch WindowMaker (development system). This utility allows you to convert InTouch windows to XML/XSL, group them into sets, and then publish them to the SuiteVoyager Portal. Thus, these converted InTouch windows are "browser-based," instead of based on the native InTouch format.

14 14 Chapter 1 Portal users can view these converted windows using only the Internet Explorer browser. When a user accesses a window, the XML data and the required stylesheet for the window will be automatically downloaded to the client computer. Internet Explorer will then use VML to render the window. The client will have full read/write-back control, if granted by the administrator, and can visualize and interact with the InTouch application on the factory floor. The browser-based window sets derive their information from InTouch WindowViewer nodes and I/O Servers. In addition, you can obtain information from other data sources by using ActiveX controls within the InTouch windows to be converted. When a client user views the converted windows containing the ActiveX control, the control will connect to the original data source just as if the window was displaying in WindowViewer. You do not need to install any special software or licenses on the client computer, unless your published window relies on third-party ActiveX controls which require runtime licenses. It is very important to optimize the InTouch application to run in a browser environment. The SuiteVoyager Win-XML Exporter Guide has been provided to help you minimize the time spent redesigning existing applications and maximize the information delivered to the client. This guide provides tips for designing applications, workarounds for unsupported functions, and instructions on optimizing your application. Make sure that you review this guide before converting and publishing windows to the portal. Localization Support SuiteVoyager is multi-lingual out of the box. The SuiteVoyager Portal will detect the language of the browser client and automatically display the portal information in the language of the browser client, as well as any error messages. No additional configuration or programming is required. SuiteVoyager currently supports English, French, German, and Japanese. On the server side, the only additional feature that you need to install to enable this is the Japanese character set; all other languages will display correctly without any other configuration on the server. The Japanese character set is available as an optional language selection when you are installing the Windows 2000 operating system. For more information, see the SuiteVoyager Installation Guide. Your distributor can provide information on additional languages for SuiteVoyager.

15 Project Planning 15 C H A P T E R 2 Project Planning A planning model is provided for you so that you can properly deploy SuiteVoyager. There are many steps to consider before deploying SuiteVoyager. Who are your casual users? What information is important to them? What can your current networking capabilities handle? What environment do you want to deploy SuiteVoyager in? This documentation will lead you through the critical areas to consider before deploying SuiteVoyager in order to minimize your work effort while maximizing your results. By planning your project in advance, you will be able to pinpoint potential problems and budget for future expansion. It is also very important for you to test the deployment using a pilot project. Contents About Deployment Project Planning A Planning and Implementation Model for Deployment Identify Key Personnel Define Vision, Scope, and Business Drivers Assess Risks Document Your Current Environment Create a Functional Specification Create and Approve the Physical Design Build the Master Project Plan Deploy a Pilot SuiteVoyager Portal Make Modifications Based on Pilot Results Deploy SuiteVoyager Throughout the Organization Assess the Complete Deployment Perform Maintenance and Support

16 16 Chapter 2 About Deployment Project Planning In planning the deployment, there are several things that you will want to keep in mind. Since every web site is unique, you will want to make sure to carefully plan, organize, and test your web site to ensure optimized performance before you actually deploy it throughout your company. The main component that will determine a successful deployment is being able to provide your casual users with the information they need, when they need it, wherever they are, easily, quickly and concisely. In order to do this, you will need to look at a number of factors that could hinder this process. During the planning phase, you need to carefully consider your communication network to determine if it is sufficient to handle the amount of users who will need to access the SuiteVoyager Portal. If necessary, this is the time that you will want to think about upgrading your communication network to a more sophisticated one. You will also want to determine what hardware and software you need and schedule when to purchase these items. During this phase, personnel necessary for the deployment should be assigned roles and know what tasks are expected from them. A Planning and Implementation Model for Deployment The following flowchart illustrates the major steps and decisions that need to be made throughout the deployment. Following this flowchart will ensure that the installation proceeds smoothly and that planning and forecasting issues are documented and scheduled. It highlights the major activities and tasks and their associated milestones and key deliverables that are important for the entire project team. Although the activities leading to each milestone have a logical progression, they need not take place in the order stated. Different team members can perform activities concurrently, to leverage resources of people, time, and money. Use your best judgement and knowledge of the application to deciding the optimal time to work on any specific activity. To maximize project efficiency, however, you should not change the sequence in which the four milestones are reached. The roadmap provides a high-level overview of the deployment process. It includes: Activities that are necessary to complete the project deliverables and advance to the next milestone. Resources that are necessary to complete each activity and create project deliverables. Deliverables resulting from activities that are necessary to complete a timely and effective project.

17 Project Planning 17 Use this roadmap to gain a comprehensive visual perspective of how your team must prepare itself to undertake this project. Gray highlighted areas in the left column denote the four milestones, and are explained in the subsequent table.

18 18 Chapter 2 Milestone Deliverable Activity Vision/scope approved (Envisioning phase) Vision/scope document The vision statement provides a conceptual foundation for the entire project. The project scope defines specific parameters and features of project implementation. An opportunity cost analysis is conducted. Risk management plan This plan provides a high-level view of risks that could occur throughout the project with parallel mitigation plans. The risk management plan is revisited during each of the succeeding phases and milestones. Project plan approved (Planning phase) Scope complete/first use (Developing phase) Release (Stabilizing/Deploying Phase) Bugs and issues database This database is a repository in which all issues that arise during the project are logged and resolved. The bugs and issues database is revisited during each of the succeeding phases and milestones. Functional specification This specification identifies business and technical design requirements, including any proposed products and technologies. The functional specification describes specific project deliverables and the final release product. Physical Design This document details the work that will take place. It is a compromise between the goals of the project and the constraints of technology, finance, and time. Master project plan This plan provides the essential elements needed to implement and track the actual project and describes the project from business, technical, application, and implementation perspectives, including all tasks needed to complete testing and piloting. Master project schedule The schedule provides the essential elements needed to track time-sensitive deliverables. Pilot server Postmortem Server deployed throughout the environment The goal is to test SuiteVoyager and the modified InTouch applications in a controlled environment, but engaged in real-world activity. This involves building a test lab, identifying a pilot group, and documenting use cases. The pilot deployment concludes with a meeting to determine if the test server met project requirements. For the most part, the full deployment process resembles the pilot deployment process, but on a larger scale. Additional portal administrators and users can be trained at this time.

19 Project Planning 19 Milestone Deliverable Activity Deployment assessment A stable, scalable process visualization infrastructure During and after the deployment, communicate with the project overseers to report progress and gauge overall satisfaction. The result of a successful deployment will be a satisfied customer or management unit, the satisfactory achievement of all primary deployment goals, and a process visualization infrastructure that can be adequately maintained and scaled for the future. Keep the test lab running after the deployment to test new applications and any significant changes you want to make to the server or network. Identify Key Personnel SuiteVoyager will enable people in your organization to have immediate access to critical plant floor information whenever and wherever they need it. A successful implementation starts with building a team with people who have the right expertise for the job, who are empowered to use their expertise, and who are held accountable for results in their areas of responsibility. The team should include a mixture of people who can promote buy-in and maintain continuity throughout the deployment. Eight distinct roles must be filled and are outlined in the table below. There need not be a one-one relationship for each role. Team member Role Skill set Executive sponsor Provides leadership, money and Familiarity with the SuiteVoyager human resources. concept. Assures changes are adopted into the company culture from the top down. Understanding of business drivers. Project manager Drives critical schedule decisions. Familiarity with the SuiteVoyager concept. Portal Administrator Responsible for deploying SuiteVoyager. Familiarity with project management tools. Knowledge of plant servers and data sources. Familiarity with company policies and practices for web servers. Understanding of security implementation.

20 20 Chapter 2 Team member Role Skill set IT Administrator Responsible for incorporating web server into existing infrastructure. Knowledge of domain controllers setup and configuration. System integrator Represents the engineers who will be modifying and designing the InTouch windows to be displayed in the portal. Testing and Validation Ensures all issues are known before deployment. Knowledge of administering IIS. Experience with designing applications in InTouch. Familiarity with the SuiteVoyager Win-XML Exporter Guide. Familiarity with applications and operating systems. Logistics management Training Performs scalability analysis and performance testing. Ensures a smooth rollout of product or service. Helps identify and meet client and portal administrators needs and desires. Familiarity with the process and related operations. Familiarity with the organization's system and network infrastructure. Good relationship with the system integrator and vendors. Good understanding of the delivery schedule. Good understanding of the SuiteVoyager functions and capabilities. Ability to write clear and useful documentation. Experience training users. End-user Represents the casual client user. Good understanding of the information available. Good relationship with the portal administrator. Ability to communicate information needs to portal administrator. Assigning roles to personnel early in the deployment phase will help to ensure that all the pieces of the deployment that require personnel will be handled. Early on it is essential to have a schedule that details when people will be expected to provide key deliverables and who is responsible for major activities in the deployment process as well as when they will occur. This will allow you to leverage the amount of personnel resources you have in an efficient manner.

21 Project Planning 21 Profiling the Client Users Before beginning the deployment, it is best to consult with the casual users who need the information from SuiteVoyager. For example, initial discussions about the upcoming deployment should center on having the users describe what information they would like to see on the browser-based windows, what rights such as read/write would be necessary, and what type of information they are looking for. You will want to consider aggregating information from multiple windows and designing a few windows which show all the information they are interested in seeing to save them time navigating and opening browser-based windows. Identifying the Portal Administrator When SuiteVoyager is initially installed, there is only one portal administrator, the person installing the software. The SuiteVoyager Portal administrator will have the responsibility for assigning portal privileges to other users. SuiteVoyager's role-based security mechanism is built into the portal framework and is easy to understand and use. An information technology person is not needed to configure this area. Other important things that an administrator on the portal will need to know are: The location of the Microsoft SQL Server that will be storing portal information The node name or IP address for the various computers that will be providing the alarm and IndustrialSQL Server information The privileges that are inherent with each of the user roles Which nodes to assign write-back privileges to How to convert and publish InTouch browser-based windows Because the portal has been designed to be easy to install and use, the portal administrator does not need to be a network domain expert or a web developer. However, the administrator might also want to have further training on Internet Information Services (IIS) if they are responsible for administering it. There are a few areas of IIS that they should be aware of. They should be familiar with where IIS is located, simple settings they can modify, where the log file is stored, and what the company procedures and policies are for archiving, purging and logging this information are, how to restart the web server and all the services required for the SuiteVoyager web server, and basic maintenance. This information can be found throughout this deployment guide, but for indepth information, you will need to consult your Microsoft documentation or IIS administrator. The portal administrator also should be familiar with the plant operations and where InTouch, IndustrialSQL Server, and alarm information are located. After installing SuiteVoyager, you will want to configure the data sources and point to where these computers are located, as well and provide passwords to access the information.

22 22 Chapter 2 Define Vision, Scope, and Business Drivers The vision statement is an expansive view of the proposed deployment. It describes the top business reasons for deployment and broadly defines the overall results of successful completion. Scope defines the portions of a vision that can actually be accomplished within the project constraints. The project scope provides boundaries for the vision statement by specific details that include business reasons for deployment, features, resources, and schedule framework. By understanding the capabilities of SuiteVoyager and the effort to provide them, you should be able to deliver what you promise. The scoping process should be specific, measurable, achievable, result-based, and time-oriented. The following table provides a more detailed definition of this process. Action Specific Measurable Achievable Results-based Time-oriented Definition Specifying results to be achieved (for example, what information needs to be available to client users). Clearly specifying what will be achieved (for example, how many portal servers or how many client licenses). Identifying what the enterprise will achieve by this action (for example, plant-wide access to process data). Establishing realistic outcomes based on company resources and project parameters. Setting a realistic time frame to achieve specific goals (for example, will commence on X date and complete on Y date). The information that you will be able to provide to the users will depend on a number of items. It will be very different depending on the bandwidth available, the environment SuiteVoyager will be deployed in, and who the client users are. The amount of graphics you will want to convert and publish will rely heavily upon the type of control network you have in place. For example, if most of the client users will be accessing the portal using 28.8 modems, you might want to make a few specialized InTouch windows that only show the information they need in text format. Also, designing the windows with minimal or InTouch graphics would help with the performance. However, if you have the bandwidth, you can use all of your graphics-intensive screens and publish the screens after making any necessary modifications. For more information on bandwidth planning, see "Required Bandwidth for Data Access" on page 36. You should read the SuiteVoyager Win-XML Exporter Guide before attempting to modify or publish any windows. This will help you modify your windows so that the information you need is displayed optimally for the portal site.

23 Project Planning 23 The information you want to display will also change depending on the installation site. If the portal is designed to provide information for a single plant, the plant engineer will be familiar with where all the information needed for the portal site is stored. However, SuiteVoyager can also be deployed as a corporate portal and used to gather information from many other portal sites. For more information on bandwidth planning, see "Using Multiple Web Servers for Browser-Based Windows" on page 46. The important thing is to determine what environment the portal will be deployed in and design your system to provide the information that is important to the users of your portal site. Assess Risks Risk identification and ranking is the first step in the proactive risk management process. It provides the team with information it needs to bring major risks to the surface before they adversely affect the project. Possible risks in deploying SuiteVoyager are: Allowing irresponsible users to have write-back privileges to the plant nodes. Insufficient firewall protection when deploying SuiteVoyager over the Internet. Combining SuiteVoyager with other plant critical applications, such as InTouch, on the same server and having to restart the web server. Failing to accurately determine the communication network for current and future applications. Failing to understand end-user expectations. Not providing adequate security to sensitive documents or applications residing in the customizable section of the portal. Failing to adequately train personnel who are responsible for administering the system. Risk is composed of two factors: probability and impact. Risk probability is the likelihood that an event will actually occur. Risk impact is the severity of adverse effects on operations, safety, cost, or the ability to continue with the project. Once identified, the risk should be rated (for example, high, medium, or low) based on its probability and impact, and a corresponding mitigation plan should be developed. The assessment is then entered into a risk assessment matrix. This matrix should be a living document, updated whenever there is a change, and included in deployment status reports.

24 24 Chapter 2 A sample risk matrix is as follows: Impact Probability Risk Description Owner Date Mitigation High High Application windows not correctly modified for the browser environment. High Low SuiteVoyager was installed on existing Windows 2000 Server and corrupted applications that were hosting other company web sites. Routers are configured to filter port Systems Integrator Portal Administrator Project Manager Medium Low IIS crashing. Portal Administrator mm/dd mm/dd mm/dd Familiarity with the SuiteVoyager Win- XML Exporter Guide in advance of application modification. Portal administrator is responsible for securing adequate hardware to install SuiteVoyager on. Configure routers to allow connections through port. Uses IIS 5.0, which provides additional feature to insure more uptime on IIS. Document Your Current Environment Before beginning the deployment process, you should assess and document all aspects of the environment in which you want to deploy SuiteVoyager. Survey the Existing Control Network It is a good idea to survey the existing infrastructure to determine if the existing control network is fast enough to allow dispersing information to the amount of casual users who need the information. The amount of bandwidth that you have available will dictate all aspects of the portal deployment, from the amount of client users that can access information to the actual design of the portal windows. For more information on bandwidth planning, see"required Bandwidth for Data Access" on page 36. Determine Internet/Intranet Use You will want to document the network configuration that SuiteVoyager will be deployed in. Typical network configurations are based on whether SuiteVoyager will be deployed as an intranet or Internet site. This will make a difference when determining what information you would like to post in the customized section and what privileges you would like to assign to various users. It is best to install SuiteVoyager in the intranet environment and configure it for the Internet at a later date after verifying that SuiteVoyager is configured correctly.

25 Project Planning 25 Also, you should be thoroughly knowledgeable about your company policies and standard operating procedures regarding deploying web applications over the intranet and/or Internet. SuiteVoyager 2.0 makes use of web services for secure and quick access to information through firewalls over the Internet or intranet. The SQL Data Access Provider can connect to any ADO-compliant database. For more information, see the SuiteVoyager Toolkit Guide. Determine General Portal Use The environment that you will be deploying SuiteVoyager in is important in determining what information you would like to provide to the casual user. If the environment is simply plant-wide, then the plant manager can appoint someone familiar with the day-to-day operations of the plant and the InTouch applications to create or modify windows to deploy in the SuiteVoyager Portal. They should follow the guidelines decided upon from earlier meetings with the end users to determine what information is important to them. If SuiteVoyager is to be deployed as a corporate portal, you may want to look at other options for creating or modifying windows. These could include making a subset of windows that displays the pertinent information from various similar facilities. This would minimize the effort required when modifying the windows, as the subset could be exported to the other facilities with minor adjustments to tagnames that might be different. However, this is one way to provide standardization among the plants. Another option is to aggregate the information from applications to a few windows that show combined information. Again, it depends on what the end user is interested in viewing and what information is important to them. If you keep in mind who the end user is when designing the application and the environment that SuiteVoyager will be deployed in, you will help to deter later complications. Migration Considerations If you already have a SuiteVoyager 1.0 installation, you will want to migrate the information and settings within that portal to SuiteVoyager 2.0. However, if you are implementing SuiteVoyager for the first time, it is a good idea to implement your portal on the actual server system you plan to use, rather than on a separate system. Migration of configuration settings, user role assignments, and process graphic windows from a SuiteVoyager 1.0 portal is managed for you by the SuiteVoyager 2.0 installation program. It is recommended that you upgrade the existing SuiteVoyager 1.0 Portal to SuiteVoyager 2.0 to take advantage of this feature. After the new SuiteVoyager 2.0 system installation is set up, your existing InTouch browser based windows and configuration settings will be ready for you to access. For more information, see the SuiteVoyager Installation Guide.

26 26 Chapter 2 Document Client Expectations and Current Level of Functionality No matter how powerful and robust your server is, or how well you have planned the architecture of your environment, in the end the success of your project will be measured by the usability of the portal to the client. Knowing the needs of the end-user and their accessibility to the portal is critical to a successful project. Most companies have a few hundred InTouch windows that show the entire operation of their company. While some users might want to have access to all of the windows, it is likely that most of the casual users to the portal do not work with the InTouch application on a daily basis and will only want to have quick access to just the information they need. If this information can be aggregated and presented in a few windows, most users will be elated; however, if they have to sift through multiple windows to try to locate the information they need, only to find it spread throughout multiple windows, they are not going to be as happy with the product. It is up to you to make sure to present the information in a way that provides the critical information to the user in a concise manner, enabling them to quickly analyze the information and make better decisions as a result. In order to set the expectations of the users, you will need to be able to measure what they have and use today with what you intend to deliver. These measurements are known as benchmarks. Benchmarks are used to draw comparisons between the "as-is" and the "to-be" models and highlight areas where expectations can be exceeded, can be met, or are deficient. Representative benchmarks include: Quick access to pertinent information Access to information from multiple data sources Availability of the SuiteVoyager Portal Time delays to process information or query databases Information analysis tools Corporate information accessibility Multi-lingual considerations Information sharing capabilities Interaction with information using the write-back option for the browserbased windows. Ease of publishing new WindowSets Ability to publish and access timely reports As the users become more familiar with the portal site, they will be able to offer valuable critiques for enhancing the portal. Your ability to accommodate those requests will enable the deployment of SuiteVoyager to be a success.

27 Project Planning 27 Create a Functional Specification Creating a specification that documents the SuiteVoyager functionality is the next step after documenting the environment. This functional specification is a high-level explanation of how SuiteVoyager will be designed and what it will do. The functional specification should be considered a blueprint for the deployment process and presents goals that have been agreed to by all team members. However, the team should not treat the functional specification as something written in stone. It should be a living document that the team updates regularly to reflect changes in scope or schedule. The functional specification should ensure that what the team wants to achieve is what is required by the business. When you can directly relate the outcome of the deployment process to business goals, you have your "to-be" model. The "to-be" model is a set of target measures that you will work to achieve. Most measures will be quantifiable, such as the information required for access by the client users through the portal, while others will be more subjective, such as better decision making ability based on access to critical information. The "to-be" data collection will most often come from your pilot users. By comparing this data against the benchmarks, you can determine whether you are ready to proceed with your implementation. Create and Approve the Physical Design A physical design is part of the design process in which you collect the information you have gathered about the current state of the environment and the goals that have been identified in the functional specification, and use this information to develop a plan for deploying SuiteVoyager within the limits set forth in the vision/scope document. The physical design builds upon the logical design and functional specification by applying real-world technology constraints, including any implementation and performance considerations. It is a compromise between the needs of your business and the limitations of the computer. This is also the point at which the team can estimate human resources, costs, and schedules. When determining the physical design, it is important that you understand the options available to you. For detailed information on computers you will need, hardware and software requirements, and networking considerations, see Chapter 3, "Networking Considerations." Build the Master Project Plan All members of the project team contribute to the project plan by producing planning and scheduling documents describing how they will create the system or service as defined in the functional specification. The project plan includes approach, dependencies, assumptions, and budget information and refines the agreement of the vision/scope document between the team and customer.

28 28 Chapter 2 The project team should have a number of major deliverables ready before the project plan is completed and the project plan approved milestone is reached. These major deliverables include: The environment analysis should contain a comprehensive assessment of the technical infrastructure as it currently exists. The functional specification should provide the beginning of the deployment plan. The physical design should detail the actual plan of action. The risk assessment should be updated with current information. After the team has created the master project plan and started the project, they should update the data on a regular basis. The project team should also review the project plan regularly to determine if the project is on time and on budget. Deploy a Pilot SuiteVoyager Portal A successful implementation of SuiteVoyager relies on having the correct hardware and installing the software correctly. The pilot deployment phase is designed to test the SuiteVoyager Portal hardware and software setup in a controlled environment. A pilot planning worksheet should be developed to help organize resources during the deployment phase. The personnel resources you identified for the deployment should be assigned tasks. Schedules for when these tasks will be accomplished should be developed to insure proper access to hardware and resources. The following steps are provided as a high-level overview of what needs to be performed to deploy the pilot SuiteVoyager: 1. If you do not currently use a domain controller, you will need to set up a domain controller and add the SuiteVoyager web server as a user. For more information, see the SuiteVoyager Installation Guide. 2. Install the operating system for the SuiteVoyager web server. For more information, see the SuiteVoyager Installation Guide. 3. Install Microsoft SQL Server. For more information, see the SuiteVoyager Installation Guide. 4. Install SuiteVoyager. For more information, see the SuiteVoyager Installation Guide. 5. Install and configure the SuiteVoyager license files. For more information, see the SuiteVoyager Installation Guide. 6. Configure additional users to roles. For more information, see the SuiteVoyager Portal Administration Guide. 7. Configure data sources. For more information, see the SuiteVoyager Portal Administration Guide.

29 Project Planning Convert and publish InTouch windows using the SuiteVoyager Win-XML Exporter. Test your settings for write-back capabilities, communication connections, and client access speeds. For information on installing and using the Win-XML Exporter, see the SuiteVoyager Win-XML Exporter Guide. 9. Test the data source configurations. 10. Customize the portal site. For more information, see the SuiteVoyager Portal Administration Guide. Adequate testing of the portal site during the pilot phase will ensure a successful final deployment. Make Modifications Based on Pilot Results The pilot deployment will provide feedback on any additional items needed, such as more memory, incorrect software installations, and control network communication capabilities. After making modifications, you should test the pilot deployment again until the deployment parameters measure up to your expectations and/or function acceptably within the limitations of your environment. Deploy SuiteVoyager Throughout the Organization Once the initial deployment is complete and the server hardware and software tested and operating properly, you can finish the deployment to the rest of the organization. This is fairly simple, since the clients only need to be running the required version of Microsoft Internet Explorer. Be sure to tell the client users the URL of the SuiteVoyager Portal so that they can access it. Typically, the URL will be: By default, everyone in the domain will have read-only access to the SuiteVoyager Portal. If you need to add users to a different security role, see the SuiteVoyager Portal Administration Guide. Also, add additional licenses if you need them, to accommodate the number of client users that will be accessing the portal site.

30 30 Chapter 2 SuiteVoyager and Large Domains Many organizations today operate large network configurations with thousands of users, groups, and domains. If your organization has such a network, then configuring a user population as SuiteVoyager users can be inefficient and time consuming. Very large groups of users (more than 10,000) can cause timeout issues when attempting to obtain the user lists in SuiteVoyager 2.0. Because of this, SuiteVoyager restricts the actual number of users displayed in a large domain. In order to configure users and groups of users in large networks as SuiteVoyager Portal users, use the Component Services Manager tool that is provided with Microsoft Windows. Note To use this tool, you must have administrator privileges on the SuiteVoyager 2.0 Portal server computer. To add a user to a SuiteVoyager role 1. On the Windows Start menu, point to Programs, point to Administrative Tools, and then click Component Services. The main window displays. 2. Expand Component Services, expand Computers, and then expand My Computer. 3. Expand COM+ Applications, expand Wonderware SuiteVoyager, and then expand Roles.

31 Project Planning In the appropriate role folder (for example, the Administrator role), rightclick on the Users folder, point to New, and then click User. The Select Users or Groups dialog box appears. 5. Select the user from the displayed list. 6. Click Add so that the name appears in the window at the bottom of the dialog box. 7. Click OK.

32 32 Chapter 2 You can also add complete groups of users (as defined in the domain) to SuiteVoyager roles. The following example shows the addition of the group LocalAdmins to a SuiteVoyager role. You can also add users to different roles in User Manager page in portal. For more information, see your SuiteVoyager Portal Administration Guide. Client User Training The SuiteVoyager Portal is easy to use and understand. The first thing you will want to do is to let the users know what the URL for the server is. Once they can access the SuiteVoyager Portal, they can read the captions under the icons to familiarize themselves with the functions each performs. There is also an online documentation manual located at the top of the SuiteVoyager web portal. This will give them more information about navigating through the portal site. A list should be made and distributed to each group of users that are assigned to the different roles to alert them to what privileges they have in the SuiteVoyager Portal. This will help to eliminate confusion between "no access," read-only," and "administrator/engineer" users. For more information on available roles and the privileges they encompass, see SuiteVoyager Portal Administration Guide.

33 Project Planning 33 WARNING! All users should be made aware of the fact that the log off button in the SuiteVoyager Portal does NOT log them off of the Windows domain. The only way to do completely log off is to close the browser. If they do not close the browser, someone else could click the Back button in the browser and access the portal page or browser-based window that was just being viewed. This could have potentially life-threatening effects if the person logged on had write-back privileges. Assess the Complete Deployment After the SuiteVoyager Portal has been deployed in your production environment, assess the effectiveness and make any changes. Perform Maintenance and Support The SuiteVoyager portal is designed to aggregate important company information in an easy-to-use format for the administrator and the user. As the organization changes, different information might become necessary to view. You will need to be able to optimize additional InTouch windows and information from InTouch nodes, configure new data sources when they are added, and add new users to the system. Also, you will want to make sure to have standard policies in place with regards to employees who are no longer with the company, what to do in the event of a hacker, backup procedures for the web server, and what to do in case of a web server failure. Be sure that you check the Wonderware web site for SuiteVoyager updates. Finally, check the Microsoft web site often for upgrades and patches for Windows 2000 Server, IIS, and SQL Server.

34 34 Chapter 2

35 Networking Considerations 35 C H A P T E R 3 Networking Considerations Network considerations include the overall network architecture, required bandwidth for data access, whether or not you will be deploying over the Internet or intranet or both, and whether you will be using multiple web servers. Contents General Architecture Required Bandwidth for Data Access Deploying SuiteVoyager over the Internet Deploying SuiteVoyager over an Intranet Using Multiple Web Servers for Browser-Based Windows

36 36 Chapter 3 General Architecture Data sources for the portal must be located and accessible via the same local area network (LAN) as the portal, or be connected via a web service such as the Wonderware SQL Data Access Provider. All clients must have access through the Internet or the Intranet. The SuiteVoyager Portal supports TCP/IP on the Internet/intranet side and all networks supported by the FactorySuite on the LAN side. The Hypertext Transport Protocol (HTTP) is used to transport data between the Internet/intranet clients and the SuiteVoyager portal and between the portal and a SuiteVoyager SQL Data Access Provider. TCP/IP-based protocols are used to transport data between the portal and any local area plant floor data sources such as WindowViewer, IndustrialSQL Server, or I/O Servers. SuiteVoyager also uses data access technologies such as ADO and OLE DB from Active Server Pages to retrieve database information from IndustrialSQL Server, AlarmSuite, or InTouch Distributed Alarm System database, and the SQL Data Access Provider service to connect to any other database that can provide access via ADO. Custom data providers can be built using the SuiteVoyager 2.0 Developer Edition. For more information, see the SuiteVoyager Toolkit Guide. Required Bandwidth for Data Access You will need to determine if you have the necessary bandwidth for: Clients to connect to the SuiteVoyager portal and download information. SuiteVoyager to retrieve data from any factory applications.

37 Networking Considerations 37 The bandwidth requirements for these two separate segments of the architecture are not necessarily the same. For the control network, SuiteVoyager aggregates information from plant floor data sources; it does not replicate information. Clients communicate with the data sources only through the SuiteVoyager web server. In the following diagram, notice that the clients are not in direct communication with IndustrialSQL Server, InTouch WindowViewer, and the I/O Server.

38 38 Chapter 3 Users can also obtain data across the Internet or intranet using a SuiteVoyager data provider. The following diagram illustrates the architecture involved. In this case, the connection to the database is made from the remote computer. SuiteVoyager uses a connection string to send a data request to the data provider. The SuiteVoyager data provider web service queries the database remotely, formats the returned record set and sends it back to the portal using HTTP. For a large number of connection strings, it is recommended this architecture be deployed even on an Intranet, as it minimizes the work the SuiteVoyager Portal computer itself has to do. No matter how many people are connected to the portal, the additional base load on the control network, at a minimum, will be that of only one InTouch node in order to supply the data. Of course, any additional Wonderware applications that you install in order to provide more functionality, such as an IndustrialSQL Server computer, will increase the control network load. Thus, the required bandwidth on the control network for SuiteVoyager is application specific. It is very important that the control network can adequately handle the transport of data from the data source applications to the SuiteVoyager portal. For the client side, it is important to know of the number of clients that will access the portal, how fast their network connections are, and what type of information they will be accessing. The SuiteVoyager Portal can handle up to 300 concurrent users (hardware and Internet connections permitting) with data update rates of two seconds.

39 Networking Considerations 39 If the clients will be downloading and viewing browser-based windows, the download time will vary with the complexity of the screen, but should average no more than 12 seconds per screen at the maximum number of connected users. Also, the first time a client accesses a WindowSet, it will take around 1 minute at 56Kbps to download the necessary behavior and data access files. The time it takes to download ActiveX controls will vary with size and dependencies. For more information, see "Maximum Number of Concurrent Clients Supported" on page 39. Both the bandwidth for the client LAN and the bandwidth for the control network contribute to the total efficiency of data transportation from the factory floor to the desktop, and vice-versa. If you have an adequate control network, but the clients are downloading complicated browser-based windows over slow Internet connections, they will experience slow performance. Likewise, if the clients are downloading very simple windows over a fast intranet connection, but the control network lacks the bandwidth to supply data to the portal effectively, clients will also experience slow performance, but because of a different problem. Tip If your control network is not adequate and you are not able to upgrade it, and you do not have adequate bandwidth for the amount of users you are supporting, then you will want to consider aggregating and simplifying the information that they can obtain from the browser-based windows in order to optimize performance. There are many benchmarking tools available on the market to test your web site in advance. This will ensure that you will be able to provide the information to the clients that need it. Microsoft provides information about networking issues for the Internet and intranet environment on their web site ( as well as a tool to test your web site. For example, at the time of writing, the Web Application Stress tool is downloadable from their site and will simulate multiple requests from clients for browser pages. This will help you to benchmark performance information about your particular installation. Maximum Number of Concurrent Clients Supported As a rule of thumb, the following table describes the maximum number of concurrent users that can access the portal and retrieve information within an acceptable time frame using various access technologies: Technology Max. Concurrent Users 28.8K modem 5 56K dedicated digital K ISDN M T1 56 T3 4,500* ATM OC3 155 M 15,000* *SuiteVoyager currently supports a maximum of 300 concurrent users.

40 40 Chapter 3 Tested Performance Metrics This section describes the performance testing scenarios and results for InTouch process graphics (browser-based windows) and MultiViews. The following browser-based windows were used for the testing. Window Window 1 Window 2 Window 3 Window 4 Window 5 Window 6 Window 7 Window 10 Window 11 Window 12 Window 13 Window 14 Description Tag data for 75 tags, no expressions 75 tags, no expressions, four filling rectangles, four meters (one of each type) 75 tags, two expressions each (blinking and color change) 20 buttons on screen with tags on each button, no expressions 20 buttons on screen with tags on each button with one expression arranged in 5x4 grid with a frame around each column and a single frame around the entire grid 72 lights, 12 of each 12 switches, two of each; two sliders Tag data for 200 tags, no expressions Four real-time trends 60 buttons, 20 discrete input touch links, 20 analog input touch links, 20 string input touch links 64 graphical objects - rectangle, rounded rectangle, ellipse, polygon, 16 each 50 tags, no expressions 57 graphical objects - 51 lines, two H/V lines, two ellipse (orientation and fill color), one round rectangle (object size, location, and percent fill) 20 tags - blinking and color change The test scenarios are based on LAN access (10/100Mbps) and also dial-up access (56k modem). All testing was performed using Internet Explorer 6.0, for which SuiteVoyager comparison tests have consistently shown improved performance over Internet Explorer 5.5. Results for these scenarios are published in the following tables. Note that two successive columns indicate the first and second access times. This is because SuiteVoyager 2.0 implements local caching of WindowSets to improve performance.

41 Networking Considerations 41 LAN Access of Browser-Based Windows This following table shows performance results for access from three clients using Internet Explorer 6.0 across a LAN. W = Window D = Data Description Average Time to Load SuiteVoyager 2.0 (in seconds) Average Time to Load SuiteVoyager 1.0 (in seconds) Factor of Performance Change in SV 2.0 over SV 1.0 (SV2.0/SV1.0) 1st Time 2nd Time (cached) 1st Time 2nd Time (cached) 1st Time 2nd Time (cached) Browser-Based Windows W D W D W D W D W D W D Window Window Window Window Window Window Window Window Window Window Window Window

42 42 Chapter 3 LAN Access of MultiViews This following table shows performance results for access from three clients using Internet Explorer 6.0 across a LAN. Note MultiViews were not available with SuiteVoyager 1.0. W = Window D = Data Description Average Time to Load SuiteVoyager 2.0 (in seconds) 1st Time 2nd Time (cached) Four windows: One graphic screen (Window 2) IndustrialSQL Server - four tags, 100 values Alarms - historical, InTouch 7.11, 1000 records Alarms - current, 1000 records Five windows: One graphic screen (Window 2) One chart - 10 variables from 100 records One data table rows by 10 columns IndustrialSQL Server - four tags, 100 values Alarms - historical, InTouch 7.11, 1000 records W D W D

43 Networking Considerations 43 Dial-Up Access of Browser-Based Windows This following table shows performance results for access from three clients using Internet Explorer 6.0 across a 56 Kbps dial-up connection. W = Window D = Data Description Average Time to Load SuiteVoyager 2.0 (in seconds) Average Time to Load SuiteVoyager 1.0 (in seconds) Factor of Performance Change in SV 2.0 over SV 1.0 (SV2.0/SV1.0) 1st Time 2nd Time (cached) 1st Time 2nd Time (cached) 1st Time 2nd Time (cached) Browser-Based Windows W D W D W D W D W D W D Window Window Window Window Window Window Window Window Window Window Window Window

44 44 Chapter 3 Dial-Up Access of MultiViews This following table shows performance results for access from three clients using Internet Explorer 6.0 across a 56 Kbps dial-up connection. Note MultiViews were not available with SuiteVoyager 1.0. W = Window D = Data Description Average Time to Load SuiteVoyager 2.0 (in seconds) 1st Time 2nd Time (cached) Four windows: One graphic screen (Window 2) IndustrialSQL Server - four tags, 100 values Alarms - historical, InTouch 7.11, 1000 records Alarms - current, 1000 records Five windows: One graphic screen (Window 2) One chart - 10 variables from 100 records One data table rows by 10 columns IndustrialSQL Server - four tags, 100 values Alarms - historical, InTouch 7.11, 1000 records W D W D Deploying SuiteVoyager over the Internet SuiteVoyager can be deployed over the Internet. By default, SuiteVoyager is able to pass information through firewalls and through Microsoft proxy servers. Note Other proxy servers may require additional configuration. For more information on configuring proxy servers, see the SuiteVoyager Portal Administration Guide. Also, consult the documentation for the proxy server for exact setup requirements.

45 Networking Considerations 45 You will need to register the SuiteVoyager web server with an Internet Service Provider (ISP). The ISP will be able to assist you with implementation details, such as router configuration, Internet IP addressing, default gateway configuration, and a subnet mask, if needed. The following illustration shows a typical network layout for deploying SuiteVoyager over the Internet. Deploying SuiteVoyager over an Intranet If you are only using SuiteVoyager on your company intranet, the web server can be integrated into any existing TCP/IP network. You will need to consult with the Information Techology department about network configuration settings in order to determine how users will access the web server.