Historian IT

SIMATIC® IT Historian 6.1

Release Notes

The following guide contains a brief description of the major innovations introduced in SIMATIC® IT Historian 6.1, suggestions for optimized product use and other general information. Therefore, we recommend that you carefully read the contents herein. According to law, Siemens AG reserves the rights inherent to the property of this document, prohibiting its reproduction (either in full or in part) and its disclosure in any form to third parties or competitors without written authorization. Although great care has been taken in compiling this document to ensure that the information contained herein is correct, no guarantee or warranty is given or implied. The policy of Siemens AG is to constantly improve its products. Therefore, Siemens AG reserves the right to make any changes to the product in question without prior notice.

© 2005 Siemens AG All rights reserved. SIMATIC® is a registered trademark of Siemens.

SIMATIC® IT Historian 6.1 Release Notes

Table of Contents

Welcome!!! ........................................................................................................................... 6

Before You Start.................................................................................................................. 6

Important Notes................................................................................................................... 7 Upgrading from previous versions ................................................................................... 7 Upgrading from versions 3.01.05..................................................................................... 7 Log files............................................................................................................................ 7 Folder share permissions .................................................................................................. 7 Licenses ............................................................................................................................ 7 Software Localization....................................................................................................... 8 Product Uninstall .............................................................................................................. 8

Installing the Software ........................................................................................................ 10 Historian components ....................................................................................................... 10 New setup structure .......................................................................................................... 10 Software Requirements .................................................................................................... 11 Operating-system localization .......................................................................................... 11 Use of SIMATIC® IT Historian with other Siemens products......................................... 12 Microsoft Security Hotfixes ............................................................................................. 12 Interaction with .NET applications .................................................................................. 14 Interaction with 3rd-party tools ......................................................................................... 14

Remote Control............................................................................................................ 15 Disk Backup and Disaster Recovery utilities .............................................................. 15 Time synchronization tools.......................................................................................... 15 Antiviruses ................................................................................................................... 15

Note on SIMATIC® IT Report Manager:......................................................................... 16 MS SQLServer Installation .............................................................................................. 16 Hardware Requirements ................................................................................................... 17 Notes regarding the product’s Setup and use ................................................................... 19

Windows 2000 configuration....................................................................................... 19 Using dynamic Screen Savers...................................................................................... 19 Optimizing performance .............................................................................................. 19

Documentation..................................................................................................................... 20 Documentation languages ................................................................................................ 20 Known Issues.................................................................................................................... 20

Obsolete features ................................................................................................................. 21 Drivers for Real-Time data sources.................................................................................. 21 Abandoned modules ......................................................................................................... 21 Arcnet support .................................................................................................................. 21 Function Keyboard support .............................................................................................. 21

Known Technical Issues...................................................................................................... 22 Intranet/Internet configurations........................................................................................ 22 Services and Management Console.................................................................................. 22

© Siemens AG 2005 All Rights Reserved. Page 2 of 45


Database Management...................................................................................................... 22 SIMATIC® IT Historian Server........................................................................................ 23

Important Notes ................................................................................................................ 23 Plant Performance Analyzer ........................................................................................ 23 Integration with SIMATIC® IT Production Modeler .................................................. 24

Installing the Software...................................................................................................... 24 Hardware and Software requirements.......................................................................... 24 Backup configurations ................................................................................................. 24 PDA server PC configuration ...................................................................................... 24 PPA server use ............................................................................................................. 24

Documentation ................................................................................................................. 25 What’s New ...................................................................................................................... 25

Client/Server PPA programmatic interface ................................................................. 25 Custom Data Management........................................................................................... 25 Alarm Archiving .......................................................................................................... 25 SIMATIC® BATCH integration ................................................................................. 25

Known Technical Issues................................................................................................... 26 Recovery of SQL connection....................................................................................... 26 OPCHDA error: “More data” ...................................................................................... 26 Import of custom library .............................................................................................. 26 Minimun number of points for Alarm Server.............................................................. 26

SIMATIC® IT Historian Client ........................................................................................ 27 Important Notes ................................................................................................................ 27

User applications embedding ADDX and PDDX........................................................ 27 Lean Clients ................................................................................................................. 27 ActiveX Message Viewer Automatic Update.............................................................. 27 Excel Add-In................................................................................................................ 28

Installing the Software...................................................................................................... 28 ActiveX Message Viewer memory requirements........................................................ 28 ActiveX Production Viewer memory requirements .................................................... 29

Documentation ................................................................................................................. 29 Obsolete features .............................................................................................................. 29

OLE support for HDD ................................................................................................. 29 What’s New ...................................................................................................................... 29

Custom Messages ........................................................................................................ 29 Equipment-relative charts ............................................................................................ 29 Extended support of offline data.................................................................................. 29 Bound Limits and Target Limits.................................................................................. 29 Context information in chart legend ............................................................................ 30 Organizing chart files into folders ............................................................................... 30 Unicode Support .......................................................................................................... 30 Date / Time format selection ....................................................................................... 30

Known Technical Issues................................................................................................... 30 Historian Data Display ................................................................................................ 30 Historian Basic Lean Client......................................................................................... 30 Lean Client Gui connection problem with Xp sp2 ...................................................... 31



SIMATIC® IT Services 5.0 ................................................................................................ 32 Important Notes ................................................................................................................ 32

PCS7 Tag Browser....................................................................................................... 32 User Change on Citrix ................................................................................................. 32 User Change on Terminal Server client (Remote Desktop Connection)..................... 32 IPC Communication port ............................................................................................. 32 MSM Display Client on Http environmental............................................................... 32 Proxy Configuration .................................................................................................... 33 SIMATIC Logon.......................................................................................................... 33 Compliace Services upgrade........................................................................................ 33 Internal tools ................................................................................................................ 33 Standard User Manager ............................................................................................... 33 Notes for Web installation ........................................................................................... 34 Chinese language ......................................................................................................... 34 Compliance service...................................................................................................... 34

Installing the Software...................................................................................................... 34 Hardware and software Requirements......................................................................... 34


Stand Alone Mode ....................................................................................................... 35 What’s New ...................................................................................................................... 35

SIMATIC Logon.......................................................................................................... 35 SIMATIC License Management.................................................................................. 35

Known Technical Issues................................................................................................... 35 Terminal Server support for Basic Client station ........................................................ 35 Cab Protocol Configurator........................................................................................... 36 Lock Object Server ...................................................................................................... 36 Compliance Service ..................................................................................................... 36 Messaging Manager..................................................................................................... 36 PCS7 Tag Browser....................................................................................................... 36

SIMATIC® IT CAB 1.1...................................................................................................... 37 Important Notes ................................................................................................................ 37

CAB Library Toolbox Configuration .......................................................................... 37 CAB Runtime Client Security Configuration.............................................................. 37 CAB Runtime WebServer Security Configuration...................................................... 38 Upgrading Smart Query Builder queries ..................................................................... 38



Component DataProviders........................................................................................... 38 Fixed Technical Issues ..................................................................................................... 39

Regional settings mismatch ......................................................................................... 39 Known Technical Issues................................................................................................... 39

CAB Web Server and CAB Server machine name problems...................................... 39 CAB Script Editor and keyboard shortcuts ................................................................. 39



How to make a Session survive its natural timeout without user interaction.............. 39 Known Technical Issues (CAB) .................................................................................. 42

SIMATIC® IT BPM 5.0 ..................................................................................................... 43 Important Notes ................................................................................................................ 43

Set the Plant in SIMATIC IT Production Modeler “CURRENT” .............................. 43 How to change the Pcell link to another BATCH UNIT............................................. 43 Deleting a Plant............................................................................................................ 43 Production Modeler server indication ......................................................................... 43


Documentation ................................................................................................................. 44 What’s New ...................................................................................................................... 44

Versioning.................................................................................................................... 44 Unicode support........................................................................................................... 44 Distributed transaction................................................................................................. 44 BPM-EQUIP-TREE-OCX........................................................................................... 44

Fixed Technical Issues ..................................................................................................... 44 Configuration ............................................................................................................... 44

Known Technical Issues................................................................................................... 45 Incremental Import in PPA.......................................................................................... 45 Default name for Process Segment (or Production Operation) Rules of Rules........... 45 Hierarchy of the Process Segment (or Production Operation) Rules of Rules............ 45 Downloading PS/Po hierarchies .................................................................................. 45 Association Between the PO and the Final Material ................................................... 45



Welcome!!!

Welcome to the world of SIMATIC IT. In modern plants, coordinating and synchronizing different parts of the enterprise is what determines success. The manufacturing process is distributed where it is convenient (outside the plant or even outside the enterprise). Being able to manage its increasing complexity is therefore a key factor to successful installation.

SIMATIC IT is the software environment that permits managing such complex systems. A Framework models the entire Supply Chain and then directly synchronizes and coordinates the activities of all the components defined in the model. A group of several components is dedicated to performing specific actions in order to achieve the manufacturing goals (scheduling, batch management, data manipulation and archiving, and so forth). Since the first release of SIMATIC IT, development has been centered on improving the product’s core, introducing new features and new components, as well as exploiting up-and-coming, innovative technologies in step with the frenetic evolution of Information Technology. We strongly believe in continuously developing our software environment: likewise, we are convinced that such development must include all of our customers’ requirements. For this reason, we kindly ask that you please provide any suggestions or comments you feel may aid us in improving our platform.

