Metasys for Validated Environments (MVE) Installation and Platform Requirements

Transcription

1 Issue Date 2/7/03 TECHNICAL BULLETIN Metasys for Validated Environments (MVE) Installation and Platform Requirements Metasys for Validated Environments (MVE) Installation and Platform Requirements...2 Introduction...2 Operating System Support...3 Personal Computer (PC) Requirements...4 Software Requirements and Exceptions...5 M5 SAES or SAOS Specific Requirements...5 Installation Documentation References...5 Installation/Upgrade Sequence...6 Upgrade Notes...6 M5 SAES and SAOS Installation/M5 Upgrade Sequence...7 Facility Explorer for Validated Environments Installation Johnson Controls, Inc. Code No. LIT Software Release 5.2

2 2 Metasys for Validated Environments (MVE) Installation and Platform Requirements Metasys for Validated Environments (MVE) Installation and Platform Requirements Introduction IMPORTANT: Read this document before installing or upgrading any Metasys software. Metasys for Validated Environments (MVE) is a suite of products consisting of Facility Explorer for Validated Environments (FX VE) and M5 Secure Architecture Engineering/Operator Station (M5 SAES/SAOS). MVE is designed for applications in the Life Sciences industry, and more specifically, for configuration to Title 21 CFR Part 11 (electronic records/electronic signatures) requirements. For configuration to these requirements for your system, consult your local Johnson Controls representative for completion of Johnson Controls internal guideline Validated Environment (VE) Customer Questionnaire. Before you purchase or implement Johnson Controls software on your network or workstation, please keep in mind the following issues as you plan for this application s installation or upgrade: Make yourself aware of all Johnson Controls applications that reside on your network or workstations. Not all Johnson Controls applications and revisions of these applications are compatible with this revision of Metasys software.

3 Metasys for Validated Environments (MVE) Installation and Platform Requirements 3 The upgrade or addition of Metasys software may require the upgrade of other devices and or applications on the network or workstation. To determine if you have a conflict with or need to upgrade other applications when upgrading to or installing Metasys software, please refer to and use the Metasys Software Compatibility Matrix. You can find this matrix on The Advisor at: Operating System Support Table 1: Operating System Support Product Windows 2000 Professional with SP3* Facility Explorer for VE (FX VE) No Yes M5 Secure Architecture Engineering/Operator Station (SAES/SAOS) Yes M5 SAES /SAOS options: Metasys Data Yes Visualization (MDV), Metasys Historical Data Visualization (MHDV) M5 SAES only options: M-Alarm Multimedia Extension (MMX), M-Tool, Graphic Programming Language (GPL) * Indicates FAT 32 file system. Windows 2000 Server with SP3* No No

4 4 Metasys for Validated Environments (MVE) Installation and Platform Requirements Personal Computer (PC) Requirements Table 2: PC Requirements PC Component Description Recommended PC 1 GHz Pentium III class PC recommended (500 MHz Pentium class PC minimum) Recommended 512 MB Memory Hard Disk 30 GB - database server 8 GB - data collector, Web server 8 GB - M5 SAES/SAOS CD-R (W) Minimum 4x CD-R CD-RW - database server Video Memory Minimum 2 MB VRAM Tape Backup Device Windows software compatible, backup to floppy disks not supported Graphics Support SVGA Refer to Facility Explorer for Validated Environments (FX VE) Product Bulletin (LIT ) and M5 Secure Architecture Engineering Station or Operator Station Product Bulletin (LIT ).

