PC-based visualization system 1 Task definition and objectives 1.1 Plant specification 1.1.1 Volume of information 1.1.2 Process images 2 Demands on the visualization system 2.1 Basic system requirements and system features 2.2 Uniform, window-oriented operator interface 2.3 Protection against unauthorized access 2.4 Openness and integration capability 2.4.1 Open interfaces for standard software 2.4.2 Open interfaces for application software 2.5 System behavior in case of disturbances 3 System and plant concept 3.1 Plant configuration 3.2 Printer 3.3 Local area network (LAN) 4 Software components of the visualization system 4.1 Operating system 4.2 Graphic system 4.3 Basic data processing 4.3.1 Signal processing 4.3.2 Measured-value processing 4.3.3 Commands / Setpoint values 4.4 Operator-process communication and process visualization 4.4.1 Process images 4.4.2 Curve displays 4.4.3 Event reporting/analysis/acknowledgement 4.5 Logging system 4.6 Archiving system 4.7 Recipes 4.8 Specifications 4.9 Display creation 4.10 Documentation 6. Technical specifications / quantity frameworks 1. Task definition and objectives A PC-based visualization system for use at the machine level is to be installed in the plant as part of the project. Installation of the visualization system includes links to various programmable controllers (PLCs). The PC-based visualization system must be able to implement the following functions: o Visualization via a Windows-compliant operator interface o Alarms and messages o Archiving of messages and process values o Recipes o Documentation of process data, events and recipes o Flexible expansion of system functions through Visual Basic Script o Language support for multilingual projects o User-oriented access protection in accordance with the demands of regularized sectors o Link to a wide range of controllers o Open communication between HMI systems and with higher-level systems o Remote operation, diagnostics and administration over intranet and Internet o Easy plant expandability thanks to the integration of panels with uniform engineering 1.1 Plant specification 1.1.1 Volume of information: The probable volume of information which must be transferred between visualization system and PLC level is summarized in the tables below. The tables describe the minimum demands on the visualization system as regards the volume of information to be transferred and processed. Volume of information: Number Type PLCs to be interfaced Binary signals Measured values Commands Setpoint values Count values Computational values Data volume 25 % must be allowed for as reserve. 1.1.2 Process images Number Type of display Plant display Trend display Setpoint display Tables/Statistics 2. Demands on the visualization system 2.1 Basic system requirements and system features The visualization system must correspond in design and function to the current state- of-the-art as operator system and its hardware and software is to be future-oriented. The visualization system must be a modern system with attractive operator interface, open to the office and process world, fully developed and reliable in its functions, efficiently configured, and scalable for simple and complex tasks. It must also be suitable for worldwide use and have international service support. Commercially available office or industrial PCs with Microsoft Windows 2000 or Windows XP must be used as operating and server stations, allowing the visualization system to profit from the innovations and cost savings options available in the PC sector. To allow the project to grow, a cost-neutral increase in the number of variables must be possible at any time, i.e. price-optimized entry-level systems and subsequent expansions must be price-neutral. The communication channels and the links to SIMATIC S7 controllers via diverse communication media must be included in the delivery scope of the visualization system, e.g. simple drivers for point-to-point links or standard Ethernet drivers. In addition, communication must be possible with devices and applications from other manufacturers over the standardized OPC software interface. The visualization system must be distinguished by the following system features: - PC basis und standard operating system - executable on all popular PCs equipped with Pentium processor - 32-bit software designed for the standard Microsoft Windows operating system. - direct use of hardware and software from the PC sector (e.g. LAN cards) - can be used as single-user system - HMI modules - Graphics system For freely configurable visualization and operator control via pixel-graphics objects (Windows, OLE, OCX and ActiveX objects) with dynamic option. A block library aids in the generation of displays. - Messaging system For the acquisition and archiving of events with display and operator input options; freely selectable message classes, message displays and reports. - Process data archiving For collecting and archiving of measured values, e.g. for curve displays, etc. - Reporting and logging system For time-driven or event-controlled documentation of messages, message archives, recipe data and current data in the form of user reports (process data) or project documentation (feedback documentation of configuration data) in flexible, freely selectable layout. - Processing functions For the configuration of events for objects and the formulation and editing of scripts with Visual Basic Script. - Open interfaces - Integration of Windows application blocks (ActiveX Controls) - Data exchange with other Windows programs over the OPC interface - Interfacing to SIMATIC S5, S7, 505 and controllers from other manufacturers (e.g. via native drivers or OPC) 2.2 Uniform operator interface By means of individually configured operator interfaces, the visualization system can be used to optimize process events and make them more transparent. Functions are available which ensure an efficient and secure process mode. The layout of the operator interface must reflect a flexible and task-oriented display of the process dialog. For a better overview, the process image screen can be subdivided into overview area, workspace area and key area. Wizards automatically create this ergonomic, process-oriented subdivision of the process image screen and structure the process images into hierarchies. Displays which have already been configured can be brought to the intended location in the hierarchical tree structure on an object-oriented basis using the mouse. All area displays and detail displays can also be selected directly by means of internationally accepted key combinations. An option must be available for utilizing other applications through configuration. In addition, it must be possible to fall back on OCX/ActiveX objects. The functionality of other programs can thus be homogeneously integrated in the visualization system's operator interface. The visualization system is to utilize the following input resources familiar from the Windows world: Keyboard, mouse or touch screen resp. soft keyboard When the standard cursor is positioned above operator-controllable objects, its depiction must change (I/O field: mouse pointer plus cursor symbol; mouse- controllable object: mouse pointer plus arrow). 2.3 Protection against unauthorized access All instances of operator control of the process must have an interlock option against unauthorized access. These include, for example, the changing of setpoint values or the selection of images. There are different access privileges for enabling the creation of hierarchical access protection as well as exclusive authorizations for individual operators. Password and user name determine an operator's access privileges, and these privileges can be changed even during the course of the process. A user-friendly user management system is available for this purpose. Validity expires after a specifiable time period during which no further operator input has been made. The visualization system thus ensures that only authorized operators may implement critical operator actions and that the process remains secure. 2.4 Openness and integration capability 2.4.1 Open interfaces for standard software The integration of standard Windows applications such as MS Excel, MS Word or MS Access must be possible by means of the standard mechanisms OLE/ActiveX and ODBC/SQL. In order to enable cross-vendor communication, the visualization system must be OPC-capable. Current process data must be made available to other computers and applications over OPC, making it possible for any computers interfaced to the network to access all process values (variables) from the visualization system. 2.4.2 Open interfaces for application software It is extremely important that the visualization system offer options for the homogeneous integration of application blocks in the operator interface for the process. ActiveX Controls can be integrated in the visualization system application. 2.5 System behavior in case of disturbances Following elimination of a fault (e.g. warm PC restart), it must be ensured that the entire system resumes operations automatically without any need for operator intervention. The process image must also be updated. 3 System and plant concept 3.1 Plant configuration The required plant configuration provides for the use of industrial HMI systems as data servers for higher-level automation components, such as control systems or systems in the office world. In a control display, for example, process values from different machines are displayed without the field level being burdened by communication requests from the management level. Remote control and remote monitoring of the visualization system must be possible over the Internet/intranet. Web-based browsers (such as the Internet Explorer) are to be used for access. The following remote functions must be made available in addition to remote control: - Starting and stopping the runtime (e.g. for maintenance purposes) - Remote access to recipe data records, passwords and system-specific information - Access to the visualization system's files - Downloading of configuration data - Sending e-mails over SMTP servers; triggered by e.g. a signal Password protection will be provided for accessing the visualization system. It must be possible to configure passwords for different functions. 3.2 Printer The printer in the operator station is normally used for operations control. It must be available as color printer, the printer will be used for hardcopy printouts of on-screen color graphics. The printer is also to be used for printing out process and archive data such as current actual values, alarms or measured values. 3.3 Local area network (LAN) A local network is used to interface the PLC level to the visualization system. Links between the computers interfaced to the visualization system must be implemented according to IEEE 802.3 (Ethernet). TCP/IP protocols must be used for this purpose. 4 Software components of the visualization system 4.1 Operating system Use of the following operating systems is mandatory throughout the entire local network: - Operator workstations: Windows 2000 or XP Professional 4.2 Graphic system The visualization system's graphic system must provide on-screen processing of all input and output during the course of the process. The displays for plant visualization and control consist of both simple and complex graphic objects. These graphic objects are integrated in the displays with the aid of the visualization system's integrated graphic editor during the configuration phase. A series of objects must be available for creating and operating an attractive operator interface: Static objects, such as - Line - Polygon, Polygon line - Circle - Ellipse - Rectangle - Rectangle with rounded corners - Static text Pre-generated objects, such as - Curve displays, event displays - User management display - Recipe display - OCX (ActiveX) objects - Input and output field - Status/control of variables (SIMATIC S7) - Bars - Graphic objects (BMP, WMF, EMF, GIF, JPG or via OLE) - Status displays - Text lists - Time-of-day - Pointer - Switch - Button - HTML browser - Slider object It must be possible to control the appearance of graphic components dynamically. Determinative variables for geometry, color, pattern, etc., can be directly addressed and selected by means of variable values or from within programs. For example, a line can be colored red, green or blue, a circle can be changed in size or moved on the screen. Status displays can be controlled by means of the alternate fading in and out of individual, superimposed graphic objects. In this way, the process, processing within the visualization system, and events can actively influence the screen displays. Examples of properties which can be changed dynamically: - Object color - Background color - Line color, type, beginning, end - Font style - Language for texts (by operator entry) - X and Y position in pixels - Display of objects (visible/hidden) - Radius of a circle - Authorization (by operator entry) - Upper and lower limit for bar graph - Scaling and scale marks for curves (by operator entry) The visualization must also offer a possibility for using existing graphics or photo material in displays. Graphics files in format BMP, WMF, EMF, GIF, JPG or OLE can be imported. 4.3 Basic data processing 4.3.1 Signal processing The event signaling system processes the results of functions which monitor events in the process, at the automation level and in the system. It displays recorded events and archives them electronically and on paper. Access options and options for sorting event messages and supplementary information for specific event messages in ascending or descending order ensure fast fault localization and elimination. The event message structure can be freely defined and must therefore be matched to the special requirements of the plant in question. An event message consists of a message text which can also contain variable values. In total, it should be possible to configure as many as 4,000 different messages. The visualization system must generate messages based on: - Bit variables Bit variables are managed as part of the variable group in the HMI system, making it possible to trigger messages with "Write variable" actions. - Analog variables With the aid of the limit-value monitor, any number of limit values can be defined for a variable. When one of these limit values is exceeded, a message is generated in the runtime system. - System monitors - Arrival of messages (Alarm_S) - from the process - from the automation level - from an action The messaging system consists of a short-term archive. The oldest entries are always deleted. The archive can be transferred to an external storage medium. A selection criterion specifies which messages are to be archived. The size of the archive is limited by the number of entries. The system must automatically warn the operator when the archive has reached its maximum size. 4.3.2 Measured-value processing The visualization system archives measured values from the programmable controller. Acquired measures values can be processed with definable actions before being stored. The acquisition of measured values may be cyclic or event-controlled via the variable group, making it possible to acquire both process values and values of internal variables. Storing saves the processing results in the measured-value archive on a read-only storage medium. The acquisition cycle can be specified by the operator. The archiving cycle can be the same length as or a multiple of the acquisition cycle. Acquired measured values can be immediately written to the hard disk to avoid loss of data (instantaneous values). The visualization must offer several methods for archiving measured values. It archives measured values on a cyclic or event-driven basis. A distinction is made between the following procedures: - Continuous cyclic archiving - Selective cyclic archiving - Acyclic archiving - Archiving only in the event of a change 4.3.3 Commands / Setpoint values The user must be able to initiate switching actions or command outputs by means of plant displays (process images) or other screen forms provided for this purpose. The execution of a command (bit command or setpoint) is – assuming the relevant parameters have been set – expected and monitored by the visualization system in the form of a checkback signal. The setpoint values parameterized in the system must be displayed as physical values in a screen form. The visualization system inhibits the unauthorized output of commands and setpoint values by means of password protection. 4.4 Process control and process visualization This component allows the user to monitor the process, to intervene in the process, and to define and change system and process parameters; visual display units with pixel graphics, keyboard and mouse are available for this purpose. For the most part, the process is controlled and monitored using: - process images - process information system - curve displays - message evaluation system 4.4.1 Process images In order to simplify the use of the visualization system for the user, process images are organized in the form of a hierarchical function tree: - Machine/plant overview - Machine/plant segment display - Object-detail information The visualization system's graphic editor must provide functions customary in powerful Windows graphic programs. It must also provide functions for precise positioning, aligning, turning or mirroring graphic object properties, as well as grouping, block formation, and the import of externally edited texts, and the embedding of graphics (BMP, WMF, EMF, GIF and JPG format or via OLE). Its ability to have multiple displays open at the same time permits fast copying between different displays. This can be done using the clipboard or, even easier, by drag & drop. Working with the block library and configuring a status display with up to 32 different states is implemented analogously. The graphic editor allows direct modification of the properties of individual objects within grouped objects without ungrouping. Properties of multiple selected objects can be simultaneously modified in the same way (e.g. the line color). It must be possible to customize the graphic editor's user interface. Size and position of the individual palettes for colors, zooming, alignment functions, object types and styles are variable; when necessary, individual unneeded palettes can simply be hidden. Frequently used functions are available as icons in the symbol list. Well-organized configuration dialogs, which enable the assignment of parameters for the most important properties of an object in a dialog box, are available for most objects. This dialog box appears automatically as soon as the relevant object is placed in the display. The graphic editor also offers an option for manipulating an object's most important properties and even make them dynamic. The graphic editor provides multiple options for making object properties dynamic. In the first case, such properties are linked directly to internal variables or process variables. An animation dialog makes it possible, for example, to agree on value ranges for color changes. One way to make them dynamic is through the direct integration of scripts, which are integrated by Visual Basic Scripts. The graphic editor supports configuration on 32 display layers. In the case of complex displays with multiple superimposed objects, individual layers can be hidden to make the display much more transparent. A Help system for the online project is integrated in the visualization system as a matter of course, and can be configured with only a few entries. Here again, a multilingual definition must always be possible for this configuration. Objects created for the first time can be stored in a library and can be retrieved from there. It is thus possible to create company-specific, technology-specific or sector- specific standards which contribute to faster project generation. The visualization system recognizes the block library, which can be subdivided into a global library and a project-specific library. The global library contains pre-generated objects, sorted according to topic, which belong to the delivery scope of the visualization system (valves, motors, cable runs, indicating instruments, etc.). The project-specific library is used for individual projects. The objects can be configured as multilingual. The blocks in the library can be listed by name. Alternatively, they can be portrayed as icons so that individual objects can be identified faster and easier. Such objects can be added to a process image simply by using drag & drop. New objects can be added to the library just as easily. The user object "Variable block" allows modular configuration. This makes it possible to group any objects into a new object and define the relevant interface parameters for process interfacing. The names used by the configuring engineer can be stored in multiple languages, e.g. "Obergrenze" in German and "Upper Limit" in English. The display block can be stored in the library with drag & drop, then built into visualization system displays in the same way. Only the parameters defined as user-specific are linked to process variables. The global library contains a whole series of such user objects (e.g. operator control blocks) and can be expanded at any time as required. The benefit of HMI (Human Machine Interface) systems lies in the central operator control and monitoring of processes. This requires displays which permit a look into the plant. Typically, there is more than one process object of the same type, for instance motors, pumps, regulators and valves. The visualization system makes it possible to standardize the control and representation of such objects using the faceplate technique. The visualization system provides a very efficient way of configuring: functions which are needed repeatedly are defined only once, but every function call can use its own data (multiple usage with central modification capability). In order to represent objects (e.g. pumps, slide valves, motors, etc.) as well as object states (e.g. on/off, remote/local, etc.) in the process images, the contractor (supplier) must create symbol sets consisting of standardized symbols; the symbols must be used in all process images. The customer must also be able to modify existing symbols as well as to create new symbols. The system must automatically transfer all changes made to a symbol set to all process images. Detailed information on an object appearing in a process image can be visualized when required. The content and configuration of all plant displays must be coordinated with the contractor within the framework of the Specifications. 4.4.2 Curve displays Archived values can be represented in the form of a curve. Colors, for example, show limit value violations and malfunctions. Like the message window, the curve window also provides a toolbar for curve control. If desired, an individual key layout can be configured and stored with the associated operator control functions. The values in a display window can be viewed in detail using the reading line and the zoom function. The scaling of the time and value axis is adapted accordingly and the curve values for the display interpolated. An axis can be configured on the right or the left side for a curve window. Limit value violations are identified by a configurable color change when output in the curve window. Because the direction of the curves is configurable, a horizontal "direction" can be set for the curves, making a text function possible. 4.4.3 Message logging / evaluation / acknowledgement The message list can be shown in line-oriented message displays. The statuses of messages can be distinguished by color whenever necessary. Freely specifiable selection filters direct the view of the message display to individual process or plant sections. Multiple message displays can be used in an application with the visualization system. The following two distinct modes of representation are possible for message displays: - Dynamic message display (process message display) This view shows only messages which have already arrived and those currently pending. Messages which have already been read be configured so that they are automatically removed from the view. - Message display with archive view In this mode, all messages acquired up to this time are displayed, even those already read. Incoming messages can be displayed in an additional message window if required. In addition, graphic objects can indicate message events by changing their appearance. The message can be acknowledged via the graphic object. Message logs document the message sequence (message sequence log) or selected views in the archive (message archive log). It is printed out in page mode with the pages completely full; the message sequence log which is assigned exclusively to a line-oriented printer, is printed out line by line as messages arrive. The operator can scroll line by line or page by page, forwards or backwards through the messages shown in the message display, but can also jump to the beginning or end of the list. The messages visible on the screen can be acknowledged individually (single acknowledgement) or as a group (group acknowledgement). A group acknowledgement acknowledges all messages belonging to a group message display. The messaging system can also forward acknowledgements to the programmable controllers so that they can respond appropriately. For a better overview and for direct access to the required information, selections can be made at configuration time. Messages can also be stored in the configuration with message-related information. This information supports the operator with additional details each time the message appears. The message "Motor 25 malfunctioned", for instance, could contain information on rectifying the problem which caused the malfunction. 4.5 Logging system The visualization system must provide an integrated report system for printing out data. Logs are used for documenting process data and completed production cycles. They may contain e.g. messages and recipe data for generating shift logs, outputting batch data or documenting manufacturing processes for product or quality inspection. When configuring. print requests may be defined which determine the layout and the scope (number of pages) of a printout. It is also possible to stipulate cyclic hourly, daily and monthly reports. A report can also be started on a time-controlled/event-controlled basis or by direct operator input. The message sequence log can output incoming messages immediately on a line printer (line-by-line printout). Screen views set online can be printed out via Hardcopy whenever required. The layout of the reports is a combination of static and dynamic objects, as they are available in the graphic system. 4.6 Archiving system The visualization system's archiving system must archive process values and messages. The archiving of process values and messages is implemented to acquire and process data from the machine/plant. The analysis of archived process data provides information on the operational status of the plant/machine. The archiving is capable of time-controlled as well as manual or process-controlled swap- out of process values and messages for long-term archiving. At runtime, the swapped-out data are read in and selectively analyzed for the presentation and analysis of archived process values based in a configurable curve display. Reading of the values is supported by a reading line. The visualization system also supports the presentation and evaluation of archived messages based on a configurable message display. In addition to user-friendly archive navigation, a provision must also be made for external analysis of the archives using MS standard tools. Sequence archives and short-term archives must be used as part of the archiving system. The archiving system is based on external archiving media, such as CVS files and ODBC databases (e.g. MS Access), which are supported by Windows. 4.7 Recipes Recipes are used for generating and managing machine parameters and production data based on associated data records. Recipes and the associated data records are created with the user-friendly engineering tool and are pre-assigned data. A configurable spreadsheet object is used to display the data at runtime. The individual data record elements can also be depicted directly over multiple process images based on standard input/output fields. The data are thus presented to the operator in well-organized, easily readable technological views. The transfer of data records to or from the controller is based on synchronized data interchange with the controller. The visualization system is to ensure the backup of data records on local data media or via networks on remote data servers, as well as the import/export of data records (CVS files). Provisions must also be made for logging of data records (e.g. batch or shift logs). 4.8 Specifications Hardware and software specifications are required for the visualization system. The contractor is responsible for the generation of the specifications. Within the framework of the specifications, all details relating to problem definition and special requirements must be clarified and the solution carefully and fully explained. If necessary, the specifications must be revised and resubmitted to the customer as part of the technical clarification phase. Scope and content of the specifications Essentially, the scope of the specifications includes: - Configuration (hardware and software) - Functional description - Creation of the information lists - Creation of the plant displays 4.9 Display creation The procedures for display creation include: - Display draft (on paper or on the monitor) - Coordination with the customer - Incorporation of the required corrections - Re-coordination with the customer - Incorporation of any additional corrections - Conclusion of the display creation process The first plant display will be regarded as an exception. The purpose of this display is to clarify basics, such as subdivision, the number and location of the message lines, colors, symbols, and so on, with the customer. Multiple changes to this display are therefore to be anticipated. 4.10 Documentation The documentation must be arranged in such a way as to ensure that system structure and system function are clearly and easily identifiable as well as to ensure optimum preventive and corrective maintenance. Documentation scope: - Hardware documentation - Standard and system software documentation - Documentation of the data points - User manual - Documentation on the system parameterization - Plant displays in hardcopy form - Program listings of plant-specific application software All documents listed above must be collected and arranged in an orderly fashion in DIN-A4 file folders or on CD, and two copies must be presented to the customer for inspection, at the latest upon conclusion of the trial run. In addition, the delivery scope must include one copy of the software system on CD. 6. Technical specifications / quantity frameworks Upper limit values - Graphic displays 500 - Fields per graphic display 400 - Variables per graphic display 400 - Static text 30,000 - Graphic objects 2,000 - Complex objects per graphic 40 (e.g. bars) - Graphic lists / Text lists 500 - Entries in symbol lists 3,500 - Variables 2048 - Bit-triggered / analog messages 4,000/500 - Message text (number of characters) 80 - Number of process values per message 8 - Size of message buffer 1024 - Pending messages 500 - Archive 100 - Data that can be archived Process values, messages - Max. entries per archive 500,000 (incl. sequence archive) - Archive types Short-term archive, sequence archive (max. 400 per archive) - Data storage format CSV and link to ODBC database - Recipes 1,000 - Elements per recipe 2,000 - Data records per recipe 5,000 - Password protection - Passwords 100 - Number of authorizations 32 - Number of user groups 50 - Visual Basic Scripts 200 - Online languages, max. 16 - Controller link/interfacing - Number of links 8 (multiprotocol mode) 01. PC-based visualization system 01.01 Hardware guidelines 01.01. 0010 1 Installation as PC-based visualization system Minimum technical requirements: - Pentium III, 500 MHz processor - Graphics: 1024x768 to 1600x1200, True Color - Main memory: >= 256 MB - Hard disk (free space): >= 100 MB - Disk drive: 3.5“/1.44 MB - CD-ROM: Standard drive including all required accessories Delivery and commissioning. Make: ................................................. Type: ................................................... Dimensions: ........................................ Power requirements :........................... 01.01. 0020 1 Printer Installation in central control room Minimum technical requirements: - Color graphics printer - min. 9 pages/minute b/w, 30 s/color page - Single sheet (paper width up to DIN A3) - Noise level, max. xx dB - Data cable, length: min. 15 meters including all required accessories, incl. drivers for WIN 2000/XP Delivery and commissioning. Make: ................................................ Type: ................................................. Dimensions:....................................... Power requirements:.......................... 01.01. 0030 1 Static uninterruptible power supply for the visualization system, consisting of: - Compact, low-noise, single-phase UPS with matching design - Functioning principle on-line, i.e. connected loads must be supplied from the UPS without interruptions and free of any irregularities in the network - Power supply for inverter during brief interruptions and power failures thanks to integrated, maintenance-free sealed lead battery, automatic loading of the integrated lead battery while network is operating, automatic switchover to bypass mode in the case of stronger or longer overloads and load short-circuits - Simple operation and function indicators for operational status and load levels: -Network power available - Inverter On – bypass mode - Group error - Load indicator 0 to 150 % acoustical pre-warning when the battery's residual buffer time (at rated load) is only 1.5 minutes, computer interface Delivery and commissioning. Make: ................................................ Type: ................................................. Dimensions:....................................... Power requirements:.......................... 01.02 Software guidelines 01.02. 0010 1 Standard software: - Operating system: WINDOWS 2000 or XP - Microsoft Internet Explorer - Adobe Acrobat Reader Make: ................................................ Type/Version: .................................... 01.02. 0020 1 Visualization system – Standard package: For use as per preliminary remarks; delivered on CD-ROM incl. installation and documentation Offer must include: Runtime licenses, incl. all licenses required to operate all visualization components. Make: Siemens WinCC flexible Runtime or equivalent. Type/Version : ....................................... 01.02. 0030 1 Visualization system application software as per requirements; delivered on CD-ROM incl. installation of the visualization system, commissioning and documentation. 01.03 Engineering guidelines 01.03. 0010 1 The following services will be provided in coordination with the customer: - Specifications for hardware and software - Functional description - Creation of information lists - Definition of master data as per preliminary remarks as well as log parameterization according to the values provided by the customer; guidelines (short and long versions), completely installed and documented 01.03. 0020 System parameter assignments for measured values Completely installed, documented and put into operation 01.03. 0030 System parameter assignments for setpoint values Completely installed, documented and put into operation 01.03. 0040 System parameter assignments for count values Completely installed, documented and put into operation 01.03. 0050 System parameter assignments for binary signals (messages) Completely installed, documented and put into operation 01.03. 0060 System parameter assignments for binary signals (commands) Completely installed, documented and put into operation 01.03. 0080 1 Specifications and implementation of process images The process images must be designed as 1-to-1 concept, and must be coordinated with the customer. Once they have received final approved, they can be entered into the system. It must be assumed that small subsequent adaptations will be required. 01.03. 0090 1 Plant displays - overview displays With 5 display variables 01.03. 0100 Process images With integration of up to 20 variables 01.03. 0100 Process images With integration of up to 40 variables 01.03. 0100 Process images With integration of up to 60 variables 01.03. 0100 Process images With integration of more than 60 variables 01.03. 0100 Curve displays For curves 01.03. 0110 1 Generation of a daily report Incl. draft, revision and implementation in the visualization system. 01.03. 0111 1 Generation of a monthly report incl. draft, revision and implementation in the visualization system. 01.03. 0112 1 Generation of an annual report incl. draft, revision and implementation in the visualization system. 01.03. 0120 1 Acceptance test The contractor will install all visualization system computers as well as a programmable controller with an option for simulation of analog and binary signals at its factory. The most important plant functions will be tested. The subsequent acceptance will be documented in a report. 01.03. 0130 1 Turnkey installation consisting of the following: - Installation of the hardware in the plant - Connection of the power supplies - Connection of the various components with standard connecting cables - Connection of the visualization system components to the process bus - Connection of the I/O devices (printer, etc.) including all materials. Space requirements and dimensions must be coordinated with the customer. 01.03. 0140 1 Commissioning of the hardware: All devices in the visualization system will be tested on the customer’s system using test programs and put into operation, including link to the automation level. 01.03. 0150 1 Commissioning of the software: Commissioning of the entire visualization system by the contractor on the customer's system. This will be followed by a performance test by the customer with support from the contractor. All functions and the interaction of all system components will be tested. Deviations from the Specifications or malfunctions of the visualization system will be documented in a report. The system will be considered accepted when the system test shows only minor flaws which will not impair the functionality of the system. If system flaws are detected during the test, the contractor will be granted a period of 20 working days for remedying defects. 01.03. 0160 1 Training of operating personnel - on site at the plant - instruction in system handling - practical work on the system - more advanced training for _xx___ persons Duration: xx days 01.03. 0170 1 System coordinator - On site at the plant - Rectify simple malfunctions of the visualization system - Display creation / modification of process images - Parameter input / Modification within the framework of system maintenance - System-related training for _xx___ persons for xx days 01.03. 0180 1 Service contract The following services, in detail, must be offered for the visualization system's hardware and software components, consisting of the various PCs and the associated I/Os (monitors, keyboards, printers, data backup devices). Restoration of the specified condition (corrective maintenance): - Troubleshooting when faults/errors occur - Elimination of errors, faults and damages to the hardware through corrective maintenance or replacement of the defective parts or modules - On system software products through delivery of corrected software (new product revision level) or new delivery (new product version) - If the problem cannot be rectified within a short period of time, the contractor will provide a temporary solution to bypass the problem if the amount of overhead required to do so is reasonable and the problem does not allow the customer to perform urgent tasks that cannot be delayed. - The response time is the time required to dispatch a service specialist or to begin teleservicing once a problem has been reported 01.03. 0180 1 Service contract As described above, but with a response time during normal working hours from Monday through Friday 01.03. 0180 1 Service contract As described above, but with a response time during normal working hours from Monday through Friday and within the contractor's warranty period 01.03. 0190 1 Engineering specifications The following services must be provided in coordination with the customer: - Creation of the hardware/software specifications - Functional description - Creation of the information lists - Definition of the master data and assignment of log parameters - Operations journal monthly report, Operations journal annual report, error log, event log, completely installed and documented on external data medium 1 Ausschreibungstext_WinCC_flexible.doc, Seite 3 von 22