Before You Start

For a complete guide to installation, please refer to the appropriate Installation manual available on the product CD-Rom. To read .PDF files, the installation of Acrobat Reader is provided in the “\Acrobat_Reader” folder of the product setup CD-Rom.



Important Notes

Upgrading from previous versions

Please refer to the migration guide (“Historian_MigrationGuide.pdf”) included in the \Documentation folder of this CD-Rom.

Upgrading from versions 3.01.05

If you are upgrading from versions 3.01.05 (including Service Packs 1 and 2), you must delete the file GPSSOCK.INI from the directory %ICUBECNF% (normally ICUBE.CNF) before installing the new version. This is necessary only if you were using the new Inter-process Communication Service (RIS) based on TCP/IP.

Log files

Due to a change in log-file format, if you are upgrading from versions < 4.2, the log-file content is automatically deleted when the new version is run for the first time. If the current version is < 4.2 and you want to keep the current content of the log files, it is recommended that you save each log file (system log file and private log files) using the “Log File Viewer” utility, before installing version 6.1.

Folder share permissions

SIMATIC® IT Management Console automatically creates shares on the application folders (Plants). As of this version, any new share is created with limited permissions in order to limit access to users belonging to the “Authenticated Users” group. Previously-created shares maintain their existing permission settings.

Licenses

This version is completely integrated with Siemens Automation License Manager. For this reason, the hardware key is no longer necessary. For further details about License installation and management, please refer to the Automation License Manager Help.



Software Localization

Version 6.1 is provided with a complete and tested user interface and online help in German and English. French, Italian and Spanish user interfaces and online helps (available for SIMATIC® IT Services and SIMATIC® IT Historian) are not provided in this version and will be supplied in a subsequent Service Pack.

Product Uninstall

In order to guarantee that the product is uninstalled correctly, the modules must be uninstalled in the following order: • Client

• PRS Database Management • PPA SQL Server Extension • BPM Configurator • BPM Display • Excel Add-In • CAB Web Server • Basic Client • (*) Full Services Or (**) Client Services

• Server • CAB Server • BPM Server • Query Tool • CAB Engineering • Historian Server • (*) Full Services • SIMATIC® Connection

• Server + Client

• PRS Database Management • PPA SQL Server Extension • BPM Configurator • BPM Display • Excel Add-In • CAB Web Server • Basic Client • CAB Server • BPM Server • Query Tool • CAB Engineering • Historian Server



• SIMATIC® Connection • (*) Full Services

Notes: (*) To Uninstall Full Services please remove the setups in the following order:

• PRS Client • Historian Client • Common Files • Full Services • Historian Documentation and/or Production Suite Documentation

(**) To Uninstall Client Services please remove the setups in the following order:

• PRS Client • Historian Client • Common Files • Basic Services • Historian Documentation and/or Production Suite Documentation

(***) The SIMATIC products listed below can be uninstalled only if no other SIMATIC products are installed.

• License Management • SIMATIC Logon Service • SIMATIC Logon Admin



Installing the Software

Each CD-Rom provided contains an Autorun file that allows you to automatically launch the Setup program upon inserting the CD into its Drive. In any case, a Setup program (INSTi386.bat) can be found in the root directory of the CD-Rom. Before installing the product, we strongly recommend that you close all open applications and save all important data and programs, even though all necessary precautions have been taken to render the software that has been provided safe.

Historian components

SIMATIC® IT Historian 6.1 is made up of: • SIMATIC® IT Services 5.0 • SIMATIC® License Manager • SIMATIC ® Logon • SIMATIC® IT Client Application Builder (CAB) 1.1 • SIMATIC® IT Business Process Modeler (BPM) 5.0 • SIMATIC® IT Historian Server (including Plant Performance Analyzer, Plant Data

Archive, Alarm Manager, GUI Development) • SIMATIC® IT Historian Client (including Historian Data Display, Excel Add-In, GUI

runtime)

New setup structure

As of SIMATIC® IT Historian 6.1, the setup procedure has changed. It is based on standard Microsoft MSI packages: all installed components are displayed in the Windows list of installed applications, thus allowing the user to safely uninstall the product and monitor installed components. The setup is structured as follows: • Server

• Simatic connection • Full Services • License Management • Simatic Logon Service • Simatic Logon Admin • Bpm Server • Cab Server • Historian Server

• Client



• Client Services • BPM Configuration • Bpm Display • Excel Add-In • Basic Client

• CAB Engineering • CAB Engineering • Query Tool

• CAB Web Server • Cab Web Server

• SQL Extension • Prs Database Management • Ppa Sql Server Extension

Note: Historian Client is automatically installed both with Full and Client Services.

Software Requirements

SIMATIC® IT Historian 6.1 has been tested with the following software: • Windows 2000 (Professional and Server) with Service Pack 4 or Windows XP with

Service Pack 2 or Windows 2003 • Internet Explorer 6.0 with Service Pack 1 • MDAC 2.8 and JET 4.0 SP8 • SqlServer 2000 (Standard Edition or Enterprise Edition 1) with Service Pack 3 (required

for SIMATIC® IT Plant Performance Analyzer) Siemens will provide customer support only if the product is installed according to this configuration; otherwise, SIMATIC® IT Historian 6.1 will not be covered by legal warranty.

Operating-system localization

SIMATIC® IT Historian 6.1 has been tested with the English version of the supported operating system and with the following localized versions: • Windows XP and Windows 2003 in German

1 SIMATIC® IT Plant Performance Analyzer also supports SQL Server 2000 Personal Edition. However, Personal

Edition includes a concurrent workload governor that limits its scalability; performance degrades when more than five Transact-SQL batches are executed concurrently. Therefore, as SIMATIC® IT PPA often uses more than five batches, we suggest using Personal edition only for test/demo projects or engineering stations for which system performance is not important. For standard server stations we suggest using the Standard Edition in order to obtain the best performances. Standard edition can only be installed on server operating systems, namely Microsoft Windows 2000 Server, Windows 2000 Advanced Server, Windows 2000 Datacenter Server or Windows Server 2003 (Standard, Enterprise or Datacenter editions).



• Windows 2000, Windows XP and Windows 2003 in English using the Chinese multilanguage add-on.

Use of SIMATIC® IT Historian with other Siemens products

SIMATIC® IT Historian 6.1 has not been tested for integration with PCS7: therefore, Siemens will not provide support for that configuration. The product component affected is:

- SIMATIC® IT PCS7 Tag Browser included in Services 5.0 Although this component is present on setup media, Siemens will not provide support for it.

Microsoft Security Hotfixes

The following table contains the list of Microsoft Security Hotfixes that have been used in SIMATIC® IT Historian 6.1 System Tests. Siemens will provide customer support only if the product is installed according to this configuration; if additional security patches are installed, SIMATIC® IT Historian 6.1 will no longer be convered by legal warranty. In any case, Siemens will provide support for all those problems not related to the new Microsoft patches installed. Windows 2000 PRO Date Microsoft Knowledge Base Microsoft Bulletin 12-gen-05 Q890175 http://support.microsoft.com/?kbid=890175 MS05001 http://www.microsoft.com/technet/security/Bulletin/MS05-001.mspx12-gen-05 Q871250 http://support.microsoft.com/?kbid=871250 MS05003 http://www.microsoft.com/technet/security/Bulletin/MS05-003.mspx14-apr-04 Q835732 http://support.microsoft.com/?kbid=835732 MS04011 http://www.microsoft.com/technet/security/Bulletin/MS04-011.mspx14-apr-04 Q828741 http://support.microsoft.com/?kbid=828741 MS04012 http://www.microsoft.com/technet/security/Bulletin/MS04-012.mspx14-apr-04 Q837001 http://support.microsoft.com/?kbid=837001 MS04014 http://www.microsoft.com/technet/security/Bulletin/MS04-014.mspx09-feb-05 Q885250 http://support.microsoft.com/?kbid=885250 MS05011 http://www.microsoft.com/technet/security/Bulletin/MS05-011.mspx10-mag-04 Q841382 http://support.microsoft.com/?kbid=841382 --- 09-feb-05 Q891781 http://support.microsoft.com/?kbid=891781 MS05013 http://www.microsoft.com/technet/security/Bulletin/MS05-013.mspx09-giu-04 Q839643 http://support.microsoft.com/?kbid=839643 MS04016 http://www.microsoft.com/technet/security/Bulletin/MS04-016.mspx14-lug-04 Q841873 http://support.microsoft.com/?kbid=841873 MS04022 http://www.microsoft.com/technet/security/Bulletin/MS04-022.mspx14-lug-04 Q840315 http://support.microsoft.com/?kbid=840315 MS04023 http://www.microsoft.com/technet/security/Bulletin/MS04-023.mspx09-feb-05 Q888113 http://support.microsoft.com/?kbid=888113 MS05015 http://www.microsoft.com/technet/security/Bulletin/MS05-015.mspx14-lug-04 Q842526 http://support.microsoft.com/?kbid=842526 MS04019 http://www.microsoft.com/technet/security/Bulletin/MS04-019.mspx00-gen-00 --- SP4 15-lug-04 Q841872 http://support.microsoft.com/?kbid=841872 MS04020 http://www.microsoft.com/technet/security/Bulletin/MS04-020.mspx10-lug-03 Q823559 http://support.microsoft.com/?kbid=823559 MS03023 http://www.microsoft.com/technet/security/Bulletin/MS03-023.mspx14-lug-04 Q839645 http://support.microsoft.com/?kbid=839645 MS04024 http://www.microsoft.com/technet/security/Bulletin/MS04-024.mspx09-feb-05 Q873333 http://support.microsoft.com/?kbid=873333 MS05012 http://www.microsoft.com/technet/security/Bulletin/MS05-012.mspx13-apr-05 Q893066 http://support.microsoft.com/?kbid=893066 MS05019 http://www.microsoft.com/technet/security/Bulletin/MS05-019.mspx13-ott-04 Q840987 http://support.microsoft.com/?kbid=840987 MS04032 http://www.microsoft.com/technet/security/Bulletin/MS04-032.mspx13-apr-05 Q890923 http://support.microsoft.com/?kbid=890923 MS05020 http://www.microsoft.com/technet/security/Bulletin/MS05-020.mspx28-ago-03 Q819696 http://support.microsoft.com/?kbid=819696 MS03030 http://www.microsoft.com/technet/security/Bulletin/MS03-030.mspx