5 Metasys for Validated Environments (MVE) Installation and Platform Requirements 5 Software Requirements and Exceptions The supported operating systems include: Windows 2000 Professional and Windows 2000 Server (Data and Web Server) with SP3. Windows 98, Windows NT, Windows XP and Windows ME operating systems have not been qualified. IMPORTANT: If you need to move from one operating system to another, do not upgrade your operating system. If you want a different operating system, start with a clean PC. M5 SAES or SAOS Specific Requirements Prior to beginning the workstation installation, install the Windows operating system, including the Transmission Control Protocol/Internal Protocol (TCP/IP). Installation Documentation References Table 3: Installation Documentation References Document LIT Number M5 Workstation Installation Technical Bulletin Operator Workstation Technical Bulletin M-Password for M5 SAES or SAOS Technical Bulletin Installing Facility Explorer for Validated Environments Technical Bulletin Converting AspenTech to Microsoft SQL Server 2000 Technical Bulletin Installing Microsoft SQL Server 2000 Technical Bulletin Metasys Historical Data Visualization Installation Bulletin LIT LIT LIT LIT LIT LIT LIT

6 6 Metasys for Validated Environments (MVE) Installation and Platform Requirements Installation/Upgrade Sequence When you are installing or upgrading Johnson Controls software products, we recommend following the installation/upgrade sequences described in this document. It is the only installation/upgrade sequence tested. Upgrade Notes IMPORTANT: Please read the following notes before upgrading any Metasys software. Consider the following when upgrading Metasys software: Installing software over a previous release of the software overwrites sample and template files. Back up those files before installing a new version of the product. Data files are not removed. Do not uninstall components with the Windows Add/Remove Programs feature. The M5 SAES/SAOS installation process performs the proper uninstall procedures. If you upgrade any of the Johnson Controls Metasys software on a Personal Computer (PC), you must upgrade all components on that PC to the latest release. Loading M5 SAES or SAOS is the equivalent of loading M5 Workstation Release 5.2, M-Graphics Release 5.2, and Metasys Person-Machine Interface (PMI) Release 12.01a software. Network Control Module (NCM) networks must be prepared to accept the requirements of all three of these components. For example, NCMs must have a minimum of 4 MB of Random Access Memory (RAM) and the N1 network must be Ethernet where installing M5 stations.

7 Metasys for Validated Environments (MVE) Installation and Platform Requirements 7 M-Authorize Table 4 describes when reauthorization is required after upgrading. Refer to the Upgrade Authorization form shipped with the software and Using M-Authorize Technical Bulletin (LIT ). Table 4: Reauthorization Requirements Upgrading From Upgrading To Reauthorize Required M5 Workstation Release 1.x M5 SAES or SAOS Release 5.2 Yes M5 Workstation Release 2.x M5 SAES or SAOS Release 5.2 Yes M5 Workstation Release 5.0 M5 SAES or SAOS Release 5.2 Yes M5 SAES and SAOS Installation/M5 Upgrade Sequence Notes: TCP/IP should be bound to the Ethernet adapter. If TCP/IP services have not been installed and bound before beginning the M5 SAES and SAOS installation, the installation stops after the system analysis procedure. Refer to Microsoft Windows online Help system or the Microsoft Windows 2000 Resource Kit. All existing configured workstations accessing Metasys N1 networks must upgrade to Metasys Release or later prior to installing M5 SAES and SAOS Release 5.2. Refer to the Upgrading the M5 Workstation on an N1 Network in the M5 Workstation Installation Technical Bulletin (LIT ).

8 8 Metasys for Validated Environments (MVE) Installation and Platform Requirements If you do not own one of the components listed, skip to the next component. 1. Install M-Tool software (System Tools). 2. Install Metasys PMI - required if connecting to NCM. Note: If you use the PREP-FOR utility, you must use it before you install the M5 SAES and SAOS software. 3. Install M5 SAES or SAOS (includes M-Graphics). 4. Install optional applications in any sequence: MDV, MHDV, MMX, GPL, and M-Tool software (Configuration Tools). Note: MMX, GPL, and M-Tools are only for M5 SAES. Facility Explorer for Validated Environments Installation Install FX VE as outlined in Installing Facility Explorer for Validated Environments Technical Bulletin (LIT ). Controls Group 507 E. Michigan Street P.O. Box 423 Release 5.2 Milwaukee, WI Printed in U.S.A.