Release. Notes. Version: 2.1

Transcription

1 MFCS / win Release Notes Version 2.1 Sartorius BBI Systems GmbH File: ReleaseNotes_215_C.doc Schwarzenberger Weg Version: 2.1 D Melsungen Date: March 2006 Tel. +49 (5661) Printed in Germany Fax +49 (5661) mfcs.service@sartorius.com

2 CONTENTS ABOUT RELEASE NOTES...4 IMPROVEMENTS...4 IMPROVEMENTS FOR SP IMPROVEMENTS FOR SP CUSTOMIZED SOFTWARE...8 SOFTWARE MODULE 21CRF PART DATABASE INTERFACE SUPPORT...11 BIOSTAT B PLUS AND ETHERNET...12 BIOSTAT B PLUS AND RS422/RS POWER FAILURE HANDLING...14 INTRODUCTION...14 BIOS SETTINGS...14 UPS INSTALLATION AND CONFIGURATION...15 Power Protection Strategy...15 Device Settings...16 Shutdown Sequence...16 Power Failure Settings...18 POWER OPTIONS...19 INTRODUCTION...19 POWER SCHEME...19 HIBERNATION...20 CHANGE HISTORY DIALOG...21 INTRODUCTION...21 CHANGE HISTORY DIALOG APPEARS WITHOUT CHANGES...21 UPDATING MFCS CONFIGURATION...22 INTRODUCTION...22 WHICH CHANGES DO NOT REQUIRE UPDATE CONFIGURATION?...22 USER CONFIGURATION...23 NEW OPERATOR RIGHT DELETE BATCHES CFR PART 11 OPTION CFR PART 11 OPTION HAS BEEN DISABLED...24 EXTENDED DCU COMMUNICATION...25 DOWNLOADING ALARM LIMITS...25 WINDOWS CONFIGURATION...26 FAST USER SWITCHING...26 SETTINGS FOR WINDOWS XP SERVICE PACK2 AND WINDOWS SERVER 2003 SP1 OR R Integrated Firewall...27 Automatic Updates

3 Security Settings for MFCS_win Folder and MFCS_win Share...29 ACCESS RIGHTS ON MFCS/WIN WORKSTATIONS...30 ACCESS RIGHTS TO THE MFCS/WIN TASKS DIRECTORY...31 SHUT DOWN OF WINDOWS...32 MFCS/WIN INSTALLATION...33 INSTALLATION WITHOUT FLOPPY DISK DRIVE...33 COMPUTER NAME LIMITATION...34 FILE DELETION DURING INSTALLATION...35 END OF SUPPORT FOR WINDOWS NT...36 DATA STORING MODULE (MFCSSTO)...37 CONSIDERATIONS REGARDING BATCH DATABASE LOCATIONS...37 ENHANCEMENTS OPC DA SERVER...38 Start Batch...39 Batch Setup...40 Define Batch [S88]...41 INI-FILE SETTINGS FOR BATCH NAME GENERATION...42 ADDITIONAL PROPERTIES FOR ALARM STATUS