http://support.microsoft.com/?kbid=890175

http://www.microsoft.com/technet/security/Bulletin/MS05-001.mspx









































13-apr-05 Q893086 http://support.microsoft.com/?kbid=893086 MS05016 http://www.microsoft.com/technet/security/Bulletin/MS05-016.mspx13-ott-04 Q841356 http://support.microsoft.com/?kbid=841356 MS04037 http://www.microsoft.com/technet/security/Bulletin/MS04-037.mspx09-set-03 Q824105 http://support.microsoft.com/?kbid=824105 MS03034 http://www.microsoft.com/technet/security/Bulletin/MS03-034.mspx14-ott-04 Q824151 http://support.microsoft.com/?kbid=824151 MS04030 http://www.microsoft.com/technet/security/Bulletin/MS04-030.mspx14-ott-04 Q841533 http://support.microsoft.com/?kbid=841533 MS04031 http://www.microsoft.com/technet/security/Bulletin/MS04-031.mspx13-apr-05 Q890859 http://support.microsoft.com/?kbid=890859 MS05018 http://www.microsoft.com/technet/security/Bulletin/MS05-018.mspx17-ott-03 Q825119 http://support.microsoft.com/?kbid=825119 MS03044 http://www.microsoft.com/technet/security/Bulletin/MS03-044.mspx14-apr-05 Q892944 http://support.microsoft.com/?kbid=892944 MS05017 http://www.microsoft.com/technet/security/Bulletin/MS05-017.mspx31-ott-03 Q826232 http://support.microsoft.com/?kbid=826232 MS03042 http://www.microsoft.com/technet/security/Bulletin/MS03-042.mspx17-ott-03 Q823182 http://support.microsoft.com/?kbid=823182 MS03041 http://www.microsoft.com/technet/security/Bulletin/MS03-041.mspx31-ott-03 Q828035 http://support.microsoft.com/?kbid=828035 MS03043 http://www.microsoft.com/technet/security/Bulletin/MS03-043.mspx11-mag-05 Q894320 http://support.microsoft.com/?kbid=894320 MS05024 http://www.microsoft.com/technet/security/Bulletin/MS05-024.mspx12-nov-03 Q828749 http://support.microsoft.com/?kbid=828749 MS03049 http://www.microsoft.com/technet/security/Bulletin/MS03-049.mspx15-dic-04 Q885836 http://support.microsoft.com/?kbid=885836 MS04041 http://www.microsoft.com/technet/security/Bulletin/MS04-041.mspx15-dic-04 Q873339 http://support.microsoft.com/?kbid=873339 MS04043 http://www.microsoft.com/technet/security/Bulletin/MS04-043.mspx15-dic-04 Q885835 http://support.microsoft.com/?kbid=885835 MS04044 http://www.microsoft.com/technet/security/Bulletin/MS04-044.mspx21-nov-03 Q329115 http://support.microsoft.com/?kbid=329115 MS02050 http://www.microsoft.com/technet/security/Bulletin/MS02-050.mspx Windows 2000 SP4 Date Microsoft Knowledge Base Microsoft Bulletin 12-gen-05 Q890175 http://support.microsoft.com/?kbid=890175 MS05001 http://www.microsoft.com/technet/security/Bulletin/MS05-001.mspx11-mar-04 Q822343 http://support.microsoft.com/?kbid=822343 MS04008 http://www.microsoft.com/technet/security/Bulletin/MS04-008.mspx12-gen-05 Q871250 http://support.microsoft.com/?kbid=871250 MS05003 http://www.microsoft.com/technet/security/Bulletin/MS05-003.mspx14-apr-04 Q835732 http://support.microsoft.com/?kbid=835732 MS04011 http://www.microsoft.com/technet/security/Bulletin/MS04-011.mspx14-apr-04 Q828741 http://support.microsoft.com/?kbid=828741 MS04012 http://www.microsoft.com/technet/security/Bulletin/MS04-012.mspx14-apr-04 Q837001 http://support.microsoft.com/?kbid=837001 MS04014 http://www.microsoft.com/technet/security/Bulletin/MS04-014.mspx09-feb-05 Q885834 http://support.microsoft.com/?kbid=885834 MS05010 http://www.microsoft.com/technet/security/Bulletin/MS05-010.mspx09-feb-05 Q885250 http://support.microsoft.com/?kbid=885250 MS05011 http://www.microsoft.com/technet/security/Bulletin/MS05-011.mspx10-mag-04 Q841382 http://support.microsoft.com/?kbid=841382 --- 09-feb-05 Q891781 http://support.microsoft.com/?kbid=891781 MS05013 http://www.microsoft.com/technet/security/Bulletin/MS05-013.mspx09-giu-04 Q839643 http://support.microsoft.com/?kbid=839643 MS04016 http://www.microsoft.com/technet/security/Bulletin/MS04-016.mspx14-lug-04 Q841873 http://support.microsoft.com/?kbid=841873 MS04022 http://www.microsoft.com/technet/security/Bulletin/MS04-022.mspx14-lug-04 Q840315 http://support.microsoft.com/?kbid=840315 MS04023 http://www.microsoft.com/technet/security/Bulletin/MS04-023.mspx09-feb-05 Q888113 http://support.microsoft.com/?kbid=888113 MS05015 http://www.microsoft.com/technet/security/Bulletin/MS05-015.mspx14-lug-04 Q842526 http://support.microsoft.com/?kbid=842526 MS04019 http://www.microsoft.com/technet/security/Bulletin/MS04-019.mspx00-gen-00 --- SP4 15-lug-04 Q841872 http://support.microsoft.com/?kbid=841872 MS04020 http://www.microsoft.com/technet/security/Bulletin/MS04-020.mspx10-lug-03 Q823559 http://support.microsoft.com/?kbid=823559 MS03023 http://www.microsoft.com/technet/security/Bulletin/MS03-023.mspx14-lug-04 Q839645 http://support.microsoft.com/?kbid=839645 MS04024 http://www.microsoft.com/technet/security/Bulletin/MS04-024.mspx09-feb-05 Q873333 http://support.microsoft.com/?kbid=873333 MS05012 http://www.microsoft.com/technet/security/Bulletin/MS05-012.mspx13-apr-05 Q893066 http://support.microsoft.com/?kbid=893066 MS05019 http://www.microsoft.com/technet/security/Bulletin/MS05-019.mspx13-ott-04 Q840987 http://support.microsoft.com/?kbid=840987 MS04032 http://www.microsoft.com/technet/security/Bulletin/MS04-032.mspx13-apr-05 Q890923 http://support.microsoft.com/?kbid=890923 MS05020 http://www.microsoft.com/technet/security/Bulletin/MS05-020.mspx28-ago-03 Q819696 http://support.microsoft.com/?kbid=819696 MS03030 http://www.microsoft.com/technet/security/Bulletin/MS03-030.mspx13-ott-04 Q883935 http://support.microsoft.com/?kbid=883935 MS04036 http://www.microsoft.com/technet/security/Bulletin/MS04-036.mspx13-apr-05 Q893086 http://support.microsoft.com/?kbid=893086 MS05016 http://www.microsoft.com/technet/security/Bulletin/MS05-016.mspx13-ott-04 Q841356 http://support.microsoft.com/?kbid=841356 MS04037 http://www.microsoft.com/technet/security/Bulletin/MS04-037.mspx09-set-03 Q824105 http://support.microsoft.com/?kbid=824105 MS03034 http://www.microsoft.com/technet/security/Bulletin/MS03-034.mspx14-ott-04 Q824151 http://support.microsoft.com/?kbid=824151 MS04030 http://www.microsoft.com/technet/security/Bulletin/MS04-030.mspx14-ott-04 Q841533 http://support.microsoft.com/?kbid=841533 MS04031 http://www.microsoft.com/technet/security/Bulletin/MS04-031.mspx13-apr-05 Q890859 http://support.microsoft.com/?kbid=890859 MS05018 http://www.microsoft.com/technet/security/Bulletin/MS05-018.mspx17-ott-03 Q825119 http://support.microsoft.com/?kbid=825119 MS03044 http://www.microsoft.com/technet/security/Bulletin/MS03-044.mspx14-apr-05 Q892944 http://support.microsoft.com/?kbid=892944 MS05017 http://www.microsoft.com/technet/security/Bulletin/MS05-017.mspx31-ott-03 Q826232 http://support.microsoft.com/?kbid=826232 MS03042 http://www.microsoft.com/technet/security/Bulletin/MS03-042.mspx17-ott-03 Q823182 http://support.microsoft.com/?kbid=823182 MS03041 http://www.microsoft.com/technet/security/Bulletin/MS03-041.mspx31-ott-03 Q828035 http://support.microsoft.com/?kbid=828035 MS03043 http://www.microsoft.com/technet/security/Bulletin/MS03-043.mspx11-mag-05 Q894320 http://support.microsoft.com/?kbid=894320 MS05024 http://www.microsoft.com/technet/security/Bulletin/MS05-024.mspx12-nov-03 Q828749 http://support.microsoft.com/?kbid=828749 MS03049 http://www.microsoft.com/technet/security/Bulletin/MS03-049.mspx15-dic-04 Q885836 http://support.microsoft.com/?kbid=885836 MS04041 http://www.microsoft.com/technet/security/Bulletin/MS04-041.mspx15-dic-04 Q873339 http://support.microsoft.com/?kbid=873339 MS04043 http://www.microsoft.com/technet/security/Bulletin/MS04-043.mspx15-dic-04 Q885835 http://support.microsoft.com/?kbid=885835 MS04044 http://www.microsoft.com/technet/security/Bulletin/MS04-044.mspx




















































































































