Thank you for choosing Monitor Pro^®7.6, the newest addition to the Monitor Pro family of products. Monitor Pro 7.6 is a new version that targets industries that require secure environments. The 7.6 version also contains new features for redundancy and e-mail notifications.

Whether you are a first-time user or a current Schneider Electric customer, we are pleased to have you as part of our Schneider Electric family. We welcome this opportunity to work with you and look forward to a mutually beneficial, long-lasting, and satisfying relationship.

This document contains information on the new features of Monitor Pro 7.6 and some late-breaking news.

II. NEW FEATURES

OFS Installation by Monitor Pro

The installation of OFS components (OPC Factory Server, OFS Remote, and Configuration Tool) is included as an option during the installation of Monitor Pro. OFS can also be installed as a standalone system. If an OFS component is selected, the installation program checks to see if the component is already installed. If the component is already installed, a message displays that states the component is already installed on the machine and will not get reinstalled.

Unity Pro Browser

The Unity Pro Browser is a configuration tool that gives the user an easy way of configuring Monitor Pro tags based on Unity Pro variables. This is done by directly connecting to a Unity Pro project or by importing a Data Exchange export file. The Unity Pro Browser tool is in the Device Interfaces folder in the Configuration Explorer. You can also run this tool from a command line.

PLC Diagnostic Viewer Enhancements

The Diagnostic Viewer (DiagViewer) can now obtain PLC diagnostic data by interfacing with the OFS Server (version 3.20 or later). For each PLC, you can specify one of the following connection types:

· OFS + Unity Pro PLC

· OFS + Premium PLC

· TECOM + Premium PLC

New fields (Alias and Connection Type) were added to the Diagnostic Viewer configuration, as well as a new child table specific to the OFS connections.

The Starter Application Customizer was updated to automatically add a Diagnostic Viewer / OFS configuration to an application, if desired. The Client Builder Examples project was also updated to use the new OFS field as well as TECOM.

Note: Do not configure simultaneous OFS and TECOM connections to the same zones in the same PLC. Doing so may lead to incorrect alarm lists.

If the DiagViewer task is shut down from RTMON or by setting its shutdown tag, it will send a request to AL_LOG to purge the diagnostic alarms from the system. This does not take place if the DiagViewer is stopped abruptly, such as from the Task Manager.

21 CFR Part 11

The United States FDA regulations for Electronic Records and Electronic Signatures (21 CFR Part 11) define the requirements for systems that provide Pharmaceutical Products for the United States.

No software vendor can declare compliance with the regulations; rather, each application must be reviewed, audited, and qualified to declare compliance with 21 CFR Part 11. As a software vendor, the focus is to provide features, tools, and techniques that make the creation of a validated system easier. Our approach is to provide extensions to the product so that they benefit development of applications to be validated.

The HMI/SCADA application is just a part of the entire manufacturing operation. Some features must be provided by the HMI/SCADA software; other features are provided by company procedure and by the internal IT department guidelines.

With the implementation of requirements for 21 CFR Part 11, Monitor Pro has made it easy for developers to build compliant applications with no scripting or special utilities. The Monitor Pro enhancements include:

User Authentication

· Single or Dual Authentication  Any changes made by the operator using Client Builder animations, Client Builder scripts, or the Database Browser Control

· User selected or entered reason code  The audit trail can record the reason for the operator’s change. Reasons can be selected from a list or optionally entered by the operator.

Password Management

· Centralized password management by the IT department

· DOD (department of Defense) password pattern requirements, such as case, special characters, and length

· Aging of passwords

· Capability to change a password online

Audit Trail

· In addition to recording the operator changes, the operator event log can record the second authentication signature and the operator’s reason code.

· Logging activity can record all Database Browser changes in addition to the real-time database changes, and it can be used from scripting to record events as necessary.

Redundancy Improvements

The redundancy module, VRN, was released with Monitor Pro 7.0++ and became part of the base package in version 7.2. For the 7.6 release, we include extended functionality for both the server and client to make redundant systems easier to build and manage. New features in this area include:

Redundant license management for CALs between servers
Client Builder now allows for the searching of multiple license servers to ensure that all of the CALs purchased are available
VRN application object in FLNEW templates in the Application Setup Wizard
New VRN tag, VRN_CONTROL, that can be used to disable various functions on the backup server
Database Logger now has a new disable tag for logging functions on the backup server
IOXlator and RAPD drivers can use mailbox redundancy for efficient and easy redundant tag transfers between servers
New application object, FLVRNSetup, used to set up redundancy

