Metasys® for Validated Environments (MVE ... - Johnson Controls
Metasys® for Validated Environments (MVE ... - Johnson Controls
Metasys® for Validated Environments (MVE ... - Johnson Controls
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Figure 7 shows the standard M-Alarm Reportinterface. From master M-Alarm Report, alarms andevents can be listed and filtered <strong>for</strong> review. Thissame logger can be used to view the audit trail ofalarms and operator transactions. It gives theoperator a window into all automatic and manualcontrol actions that have occurred in the system,collected in the secure database.All transactions contain: old and new values, date andtime of occurrence, identification of the operator, eventname, device tag name, units, and optionally an operatorannotation of the event.Figure 7: M-Alarm ReportsTime-stamped Audit TrailsThe ability to chronologically retrace alarm andevent transactions is paramount to reproducing anaudit trail during a facility system’s review by theFDA. This Part 11 requirement is met byimplementing the M-Alarm Logger of the <strong>MVE</strong>. Inaddition to logging alarms and the operator’sresponse to those alarms, it also logs events as theyoccur on the network.The secure system database contains all of thesealarms and events. The entries log both the time anddate of the individual operator transaction (<strong>for</strong> example,Login, Logout, Alarm Acknowledge, and Value Adjust orOverride) and also log the identity of that operator,providing an audit trail of the operation of the system.6 Metasys <strong>for</strong> <strong>Validated</strong> <strong>Environments</strong> (<strong>MVE</strong>) Product Bulletin