15-dic-04 Q870736 http://support.microsoft.com/?kbid=870736 MS04045 http://www.microsoft.com/technet/security/Bulletin/MS04-045.mspx15-dic-04 Q870763 http://support.microsoft.com/?kbid=870763 MS04045 http://www.microsoft.com/technet/security/Bulletin/MS04-045.mspx21-nov-03 Q329115 http://support.microsoft.com/?kbid=329115 MS02050 http://www.microsoft.com/technet/security/Bulletin/MS02-050.mspx Windows 2003 Server SP1 Date Microsoft Knowledge Base Microsoft Bulletin 06-apr-05 Q889109 http://support.microsoft.com/?kbid=889109 SP1 Windows XP SP2 Date Microsoft Knowledge Base Microsoft Bulletin 02-giu-05 Q893357 http://support.microsoft.com/?kbid=893357 M620740 http://www.microsoft.com/technet/security/Bulletin/M620-740.mspx12-gen-05 Q890175 http://support.microsoft.com/?kbid=890175 MS05001 http://www.microsoft.com/technet/security/Bulletin/MS05-001.mspx09-feb-05 Q887472 http://support.microsoft.com/?kbid=887472 MS05009 http://www.microsoft.com/technet/security/Bulletin/MS05-009.mspx09-feb-05 Q885250 http://support.microsoft.com/?kbid=885250 MS05011 http://www.microsoft.com/technet/security/Bulletin/MS05-011.mspx09-feb-05 Q891781 http://support.microsoft.com/?kbid=891781 MS05013 http://www.microsoft.com/technet/security/Bulletin/MS05-013.mspx09-feb-05 Q888113 http://support.microsoft.com/?kbid=888113 MS05015 http://www.microsoft.com/technet/security/Bulletin/MS05-015.mspx09-feb-05 Q888302 http://support.microsoft.com/?kbid=888302 MS05007 http://www.microsoft.com/technet/security/Bulletin/MS05-007.mspx09-feb-05 Q873333 http://support.microsoft.com/?kbid=873333 MS05012 http://www.microsoft.com/technet/security/Bulletin/MS05-012.mspx10-ago-04 Q835935 http://support.microsoft.com/?kbid=835935 SP2 13-apr-05 Q893066 http://support.microsoft.com/?kbid=893066 MS05019 http://www.microsoft.com/technet/security/Bulletin/MS05-019.mspx13-apr-05 Q890923 http://support.microsoft.com/?kbid=890923 MS05020 http://www.microsoft.com/technet/security/Bulletin/MS05-020.mspx13-apr-05 Q893086 http://support.microsoft.com/?kbid=893086 MS05016 http://www.microsoft.com/technet/security/Bulletin/MS05-016.mspx13-apr-05 Q890859 http://support.microsoft.com/?kbid=890859 MS05018 http://www.microsoft.com/technet/security/Bulletin/MS05-018.mspx15-dic-04 Q885836 http://support.microsoft.com/?kbid=885836 MS04041 http://www.microsoft.com/technet/security/Bulletin/MS04-041.mspx15-dic-04 Q873339 http://support.microsoft.com/?kbid=873339 MS04043 http://www.microsoft.com/technet/security/Bulletin/MS04-043.mspx15-dic-04 Q885835 http://support.microsoft.com/?kbid=885835 MS04044 http://www.microsoft.com/technet/security/Bulletin/MS04-044.mspx16-dic-04 Q886185 http://support.microsoft.com/?kbid=886185 --- 25-June-05 Q319740 http://support.microsoft.com/?kbid=319740 ---

Interaction with .NET applications