One-Click Client

One-Click Client combines the best features of WebClient with .NET Client that allow a client to be installed by anyone in the organization. For the corporate user, one-click client provides the ability to build install scripts so that each installation is identical and automatic.

One-Click Client is a wizard that provides the capability to install a client on a remote system on the LAN, WAN, or VPN to access Monitor Pro information. The functions of this wizard include:

Quick installation of client to a client machine
Cached mimics on client (auto updated)
All functionality of Client Builder at run time
Creates icons on the desktop
Customizable for corporate deployment
Easy to maintain

E-mail Alarm

E-mail alarms functionality is an integrated part of the Alarm System on the server computer. Alarms can be sent to Client Builder as well as to e-mail recipients on time-based schedules. E-mail alarm recipients can acknowledge the alarm remotely using a computer or Internet-enabled cell phone via Internet standard POP3 and SMTP e-mail systems.

Redundant Licensing

Redundant Licensing provides an automatic means for clients to fail over to backup license servers if the primary license server fails. This feature also provides the synchronization of Client Access Licenses (CALs) between a pair of redundant license servers. Users can purchase various systems and consolidate their licenses to obtain a more effective client-server use of their systems.

Redundant licensing can be configured for client operation and license server operation. This feature accommodates various licensing scenarios:

A single system without redundant licensing
Multiple application servers without redundant licensing
Redundant system
Complex servers (combination of multiple application servers without redundant licensing and a redundant system)

The Monitor Pro License Utility is used to define the client license server(s) and designates the license server to use redundancy.

Alarm Viewer Enhancements

The following enhancements were added to the Alarm Viewer:

The capability to trigger events by single-clicking or double-clicking an alarm row in the viewer
The number of unacknowledged alarms to the Alarm Viewer status bar along with the existing total number of alarms
The displaying of the server name on the status bar
The capability to customize the Alarm Viewer column headings
New display attributes
The capability to set operator permission security options
Automatic resizing of the toolbar when it is modified during run time

Historical Reports

The Historical Reports provide secure access to electronic data through standard reports to match the most stringent requirements of regulatory applications. Standard reports cover the basic requirements of 21 CFR Part 11, the FDA guidelines for trustworthy electronic records. Monitor Pro provides the security and access control necessary for companies to ensure the authenticity, integrity, and confidentiality of their electronic records.

The Historical Reports include the following features:

Streamlines regulatory reporting to save time and reduce errors through report templates that feature common regulatory reporting requirements.
Automates standard reporting by enabling users to quickly compile change histories, issue detail reports, and more.
Allows users to create ad hoc (user-defined) reports to suit their needs by selecting a template report from a list, set constraints, and other items to suit unique needs.
Allows operator, alarm, and data logs to keep track of all events that happen in a process, from tracking when samples were run, to logging any errors such as equipment failures.

Note: For this release, the Historical Reports are available in English only.

Waveform Generator and Sequencing Task

A new module provides two important functions for system qualification and commissioning. The first is the ability to generate various waveforms to simulate changes in process variables. The second function is a sequencing module to drive digital events based on steps.

The Waveform Generator and Sequencer (FLWAVE) task provides features for simulating real-world data for the purpose of testing, training, and commissioning of Monitor Pro applications and operator stations. The task is divided into three functional areas:

· continuous waveform generation

· event-driven output curve

· event sequencing

Configuration tables are used to establish the simulation. The FLWAVE task uses function generators to simulate factory floor data. The functions simulate continuous output devices.

In Client Builder, an operator can see a snapshot of the waveform as if it were generated from a real device connected to a PLC.

This new module is in the Other Tasks folder in the Configuration Explorer.

General Enhancements

· Application object creation performance improvement

· Security information exposed in VBA

· Support for the SQL Date format for Alarm Logger

· Toolbars can be turned off on run-time clients

· Updated Examples Application (called StarterApp in previous releases) and FLNEW applications with new application objects

· Monitor Pro License Wizard enhanced to provide incomplete/inaccurate visual recognition for the entry of the serial number and configuration sequence and to include an entry for the licensed Company Name, which must be specified when Monitor Pro is authorized