4 About Release Notes The MFCS/win Release Notes contain information that either is missing in previous versions of the MFCS/win manuals or news about MFCS/win Service Packs. Service packs include improved versions of the MFCS/win software modules for the actual MFCS/win release. They usually are free of charge if downloaded from the BBI homepage from the Internet ( Improvements New functions 1. Audit Trail for changes All changes of the configuration of the MFCS/win system are written into a protected audit trail database All changes at process-relevant parameters are logged in the batch database Audit Trail Reports 2. New User Management Windows users will be linked to an MFCS/win user group The security profiles are divided into Application, Operation and Configuration Rights, which are subdivided in approximately 30 elementary rights. 3 pre-defined user group profiles for Administrators, Configurators and Operators A local user with administrator rights, is assigned to the group Administrator in the MFCS/win user management automatically 3. Storage of the time as GMT time Internal time format is GMT Conversion into local time by operating system routines No more gaps in the case of summer/winter time adjustment 4. Kernel modules run as Windows service Service starts automatically Logging out and in with another user, without interrupting data recording. Data acquisitions starts automatically without a user logged in. 4

5 5. Batch related Info fields 10 Input fields Can be displayed in the batch directory list Will be printed in the Batch Ticket Report 6. Automatic actions during batch finish Creation of the averaged data Start of the MS Access database function Compact Database, in order to optimize the size of the batches database. 7. Prompts on Workstations and Server Sends a message to all users logged in MFCS/win workstations and servers. After confirming the Prompts the recipe continues. 8. Reading from archived batches from CD Batches can be written with Direct CD to CD (archived) and afterwards the session can be closed. If the batch database will be not found on hard disk, then MFCS/win searches automatically in the archive path of the batch. 9. System Utilities / System Security Check This new utility examines whether the operating system attitudes for MCS/win in view to security are correctly adjusted Improvements for SP 3 New functions 1. Storage Control Module Since MFCS/win Service Pack 3, MFCS/win provides a control module for the Data Storage Module: The MFCS/win Storage Control module (MFCSSTC) ensures, that data will be written by the MFCS/win Data Storage module. It behaves as a watchdog program that cyclically reads the databases of running batches and verifies that data is stored. In case that the Storage module hangs, STC sends a shutdown message to it and generates an alarm. The Storage module will then be restarted by the MFCS/win Loader. For instructions about activation and usage of the MFCSSTC refer to the handbook MFCSSTC.pdf in the directory :\MFCS_WIN\USERDOCU. 5

6 Improvements for SP 5 New functions 1. Terminal Server Option Terminal Servers can act as MFCS/win Workstations and support multiple Terminal Server client sessions that use the MFCS/win Shell running on the Terminal Server. The Terminal Server can therefore act as a Gateway between the corporate network and the production network, with all MFCS/win Users establishing workstation connections to the MFCS/win Server from the Terminal Server. When performing actions that are usually logged (Audit Trail related actions, Batch Starting/Stopping etc.) from a Terminal Server session, the client computer name that connects to the Terminal Server, and the username used to login to the Terminal Server are used to log the respective actions. To use the Terminal Server Option from multiple Clients, a new dongle for enabling this option must be purchased from Sartorius BBI Systems. 2. Off-Line Shell It is now possible to start the MFCS/win shell in off-line mode if no on-line connectivity is needed. As the Off-Line Shell doesn t log in to the MFCS/win kernel, there is no limitation to the number of Off-Line Shells. Therefore, no MFCS/win connection will be occupied, even if more connections to MFCS/win would be possible: The Off-Line Shell and On-Line Shell can be used simultaneously. The number of network users (e.g. 5) will not be reduced by using the Off-Line Shell. 3. Batch Report To support multiple users on a Terminal Server using the same MFCS/win installation, session-specific directories in the :\MFCS_WIN\TASKS directory are created to store the userspecific batch reports. These directories are named after the client computer from which the user connects, and are not deleted after the user disconnects so that the user can use his settings for future reports. This behavior will also be used on MFCS/win servers. 4. Communication Watchdog The new MFCS/win Communication Driver Control Module (MFCSCDC) will be delivered with this Service Pack. This module may be used as a watchdog, to monitor the communication driver, which is used for the communication between MFCS/win and control units and may be installed separately. The necessary files can be found in the MFCS_WIN\DRIVER SETUPS folder. 5. DCU Logbook Alarming It is now possible to optionally use the Alarm Messages sent from Control Units, instead of generating alarms in the MFCS/win System. These DCU Logbook Alarms contain the time, the message and process value of the alarm as it happened at the DCU instead of the time when the respective alarm was sent to MFCS/win. 6

7 6. Improved Robustness in Large-Scale Environments Starting with Service Pack 5, the MFCS/win Kernel (MFCSMRD) now handles a greater amount of system connections. This leads to an improved robustness in large-scale environments with a great amount of connected control units, users, and add-on modules. In the past, some errors may have occurred if the maximum number of system connections was reached, which leads to system instability. This number has been raised. Additionally, an alarm message will be reported if the current number of system connections reaches a critical level (i.e.: 80% of the maximum), allowing the operator to plan a system restart before further errors may occur. 7

8 Customized Software Customer specific software like mimic displays, communication drivers or other applications need to be adapted to the current version 2.1 of MFCS/win before usage. The main reasons for that are: The MFCS/win kernel is running as Windows Service. Modules belonging to that design have to be adapted too. Changes are made in MFCS/win in view of CFR 21 part 11 compliance, especially internal structures and database changes, have to be considered. For adaptation of such software, please contact us under: 8

9 Software Module 21CRF Part 11 MFCS/win 2.1 supports all technological requirements to apply full compliance with the FDA rule 21 CRF Part 11. The Software Module 21 CRF Part 11 allows access to all related features which have been implemented within MFCS/win like User Management Security Profiles Audit Trail After a new installation, the Audit Trail, User Manager and Security is disabled as in the Basic Version. The MFCS/win Configuration Manager is the entry point to configure these features. Please refer also to the System Manager s Handbook, chapter User Configuration. If the system has found the Software Module 21 CRF Part 11, then the User Manager and Security can be enabled via menu Maintenance / Audit Trail / Enable / Disable Security 9

10 The User Management and System Security are linked together and can be activated inside the following dialogue. User Management disabled enabled MFCS/win will not check security aspects, each on Windows logged-on user has all rights without any restriction. The built-in security is active and uses the configured security profile for user actions. Without configured user and security profile, all modules are disabled inside the Shell. If the User Management will be enabled for the first time, then no User is configured. The current active user who has enabled the User Management will be added automatically to the pre-defined Administrator Group. 10

11 Re-Identification For actions that require an electronic signature the user is forced to identify himself with username and password. This belongs to all batch related actions influencing the batch status: Start, Setup, Initialize, Synchronize, Finish, Review, Approve, Archive and Restore. disabled enabled The user re-identification is not active. User re-identification will be forced. The user is forced to identify himself with user name and password. Database Interface Support MFCS/win 2.1 uses DAO 3.6 with Jet Engine 4.0 as database interface. Because Microsoft has improved this database interface, we strongly recommend to install the Service Pack 8 for the Jet Engine 4.0. For convenience, we have placed this Service Pack 8 on the MFCS/win CD-ROM. Please note, this Service Pack 8 is different for operating system platforms and languages. For installation, please use the correct executable, located on the MFCS/win CD in folder: Support\Jet_40_SP8\Jet_40_SP8_for_W2K Support\Jet_40_SP8\Jet_40_SP8_for_XP Windows 2000 Professional Windows XP Professional For already installed MFCS/win systems, you may find detailed information and download section about this Service Pack 8 on the Microsoft web site. (German) (English) 11

12 Biostat B plus and Ethernet Recently, Sartorius BBI Systems has presented the new Biostat B plus Bioreactor System. The digital measurement and control unit is equipped with an Ethernet communication port and the implemented communication protocol is a sub-set of DCU- Systems. Within MFCS/win Version 2.1 Service Pack 3, the MFCS/win Ethernet communication driver has been improved to handle also this new bioreactor generation. To decide between both control unit types, in MFCS/win a new control unit type like [DFC Ethernet] is required. Because this can be realized only in a new software version of MFCS/win, a straight forward solution has been realized. During start-up, the driver is searching for a new key inside the MFCS.INI file and enables the handling for the Biostat B plus if the key was found. Key Specification: [MFCSDED] CU1=DFC (Section for Ethernet Driver) where the number specifies the control unit ID from the MFCS/win configuration Configure Control Units In case you need to connect a Biostat B plus, please add this key manually inside the MFCS.INI file as specified above. Without such a key, the driver is using the DCU communication protocol. In case that a Biostat B plus is connected without such a key, an error message will be generated. 12

13 Biostat B plus and RS422/RS Information Systems with DFC4 and Touchpanel are able to communicate to Host via RS232 and RS422. Default setting is RS422 for systems with LCD operator panel. RS232 for systems with Touch-Panel. To change from RS422 to RS232 and vice versa follow the following instructions. 2. Software settings 1. In menu Maintenance of Biostat B plus choose the option External settings. 2. The used interface can be chosen by pushing function Host and then select one of the following options RS232, RS422, Ethernet. 3. After the changes have been made the system informs to set jumpers on the DFC4 board and perform a system reset. Press OK and switch off the system. 3. Hardware settings 1. After opening the right side plate you have to set seven (7) jumpers on the DFC4 board. RS422: Set jumper S1600 S1606 to position 2-3. RS232: Set jumper S1600 S1606 to position After power on the system will work with the new settings. 13

14 Power Failure Handling Introduction An uninterruptible power supply (UPS) is a device connected between a computer and a power source to ensure that electrical flow is not interrupted. UPS devices use batteries to keep the computer running for a period of time after a power failure. UPS devices usually provide protection against power surges and brownouts. Spikes, surges, sags, and noise will be removed from the power supply. A running UPS service supervises the status of a connected UPS device. In case of a low battery event, the service provides an automatic shutdown sequence to turn off the computer in a safety defined way, even if nobody is present to do anything on the PC: Executes a defined command file to support a shutdown of additional software packages like a MFCS/win SCADA-System, just a few minutes before the operating system will be stopped. Triggers Windows to perform a safety shutdown, before the battery flow stops. The fundamental purpose of a UPS is to protect your computer equipment and to avoid possible operating system problems caused by the power going out suddenly to the PC. BIOS Settings The BIOS of your MFCS/win computer may provide a section Power Management where you can specify how the computer shall react after a power failure and if the system shall use a low power mode or not. Please enter the BIOS, for our currently standard Dell PC press function key F2 direct after power on your computer and configure the following settings: AC Power Recovery = On Low Power Mode = Disable The computer will automatically restart after the power comes back. This is an important setting, even if the power failure happens during the night and nobody is present. All components e.g. the hard disk, are always on. After changing the parameters do not forget to save all settings. For different computer systems, please refer to your system documentation how to enter the BIOS and evaluate if there is a similar function available. Please contact your system administrator in case of further questions. 14

15 UPS Installation and Configuration If you have purchased a new computer from Sartorius BBI Systems, then the delivery includes a Smart-UPS from manufacturer APC. For your convenience, the UPS installation is already done. To login to the APC PowerChute software, please use the following settings for identification: User Name Password apc apc To install the APC PowerChute software, please refer to the APC installation instructions and follow the dialogues appearing on the screen. The following is a briefly configuration description about the most important settings. All of them can be adapted also after installation is done. Power Protection Strategy The power protection strategy selects how the system responds to power and UPS hardware failures. Open from menu Tools / Change Configuration Profile and choose card Power-Protection Strategy. Set this option to Maximize Runtime as shown below. This allows MFCS/win to run as long as the battery is able to power the machine. Small power failures will not influence the data acquisition and MFCS/win can continue until the battery capacity becomes empty. 15

16 Device Settings The UPS device properties can be configured by a click with the right mouse key on the shown host within the APC PowerChute list. Within the device properties the power failure options and shutdown sequence will be configured. Shutdown Sequence The shutdown sequence specifies how the system will be stopped in case that the battery reaches the Low-Battery-Threshold. The low-battery-threshold is set to initiate a shutdown when only five minutes of runtime remains at the UPS. However, if the time needed to shutdown the operating system safely, as defined by the Shutdown Sequence exceeds five minutes (300 seconds) then that time is used. Configure the timing as specified below, five minutes for MFCS/win and five minutes for the operating system. This gives MFCS/win and the operating system enough time to stop safely. 16

17 If the Shutdown Procedure was triggered one time, then in each case the computer will be stop, even when the power comes back during the procedure is active. Before the operating system will be stopped, the configuration file default.cmd will be executed. To stop MFCS/win in a safely way, an entry inside this needs to be placed. Click on text Where are these files located to get the path to this file. Use the explorer, click with the right mouse key on this file and choose Edit to open the file. Add the following command at the end of the file, just C:\MFCS_WIN\TASKS\MFCSSTOP.EXE LOD_STOP C:\ D:\ if MFCS/win is installed on hard disk drive C:\ if MFCS/win is installed on hard disk drive D:\ MFCSSTOP is a new program since SP3A, which informs MFCS/win about the power failure situation and stops it in a safely way. This is required to generate a system alarm and to flag all variables as not present before closing all active batch databases. 17

18 Power Failure Settings The configuration of power failure settings determine when the shutdown sequence begins and when the UPS powers on the computer if the power returns. In section Power Failure the specification when the shutdown sequence begins is made. Activate setting At runtime limit to use the maximum battery capacity of the UPS. The Power Return setting After battery charges to 50% causes the UPS to turn on when the battery power equals 50 percent. For a Smart-UPS 620 (standard model) this needs about 40 minutes. During the battery loading procedure, the LED indicators for on-line and overload are flashing. The UPS will automatically power on the computer if the battery capacity reaches 50 percent. This is a safety value, because the UPS has enough capacity to shutdown the system again in case of a new power failure. 18

19 Power Options Introduction Using Power Options in Control Panel, allows a reduction of the power consumption of any number of your computer devices or of your entire system. This is done by choosing a power scheme, which is a collection of settings that manages the power usage by your computer. Power Scheme MFCS/win is a SCADA-System and needs to be running all the time without any standby mode or hibernation. The power scheme Always On is required for MFCS/win. To set this power scheme, open the control panel and click on Power Options. 19

20 Hibernation When hibernation is enabled, then the computer will go in hibernation when you will be away from the computer for an extended time or overnight. In such a case MFCS/win is unable to collect and store process data. The hibernation feature must be disabled to avoid data loss. Click on card Hibernate and disable the hibernation as shown below: 20

21 Change History dialog Introduction The configuration of MFCS/win will be managed by the configuration program (MFCSCMA) and by components, which will be launched from configuration program. Inside the MFCS configuration program, the change history dialog will be activated only if changes have been done. If a component will be called from CMA, then CMA will not be informed, whether configuration changes has been done or not. To be on the save side in this case the Change History dialog will be activated always if one of this components have been started. Change History dialog appears without changes The Change history dialog will be activated always, if one of the following configuration menus has been entered: Menu Configure / Algorithms / Button Modify Button Algorithms / Button Modify Button Algorithm of each form of the variable configuration Component Algorithm Editor Algorithm Editor Algorithm Editor Configure / Profiles/ Button Modify Button Profile of each form of the variable configuration. Then the button Modify Configure / Recipe Configure Users Configure Control Units / Button Parameters (for control units of type DCU (Ethernet) Profile Editor Profile Editor Recipe Editor User Manager Configuration Manager 21

22 Updating MFCS Configuration Introduction The command Update configuration from the MFCS/win Shell can be used to inform the MFCS system to recreate its data structures from the configuration database. In general this action is required if the MFCS/win configuration has been changed and changes shall be available immediately. Receiving a configuration update command, the system recreates its own internal data pool and asks all the MFCS/win server modules to recreate their data structure too. Otherwise, if Update configuration is not performed, some configuration changes are only available after the next restart of the MFCS/win kernel system. Which changes do not Require Update Configuration? Configuration update is not necessary, if parts of the configuration have been changed which are not read by the background modules. The following list documents all configuration menus which will not require Update configuration but other action to be activated. Menu Configure / Group Display Configure / Variable Display Configure / Trend Display Configuration change becomes active after: Restart of Operator Service Program Restart of Operator Service Program Restart of Operator Service Program Configure / Recipe Configure Users Definition of next batch with the modified recipe Restart of MFCS/win Shell 22

23 User Configuration New Operator Right Delete Batches Within MFCS/win Version 2.1 Service Pack 4 the operator rights have been enhanced by an own right to delete Batches. When starting with the new user management in version 2.1 this right was linked to the operator right Archive Batches. It was requested by customers to give a group the right Archive Batches without granting the right Delete Batches. If an MFCS/win system will be updated to version MFCS/win 2.1 SP4, then the new right will be available after the update as operator right and all groups, which had the operator right Archive batches before, get additional the right delete batches. The right delete Batches is a global right. 23

24 21 CFR Part 11 Option 21 CFR Part 11 option has been disabled If the 21 CFR part 11 option has been removed while an MFCS/win system has been upgraded, then a message window will be shown from the MFCS/win Shell. To get rid of this error message, the following steps must be performed: 1. Start MFCS/win Configuration Management with a user with MFCS/win administrator rights. 2. Disable the option Maintenance / Audit Trail / Enable / Disable Security 3. Disable the option Maintenance / Audit Trail / Enable / Disable Audit Trail 4. Shut Down MFCS/win 5. Restart MFCS/win 24

25 Extended DCU Communication Downloading Alarm Limits Alarming is an important function of the MFCS/win software package. The alarm design allows two different setups: Alarming is active in MFCS/win. Incoming process values will be checked against the configured limits in MFCS/win. Please refer to chapter Configuration of Variables inside the System Manager s Handbook for details. Alarming is active inside the DCU. The DCU software performs a supervision of it s process values against their own alarm limits. To adapt the alarm limits inside the DCU during a fermentation process, both communication drivers has been expanded. The following is a list of requirements to use the new download function: o New download function has been implemented for control unit types DCU1, DCU2 / DCU3 and DCU [Ethernet]. o Control unit setting Process Value Alarming must be activated inside the upload group. o For each variable to send alarm limits, the Alarm Mode configuration must be set to Control Unit. The driver reads the limits from the DCU for all such variables and writes it to the on-line data pool. The high high and low low limits in MFCS/win will be set to the measurement end ranges automatically. o Within MFCS/win Version 2.1 Service Pack 4, new alarm limits can be set by a parameter phase in a recipe only. Supported variable properties are: Alarm_low Alarm_high 25

26 Windows Configuration Fast User Switching Fast User Switching, a feature of Windows XP when it is not joined to a domain, makes it possible for you to quickly switch between users without actually logging off from the computer. Multiple users can share a computer and use it simultaneously, switching back and forth without closing the programs they are running. The Fast Use Switching feature of Windows XP doesn t comply with MFCS/win. We found several problems by using this feature and strongly recommend to disable it. To turn off the Fast User Switching You must have a computer administrator account on a computer that is a member of a workgroup or is a stand-alone computer to turn off this feature. Fast User Switching is not available on computers that are members of a network domain. 1. Open User Accounts in Control Panel. 2. Click Change the way users log on or off 3. Disable checkbox Use Fast User Switching 26

27 Settings for Windows XP Service Pack2 and Windows Server 2003 SP1 or R2 With Service Pack 2 for Windows XP and Service Pack 1 for Windows Server 2003, Microsoft has included some security features, which may cause trouble with MFCS/win if they are not configured correctly. Integrated Firewall The integrated Firewall should be disabled. If for any reason ( i.e. company security policies) the firewall cannot be disabled, please contact the SBBIS service for required configuration settings. Please send an to MFCS.Service@Sartorius.com The XP firewall can be disabled in the network environment / Advanced Settings as shown in the next picture. 27

28 Automatic Updates Windows has a feature to automatically download updates for the operating system if your PC is connected to the internet. For a SCADA system like MFCS/win this feature should be disabled. Automatic updates may overwrite components used from the SCADA software or may initiate a Shutdown/Restart of the PC. Both effects could lead to loss of data or a not functioning system. Automatic Updates can be disabled in Windows Control Panel / Security Center. 28

29 Security Settings for MFCS_win Folder and MFCS_win Share Please check the security settings for the MFCS/win home directory MFCS_win. The system is based on Microsoft Access databases, to which users require write access permissions. Until Windows 2000 the default security setting for all folders was full access for everyone. Since Windows XP and Windows Server 2003, the access permissions are restricted. Only administrators have full access to folders by default. Add modify or at least write permissions to all users or user groups that need to work with the MFCS/win system to the MFCS_win folder and shares for that folder. 29

30 Access Rights on MFCS/win Workstations Additional considerations have to be taken when running the MFCS/win Service under a user account other than Local System (e.g. when using the Replication Module): When configuring MFCS/win Workstations, make sure that the user running the MFCS/win Service has administrative access to all Workstations. This can be achieved by adding the user account that launches the MFCS/win Service to the local Administrator group on each workstation. Otherwise the MFCS/win Kernel would have no rights to send messages to the MFCS/win Shell on the workstation, which would result in MRD timeouts and lost shell connections (e.g. when sending alarm messages/popup alarms to the shell). 30

31 Access Rights to the MFCS/win TASKS Directory MFCS/win 2.1 Service Pack 5 introduces personalized directories in the \MFCS_WIN\TASKS directory, that hold the file MFCSBRP.mdb for each computer where the Batch Report is started from. Upon start of BRP, it is checked if the directory already exists or if it has to be created. This action is performed on the MFCS/win system where the MFCS/win shell is running (workstation or server system). Therefore, the account that starts the MFCS/win shell needs the appropriate access rights to the TASKS directory and must be allowed to create directories and files. Another approach may be used if the administrator has knowledge of the computer names, where Batch Report is started from. He may then create a subdirectory named after the computer name and copy the \MFCS_WIN\TASKS\MFCSBRP.mdb file into it. The user then only needs write rights on the MFCSBRP.mdb file in the specific directory. 31

32 Shut Down of Windows If the MFCS/win server computer shall be shut down (e.g. Restart of computer or for maintenance purposes), then it is recommended that the following shut down sequence will be followed. This procedure shall be followed with and without running batches. 1. Use Shut down from MFCS/win Shell 2. MFCS Kernel is stopped Wait until the message MFCS Kernel is stopped has been written into the MFCS.MEV log file. The log messages from the MFCS.MEV log file can be read by opening the program Service Control Program from the MFCS win menu inside the windows start menu. 3. Shut down Windows operating system 32

33 MFCS/win Installation Installation without Floppy Disk Drive Newer computers may be delivered without a floppy disk drive. Because the MFCS/win setup is asking for a Network Configuration Disk you need to copy the required floppy disk contents from the MFCS/win CD-ROM to your hard disk in advance. The following is a description how to handle such a situation. On each MFCS/win CD-ROM in folder \MFCS_21\NETWDISK you will find the file CONFIG.INI including a default installation information template. Normally, this file is located on the Network Configuration Disk and used for all installations. Copy the complete folder NETWDISK to the hard disk of your MFCS computer, where you want to install MFCS/win like C:\MFCS_WIN\NETWDISK After copying the folder, the file CONFIG.INI may be assigned with the file attribute Read-only which needs to be removed. Click with the right mouse key on the file by using the Explorer and choose properties as shown below: Disable the Attribute Read-only and click on button Apply. If the installation procedure will ask for the Network Configuration Disk, then click on button Browse and choose the directory C:\MFCS_WIN\NETWDISK instead of the default disk drive A:\ For network systems, please use always the same directory/file of the MFCS/win Server, so that setup is able to set the correct Node_ID s for all systems to be installed. 33

34 Computer Name Limitation For technical reasons, MFCS/win 2.1 can only run on a computer system where the computer name is shorter or equal to 14 characters. If the number of used characters exceeds 14, then the following error message will occur after starting the Shell: Do not use Computer Names longer than 14 characters for MFCS/win systems. Refer also to documentation Installation Handbook / Setting the Computer Name for further details. 34

35 File Deletion During Installation During the installation of MFCS/win Service Pack 5, some files from the previous version need to be deleted. The files to be deleted include: - All backup files in the \MFCS_WIN\logdir directory (MRDBUP.Fn, MRDBUP.Bn, MRDBUP.Sn and MRDBUP.In with n = {01, 02,, 16}). If batches are running during the upgrade to MFCS/win 2.1 SP5, these batches may become unusable and require to be finished using the Batch Management Maintenance functions as described in MFCS/win User s Handbook / Batch Management / Maintenance. - Batch Report databases in the user-specific subdirectories within the \MFCS_WIN\TASKS directory. These databases are created since 2.1 SP5 and if existing in any subdirectory, will be deleted to assure that users get a copy of the new database. If you have any MFCSBRP.mdb file in a subdirectory of \MFCS_WIN\TASKS that you need for backup reasons, make sure to move the backup to another directory that is not in the \MFCS_WIN\TASKS directory. 35

36 End of Support for Windows NT Since MFCS/win 2.1 Service Pack 5, MFCS/win no longer supports Windows NT and therefore must be installed on later Windows versions. The supported Windows versions are specified in the Release Paper for each MFCS/win Release. 36

37 Data Storing Module (MFCSSTO) Considerations regarding Batch Database Locations The Data Storing module (MFCSSTO) takes care of storing the specified process values of MFCS/win into batch specific databases. STO stores process data whenever data changes exceed a configured deadband of the previously stored value. The batch databases where STO stores the values should reside on the local hard drive. It is not recommended to configure MFCS/win in such way, that the batch databases are stored on a fileserver directly. STO would then have to use the network each time a data item needs to be stored. This configuration is not recommended, as network timeouts and unreliable network connections would affect STO s operation negatively. Customers with the need for batch database backups on a dedicated fileserver should make use of the Replication Module (MFCSREPL), which provides a reliable replication of batch databases over the network. Therefore - Do not configure the System Batch Dir to be on a fileserver on the network this could result in data loss in case of heavy network load - For reliable storage on a dedicated fileserver consider using the Replication Module 37

38 Enhancements OPC DA Server After installation of MFCSOPC DA Server Level 9 and higher it is possible - to take over the batch name from an external system by OPC DA. - to have 5 additional alarm properties inside MFCS/win, to indicate the alarm state. This function to take over the batch name is necessary if the MFCS/win system is connected to another supervisory system, which generates charge ID s and this charge numbers must be transferred into MFCS without the possibility of a typing error. The batch name proposal can be taken over from OPC during the following MFCS actions Start Batch and Batch Setup from Operator Service and Define Batch from Batch Management. To specify the batch name externally by OPC procedure as follows. a) Make NextBatchName available for OPC b) Set NextBatchName by OPC Client c) Parameter BatchIdSource The parameter BatchIdSource from file MFCS.INI must be set to External. Please refer to chapter INI-file settings for Batch Name generation. 38