SIMATIC® IT Historian 6.1 guarantees interaction with .NET applications only via the .NET components provided by SIMATIC IT CAB (refer to the CAB documentation for additional details) or the public COM interfaces exposed by SIMATIC IT Components. Even if .NET applications and SIMATIC IT can interact using the interoperability layer provided by the .NET Framework itself (this layer is commonly called “COM Interop”, and guarantees communication between .NET and COM-based applications), the safe use of any other COM interfaces or public APIs is not guaranteed. Please refer to Microsoft knowledge base (available at the Microsoft WEB site http://support.microsoft.com) for a list of currently-known problems and suggestions regarding the use of the COM interop layer.

Interaction with 3rd-party tools

Using 3rd-party tools can interfer with the correct behavior of SIMATIC® IT Historian 6.1.










http://www.microsoft.com/technet/security/Bulletin/M620-740.mspx
































http://support.microsoft.com/


Particular care should be taken when using:

Remote Control

Typically, these tools make it possible to view and fully interact with a specificcomputer from any other computer or mobile device anywhere on the Internet. Some of the most commonly-used tools are: • “NetMeeting” (distributed by Microsoft) • “On Command Remote” (distributed by Symantec) • “VNC” - Virtual Network Computing (distributed by RealVNC) • “pcAnywhere” (distributed by Symantec) Using these tools could slow down overall system performance.

“VNC” and “pcAnywhere” software is currently NOT supported. Please refer to the Technical Support Service ([email protected]) for any questions regarding this issue

Disk Backup and Disaster Recovery utilities

These tools provide data backup and recovery functionalities. Some of the most commonly-used tools are: • “Backup Exec”, “NetBackup” (distributed by Veritas) • “OpenView Storage Data Protector” (distributed by HP) Using these tools could slow down overall system performance: therefore, it is recommended that they be used during low activity periods of the system.

Time synchronization tools

These tools are used to synchronize the local clock of the PC with an external source (e.g. via a GPS) Notes:

• If not properly configured, the use of these tools could slow down overall system performance, due to the high percentage of CPU time they may require.

• It is recommended that these tools be tuned properly, monitoring the use of system resources.

Antiviruses

These tools are used to protect the system from virus infections. Some of the most commonly-used tools are: • “Norton Antivirus” (distributed by Symantec) • “Office Scan, Server Protection” (distributed by Trend Micro)


mailto:[email protected]


SIMATIC® IT Historian 6.1 has been tested with the “Trend Micro“ antivirus software in the following configuration: • On client machine: Office Scan version 5.5 • On server machine: Server Protection 5.56 Siemens will provide customer support only if the product is installed according to this configuration; if a different antivirus software is used, SIMATIC® IT Historian will no longer by covered by legal warranty. Notes:

• Scanning must be configured to run on a periodic basis and must be disabled on all product and project directories of the system.

• It is highly recommended not to configure antiviruses to scan SQL Server files (.mdf and .ldf).

• This activity could affect system performance and behaviour considerably.

Note on SIMATIC® IT Report Manager:

SIMATIC® IT Report Manager V6.1 must be used together with SIMATIC® IT Historian 6.1. SIMATIC® IT Report Manager is the SIMATIC® IT component for reporting on the SIMATIC® IT product portfolio, including: • SIMATIC® IT Production Suite • SIMATIC® IT Historian • SIMATIC® IT Unilab • SIMATIC® IT Interspec SIMATIC® IT Report Manager provides out-of-the box 5 universes and a set of reports to speed up project implementation. Refer to the SIMATIC® IT Report Manager documentation for additional info. Note: SIMATIC® IT Report Manager embeds a BusinessObjects license restricted for reporting on SIMATIC® IT. For more details about license coverage of project customizations, please refer to SIMATIC® IT Report Manager documentation.

MS SQLServer Installation

The following MS SQLServer 2000 editions are available: • Standard Edition



• Personal Edition The software requirements for MS SQLServer are available at http://www.microsoft.com/sql/evaluation/sysreqs/2000/default.asp The “MS SQLServer 2000 for SIMATIC® IT” installation CD is intended only for use with Siemens SIMATIC® IT products. If other uses are foreseen, MS SQLServer 2000 must be installed from the official Microsoft CD. Only the default instance is installed and no other instances can be added. Installation of MS SQLServer 2000 from MES Components SQL Server Setup CD-ROM will also be successful if a previous instance of SQL Server for WinCC is configured on the system. In this case, the user must not use WinCC MS SQLServer instance for Components or for PPA, but he/she must use the default instance just installed. The system administrator login ‘sa’ is installed without a password: it is strongly recommended that a password be entered for ‘sa’, following installation. MS SQLServer must be configured to use mixed-mode authentication; the ‘Windows authentication only’ option is not supported.

Hardware Requirements

Depending on the user’s requirements, several workstation and server configurations are available. However, as a rule, the following types of workstations can be identified: Category Description Server It is a workstation, on which the server components are running.

For the Server workstation, it is assumed that all typical Historian server components are running on the server. Depending on the size of the application, Microsoft Sql Server may run on the Server station or on a separate dedicated station.

Fat Client It is a complete client workstation with SIMATIC® IT Services and all typical Historian client components, on which a large number of operations are executed. It also supports engineering operations.

Lean Client The Historian Lean Client has no SIMATIC® IT Services installed and running, but only a reduced set, called Basic Services. It carries out typical client analysis operations on data from PPA and PDA, by means of the viewer controls provided by Historian Data Display and Historian Excel Add-in.

Web Server MS-IIS and CAB server are running on this server CAB Engineering CAB Engineering station


http://www.microsoft.com/sql/evaluation/sysreqs/2000/default.asp


Minimum and recommended requirements to obtain satisfactory performance Category Minimum configuration Recommended Configuration Server • Intel processor ≥ 2Ghz

• 512-Mb RAM • Intel Xeon processor ≥ 2.5 GHz • RAM ≥ 1-Gb RAM

Fat Client • Intel processor ≥ 1Ghz • 256 - Mb RAM

• Intel processor ≥ 2Ghz • RAM ≥ 512-Mb

Lean Client • Intel processor ≥ 1Ghz • 128-Mb RAM

• Intel processor ≥ 1.5Ghz • 256-Mb RAM

Web Server Please refer to Microsoft documentation. CAB Engineering • Intel processor ≥ 1 GHz

• 512-Mb RAM • Intel Xeon processor ≥ 2.5 GHz • RAM ≥ 1-Gb RAM

Common Requirements

• Disk space required for server or fat client installation: about 400 Mb.2

• The configuration (engineering) workstations require extra disk space for the applications, with regard to the configuration of historical archives, alarms, etc. (to calculate the required disk space refer to the relevant manuals). Therefore, an application may occupy from a few tens to several hundreds of Mb.

• • SVGA monitor card with 800x600 resolution or higher. For

HDD a minimal resolution of 1024x768 is recommended for optimal visualization.

• CD-Rom drive • Mouse • Network adapters

Optional Hardware Printer Please note that SIMATIC® IT Historian 6.1 has been tested with the configurations illustrated above: therefore, it is guaranteed and supported only when used with software and hardware configurations as those previously described. The product has been successfully tested on multiprocessor machines with dual Pentium Xeon and Hyper Threading technology enabled running Windows 2000 SP4 operating system.

2 It should be pointed out that development stations require additional disk space for applications in relation to the

configuration of historical archives, alarms, etc. (For the precise calculation of space, refer to the relevant manual). Depending on how extensive the application is, it may occupy as little as a few dozen to hundreds of megabytes (Mb).



Notes regarding the product’s Setup and use

Windows 2000 configuration

To optimize the use of SIMATIC® IT with Windows 2000, we recommend checking that option “Applications”, rather than ”Background Service”, has been selected in the Windows 2000 “Performance Options configuration (Control Panel Advanced Performance Options).

Using dynamic Screen Savers

We recommend that dynamic Screen Savers not be used, as the resulting CPU occupation may reach 100% of Processor Time.

Optimizing performance

To enhance alarm-display (AMD) and historical data display (HDD) client performance using TCP/IP protocol, a dedicated tool (TCPTune.exe) has been provided. This tool can be found in the installation directory (normally %ICUBEPATH%\BIN). In particular, using this tool, it is possible to operate on the appropriate configuration parameters of the TCP/IP protocol, in order to obtain the following performance enhancements: • Quick reconnection to the server when a switch between servers configured in backup

takes place • Rapid detection of server connection failure in the case of server anomaly. For more information on how to adjust these parameters, we recommend that you please contact our Technical Support Service ([email protected]).




Documentation

It is possible to access the online documentation (manuals and helps) for the entire SIMATIC® IT Historian via the shortcut Start > SIMATIC® IT Documentation. In addition, all online helps can be accessed from the Help menu of the various user interfaces. Installation Manuals can be also found in the \Documentation folder of each setup CD-ROM.

Documentation languages

Online helps are available in both English and German. The following documentation is available only in English. • Historian Installation Manual • Historian Migration Guide • Historian Functional Overview • Historian FAQs (online help)

Known Issues

From Start > SIMATIC IT Documentation, when opening a documentation file, a dialog box that asks the user to either open or save files is displayed. To display documentation, click Open.



Obsolete features

Drivers for Real-Time data sources

The only available drivers for Real-Time data sources are: OPC Client, Modbus RTU, and 3964R. Other drivers are no longer supported but can be substituted with alternative solutions based on the OPC client RTDS interface and a suitable OPC Server.

Abandoned modules

The RMS (Report Manager System) and ODL (Operator Data Logger) modules are no longer supported, although they are installed to guarantee compatibility with previous versions. Please refer to the Technical Support Service ([email protected]) for any questions regarding this upgrade behavior.

Arcnet support

The Inter Process Communication service no longer supports Arcnet networking.

Function Keyboard support

The Function Keyboard is no longer supported.




Known Technical Issues

Intranet/Internet configurations

The tests conducted up to the release of this version primarily concerned Intranet or Internet configurations without the use of a Proxy/Firewall. Using these corporate-network protection systems could result in cases of abnormal behavior.

Services and Management Console

Following a log-off from the plant, the message “Abnormal Termination” of the Session Manager Server is displayed in the Management Console log file. In reality, this message must be disregarded, as it contains erroneous information.

Database Management

• If some variables not defined in the database are detected while compiling an ITER, Ladder, or Block Diagram source file, you can automatically insert them in the database. However, keep in mind that the variables are considered as scalar and permanent-memory in type by default. Also, whereas in the case of Ladder and Block Diagram, the type (integer, real, logic or character) is set correctly depending on the context in which the variable is used, this is not always the case for ITER.

• If you select a database and perform a Save as CSV, the acquisition data is also imported. To delete this information, you must do so manually.



SIMATIC® IT Historian Server

Important Notes

Plant Performance Analyzer

Event Manager interactions

Plant Performance Analyzer makes use of the Event Manager module for scheduling purposes. This means that, in order to function properly, Plant Performance Analyzer needs Event Manager to be up and running. You can run EM manually before starting the Plant Performance Analyzer engine or before adding EM to the SIMATIC® IT Historian startup.

Database Backup

Plant Performance Analyzer does not schedule any database backup: therefore, you must backup the SQLServer database. Please refer to the MS SQL Server BooksOnLine documentation for instructions.

Quality Codes

When retrieving historical data from an external relational database, no automatic conversion of the quality code is supplied; you are expected to use only OPC-compliant quality codes as input.

Hot Backup

The Plant Performance Analyzer engine is not yet available in a redundant (hot-backup) configuration: in case of a system failure, a recovery mechanism is supplied for data retrieved from historical data sources (such as PDA, WinCC TLS, etc), but data loss may occur for real-time data coming from RTDS.

Online updates of PPA configuration

Online updates of PPA configuration are supported only for changes to the SIMATIC® BATCH PCell for the automatic data collection of batch-related process values from the WinCC Tag Logging System. Engineering data can be imported from an Excel file (by means of the “Import Configuration” command in the PPA Administrative Tool). In order to avoid any data loss, it may be necessary to configure a suitable acquisition delay parameter for the Plant Performance Analyzer classes, when retrieving data from a historical data source.

PPA programmatic interface

The PPACOM interface is now exposed by “PPACOMCLI.DLL”, instead of “PPACOM.EXE”. No modification need be made to code using this interface, expect in the case in which a custom project is recompiled. In such cases, the reference to the old “PPACOM.EXE” must be removed and substituted with the new “PPACOMCLI.DLL”.



PPAOBCOM

This new interfaces was added to beta version of Historian 6.1 with ProgId “PPAOBCOMLIB”. As of SIMATIC® IT Historian 6.1, the PPAOBCOM ProgId has been modified to “PPAOBCOMCLI”.

Integration with SIMATIC® IT Production Modeler

When downloading objects with the Clean option set on SIMATIC® IT Production Modeler, the link between KPIs imported from PM and PPA tags will be lost and must be re-engineered manually. Therefore, it is strongly recommended that the Clean option not be used when performing an object download on PM.


Hardware and Software requirements

Refer to general requirement for SIMATIC® IT Historian 6.1. • VBScript engine supported for PPA calcolus is 5.6.0.8825

Backup configurations

In the backup configuration (Management Console Configuration System Modules backup Advanced...), you may no longer select the automatic switchover of the plant on primary Master. Therefore, should the plant be master on the auxiliary server following the close of the primary server, even if this server is started up, the plant remains Master on the auxiliary server. This function is retroactive: as a result, the function is disabled even if the installation is performed on a computer that was already installed with a version < 4.2 configured for automatic switchover.

PDA server PC configuration

It is strongly suggested that DMA (Direct Memory Access) be enabled, from the hardware setup utility of the PC where PDA is running. This optimizes disk usage, thus improving PDA performance.

PPA server use

The main goal of PPA server is to store production and aggregated data. PPA is not a process archive: therefore, its use in this sense is discouraged.



Documentation

Please see the general Documentation section for more information.

What’s New

Client/Server PPA programmatic interface

The PPA programmatic interface (PPACOM) is now a client/server module, allowing custom applications to use it without requiring the PPACOM.EXE to be running on the same machine. The PPACOM interface is now exposed by a client .dll (PPACOMCLI.DLL) that can be used by custom applications.

Custom Data Management

The PPA database can be extended with custom data objects both for engineering data (PPA configuration database) and runtime data (PPA online database). Custom data can be defined by means of programmatic interfaces (PPA APIs) or engineering tools (only for run-time data). Users can define the following for a data structure: name, description, attributes names and attributes types. Custom data can be archived by means of programmatic interfaces both from external applications and PPA scripts. Custom data can be retrieved by means of programmatic interfaces, visualized in a CAB screen, queried by Smart Query Tool, or reported through SIMATIC® IT Report Manager.

Alarm Archiving

Alarm management has an improved reporting performance and supports third party alarm systems.

SIMATIC® BATCH integration

Integration with SIMATIC® BATCH has been extended: • Audit Trail, Electronic Signature, and Comment information can be archived with a

BATCH “Close” event • Operator Dialog information is available • Status change History is archived for Recipe elements • The complete control recipe is stored on a BATCH “Release” event • New COM APIs are available to retrieve BATCH data, add recipe elements

programmatically, and to calculate KPIs based on BATCH data. • BATCH data can be imported into MS Excel




Recovery of SQL connection

Plant Performance Analyzer does not support data recovery on SQL access error due to disconnection for the following data sources: PPA, RTDS and VBScript (Custom).

OPCHDA error: “More data”

PPA does not manage the OPCHDA Server error: "More data".

Import of custom library

PPA configurarion editor (DAMan) crashes following an import of a custom library and no custom libraries were previously defined. Workaround: before executing an import of a custom library, create at least one custom library manually.

Minimun number of points for Alarm Server

Each active Alarm Server must have at least one configured point. If no points are configured, the Alarm Server must not be activated; otherwise, this may create some problems.



SIMATIC® IT Historian Client

Important Notes

User applications embedding ADDX and PDDX

If you are upgrading from versions < 4.2 and you are using applications that embed ADDX (now called AMDX) and PDDX (now called HDDX) controls, and the applications refer to these controls by means of their ProdID, you must modify the controls in order for them to be compatible with this version. This is due to the fact that the ProdID has been changed in order to reflect the new names.

Lean Clients

Two types of Lean Clients are defined: • “Basic Lean Client”: the classic Lean Client, which contains Historian Data Display

together with Alarm Manager Display and GUI runtime; • “Historian Lean Client”: the new Lean Client, essentially consisting in Historian Data

Display. Important modifications: Both Basic Lean Client and Historian Lean Client require the installation of Basic Services as a prerequisite; CAB pages using HHD controls require the installation of Web Basic Services when used on a web client. The Automatic Update is no longer supported, although you will find all options related to this functionality from the configuration windows. The use of the feature is discouraged as the automatic update will be abandoned in the near future and currently no support is available. The HDD lean client has changed its user validation method: user rights will be validated on the default foundation server configured. On the contrary, the old HDD lean client validated user rights on the foundation server configured for the PDA to which it was connected.

ActiveX Message Viewer Automatic Update In the case of automatic updating, the messages returned are those dating from the time of the last message up to the current time (TNow – LastSampleTime): as a result, even if previous messages have been recovered, they will not be displayed. To display all messages, including those recovered, a "Refine Query" must be performed manually.



Excel Add-In

Operation window

The dialog box shows messages related to the insertion of data into PPA. The window remains empty when using RDTS data.

Project name

The name of the project for Excel Add-in was renamed from “VBAProject “to “HistorianAddIn”. This does not introduce any incompatibility into existing user projects. However, if the reference to the old project is eliminated and substituted with a new one, the name of the old object must be changed to the new name. For example VBAProject.Function(....) must be modified into HistorianAddIn.Function(...).

Automatic load from Excel

If Excel Add-In is not loaded automatically, please check the following settings: from the menu Tools Macro Security, verify that the ‘Security Level’ is high; if it is, enable the ‘Trust all installed add-ins and templates’ option present in the ‘Trusted Sources’ tab.

Updating automatic links

Excel worksheets using SIMATIC® IT Historian Excel Add-In require the update of automatic links in the following circumstances: • Upgrade of a worksheet based on Excel Add-In version 4.3 • Transfer of the worksheet to a disk other than the one where Excel Add-In is installed. To perform the update, the user must use the macro “ChangeSource” included in the Add-In. Please refer to online help for a detailed description of the procedure.

Internal methods

Some internal features available with version 4.3 have been changed/removed. No documentation of those methods was presented, because they were available only for internal use. Please refer to the online help for the up-to-date list of the methods currently available.


ActiveX Message Viewer memory requirements

The memory used by this component is directly related to the configured value for the maximum number of messages cached (the default value is 5000 messages). The user must be aware that incrementing the cache size will require more memory and can degrade the performance of the system. It is not possible to calculate the required memory for custom messages, as they contain variable length fields, whereas batch messages have a fixed memory occupation of 10K-bytes.



ActiveX Production Viewer memory requirements

The memory used by this component is directly related to the quantity of data displayed. In the case of dynamic update, it is strongly recommendedthat a filter be used on the query to limit the amount of data displayed and avoid high memory consumption.

Documentation

Please see the general Documentation section for more information.

Obsolete features

OLE support for HDD

The HDDX control is no longer supported as an OLE Object.

What’s New

Custom Messages

It is possible to display user defined custom messages through the use of ActiveX Message Viewer. The visualization must be 'Extended' or 'Compressed' according to the defined filter.

Equipment-relative charts

Tag alias names (Equipment Properties) can be used to build charts in Trend and Bargraph viewer; these names are automatically translated into the corresponding tag, depending on selected context (e.g. Batch, Production Operation).

Extended support of offline data

It is possible to compare data from online and offline databases (e.g. compare latest Batch with a one-year-old Batch).

Bound Limits and Target Limits

It is possible to display an upper limit, lower limit and more target values to evaluate the trend of the process.



Context information in chart legend

Any context attribute (e.g. Batch attributes, Production Operation attributes) can be added to the chart legend.

Organizing chart files into folders

It is possible to create subfolders to improve the organization of chart files (quick and efficient access to the HDD files).

Unicode Support

ActiveX controls of the run-time user interface are available also in Chinese (the description of tags, snapshots, equipments etc. can be displayed in the language chosen during the configuration phase).

Date / Time format selection

Available Date Formats: Windows default, dd/mm/yyy, mm/dd/yyyy, yyyy/mm/dd Available Time Formats: Windows default, 12 (AM/PM), 24 H


Historian Data Display

• If modifications are made to a point’s maximum and minimum values, workspaces must be reloaded to permit their proper display.

• When specifying a filter, it is recommended that the Equipment field in the Production Viewer Configuration Wizard be left blank.

Historian Basic Lean Client

• If you perform a logoff while connections to Lean Clients are still active, the dialog boxes containing the relative messages are displayed correctly. If you also attempt to disconnect from the Lean Client side, the system may need a few seconds before disconnecting.

• If the GUI Run-time component is activated, the new hotkey combination Ctrl+Q for enabling/disabling the title bar and the menu bar is managed only if the GUI Run-time component loses focus, whereas the right click to call up the pop-up menu is managed correctly.

• Closing Fat Clients when Lean Clients are connected and active may result in inconsistent behavior on both the Fat Client and the Lean Client.



Lean Client Gui connection problem with Xp sp2

On a Lean Client with Windows XP Service Pack 2 installed, the GUI Runtime is unable to connect to the server. Workaround: modify the authentication level from <None> to <Default> using the following procedure: 1. Start the DCOM configurator (DCOMCNFG.EXE) 2. Select Component Services / Computers 3. Right-click My Computer and select Properties 4. From the Default Properties tab, set the default authentication level to Default



SIMATIC® IT Services 5.0

Important Notes

PCS7 Tag Browser

The PCS7 Tag Browser is not officially supported by this product version. Although the component is installed, Siemens will not provide any support until the next product version.

User Change on Citrix

Due to a particular Hotkey management on Citrix Client, the instructions below must be followed to change the user: • Publish the RACHK.EXE application (in %ICUBEPATH%\BIN) to the client • Execute this application on the client side • When a user change is necessary, set the focus on another application running in

CITRIX mode and then press Shift+Esc. At this point it is possible to insert the login and password of the new user.

User Change on Terminal Server client (Remote Desktop Connection)

The first time you connect to the machine with TS support, customize the Desktop as follows: Create a shortcut of RACHK.EXE process on the desktop. When you connect, creating a session, run the program by clicking on the shortcut. When the user must be changed, press Shift+Esc and insert the new user name and the relative password.

IPC Communication port

By default, IPC Services uses port 3002 for TCP transmission. If you are accessing the network through a firewall, your firewall administrator must authorize this port or change, with the IPC Configuration wizard, the Ris port number in accordance with opened port in the firewall. If you change the default, verify that all workstations in the SIMATIC® IT configuration have the same port number configured.

MSM Display Client on Http environmental

If you force a particular client to use the HTTP or HTTPS protocol for the communication, by using contexts (See CAB Protocol Configurator documentation, available from the Help > Contents & Index menu of SIMATIC IT Management Console), Messaging Manager Display Client may display its messaged received more slowly.



To increase the message download rate of MSM client side, in this environment, the following configuration must be set: By Regedit, create the following entry in the registry: HKEY_LOCAL_MACHINE\SOFTWARE\SIEMENS-ORSI Automation S.p.A.\Simatic IT\Messanger\Parameters\ Set the value:

PollingRefresh=3000

Proxy Configuration

The communication channel via Http uses Microsoft® Windows® HTTP Services (WinHTTP) In order to use Internet proxy, the Microsoft utility proxycfg must be run with parameter u:

proxycfg –u This utility creates the following entry in the register HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\ CurrentVersion\Internet Settings\Connections\WinHttpSettings

With parameter –u, IPC services with channel Http will use the Internet Explorer settings in order to access the Internet proxy.

SIMATIC Logon

The authentication of users imported from Windows, by using SIMATIC Logon, is granted only if it is executed in a domain. In other cases, if SIMATIC Logon is installed, SIMATIC Logon must be disabled by checking the proper check box in Import User Tool.

Compliace Services upgrade

If it is being upgrated from a previous version, the Compliance Services configurator (from ISM menu > configuration ) must be started in order to convert the default DataBase.

Internal tools

The DllDebug application and SitMon application are internal tools which monitor operations in applications and libraries and can only be used under the supervision of Technical Support.

Standard User Manager

To use standard User Manager on Basic services, RAC.ENG must be copied and renamed "RAC.CHI".



Notes for Web installation

On Web installation it is necessary to manually register MsgBrwGrid.ocx and complSrvX.ocx: Launch a Command Prompt and type "regsrv32 %ICUBEPATH%\BIN\MsgBrwGrid.ocx" "regsrv32 %ICUBEPATH%\BIN\complSrvX.ocx". On Windows 2000 SP4 with Internet Explorer 6 SP1, it is also necessary to manually register CDT.dll: Launch a Command Prompt and type "regsrv32 %ICUBEPATH%\BIN\CDT.dll" then restart the PC.

Chinese language

From this version, the capability to integrate the Chinese Language has been added to SIMATIC® IT products. To enable this language it is necessary to launch the application "add_chinese.exe".

Compliance service

From this version, the plant must always be shared when using Compliance Services.


Two installation options exist for SIMATIC® IT Services 5.0: • Full Services: provides all functionality of SIMATIC® IT Services • Basic Services: provides limited client functionality:

• Core functionality (interprocess communication, localization management, etc.) • MSM Display Client • Compliance Service Viewer

Hardware and software Requirements

Refer to the general requirements for SIMATIC® IT Historian 6.1.

Documentation

Please refer to the general Documentation section for more information.



Obsolete features

Stand Alone Mode

The “Stand Alone” working modality is no longer supported and has only been kept for compatibility. It is always necessary to define both a network configuration and a Foundation Server (on a configuration consisting of a unique station - it stands to reason that the foundation server corresponds to the unique existing machine) If the StandAlone mode is selected, a warning dialog is displayd.

What’s New

SIMATIC Logon

The User Manager Module is intregrated with SIMATIC® Logon.

SIMATIC License Management

This version is completely integrated with Siemens Automation License Manager.


Terminal Server support for Basic Client station

If you want to add Terminal Server/Citrix support to a Basic Services station, the following steps must be executed:

1. Close all SIMATIC® IT applications that are active on the client 2. From a command prompt, run the command "net stop simaticitipc" 3. Rename “rqmlib.dll”, which is located in the directory “%ICUBEPATH%\BIN”, to

“rqmlib.UFF” 4. Rename rqmlib_”TS.dll”, which is located in the directory “%ICUBEPATH%\BIN”, to

“rqmlib.dll” 5. From cmd set the command "net start simaticitipc"

The TS/Citrix support is active for applications which support it.



From a services’ point of view the support is assured (IPC, Access Control). It is mandatory to verify whether or not the applications support this working procedure. The following applications completely support TS/Citrix mode: • Messaging Manager Display Client • Compliance Services Common Viewer • Historian Data Display (Historian)

Cab Protocol Configurator

It is not possible to visualize the relative file by clicking the Help Button. Refer to services help. In this version, there is no check on the syntax of entries which have been inserted in protocol configuration fields. Specifically, in the field “WEB SEVER IP” the server IP address must be inserted containing the SITISAPI EXTENSION.

Lock Object Server

The Lock Object Server is not integrated in the Management Console. To use this server the file LockObject.and, contained in the %ICUBECNF% from the MMC > System Configuration, must be loaded as a Third Part application.

Compliance Service

The format of the Audit Trails’ database has been changed: the old databases can no longer be used. In terms of secure store management, the reference between the ER and the AT is established in a more effective manner using the “ObjectID” field of the AT managed with specific functions. If secure store is not required, this field can be managed by the application. In this case, the ‘#’ character is not allowed in the “ObjectID” field. In the AT Repository, only the records with GMPRelevant=1 are valid Audit & Trail.

Messaging Manager

Groups of radio buttons may have encounter problems if the buttons are not aligned vertically or horizontally. In Template Editor, the template or area does not refresh correctly when scrolling.

PCS7 Tag Browser

In the CCINSInfoBrowser ocx, when the user clicks the "Symbolic Name", "Status", or "Unit" column headers, listed tags are sorted by tag name.



SIMATIC® IT CAB 1.1

Important Notes

CAB Library Toolbox Configuration

In order to use the CAB Graphic Components they must be added to the VS .NET Toolbox. To do this perform the following steps: 1. Open Microsoft Visual Studio .NET 2. Launch the “Reload Toolbar” command from the VS.NET “CAB” menu If the operation is completed successfully, the VS .NET Toolbox will contain extra tabs filled with components from the CAB Library.

CAB Runtime Client Security Configuration

SIMATIC® IT Client Application Builder is designed to be compliant with Internet Explorer’s default security level. Set Internet Explorer’s default security level as follows: 1. Open Control Panel 2. Double-click Internet Options 3. Select the Security tab 4. Select Web Zone Internet 5. Click the Default Level button 6. Repeat step 5 selecting the Web Zone Local Intranet and Trusted Site. 7. Click Apply and OK Add the CAB Application web server to the Trusted Site in the Internet Explorer Configuration. To accomplish this task, the following steps must be executed: 1. Open Control Panel 2. Double-click Internet Options 3. Select the Security tab 4. Select Trusted Site 5. Click the Sites... button 6. Add the site name where your CAB Application resides. (e.g. http://myCABSite) 7. Click OK.



CAB Runtime WebServer Security Configuration

The “DiscoveryAccess” process must grant access and launch permissions for the APSNET user (for IIS5.1) or NETWORK_SERVICES user (for IIS6.0) using Microsoft dcomcnfg or oleview utilities. SIMATIC® IT Client Application Builder MM Data Provider requires some extra security configurations when MM Server is installed and running on a CAB WebServer machine. The “MM.HutServer”, “MMSrv.MMConnector”, and “MM” processes must grant access and launch permissions for the APSNET user (for IIS5.1) or NETWORK_SERVICES user (for IIS6.0) using Microsoft dcomcnfg or oleview utilities.

Upgrading Smart Query Builder queries

After upgrading to SIMATIC® IT Historian 6.1, all queries created with Smart Query Builder must be refreshed in order to function correctly. All CAB pages which reference them must be updated as needed.


Three installation options exist for SIMATIC® IT CAB 1.1:

- CAB Server - CAB Engineering - CAB Web Server


Refer to the general requirements for SIMATIC® IT Historian 6.1.

Documentation


Obsolete features

Component DataProviders

DataProviders for SIMATIC® IT Historian 6.1 components are no longer supported. They are only provided to guarantee compatibility with previous versions of the product. Component data is accessed through Smart Query Builder.



Fixed Technical Issues

Regional settings mismatch

CAB 1.0 HotFix1 Release Notes described a workaround for the “Regional settings mismatch” problems. In CAB 1.1 a simplified “workaround” was introduced.

SYMPTOMS

If your server machine has regional settings that do not match with the settings used by ASP.NET during runtime, you can correct errors loading date/time or other culture dependant data types (e.g. “System.FormatException: String was not recognized as a valid DateTime”).

WORKAROUND

Both CAB 1.1 MM and POM DataProviders “server culture” can now be configured directly in the web.config file of a CAB WebApplication. For example: <appSettings> <add key="mmServerCulture" value="it-CH" /> <add key="pomServerCulture" value="it-CH" /> </appSettings>


CAB Web Server and CAB Server machine name problems

Domains that use cookies can only use alphanumeric characters ("-" or ".") in the domain name and the server name. Refer to “PRB: Session Variables Do Not Persist Between Requests After You Install Internet Explorer Security Patch MS01-055” article at http://support.microsoft.com/default.aspx?scid=kb;en-us;316112 for more details.

CAB Script Editor and keyboard shortcuts

While writing code with CAB Script Editor some keyboard shortcuts (F5, CTRL+key, etc…) are captured by CAB. To solve this problem, remove the focus from the CAB Script Editor.

How to make a Session survive its natural timeout without user interaction

SYMPTOMS

When you have a web page containing “self-updating” graphical objects and users need to open this page without refreshing it for a long period of time, you may experience a “session expiration”.


http://support.microsoft.com/default.aspx?scid=kb;en-us;316112


The user may be requested to re-login to the application or may even lose the connection with the server side engine.

CAUSE

On the web server, each “user session” (i.e. a sequence of a user’s browsing actions) is associated with a SessionState object that has a default timeout period of 20 minutes (see web.config file, tag sessionState, attribute timeout).

WORKAROUND

To overcome this problem periodical activity must be performed with the web server to retrigger the Session timeout. One way of doing this is as follows.

1) Add a new empty webform to your application (e.g. Pong.aspx).

2) On the “Page_Load” event handler of the inserted page, add the following line. C#: Response.Cache.SetCacheability(HttpCacheability.NoCache); VB.NET: Response.Cache.SetCacheability(HttpCacheability.NoCache)