· Updated and reorganized documentation

III. INSTALLATION

Minimum Hardware and Software Requirements

Minimum hardware and software requirements for Monitor Pro 7.6 are published in the Installation Guide. While the software will run on these minimum requirements, they may not be adequate for satisfactory performance on some systems, especially larger, complex systems. Because it is impossible to define the exact requirements for each system due to the flexibility and scalability of Monitor Pro and other layered software involved, we prepared additional guidelines to help you select the “best estimate” of system requirements. Your exact requirements may differ slightly from these guidelines.

Hardware Requirements

· CPU: Pentium III 500 MHz (or better)

· CD-ROM drive for installation

· 256 MB RAM

· XVGA Monitor and graphics processor (1024 X 768, with at least 65K colors)

· Keyboard and Windows compatible mouse

· Hard drive space: 1 GB or larger for a Monitor Pro Client, 2 GB for a Monitor Pro Server. More space is required if you plan to install Microsoft SQL Server 2000 or to keep a large amount of historical data.

Note: These minimum requirements may not be appropriate for your particular application. Please contact your authorized Schneider Electric reseller or representative to discuss recommended hardware and software for your specific needs.

If you install Microsoft SQL Server 2000 on the same machine as the Monitor Pro Server, then you should consider using a dual processor Pentium and increasing the memory by at least 64 MB RAM.

For additional information on SQL Server 2000 requirements, search the Microsoft online MSDN Library at: http://msdn.microsoft.com/library.

Software Requirements

· One of the following Microsoft operating systems

o Windows 2000 Professional with SP4

o Microsoft Windows XP Professional with SP2

o Windows 2000 Server with SP4

o Windows Server 2003 with SP1

· Internet Explorer 6 with SP1

· Adobe Reader 5.0 or later (for viewing documentation)

· TCP/IP network protocol must be installed

Supported Layered Products

· Compiler (only required for PAK or CML)

o Microsoft Visual Studio .NET

o Microsoft Visual C++ 6.0

· Database Management

o Microsoft supplied Oracle 10 ODBC Driver

o Microsoft Access 2003, XP, or 2000

o Microsoft SQL Server 2000 with SP4

o Oracle 10

o Sybase System 12 ODBC Driver

· Drivers

o RSLinx OEM version 2.42

o MBX Driver Suite, version 4.20.02 SP2

o Unitelway WDM driver V1.4

o XWAY TCP/IP Win32 Driver 1.6

o ISAWAY PCX57 v1.2

o FIP PCMCIA FPP20 v1.2

o SCP114 PCMCIA v1.1

o FIP FPC10 DRIVER v1.2

o ETHWAY V2.6

Installing/Updating Databases

It is recommended that you use Microsoft SQL Server 2000 as the primary database and that you install it before installing Monitor Pro. SQL Server is not required on the same computer as Monitor Pro. Monitor Pro 7.6 is shipped with Microsoft SQL Server 2000 Standard and Personal editions. Monitor Pro 7.6 is qualified on SQL Server 2000 Enterprise; however, if you want to use this version of SQL Server, you should obtain it from Microsoft. Detailed instructions to install Microsoft SQL Server 2000 as your primary database are provided in the Installation Guide.

Microsoft SQL Server 2000 Memory Size Setup

After Microsoft SQL Server 2000 is installed, you need to set a maximum memory limit to prevent SQL Server from consuming all the memory available to it and to ensure the operation and speed of Monitor Pro tasks.

From the Windows Start menu, select Programs > Microsoft SQL Server > Enterprise Manager.
In the Console Root window, navigate to SQL Server Group folder. Right-click your host server name and select Properties.
In the SQL Server Properties (Configure) dialog box, click the Memory tab. Click Use a fixed memory size (MB) and use the slider to set the Microsoft recommended memory size in the range of 40 to 80 MB, depending on your system’s RAM and virtual memory size.
Click OK and close the window.

Security Event Logging Table

Monitor Pro 7.6 has expanded the functionality of the Security Event Logging to include new columns that provide for the 21 CFR Part 11 Electronic Signatures requirements.

If you want to retain your current historical log of operator events, you need to update the Security Event Logging Schema and OperLog table in your SQL Server. Perform the steps below to add the new columns to the existing table without loosing historical information.