39 Start Batch If steps a), b) and c) have been done then function Start Batch can be done from the MFCS and the externally set batch name will appear in the field Batch Name automatically when doing Start Batch. After the batch has been started successfully the value of property NextBatchName will be reset. All restrictions to the batch name will not be touched by the external batch proposal. 39

40 Batch Setup If steps a), b) and c) have been done then the function Batch Setup can be done from the MFCS and the externally set batch name will appear in the field Batch Name automatically when doing Batch Setup. After the batch has been started successfully the value of the property NextBatchName will be reset. All restrictions to the batch name will not be touched by the external batch proposal. 40

41 Define Batch [S88] If steps a), b) and c) have been done then the function Define Batch can be done from the MFCS. It is necessary, that a process unit will be pre selected. Open the selection list Preselect Process unit and select the process unit to define the batch for. If another process unit will be selected, then the batch name proposal will be updated immediately. After the batch has been defined successfully the value of the property NextBatchName will be reset. All restrictions to the batch name will not be touched by the external batch proposal. 41

42 INI-file settings for Batch Name generation After installation of MFCSOPC DA Server Level 9 and higher it is possible to take over the batch name from an external system by OPC DA. There are additional parameters in the file MFCS.INI in section [SYSTEM], which controls the system behavior of taking over the Batch Name proposal. New keys for setting batch name via OPC BatchNamePrefix (blank) (string) e.g. Test The BatchNamePrefix controls the first part of the Batch Name proposal, if the BatchIdSource is set to Auto. It can be any string which contains the following characters: a z, A Z, 0 9, /, _, -, +, <, >, and blank It is recommended to make the BatchNamePrefix not longer than 4 characters. The BatchNamePrefix will be case sensitive. FixBatchName 0 1 The user can modify the batch name. The field for editing the Batch Name (Start Batch, Batch Setup, Batch Define) is not locked. The user cannot modify the batch name. The field for editing the Batch Name (Start Batch, Batch Setup, Batch Define) is locked. BatchIdSources Auto Generate a unique proposal with the following structure PPP UUUU MMM DD YYYY N PPP Prefix if specified UUUU Process unit name if a process unit is selected MMM Month DD Day YYYY Year N Number if the previous part is not unique Take the proposal from the specified process unit. Empty if offline or if no pro specified External The string which was written to property NextBatchName via OPC, will be used for the Batch name proposal. Remark: For version 2.1 it is necessary, that a file MFCS.INI exist on each MFCS/win workstation in directory :\MFCS_win, which holds the above specified keys. If this file does not exist, then the default settings will be used: BatchNamePrefix: FixBatchName: 0 BatchIdSources: Auto 42