3) In Global.asax, add a variable containing the script that will be injected on selected pages. C#: private string _stayAlive = "<script language=\"javascript\">" + '\n' + "var pingTime = 4000;" + '\n' + "var timerId;" + '\n' + "var req;" + '\n' + "function ping() {" + '\n' + " req = new ActiveXObject(\"Microsoft.XMLHTTP\");" + '\n' + " req.onreadystatechange = receive;" + '\n' + " req.Open(\"GET\", \"Pong.aspx\", true);" + '\n' + " req.send();" + '\n' + "}" + '\n' + "function receive() {" + '\n' + " if (req.readyState == 4) {" + '\n' + " if (req.status == 200) {" + '\n' + " window.status = \"Ok on: \" + new Date();" + '\n' + " }" + '\n' + " }" + '\n' + "}" + '\n' + "timerId = window.setInterval(\"ping();\", pingTime);" + '\n' + "</script>"; VB.NET: Dim _stayAlive As String = "<script language=""javascript"">" & Environment.NewLine & _ "var pingTime = 4000;" & Environment.NewLine & _ "var timerId;" & Environment.NewLine & _ "var req;" & Environment.NewLine & _ "function ping() {" & Environment.NewLine & _ " req = new ActiveXObject(""Microsoft.XMLHTTP"");" &