If you do not need to save the historical logging information, the Security Event Logging Schema must be updated and the OperLog table needs to be dropped from your current historical database.

Note: An easy way to update your application table is to copy the Security Event Logging Schema table from the new Examples Application into your application. You will still need to manually delete (drop) or update the OperLog table in the database.

If you intend to use security event logging in Client Builder, you must add new columns to the security schema.

Open Configuration Explorer. In your server application, open Data Logging > Database Schema Creation > Security Event Logging Schema.
Add the columns shown here to the security schema table.

	Column Alias	Column Name	Column Type	Length or Precision
1	TMSTAMP	TMSTAMP	DATE
2	OPERNAME	OPERNAME	CHAR	16
3	OPER2NAME	OPER2NAME	CHAR	16
4	CLIENT	CLIENT	CHAR	20
5	EVNTYPE	EVNTYPE	CHAR	16
6	EVNTMSG	EVNTMSG	CHAR	64
7	TAGNAME	TAGNAME	CHAR	48
8	OLDVALUE	OLDVALUE	CHAR	32
9	VALUE	VALUE	CHAR	32
10	REASON	REASON	CHAR	40

Operator Log Table

Due to new columns in the Operator Log (OperLog) table, it is necessary to replace or update the table in SQL Server.

If you do not have an OperLog table that you want to keep, delete (drop) the table and Monitor Pro will recreate it with the new columns as defined in the Security Event Logging Schema table.

If you have data that you want to preserve, perform the following steps using the Microsoft SQL Enterprise Manager to add the new columns to your table.

Open the Enterprise Manager and then expand the tree to your database tables.
In the right pane, right-click your OperLog table and select Design Table.
Right-click on the row where you want to insert the information for a new column and select Insert Column. A row is inserted above the row you clicked.
Enter the column name, data type, and length in the new security schema table shown above. Select Allow Null to enable it.
If you want the existing data to populate with a default value, enter a value in the Default Value field in the list of properties at the bottom of the screen.
Repeat steps 3 to 5 to define other new columns.
Press SAVE and close the Enterprise Manager.

Installing Monitor Pro 7.6

You can install Monitor Pro as either a Monitor Pro System (client and server on the same machine) or a Monitor Pro Client (client only).

In this release, the License Wizard was enhanced to provide a visual recognition during the entry of the serial number and configuration sequence (provided in Exhibit A of your Monitor Pro shipping package). Any incomplete or inaccurate information displays in red. The License Wizard now includes an entry for the licensed Company Name. The name specified in this field must also be specified when Monitor Pro is authorized.

Detailed information is in the Installation Guide. This document is available on the Monitor Pro CD and can be viewed from the installation Flash startup screen.

Uninstalling Monitor Pro and OFS Components

You uninstall Monitor Pro components and the OFS using the Windows Installer program.

From the Windows Control Panel, open the Add or Remove Programs component.
In the currently installed programs list, select the desired program to uninstall, and click Change/Remove.

o Telemecanique, Monitor Pro Version 7.6

o OPC Factory Server

o OPC Configuration Tool

When the installation wizard opens, select Remove and click Next. At the confirmation message, click OK.
After the program is uninstalled, click Finish.

Note: You may be asked to reboot your machine after uninstalling the components.

IV. DOCUMENTATION

In this release, the documentation was reorganized under a functional methodology so that users can find the reference information quickly. The legacy documentation was merged into the main documentation set, and an index with links was created that opens to desired topics in the PDF files.

The Monitor Pro Documentation folder that was installed on the desktop of previous versions of Monitor Pro is replaced with a Monitor Pro Documents icon. When this icon is double-clicked, the Monitor Pro Documents file opens providing links to the documents and Help files. Clicking the View Index by Topics button opens the master index that provides links to specific topic locations in the documents.

The documentation is installed in the Telemecanique\Monitor Pro\Documentation directory, in three languages English, French, and German. These three versions can be accessed from the English, Francais, and Deutsch subdirectories. The documentation is in PDF format, which you can view using a PDF viewer, such as Adobe Reader. If you do not have a PDF viewer installed, you can install Adobe Reader from the Monitor Pro CD or from http://adobe.com/products/acrobat/readstep2.html.

Note: For this release, the documentation is available in English only.

V. MISCELLANEOUS ISSUES

Upgrading from Previous Releases

Existing DiagViewer applications must be converted before they can be used with Monitor Pro 7.6.