43 A detailed description of all combinations can be found from the following table, which shows all possible scenarios. Scenario Setting of Parameters a) BatchNamePrefix: Test FixBatchName: 0 BatchIdSources: External Description The batch name will be taken over from OPC property NextBatchName. Because FixBatchName is 0 it can be manually modified or entered manually. The batch name must be the name set via OPC or the first part must start with the BatchNamePrefix, to distinguish, that the batch name was created locally in MFCS. The BatchNamePrefix is case senitive and so it must be exactly written as specified. This scenario should be used, if the batch name shall be always generated by an external system (e.g. for production), but there is the possibility to generated batch name locally, if the BatchNamePrefix (e.g. Test) will be used. All batch names, which do not start with the BatchNamePrefix, have been generated by the external system. b) BatchNamePrefix: Test FixBatchName: 1 BatchIdSources: External c) BatchNamePrefix: Test FixBatchName: 0 BatchIdSources: Auto d) BatchNamePrefix: Test FixBatchName: 1 The batch name will be taken over from OPC property NextBatchName, only. Because FixBatchName is 1 it cannot be manually modified. This scenario should be used, if the batch name must always be generated by an external system (e.g. for production). The batch name is generated automatically (e.g. TestF03 Jul ), but can be modified manually. In this case the batch name must start with the BatchNamePrefix. This scenario should be used, to get a high flexibility for the creating the batch name (e.g. for research) The batch name is generated automatically (e.g. TestF03 Jul ), and cannot be modified. This scenario should be used, if the batch name must be always generated by MFCS/win. BatchIdSources: Auto 43

