SIMATIC HMI WinCC V7.0 System Description - DCE FEL ČVUT v ...

More documents

Recommendations

Info

3.5 Traceability and validation Options SIMATIC WinCC Requirements and licensing ● Microsoft Windows Server operating system at the location of the audit database ● Audit complete package RC: license for runtime and configuration (engineering) on each operator station on which WinCC/ChangeControl is configured. ● Audit runtime package RT: license for runtime on each operator station on which configuration changes are logged. Application Once a plant has been commissioning and validated, if necessary, the project version is archived via project versioning. Each time the configuration changes as the result of small adjustments, large expansions, or anything in between, all changes made in the plant are recorded seamlessly with WinCC/ChangeControl (in a change log), thus providing specific, documented evidenceof changes made, for example, when the plant is expanded. The change log covers the entire plant, from machine-level configurations all the way to higher-level WinCC projects. The reproducible versions of the WinCC project created with project versioning make it possible to go back to the last executable version or any other version in the event of problems with the plant or expansions. In the event of plant shutdowns, for example, plant constructors (such as OEMs) or plant operators can quickly and efficiently verify the changes that have been made in the plant and can infer the cause of the problem. This facilitates error analysis, saves services costs, and reduces downtime. You can also perform a risk analysis of the change based on the change log in the event of plant expansion and subsequent revalidation. WinCC/ChangeControl also helps you fulfill traceability requirements in compliance with FDA 21 CFR Part 11 and EU 178/2002. Configuration auditing In the course of a configuration, changes are made in various WinCC editors. These changes are logged with configuration auditing. Examples: ● WinCC Explorer with central properties, such as clientserver ● Tag management with communication links ● Message system ● Archive system ● Text Library ● User administration with access rights ● Reporting and logging system ● WinCC/User Archives Every change generates an audit trail entry, which is stored in the audit database. This audit trail contains the following information: ● Time stamp ● Modified object: old value, new value ● User logged on to the WinCC server ● Computer name of the WinCC server ● WinCC project Some objects are not stored in the WinCC database and cannot therefore be logged in audit trails. These include process pictures and scripts you create yourself. Changes made to these objects are recorded by document control. Document control Figure 107 Archiving and restoring projects or project data In order to version individual local files in the WinCC project during configuration, place them in the document control database: ● Process pictures ● C functions and C actions ● VBScript functions and VBScript actions ● Line layouts and page layouts ● Any documents in the project folder When a file is changed, a local copy of the file from the document control database is created. Other users are not able to edit the file during this time. After the change is made, the file is returned to the document control database as a new version, along with change information added by the user. This allows you to track individual changes from version to version, in the change history, for example, in which each change is clearly documented. If necessary, previous versions and deleted files can also be restored in WinCC. Special features ● In the Audit Viewer, audit trails (configuration auditing) can be displayed, searched, filtered, printed, and exported as .xls files. Query Builder is used to create, save, and edit user-specific queries for audit databases. ● In addition, all documents in the project folder under "Misc. Documents" are automatically added to document control. ● You can compare the current version of a file with its previous version. ● The document control database can be archived. SIMATIC WinCC System Description 70 A1900-L531-B996-X-7600, 09/2008
Options SIMATIC WinCC 3.6 Batch processes 3.6 Batch processes 3.6.1 SIMATIC BATCH for WinCC Note Currently, SIMATIC BATCH is only released for specific versions of WinCC. For more information, refer to "Support/ Product support" (see "More information about SIMATIC WinCC"). Definition A discontinuous process produces a product in discrete groups, called batches (batch process). The product quantities are finite and can be clearly identified. An essential factor in batch processing is that end customers themselves can optimize production processes and change them over to new and different products without changing the automation system. SIMATIC BATCH for WinCC provides this flexibility far beyond mere recipes (see WinCC/User Archives). Features: ● Short product life cycles and wide range of products ● Different products produced in the same plant ● Frequent changes to production process ● Limited product quantity/volume ● Recipe-controlled (production know-how) ● Production is documented in verifiable logs. Application In the process control industry, discontinuous processes are taking on an increasingly important role. Rapid response to changes in market conditions, requirements for verifiable documentation of production (FDA compliance), and fulfillment of legal standards and control specifications place significant demands on the flexibility and reliability of automation systems in plants, which often are only partially automated and require frequent operator intervention (setup times). With SIMATIC BATCH for WinCC, production processes are flexibly structured, planned, and assigned to different production configurations, for example, to control multiple instances of the same production line and enable optimal plant utilization. Examples: dye-mixing plants, fertilizermixing plants, and plants for the production of food, beverages, and tobacco. The fact that SIMATIC Batch for WinCC has access to SIMATIC WinCC configuration data means safe operator management and a quick response to process faults. In addition, duplicate configuration and the errors associated with it are avoided. Benefits: ● High availability through redundant plant configurations provides protection against loss of batch data ● Modular architecture with flexible scalability ● Assignment planning of process units, automatic selection of process units ● Optimum adaptation to plant size and individual requirements, such as different controllers ● Greater production flexibility, shorter time to market ● Optimized utilization of plants with process-unit-neutral, hierarchical recipes to ISA S88.01 ● Flexible control strategies and assignment of recipes during runtime ● Reproducible production processes in batch logs ● Consistent product quality, even after x number of batches ● Validation support in compliance with 21 CFR Part 11, lower validation costs ● Reduced operating and lifecycle costs through the use of standard products ● Minimized engineering overhead through type/instance concept that is advantageous for validation Owing to its scalability, SIMATIC BATCH for WinCC is equally well suited for small plants and large quantity structures. Complexity increases along with the number of products and the number of production lines. With SIMATIC BATCH for WinCC, multiple-line/multiple-product plants can be automated in compliance with standards. Structure Figure 108 SIMATIC BATCH for WinCC: job planning of batch recipes SIMATIC BATCH is distributed to SIMATIC BATCH for WinCC (clients) and one SIMATIC BATCH for WinCC (server), all of which work with the same plant project. SIMATIC BATCH for WinCC communicates with the automation system (for example, to write recipe parameters or read actual values) via the WinCC server. Similarly to WinCC server and OS clients, SIMATIC BATCH for WinCC (server) and SIMATIC BATCH for WinCC (clients) are configured on the engineering station and loaded from there. The plants are always the same; only the production processes change. Therefore, SIMATIC BATCH for WinCC separates the automation system from the recipe system. The recipe system represents the production processes hierarchically and is managed by operating staff. Centrally modifiable ROP libraries (Recipe operation) with hierarchical recipes to ISA S88.01 and a process-unit-neutral configuration guarantee a high level of reusability. SIMATIC WinCC System Description A1900-L531-B996-X-7600, 09/2008 71
Page 3:
Table Of Contents 1 SIMATIC WinCC S
Page 6 and 7:
1.2 Introduction SIMATIC WinCC Syst
Page 8 and 9:
1.3 Investment protection SIMATIC W
Page 10 and 11:
Page 12 and 13:
Page 14 and 15:
2.1 Expandability Process visualiza
Page 16 and 17:
Page 18 and 19:
Page 20 and 21:
Page 22 and 23:
Page 24 and 25: 2.2 Efficiency Process visualizatio
Page 36 and 37: 2.3 Security and availability Proce
Page 42 and 43: 2.4 Quality and traceability Proces
Page 48 and 49: 2.5 Openness and integration Proces
Page 50 and 51: 2.5 Openness and integration Proces
Page 52 and 53: 3.1 Scalable plant configurations O
Page 54 and 55: 3.1 Scalable plant configurations O
Page 56 and 57: 3.2 Increased availability Options
Page 62 and 63: 3.3 Plant Intelligence Options SIMA
Page 72 and 73: 3.5 Traceability and validation Opt
Page 76 and 77: 3.6 Batch processes Options SIMATIC
Page 78 and 79: 3.7 Openness Options SIMATIC WinCC
Page 80: 3.8 More information about SIMATIC
show all

SIMATIC HMI WinCC V7.0 System Description - DCE FEL ČVUT v ...

Create successful ePaper yourself

Delete template?

Save as template?