Please see the Conversion Guide for information about upgrading from previous releases.

Drivers

Updated RAPD Drivers

Prior to Monitor Pro 7.6, RAPD drivers used IMX libraries. With this release, Monitor Pro uses the MCI libraries. If you have written custom RAPD drivers, you need to update your drivers in order to compile with the MCI RAPD PAK. Conversion instructions are provided in the appendix of the Programmer’s Access Kit (PAK) guide.

Modbus TCP Interface

If you want to use exception writes with the Modbus TCP interface, it is necessary to configure at least one read table. This issue will be addressed in a future release.

FIPWAY

Under a very heavy load, communication issues can appear using a FIPWAY PC card and OFS.

Legacy Drivers and Add-Ons Removed

The following legacy drivers and add-ons are no longer supported and have been removed from the Configuration Explorer and the documentation:

Telemecanique File Transfer
Ethway Series 1000 Communication Interface
JBUS Series 1000 Communication Interface

Historical Reports

The Historical Reports feature requires MDAC version 2.7 or greater installed. To obtain this update, see the Microsoft web site: http://www.microsoft.com/downloads.

Unity Pro Browser

When the Monitor Pro development server and the Unity Pro server are installed on different systems, you need to install the Unity Pro client (UnityProClient.msi), available on the Unity Pro installation media, and then configure additional DCOM settings for the Unity Pro server and client. Refer to the DCOM Configuration section in the OPC Factory Server User Manual, “OFS Server installation” chapter.

VRN Configuration

Adhere to the following best practices when using the Exclude, Include, ExclGlobal, and InclGlobal arguments in the Client Object Information table. When using these arguments, it is important to order your entries in such a way that no entry will result in negating a previously defined entry. The following guideline describes the best practice rules:

Define wildcard entries that you want included first. If the entry is to include everything (example, the Tag/Item is '* ), it is considered best to use the ExclGlobal argument to exclude the system and global tags from the VRN connection.
Define specific items/tags that you want to Include. The Include argument is not required because it is the default.
Define specific items/tags that you want to Exclude. The Exclude argument is required on the first item to be excluded, but is optional on subsequent entries because the first excluded item is now the new default mode.

Client/Server Networking

If your network does not have a DNS server, it is recommended that you use static IP addresses on all your Monitor Pro server and client computers.

Note: Schneider Electric suggests that you not edit the Windows hosts file while a Monitor Pro application is running.

On the Monitor Pro server(s), add the IP address and computer name of all the Monitor Pro clients and servers, if you have multiple servers, to the Windows hosts file.
On each Monitor Pro client, add the IP address and computer name of all the Monitor Pro servers to its Windows hosts file.

If you experience Monitor Pro client connection problems and you have a DNS server, it is recommended that you put the Monitor Pro server(s) IP address and computer name in the Windows hosts file on each Monitor Pro client computer. If all your Monitor Pro computers have static IP address, perform the steps above.

TCP/IP Ports and Port 8000

Some IT tools search for holes in security and check for attacks on various TCP/IP ports. These tools may cause problems with the Monitor Pro license system if port 8000 is shared with other software. There is no “safe” port to monitor for license checkout. If a port 8000 conflict occurs, move the Monitor Pro license server to a user-defined port number. Non-Monitor Pro requests to port 8000 are filtered, but it is possible that something might make the license system fail. Check with your IT department for details about your network.

Third-Party Software

Monitor Pro is tested on many versions of Windows operating systems, in multiple languages, and with many other non-related software packages installed on the same computer. While software developed by other companies, such as third party OPC clients, may work with Monitor Pro, Schneider Electric cannot guarantee that all such software will function correctly. For example, one version of Norton anti-virus software had a conflict with Monitor Pro. When the anti-virus software was upgraded, the incompatibility was resolved. It is impossible to test every combination of every software package available on the market today. We have found very few incompatibilities, but we cannot guarantee compatibility with all software developed by all developers. Please see the license agreement for more information about third-party software. Schneider Electric disclaims any and all warranties, conditions and representations (either express or implied), with respect to third-party software.

VI. COPYRIGHT NOTICE

Monitor Pro is a registered trademark of Schneider Automation SAS. Windows is a registered trademark of Microsoft Corporation. Tecnomatix and FactoryLink are registered trademarks of UGS Corp.