Environment.NewLine & _ " req.onreadystatechange = receive;" & Environment.NewLine & _ " req.Open(""GET"", ""Pong.aspx"", true);" & Environment.NewLine & _ " req.send();" & Environment.NewLine & _ "}" & Environment.NewLine & _ "function receive() {" & Environment.NewLine & _ " if (req.readyState == 4) {" & Environment.NewLine & _ " if (req.status == 200) {" & Environment.NewLine & _ " window.status = ""Ok on: "" + new Date();" & Environment.NewLine & _ " }" & Environment.NewLine & _ " }" & Environment.NewLine & _ "}" & Environment.NewLine & _ "timerId = window.setInterval(""ping();"", pingTime);" & Environment.NewLine & _ "</script>" This is just a sample. The body of the function receive() is only a suggestion.

4) On Global.asax, add the following event handlers. C#: private void Global_PreRequestHandlerExecute(object sender, EventArgs e) { System.Web.UI.Page p = Context.Handler as System.Web.UI.Page; if (p != null) { // Check here what page include or exclude. E.g. : if (Request.CurrentExecutionFilePath != "/StayAlive/Pong.aspx") { p.PreRender += new EventHandler(InjectScript); } } } private void InjectScript(object sender, EventArgs e) { System.Web.UI.Page p = sender as System.Web.UI.Page; if (p != null) { if (!p.IsClientScriptBlockRegistered("ALIVE")) { p.RegisterClientScriptBlock("ALIVE", _stayAlive); } } } VB.NET: Private Sub Global_PreRequestHandlerExecute(ByVal sender As Object, ByVal e As EventArgs) Handles MyBase.PreRequestHandlerExecute If TypeOf Context.Handler Is System.Web.UI.Page Then Dim p As System.Web.UI.Page = CType(Context.Handler, System.Web.UI.Page) AddHandler p.PreRender, New EventHandler(AddressOf Me.InjectScript) End If