44 e) BatchNamePrefix: FixBatchName: 0 BatchIdSources: External f) BatchNamePrefix: FixBatchName: 1 BatchIdSources: External g) BatchNamePrefix: FixBatchName: 0 BatchIdSources: Auto h) BatchNamePrefix: FixBatchName: 1 BatchIdSources: Auto The batch name will be taken over from OPC property NextBatchName. Because FixBatchName is 0 it can be manually modified. Because there is no BatchNamePrefix specified manual entered or modified batch names have not to follow special rules. This scenario is a very flexible one. The batch name will be taken over from OPC property NextBatchName, only. Because FixBatchName is 1 it cannot be manually modified. This scenario should be used, if the batch name must always be generated by an external system (e.g. for production). Same as scenario b). The batch name is generated automatically (e.g. F03 Jul ) and can be modified manually. This scenario should be used, to get a high flexibility for the creating the batch names local in MFCS/win (e.g. for research). The batch name is generated automatically (e.g. TestF03 Jul ), and cannot be modified. This scenario should be used, if the batch name must be always generated by MFCS/win. Same as scenario d). 44

45 Additional Properties for Alarm Status There will be 4 additional properties for analog variables inside MFCS/win, which indicate the alarm state. These 4 additional properties can be read by an OPC DA Client, if they are configured to be available inside the OPC DA Server. Level 9 and higher of the MFCS OPC DA Server supports the following properties for the specified variable types: Variable type Property Write Access Values Digital Input Alr_Status no 0 not in Alarm 1 Digital Input in Alarm Cyclic Variable, DCU Controller, PID Controller, FIS Controller FIS PID Controller HH_Status H_Status no no 0 if no alarm 1 if alarm limit Alarm_High_High exceeded if no alarm 1 if alarm limit Alarm_High exceeded L_Status no 0 if no alarm 1 if alarm limit Alarm_High exceeded LL_Status no 0 if no alarm 1 if alarm limit Alarm_High exceeded 45