End Sub Private Sub InjectScript(ByVal sender As Object, ByVal e As EventArgs) If TypeOf sender Is System.Web.UI.Page Then Dim p As System.Web.UI.Page = CType(sender, System.Web.UI.Page) If Not p.IsClientScriptBlockRegistered("ALIVE") Then p.RegisterClientScriptBlock("ALIVE", Me._stayAlive) End If End If End Sub 5) Adjust the request period changing the value of the script variable pingTime (in

milliseconds). 6) Adjust the name of the page to call (in our example “Pong.aspx”).

Viewing a page you should be able to find the injected script by clicking “View Source” in Internet Explorer. Another check you can perform is to start your application in debug mode and set a breakpoint on the “Page_Load” event handler of the page “Pong.aspx”: you should see a periodical invocation.

Known Technical Issues (CAB)

After the installation of a ZAC client, the MsgBrwGrid.ocx must be manually registered through the system utility REGSVR32.EXE.



SIMATIC® IT BPM 5.0

Important Notes

Set the Plant in SIMATIC IT Production Modeler “CURRENT”

In SIMATIC® IT Production Modeler, the user must set the plant to CURRENT if it must be selected from SIMATIC® IT Production Order Manager (POM) or imported into Historian Plant Performance Analyzer.

How to change the Pcell link to another BATCH UNIT

In SIMATIC® IT Production Modeler, the sub UNITs of a PCell linked to a SIMATIC® BATCH PCell (through the SIMATIC® IT COM Interface for SIMATIC® BATCH) can also be linked with the UNITs in SIMATIC® BATCH. This link is performed through the attribute “SB-UNIT-NAME”. To modify the link to another SIMATIC® BATCH UNIT, it is strongly recommended that the following steps are performed: 1. Clean the attribute by removing the link 2. Save the Production Modeler Plant in Business Process Modeler Database 3. Import the Plant Model in Plant Performance Analyzer 4. Define the new value for the SB-UNIT-NAME attribute and perform step 2 and 3 again

Deleting a Plant

When deleting a Plant from BPM, a check is performed to verify that data referenced by other components are not deleted. This can lead to a persistence of some data in the BPM database even if the deletion is correctly performed.

Production Modeler server indication

The SetEquipProperty (BPMServer) and ChangeEquipmentProperty (BPMBrowser) methods require the correct specification of the running Production Modeler server. This can be configured from the Options option in the BPM Server form.


Three installation options exist for SIMATIC® IT BPM 5.0: - BPM Server - BPM Configurator - BPM Display




Refer to general requirements for SIMATIC® IT Historian 6.1.

Documentation


What’s New

Versioning

BPM is able to archive several versions of the same plant or library in the SQL Server database.

Unicode support

All textual fields support UNICODE character sets.

Distributed transaction

Using the new COM (BPM Browser) interface, all methods can be provided with a transaction cookie that allows the BPM server to participate in a distributed transaction, coordinated by Microsoft Distributed Transaction Coordinator.

BPM-EQUIP-TREE-OCX

This new OCX show the hierarchy of each plant archived in the database and the list of equipment and objects contained in each library. It is possible to apply filters to choose the objects retrieved from the database.

Fixed Technical Issues

Configuration

The configuration of database connection parameters is no longer needed in the .INI file. All connection parameters are managed by the “Component Database Configurator” tool and are stored in the system registry.




Incremental Import in PPA

For a plant model imported into PPA, BPM stores all changes to allow alignment with PPA. Changes must be stored in a strictly chronological order. In some circumstances, BPM may be unable to guarantee the chronological order of archived modification. In such cases, the incremental import from PPA may experience problems.

Default name for Process Segment (or Production Operation) Rules of Rules

BPM supports only the default name of the Process Segment Rules of Rules (or Production Operation Rules of Rules): “INITIALIZE”, “EXECUTION”, “END”. If you rename them, BPM will not function properly.

Hierarchy of the Process Segment (or Production Operation) Rules of Rules

BPM builds the hierarchy of the Process Segment Rules of Rules (or Production Operation Rules of Rules) through the configuration of the Start-Segment (or Start-Product) steps in SIMATIC®

IT Production Modeler. If you want to create a hierarchy among PSs (or POs),

you should ensure that you only browse the instances of the production operations.

Downloading PS/Po hierarchies

If you do not succeed in obtaining a hierarchy among PSs/POs in SIMATIC® IT Production Order Manager, download the root PS/PO (download-objects starting from the root PS/PO) again. It depends on the order in which the child POs were downloaded in the database.

Association Between the PO and the Final Material

A PO can only have a single Final Material (however, any number of input/output materials can be specified as associated with the PO)


Documents

Historian IT